The study performed a systems analysis and design of the Central Luzon State College Admission Test Information System (CLSU CAT IS). The CLSU CAT IS is a project sought to solve the problem of the CLSU Testing and Evaluation Center (CTEC) in the management (namely; capturing, retrieval, storage, manipulation and display) of data about the profile of the CLSU CAT applicants and the CAT result itself.
The approach used in the conduct of the systems analysis and design was based on the seven phases of the Systems Development Life Cycle (SDLC) Methodology by Hoffer, Jeffrey A. et al. (Hoff’ 96), namely: (1) Project Identification and Selection , (2) Project Initiation and Planning, (3) Analysis, (4) Logical Design, (5) Physical Design, (6) Implementation, and (7) Operation and Maintenance.
In the Project Identification and Selection phase, a preliminary understanding of the situation was narrated when the CTEC requested for the development of the CLSU CAT IS. In the Project Initiation and Planning phase, three documents were produced: (1) the Statement of Work (SOW) that enumerates and describes what the project will deliver and outlines all work required to complete the project; (2) the Baseline Project Plan (BPP) Report that contains all information collected and analyzed during planning, and reflects the estimate of the project’s scope, benefits, costs, risks and resource requirements; and (3) the Statement of Project Scope (SPS) that enumerates and describes the project’s scope.
The system requirements were determined and structured in the analysis phase. The systems look and feel to the user such as input and output interfaces forms and reports are designed in the logical phase. The logical structure of the database was laid out as well. The logical specifications of the system were transformed into technology-specific details in the physical design phase.
The study however, did not produce the actual system; instead, it built a prototype that could perform the system’s features and capabilities. Consequently, in the implementation phase, rather than coding the programs and modules on the processes developed in the prior phases, a comprehensive list of these programs and modules was prepared and a coding plan was laid out. Further, instead of documenting results of testing, training, and conversion, plans were developed for these activities. In the maintenance phase, plan and standards in conducting maintenance were drafted.
