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