Software Development and the Software Life Cycle

A knowledge of life cycle software will makeĀ Software development that is structured, easy to communicate and easy to monitor.A knowledge of life cycle software will make software development structured, easy to communicate and easy to monitor. A waterfall model is shown by the picture below. It starts from Requirements specification, System analyst, Detailed design, Implementation and unit testing, Integration and system testing; Operation and maintenance.Software development can have the same parts as the life cycle software except in the final stages.


  • Requirements specification

Requirements specification refers to any service Which should be provided by the software and under the boss of what the sotfware is operating. Accurate needs are often difficult to determine because the field of computers is closely related to the complex social and organizational world of the world.

  • System Analysis

The process of systems analysis and design will determine the accurate functions required to meet the needs and hardware required to operationalize them. This may include sub systems not related to computers, along with a complete definition of human roles. Imagine an example of an aircraft system: there will be a number Computer monitoring and controlling aspects of the flight with multiple display devices, and interfacing with ground systems; The role of the pilot is also decisive.

  • Detailed design

Detailed design will be related to breaking the system or subsystem into Clearer definition modules. Subdivision or functional repetition will be important until a clear description can be fulfilled by modules which are the building blocks of the system. We will look at some techniques to illustrate the details of the program at this level.

  • Implementation and testing

Implementation and testing relates to the writing of code to generate a program that can be executed for modules (implementation) and experiments on the program to ensure the program works. This is usually related to bug fixes until the program runs correctly. This is the work area of the programmer.

  • Integration and testing

Integration and testing involves bringing the program into the subsystem, with various interfaces between programs, and so the subsystems into the system. Testing is required to ensure that the program runs correctly when they are combined, and the functionality of the system is correct. When testing is found error, redesign or re-encoding may be required.

When the software is complete it must be installed and the user must be trained. As when used in the target environment a new error may arise. Also by that time the need may change. If the software has entered this stage referred to as maintenance.