ITSS 4330 Exam 2 | UPDATED Questions with 100%
Verified Answers
Q1: Object-Oriented Approach
A: Views a system as a collection of self-contained objects, including both data and
processes
Q2: Object-Oriented Systems
A: Focus on capturing information systems' structure and behavior in modules [objects] that
encompass both data and processes
Q3: Object
A: A person, place, or thing about which we want to capture information
Perceived as an entity and referredd to by name
Perceptible by at least one of the senses
Intelligible or perceptible by the mind.
Q4: Class
A: The general template used to define and create specific instances.
Q5: Class vs. Objects - Differences
A: An object is an instance [instantiation] of a class
Every object is associated with a class.
Q6: Instance
A: A concrete manifestation of a class.
Q7: Attributes
A: Features, properties, qualities, or characteristics that are associated with an object
Usually paired with qualitfying/quantifying values
Name Value Pair [Name = Value]
Q8: Domain of an Attribute [Attribute's Domain]
A: The range of values that can be assigned to an attribute
Q9: Operation
A: What an object does or is capable of doing
Q10: Mesages
A: Information sent to objects to invoke behaviors
, Q11: Behaviors
A: Specify what an object can do
Q12: Method
A: An action that an object can perform
Q13: Message
A: Information sent to an objject in order to trigger methods.
Q14: Encapsulation
A: The combination of process and data into a single entity
Q15: Information Hiding
A: The practice of hiding the details of a module with the goal of controlling access to the
details of the module
Q16: Inheritance
A: A relationship in which common sets of attributes and methods are organized into a
hierarchy - where subclasses take attributes from certain superclasses.
Q17: Concrete Class
A: A class that allows individual objects or instances to exist
An class that has instances
Q18: Abstract Classes
A: A class that cannot be instantiated (can't use new on it). It can only be extended and is
used to define base classes.
Q19: Polymorphism
A: The same message can be interpreted differently by different classes of objects
Made possible due to Dynamic Binding
Q20: Dynamic Binding
A: A technique that delays typing the object until run-time
Q21: Static Binding
A: The type of object is determined at compile-time
Q22: Use-Case Driven Approach
A: Use cases are the primary modeling tools defining the system's behaviors
Verified Answers
Q1: Object-Oriented Approach
A: Views a system as a collection of self-contained objects, including both data and
processes
Q2: Object-Oriented Systems
A: Focus on capturing information systems' structure and behavior in modules [objects] that
encompass both data and processes
Q3: Object
A: A person, place, or thing about which we want to capture information
Perceived as an entity and referredd to by name
Perceptible by at least one of the senses
Intelligible or perceptible by the mind.
Q4: Class
A: The general template used to define and create specific instances.
Q5: Class vs. Objects - Differences
A: An object is an instance [instantiation] of a class
Every object is associated with a class.
Q6: Instance
A: A concrete manifestation of a class.
Q7: Attributes
A: Features, properties, qualities, or characteristics that are associated with an object
Usually paired with qualitfying/quantifying values
Name Value Pair [Name = Value]
Q8: Domain of an Attribute [Attribute's Domain]
A: The range of values that can be assigned to an attribute
Q9: Operation
A: What an object does or is capable of doing
Q10: Mesages
A: Information sent to objects to invoke behaviors
, Q11: Behaviors
A: Specify what an object can do
Q12: Method
A: An action that an object can perform
Q13: Message
A: Information sent to an objject in order to trigger methods.
Q14: Encapsulation
A: The combination of process and data into a single entity
Q15: Information Hiding
A: The practice of hiding the details of a module with the goal of controlling access to the
details of the module
Q16: Inheritance
A: A relationship in which common sets of attributes and methods are organized into a
hierarchy - where subclasses take attributes from certain superclasses.
Q17: Concrete Class
A: A class that allows individual objects or instances to exist
An class that has instances
Q18: Abstract Classes
A: A class that cannot be instantiated (can't use new on it). It can only be extended and is
used to define base classes.
Q19: Polymorphism
A: The same message can be interpreted differently by different classes of objects
Made possible due to Dynamic Binding
Q20: Dynamic Binding
A: A technique that delays typing the object until run-time
Q21: Static Binding
A: The type of object is determined at compile-time
Q22: Use-Case Driven Approach
A: Use cases are the primary modeling tools defining the system's behaviors
