Software Engineering: Design Phase in SDLC, Summaries of Software Engineering

A concise overview of the design phase within the software development life cycle (sdlc). It outlines the essential aspects of the design phase, including its objectives, the roles and responsibilities of various team members, and the exit criteria. The document emphasizes the transformation of requirements into specifications, risk planning and assessment, and the importance of detailed documentation. It also highlights the involvement of customers, business analysts, project managers, technical architects, developers, and testers in the design process, making it a useful resource for understanding the structured approach to software design and development.

Typology: Summaries

2023/2024

Available from 12/31/2025

alna-albert
alna-albert 🇮🇳

7 documents

1 / 2

Toggle sidebar

This page cannot be seen from the preview

Don't miss anything!

bg1
SOFTWARE ENGINEERING
DESIGN PHASE IN SDLC
* Essential phase of SDLC
* In design phase, one or more design is created to achieve project result
* Design phase products include flow charts ,diagrams, sketches etc.
Once a design is selected, changes cannot be made
* This phase is followed by development phase
OBJECTIVE/GOALS OF SDLC
* Transformation of requirements into specialization - primary purpose
* Planning of risk
*Assessment of risk
* Approval for proggessing
During Documentation Development, The development team should -
* Provide detailed and easy to understand document with no unnecessary
information
* Develop an organized document repository
ROLES & RESPONSIBILITIES FOR DESIGN PHASE
* Customer - sponsors project
- reviews strategy
* Business Analyst - provides requirements
pf2

Partial preview of the text

Download Software Engineering: Design Phase in SDLC and more Summaries Software Engineering in PDF only on Docsity!

SOFTWARE ENGINEERING

DESIGN PHASE IN SDLC

  • Essential phase of SDLC
  • In design phase, one or more design is created to achieve project result
  • Design phase products include flow charts ,diagrams, sketches etc. Once a design is selected, changes cannot be made
  • This phase is followed by development phase OBJECTIVE/GOALS OF SDLC
  • Transformation of requirements into specialization - primary purpose
  • Planning of risk *Assessment of risk
  • Approval for proggessing During Documentation Development, The development team should -
  • Provide detailed and easy to understand document with no unnecessary information
  • Develop an organized document repository

ROLES & RESPONSIBILITIES FOR DESIGN PHASE

  • Customer - sponsors project
  • reviews strategy
  • Business Analyst - provides requirements
  • reviews software design
  • Project Manager - Finalize data conversion strategy
  • test strategy
  • reviews software design
  • Technical - Architect, Tech-Designer, Design Team
  • design system architecture, software components etc DEVELOPER/CONSTRUCTION TEAM
  • Assists in finalizing data conversion
  • Review Architecture and software components TESTING TEAM TESTER
  • Assists with identifying and finalizing testing strategy
  • Reviews architecture and software components

EXIT CRITERIA FOR DESIGN PHASE

  • Completion & reviewal of specialization.
  • Master Test plan should be completed, reviewed & placed in baseline.
  • Work on documents has begun and is in progress