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