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