Business Analysis

C.
Essential Skills for Business
Analysis

LL
Zaran Tech
ch Puja
Te

Waterfall Methodology
an

 Waterfall model is an SDLC

approach that assumes the various
r

phases of a project can be

Za

completed sequentially – one phase

leads into the next phase.

Zaran Tech Puja

1
 “Waterfall” Approach to the SDLC

C.
LL
Zaran Tech
ch Puja
Te

Spiral Methodology
an

 Newer Adaptive Approach to the

SDLC
– Project cycles through
development activities over and
r

over until project is complete

– Prototype created by end of each
cycle
Za

– Focuses on mitigating risk

 Iteration – Work activities are
repeated
– Each iteration refines previous
result
– Approach assumes no one gets it
right the first time
– There are a series of mini
projects for each iteration
Zaran Tech Puja

2
Agile Methodology
 Group of software development methodologies

C.
based on iterative and incremental development,
where requirements and solutions evolve through
collaboration between self-organizing, cross-
functional teams.

LL
 It promotes adaptive planning, evolutionary
development and delivery, a time-boxed iterative
approach, and encourages rapid and flexible
response to change.
 It is a conceptual framework that promotes
foreseen interactions throughout the development
cycle. Examples Scrum, XP, etc

Zaran Tech
ch Puja
Te

Agile Scrum Model

r an
Za

Zaran Tech Puja

3
 Agile Scrum
Scrum is a process that teams can adopt quickly to plan and manage their work.
Each Scrum step has just enough detail to plan, design, build and test code,
while tracking team progress.
Scrum has three primary roles: Product Owner, Scrum Master, and team member.

C.
 The Product Owner communicates the vision of the product to the
development team. This includes representing the customer’s interests through
requirements and prioritization.
 The Scrum Master acts as a liaison between the Product Owner and the team.
 The team members do the project work. The team typically consists of
software engineers, architects, analysts and testers.

LL
The intent of Scrum is to build working components in small iterations, each
iteration lasting between two and four weeks. A typical Scrum lifecycle has
the following steps:
• Write the requirements (and store in the Backlog)
• Plan the release (which could span more than one 2-4 week Sprint)
• Plan the Sprint
• Conduct the Sprint
- Analysis
- Design
- Coding
- Testing
• Conduct Sprint retrospective
 ch
Daily stand-up meetings are held to track team progress and identify barriers.
Te
Extreme Programming (XP)
 Recent, lightweight, development approach to keep process
simple and efficient
an

 Describes system support needed and required system

functionality through informal user stories

 Has users describe acceptance tests to demonstrate defined

r

outcomes
Za

 Relies on continuous testing and integration, heavy user

involvement, programming done by small teams

Zaran Tech Puja

4
 Rapid Applications
Development (RAD)

C.
 Like prototyping, uses
iterative development
 Uses tools to speed up
development
– GUI

LL
– reusable code
– code generation
– programming, language
testing and debugging
 Requirements may be
frozen too early
 Basic standards often
overlooked

Zaran Tech
ch Puja
Te

Rational Unified Process

r an
Za

 Software Engineering Process (SDLC + Software Process Improvement)

 Developed by Rational Inc (Now IBM)
 Based on UML ( RUP is a guide for how to effectively use UML)
 Supports an Iterative and Incremental Approach
 Supported by Tools, which automate large parts of the
process
Zaran Tech Puja

5
 Components Of RUP
 Time Dimension

C.
– Inception
– Elaboration
– Construction
– Transition

LL
 Process Components
– Business Modeling
– Requirements Gathering
– Analysis & Design
– Implementation
– Test
– Deployment

Zaran Tech
ch Puja
Te

RUP Disciplines
an

The Rational Unified Process (RUP) is modeled in two dimensions. The horizontal axis of
Table represents time, and the vertical axis represents logical groupings of core activities.
r
Za

Zaran Tech Puja

6
 Advantages of RUP
 Iterative Approach
- allows changes in functional requirements also to be accommodated as they inevitably change
during system development due to external circumstances or clearer understanding of system
functionality as functionality develops.
 Requirements Management
- describes how to elicit, organize, and document required functionality and constraints; track and

C.
document tradeoffs and decisions; and easily capture and communicate the business
requirements.
 Component Based Architecture
- describes how to design a resilient architecture that is flexible, accommodates change, is intuitively
understandable, and promotes more effective software reuse.

LL
 Create visual models
- shows you how to visually model software to capture the structure and behavior of architectures and
components.
 Quality Management
-Quality assessment is built into the process, in all activities and reviewed with respect to the
requirements based on reliability, functionality, application performance and system
performance.
 Change Management & Control
- describes how to control, track and monitor changes to enable successful iterative development,
ch
how to establish secure workspaces for each developer and by controlling changes of all software
artifacts (e.g., models, code, documents, etc.).

Zaran Tech Puja

Te

RUP- Inception Phase

an

 Specifying Project Vision and Scope

 Initial Risk Assessment
 Any sample prototype
