1. IB Computer Science Section 1: Systems life cycle and software development

2. The systems life cycle Analysis Design Implementation Operation & Maintenance

3.  Interviews with users and domain experts  Questionnaires and Surveys  Observation of existing system  Reading documentation Analysis: Data Collection

4.  Requirements specification  Inputs: what data/information will the system require  Outputs: what information is expected from the system  Human resources requirements  Schedule  Critical success factors. Key objectives. Analysis: Requirements Specification

5. Analysis: IPO Input Processing Output What data or information will the system need? What will the system do to the data? How will information be stored and represented? What information should the system give its users? Three stages of programming:

6.  Brief description of the proposed system  Estimated costs  Financial, technical, legal responsibility  Estimated completion date Analysis: Feasibility Report

7. Analysis: Systems Flowcharting Tape Storage Disk Storage Document Process Input/ Output Manual Input Documents

8. Analysis: Pay System Example Master File Transaction File Payslips Calculate Pay Hours worked Updated Master File

9. Analysis: Systems Flowchart Past Paper Question

10. Analysis: Systems Flowchart Past Paper Answer Customer orders are collected on paper, keyed in, and stored in a customer orders file. A stock master file is searched to determine whether sufficient stock is available, and a report produced. The mark scheme awarded one mark for each of the boxes, up to a maximum of five boxes. In my opinion you could have left out the keyboard input, or you could have specified the master file as tape drive (sequential access storage), and you would still get full marks.

11.  Why is software development considered to be cyclic?  Why is data collection important? What are the methods of data collection?  What is a requirements specification? What does it contain and what purpose does it serve?  Outline the features of a feasibility report.  Annotate the systems flowchart you created in the past paper exercise. Try to think of another computerised process you could model with a systems flowchart. Discuss with a colleague and prepare the flowchart. Resources: Computer Science Java Enabled, IB Computing website, Richard Jones’ site (Int. Sch. Toulouse). Analysis: Review