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