diagram { /* line-style: sloppy 0.3; */ }

controlflow { dash-style: 0; }
Query
1. Use Cases
2. Domain Analysis
3. Architectural Design
4. Detailed Design
uc
Use Cases
Analyze functional requirements by identifying user roles – actors – and associating them to their use cases.
(1.0, 0.0, 0.0, 1.0, 93.76953125, 79.1953125)
(0.0, 0.0)
258.0
110.0
act
Use Case Scenarios
Model abstract use case implementation by creating activity diagrams visualizing activity flows for primary and secondary use case scenarios.
(1.0, 0.0, 0.0, 1.0, 58.0, 79.0)
(0.0, 0.0)
364.0
95.0
cls
Domain Entities
Perform domain analysis by modeling domain entities and their relationships using simplified class diagram. This diagram will serve as a visual dictionary of concepts. It will also be a starting point for your design-level data model.
(1.0, 0.0, 0.0, 1.0, 46.015625, 81.69921875)
(0.0, 0.0)
400.0
100.0
pkg
Package Dependencies
sd
Interactions
Prepare package dependencies diagram to group your implementation classes in appropriate way. This will help you maintain the code well structured and avoid design flaws such as cyclic dependencies or dependencies on unstable parts
(1.0, 0.0, 0.0, 1.0, 106.71484375, 51.49999999999997)
(0.0, 0.0)
271.5703125
144.0
Model component interactions for use case scenarios in order to find out new methods in existing classes or even new classes with specific responsibilities.
(1.0, 0.0, 0.0, 1.0, 43.0, 73.0)
(0.0, 0.0)
322.0
93.0
cls
Detailed Class Design
Create detailed class diagrams to capture your object-oriented data model.
(1.0, 0.0, 0.0, 1.0, 72.0, 76.5)
(0.0, 0.0)
215.0
76.0
cmp
Implementation Architecture
Define the major artifacts that manifest implementation of your components. Indicate how they are deployed on hardware nodes, their inter-dependencies and communication protocols.
(1.0, 0.0, 0.0, 1.0, -7.59375, 75.08984375)
(0.0, 0.0)
271.0
129.0
Interaction
(1.0, 0.0, 0.0, 1.0, 100.0, 100.0)
(0.0, 0.0)
150.0
100.0