1. The Systems Life Cycle AS Computing F451 AS Computing F451

2. Stages of the life cycle Exact definitions vary, but the main stages of the life cycle are: Exact definitions vary, but the main stages of the life cycle are:

3. Waterfall & Spiral 2 key methodologies of the system life cycle 2 key methodologies of the system life cycle What are the differences? What are the differences?

4. Information gathering Interview: This can be time-consuming, but it does allow you to probe for answers and get first-hand information. Interview: This can be time-consuming, but it does allow you to probe for answers and get first-hand information. Questionnaire: This is useful when there are lots of users, although there is a limit to how much you will find out. Questionnaire: This is useful when there are lots of users, although there is a limit to how much you will find out. Observe the current system: Although time- consuming, this is objective rather than subjective and you might spot things that the user doesn’t. Observe the current system: Although time- consuming, this is objective rather than subjective and you might spot things that the user doesn’t. Examine the existing documentation: This is very useful for identifying the data requirements, as well as the input and output required. Examine the existing documentation: This is very useful for identifying the data requirements, as well as the input and output required.

5. Feasibility study A feasibility study is a report to identify the possible solutions to the problem and how ‘possible’ they are. A feasibility study is a report to identify the possible solutions to the problem and how ‘possible’ they are. Technical, Economics, Legal, Social feasibility of the new system. Technical, Economics, Legal, Social feasibility of the new system. A typical feasibility study would look at the following options: A typical feasibility study would look at the following options: –Should we: Stick with the old system? Adapt the old system? Create a new computerised system? –Should we: Buy an off-the-shelf package? Employ a programmer to create bespoke software? Write it in-house? –Could new system be developed in the required time?

6. Key Factors in a Feasibility Study Technical Technical –Is the HW/SW available to solve this problem? Economic Economic –Is the proposed solution cost effective Social Social –Impact on jobs, skills, training of staff

7. Importance of Analysis Problem must be accurately defined to solve it effectively Problem must be accurately defined to solve it effectively User may not understand potential of computer systems User may not understand potential of computer systems Developer not likely to understand the industry which the user is working in Developer not likely to understand the industry which the user is working in Developer must produce a solution/software that the user requires to meet their needs Developer must produce a solution/software that the user requires to meet their needs Clear communication between user and developer is important Clear communication between user and developer is important

8. Requirements Specification Contains… – –Input requirements – –Processing requirements – –Output requirements – –Clients agreement to requirements (signed) – –What Hardware will be needed to run new system

9. If problem is not defined accurately at the beginning…. Client will be unhappy Client will be unhappy Software will be useless... Software will be useless... Programmer will not get paid! Programmer will not get paid!

10. DesignDesign How will the system be produced? How will the system be produced? HCI HCI Pseudo Code Pseudo Code Database Design Database Design –Fields –Records

11. Design Specification Used by programmers to ensure they are producing the correct system Input design Output design Data structure Pseudo Code algorithms/flowcharts Data flow diagrams Entity Relationships Diagram Sitemaps

12. ImplementationImplementation Programming! Programming!

13. Installation Strategy Method of implementation – –parallel/pilot/phased/direct Training program must be devised Hardware must be purchased and installed System must be tested with real data by end users Write technical and user documentation

14. Test Data Normal Normal Extreme Extreme Erroneous Erroneous Enter Number between 1 and 10 510No

15. DocumentationDocumentation User Manual User Manual –Written from the users point of view on how to use the system Technical Documentation Technical Documentation –Variable Names, Data Structure, how the code works, Procedures. DFDs, Flowcharts, Entity Relationship Diagrams. Meant for future programmers.

16. User Manual Contents of user manual usually include… Contents of user manual usually include… – –Installation instructions – –Minimum required hardware specifications – –Input /Output procedures – –How to operate the system – –Backing up and archiving procedures – –Error messages/trouble shooting – –FAQs

17. Technical Documentation Written for future programmers. Written for future programmers. Contains Contains –Variable Names –Data Structure –how the code works –Procedures names –DFDs –Flowcharts –Entity Relationship Diagrams.

18. Data Flow Diagram (DFD) This is a diagrammatical way of showing how data moves around a system. This is a diagrammatical way of showing how data moves around a system. It is not concerned with how the system processes the data – it just shows the flows. It is not concerned with how the system processes the data – it just shows the flows. It uses four symbols: It uses four symbols:

19. DFD example The following is a DFD for a meter reading: The following is a DFD for a meter reading:

20. EvaluationEvaluation End User Requirements decided on in Analysis End User Requirements decided on in Analysis Does it meet them? Does it meet them? Future Enhancements Future Enhancements Important to user because need to be sure software performs as required – is it actually what they wanted?! Important to user because need to be sure software performs as required – is it actually what they wanted?! Important to developer because it determines the end of the job if they are being paid for producing a suitable solution Important to developer because it determines the end of the job if they are being paid for producing a suitable solution

21. Software Maintenance Once software is completed it needs to be maintained/upgraded as its requirements change Once software is completed it needs to be maintained/upgraded as its requirements change Corrective Maintenance Corrective Maintenance –To correct bugs found in software when being used Adaptive Maintenance Adaptive Maintenance –To alter software because of external need eg VAT paid changes from 17.5% to 15% Perfective Maintenance Perfective Maintenance –To improve performance of software