1. 4 REQUIREMENTS ANALYSIS CASE STUDY

2. Initialize Use Case for Encounter
Use case details
actors
Initialize
1. System displays player’s main character in the dressing room.
2. System displays a window for setting his character's qualities.
3. Player allocates the qualities of his main character.
4. Player chooses an exit from the dressing room.
5. System moves player’s main character into the area on the other side of the exit.
Use case
Initialize
Travel to
adjacent area
player
Encounter
foreign
character
designer
Set rules
Adapted from Software Engineering: An Object-Oriented Perspective by Eric J. Braude (Wiley 2001), with permission.

3. Engage Foreign Character Use Case
Encounter
Use case details
Engage Foreign Character
1. System displays the foreign character in the same area as the player’s.
2. System exchanges quality values between the two characters.
3. System displays the results of the engagement.
4. System displays player’s character in a random area.
Use case
Initialize
Travel to
adjacent area
player
Engage
foreign
character
designer
Set rules
Adapted from Software Engineering: An Object-Oriented Perspective by Eric J. Braude (Wiley 2001), with permission.

4. Conceptual Model of the System
Player 1
ForeignCharacter n
Plays
Has 1 1
EncounterGame
Has 1 1
MainCharacter 1 1
Entity
Relationship
Model or
Object Model
Has
Has
Area n n
Engagement 1
Takes place in 1

5. Data Flow Diagram: Explanation of Symbols
Processing
element
Get
deposit
Account #
& deposit
Direction
of data flow
Data type
Check
deposit

6. Data Flow Diagram: Explanation of Symbols
Processing
element
Get
deposit
Input
User
Account #
& deposit
Output
Direction
of data flow
Printer
Data type
Check
deposit
…...
balance
query
Create
account
summary
account
data
account
database
Data store
Adapted from Software Engineering: An Object-Oriented Perspective by Eric J. Braude (Wiley 2001), with permission.

7. Partial Data Flow Diagram for ATM Application
member
banks
Get
deposit
Get
inquiry
User
bank name
error
account #
error
account #
& deposit
account
display
Validate
deposit
Validate
inquiry
Display
account
Make
inquiry
account #
account #
& deposit
Printer
account
data
balance
query Do
deposit
transaction
Create
account
summary
deposit
transaction
account
data
account
database
Adapted from Software Engineering: An Object-Oriented Perspective by Eric J. Braude (Wiley 2001), with permission.

8. Partial Encounter State-Transition Diagram
Preparing
Setting up
Player clicks qualities menu
Complete setup
Foreign character enters area
Waiting
Engaging
Adapted from Software Engineering: An Object-Oriented Perspective by Eric J. Braude (Wiley 2001), with permission.

9. Using Conditions in State-Transition Diagrams
event
condition
Waiting
Player moves to adjacent area
[foreign character present]
[foreign character absent]
Engaging
state
condition
Adapted from Software Engineering: An Object-Oriented Perspective by Eric J. Braude (Wiley 2001), with permission.

10. Sketch of Encounter State-Transition Diagram
Reporting
Setting
qualities
Setting up
Player dismisses report window
Player completes setup
Player dismisses set qualities widow
Player requests to set qualities
Player requests status
Foreign character enters area
Waiting
Encounter completed
Foreign character enters area
Player moves to adjacent area
Engaging
Player quits
[foreign character absent]
[foreign character present]
Adapted from Software Engineering: An Object-Oriented Perspective by Eric J. Braude (Wiley 2001), with permission.

11. Sequence diagrams

12. Beginning of Sequence Diagram for Initialize Use Case
dressing
room:
Area
:Encounter-
Game
1. create
time

13. Beginning of Sequence Diagram for Initialize Use Case
note 1
main player
character:
Player Character
dressing
room:
Area
:Encounter-
Game
note 2
note 3
note 4
1. create
time
create
Adapted from Software Engineering: An Object-Oriented Perspective by Eric J. Braude (Wiley 2001), with permission.

14. Sequence Diagram for Initialize Use Case
:Encounter-
Game
main player
character:
Player Character
:Player
quality
window
dressing
room:
Area
1*.1 create
1. create
User
2. create
3a. set quality values
3b. set quality values
4. select exit for character
5. move
* Numbering keyed to use case
Adapted from Software Engineering: An Object-Oriented Perspective by Eric J. Braude (Wiley 2001), with permission.

15. Sequence Diagram Showing Concurrency
Player
:Encounter-game
mainPlayer-
Character:
PlayerCharacter
freddie:
ForeignCharacter
create & display
move
(Concurrent player movement)
create & display
move
Adapted from Software Engineering: An Object-Oriented Perspective by Eric J. Braude (Wiley 2001), with permission.

16. Build a Sequence Diagram 1
One way to ...
Build a Sequence Diagram 1
1. Identify the use case whose sequence diagram you will build
2. Identify which entity initiates the use case
the user, or
an object of a class
name the class
name the object
3. Draw a rectangle to represent this object at left top
use UML object:Class notation
4. Draw an elongated rectangle beneath this to represent the execution of an operation
5. Draw an arrow pointing right from its top
myObject
:MyClass
Adapted from Software Engineering: An Object-Oriented Perspective by Eric J. Braude (Wiley 2001), with permission.

