A) Represent objects states and transitions B) Visualize system actors C) Show software and hardware configurations D) Depict workflows in use cases
A) Identifying class relationships B) Drawing sequence diagrams C) Writing the system requirements D) Identifying actors
A) Extend B) Generalization C) Use D) Include
A) It validates the system architecture B) It visualizes hardware requirements C) It depicts the data flow in the system D) It manages the project's timelines
A) based on system architecture B) from the perspective of actors C) based on workflows D) based on functionality
A) with arrows B) with the dotted lines C) with solid lines D) with triangles
A) State Machine Diagram B) Class Diagram C) Activity Diagram D) Deployment Diagram
A) gathering and clarifying system requirements B) testing the system components C) managing project timelines D) coding the system architecture
A) who gets information from this system B) who installs the system C) what functions the system performs D) what data the system processes
A) relationships between use cases B) system requirements C) hardware configurations D) interactions between objects over time
A) The high level-structure of software components B) object interactions over time C) the dynamic behavior of the system D) The hardware configurations of a system
A) to specify base use case functionalities B) to show optional system behavior C) To show common behavior D) to define actors interactions
A) system administrators B) analysts C) actors D) developers
A) extend B) association C) generalization D) include
A) software components and their dependencies B) classes and their methods C) objects and their relationships at a specific point in time D) system workflows
A) unstructured modeling language B) unified modeling language C) universal modeling language D) unified management language
A) 1990 B) 2005 C) 1995 D) 1985
A) sequence diagram B) class diagram C) data flow diagram D) use case diagram
A) activity diagram B) use case diagram C) class diagram D) sequence diagram
A) static structure: classes, attributes, methods, and relationships B) object states and transitions C) system workflows D) dynamic behavior of a system
A) state machine diagram B) sequence diagram C) use case di D) class diagram
A) to visualize system workflows B) To show hardware configurations C) The summarize the system's users and their interactions D) to the big class relationships
A) a user or system interacting with the application B) a module within the software C) a database system D) a hardware component
A) after testing the system B) at the early stage of development C) right before deployment D) during the coding phase
A) a use case using the functionality of another use case B) a child use case inheriting from a parent use case C) a dependency between two use cases D) The optional behavior of a system
A) system workflows B) optional functionality C) actor interactions with multiple systems D) inheritance between use cases
A) Show mandatory system behavior B) include optional system behavior C) depict system requirements system requirements D) include test cases
A) software developers alone B) domain experts only C) analyst and domain expert together D) system administrators
A) sequence diagram B) state machine diagram C) activity diagram D) use case diagram
A) object relationships in real time B) system interactions with users C) high level software components and their dependencies D) workflows within use cases |