case study

Topics: Software development process, Software engineering, Software development Pages: 18 (4912 words) Published: February 9, 2014
Software development process
A software development process, also known as a software development life-cycle (SDLC), is a structure imposed on the development of a software product. Similar terms include software life cycle and software process. It is often considered a subset of systems development life cycle. There are several models for such processes, each describing approaches to a variety of tasks or activities that take place during the process. Some people consider a life-cycle model a more general term and a software development process a more specific term. For example, there are many specific software development processes that 'fit' the spiral life-cycle model. ISO/IEC 12207 is an international standard for software life-cycle processes. It aims to be the standard that defines all the tasks required for developing and maintaining software. Software development models[edit]

Several models exist to streamline the development process. Each one has its pros and cons, and it is up to the development team to adopt the most appropriate one for the project. Sometimes a combination of the models may be more suitable. Waterfall model[edit]

Main article: Waterfall model

The activities of the software development process represented in the waterfall model. There are several other models to represent this process. The waterfall model shows a process, where developers have to follow these phases in order: 1. Requirements specification (Requirements analysis)

2. Software design
3. Implementation and Integration
4. Testing (or Validation)
5. Deployment (or Installation)
6. Maintenance
In a strict Waterfall model, after each phase is finished, it proceeds to the next one. Reviews may occur before moving to the next phase which allows for the possibility of changes (which may involve a formal change control process). Reviews may also be employed to ensure that the phase is indeed complete; the phase-completion criteria are often referred to as a "gate" that the project must pass through to move to the next phase. Waterfall discourages revisiting and revising any prior phase once it's complete. This "inflexibility" in a pure Waterfall model has been a source of criticism by supporters of other more "flexible" models. The Waterfall model is also commonly taught with the mnemonic A Dance in the Dark Every Monday, representing Analysis, Design, Implementation, Testing, Documentation and Execution, and Maintenance.[citation needed] Spiral model[edit]

Main article: Spiral model

Spiral model (Boehm, 1988)
The key characteristic of a Spiral model is risk management at regular stages in the development cycle. In 1988, Barry Boehm published a formal software system development "spiral model," which combines some key aspect of the waterfall model and rapid prototyping methodologies, but provided emphasis in a key area many felt had been neglected by other methodologies: deliberate iterative risk analysis, particularly suited to large-scale complex systems. The Spiral is visualized as a process passing through some number of iterations, with the four quadrant diagram representative of the following activities: 1. Formulate plans to: identify software targets, implement the program, clarify the project development restrictions 2. Risk analysis: an analytical assessment of selected programs, to consider how to identify and eliminate risk 3. Implementation of the project: the implementation of software development and verification Risk-driven spiral model, emphasizing the conditions of options and constraints in order to support software reuse, software quality can help as a special goal of integration into the product development. However, the spiral model has some restrictive conditions, as follows: 1. The spiral model emphasizes risk analysis, and thus requires customers to accept this analysis and act on it. This requires both trust in the developer as well as the willingness to spend more to fix the issues, which is...

References: Object-oriented programming
Comparison of Methodology Approaches (Post, & Anderson 2006)[14]
Continue Reading

Please join StudyMode to read the full document

You May Also Find These Documents Helpful

  • case study Essay
  • CASE STUDY Essay
  • Case Study Essay
  • Case Study Research Paper
  • case study Essay
  • Case Study Essay
  • case study Essay
  • CASE STUDIES Essay

Become a StudyMode Member

Sign Up - It's Free
Mackenzie Foy | Watch Link | Eps13 Larva Island