Which description best captures Object-oriented programming?

Which description best captures Object-oriented programming?

• A. A programming approach that models data with objects and classes.
• B. Designing a program by discovering objects, their properties, and their relationships.
• C. Writing code that describes exact computer steps.
• D. Creating programs solely with functions.

Answer: (B)

Object-oriented programming centers on designing software by identifying the things that matter in the domain and modeling them as objects with their own data and behavior. The best description captures this design process: you discover the objects the system will use, define their properties, and map out how these objects relate and collaborate with each other. This approach starts from real-world concepts and translates them into a network of interacting objects, each encapsulating data and the operations that act on that data. For example, in a library system you’d identify objects like Book, Member, and Loan, specify properties such as a book’s title or a member’s name, and describe relationships like a Loan linking a Member to a Book. This emphasis on identifying objects, their attributes, and their relationships is what makes this description the most accurate reflection of object-oriented design. Other options point to different styles: modeling data with objects and classes hints at OOP but doesn’t highlight the design process of discovering and connecting objects; describing exact computer steps aligns with imperative programming; and creating programs solely with functions points to functional programming.

Object-oriented programming centers on designing software by identifying the things that matter in the domain and modeling them as objects with their own data and behavior. The best description captures this design process: you discover the objects the system will use, define their properties, and map out how these objects relate and collaborate with each other. This approach starts from real-world concepts and translates them into a network of interacting objects, each encapsulating data and the operations that act on that data.

For example, in a library system you’d identify objects like Book, Member, and Loan, specify properties such as a book’s title or a member’s name, and describe relationships like a Loan linking a Member to a Book. This emphasis on identifying objects, their attributes, and their relationships is what makes this description the most accurate reflection of object-oriented design.

Other options point to different styles: modeling data with objects and classes hints at OOP but doesn’t highlight the design process of discovering and connecting objects; describing exact computer steps aligns with imperative programming; and creating programs solely with functions points to functional programming.