Koku Management System

Siti Fairuz, Ab Rahman (2011) Koku Management System. Project Report. UTeM, Melaka, Malaysia. (Submitted)

	PDF (24 pages) Koku_Management_System_-_24_pages.pdf - Submitted Version Download (456kB)
	PDF (Full Text) Koku_Management_System_-_Full_Text.pdf - Submitted Version Restricted to Registered users only Download (4MB)

Abstract

Koku Management System has been developed using Oracle Fom1 Developer 1 Og as a graphical user interface and Oracle 1 Og as a scripting language. The system has been divided into seven chapters in this repmi. The chapters start from introduction to the system. This chapter was explained more detail about the system and what the system should be. Koku Management System could facilitate students SMK Dm·ian Tunggal to check their co-curriculum marks, knows new announcements from their teachers Next chapter is Literature Review and Project Methodology, this chapter included overall the literature review of the system, domain of the system, techniques to get information and the existing system to serve as a reference. Then, the next chapter is Analysis. To develop and implement a system, the analysis should be carried out to ensure that all targets to the original purpose are successfully. The problem analysis is describing the current system situation using Data Flow Diagram (DFD) and context diagram. This chapter also is focus on requirement analysis for Koku Management System for SMK Durian Tunggal. The next chapter is Design. The database design is included in the project. The database design is based on the conceptual and logical database design. Next chapter is Implementation. During the implementation phase, the system is built, tested and instal led. The activities for this chapter are include with tasks to make sure the software deployment are suitable to the system requirement and also discusses the software configuration and the version control procedure. Then, the next chapter is Testing. The level of testing will be done after the implementation of the system has been completed. At this level, errors that may occur in the system can be detected before the system is handed over to the end user and the last chapter is Project Conclusion. This chapter is about the overall conclusion of the system such as the strengths and the weaknesses of the system also have the proposition of the system.

Actions (login required)

View Item