Stage 5 deployment when the program is finalized and

  • No School
  • AA 1
  • Abhicpj
  • 10

This preview shows page 2 - 6 out of 10 pages.

Stage 5. Deployment
Image of page 2
When the program is finalized and has no critical issues – it is time to launch it for the end users. After the new program version release, the tech support team joins. This department provides user feedback; consult and support users during the time of exploitation. Moreover, the update of selected components is included in this phase, to make sure, that the software is up-to-date and is invulnerable to a security breach. SDLC MODELS Waterfall SDLC Model Waterfall – is a cascade SDLC model, in which development process looks like the flow, moving step by step through the phases of analysis, projecting, realization, testing, implementation, and support. This SDLC model includes gradual execution of every stage completely. This process is strictly documented and predefined with features expected to every phase of this software development life cycle model.
Image of page 3
ADVANTAGES DISADVANTAGES Simple to use and understand The software is ready only after the last stage is over Management simplicity thanks to its rigidity: every phase has a defined result and process review High risks and uncertainty Development stages go one by one Not the best choice for complex and object-oriented projects Perfect for the small or mid-sized projects where requirements are clear and not equivocal Inappropriate for the long-term projects Easy to determine the key points in the development cycle The progress of the stage is hard to measure while it is still in the development Easy to classify and prioritize tasks Integration is done at the very end, which does not give the option of identifying the problem in advance Use cases for the Waterfall SDLC model: The requirements are precisely documented Product definition is stable The technologies stack is predefined which makes it not dynamic No ambiguous requirements The project is short Iterative SDLC Model: This model does not need the full list of requirements before the project starts. The development process may start with the requirements to the functional part, which can be expanded later. The process is repetitive, allowing to make new versions of the product for every cycle. Every iteration (which last from two to six weeks) includes the development of a separate component of the system, and after that, this component is added to the functional developed earlier.
Image of page 4
Speaking with math terminology, the iterative model is a realization of the sequential approximation method; that means a gradual closeness to the planned final product shape.
Image of page 5
Image of page 6

You've reached the end of your free preview.

Want to read all 10 pages?

  • Fall '19
  • Software development process, Iterative and incremental development

  • Left Quote Icon

    Student Picture

  • Left Quote Icon

    Student Picture

  • Left Quote Icon

    Student Picture