ITSW 2226 D284 Software Engineering

Correct Answer

A. Software requirement specification

Explanation

After collecting the requirements from stakeholders, the system analyst creates the Software Requirements Specification (SRS) document. This document details the software’s functional and non-functional requirements, providing a clear and concise description of what the software should do. The SRS serves as a blueprint for the design, development, and testing phases.

Why other options are wrong

B. Software requirement validation

This is incorrect because requirement validation is the process of ensuring the gathered requirements are complete, accurate, and feasible. It is not the document created after gathering requirements, but a task that may be part of the requirements analysis phase.

C. Feasibility study

This is incorrect because the feasibility study was conducted earlier in the project to assess whether the project is viable in terms of resources, time, and technology. It is not created after requirements collection.

D. Requirement Gathering

This is incorrect because requirement gathering is the process of collecting the requirements from stakeholders, not the document. After gathering the requirements, a formal document like the Software Requirements Specification (SRS) is created.

Correct Answer

A. It provides a structured approach to software development.

Explanation

The Software Development Life Cycle (SDLC) is a systematic process for building software that ensures quality and efficiency. One of its key benefits is that it provides a structured approach, guiding the development through distinct phases such as planning, design, coding, testing, and maintenance. This structure helps ensure that all aspects of the software are addressed, reducing the risk of overlooking important details.

Why other options are wrong

B. It eliminates the need for user feedback during development

This is incorrect because user feedback is essential throughout the development process, especially during iterative phases such as design and testing, to ensure the product meets user requirements.

C. It focuses solely on coding and implementation

This is incorrect because the SDLC covers more than just coding. It includes planning, analysis, design, testing, and maintenance, ensuring that all stages of development are properly addressed.

D. It guarantees that all software projects will be completed on time

This is incorrect because while SDLC helps structure the process, it does not guarantee that a project will be completed on time. Delays can still occur due to various factors such as scope changes, resource constraints, or unforeseen challenges.

Correct Answer

D. Accessing a global variable directly inside a function (without passing it as a parameter)

Explanation

Accessing a global variable directly inside a function can cause unexpected side effects because it introduces hidden dependencies that make the function harder to test, understand, and maintain. Global variables can be modified by other parts of the program, potentially leading to unanticipated changes in the function’s behavior.

Why other options are wrong

A. Assigning to a call by value formal parameter inside the body of a function

Assigning to a call by value formal parameter does not affect the calling function’s environment, since only a copy of the argument is passed to the function. Therefore, there is no risk of side effects in this case.

B. Changing the values of local variables inside a function

Changing the values of local variables inside a function is completely acceptable and expected in most cases. Local variables are isolated to their function scope, so modifying them doesn’t cause unexpected side effects.

C. Accessing a global constant directly inside a function (without passing it as a parameter)

Accessing a global constant is not inherently problematic because constants cannot be modified. However, it's still better practice to pass constants as parameters when necessary, as it improves clarity and modularity, though it doesn't typically lead to side effects.

Correct Answer

C. Enroll Student

Explanation

A good use case name should describe an action or a task that the user performs. "Enroll Student" clearly describes the action of enrolling a student, making it a suitable and clear name for a use case. It follows a common convention of naming use cases with a verb-noun combination that conveys the specific task the system is designed to handle.

Why other options are wrong

A. enrollStudent()

This is a method-style naming convention, typically used for function or method names in code, not a use case. Use cases should have names that are descriptive of the actions a user takes, not code-related.

B. Enrollment

"Enrollment" is a noun and doesn't represent a specific action. A use case name should focus on what the user does (i.e., an action), such as "Enroll Student."

D. Student Enrollment

While this option could work, it sounds more like a system or feature name rather than an action. Use cases should focus more on the verb describing the user action.

E. Student

"Student" is a noun and represents an entity, not an action. A use case name should describe what the user does, not just the objects or entities involved in the system.

Correct Answer

D. Sensitivity analysis and simulation

Explanation

Sensitivity analysis and simulation are techniques primarily used for risk management, financial modeling, and scenario planning rather than for gathering requirements. These methods focus on understanding how different variables impact a system’s behavior and are typically used later in the project to test hypotheses or assess risks. They are not directly associated with gathering initial project requirements, which focus more on understanding the needs of stakeholders and documenting the necessary system functionality and features.

Why other options are wrong

A. Expert judgment, brainstorming, interviews, focus groups, questionnaires, and surveys

These techniques are widely used during the requirements-gathering phase. They involve directly engaging with stakeholders to capture their needs, opinions, and expectations for the project. These methods are fundamental to understanding what is required from both a technical and business perspective.

B. Voting, autocratic decision making, multi-criteria decision analysis, and nominal group technique

