User interface subsystem
Components might be the viewer, the controller (we might have an MVC model)
On Database side show the DBMS
Application server where we show the significant components of our architecture inside the application components (for example in the case of library automation, the components might be cart catalog the central component in which all components work off of, librarian profile, circulation, ability to check in and check out artifacts, ordering might be another component, interface into building would be a third.)
No tables because we don’t know what they’re gonna be
6.1 Component Architecture Diagram
Show the 3 interconnected subsystems, and show connections to external systems (the utility thats gonna provide the services to the customers)
Architecturally significant design elements (components, subsystems, interfaces) and their relationships
Logical system architectures derived from functional requirements and the domain (context, scope, boundary) descriptions
6.2 Component Descriptions
Identify and describe the functionality of each system and subsystem component or subsystem shown in part 1.
6.3 Class Diagrams
Individual Class Diagrams (name, attributes, methods)
This section is initiated in this analysis document and the details are refined in the design document (some of the attributed and most of the methods will be completed in design)
6.4 Class Relationship / Interaction Diagrams
Class interaction diagrams
Draw relationship lines between classes and name them and cardinality if its many to many them youre probably missing a class!
Do dictionaries after this (class, method, dictionary)
6.5 Events
Events to which the system responds
6.5.1 Motives
Identify major events (motives in library would be to check out artifacts)
Cause an event that either changes the state of the system or an output
6.5.2 Event Diagrams
A diagram for each motive
6.6 Activity/State (Scenario) Section (Started in Analysis and completed in design)
A scenario (work flow) diagram will be provided for each scenario This section is started in this Analysis document and details are refined in the Design document
6.7 State logic (Started in analysis and completed in design)
6.8 Behavior
6.8.1 Sequence Diagrams
One per each requirment/use case
Cover the classes (domain/entity, boundary classes NO CONTROL CLASSES)
6.8.2 Collaboration Diagrams To be completed in design Requirements and Analysis Specification (RAS) Version 3.0 10 11/28/18
7. Dictionaries (Initiated here and completed in design) This is the initial set of dictionaries. They will be completed (refined) in the design Phase
7.1 Class
7.2 Method
7.3 Attribute
7.4 Relationship
7.5 Key Events
Sample dictionary format:
