The systems life cycle

Topics

Choose a topic to revise

Sample objectives

What this unit covers

• Analysis: Students should be able to understand and explain the analysis of the existing system, including the features, applications, benefits, and drawbacks of various research methods such as observation, interviews, surveys, and reviewing existing documents. They must gather and assess information regarding the current system, recognizing the necessary inputs, outputs, and processing involved, as well as identifying issues with the current system and the user and information needs for the new system. Additionally, they should be able to determine and justify appropriate hardware and software for the new system.
• Design: Students should be familiar with and comprehend various aspects of design, including file and data structures, input and output formats, and validation processes. This encompasses understanding file structures such as field length, field name, data type, and coding conventions (e.g., M for male, F for female). They should also grasp validation routines like range checks, character checks, length checks, type checks, format checks, presence checks, and check digits. Additionally, students should know about input formats such as data capture forms and output formats including screen layouts and report layouts.
• Development and testing: Learners should comprehend the importance of testing a system prior to its deployment. They should be familiar with creating test designs, strategies, and plans that include test data, expected results, actual results, and corrective measures. This includes testing data structures, file structures, input formats, output formats, and validation routines. They should understand strategies for testing each module, function, and the entire system. Additionally, they should know the definition, characteristics, and application of test data, which encompasses normal, abnormal, and extreme data, as well as the use of live data.
• Implementation: Learners must comprehend the characteristics, applications, benefits, and drawbacks of the four implementation methods: direct changeover, parallel running, pilot running, and phased implementation.
• Documentation: Understand the features, purposes, and uses of both technical and user documentation. Recognize the parts of technical documentation such as system/program purpose, system limitations, program listing and language, flowcharts or algorithms, hardware and software needs, file structures, variable lists, input and output formats, sample or test runs, and validation routines. Identify components of user documentation including system purpose and limitations, hardware and software requirements, instructions for loading, running, or installing software, saving files, printing data, adding, deleting, or editing records, input and output formats, sample runs, error messages and handling, troubleshooting guides or helplines, FAQs, and glossaries.
• Evaluation: Students should be able to assess a solution by examining its effectiveness, user-friendliness, and suitability. They should compare the solution against the initial task requirements, recognize any shortcomings, suggest improvements to the system, and evaluate user feedback from testing the system.