Session 2 - SDLC Part 1

BA Foundation
Software Development Life Cycle

Part 1
4/20/2022 09e-BM/DT/FSOFT - ©FPT SOFTWARE – Fresher Academy - Internal Use 1

Lesson Objectives
 Objectives
 Understanding different phases in the SDLC
 Understanding basics knowledge about project development, project scope and BA’s
activities in a project
 Outline
1. What is Software Development Life Cycle (SDLC)
1. Six phases in SDLC
2. SDLC model:
1. Waterfall model
3. Project management and project scope
1. Project definition and project management activities
2. Work Breakdown Structure (WBS)
3. Project roles
4. BA activities and responsibilities

Section 1
Software Development Life Cycle

Content #1. Agenda
 What is SDLC?
 Stages in SDLC

Software Development Life Cycle (SDLC)
 Software Development Life Cycle (SDLC) is a process which defines the

various stages and their sequence that are involved in the development
and implementation of an IT system.
 Two main approaches of SDLC:
 Linear/Predictive approach: Steps are carried out in sequence and are

completed before moving on
 Evolutionary/Adaptive approach: the solution to be delivered emerges during

iterative periods of software development based upon the use of prototyping
and multi-disciplinary teams.

Software Development Life Cycle (SDLC)
Rational Unified Process

- RUP

Phases in RUP
Each phase is concluded with a well-defined milestone—a point in time at which

certain critical decisions must be made, and therefore key goals must have been
achieved

Phases in RUP
1. Inception phase
 Establish the business case for the system and delimit the project scope.
 Identifying all use cases and describing a few significant ones.
 Includes success criteria, risk assessment, and estimate of the resources
needed, and a phase plan showing dates of major milestones
2. Elaboration phase
 Analyze the problem domain, establish a sound architectural foundation,
develop the project plan, and eliminate the highest risk elements of the project
3. Construction phase
 all remaining components and application features are developed and
integrated into the product, and all features are thoroughly tested
4. Transition phase
 Transition the software product to the user community
 Go-Live, Release to Production

Iterations in RUP
Each phase in the Rational Unified Process can be further broken down into
iterations

Process Workflow (Disciplines) in RUP
The core process workflows are divided into six core “engineering” workflows:
1. Business modeling workflow
2. Requirements workflow
3. Analysis & Design workflow
4. Implementation workflow
5. Test workflow
6. Deployment workflow
And three core “supporting” workflows:

1. Project Management workflow
2. Configuration and Change Management workflow
3. Environment workflow

 Business Modeling
 Build business case, business use case
 Requirement
 Elicit relevant information from the customer to develop a product as
per their expectation.
 Describe what the system should do
 Output: Requirement document

 Analysis & Design

 The requirement elicited in requirement document is used as an
input and software architecture that is used for implementing
system development is derived.
 Show how the system will be realized in the implementation phase
 Output: Software architecture and design document

 Implementation or Coding
 Based on the design document, the developer starts implementation/coding. The Software design
is translated into source code. Components of the software are implemented in this phase.
 Output: the software itself / source code, unit test
 Testing
 Testing starts once the coding is completed and the product is released for testing. In this phase,
the developed software is tested thoroughly and any defects found are assigned to developers to
get them fixed.
 Re-testing, regression testing is done until the software is as per the customer’s expectation.
Testers refer to requirement document to make sure that the software meets with the customer’s
standard.
 Output: Test cases, Test report

 Deployment
 Once the product is tested, it is deployed in the production
environment or first UAT (User Acceptance testing) is done
depending on the customer expectation.
 In the case of UAT, a replica of the production environment is

created and the customer along with the developers does the
testing. If the customer finds the application as expected, customer
can sign-off for the product to go live.
 Output: User manual, Environment specifications

 Project Management
 balancing competing objectives, managing risk, and overcoming constraints to deliver,
successfully, a product in which meets the needs of both customers (the payers of bills) and the
users.
 Configuration & Change Management

 control the numerous artifacts produced by the many people who work on a common project
 Environment
 provide the software development organization with the software development environment—both
processes and tools—that are needed to support the development team
 Maintenance
 After the deployment of a product on the production environment, maintenance of the product
means to make sure that the application is up and running. In case user encounter defects, the
issue is noted to be fixed and deployed. Possible enhancement of the product can also be found
in this phase.
 Output: User manual, List of production tickets, List of new features

