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