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