Question 1

Actual techniques and approaches that analysts and developers use have remained largely unchanged over time.

Accepted Answer

The techniques and approaches used by analysts and developers have evolved and changed over time with advancements in technology and best practices.

Question 2

As systems analysts have worked with projects and the Systems Development Life Cycle for many years,they have found that about 35% of all projects do not require analysts to model the business needs and to gather business requirements.

Accepted Answer

Systems analysts have found that it is essential to model the business needs and gather business requirements for all projects, regardless of their size or complexity. Not doing so may lead to project failure or a final product that does not meet the needs of the business or end-users.

Question 3

A class is the general template we use to define and create specific instances (or objects)in the object-oriented approach.

Accepted Answer

This is the definition of a class in object-oriented programming.

Question 4

A method of simplifying complex class diagrams is to use a(n):

Accepted Answer

Using a view is the best choice to simplify a complex class diagram. A view is a subset of the entire class diagram that shows only the relevant classes and their relationships. It allows for a clearer and more focused understanding of the system being modeled.

Question 5

The 'actor' in an UML use case diagrams:

Accepted Answer

An actor in a UML use case diagram is similar to an external entity on a DFD, in that both represent an external agent that interacts with the system being modeled. The actor can be a person, another system, or even time. The actor initiates a use case by triggering a sequence of events within the system.

Question 6

Considering all the possible UML diagrams,which of the following IS NOT a valid UML 2.0 diagram?

Accepted Answer

Aggregate is not a UML diagram type; it is a concept used in UML to describe a relationship between classes.

Question 7

Which is NOT a normal part of the UML Use Case Diagram?

Accepted Answer

Class is not a normal part of the UML Use Case Diagram. The other four options (Actor, Specialized Actor, Use Case, and System Boundary) are all typical components of a use case diagram.

Question 8

A(n)___________ illustrates the objects that participate in a use case and the messages that pass between them over time for one use case.

Accepted Answer

A Sequence Diagram illustrates the interactions between objects over time for a specific use case. It shows the messages that are exchanged between the objects, as well as their sequence and timing. This makes it a useful tool for visualizing the behavior of a system and identifying potential problems or areas for improvement.

Question 9

One of the enabling technologies for the object-orientation approaches was that processors increased in power and speed as well as were less expensive (aka "Moore's Law").

Accepted Answer

This statement is true. The increase in processor power and speed as well as the decrease in cost were key factors in enabling the development of object-oriented approaches. This phenomenon is often referred to as Moore's Law, named after Gordon Moore, one of the founders of Intel Corporation.

Question 10

The main building block of the UML class diagram is the class which _____________.

Accepted Answer

The answer of The main building block of the UML...

Question 11

Which is NOT a term associated with the UML class diagram?

Accepted Answer

"Open attribute" is not a term commonly associated with UML class diagrams. The other four options are all types of attributes that can be used to describe the properties of a class in a UML diagram.

Question 12

Dave is working on an object-oriented system.He has created an abstract class called 'person'.'Student' might be an object of the class 'person'.

Accepted Answer

Yes, 'Student' can be considered as an object of the abstract class 'person' since it is a specific type of person.

Question 13

In UML Class Diagrams,'generalizations'

Accepted Answer

Generalizations in UML Class Diagrams show that one class (subclass) inherits from another class (superclass). They are illustrated with a solid line with a hollow arrowhead pointing from the subclass to the superclass. Option A is incorrect because double dashed lines are used to represent dependencies between classes. Option C is incorrect because extending use cases through normalization is a process used in use case modeling, not in UML class modeling. Option D is incorrect because actors in UML class diagrams are represented as stick figures with the name of the actor next to it.

Question 14

The Object-Oriented Approach is considered as an 'exciting enhancement to systems analysis and design'.

Accepted Answer

The Object-Oriented Approach is a widely adopted methodology in systems analysis and design, known for its ability to improve software design and maintenance. Its popularity can be attributed to its ability to handle complex software and make code modular and reusable.

Question 15

UML stands for "Unified Modeling Language".

Accepted Answer

UML stands for Unified Modeling Language, which is a standardized visual language used for modeling software systems.

Question 16

UML Use Cases are connected to actors through:

Accepted Answer

UML Use Cases are connected to actors through association relationships in order to show the interactions between the actor and the system. Data flows are typically used in data flow diagrams, and protected attributes and bimodal accesses are not relevant to connecting use cases to actors. "External affairs" is not a commonly used term in UML.

Question 17

Fortunately,in learning object-oriented approaches to developing information systems,there is little new terminology and the approaches are very similar to what has been done with structured development approaches over the years.

Accepted Answer

Object-oriented approaches introduce new terminology and concepts, such as classes, objects, inheritance, and polymorphism, which differ from structured development approaches.

Question 18

An object is an attribute of an instantiation.

Accepted Answer

An instantiation is an instance of an object, meaning the object is the template or class, and the instantiation is the specific instance created from that class or template, not an attribute.

Question 19

Object-Oriented systems focus on capturing the structure and behavior of the information system in little modules (known as objects)that encompass both data and processes.

Accepted Answer

This statement is true. Object-oriented systems use objects, which are modules that contain both data and the processes that manipulate that data. This approach helps to organize and encapsulate the system's structure and behavior.

Question 20

The two main items in a UML use case diagram are:

Accepted Answer

The two main items in a UML use case diagram are actors and use cases. Actors are the external entities that interact with the system, and use cases are the specific actions or behaviors that the system performs in response to the actors' interactions. Entity and attribute, data flow and data store, database and table, principals and students are not the main items in a UML use case diagram.

Quiz 14: the Movement to Objects