Documente Academic
Documente Profesional
Documente Cultură
Confidential...........!!!!
Requirements Analysis
Requirements analysis
Confidential...........!!!!
A Bridge
system
description
analysis
model
design
model
Confidential...........!!!!
Rules of Thumb
Confidential...........!!!!
Domain Analysis
Software domain analysis is the identification, analysis,
and specification of common requirements from a
specific application domain, typically for reuse on
multiple projects within that application domain . . .
[Object-oriented domain analysis is] the identification,
analysis, and specification of common, reusable
capabilities within a specific application domain, in
terms of common objects, classes, subassemblies, and
frameworks . . .
Confidential...........!!!!
Domain Analysis
Confidential...........!!!!
Confidential...........!!!!
Scenario-Based Modeling
[Use-cases] are simply an aid to defining what exists
outside the system (actors) and what should be
performed by the system (use-cases).
(1) What should we write about?
(2) How much should we write about it?
(3) How detailed should we make our description?
(4) How should we organize the description?
Confidential...........!!!!
identify stakeholders
define the scope of the problem
specify overall operational goals
establish priorities
outline all known functional requirements, and
describe the things (objects) that will be manipulated by the
system.
Confidential...........!!!!
Confidential...........!!!!
10
Use-Cases
Confidential...........!!!!
11
Developing a Use-Case
Confidential...........!!!!
12
Use-Case Diagram
SafeHome
Access camera
surveillance via the
Internet
cameras
Configure SafeHome
system parameters
homeowner
Set alarm
Confidential...........!!!!
13
Activity Diagram
Supplements the use
case by providing a
graphical
representation of the
flow of interaction
within a specific
scenario
enter password
and user ID
valid passwords/ ID
invalid passwords/ ID
other f unctions
may also be
selected
input tries remain
select surveillance
thumbnail views
no input
tries remain
select specific
camera - thumbnails
prompt for
another view
exit this f unction
Confidential...........!!!!
14
Swimlane Diagrams
h o m e o wn e r
c a m e ra
i n t e rf a c e
enter password
and user ID
inpu t t ries
remain
select surveillance
n o input
t ries remain
select specific
camera - thumbnails
generate video
output
view camera output
in labelled window
prompt for
another view
exit t his
f unct io n
see
an o t her
camera
Confidential...........!!!!
15
Data Modeling
Confidential...........!!!!
16
Confidential...........!!!!
17
Confidential...........!!!!
18
What is a Relationship?
Confidential...........!!!!
19
ERD Notation
One common form:
object1
(0, m)
relationship
(1, 1)
object 2
attribute
object1
(0, m)
Confidential...........!!!!
(1, 1)
object 2
20
Building an ERD
Confidential...........!!!!
21
(1,1)
places
(1,m)
request
for service
(1,1)
standard
task table
generates
(1,1)
selected
from
work
(1,w) tasks
materials
Confidential...........!!!!
(1,w)
(1,n)
work
order
(1,1)
(1,1)
consists
of
(1,i)
lists
22
Class-Based Modeling
Confidential...........!!!!
23
Confidential...........!!!!
24
Confidential...........!!!!
25
Potential Classes
Confidential...........!!!!
26
Defining Attributes
Confidential...........!!!!
27
Defining Operations
Confidential...........!!!!
28
CRC Models
Confidential...........!!!!
29
CRC Modeling
Class:
Class:
Description:
Class:
Description:
Class:FloorPlan
Description:
Responsibility:
Description:
Responsibility:
Responsibility:
Responsibility:
Collaborator:
Collaborator:
Collaborator:
Collaborator:
Confidential...........!!!!
Wall
Camera
30
Class Types
Confidential...........!!!!
31
Responsibilities
Confidential...........!!!!
32
Collaborations
Confidential...........!!!!
33
PlayerHead
Confidential...........!!!!
PlayerBody
PlayerArms
PlayerLegs
34
Confidential...........!!!!
In such cases, a client-class depends on the serverclass in some way and a dependency relationship is
established
35
Multiplicity
Wall
1
is used to build
Confidential...........!!!!
1
is used to build
1..*
WallSegment
Window
0..*
Door
36
Dependencies
Camera
DisplayWindow
<<access>>
{password}
Confidential...........!!!!
37
Analysis Packages
Confidential...........!!!!
38
Analysis Packages
package name
Environment
+Tree
+Landscape
+Road
+Wall
+Bridge
+Building
+VisualEffect
+Scene
RulesOfTheGame
+RulesOfMovement
+ConstraintsOnAction
Characters
+Player
+Protagonist
+Antagonist
+SupportingRole
Confidential...........!!!!
39
All participants in the review (of the CRC model) are given a subset of the CRC model
index cards.
Cards that collaborate should be separated (i.e., no reviewer should have two cards
that collaborate).
All use-case scenarios (and corresponding use-case diagrams) should be organized into
categories.
The review leader reads the use-case deliberately.
As the review leader comes to a named object, she passes a token to the person
holding the corresponding class index card.
When the token is passed, the holder of the class card is asked to describe the
responsibilities noted on the card.
The group determines whether one (or more) of the responsibilities satisfies the
use-case requirement.
If the responsibilities and collaborations noted on the index cards cannot accommodate
the use-case, modifications are made to the cards.
This may include the definition of new classes (and corresponding CRC index cards)
or the specification of new or revised responsibilities or collaborations on existing
cards.
Confidential...........!!!!
40