1 S T P H A S E : T E A M L E A D , M O D E L I N S T A N T I A T I O N D E S I G N E R , S C R I B E
2 N D P H A S E : M O D E L I N S T A N T I A T I O N D E S I G N E R , S C R I B E
3 R D P H A S E : T E A M L E A D , M O D E L I N S TA N T I AT I O N D E V E L O P E R , D E P L O Y M E N T S E R V I C E D E V E L O P E R
Modeling and Realization of Mobile Multimedia Communications
KARL MORRIS
XABRIEL J. COLLAZO -MOJICA
1 S T P H A S E : M O D E L I N G E N V I R O N M E N T D E S I G N E R , D E P L O Y M E N T S E R V I C E D E S I G N E R
2 N D P H A S E : T E A M L E A D , M O D E L I N G E N V I R O N M E N T D E S I G N E R
3 R D P H A S E : M O D E L I N G E N V I R O N M E N T D E V E L O P E R , S C R I B E
Overview of the System
Provide a way for domain experts to model mobile communication services.
Abstract away the details of communications for mobile end-users. Mobile end-users only have to specify with whom they
want to communicate and not how.
Provide a proof-of-concept for realization of mobile CVM.
Design Methodology
USDP Use-case driven Work products as
models Breaks a project into phases
Tight integration with UML
Traceability!
Analysis model
Use case model
Design model
Deployment model
specified by
realized by
distributed by
System Development
.
.
. ...
Design Methodology
UML Object Diagrams
Capture scenario static behavior
Sequence Diagrams Captures scenario dynamic
behavior Class Diagrams
Synthesizes captured objects.
UML Profile Extends UML for our
specific modeling needs Deployment Diagrams
Maps the code artifacts to hardware resources
Image from: http://en.wikipedia.org/wiki/File:Uml_diagram2.png
Project Plan
GANNT
Weeks
09/07to09/14
09/14to09/21
09/21to09/28
09/28to10/05
10/05to10/12
10/12to10/19
10/19to10/26
10/26to11/02
11/02to11/09
11/02to11/09
11/02to11/09
11/23to11/30
Tasks
Project Definition
Req. Elicitatio
n
Req. Analysis
Design
Implementation and V&V
Project Plan
Milestones Formalization of model representation language Mobile architecture modeling Demo of implementation
Meeting best practices In-person meeting held weekly Agreed agenda distributed prior to meeting date Constant electronic communication encouraged
between meetings
System Requirements
The system shall allow domain experts to design models for the case of mobile-to-mobile communications. Related use cases that were implemented:
MMMC-2 – Validate Model MMMC-9 – Sign Model MMMC-11 – Design Mobile Communication Model
System Requirements
The system shall be able to deploy mobile-to-mobile communication models to the respective mobile participants Related use cases that were implemented:
MMMC-12 – Deploy Mobile Communication Model MMMC-13 – Pull Model
System Requirements
The system shall allow an already deployed communication model to be edited in the mobile device. Related use cases that were implemented:
MMMC-3 – Check or Specify Participants
System Requirements
The system shall allow an already deployed communication model to be instantiated from a mobile device. Related use cases that were implemented:
MMMC-1 – Instantiate Mobile Communication Model MMMC-4 – Do N-way Chat MMMC-8 – Do N-way Call
Validation of Models
Software Inspection (static) Syntactical Correctness
I.e. Does the model follow UML rules for that particular diagram?
Semantical Correctness I.e. Does this Sequence Diagram follows from the Object
Diagram and from the Scenario? Aesthetics
I.e. Is it readable? Should we partition this diagram in two (maybe because it includes two functionalities)?
Software Testing (dynamic) Executing an implementation with specific inputs
Object Diagram for Design Scenario #1
Validation MMMC-Test-1
Criteria Pass/Fail
Attribute Instances
PASS
No multiplicity PASS
Examples clarify links
PASS
Objects related to Class Diagram
PASS
Not too many diagrams
PASS
Readability PASS
Validation of Analysis Model
Sequence Diagram for Design Scenario #1
Validation MMMC-Test-2
Validation of Analysis Model
Criteria Pass/Fail
Actor Correctness
PASS
Object-Object Interaction
PASS
Correctness PASS
Object Timelines PASS
Represents the Object Design
PASS
Sufficient Notes FAIL
Architecture Validation MMMC-Test-3
Criteria Pass/Fail
Direction and type of Associations
PASS
Stereotypes PASS
Associations makes sense?
PASS
Follows from non-functional reqs?
PASS
Readability PASS
Comment Anchors
PASS
Validation of System Model
UML Profile Validation MMMC-Test-4
Validation of System Model
Criteria Pass/Fail
Direction and type of Associations
PASS
Stereotypes PASS
Associations make sense?
PASS
Follows from Meta-model?
PASS
Readability PASS
Comment Anchors
FAIL
Statemachine Diagram for Deployed MCM Object
Validation MMMC-Test-5
Criteria Pass/Fail
Entry/Exit Cond.
PASS
Every state and transition labeled
FAIL
States make sense?
PASS
Maps to object?
Ongoing
Readability? PASS
Complexity? PASS
Validation of Object Design Model
Validation of Object Design Model
Validation of Object Design Model
Validation MMMC-Test-5Criteria Pass/FailAssociation Multiplicity
PASS
Stereotypes use <<>>
PASS
Direction of Associations
PASS
Cardinality Check FAIL
Readability FAIL
Sufficient Explanatory Notes
PASS
Validation of Implementation Model
System tests example:Test Case ID MMMC-SystemTest-1
Purpose To validate Use Case MMMC-2 (Validate model) in the actual implementation
Preconditions User has launched the Design environment and has designed a valid MCM.
Stimulus User clicks on the validate feature of the model.
Expected Response
System accepted the model as valid.
Actual Response System accepted the model as valid.
Result PASS
Validation of Implementation Model
System tests example:Test Case ID MMMC-SystemTest-2
Purpose To validate Use Case MMMC-2 (Validate Model) in the actual implementation
Preconditions User has launched the Design environment and has designed an invalid MCM.
Stimulus User clicks on the validate feature of the model.
Expected Response
System rejects the model and explains the errors found.
Actual Response System rejects the model and explains the errors found.
Result PASS
THANK YOU FOR YOUR TIME.
Questions?
Top Related