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