r

 Documentations- BRD, Use Case (Draft)

Za

Inception Phase Milestones

 Stakeholder concurrence
 Requirements understanding – Complete BRD
 Credibility of the cost/schedule estimates, priorities, risks, and
development process.
 Depth and breadth of prototype
 Actual versus planned expenditures.

Zaran Tech Puja

7
RUP- Elaboration Phase
 Revise Business Requirements and complete Functional
Requirement Document
 Complete Use Case Document
 Develop a sound foundation for architecture
 Understand system dependencies and complete Supplementary

C.
requirements
 Re-Analyze the problem domain -Revise risk list and business
case.
 Development plan for the overall project

LL
Milestones:
 Is the vision stable?
 Is the architecture stable?
 Are major risk elements have been addressed?
 Is the plan backed up with a credible basis
 Do all stakeholders agree on the current vision
 Is the actual resource expenditure versus planned expenditure
acceptable?

Zaran Tech
ch Puja
Te

RUP- Construction Phase Objectives

an

 Coding of software
 Parallel Run Activities
 Any integration of requirements
Releasing the “Beta” Version
r


Za

Milestone
 Is this product release stable and mature enough?
 Are all stakeholders ready for the transition?
 Are the actual resource expenditures versus
planned expenditures still acceptable?

Zaran Tech Puja

8
RUP- Transition Phase Objectives
 “Beta Testing”

C.
 Parallel operation
 Conversion of operational databases
 Training of users and maintainers

LL
 Roll-out

Milestones
 Is the product acceptable?
 Is the user satisfied
 Evaluation of whole project
 Project knowledge book

Zaran Tech
ch Puja
Te

RUP Process Component- 9 Core

an

Workflows
 Engineering Workflows
– Business Modeling
r

– Requirements Gathering
– Analysis & Design
Za

– Implementation
– Test
– Deployment
 Support Workflows
– Project workflow
– Change Management
– Environment

Zaran Tech Puja

9
Capability Maturity Model
 The Capability Maturity Model (CMM) for software
development was developed by the Software Engineering
Institute at Carnegie Mellon University.

C.
 CMM is an organizational maturity model. Maturity
involves continuous process improvement based on
evaluation of iterative execution, gathering results, and
analyzing metrics. As such, it has a very broad universe
of application.

LL
 The CMM is based on four principles:
– Evolution (process improvement) is possible but takes time.
– Process maturity has distinguishable stages. The five levels of the
CMM are indicators of process maturity and capability.
– Evolution implies that some things must be done before others.
Experience with CMM since 1987 has shown that organizations
grow in maturity and capability in predictable ways.
– Maturity will erode unless it is sustained. Lasting changes require
continued effort.
ch
Te

5 Levels of CMM
an

The five levels of the CMM, in order of developing

maturity, are as follows:
 Level 1 (Ad Hoc): Characterized by the development of
software that works, even though no one really
understands why. The team cannot reliably repeat past
successes.
r

 Level 2 (Repeatable): Characterized by requirements

management, project planning, project tracking, quality
Za

assurance, configuration management.

 Level 3 (Defined): Organization project focus and project
definition, training program, integrated software
management, software product engineering, inter group
coordination, peer reviews.
 Level 4 (Managed): Quantitative process management,
software quality management.
 Level 5 (Optimizing): Defect prevention, technology
change management, process change management.

10
ISO 9000-3 Software Development
Guidance Standard
This guidance standard is a guideline for the application of standards to
the development, supply, and maintenance of computer software. It
is not a development model like RUP or even a organization

C.
developmental model like CMM. Neither is it a certification process.

It is a guidance document that explains how ISO 9001 should be

interpreted within the software industry (see Figure 1.10). It was
introduced as ISO 9001 Software Quality Management.13 and
updated in 2002 as ISO 9000-3.

LL
Benefits of ISO 9000-3 compliance:

 Increases the likelihood of quality software products

 Gives you a competitive advantage over non-ISO 9000 certified
development vendors
 Assures customers of the end product’s quality
 Defines the phases, roles, and responsibilities of the software
development process


ch
Measures the efficiency of the development process
Gives structure to what is often a chaotic process
Te

Comparison of RUP, CMM, and

an

ISO 9000
r
Za

11
When are these Methodologies
used?

C.
LL
Zaran Tech
ch Puja
Te
Identify and Select the System for
Development
r an
Za

Zaran Tech Puja

12
Assignment
 Explain the purpose and various phases of the systems development life
cycle (SDLC)

C.
 Explain the differences between Waterfall SDLC and RUP SDLC

 Explain the differences between a model, a tool, a technique, and a

methodology

LL
 Describe the two overall approaches used to develop information systems:
the traditional method and the object-oriented method

 Summarize the activities associated with the planning phase in the SDLC

 Summarize the activities associated with the analysis phase in the SDLC

 Summarize the activities associated with the design phase in the SDLC


SDLC
Zaran Tech
ch
Summarize the activities associated with the development phase in the
Puja
Te
r an
Za

Zaran Tech Puja

13