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