ITSW 2226 D284 Software Engineering

Correct Answer

D. Ignore conflict to get the job done

Explanation

Effective project managers must manage conflict, not ignore it. Addressing conflict constructively ensures that team morale, productivity, and collaboration are maintained. Ignoring conflict can lead to unresolved issues that hinder project success and damage team dynamics.

Why other options are wrong

A. Recruit effective team members

Selecting the right individuals for a project is essential for team performance and project success. A project manager must ensure that team members have the right skills and fit well with the team dynamic.

B. Coordinate activities

Project managers are responsible for aligning tasks, resources, and schedules to keep the project moving efficiently. Coordination is fundamental to ensuring that deadlines are met and resources are optimized.

C. Keep vision clear & work on track

Maintaining a clear vision and ensuring the project stays aligned with goals and timelines is critical for delivering value and avoiding scope creep or misalignment.

Correct Answer

D. CASE tools used in the project

Explanation

Software Configuration Items (SCIs) are artifacts that are under configuration control in a project. They include documents, source code, test cases, and system prototypes—basically anything that is a deliverable or needs version control. CASE (Computer-Aided Software Engineering) tools are utilities or software used to assist in software development but are not themselves part of the project deliverables or subject to configuration management for that specific software project.

Why other options are wrong

A. configuration management plan for the project

This is an SCI because it is a documented plan that outlines how configuration management will be performed and is typically maintained under version control.

B. prototype of the system

A system prototype is an SCI because it represents a part of the evolving product and is often subject to updates, reviews, and approvals.

C. windows 10 operating system

Although it is third-party software, when it is part of the system's runtime environment or required for deployment, it can be considered an SCI to track compatibility and dependencies.

E. test cases

Test cases are SCIs because they are deliverables that need to be maintained, versioned, and traced to requirements. They play a critical role in validation and verification processes.

Correct Answer

B. Balance is best: strategically select a manageable number of SCIs which will provide adequate visibility without being too difficult to track.

Explanation

The goal when identifying Software Configuration Items (SCIs) is to find a balance. A manageable number of SCIs allows for effective tracking without overwhelming the team with excessive complexity. It’s important to track enough items to maintain control over the software's configuration, but not so many that it becomes difficult to manage or impractical.

Why other options are wrong

A. Short and sweet is best: strategically select only the top ten most important SCIs to track.

This approach may oversimplify the task by focusing only on a small subset of SCIs. While prioritization is important, limiting the selection to just ten items could overlook other critical elements of the software that need to be tracked.

C. Close enough is good enough: strategically select the most important 90% of the potential SCIs because the last 10% usually are not sufficiently important.

This approach risks neglecting key SCIs that may not seem immediately important but could play a crucial role later. The idea of dismissing the last 10% of SCIs could lead to gaps in configuration management.

D. Completeness is best: identify all potential SCIs and track each one.

While completeness might seem thorough, trying to track every possible SCI could lead to an unmanageable level of complexity and effort. It is often more efficient to focus on a subset of SCIs that provides the necessary visibility and control without becoming too burdensome.

Correct Answer

B. Interviews

Explanation

Interviews are considered the most effective technique for collecting requirements from high-level stakeholders, especially in executive-level projects. They provide a direct, one-on-one method to explore priorities, objectives, and insights. Executives often prefer interviews because they offer privacy, flexibility, and the ability to tailor the discussion to specific concerns and strategic goals.

Why other options are wrong

A. Focus groups

This is incorrect because focus groups involve multiple participants and are better suited for gathering consensus or ideas from larger user bases. Executives may not have time for group sessions and may be less candid in such settings.

C. Surveys

This option is incorrect because surveys are impersonal and limited in depth. While they are scalable and useful for collecting data from many people quickly, they don't allow for deep, exploratory discussions that are essential when engaging executives.

D. Document analysis

This is incorrect as it relies on existing materials and does not involve direct communication. While useful as a complementary technique, it lacks the personal interaction needed to gather nuanced requirements from high-level stakeholders.

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.

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

B. Visual language

Explanation

A visual language allows developers to design applications by selecting from a predefined set of components and arranging them using a graphical interface. This type of programming language often uses drag-and-drop features to create applications, making it easier for developers to build applications without writing extensive code. These languages are typically used in environments like visual development tools or integrated development environments (IDEs) where the user interface can be visually manipulated.

Why other options are wrong

A. Toolkit language

A toolkit language refers to a set of software tools and libraries that provide components and functions to help developers build applications. While it may offer prebuilt components, it does not necessarily involve a graphical interface to select them, making it different from a visual language.

C. Configuration language

A configuration language is used for defining the settings or configurations of a system or application, not for creating applications with predefined components through a graphical interface.

D. Scripting language

A scripting language is used for writing scripts to automate tasks or control the behavior of applications. It does not typically involve the selection of predefined components using a graphical interface but is more focused on writing code in a textual form.

Correct Answer

C. Researching similar products

Explanation

Researching similar products is not a technique commonly used in the requirements gathering phase. Requirements gathering typically involves direct methods such as interviews, questionnaires, and observations, where stakeholders' specific needs are identified. While researching similar products might inform the process, it is not the primary method used to gather direct requirements from stakeholders.

Why other options are wrong

A. Questionnaires

This option is incorrect because questionnaires are a widely used data gathering technique in requirements activity. They allow for collecting data from a large number of stakeholders quickly and efficiently, especially when direct interviews are not feasible.

B. Interviews

This is incorrect because interviews are one of the most common techniques used in requirements gathering. They involve direct interaction with stakeholders to gather detailed, personalized information about their needs and expectations for the system.

D. Indirect observation

This is incorrect because indirect observation, such as observing how users interact with existing systems or processes, is a valid and useful technique in the requirements gathering process. It helps analysts understand user behavior and identify any potential improvements or gaps in current systems.

Correct Answer

D. Test case design/data management techniques

Explanation

Error guessing is a test case design technique where the tester uses experience, intuition, and knowledge of the system to anticipate where errors are most likely to occur. Based on this insight, the tester designs test cases to focus on areas that are likely to have defects, such as known problem areas or high-risk features.

Why other options are wrong

A. Test control management techniques

Test control management involves planning, organizing, and managing the testing process. It is not directly related to error guessing, which is focused on designing specific test cases based on potential errors.

B. Test verification techniques

Test verification techniques are used to ensure that the system meets the specified requirements, but error guessing is not about verifying requirements; it’s about anticipating possible errors based on knowledge of the system.

C. Test execution techniques

Test execution techniques focus on how tests are carried out. While error guessing informs test design, it is not a test execution technique, but rather a strategy for test case creation.