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