Presentation is loading. Please wait.

Presentation is loading. Please wait.

UML Development - Overview PROGRAM ACTORS ANALYSIS Domain Objects DESIGN IMPLEMENTATION D A T A D I C T I O N A R Y Time USE CASES ANALYSIS CLASS DIAGRAM(S)

Similar presentations


Presentation on theme: "UML Development - Overview PROGRAM ACTORS ANALYSIS Domain Objects DESIGN IMPLEMENTATION D A T A D I C T I O N A R Y Time USE CASES ANALYSIS CLASS DIAGRAM(S)"— Presentation transcript:

1 UML Development - Overview PROGRAM ACTORS ANALYSIS Domain Objects DESIGN IMPLEMENTATION D A T A D I C T I O N A R Y Time USE CASES ANALYSIS CLASS DIAGRAM(S) IMPLEMENTATION CLASS DIAGRAM SEQUENCE DIAGRAMS OPERATION CONTRACTS CLASS STATE DIAGRAMs DEPLOYMENT DIAGRAM SUBSYSTEM/ COMPONENT DIAGRAMS System Design Object Design SCENARIOS REQUIREMENTS ELICITATION DESIGN CLASS DIAG. IMPLEMENTATION CHOICES DESIGN COLLABORATION DIAG.

2 Information Available at Architectural Design Use cases, Use case Diagram Analysis and Arc. Design class diagrams Analysis and Arc. Design Sequence/Collaboration diagrams Statecharts for multi-modal classes Subsystems + their public interface (API) Subsystem dependencies Mapping subsystems’ instances to Hardware (Deployment) Data management, Security control

3 MyTrip Analysis Class Diagram Location Segment Crossing Direction Destination Trip RouteAssistant PlanningService

4 MyTrip Subsystems Location Segment Crossing Direction Destination RoutingSubsystem PlanningSubsystem Trip RouteAssistant PlanningService

5 Subsystem Interface The set of public operations forms the subsystem interface or Application Programming Interface (API) Includes operations but also their parameters, types, and return values Operation contracts are also defined (pre- and post-conditions) and accounted for by client subsystems – they can be considered part of the API

6 6 Components vs Subsystems A Component are used to implement a package of classes defined in a subsystem A component defines a module in the architectural design Component types defined by component stereotypes include a Main program component, and Tasks Task components represent packages or subsystems with independent threads of control

7 7 Components and Component stereotypes

8 MyTrip Deployment Diagram :RoutingSubsystem :PlanningSubsystem :OnBoardComputer :WebServer Components must be associated with a processor4 node in the deployment diagram

9 New Classes and Subsystems Trip Location PlanningService Segment Crossing RouteAssistant Direction Destination TripProxy SegmentProxy PlanningSubsystem Message Connection CommunicationSubsystem RoutingSubsystem

10 MyTrip Data Storage PlanningSubsystem MapDBStoreSubsystem TripFileStoreSubsystem RoutingSubsystem CommunicationSubsystem

11 Static versus Dynamic Architecture Information Subsystem Interfaces and dependencies provide static information Interaction models provide dynamic information Concurrency information can be specified on objection collaboration diagrams, sequence diagrams, and component diagrams

12 12 Concurrency Adornment The concurrency of a class is a statement about its semantics in the presence of multiple threads of control. You can set the concurrency of a class to type Active The class will has its own thread of control. The method can be executing concurrently with other methods. You can display the concurrency for the class in the class diagram by selecting Show Concurrency from the class shortcut menu.

13 13 Concurrency in Sequence Diagrams Synchronous method invocation for sequential execution

14 14 Concurrency in Sequence Diagrams

15 15 Concurrency in Sequence Diagrams Asynchronous method calls should be explicitly identified with the UML standard notation of a solid line with a half arrowhead. Asynchronous messages do not yield the current thread of control. Therefore, from the initiating object's viewpoint, there is no implied return message or waiting

16 16 Proposed Component-based IETM Display System Architecture Business ServicesUser ServicesData Services IETM Object Model MIL-PRF-87269A Alternative COTS Components Web Technologies IETM Object Model Interfaces

17 17 User Interface Web Server IETM Navigation Handler Receive-Request Receive-Response User Interface Engine Send-Request Send-Response Web page + Style info if not processed on server (Requires IE5) GUI Manager Render-Info Might require a Media Server Media Viewer Scripts Applet Jbeans ActiveX Forms Plugins or Helper Applications Browser HTTP, IIOP, DCOM

18 18 IETM EDS IETM Display Engine IETM Object Model Search IETM Object Model Interfaces Get-Result- Objects Start IETM Interpreter Get-IETM- Objects Receive-Request Send-Response Web Server Receive- Response Optional: Use it to allow rendering on all browsers not just IE5 XML/HTML Transformer (XSL Processor) CGI Servlet EJB CORBA Beans VB, Java, ECMA Scripts ASP, JSP Session State Session Manager Session Cache Remove GetAddUpdate

19 19 Data Access Database-driven System Data Loader IETM Content Get-Info Style Info Database Object Interface Get-Result- Objects IETM Interpreter Vendor Driver + ODBC or JDBC Driver Database to DOM Relational to Object Mapping SQL OQL SQLJ XML/HTML Transformer (XSL Processor) Database on O/DBMS Server XML on O/DBMS Server O/DBMS + ORBCORBA/IIOPCORBA Server

20 20 Architectural Forms in UML IETM Object Model NODE-ALTS Nodes : NODE Eval_Alts() > NODE name : CDATA type : CDATA itemid : CDATA preconditions [0..*] : precond postconditions [0..*] : postcond Contents : InformationContent-Forms primitives [0..*] : %primitive links [0..*] : %link Display() Set_Post_Conditions() Eval_Pre_Conditions() hasContents() > 1 1..* 1 InformationContent-Forms 1 0..* 1 LOOP-NODE IndexDeclare [0..1] : assertion ExitCond : expression IndexAlter [0..1] : assertion RepeatSeq : NODE-SEQ Start() Eval_Condition() Update_Index() Terminate() > Architectural-Forms id : ID cdm : NAME ref : IDREF IF-NODE Condition : expression ThenSeq : NODE-SEQ ElseSeq [0..1] : NODE-SEQ selectFlow() getThenSeq() > NODE-SEQ SeqElements : Architectural-Forms getNextElement() > 1 1 1 1 1 1..* 1 stepBack() hasMoreElements() Reset()

21 21 The IETM Object Model Interfaces IETM Object Model


Download ppt "UML Development - Overview PROGRAM ACTORS ANALYSIS Domain Objects DESIGN IMPLEMENTATION D A T A D I C T I O N A R Y Time USE CASES ANALYSIS CLASS DIAGRAM(S)"

Similar presentations


Ads by Google