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