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