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