| 0417 Information and Communication Technology Past Paper Resources
Paper 1 Topic Questions and Mark Schemes / Topic 7 The systems life cycle
  • 7.1-IGCSE-ICT-analysis-Mark-Scheme-Paper-1-Set-1.pdf
  • 7.1-IGCSE-ICT-analysis-Mark-Scheme-Paper-1-Set-2.pdf
  • 7.1-IGCSE-ICT-analysis-Topic-Questions-Paper-1-Set-1.pdf
  • 7.1-IGCSE-ICT-analysis-Topic-Questions-Paper-1-Set-2.pdf
  • 7.2-IGCSE-ICT-design-Mark-Scheme-Paper-1-Set-1.pdf
  • 7.2-IGCSE-ICT-design-Mark-Scheme-Paper-1-Set-2.pdf
  • 7.2-IGCSE-ICT-design-Topic-Questions-Paper-1-Set-1.pdf
  • 7.2-IGCSE-ICT-design-Topic-Questions-Paper-1-Set-2.pdf
  • 7.3-IGCSE-ICT-development-and-testing-Mark-Scheme-Paper-1-Set-1.pdf
  • 7.3-IGCSE-ICT-development-and-testing-Mark-Scheme-Paper-1-Set-2.pdf
  • 7.3-IGCSE-ICT-development-and-testing-Topic-Questions-Paper-1-Set-1.pdf
  • 7.3-IGCSE-ICT-development-and-testing-Topic-Questionss-Paper-1-Set-2.pdf
  • 7.4-IGCSE-implementation-Mark-Scheme-Paper-1-Set-1.pdf
  • 7.4-IGCSE-implementation-Mark-Scheme-Paper-1-Set-2.pdf
  • 7.4-IGCSE-implementation-Topic-Questions-Paper-1-Set-1.pdf
  • 7.4-IGCSE-implementation-Topic-Questions-Paper-1-Set-2.pdf
  • 7.5-IGCSE-documentation-Mark-Scheme-Paper-1-Set-1.pdf
  • 7.5-IGCSE-documentation-Topic-Questions-Paper-1-Set-1.pdf
  • 7.6-IGCSE-evaluation-Mark-Scheme-Paper-1-Set-1.pdf
  • 7.6-IGCSE-evaluation-Topic-Questions-Paper-1-Set-1.pdf
Note:

The systems life cycle IGCSE ICT Topic Questions

The following topics are included:

7.1 Analysis  Analysis of the current system :Characteristics, uses, advantages and disadvantages of the research methods of observation, interviews, questionnaires and examination of existing documents Record and analyse information about the current system The need to identify the inputs, outputs and processing of the current system, problems with the current system, the user and information requirements for the new system System specification Identify and justify suitable hardware and software for the new system

7.2 Design

Design: Design file/data structures, input formats, output formats and validation routines File/data structures including field length, field name, data type, coding of data for example M for male, F for female Validation routines including range check, character check, length check, type check, format check, presence check, check digit Input formats including data capture forms Output formats including screen layouts and report layouts 

7.3 Development and testing :Testing : The need to test the system before implementation Test designs, test strategies, test plan (test data, expected outcomes, actual outcomes, remedial action) following testing Test designs including the testing of data structures, file structures, input formats, output formats and validation routines Test strategies including to test each module, each function and the whole system The definition, characteristics and use of test data using normal, abnormal and extreme data The use of live data

7.4 Implementation System implementation :Characteristics, uses, advantages and disadvantages of the four methods of implementation, direct changeover, parallel running, pilot running, phased implementation

7.5 Documentation: Documentation: Characteristics, uses and purpose of technical and user documentation Components of technical documentation including: 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 Components of user documentation including: 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 format, sample runs, error messages, error handling, troubleshooting guide/ helpline, frequently asked questions, glossary of terms 

7.6 Evaluation : Evaluate a solution : Evaluate a solution including the efficiency of the solution, the ease of use of the solution, and the appropriateness of the solution 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