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