ITSW 2226 D284 Software Engineering

Correct Answer

D. Abstract classes are complete classes that can be used to instantiate objects.

Explanation

Abstract classes cannot be instantiated directly. They are designed to provide a base structure or behavior for other classes to extend and implement. They can include both fully implemented (concrete) methods and abstract (unimplemented) methods. Their purpose is to serve as a blueprint for subclasses rather than being used on their own.

Why other options are wrong

A. An abstract class is a class which declares the existence of some methods but not its implementation

This is true. Abstract classes can include methods that are declared without implementation, which forces subclasses to provide the method body.

B. Abstract classes are used to represent some fundamental behavior expected for all specialized classes

This is correct. Abstract classes define common functionality and structure that are shared across multiple subclasses, making code more reusable and organized.

C. All non implemented methods of an abstract class should be implemented in its subclasses

This is also correct. If a subclass does not implement all of the abstract methods of its parent abstract class, it must also be declared abstract. For a concrete subclass, all unimplemented abstract methods must be defined.

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

B. Nonfunctional tests

Explanation

Nonfunctional testing focuses on assessing aspects of the system that do not relate to specific functions, such as performance, scalability, security, and user experience. It ensures that the system can handle various conditions and stresses, testing for factors like response times and load handling, which are critical to ensuring a good user experience under different conditions.

Why other options are wrong

A. Regression tests

Regression tests focus on ensuring that new changes to the system do not break or negatively impact existing functionality. They are not concerned with the system’s performance or user experience under various conditions.

C. Acceptance tests

Acceptance testing verifies that the software meets the business requirements and is ready for deployment. It does not primarily focus on performance or nonfunctional aspects but rather on whether the system satisfies the functional needs of the user.

D. System tests

System tests validate the entire system’s functionality, ensuring that it behaves correctly under normal conditions. While system tests may include performance testing as part of their scope, nonfunctional testing specifically targets performance, load, scalability, and user experience under various stress conditions.

Correct Answer

D. It includes the application of a organized, controlled, measurable approach to the development, operation and maintenance of the software systems

Explanation

Software engineering is defined as the application of engineering principles to software development in a systematic, disciplined, and quantifiable manner. It includes processes, methods, and tools for the design, development, testing, and maintenance of software. This approach ensures software is reliable and works efficiently on real machines while meeting the client’s needs.

Why other options are wrong

A. It is the set of software applications used by engineers of different disciplines in the development process

This is incorrect because it describes software tools used by engineers, not the discipline of software engineering itself. Software engineering is not just about using software but about applying engineering practices to the creation and maintenance of software.

B. It is the process of solving customers' problems by recommending and using existing software systems according to the customer's budget and priorities

This is more aligned with IT consultancy or software procurement than with software engineering. Software engineering focuses on the creation and maintenance of software rather than selecting existing tools.

C. It is the systematic activities involved in the design, implementation, and testing of electronic hardware devices to optimize processing time and functionality

This describes hardware engineering or embedded systems development, not software engineering. Software engineering does not primarily concern itself with electronic hardware devices.

Correct Answer

A. review and reflection

Explanation

The end of each project phase or the entire project should always involve review and reflection. This process ensures that teams can evaluate what went well, what challenges occurred, and what improvements can be made in future phases or projects. It helps reinforce lessons learned, ensures accountability, and sets the stage for continuous improvement.

Why other options are wrong

B. initiation and planning for next phase or project

While planning for the next phase may occur, it typically comes after review and reflection. The planning is based on insights gained from evaluating the completed phase, so it is not the first thing that should happen.

C. testing

Testing is crucial but usually occurs before the end of a phase, particularly during the execution phase of the software development lifecycle. It is not an activity that concludes every phase or project but one that occurs during specific phases.

D. support

Support is generally an activity that follows deployment and goes into the maintenance phase. It is not part of closing every project or phase, especially in early development stages.

Correct Answer

C. The knowledge, skills, and behaviors related to guide, motivate, and direct a team.

Explanation

Leadership skills are considered the most important for a project manager. These include the ability to guide, motivate, and direct team members toward achieving project goals. Strong leadership ensures alignment, promotes collaboration, handles conflict, and drives team performance. Regardless of industry or technical knowledge, the ability to manage people effectively is critical for project success.

Why other options are wrong

A. The knowledge of, and expertise in, the industry and organization that enhance performance and better deliver business outcomes.

While industry knowledge can enhance decision-making and stakeholder communication, it is not as universally critical as leadership skills. A project manager can successfully lead a team even without deep industry expertise, especially with a strong support team of subject matter experts.

B. The knowledge, skills, and behaviors related to specific domains of the project.

Technical or domain-specific skills can be helpful but are secondary to leadership abilities. Domain knowledge supports understanding of tasks, but it doesn't replace the need to lead and align the team toward a common objective.

D. Anyone of the a, b, or c, depending on the nature of the project.

Although all skills listed are valuable, leadership is fundamental across all projects. This option dilutes the importance of leadership by suggesting it's not always needed, which is incorrect in the context of project management essentials.

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. Identify gaps in requirements

Explanation

At the end of the requirements analysis phase, a review session is conducted to ensure that all requirements have been identified, understood, and documented accurately. One of the primary objectives is to identify any gaps or missing information in the requirements. This review ensures that no crucial aspects have been overlooked and that all stakeholders' needs have been considered, reducing the risk of scope changes or project delays later on.

Why other options are wrong

B. Develop the user interface

The user interface development typically occurs later in the project, after the requirements phase is completed and the system design begins. While requirements might inform the user interface design, the review session is focused on ensuring that all requirements are captured accurately, not on developing specific features like the UI.

C. Create the final codebase

Creating the final codebase happens after the design and development phases, not during the requirements analysis phase. The review session is aimed at ensuring that the requirements are comprehensive and feasible, not at developing or writing code, which comes later in the project lifecycle.

D. Establish the deployment schedule

The deployment schedule is typically established during the planning or implementation phases, not during the requirements analysis phase. The review session is more concerned with validating that the requirem

Correct Answer

D. Structure

Explanation

Structure refers to the way data is organized and formatted, such as whether it’s structured (like rows and columns in a database), semi-structured (like JSON or XML), or unstructured (like free-form text). Understanding the structure of data is critical for designing how the application stores, accesses, and processes the information.

Why other options are wrong

A. Format

Format refers more to the representation of data (e.g., CSV, XML, binary), not the organizational structure. While format impacts storage and transmission, it does not capture the deeper organizational aspects that "structure" implies in application requirements.

B. Volume

Volume relates to the quantity of data and is associated with considerations around scalability, storage capacity, and processing performance. It does not address how data is organized.

C. Importance

Importance relates to data prioritization or criticality, such as whether certain data is mission-critical or optional. It has more to do with how the system prioritizes processing or protects data, not how it’s structured or formatted.