1. 1 ST PHASE: TEAM LEAD, MODEL INSTANTIATION DESIGNER, SCRIBE 2 ND PHASE: MODEL INSTANTIATION DESIGNER, SCRIBE 3 RD PHASE: TEAM LEAD, MODEL INSTANTIATION DEVELOPER, DEPLOYMENT SERVICE DEVELOPER Modeling and Realization of Mobile Multimedia Communications KARL MORRIS XABRIEL J. COLLAZO-MOJICA 1 ST PHASE: MODELING ENVIRONMENT DESIGNER, DEPLOYMENT SERVICE DESIGNER 2 ND PHASE: TEAM LEAD, MODELING ENVIRONMENT DESIGNER 3 RD PHASE: MODELING ENVIRONMENT DEVELOPER, SCRIBE

2. 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.

3. 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............

4. 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

5. Project Plan GANNT Wee k s 09/07 to 09/14 to 09/21 to 09/28 to 10/05 to 10/12 to 10/19 to 10/26 to 11/02 to 11/09 11/02 to 11/09 11/02 to 11/09 11/23 to 11/30 Tasks Project Definition Req. Elicitation Req. Analysis Design Implementation and V&V

6. 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

7. 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

8. 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

9. 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

10. 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

11. 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

12. Object Diagram for Design Scenario #1 Validation MMMC-Test-1 CriteriaPass/Fail Attribute InstancesPASS No multiplicityPASS Examples clarify links PASS Objects related to Class Diagram PASS Not too many diagrams PASS ReadabilityPASS Validation of Analysis Model

13. Sequence Diagram for Design Scenario #1 Validation MMMC-Test-2 Validation of Analysis Model CriteriaPass/Fail Actor CorrectnessPASS Object-Object Interaction PASS CorrectnessPASS Object TimelinesPASS Represents the Object Design PASS Sufficient NotesFAIL

14. Architecture Validation MMMC-Test-3 CriteriaPass/Fail Direction and type of Associations PASS StereotypesPASS Associations makes sense? PASS Follows from non- functional reqs? PASS ReadabilityPASS Comment AnchorsPASS Validation of System Model

15. UML Profile Validation MMMC-Test-4 Validation of System Model CriteriaPass/Fail Direction and type of Associations PASS StereotypesPASS Associations make sense? PASS Follows from Meta- model? PASS ReadabilityPASS Comment AnchorsFAIL

16. Statemachine Diagram for Deployed MCM Object Validation MMMC-Test-5 CriteriaPass/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

18. Validation MMMC-Test-5 CriteriaPass/Fail Association Multiplicity PASS Stereotypes use >PASS Direction of Associations PASS Cardinality CheckFAIL ReadabilityFAIL Sufficient Explanatory Notes PASS

19. Validation of Implementation Model System tests example: Test Case IDMMMC-SystemTest-1 PurposeTo validate Use Case MMMC-2 (Validate model) in the actual implementation PreconditionsUser has launched the Design environment and has designed a valid MCM. StimulusUser clicks on the validate feature of the model. Expected ResponseSystem accepted the model as valid. Actual ResponseSystem accepted the model as valid. ResultPASS

20. Validation of Implementation Model System tests example: Test Case IDMMMC-SystemTest-2 PurposeTo validate Use Case MMMC-2 (Validate Model) in the actual implementation PreconditionsUser has launched the Design environment and has designed an invalid MCM. StimulusUser clicks on the validate feature of the model. Expected ResponseSystem rejects the model and explains the errors found. Actual ResponseSystem rejects the model and explains the errors found. ResultPASS

21. THANK YOU FOR YOUR TIME. Questions?