As in any other engineering discipline, software engineering also has some structured models for software development. This document will provide you with a generic overview about different software development methodologies adopted by contemporary software firms. Read on to know more about the Software Development Life Cycle (SDLC) in detail.

Initial Project Information Discovery Process

The program development cycle begins with gathering clear and precise requirements. A listing of input and output requirements will be helpful especially when sample data is included. The client names of the key players should be noted as they will be included in the program development cycle.

Rapid Application Development (RAD) Model

1.  Analyze the Requirements

• Review application requirements
• Meet with end-users and system analysts
• Identify the components of the application

Requirements must be analyzed in order to design the process in pseudo code. Multiple meetings with end-users and system analysts should be conducted to insure all requirements have been discussed. The basis for the user interface look and feel should be reviewed.

• Group similar activities into modules within the components
• Identify solution pseudo code
• Design the graphic user interface

Develop the logical model the displays the steps needed to solve each problem. Flow charts, diagrams and storyboards can be helpful in the initial design of the pseudo code. The user interface can now be roughly designed using the requirements and end-user input given. The user interface can be designed using a sketch on paper or UI design application such as Microsoft Visio.

• Test the pseudo code process with sample data
• Confirm with end-users that solution meets requirements

The development team steps through the pseudo code processes with sample data validating proper results. The end-users should now confirm the functionality is proper and includes all documented requirements.

• Convert pseudo code into a programming language
• Compile the solution including necessary install process

The development team now converts the pseudo code with any needed changes into a programming language. They also create the UI using the development tools chosen to complete the project. Documentation and physical comments in code at this level really helps with future development. The application is tested within the development environment and updated as needed. Installers and implementation plans should be finalized before testing in the production environment.

• Test program in end-user environment
• Correct errors as needed

Test documents will help test every function of the solution. These test documents should be part of the overall test plan. Tests will include integration testing, boundary limits, validation and resulting output of data. Document issues with as much detail as possible and restart the requirements cycle as needed to limit ongoing issues.

• Review program code and process
• Review and revise existing internal documentation
• Complete standardized user documentation

Documentation is a very important step for the end-user. These documents will be used to help answer future questions and training of new users. Client should now sign off on successful completion of testing and implementation. All solution files should be archived for support, review and future change requests.

Project Maintenance Process

Once the development cycle is complete and the client is satisfied maintenance begins. This area consists of technical support, training and change requests. Some change requests can be due to lack of testing others should be considered new projects starting the development cycle over completely.

Works Cited

New Product Development Methodologies. (n.d.). Retrieved from HyperThot:

http://www.hyperthot.com/pm_npdm.htm

Software Development Life Cycle (SDLC). (n.d.). Retrieved from Stylus Inc:

http://www.stylusinc.com/Common/Concerns/SoftwareDevtPhilosophy.php

Systems Development Life Cycle. (n.d.). Retrieved from FFIEC:

http://www.ffiec.gov/ffiecinfobase/booklets/d_a/08.html