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