Software Engineering Diagram Types Quiz and Flashcards

Study Notes

System Modeling Diagrams

Use Case Diagram: represents the interactions between a system and other 'actors'

System Design Diagrams

State Machine Diagram: used to model the behavioral aspects of a system
Class Diagram: represents the static relationships between design entities
Sequence Diagram: used to represent the synchronization and coordination of system activities

Notations and Diagrams

Black Box Notation: primary purpose is to model a system without considering its internal workings
Composite Structure Diagram: described as being more concerned with 'structure' and less explicitly related to any one viewpoint
Architecture Style Diagram: related to an architectural style focused on transaction-based forms, such as Client-Server architecture

Data Flow Diagrams (DFDs)

Primary Purpose: to model the flow of data through a system
External Entities: components that represent an external source or sink of information
True Statement: DFDs can be used to model systems at different levels of abstraction
De Marco's Distinction: DFDs focus on the flow of data rather than the control flow of the system
False Statement: DFDs are only used to model the internal workings of a system
Potential Drawback: DFDs can become complex and difficult to understand for large systems

Description

This quiz covers various types of diagrams commonly used in software engineering such as Data-Flow Diagram, Entity-Relationship Diagram, and UML diagrams like Class Diagram and Use Case Diagram. It also includes topics like State Transition Diagram and Structure Diagram.