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