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