Object-Oriented Analysis and Design Practice Quiz (26 questions)

Explanation

A software process consists of activities that transform user requirements into a software system. Source code, testing, and deployment are activities or outputs within that broader transformation, not its initial input.

Explanation

The main phases progress from identifying requirements through analysis, design, programming, testing, and finally deployment and maintenance. The other sequences place major phases in an incorrect order.

Explanation

Analysis defines the system’s required behavior, such as sending low-inventory alerts, whereas design determines the implementation approach. Coding, deployment, testing, and maintenance are separate development activities.

Explanation

Waterfall proceeds through completed phases in sequence, while the Prototype model creates an early working model to clarify requirements. Risk-focused iteration characterizes the Spiral model rather than Waterfall.

Explanation

The Spiral model is defined by combining iteration with risk analysis during development. Fixed sequencing describes Waterfall, rapid requirement clarification describes Prototyping, and functional decomposition describes structured analysis.

Explanation

Object-oriented analysis decomposes a system into objects that combine data and behavior, as in Customer, Order, and Product entities. Structured analysis instead separates data from processing and decomposes the system by functions.

Explanation

An object has state represented by attributes, behavior represented by methods, and an identity that distinguishes it from other objects. Separating data from processing is characteristic of structured analysis rather than the definition of an object.

Explanation

The four core object-oriented properties are abstraction, encapsulation, inheritance, and polymorphism. The other sets describe development activities, traditional modeling concerns, or structured-analysis elements rather than core object-oriented properties.

Explanation

RUP combines iterative and incremental development with a focus on use cases and software architecture. The sequential description corresponds more closely to the Waterfall model, not RUP.

Explanation

RUP progresses through Inception, Elaboration, Construction, and Transition. The other sequences describe generic development activities rather than the official RUP phases.

Explanation

Each RUP iteration delivers a runnable increment, allowing the system to grow through repeated cycles. Documentation alone does not constitute the runnable product increment produced by an iteration.

Explanation

UML is a visual modeling language standardized by OMG, defining notation and semantics. RUP, rather than UML, is the software development process among these concepts.

Explanation

UML is built from elements, relationships, and diagrams, supported by rules and common mechanisms. Classes and objects are examples of modeling elements, not the complete set of three building-block categories.

Explanation

Structural diagrams represent relatively static aspects of a system, while behavioral diagrams represent its dynamic behavior. User goals, testing results, and deployment locations are not the defining distinction between these diagram groups.

Explanation

A class describes a set of objects that share attributes, methods, relationships, and semantics. A concrete runtime entity is an object, whereas a class serves as its template.

Explanation

A use case is a sequence of system actions that produces a result for an actor, while an actor is a user or external system interacting with the system. Treating the actor as the system behavior reverses their UML roles.

Explanation

Aggregation is a weak whole-part relationship in which the part remains independent if the whole is destroyed, while composition is a strong relationship in which the part is destroyed with the whole. The other distinctions concern inheritance, contracts, or interaction roles rather than whole-part ownership.

Explanation

The multiplicity $1..*$ means at least one instance may participate, with no stated upper limit. By contrast, $0..1$ permits zero or one, $0..*$ permits any number including zero, and $1$ means exactly one.

Explanation

UML primitive types include Integer, Boolean, String, Real, and UnlimitedNatural. Date is not a built-in primitive, while collection types and modeling elements belong to different categories.

Explanation

An enumeration is a finite set of named values, while a structured data type is compound and combines fields or other data types. Confusing these reverses their defining characteristics.

Explanation

The principal UML extension mechanisms are stereotypes, tagged values, and constraints. The other groups contain modeling concepts or artifacts rather than the three standard extension mechanisms.

Explanation

UML 2.0 defined 13 diagram types, and UML 2.2 reached 14 after adding the Profile diagram. The other choices give incorrect changes or attribute the change to the wrong event.

Explanation

Composite Structure is one of the seven structural UML diagrams. Sequence, Activity, and State Machine diagrams belong to the behavioral group.

Explanation

Interaction Overview is one of the seven behavioral UML diagrams. Deployment, Package, and Component diagrams are structural diagrams.

Explanation

Kruchten's model uses the use-case view to guide the other four views. The deployment view instead emphasizes software distribution across hardware, so it does not serve as the guiding view.

Explanation

A CASE tool supports both modeling and engineering tasks, including consistency checking, code and documentation generation, and reverse engineering. A simple drawing tool primarily provides visual diagram creation.