1.

Inception
• 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?
• Oil drilling analogy as inception:
• Estimates about oil availability is inception. Its feasibility study to
decide whether the project continue or not. But realistic exploration
of oil is elaboration.
• If feasibility study or vision about the project to be develop is clear
then inception may be very brief.
• It must be one week or two week long period of time for inception
 What Artifacts May Start in Inception?
Artifact Comment
Vision and Business Case Describes the high-level goals and constraints, the business
case, and provides an executive summary.
Use-Case Model Describes the functional requirements, and related non-
functional requirements.
Supplementary Describes other requirements.
Specification,
Glossary Key domain terminology.
Risk List & Risk Describes the business, technical, resource, schedule risks, and
Management Plan ideas for their mitigation or response.
Prototypes and proof-of- To clarify the vision, and validate technical ideas.
concepts,
Iteration Plan Describes what to do in the first elaboration iteration.
Phase Plan & Software Low-precision guess for elaboration phase duration and effort.
Development Plan , Tools, people, education, and other resources.
Development Case
A description of the customized UP steps and artifacts for this
project. In the UP, one always customizes it for the project.
 Requirements
• These are user real scenarios or stories or
needs.
• Requirements are capabilities and conditions
to which the system—and more broadly, the
project—must conform or adapt. A prime
challenge of requirements work is to find,
communicate, and remember what is really
needed, in a form that clearly speaks to the
client and development team members..
 Types of Requirements
• In the UP, requirements are categorized according to the
FURPS+ model .
• F > Functional—features, capabilities, security…
• U > Usability—human factors, help, documentation
• R > Reliability—frequency of failure, recoverability,
predictability
• P > Performance—response times, throughput, accuracy,
availability, resource usage.
• S > Supportability—adaptability, maintainability,
internationalization, con figurability
The "+" in FURPS+ indicates Supplementary and
sub-factors, such as:
• Implementation —resource limitations, languages and
tools, hardware, ...
• Interface —constraints imposed by interfacing with
external systems.
• Operations —system management in its operational
setting.
• Packaging
• Legal —licensing and so forth.
In common usage, requirements are categorized as
functional and non functional requirements.
Requirements Engineering Process
• From Ms Word Documents and Research
Papers
 Use case diagrams
• Describe the functional behavior of the system
as seen by the user.
• e.g. See diagram on next slide…
Use case diagrams represent the functionality of the system
from user’s point of view

Classifier
Use Case

Actor.

System boundary