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