SDLC_and_Design_Process_Lecture2 for Software Engi
altafkhanms2023
0 views
13 slides
Sep 29, 2025
Slide 1 of 13
1
2
3
4
5
6
7
8
9
10
11
12
13
About This Presentation
Software design and architecture class
Size: 39.04 KB
Language: en
Added: Sep 29, 2025
Slides: 13 pages
Slide Content
Software Development Life Cycle (SDLC) & Design Process Software Design and Architecture - Lecture 2
Agenda • What is SDLC? • Phases of SDLC • Importance of SDLC • Software Design Process • Relationship between SDLC and Design • Summary & Key Takeaways
What is SDLC? • SDLC stands for Software Development Life Cycle. • It is a structured process for developing software. • Ensures quality, reliability, and cost-effectiveness. • Involves planning, designing, building, testing, and deploying software.
Phases of SDLC (Overview) 1. Requirement Analysis 2. System Design 3. Implementation (Coding) 4. Testing 5. Deployment 6. Maintenance
Requirement Analysis • Gather user requirements. • Identify functional and non-functional needs. • Involves stakeholders, users, and analysts. • Output: Software Requirement Specification (SRS).
System Design • Defines system architecture and detailed design. • Translates requirements into a blueprint. • Includes data models, UI designs, and architecture diagrams. • Output: Design Documents.
Implementation (Coding) • Developers write code based on design documents. • Programming languages and tools are chosen. • Code is written, compiled, and documented. • Output: Source Code.
Testing • Ensures software works as intended. • Types: Unit Testing, Integration Testing, System Testing, User Acceptance Testing. • Identifies and fixes bugs. • Output: Tested Software.
Deployment & Maintenance Deployment: • Software is released to users. • Training and documentation provided. Maintenance: • Fixing bugs after release. • Updating software with new features. • Ensuring long-term reliability.
Software Design Process • High-level Design (Architecture): Overall structure. • Low-level Design: Detailed class, module, and function design. • Emphasis on Modularity, Reusability, and Maintainability. • Bridges the gap between requirements and coding.