Sytem Design Life Cycle

Sytem Design Life Cycle

1. Analysis

   • Feasibility
     • This is done to make sure that making a new system is worthwhile
     • Sometimes, it may not be necessary, as the problem could easily be solved by a new computer system.
     • The feasibility study contains
       • Indicates to what extent the requirements can be met
       • What software and hardware will be used to develop the system and for what cost
       • Changes that may need to be made to the organisation
       • A suggested plan for the development of the system
       • Requirement Specification (Imputs, processes and outputs required and required hardware and software
     • Some problems are not ‘feasible’. The report is discussed in a meeting with the users in order to agree whether to go ahead with the project.
     • It is collected by
       • Observing and Using the current system
       • Consulting current documentation
         • This is looking at the
       • Carry out a questionnaire
         • Good because it allows them to get a lot of data very quickly but the data is quantitative and so doesn't have much in depth information about the system
       • Interview staff/Customers/Employees
         • This is good since it collects quantitative data but it is very time consuming
     • Questions asked
       • Is it cost effective?
       • Will it be time effective?
       • Is the System Affordable?
       • Can the system be made in the given time limit?

2. Maintenance

3. Design

4. Implementation

5. Testing

6. Evaluation