1.2.3 SOFTWARE DEVELOPMENT

A software development methodology that is based on a series of steps completed sequentially. It is suitable for small/medium projects with little risk. Uses TELOS

Simple,easy to manage,Easy to understand and everyone knows their responsibilities in different stages. Easy to see if a project is running on schedule.

No risk analysis . User doesn't see the product until the project is almost finished. Misunderstanding the requirements can lead to difficult fixes. Not flexible

An iterative development methodology where requirements do not need to be entirely clear at the beginning and uses prototypes. Suitable for small/medium projects with short time frames

Caters to user changing requirements. Highly useable finished products. Focuses only on core features so quicker to develop

Not suited for projects where code quality is important. Regular contact with clients must be maintained at all times. Poor quality documentation

A software development methodology that focuses on risk analysis. Suitable for large-scale projects with a high level of risk with big budgets

Risk analysis is at the heart of this model. Caters to changing user needs. Produces prototypes throughout

Nature of risk analysis is highly specialized and expensive skill. If risk analysis is done badly, the project suffers. Does not focus on code efficiency

A software development methodology that emphasizes programming and high-quality code. Suitable for small/medium projects where initial requirements are unclear. (Agile) apart from high usability

Emphasizes programming, leading to high-quality code. a very productive team. Regular user input
Also agile is flexible to user changing requirements

Requires a close-knit team and may not work well if the team is international. Clients must be able to commit working with the team at all times. May be costly.
Agile - poor documentation

Testing done where user does not see the code and only looks at if the expected outcome occurs with a specific input.

testing carried out by software development teams in which checks if all parts work. All of the possible routes through the program are tested. Checks overall efficiency and does dry runs

Very early testing carried out by development team

Later testing done by end-users which provide feedback.

1)User requirements are initially gathered and is used to develop an incomplete version of solution.
2)User looks at it and provides feedback
3)This feedback is used to make any changes and make new prototype
Repeat until finished product

Product built in a series of sprints. These are short time boxed periods where teams have focused goals to complete a set amount of work and is bite sized.

Requirements
Analysis
Design
Implementation
Testing
Deployment
Maintenance

1) Determining objectives and risks
2)Identify and resolve risk
3)Development and testing
4)Plan next iteration.