1 Lecture 4.5: AV-1 and AV-2 (Ch 3.1 and 3.2) Dr. John MacCarthy UMBC CMSC 615 Fall, 2006

2 Agenda AV-1 Overview and Summary Information (Overview) AV-2 Integrated Dictionary (Overview) Conclusions

3 AV-1: Overview and Summary Information (3.1) Product Definition: the AV-1 “provides executive-level summary information in a consistent form that allows quick reference an comparison among architectures. AV-1 It includes assumptions, constraints and limitations that may affect high-level decision processes involving the architecture.” Product Purpose: “[It] enable[s] the reader to select one or more architectures from among many to read in detail. … it serves as a planning guide … [and] provides summary textual information concerning the architecture.” Implementation Options Hyperlinks Briefing Text, Tables, Graphics Views Multiplicity: 1/project Critical Artifact Product Detailed Description (Content):

4 Base Product Description (X.Y.1) and UML Representation (X.Y.2) X.1.1 provides a description of the “reference” artifact (generally SA- based) X.1.2 provides one or more UML artifacts that may be used as an alternative to the reference artifact Note there is no UML equivalent to a AV-1

5 AV-1 Data Element Definition (3.1.3) [1]

6 AV-1 Data Element Definition (3.1.3) [2]

7 CADM ER Diagram for the AV-1 (3.1.4)

8 Class Exercise: Develop AV-1

9 AV-2: Integrated Dictionary Product Definition: The AV-2 “contains definitions of terms used in a given architecture.” :Consists of textual definitions in he form of a glossary” “Data repository with definitions of all terms used in all products” All functions, nodes, classes, data entity, data attribute, operations, components, interfaces, etc. Product Purpose: “Provides a central repository for a given architecture’s data and metadata.” Ensures Consistency/Unity in vision Ensures Consistency between Artifacts Implementation Options: Access Database Word Document Architecting Tool Output Multiplicity: 1/project Content: Definitions of Terms used in the Architecture: Activities/Functions/Methods Input/Output/Internal Data Entities Data Attributes (including description, data type, range, units, etc.) Actors Operational Nodes Structural Elements/Mechanisms (Systems, Subsystems, Components, Interfaces, etc.) Classes Performance Metrics Etc. May also include Acronym List Critical Artifact

10 Taxonomies (Types of entities)

11 Base Product Description (3.2.1) and UML Representation (3.2.2) provides a description of the “reference” artifact (generally SA- based) provides one or more UML artifacts that may be used as an alternative to the reference artifact Note there is no UML equivalent to a AV-1

12 Data Element Definitions (3.2.4) and CADM Model (3.2.5) Blah Blah Blah …

13 AV-2: Integrated Dictionary - WBRS Example

14 Example: Integrated Dictionary Legend Entry Types: Operational Node (ON) Operational Element (OE) System (Sys) Subsystem Element (SE) Actor (Actor) External System (ES) External Subsystem Element (ESE) Function/Activity (Fnc) Rule Model (RM) State (State) Data Entity (DE) Data Attribute (DA) Reference ID: Function/Activity: A1.X.y System/Subsystem Element: C1.X.y External System/Subsystem Element: ESX.Y Rule Model: RM1.X.y Data Entity (DE): DEX.y Acronym Term Definitions Functions should indicate I/O Des and Rule Models System/Subsystem Elements should include alllocated Functions DEs should include list of DAs DAs should include data type, visibility, and ranges. RMs should include reference to functions and DEs

15 Conclusions AV-1 and AV-2 are essential products for every architecture AV-1 is usually developed in a Word (or HTML) document and may be hyperlinked to supporting artifacts Initially one may want to develop the AV-2 in Word or Excel until you figure out the desired format or until a CASE Architecture Tool is selected.