The course syllabus states that you should be able to:
7.1	Analysis
	Methods of researching an existing system: Identify and describe methods of researching an existing system (e.g. observation, interviews, questionnaires and examination of existing documents) Discuss the disadvantages and advantages of the different methods. Recording and analysing information about the current system: Describe the need to identify inputs, outputs and processing of the current system Describe the need to identify problems with the current system Describe the need to identify the user and information requirements for the new system. Recording and analysing information about the current system: Describe the need to identify inputs, outputs and processing of the current system Describe the need to identify problems with the current system Describe the need to identify the user and information requirements for the new system
7.2	Design
	Describe how it is necessary to design documents, files, forms/inputs, reports/outputs and validation Produce designs to solve a given problem Design data capture forms and screen layouts Design report layouts and screen displays Design validation routines (including length check, type check, format check, presence check, check digit) Design the required data/file structures (e.g. field length, field name, data type).
7.3	Development and testing
	Testing designs: Describe how data/file structures are created and tested Describe how validation routines are created and tested Describe how input methods are created and tested Describe how output formats are created and tested. Testing strategies: Describe the need to test each module Describe the need to test the whole system Describe testing using normal data including definition and examples Describe testing using live data including definition and examples Describe testing using abnormal data including definition and examples Describe testing using extreme data including definition and examples. Improvements needed as a result of testing: Describe how it may be necessary to improve the system and make changes (e.g. data/file structures, validation rules,input methods, output formats may need to be amended/improved).
7.4	Implementation
	Different methods of system implementation: Describe the four methods of implementation (direct changeover, parallel running, pilot running, phased implementation). Methods of implementation: Identify suitable situations for the use of different methods of system implementation (e.g. organisations or departments within organisations which need a quick changeover, organisations or departments within organisations which cannot afford to lose data) Describe advantages and disadvantages of each method of implementation.
7.5	Documentation
	Technical documentation for an information system: Explain the need for technical documentation Identify the components of technical documentation (e.g. purpose of the system/program, limitations of the system, program listing, program language, program flowcharts/algorithms, system flowcharts, hardware and software requirements, file structures, list of variables, input format, output format, sample runs/test runs, validation routines). User documentation for an information system: Explain the need for user documentation Identify the components of user documentation (e.g. purpose of the system, limitations of the system, hardware and software requirements, how to load/run/install software, how to save a file, how to print data, how to add records, how to delete/edit records, input format, output formats, sample runs, error messages, error handling, trouble-shooting guide/help line, frequently asked questions, glossary of terms).
7.6	Evaluation
	Describe the need to evaluate a solution in terms of the efficiency of the solution, the ease of use of the solution, and the appropriateness of the solution. Describe the need for a variety of evaluation strategies e.g. Compare the solution with the original task requirements Identify any limitations and necessary improvements to the system Evaluate the users' responses to the results of testing the system.