These techniques are used to facilitate decision-making processes once requirements have been gathered. They help prioritize and refine requirements when there are competing interests or when it's necessary to make group decisions. These are still relevant during the requirements phase, but they are more focused on managing group dynamics and consensus-building.

C. Affinity diagrams and mind mapping

These are creative techniques that help organize ideas, information, and requirements visually. Affinity diagrams are often used to sort and categorize large amounts of data, while mind mapping helps to visualize relationships between various ideas and concepts. Both are excellent for gathering, organizing, and refining requirements in the early stages of a project

Correct Answer

D. Managing Complexity, Managing Personnel Resources, Managing Time and Money and Producing Useful Products

Explanation

The core of software engineering is to manage complexity and deliver useful software products within constraints. This involves organizing people and processes, using resources efficiently, and applying engineering principles to develop high-quality software. Effective management of complexity, people, time, and budget ensures the delivery of software that meets user needs and expectations.

Why other options are wrong

A. Requirements Definition, Design Representation, Knowledge Capture and Quality Factors

While these are important components of software engineering, they do not fully capture the broader essence of the discipline, particularly the emphasis on resource and complexity management.

B. Maintaining Configurations, Organizing Teams, Channeling Creativity and Planning Resource Use

This option includes useful activities, but it lacks a focus on the ultimate goal—producing useful software—and does not mention managing complexity, which is central to software engineering.

C. Time/Space Trade-offs, Optimizing Process, Minimizing Communication and Problem Decomposition

This is incorrect because minimizing communication is counterproductive. Effective communication is critical in software projects. Additionally, this option overemphasizes low-level optimizations, which are not the essence of software engineering.

E. Maintaining Communication, managing un-useful products and not optimizing processes

This is clearly incorrect as it includes negative and incorrect statements. Managing "un-useful products" and "not optimizing processes" contradicts the goals of software engineering.

Correct Answer

A. Ease of data capture

Explanation

When determining whether data are appropriate for use, dimensions such as timeliness, source, and suitability for producing reliable results are critical. These factors ensure that the data is not only accurate and relevant but also applicable for generating meaningful insights. While ease of data capture is important for logistical purposes, it is not a primary dimension for determining whether data is appropriate for analysis.

Why other options are wrong

B. Timeliness of data

This is incorrect because timeliness refers to how up-to-date the data is, which directly impacts its relevance and usefulness. Data that is outdated may not be suitable for certain analyses.

C. Source of data

This is incorrect because the source of the data is an essential dimension in determining data appropriateness. The credibility and reliability of the data source impact the accuracy and validity of the data.

D. Suitability of data to produce a reliable result

This is incorrect because the suitability of data refers to whether the data is fit for the intended purpose. If the data cannot reliably support decision-making or analysis, it is considered inappropriate.

Correct Answer

B. Deploy a load testing tool that can simulate multiple concurrent users

Explanation

The most effective way to simulate high user demand during load testing is by using a load testing tool that can simulate multiple concurrent users. These tools are designed to simulate real-world traffic, generating a large number of virtual users to interact with the system, helping to identify performance bottlenecks and scalability issues. This allows testing under conditions that closely match actual usage scenarios.

Why other options are wrong

A. Use a single powerful machine to run the tests

While using a powerful machine might offer some capacity to run tests, it does not replicate the actual high load of concurrent users. The testing would not accurately simulate how the system behaves when many users are interacting simultaneously.

C. Conduct tests during off-peak hours with a limited number of users

Testing during off-peak hours with a limited number of users is not effective for simulating high traffic. It would not provide insight into how the system behaves under heavy demand, as the load would not be representative of peak user activity.

D. Rely on user feedback to gauge system performance

While user feedback is valuable for identifying problems, it is not a sufficient method for testing performance under load. Feedback is subjective and may not provide the detailed metrics necessary to assess the system’s behavior under high traffic.

Correct Answer

B. Constructor, Destructor, Accessor, Mutator

Explanation

In object-oriented programming, a class can provide four main categories of operations:

1. Constructor: Initializes a new object of the class.

2, Destructor: Cleans up when an object is destroyed.

3. Accessor: Retrieves data from an object without modifying it (also known as getters).

4. Mutator: Modifies the object’s state (also known as setters).

These operations define the behavior of class instances and manage their lifecycle and data.

Why other options are wrong

A. Terminator, Destructor, Accessor, Mutalor

This is incorrect because "Terminator" and "Mutalor" are not standard terms in software engineering. The correct terms are "Constructor" and "Mutator".

C. Constructor, Destructor, Terminator, Mutator

This is incorrect because "Terminator" is not a recognized category of class operations in object-oriented programming.

D. Constructor, Termination, Accessor, Mutator

This is incorrect because "Termination" is not a valid term used in this context. The correct term for cleaning up an object is "Destructor".