Exam 2 Flashcards
(38 cards)
Activity diagrams
which show the activities involved in a process or in data processing .
Use case diagrams
which show the interactions between a system and its environment.
Sequence diagrams
which show interactions between actors and the system and between system components.
Class diagrams
which show the object classes in the system and the associations between these classes.
State diagrams
which show how the system reacts to internal and external events.
External Entity
Square shape: An element that inputs data into a system and/or retrieves data from the system.
Process
Circle: Circle represent a process. In context diagram there is only 1 process that represents the entire system.
Flow Line
shows the movement of data from one entity/process to another
Interaction Models
-Use case modeling:model interactions between a system and external agents
-Sequence Diagrams: model interactions between system components
Use Case Model Symbols
System: Rectangle
Use Case: Circle
Actor: Person
Line: Relationships
«Include»
Points to Included Use case, always happens
«Extend»
Points to Base Use case, sometimes happens but not required
Inheritance
Open arrow Ex. Customer with children New Customer and Returning Customer
Structural Models
Class Diagrams
Class Diagram
Box With the following:
Class Name/
Attributes (like int char etc)/
Operations/Methods (void operation(), int operation_c(int), etc)
Class Diagram Symbols
Public(+)
Private(-)
Protected(#)
Relationships
Open arrow: Inheritance
Straight Line: Association
Aggregation: open diamond
Behavioral Model
Data-driven modeling
-Activity diagrams
Event-driven modeling
-State machine
Data-Driven Model figures
Box: shows input/outputs from objects.
Oval box: shows activities
Model-driven Engineering
is an approach to software development where models rather than programs are the principal outputs of the development process.
Types of models in Model-driven architecture (MDA)
-A computation-independent model (CIM)
-A platform-independent model (PIM)
-Platform-specific models (PSM)
Cons to MDA
-There is limited tool availability and organizations may require tool adaptation and customization to their environment
-Companies do not want to develop or maintain their own tools or to rely on small software companies, who may go out of business
-Without these specialist tools, model-based development requires additional manual coding which reduces the cost-effectiveness of this approach.
Importance of Architecture
Architecture is a critical link between requirements and the software that will be built.
Box Architecture
Each box in the diagram represents a component. Boxes within boxes indicate that the component has been decomposed into subcomponents.