Object Model and Dynamic Model - The University of Texas at Dallas

advertisement
Phase 2 Software Domain Object Analysis
H.O.P.E.
Version 1.0
November 25, 2011
SE 6v81 .002 – Think For You (TFY)
Caitlin Fowler
Eric Blackburn
Frank (Zhenzhou Sun)
Frederico Araujo
Owolabi Legunsen
Sam Shaw
Sean Wilson
cmf067000@utdallas.edu
ejb022000@utdallas.edu
zxs101020@utdallas.edu
fxs105020@utdallas.edu
ool090020@utdallas.edu
sas071100@utdallas.edu
srw051000@utdallas.edu
http://www.utdallas.edu/~sas071100/hope
TFY
Domain Object Analysis
Version 1.0
Revision History
Version
0.1
1.0
Changes
Integrated collection of materials pertaining to the prearchitectural analysis of the system’s objects statically and
behaviorally.
Completed forward traceability matrix. Prepared for turn-in.
Date Modified
11/13/2011
11/25/2011
Page 2 of 12
TFY
Domain Object Analysis
Version 1.0
Table of Contents
Revision History
2
Table of Contents
3
1.
4
Introduction
1.1 Project overview
4
1.2 Purpose
4
1.3 Evolution of this document
4
1.4 References
4
1.5 Definitions, acronyms, and abbreviations
4
1.6 Object representation
5
1.7 Object goals and constraints
5
2.
Traceability matrix
5
3.
Use Case
8
4.
Domain object view points
9
4.1.
Static perspective
4.1.1. Domain Diagram
4.2.
Interaction perspective
4.2.1. System Sequence Diagram
4.2.2.
Sequence Diagram
9
9
10
10
10
11
Page 3 of 12
TFY
Domain Object Analysis
Version 1.0
1. Introduction
1.1 Project overview
Part of the world’s population has difficulty communicating and interacting with their environment due
to physical and mental disabilities. Difficulties with hearing loss, memory loss, and vision and speech
impairment are common problems encountered amongst the disabled population. H.O.P.E is an
application developed by the University of Texas at Dallas and Dr. Lawrence Chung in order to assist this
population with interacting and communicating with the world around them.
TFY is developing an application, which will integrate with the current H.O.P.E. application and allow the
user to sort icons based on contextual information. The icons will be sorted based on characteristics
such as time of year, location and frequency of use. The user will have the option to turn on and off the
module based on their preference.
1.2 Purpose
This document provides a pre-architectural overview of the context-aware sorting feature within the
domain that will extend the current version of the H.O.P.E. application. Multiple views are present to
highlight particular aspects of the software feature objects as seen from various perspectives.
1.3 Evolution of this document
See Revision History section for the document’s revision history.
1.4 References
Project Plan:
Project plan containing expected deliverables, deadlines, and project organization.
http://www.utdallas.edu/~sas071100/hope/Project_Plan_v3.0.doc
WRS:
Requirements specification document.
http://www.utdallas.edu/~sas071100/hope/WRSv09.doc
HOPE Website:
http://www.utdallas.edu/~rym071000/index.html
1.5 Definitions, acronyms, and abbreviations
H.O.P.E. – Helping Our People Easily
Page 4 of 12
TFY
Domain Object Analysis
Version 1.0
1.6 Object representation
This document presents the object analysis using 3 views: Use case, Domain Diagram, and System
Sequence Diagram.
1.7 Object goals and constraints
This section lists the object goals and constraints with respect to the new context-aware sorting feature
for the H.O.P.E. application.


