Spiral Model

The spiral model was defined in 1988 by Barry Boehm. It is often used for large projects. Following are the steps for spiral model:

- Define requirements in details
- Create preliminary design
- Create prototype from design
- Evaluate prototype
- Define requirements for next prototype
- Create design for second prototype
- Create second prototype
- And so on...

One can define spiral model in four phases as below
1. Determine objectives
2. Identify and resolve issues/risks
3. Development and test
4. Plan next iteration

Waterfall Model

Waterfall model is sequential development process. This has predefined phases like following:

1. Requirement analysis
2. Architecture/Design
3. Development/Implementation
4. Integration
5. Testing/Validation
6. Deployment
7. Maintenance

The waterfall model moves from one phase to another in sequential manner. The output of one phase is used in next phase. The completion of one phase can be considered as milestones. There are different teams to work on different phases of the waterfall model.

This model is being used by large projects. For smaller projects there are different methodologies being used as spiral model, iterative model, and agile methodology.

List of software development methodologies

Following are few methodologies / philosophies for software development:

1. Waterfall Model
2. Spiral Model
3. Iterative Model
4. Agile Software Development
5. Agile Unified Process (AUP)
6. Unified Process / Rational Unified Process (RUP)
7. Test Driven Development (TDD)
8. Microsoft Solution Framework (MSF)
9. Joint Application Development (JAD)

Threat modeling tool

Microsoft’s Thread Modeling Tool can be used during design phase of application. It allows architects/designers to identify security related issues during design phase. More details can be found at
http://msdn.microsoft.com/en-us/security/dd206731.aspx

Download URL: http://download.microsoft.com/download/E/5/3/E5318D25-7AEF-4A66-A147-81BBA727F2C1/SDLTM.msi