Section 2
SDLC MODELS

Software Development Life Cycle Models
 Waterfall Model (Predictive Approach)

 Waterfall model is the very first model that is used in SDLC. It is also
known as the linear sequential model.
 In this model, the outcome of one phase is the input for the next
phase. Development of the next phase starts only when the
previous phase is complete.


 Advantages of the Waterfall Model:

 Good control of the project.
 Simple and easy to understand
 Deliverables of each phase are well defined and sign-off before the
next stage, which would ensure a high-quality system
 Process and results are well documented.

 Disadvantages of Waterfall model

 Time-consuming
 Does not adapt well to change.
 This model expects the requirement to be clear in the requirement
gathering and analysis phase. Any change in the later stages would
lead to higher cost as the changes would be required in all the phases.
 It is very difficult to go back and change something that was not well-
thought out in the previous stages.
 No working software is produced until late of project.
 Integration is done as a "big-bang”, at the very end, which lead to
technological/business bottleneck/risk.
 High amounts of risk and uncertainty.

Waterfall to Iteration
21
 Iteration model
 Cost of change is lesser, but it still not very suitable for changing
requirements.
 Some functionality can be developed early but still not be really
working product and not periodically.
 Management is more complex, need more attention.

Adaptive
approach

Section 3
PROJECT MANAGEMENT AND PROJECT

SCOPE
Project management and project scope
 Project definition - PMI
“A temporary endeavor undertaken to create a unique product, service or result.”
 A project is temporary in that it has a defined beginning and end in time, and therefore defined
scope and resources.
 And a project is unique in that it is not a routine operation, but a specific set of operations
designed to accomplish a single goal.
 Project management
“The application of knowledge, skills, tools, and techniques to project activities to meet
the project requirements.”

 Project scope:
“All the work that needs to be performed to deliver a product, service, or result with the specified
features and functions.”
 Project scope management
Includes processes involved in defining and controlling what is or is not included in a project
 Project scope management process:
 Plan scope management

 Collect requirement
 Define scope
 Create Work breakdown structure (WBS)
 Validate scope
 Control scope

Scope Creep
The uncontrolled expansion to a product or project scope

without adjustments to time, cost, and

Work breakdown structure (WBS)
 A WBS is a deliverable-oriented grouping of the work involved in a

project that defines the total scope of the project
 The WBS consists of project deliverables which have been

decomposed into smaller pieces
 WBS is a valuable input in the estimation process. The team will

base on the WBS to provide the estimation for the project. Which
then can be used to communicate with customer


 The project teams and roles

 Project Manager (PM)
 Developers (Dev)
 Testers
 Quality assurance (QA)
 Business Analyst (BA)
 The project manager (PM) and business analyst (BA) serve in critical leadership
roles on programs and projects.
 Partnership and effective collaboration between PM and BA will ensure a higher
chance of success for the project.
 Challenges
 Overlap of responsibilities
 Inconsistent definitions
 Understanding the work performed by BA and the importance of business analysis
work in the project will help to improve the collaborations between BA and PM.

 BA’s activities and responsibilities during the project life cycle
 BAs would typically be involved in the feasibility study, requirement and

analysis stages of the project.
 They would also probably assist in the user acceptance that forms part
of the testing stage and help the business users during implementation.
 During design and development, BAs would be available to answer

queries about the business and solution requirements raised by the
development team (developers and testers)
References
 A Guide to the Project Management Body of Knowledge
(PMBOK® Guide) – Fifth Edition
 A Guide to the Business Analysis Body of Knowledge – V3
 Business Analysis BCS - Third editions

Thank you

Session 2 - SDLC Part 1

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Session 2 - SDLC Part 1

Uploaded by

Copyright:

Available Formats

BA Foundation

Software Development Life Cycle

4/20/2022 09e-BM/DT/FSOFT - ©FPT SOFTWARE – Fresher Academy - Internal Use 1

4/20/2022 09e-BM/DT/FSOFT - ©FPT SOFTWARE – Fresher Academy - Internal Use 2

4/20/2022 09e-BM/DT/FSOFT - ©FPT SOFTWARE – Fresher Academy - Internal Use 3