Each sortable option must be related to a frequency statistic value, time statistic value, and AHP
priority weights.
The feature must reflect user habits.
2. Traceability matrix
Table 1 shows the traceability between the specified requirements and the architectural specification.
Table 1 – Forward traceability matrix from requirements specification, version 0.9.
D ID
Domain Object
3.2.1.1
3.2.1.2
3.2.1.3
3.2.2.1
3.2.2.2
3.2.2.3
3.2.2.4
3.2.2.5
3.2.2.6
3.2.2.7
3.2.2.8
HOPE Application
HOPE Application
Analytical Hierarchy Process Sorting Feature
Time Sorting Feature
Time Sorting Feature
Time Sorting Feature
Time Sorting Feature
Time Sorting Feature
Time Sorting Feature
Time Sorting Feature
Time Sorting Feature
Analytical Hierarchy Process Sorting Feature
Analytical Hierarchy Process Sorting Feature
Analytical Hierarchy Process Sorting Feature
Analytical Hierarchy Process Sorting Feature
Analytical Hierarchy Process Sorting Feature
Analytical Hierarchy Process Sorting Feature
3.2.3.1
3.2.3.2
3.2.3.3
3.2.3.4
3.2.3.5
3.2.3.6
FR ID
3.3.1.1
3.3.1.2
3.3.1.3
3.3.1.4
Frequency Statistic
Frequency Sorting Feature
Frequency Sorting Feature
Frequency Sorting Feature
Page 5 of 12
TFY
Domain Object Analysis
3.3.1.5
3.3.2.1
3.3.2.2
3.3.2.3
3.3.2.4
3.3.2.5
3.3.2.6
3.3.2.7
3.3.2.8
3.3.2.9
3.3.2.10
3.3.3.1
3.3.3.2
3.3.3.3
3.3.3.4
3.3.3.5
3.3.3.6
3.3.3.7
3.3.3.8
3.3.3.9
3.3.3.10
3.3.3.11
3.3.3.12
Version 1.0
Frequency Sorting Feature
Time Statistic
Time Statistic
Time Sorting Feature
Configuration Settings
Time Sorting Feature
Configuration Settings
Time Sorting Feature
Time Sorting Feature
Time Statistic
Time Sorting Feature
Analytical Hierarchy Process Sorting Feature
Analytical Hierarchy Process Sorting Feature
Priority Weight
Priority Weight
Analytical Hierarchy Process Sorting Feature
Priority Weight
Configuration Settings
Analytical Hierarchy Process Sorting Feature
Analytical Hierarchy Process Sorting Feature
Analytical Hierarchy Process Sorting Feature
Analytical Hierarchy Process Sorting Feature
Analytical Hierarchy Process Sorting Feature
O NFR ID
3.4.1.1
3.4.1.2
3.4.1.3
3.4.1.4
3.4.2.1
3.4.3.1
3.4.4.1
3.4.4.2
3.4.5.1
3.4.5.2
3.4.5.3
3.4.5.4
3.4.5.5
3.4.5.6
3.4.5.7
3.4.5.8
3.4.5.9
3.4.5.10
3.4.5.11
Analytical Hierarchy Process Sorting Feature
Analytical Hierarchy Process Sorting Feature
Analytical Hierarchy Process Sorting Feature
Analytical Hierarchy Process Sorting Feature
Analytical Hierarchy Process Sorting Feature
Analytical Hierarchy Process Sorting Feature
Analytical Hierarchy Process Sorting Feature
Analytical Hierarchy Process Sorting Feature
Analytical Hierarchy Process Sorting Feature
Analytical Hierarchy Process Sorting Feature
Analytical Hierarchy Process Sorting Feature
Analytical Hierarchy Process Sorting Feature
Analytical Hierarchy Process Sorting Feature
Analytical Hierarchy Process Sorting Feature
Analytical Hierarchy Process Sorting Feature
Analytical Hierarchy Process Sorting Feature
Configuration Settings
Analytical Hierarchy Process Sorting Feature
Analytical Hierarchy Process Sorting Feature
Page 6 of 12
TFY
Domain Object Analysis
3.4.5.12
3.4.5.13
3.4.5.14
3.4.6.1
3.4.6.2
3.4.6.3
3.4.6.4
3.4.6.5
3.4.6.6
3.4.6.7
3.4.7.1
3.4.7.2
3.4.8.1
Version 1.0
Analytical Hierarchy Process Sorting Feature
Analytical Hierarchy Process Sorting Feature
Analytical Hierarchy Process Sorting Feature
Configuration Settings
Configuration Settings
Configuration Settings
Configuration Settings
Configuration Settings
Configuration Settings
Configuration Settings
Time Sorting Feature
Analytical Hierarchy Process Sorting Feature
Analytical Hierarchy Process Sorting Feature
Page 7 of 12
TFY
Domain Object Analysis
Version 1.0
3. Use Case
View Fruit Options Sorted by Analytical Hierarchy Process (AHP)
Scope: HOPE System
Level: user goal
Primary Actor: Hope User (Speaker)
Stakeholders and Interests:
Speaker: Want an easy to navigate system, with minimum scrolling. Want to be able to
express
correct needs through system.
Assistive Person: Want to be able to care for and understand the Speaker.
Listener: Want to be able to understand the listener without a substantial wait.
Speaker Family Members: Want Speaker to live a happy life, have Speaker’s needs met.
Preconditions: Speaker has logged into the HOPE system and clicked sentence. The Speaker
has selected an option before in the Fruit category so that usage information has been gathered in
the system, and the information gathered has not been reset since gathering recent information. .
The AHP sorting feature is On.
Postconditions: The priority weights of each criterion, feature such as Frequency Sorting
Feature, are updated to reflect user’s habits.
Main Success Scenario:
1.
2.
3.
4.
5.
6.
7.
8.
9.
Speaker clicks Food option.
System displays Food options.
Speaker clicks Fruit option.
System displays Fruit options.
Speaker clicks the designated sort button.
System starts AHP process.
System gets information from Time Sorting Feature.
System gets information from Frequency Sorting Feature.
System applies priority weight adjustment on information received from the Time and
Frequency features.
10. System sorts options based on AHP, rankings.
11. System displays Fruit sorted fruit options with the highest ranked listed first.
12. User selects an option.
13. System ranks Time and Frequency features by which listed option picked highest in their
respective list of ranked options.
14. System increases priority of highest ranked feature and decreases priority of lowest ranked
feature.
Extensions: This is an abstract simple scenario and extension situation will not be covered.
Technology and Data Variations List:
 Any phone running the Android operating system
 Developers can add icons
 Developers can add categories
Frequency of Occurrence: Almost continuous.
Page 8 of 12
TFY
Domain Object Analysis
Version 1.0
4. Domain object view points
4.1.
Static perspective
4.1.1. Domain Diagram
Figure 1 – Domain diagram showing aspects of the frequency sorting feature, time sorting feature, and AHP
sorting feature in the context of the domain.
Page 9 of 12
TFY
Domain Object Analysis
4.2.
Version 1.0
Interaction perspective
4.2.1. System Sequence Diagram
Figure 2 – System Sequence diagram for sorting fruit.
Page 10 of 12
TFY
Domain Object Analysis
Version 1.0
4.2.2. Sequence Diagram
Figure 3 – Sequence Diagram for sorting fruit that demonstrates the responsibilities of the AHP sorting feature,
Time sorting feature, and the Frequency sorting feature in providing a sorted list of options to the user. This
diagram is meant as a template to aid in the process of developing an architecture and detailed design.
Page 11 of 12
TFY
Domain Object Analysis
Version 1.0
Figure 4 – Sequence Diagram for updating the priority weights controlled by the AHP sorting feature. This
diagram is meant as a template to aid in the process of developing an architecture and detailed design.
Page 12 of 12
Download