OOAD Lecture 4

Object Oriented Analysis
and Design
DEPARTMENT OF INFORMATION TECHNOLOGY
GOVT. GORDON COLLEGE RAWALPINDI
Fall 2019 Semester

BS Course: IT-325 OOA/D
Course Instructor: Mubashra Rabbani
Lecture 4
INCEPTION
Inception Phase
 Inception in one sentence:

Envision the product scope, vision, and business case.
 The main problem solved in one sentence:

Do the stakeholders have basic agreement on the vision of the
project, and is it worth investing in serious investigation?
Inception Phase
 To describe the problem and initial requirements
 To develop and justify the business case for the system
 To determine the scope and objective of your system
 To identify the people, organizations, and external systems
that will interact with your system
 To develop an initial risk assessment, schedule, and estimate
for your system
 To develop an initial tailoring of the Unified Process to meet
your exact needs
In iterative development and UP, plans and estimates are not to

be considered reliable in inception phase.
Project Management
 Involves the
 Planning
 Monitoring
 Control
Of people, process, and events that occur as a

software evolves from concept to an
operational implementation.
 Work Product
 Project Plan
The 4 P’s
People Stakeholders
Product the software to be built
the set of framework activities and

Process software engineering tasks to get the job
done
all work required to make the product a

Project
reality
Planning Practices
 Principals
 Understand the project scope
 Involve the customer / stakeholders
 Estimate based on what you know
 Consider risk
 Be realistic
 Adjust granularity as you plan
 Define how quality will be achieved
 Define how you will accommodate changes
 Track what you have planned
Project Planning Task Set
 Establish project scope
 Determine feasibility
 Analyze risks
 Define required resources
 Determine required human resources
 Define reusable software resources
 Identify environmental resources.
 Estimate cost and effort
 Decompose the problem
 Develop two or more estimates.
 Reconcile the estimates.
 Develop a project schedule
 Establish a meaningful task set
 Define a task network
 Use scheduling tools to develop a timeline chart
 Define schedule tracking mechanisms
Problem definition
 A problem statement is a clear description of the issue(s), it includes a
vision, issue statement, and method used to solve the problem.
 A problem statement expresses the words that will be used to keep the
effort focused and it should represent a solvable problem.
 The 5 'W's is a great tool that helps get pertinent information out for
discussion
 Who - Who does the problem affect? Specific groups, organizations,
customers, etc.
 What - What are the boundaries of the problem, e.g. organizational, work flow,
geographic, customer, segments, etc
 Where - When does the issue occur? - When does it need to be fixed?
 When - Where is the issue occurring? Only in certain locations, processes,
products, etc
 Why - Why is it important that we fix the problem? - What impact does it have
on the business or customer?
Objective \ Vision
 A project objective is a statement that describes the
“what” of your project. The tangible
and measurable “what”.
 Project objectives are the guideposts when making

decisions throughout the lifespan of the project.
 It’s important to have well-defined project objectives

that all stakeholders review and agree to.
 You need these objectives at project initiation and you’ll

reference them throughout the lifecycle of the project.
Project Scope
 Software scope defines
 at a high level, what the system will do. Equally
important is to define what the system will not do. This
establishes the boundaries of the system. This forms a
list of high level features.
 Scope is defined using one of the two techniques:

 A narrative description of software scope is
developed after communication with all stake
holders.
 A set of use cases is developed by end users.
Feasibility and Risk Analysis
 Feasibility - a feasibility analysis is used to determine the
viability of an idea, such as ensuring a project is legally and
technically feasible as well as economically justifiable. It tells
us whether a project is worth the investment — in some cases,
a project may not be doable.
 Risk – involves UNCERTAINTY and LOSS.
 Risk analysis takes into account
 What can go wrong
 What is the likelihood
 What will the damage be
 What can we do about it
 Risk can be technical, project related and business related.
Risk Management

OOAD Lecture 4

Uploaded by

Copyright:

Available Formats

OOAD Lecture 4

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

OOAD Lecture 4

Uploaded by

Copyright:

Available Formats

Object Oriented Analysis

Fall 2019 Semester

 Inception in one sentence:

 The main problem solved in one sentence:

In iterative development and UP, plans and estimates are not to

Of people, process, and events that occur as a

Product the software to be built

the set of framework activities and

all work required to make the product a

 Project objectives are the guideposts when making

 It’s important to have well-defined project objectives

 You need these objectives at project initiation and you’ll

 Scope is defined using one of the two techniques:

You might also like