17. Build a Sequence Diagram 2
One way to ...
6. Identify which entity handles the operation initiated
an object of a class
name the class
name the object
7. Label the arrow with the name of the operation
don’t show return
8. Show a process beginning, using an elongated rectangle
9…… Continue with each new statement of the use case.
MyObject
:MyClass
MyObject1
:MyClass1
My operation
Adapted from Software Engineering: An Object-Oriented Perspective by Eric J. Braude (Wiley 2001), with permission.

18. Classes in Initialize Sequence Diagram
EncounterGame
- a class with a single object
PlayerCharacter
- with object mainPlayerCharacter
Area
- with object dressingRoom, and
PlayerQualityWindow
- a GUI class included to complete the use case.
Adapted from Software Engineering: An Object-Oriented Perspective by Eric J. Braude (Wiley 2001), with permission.

19. Sequence Diagram for Initialize Use Case
main player
character:
Player Character
dressing
room:
Area
:Encounter-
Game
1*. «create»
1. «create»
Adapted from Software Engineering: An Object-Oriented Perspective by Eric J. Braude (Wiley 2001), with permission.

20. Sequence Diagram for Travel to Adjacent Area Use Case
:ConnectionHyperlink
:AreaConnection
:PlayerCharacter
User
:Area
1.1 hit
1.2 display other area
2.1 display
2.2 display
Adapted from Software Engineering: An Object-Oriented Perspective by Eric J. Braude (Wiley 2001), with permission.

21. Sequence Diagram for Engage Foreign Character Use Case
freddie:
Foreign
Character
Encounter
game
anEngagement
: Engagement
1.1 create; display
1.2 create
2. execute
Adapted from Software Engineering: An Object-Oriented Perspective by Eric J. Braude (Wiley 2001), with permission.

22. Sequence Diagram for Engage Foreign Character Use Case
:Encounter
Game
freddie:
Foreign
Character
:Engagement
:Engagement
Display
:Player
Character
1.1 create; display
1.2 create
2.1 execute
2.2 change quality values
3.1 Display result
3.2 create
Adapted from Software Engineering: An Object-Oriented Perspective by Eric J. Braude (Wiley 2001), with permission.

23. Case Study HCI Interfaces

24. Foreign Character Freddie’s Image
Adapted from Software Engineering: An Object-Oriented Perspective by Eric J. Braude (Wiley 2001), with permission.
Graphics reproduced with permission from Corel.

25. Player Character Image Options
Elena
Sean
Boris
Adapted from Software Engineering: An Object-Oriented Perspective by Eric J. Braude (Wiley 20001), with permission.
Graphics reproduced with permission from Corel.

26. User Interface for Setting Quality Values
Sean
Current life points: 100.0
Choose the quality you wish to set
Choose the value of the quality selected
16.3
image
Adapted from Software Engineering: An Object-Oriented Perspective by Eric J. Braude (Wiley 2001), with permission.
Graphics reproduced with permission from Corel.

27. User Interface for Setting Quality Values
Sean
Current life points: 100.0
Image
Choose the quality you wish to set
Choose the value of the quality selected
16.3
Explanation
The values of the qualities not specifically chosen remain in the same proportion to each other. Values less than 0.5 are counted as zero. E.g.,
before: strength = 10.0, endurance = 60.0, intelligence = 30.0, patience = 0.0
(current life points = 100.0)
change: strength from 10.0 to 20.0
after: strength = 20.0, endurance = 53.3, intelligence = 26.7 OK
Adapted from Software Engineering: An Object-Oriented Perspective by Eric J. Braude (Wiley 2001), with permission.
Graphics reproduced with permission from Corel.

28. Encounter Courtyard Image (including game characters)
Note: Each part of this figure is specified separately in section 3.
kitchen
COURTYARD
living room
dressing room
Graphics reproduced with permission from Corel. OK
Get status
Set qualities
End game

29. Encounter Courtyard Image
kitchen
kitchen
COURTYARD
living room
dressing room
Get status
Set qualities
End game
Adapted from Software Engineering: An Object-Oriented Perspective by Eric J. Braude (Wiley 2001), with permission.

30. Encounter Dressing Room Image
courtyard
dungeon
Get status
Set qualities
End game
Adapted from Software Engineering: An Object-Oriented Perspective by Eric J. Braude (Wiley 2001), with permission.

31. Encounter Dungeon Image
dressing room
study
Get status
Set qualities
End game
Adapted from Software Engineering: An Object-Oriented Perspective by Eric J. Braude (Wiley 2001), with permission.

32. Encounter Kitchen Image
Get status
Courtyard
Set qualities
End game
Adapted from Software Engineering: An Object-Oriented Perspective by Eric J. Braude (Wiley 2001), with permission.

33. Encounter Living Room Image
courtyard
Get status
study
Set qualities
End game
Adapted from Software Engineering: An Object-Oriented Perspective by Eric J. Braude (Wiley 2001), with permission.

34. STUDY Encounter Study Image Living room dungeon Get status
Set qualities
End game
Adapted from Software Engineering: An Object-Oriented Perspective by Eric J. Braude (Wiley 2001), with permission.

35. Encounter Area Configuration (Desirable Requirement)
Kitchen
Dressing
room
Courtyard
Living
room
Dungeon
Study
Key:
= connection
Adapted from Software Engineering: An Object-Oriented Perspective by Eric J. Braude (Wiley 2001), with permission.

36. User Interface for Status
Elena
Current life points: 56.68
Strength
Endurance
Intelligence
Patience
Value
16.18
Endurance
Adapted from Software Engineering: An Object-Oriented Perspective by Eric J. Braude (Wiley 2001), with permission.
Graphics reproduced with permission from Corel.