SDLC Overview.pdf - SDLC Overview SDLC OVERVIEW https\/www.tutorialspoint.com\/sdlc\/sdlc_overview.htm Copyright \u00a9 tutorialspoint.com Advertisements

SDLC Overview.pdf - SDLC Overview SDLC OVERVIEW...

This preview shows page 1 - 3 out of 30 pages.

SDLC Overview [2/25/2019 4:19:13 AM] Copyright © tutorialspoint.com SDLC - OVERVIEW Advertisements Software Development Life Cycle is a process used by the software industry to design, develop and test high quality softwares. The SDLC aims to produce a high-quality software that meets or exceeds customer expectations, reaches completion within times and cost estimates. SDLC is the acronym of Software Development Life Cycle. It is also called as Software Development Process. SDLC is a framework defining tasks performed at each step in the software development process. 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. What is SDLC? SDLC is a process followed for a software project, within a software organization. It consists of a detailed plan describing how to develop, maintain, replace and alter or enhance specific software. The life cycle defines a methodology for improving the quality of software and the overall development process. The following figure is a graphical representation of the various stages of a typical SDLC. SDLC
Image of page 1
SDLC Overview [2/25/2019 4:19:13 AM] A typical Software Development Life Cycle consists of the following stages Stage 1: Planning and Requirement Analysis Requirement analysis is the most important and fundamental stage in SDLC. It is performed by the senior members of the team with inputs from the customer, the sales department, market surveys and domain experts in the industry. This information is then used to plan the basic project approach and to conduct product feasibility study in the economical, operational and technical areas. Planning for the quality assurance requirements and identification of the risks associated with the project is also done in the planning stage. The outcome of the technical feasibility study is to define the various technical approaches that can be followed to implement the project successfully with minimum risks. Stage 2: Defining Requirements Once the requirement analysis is done the next step is to clearly define and document the product requirements and get them approved from the customer or the market analysts. This is done through an SRS document which consists of all the product requirements to be designed and developed during the project life cycle. Stage 3: Designing the Product Architecture SRS is the reference for product architects to come out with the best architecture for the product to be developed. Based on the requirements specified in SRS, usually more than one design approach for the product architecture is proposed and documented in a DDS - Design Document Specification.
Image of page 2
Image of page 3

You've reached the end of your free preview.

Want to read all 30 pages?

  • Spring '19
  • Salma
  • Systems Development Life Cycle, Software development process, Iterative and incremental development

  • Left Quote Icon

    Student Picture

  • Left Quote Icon

    Student Picture

  • Left Quote Icon

    Student Picture