4/20/2022 09e-BM/DT/FSOFT - ©FPT SOFTWARE – Fresher Academy - Internal Use 4

 Software Development Life Cycle (SDLC) is a process which defines the

 Two main approaches of SDLC:

 Linear/Predictive approach: Steps are carried out in sequence and are

 Evolutionary/Adaptive approach: the solution to be delivered emerges during

4/20/2022 09e-BM/DT/FSOFT - ©FPT SOFTWARE – Fresher Academy - Internal Use 5

Rational Unified Process

4/20/2022 09e-BM/DT/FSOFT - ©FPT SOFTWARE – Fresher Academy - Internal Use 6

Each phase is concluded with a well-defined milestone—a point in time at which

4/20/2022 09e-BM/DT/FSOFT - ©FPT SOFTWARE – Fresher Academy - Internal Use 7

4/20/2022 09e-BM/DT/FSOFT - ©FPT SOFTWARE – Fresher Academy - Internal Use 8

4/20/2022 09e-BM/DT/FSOFT - ©FPT SOFTWARE – Fresher Academy - Internal Use 9

And three core “supporting” workflows:

4/20/2022 09e-BM/DT/FSOFT - ©FPT SOFTWARE – Fresher Academy - Internal Use 10

 Describe what the system should do

 Output: Requirement document

4/20/2022 09e-BM/DT/FSOFT - ©FPT SOFTWARE – Fresher Academy - Internal Use 11

 Analysis & Design

 Show how the system will be realized in the implementation phase

 Output: Software architecture and design document

4/20/2022 09e-BM/DT/FSOFT - ©FPT SOFTWARE – Fresher Academy - Internal Use 12

 Output: the software itself / source code, unit test

 Output: Test cases, Test report

4/20/2022 09e-BM/DT/FSOFT - ©FPT SOFTWARE – Fresher Academy - Internal Use 13

 In the case of UAT, a replica of the production environment is

 Output: User manual, Environment specifications

 Configuration & Change Management

4/20/2022 09e-BM/DT/FSOFT - ©FPT SOFTWARE – Fresher Academy - Internal Use 15

4/20/2022 09e-BM/DT/FSOFT - ©FPT SOFTWARE – Fresher Academy - Internal Use 16

 Waterfall Model (Predictive Approach)

4/20/2022 09e-BM/DT/FSOFT - ©FPT SOFTWARE – Fresher Academy - Internal Use 17

4/20/2022 09e-BM/DT/FSOFT - ©FPT SOFTWARE – Fresher Academy - Internal Use 18

 Advantages of the Waterfall Model:

4/20/2022 09e-BM/DT/FSOFT - ©FPT SOFTWARE – Fresher Academy - Internal Use 19

 Disadvantages of Waterfall model

4/20/2022 09e-BM/DT/FSOFT - ©FPT SOFTWARE – Fresher Academy - Internal Use 20

4/20/2022 09e-BM/DT/FSOFT - ©FPT SOFTWARE – Fresher Academy - Internal Use 22

4/20/2022 09e-BM/DT/FSOFT - ©FPT SOFTWARE – Fresher Academy - Internal Use 23

PROJECT MANAGEMENT AND PROJECT

 Project definition - PMI

“A temporary endeavor undertaken to create a unique product, service or result.”

4/20/2022 09e-BM/DT/FSOFT - ©FPT SOFTWARE – Fresher Academy - Internal Use 25

 Project scope management

 Project scope management process:

 Plan scope management

4/20/2022 09e-BM/DT/FSOFT - ©FPT SOFTWARE – Fresher Academy - Internal Use 26

The uncontrolled expansion to a product or project scope

4/20/2022 09e-BM/DT/FSOFT - ©FPT SOFTWARE – Fresher Academy - Internal Use 27

Work breakdown structure (WBS)

 A WBS is a deliverable-oriented grouping of the work involved in a

 The WBS consists of project deliverables which have been

 WBS is a valuable input in the estimation process. The team will

4/20/2022 09e-BM/DT/FSOFT - ©FPT SOFTWARE – Fresher Academy - Internal Use 28

4/20/2022 09e-BM/DT/FSOFT - ©FPT SOFTWARE – Fresher Academy - Internal Use 29

 The project teams and roles

4/20/2022 09e-BM/DT/FSOFT - ©FPT SOFTWARE – Fresher Academy - Internal Use 30

 BA’s activities and responsibilities during the project life cycle

 BAs would typically be involved in the feasibility study, requirement and