ITSW 2226 D284 Software Engineering

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. 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

D. Question and answer sessions are held with individual stakeholders

Explanation

Interviews involve direct interactions, usually between a requirements analyst and a single stakeholder. These Q&A sessions allow for detailed probing, follow-up questions, and the opportunity to uncover unstated or implied requirements. This technique is ideal for clarifying stakeholder expectations in depth.

Why other options are wrong

A. Survey questions are sent out and respondents fill them out on their own time

This is incorrect because it describes surveys, not interviews. Surveys are self-administered and lack the interactive nature of interviews.

B. Multiple users participate in a moderated discussion setting

This is incorrect because it describes focus groups. Interviews are typically one-on-one sessions rather than group discussions.

C. Stakeholders are only allowed to provide written feedback

This is incorrect because interviews encourage verbal interaction. Limiting stakeholders to written responses removes the opportunity for real-time clarification and dialogue.

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. 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. Design of test cases that verify that user functions are correct.

Explanation

Test Analysis and Design is a phase where requirements and functional specifications are examined to design test cases that validate user-facing functionality. This ensures that the software meets user needs and behaves correctly under various conditions. The focus is on translating requirements into meaningful and executable test cases.

Why other options are wrong

B. The design of test cases for testing the internal structure of the system

This activity belongs more to white-box testing or structural testing, which involves knowledge of internal code. It’s typically not part of the standard Test Analysis and Design phase, which is more functionally oriented.

C. Test case design that is based on an analysis of the behavior of the component without reference to its internal workings

This describes black-box testing. While it may overlap with Test Analysis, this description is too specific and does not represent the broader scope of designing test cases for all user functions.

D. The design of test cases to ensure that the organization has defined exactly what the customer wants

This is related more to requirements validation or business analysis than to the actual test design phase. Ensuring the requirements are correctly defined is a prior step before designing tests.

Correct Answer

A. It encourages diverse perspectives from participants

Explanation

Focus groups are designed to bring together individuals with different viewpoints and expertise, which encourages diverse perspectives on the topic being discussed. This approach is useful for gathering varied insights and can often lead to rich, qualitative data.

Why other options are wrong

B. It is primarily used for quantitative data collection

Focus groups are more commonly used to collect qualitative data, such as opinions, experiences, and perceptions. Quantitative data is typically collected through methods like surveys or experiments, not focus groups.

C. It guarantees unanimous agreement among participants

Focus groups do not guarantee unanimous agreement. In fact, one of the strengths of focus groups is that they can capture a range of opinions and allow for healthy discussion and debate among participants.

D. It is less effective than individual interviews for detailed insights

Focus groups can be very effective for generating discussion and capturing a variety of perspectives. While individual interviews might provide more depth for certain topics, focus groups are valuable for capturing collective insights and exploring group dynamics. Therefore, they can be just as effective as, if not more than, individual interviews in some contexts.

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. Keeping the project on track

Explanation

During the execution phase, the project manager's main responsibility is to ensure that the project progresses as planned. This includes monitoring timelines, managing resources, resolving issues, and ensuring deliverables meet quality standards. Keeping the project on track is critical to meeting deadlines and staying within budget.

Why other options are wrong

A. Developing a list of work tasks

This is generally done during the planning phase, not the execution phase. By the time execution begins, the work tasks should already be defined and scheduled.

B. Assembling a steering committee

Steering committees are typically formed during project initiation or planning to provide oversight. This is not a task assigned to the project manager during execution.

D. Acquiring project supplies and equipment

While this might occasionally fall under execution, procurement is often handled during planning or delegated to support teams. The project manager oversees this process but it is not a primary responsibility during execution.