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