Summary of "SDLC Phases in Business Analyst | Waterfall | V-Shaped | Prototype Model Tutorials"
Summary of “SDLC Phases in Business Analyst | Waterfall | V-Shaped | Prototype Model Tutorials”
This video provides a comprehensive overview of the Software Development Life Cycle (SDLC) phases from a Business Analyst (BA) perspective. It explains the roles, activities, and involvement of a BA across various project phases and SDLC models such as Waterfall, V-Shaped, Prototype, Iterative, and others.
Main Ideas and Concepts
1. Understanding the IT Organizational Structure and Project Initiation
- Key stakeholders in client organizations include Developers, QA, Operations, Subject Matter Experts (SMEs), Project Managers, Delivery Managers, and Account Managers.
- Vendor onboarding and competitive bidding processes are important.
- The Statement of Work (SOW) defines features and scope.
- Project planning begins after vendor selection and team formation.
2. Phases of a Typical Project and BA Involvement
Phase 1: Enterprise Analysis (Project Identification & Business Case Creation)
- Identify potential projects based on organizational needs.
- Create a business case justifying the project investment (e.g., benefits, costs).
- Budget allocation and project approval by senior management.
- BA’s role: Help identify projects, create business cases, and define high-level scope.
Phase 2: Project Planning and Requirements Gathering
- Project managers prepare detailed project plans with timelines, tasks, and dependencies.
- BA provides input on requirement-related activities and plans requirements elicitation.
- Requirements elicitation involves detailed understanding of features (functional and non-functional).
- Documentation of requirements using frameworks like Use Cases, User Stories, ER diagrams.
- Deliverable: Business Requirements Document (BRD).
- BA’s role: Lead elicitation, analysis, documentation, and obtain sign-off on BRD.
Phase 3: Design
- Technical architects design system architecture (e.g., 3-tier, MVC).
- BA supports by clarifying requirements for architects.
- BA is not involved in design creation but acts as a liaison.
Phase 4: Development
- Programmers write code based on design.
- BA clarifies any functional questions from developers.
- BA’s role: Supportive, ensuring requirements are understood.
Phase 5: Testing
- QA team performs unit, integration, and system testing.
- Testing ensures all requirements (functional and non-functional) are met.
- Customer’s QA team conducts acceptance testing to validate deliverables.
- BA coordinates testing efforts, analyzes defects, and communicates with developers for fixes.
- Defects are tracked, fixed, retested, and approved before release.
Deployment and Maintenance
- Operations team deploys the system to production (Go-Live).
- Data migration, user creation, and operational setup handled by operations.
- Post-deployment support and maintenance begins.
3. Types of Requirements
- Functional Requirements: What the system should do (e.g., check balance, transfer funds).
- Non-Functional Requirements: Performance, availability, security, operational needs.
- BA must capture both and clearly differentiate them in documentation.
4. Role of Business Analyst
- Involved mainly in:
- Enterprise analysis and business case creation.
- Requirements elicitation, analysis, and documentation.
- Supporting testing and defect management.
- Acts as a bridge between business users and technical teams.
- Responsible for asking detailed questions that business users may not articulate.
- Not responsible for technical design or coding.
5. SDLC Models and Their Applicability
Waterfall Model
- Linear, sequential phases.
- Best when requirements are clear and stable.
- Simple and straightforward.
- Output of one phase is input to the next.
V-Shaped Model
- Enhanced version of Waterfall with more rigorous and elaborate testing.
- Used for highly reliable systems where defects are unacceptable (e.g., aircraft systems).
- Testing phases correspond to development phases (unit, integration, system, acceptance testing).
Prototyping Model
- Used when customers cannot visualize the final product.
- Involves creating mockups or screens early to gain clarity and agreement.
- Types:
- Throwaway Prototyping: Prototype discarded after requirements are finalized.
- Evolutionary Prototyping: Prototype evolves into the final product.
- Helps reduce misunderstandings and rework.
Iterative Model
- Large projects are broken into smaller parts or phases.
- Each part is developed and delivered incrementally.
- Allows faster delivery of usable components and adapts to changing business needs.
Other Models Mentioned
- Spiral Model: For high-risk projects.
- Product Incremental Model: For implementing existing products with customization.
- Agile/Scrum: Popular iterative and incremental approach for flexibility.
6. Key Points for Business Analysts Regarding SDLC Models
- BAs do not decide which SDLC model to use; it is the project manager’s responsibility.
- Understanding models helps BAs relate their tasks to project progress.
- Different projects require different models based on size, risk, clarity of requirements, and reliability needs.
Methodology / Instructions for Business Analysts in SDLC
Phase 1: Enterprise Analysis
- Identify potential projects.
- Collaborate with stakeholders to create a business case.
- Present benefits and justify budget allocation.
Phase 2: Requirements Planning and Elicitation
- Participate in project planning with PMs.
- Conduct detailed requirement gathering sessions.
- Use techniques like interviews, workshops, use cases, and user stories.
- Document requirements clearly (functional and non-functional).
- Obtain sign-off on BRD.
Phase 3 & 4: Support Design and Development
- Clarify requirements to architects and developers.
- Be available for queries related to functionality.
Phase 5: Testing Coordination
- Coordinate with QA teams.
- Analyze defects and communicate with development.
- Ensure all requirements are tested and met.
- Support customer acceptance testing.
Deployment and Maintenance
- Coordinate with operations for smooth go-live.
- Assist in data migration and user setup if needed.
- Support post-deployment issue resolution.
When Using Prototyping
- Create quick mockups or wireframes.
- Use tools ranging from paper sketches to PowerPoint or specialized software.
- Use prototypes to gain early customer feedback and reduce misunderstandings.
- Decide on throwaway vs evolutionary prototyping based on project needs.
Speakers / Sources Featured
- Primary Speaker: Unnamed instructor or trainer explaining SDLC phases and BA role.
- Implied Sources:
- Project Managers
- Technical Architects
- Developers and QA teams
- Business users / Subject Matter Experts
This summary captures the core teachings about SDLC phases from a Business Analyst’s viewpoint, the role and responsibilities of a BA in each phase, the differentiation of requirements, and an overview of various SDLC models with their contexts and use cases.
Category
Educational
