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