Museum database management system

Hassan, Nur Haslina (2016) Museum database management system. Project Report. Universiti Teknikal Malaysia Melaka, Melaka, Malaysia. (Submitted)

	Text (24 Pages) Museum database management system.pdf - Submitted Version Download (264kB)
	Text (Full Text) Museum database management system.pdf - Submitted Version Restricted to Registered users only Download (3MB)

Abstract

In general, the report discuss on the process of developing a system named Museum Database Management System (MDMS) from starting phase until the end phase. The report start with the introduction chapter that comprises of project background, problem statements, the objectives of developing the system, the significance of the project and the boundary of the system. It continues with project methodology and planning chapter that discuss on the methodology to be used in developing the system which is in this case, Agile Software Development Methodologies. It simplicity and work minimization concept makes it an ideal method in developing the system. Gantt Chart has been used as a guideline in order to complete the system within the time given. The report went more detail in the analysis chapter where the functional and non functional requirement have been specified in level 0 of data flow diagram and level 1 of data flow diagram. The diagram indicates the flow of data through different processes or function in the MDMS. In the design chapter, the system architecture design that have been implemented for the system is in three-tier design which comprises of presentation tier, application tier and database tier. The Entity Relationship Diagram (ERD) of the system consists of eight (8) tables named Activity, Employee, Asset, Ticket Info, Visitor, Visit, Museum and Booking. The implementation chapter shows all the Data Definition Language (DDL), Data Manipulation Language (DML), stored procedures and triggers used in developing the system. After the completion of implementation part, testing activity is conducted with a list of test requirement is being specified in the form of test cases and being test in the form of test plan. The report is concluded with the possible weaknesses and strengths and suggestion of improvement have been stated for guidance of future developer.

Actions (login required)

View Item