Software Development LifeCycle

Category: Entertainment

Presentation Description

No description available.


Presentation Transcript

Software Development:

Software Development

Software Development Lifecycle:

Software Development Lifecycle


Analysis This is the process of writing out clearly what the solution to the problem must to. Understanding the problems Identifying problems with the current system Identifying the needs of users Investigating similar systems elsewhere Investigating what input, processing and output are needed Establishing what tasks need to be completed Establishing deadlines for completion of tasks Problem specification:- must be clearly understood by client and developers.


Analysis Tools Flow charts Data flow diagrams Structure diagrams


Design The design stage looks at how the new system will be built. Software systems can be broken down into: Input Process Output This stage looks at the design of all three. When the design is complete, a document called a design specification is created. This is shown to users for their comments.


Design The Design Specification The hardware platform (PC, mainframe) The software (off the shelf, bespoke) The outputs (hardware, reports) The processing (sorting, searching, grouping) The inputs (data capture, input devices) Storage (devices, method) Security and backup The user interface (GUI, command line) The modular design of each program in the application The test plan Documentation including systems and operations documentation.


Implementation Programs written, tested and documented Data loaded from old system to new system Staff trained on new system May be parallel running of both systems for a while or direct implementation or phased implementation System maintained by keeping it up-to-date, solving any problems and writing new programs when required.


T esting As soon as a system is developed it should be checked against user requirements to ensure the system does everything the user wants. Four stages System tested with data that contains no errors to see if it produces correct results. Known errors are introduced into the data to see how the system handles them Output is produced and checked Extreme data is entered to ensure range checks are included as part of validation


Documentation Two types of documentation are produced: User guide: so that users can learn to use the system Technical documentation: so that the system can be maintained


Evaluation Does the system meet all user needs? Is it functioning correctly? Are any improvements needed?

authorStream Live Help