ITSW 2226 D284 Software Engineering

Correct Answer

A. Users of the software

Explanation

Users of the software are typically considered one of the most important stakeholders because they are the ones who will interact with the system and rely on it to meet their needs. Their feedback and satisfaction are crucial for determining the success of the software. Understanding their requirements, addressing their concerns, and ensuring the system meets their expectations is vital for the software's effectiveness and usability.

Why other options are wrong

B. Middle level stakeholders

While middle-level stakeholders play an important role in the decision-making process and project execution, they are not directly engaged with the use of the software. The users' perspectives and needs are typically more critical for ensuring the software's success.

C. Managers

Managers are important in overseeing the project and ensuring it stays on track, but they do not always interact directly with the software. Their role is more focused on project management, resource allocation, and strategy.

D. Entry level personnel

Entry-level personnel may be involved in the project, but they do not usually have as much influence on the requirements or usage of the software. Their feedback is valuable, but the users' input generally carries more weight in determining software success.

Correct Answer

A. SRS - Software requirement specification

Explanation

The Software Requirement Specification (SRS) document provides a complete, consistent, and correct set of requirements from the developer's perspective. It details what the software system should do and acts as a guide for design, development, and testing. An SRS ensures that both stakeholders and developers have a shared understanding of the expected system behavior.

Why other options are wrong

B. DDD - Detail Design Document

This document focuses on the technical implementation details of the software system, including class diagrams, interfaces, and logic. It is created after the requirements have been established and does not contain the original set of requirements from the developer’s viewpoint.

C. URD - User Requirement Definition

The URD captures the requirements from the users' perspective and focuses on what the users expect the software to do. It lacks the technical specificity and completeness expected from a developer’s perspective, which is provided by the SRS.

D. ADD - Architecture Design Document

The ADD describes the software’s overall structure and how the system components interact. It is concerned with system architecture and high-level design rather than the detailed and validated list of requirements that define software behavior

Correct Answer

A. Functionality, reliability, performance, and security

Explanation

These four attributes are commonly recognized as core quality factors for software products. Functionality measures whether the software provides the intended features. Reliability refers to its consistency and stability. Performance gauges responsiveness and efficiency, while security ensures protection against threats and vulnerabilities.

Why other options are wrong

B. Necessity, certainty, flexibility, and testability

These are not standard software quality metrics. While flexibility and testability can influence quality, necessity and certainty are vague and not generally used for quality evaluation.

C. Complexity, size, speed, and cost

These may affect software development but are not direct indicators of software quality. Complexity and size can even be negative attributes if not managed well, and cost is a business factor, not a quality attribute.

D. Number of GUIs, database independence, bandwidth, and size

These are technical characteristics or implementation details, not core quality attributes. They may influence certain quality aspects, but they are not the primary metrics for evaluating software quality.

Correct Answer

B. Checking Cart such as name, quantity, price, and total price of products which customer has been selected.

Explanation

Functional testing focuses on checking the system’s functionality to ensure it behaves according to requirements. Option B is a functional test because it checks the functionality of the shopping cart, such as the accuracy of the product name, quantity, price, and total price, which directly relate to the core functions of the system. This verifies that the system performs as expected in the context of a typical user operation.

Why other options are wrong

A. Checking the quality attributes of the system including reliability and usability.

This option is incorrect because it refers to non-functional testing. Non-functional tests focus on attributes such as reliability, usability, performance, and scalability. These tests do not assess whether the system performs specific functions as expected, which is the focus of functional testing.

C. Measuring response time on an online booking system.

This is incorrect as response time measurement is a performance test, which is classified as non-functional testing. It deals with how well the system performs under certain conditions, like the speed of completing tasks, rather than testing the system's functional features.

D. Checking how easy the system is to use.

This option refers to usability testing, which evaluates the user-friendliness of the system. Usability testing is not functional testing as it assesses the user experience rather than verifying the system's core functions.

Correct Answer

D. B & C

Explanation

The Unified Process (UP) is an iterative and incremental software development process framework. It divides the project into a series of iterations where the activities are executed and refined in each iteration, allowing for feedback and adjustments as the project progresses. This flexibility allows it to adapt to changes in requirements and technology. While it is prescriptive in the sense that it defines roles, workflows, and artifacts, it does not strictly mandate that each phase be executed only once or in a specific order, as the process is designed to be iterative.

Why other options are wrong

A. It mandates that each phase be executed in a specific order and only once.

This statement is incorrect because the Unified Process is not a linear, sequential process. Instead, it is iterative, where each phase (e.g., requirements, design, implementation) is revisited and refined over multiple iterations.

B. It is a prescriptive process.

While the Unified Process is prescriptive in providing guidelines for roles and workflows, it is not a rigid process like the waterfall model. It allows for flexibility through its iterative approach, which contradicts the idea that it mandates a single execution order.

C. It is a process that divides the project into a number of iterations and executes its activities during each iteration.

This is true, but it is not the full picture. The correct answer is D because the Unified Process is both prescriptive (B) and iterative (C).

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

D. All of the above

Explanation

In a problem space, candidate objects refer to potential entities or concepts that can be modeled as objects in an object-oriented design. These can include events (things that happen or occur), people (entities interacting with the system), and structures (physical or logical entities that make up the system or environment). All of these are valid candidates for modeling within the problem space.

Why other options are wrong

A. Events

Events are indeed a valid candidate object but are just one part of the broader range of possible candidates. Thus, this answer alone is incomplete without considering other types of objects such as people or structures.

B. People

People are also important candidates as they can represent users or stakeholders interacting with the system. However, by themselves, people are not the only candidates for the problem space.

C. Structures

Structures are also potential candidate objects in a problem space. But like events and people, they should not be considered in isolation when defining the full set of candidate objects in the problem space.

Correct Answer

A. Using appropriate theories and methods to solve problems bearing in mind organizational and financial constraints

Explanation

Software engineering is primarily concerned with applying engineering principles, methods, and best practices to the software development process. This includes considering the organizational, technical, and financial constraints while designing and developing software solutions. It involves using a mix of appropriate theories and methodologies to solve problems and create efficient, scalable, and reliable software.

Why other options are wrong

B. Using appropriate programming languages to solve problems bearing in mind organizational and financial constraints

While programming languages are essential tools in software development, software engineering is not just about using languages. It encompasses a broader scope that includes the application of engineering principles, methodologies, and managing various constraints to achieve high-quality software.

C. Using appropriate tools to program to solve problems bearing in mind organizational and financial constraints

While tools are important for programming and development, software engineering goes beyond just tool selection. It involves strategic planning, requirements analysis, design, and system management to ensure that the developed software meets the desired quality and performance standards within given constraints.

Correct Answer

D. A software development methodology

Explanation

The Systems Development Life Cycle (SDLC) is a structured approach used for developing software systems. It outlines a series of clearly defined phases including planning, analysis, design, implementation, testing, deployment, and maintenance. Its primary purpose is to ensure the production of high-quality software that meets or exceeds customer expectations, reaches completion within time and cost estimates, and functions effectively and efficiently in the current and planned IT infrastructure.

Why other options are wrong

A. A project management framework

This is incorrect because while SDLC involves elements of planning and coordination, it is not primarily a project management framework. Project management frameworks like PMBOK or PRINCE2 focus more broadly on managing scope, time, cost, and quality across various types of projects.

B. A model for project phases

This is too vague. Although the SDLC does involve project phases, it is more specifically defined as a methodology for software development with particular activities and deliverables in each phase.

C. A type of virtual team

This is entirely incorrect. The SDLC has nothing to do with the composition or structure of teams but rather focuses on the process of software development.