ITSW 2226 D284 Software Engineering

Correct Answer

A. The official document that defines the requirements that should be implemented by the system developers

Explanation

The software requirements document, often called the Software Requirements Specification (SRS), formally outlines the complete set of functional and non-functional requirements that the developers must implement. It serves as a bridge between users' needs and the development team's tasks, offering clarity and agreement on what the system must do.

Why other options are wrong

B. The official document that defines the requirements that is written for the customer

This is incorrect because while customers may review the requirements document, it is primarily written for the development team. Documents specifically written for customers are often in less technical language, such as requirement summaries or business requirement documents.

C. The official document that defines the requirements that come from the application domain of the system

This is incorrect as it only describes one potential source of requirements. The software requirements document includes all system requirements, regardless of source — not just those from the application domain.

Correct Answer

A. Make appointment

Explanation

A use case should describe an action or a process that provides a specific outcome or interaction from the perspective of the user or system. "Make appointment" is an appropriate name for a use case because it focuses on the action that the user performs to achieve a goal. Use cases typically describe the steps taken to complete a task, such as making an appointment, rather than just naming objects or entities.

Why other options are wrong

B. Appointment

"Appointment" is a noun and does not describe an action or a process. A use case should focus on what the user does, not just the object involved.

C. Doctor

"Doctor" is a noun and represents an entity or role, not an action. Use cases should focus on actions rather than naming people or objects.

D. Patient

"Patient" is similarly a noun, and it does not describe a user action. Use cases should focus on actions that can be performed, not simply entities involved in the system.

Correct Answer

C. Scalability

Explanation

Scalability is an important aspect of software performance, but it is typically considered a quality attribute or design goal rather than a core software characteristic. The core software characteristics are typically things like reliability, usability, and maintainability. These attributes describe the quality and functionality of the software from the user's and developer's perspectives.

Why other options are wrong

A. Reliability

Reliability is a key characteristic of software, referring to how well the software performs its functions without failure over time. It is crucial for ensuring the software works correctly under normal and extreme conditions.

B. Usability

Usability refers to how user-friendly and accessible the software is to its intended users. It is a core characteristic of software, focusing on the experience of the user when interacting with the system.

D. Maintainability

Maintainability is another important software characteristic, focusing on how easily the software can be updated, modified, or repaired over time. It ensures that the software can be improved or fixed as new requirements or issues arise.

Correct Answer

C. Reporting project metrics

Explanation

The primary responsibility of a project manager when assessing progress and communicating updates is to track and report key project metrics. This includes providing information on the project’s schedule, budget, scope, and overall health. Regular updates are essential for stakeholders to understand how the project is progressing and whether any adjustments or interventions are needed. Project metrics give stakeholders clear insights into the project's status.

Why other options are wrong

A. Coordinating team meetings

While coordinating team meetings is an important task for a project manager, it is not their primary responsibility when assessing and communicating project progress. Meetings are one tool to support progress tracking, but reporting metrics is the key responsibility.

B. Evaluating project risks

Evaluating risks is a part of the project manager's role, but when assessing progress and communicating updates, the focus is on reporting project metrics. Risk evaluation is a continuous activity that may be incorporated into the update, but it is not the primary responsibility when communicating progress.

D. Assigning project tasks

Assigning tasks is an important part of project management, but it is not the primary responsibility when assessing the overall progress of the project. The project manager needs to report on the project's status through metrics, not just assign tasks.

Correct Answer

A. When the project has evolving requirements that may change during development

Explanation

The iterative development process is ideal when requirements are expected to evolve over time or when the full scope of the project is not clearly defined at the start. This approach allows for flexibility and adjustments based on feedback and changing needs, with repeated cycles of development, testing, and evaluation.

Why other options are wrong

B. When the project scope is fixed and well understood from the start

The sequential (or "waterfall") model is more suitable for projects with a fixed and well-understood scope. In these cases, the requirements are clear, and the project can proceed in a linear manner.

C. When the project requires extensive documentation before any development begins

This scenario aligns with the sequential life cycle, as it involves planning and documentation upfront before development begins. Iterative processes generally focus more on delivering incremental results rather than extensive documentation.

D. When all system components must be developed and delivered at once

The iterative approach involves delivering smaller parts of the system over multiple iterations, rather than waiting to deliver everything at once. A sequential process would be preferred when the system needs to be developed and delivered in one final release.

Correct Answer

C. MyClass

Explanation

In Java, class names should follow the CamelCase convention, where the first letter of each word is capitalized, and no underscores are used. MyClass adheres to this naming convention and is a valid class name. Math2 is valid as well, but it's better to use descriptive names rather than numbers in class names. System is a reserved keyword in Java, and Phone_User violates the convention due to the underscore.

Why other options are wrong

A. Phone_User

This is incorrect because class names should not contain underscores. Java uses CamelCase for class naming, so this would not be considered a proper class name by convention.

B. System

This is incorrect because System is a predefined class in Java (java.lang.System), and using it as a class name would cause conflicts and errors in the program.

D. Math2

While this name is technically valid, it is not ideal by convention because class names should be descriptive and should avoid including numbers unless necessary. Using more descriptive names without numbers is generally preferred for readability and maintainability.

Correct Answer

A. Providing a clear understanding of what is expected

Explanation

The project manager's primary responsibility is to ensure that the project team understands what is expected in terms of specific results. This involves setting clear objectives, defining project goals, and ensuring alignment with the project's requirements. A clear understanding of expectations helps the team stay focused and deliver on time and within scope.

Why other options are wrong

B. Telling project team members how to perform

This is incorrect because the project manager should not micromanage how team members perform their tasks. Instead, the manager should focus on setting goals, providing resources, and enabling the team to perform effectively while allowing them the autonomy to execute the tasks.

C. Detailing the specific actions

This is incorrect because while the project manager provides guidance, it is the responsibility of the team members to execute the specific actions based on the tasks outlined. The project manager sets the broader objectives but does not get involved in every minute detail.

D. Limiting the actions of the project team

This is incorrect because while the project manager ensures that work is aligned with the project goals, they should not unnecessarily limit team members' actions. Empowering the team to make decisions and take initiative is crucial for fostering creativity and efficiency.

Correct Answer

A. Minimize the use of global variables

Explanation

Minimizing the use of global variables is essential for optimizing memory usage because global variables stay in memory for the life of the application. Excessive use can lead to unnecessary memory consumption and reduced flexibility. Keeping variables local to functions or blocks ensures better memory management and scope control, improving performance and maintainability.

Why other options are wrong

B. Use recursion for all functions

While recursion is a useful technique, using it for all functions is not memory-efficient. Recursive calls add layers to the call stack, which can cause stack overflow or excessive memory use, especially for deep recursions.

C. Rely heavily on dynamic memory allocation

Dynamic memory allocation gives flexibility but must be used cautiously. Overusing it without proper deallocation (freeing memory) can lead to memory leaks and inefficient memory use, reducing performance over time.

D. Store all data in static arrays

Using static arrays means the memory is allocated at compile time and cannot be adjusted during execution. This can lead to wasted memory (if arrays are oversized) or runtime issues (if undersized). It lacks the flexibility required for optimal memory use in many dynamic scenarios.

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.