Software Engineering Final Exams -
Questions and Answers
- 1.
It is a process that involves all of the activities required to create and maintain a system requirements document
Explanation
Requirements Engineering is the process that encompasses all activities necessary for the creation and maintenance of a system requirements document. This process involves gathering, analyzing, documenting, and managing the requirements of a system. It includes identifying stakeholders, understanding their needs and expectations, and translating them into specific and measurable requirements. The goal of Requirements Engineering is to ensure that the system meets the desired functionality, performance, and quality standards, while also considering constraints such as time, budget, and resources. This process is crucial for the successful development and implementation of any system.Rate this question:
- 2.
A source of requirement where it refers to the overall, high level objectives of the software or critical success factor
- A.
Goals
- B.
Domain Knowledge
- C.
Stakeholders
- D.
Operational Environment
- E.
Organizational Environment
Correct Answer
A. GoalsExplanation
Goals are the overall, high-level objectives of the software or critical success factors. They represent the desired outcomes or achievements that the software should fulfill. In the context of requirements, goals provide a clear direction and purpose for the development process. They help in defining the scope and priorities of the software project, and serve as a basis for making design decisions. By focusing on goals, the development team can ensure that the software meets the needs and expectations of the stakeholders.Rate this question:
-
- 3.
A source of requirement where the engineer himself will have to acquire knowledge from the specific application domain
- A.
Goals
- B.
Domain Knowledge
- C.
Stakeholders
- D.
Operational Environment
- E.
Organizational Environment
Correct Answer
B. Domain KnowledgeExplanation
Domain knowledge refers to the specific knowledge or expertise required in a particular field or industry. In this context, the engineer needs to acquire knowledge from the specific application domain in order to understand the requirements and develop a solution that meets the needs of the stakeholders. This implies that the engineer cannot solely rely on their existing knowledge or skills, but must actively seek out and learn about the domain in which they are working. This is important because without a deep understanding of the domain, the engineer may not be able to accurately identify and address the requirements of the project.Rate this question:
-
- 4.
A source of requirement where the engineer must identify, represent and manage the 'viewpoints' of many different types of stakeholders
- A.
Goals
- B.
Domain Knowledge
- C.
Stakeholders
- D.
Operational Environment
- E.
Organizational Environment
Correct Answer
C. StakeholdersExplanation
In order to meet the requirements of a project, engineers must consider the needs and perspectives of various stakeholders. Stakeholders can include clients, users, managers, and other individuals or groups who have an interest in the project. By identifying, representing, and managing these viewpoints, engineers can ensure that the final product or solution meets the expectations and requirements of all relevant parties. Therefore, stakeholders are a crucial source of requirements for engineers.Rate this question:
-
- 5.
A source of requirement where the requirement will be derived from the environment in which the software will be executed.
- A.
Goals
- B.
Domain Knowledge
- C.
Stakeholders
- D.
Operational Environment
- E.
Organizational Environment
Correct Answer
D. Operational EnvironmentExplanation
Operational environment refers to the specific conditions and constraints in which the software will be executed. This includes factors such as the hardware, software, network, and other resources that the software will interact with. The requirements derived from the operational environment are essential for ensuring that the software functions correctly and efficiently in its intended environment. This could include requirements related to performance, compatibility, security, and usability. By considering the operational environment, developers can design and implement software that meets the needs and expectations of the users and stakeholders.Rate this question:
-
- 6.
A source of requirement where the software engineer must conform to the structure, culture and internal politics of an organization
- A.
Goals
- B.
Domain Knowledge
- C.
Stakeholders
- D.
Operational Environment
- E.
Organizational Environment
Correct Answer
E. Organizational EnvironmentExplanation
The organizational environment refers to the structure, culture, and internal politics of an organization. In this context, the software engineer must conform to these aspects in order to meet the requirements of the organization. This includes understanding and adhering to the organization's hierarchy, communication channels, decision-making processes, and any specific rules or norms that exist within the organization. By conforming to the organizational environment, the software engineer can ensure that their work aligns with the goals and expectations of the organization.Rate this question:
-
- 7.
_____________ is concerned with where software requirements come from and how the software engineer can collect them. It is the first stage in building an understanding of the problem the software is required to solve. It is fundamentally a human activity, and is where the stakeholders are identified and relationships established between the development team and the customer.
Correct Answer
Requirements ElicitationExplanation
Requirements elicitation is the process of gathering and collecting software requirements. It involves determining where the requirements come from and how the software engineer can collect them. This stage is crucial in building an understanding of the problem that the software needs to solve. It is a human activity that involves identifying stakeholders and establishing relationships between the development team and the customer.Rate this question:
- 8.
The term ________ is used to refer to anyone who should have direct or indirect influence on the system requirements.
Correct Answer
stakeholderExplanation
A stakeholder is a term used to refer to anyone who should have direct or indirect influence on the system requirements. This means that stakeholders can include individuals or groups who have a vested interest in the system, such as end-users, clients, managers, developers, or even external entities. Their involvement is crucial in order to ensure that the system requirements align with their needs and expectations. By considering the perspectives and input of stakeholders, the development process can be more effective and ultimately lead to a successful system implementation.Rate this question:
- 9.
A type of software stakeholder which comprises of those who will operate the software. It is often a heterogeneous group comprising people with different roles and requirements.
- A.
Users
- B.
Market Analysts
- C.
Customers
- D.
Software Engineers
Correct Answer
A. UsersExplanation
The correct answer is "Users" because they are the individuals who will operate the software. They are a heterogeneous group with different roles and requirements, making them an important software stakeholder. Market analysts, customers, and software engineers may also be stakeholders, but they may have different roles and responsibilities compared to the users.Rate this question:
-
- 10.
A type of software stakeholder which comprises those who have commissioned the software or who represent the software’s target market.
- A.
Users
- B.
Market Analysts
- C.
Customers
- D.
Software Engineers
- E.
Regulators
Correct Answer
C. CustomersExplanation
Customers are the correct answer because they are the ones who have commissioned the software or represent the software's target market. Customers play a crucial role in the development and success of the software as they provide requirements and feedback, ensuring that the software meets their needs and expectations. They are the primary stakeholders who have a direct interest in the software and its functionality.Rate this question:
-
- 11.
A type of software stakeholder who are needed to establish what the market needs and to act as proxy customers.
- A.
Users
- B.
Market Analysts
- C.
Customers
- D.
Software Engineers
- E.
Requlators
Correct Answer
B. Market AnalystsExplanation
Market Analysts are a type of software stakeholder who play a crucial role in understanding and establishing what the market needs. They gather and analyze data related to market trends, customer preferences, and competitor analysis. By acting as proxy customers, they provide valuable insights and help in shaping the software development process. Their expertise helps in identifying market opportunities, defining product requirements, and ensuring that the software meets the demands and expectations of the target market.Rate this question:
-
- 12.
Many application domains such as banking and public transport are regulated. Software in these domains must comply with the requirements of the ________
- A.
Users
- B.
Market Analysts
- C.
Customers
- D.
Software Engineers
- E.
Regulators
Correct Answer
E. RegulatorsExplanation
In regulated application domains such as banking and public transport, software must comply with specific requirements set by regulatory bodies. These requirements are put in place to ensure the safety, security, and integrity of the systems and to protect the interests of the users, customers, and the general public. Therefore, the correct answer is "Regulators" as they are the ones responsible for setting and enforcing these regulations.Rate this question:
-
- 13.
These individuals have a legitimate interest in profiting from developing the software by, for example, reusing components in other products. If, in this scenario, a customer of a particular product has specific requirements which compromise the potential for component reuse, the software engineers must carefully weigh their own stake against those of the customer.
- A.
Users
- B.
Market Analysts
- C.
Customers
- D.
Software Engineers
- E.
Regulators
Correct Answer
D. Software EngineersExplanation
In this scenario, the software engineers have a legitimate interest in profiting from developing the software by reusing components in other products. If a customer has specific requirements that would compromise the potential for component reuse, the software engineers must carefully weigh their own stake in profiting from the software against the needs and desires of the customer. This suggests that the software engineers are the ones who have to make the decision in this situation.Rate this question:
-
- 14.
A process in elicitation where analyst must develop their understanding of the application domain. For example, if a system for a supermarket is required, the analyst must find out how supermarkets operate.
- A.
Domain understanding
- B.
Requirements collection
- C.
Classification
- D.
Conflict resolution
- E.
Prioritization
- F.
Requirements checking
Correct Answer
A. Domain understandingExplanation
Domain understanding refers to the process in which an analyst develops their knowledge and comprehension of the specific application domain. In this case, the analyst needs to gain an understanding of how supermarkets operate in order to gather the necessary requirements for the system. This involves learning about the various processes, operations, and functions that are typically found in a supermarket setting. By acquiring domain understanding, the analyst can effectively identify and document the requirements that will meet the needs of the supermarket system.Rate this question:
-
- 15.
It is a process of elictiation where the engineer is interacting with stakeholders in the system to discover their requirements. Domain understanding develops further during this activity.
- A.
Domain understanding
- B.
Requirements collection
- C.
Classification
- D.
Conflict resolution
- E.
Prioritization
- F.
Requirements checking
Correct Answer
B. Requirements collectionExplanation
Requirements collection is the process of elicitation where the engineer interacts with stakeholders in the system to discover their requirements. This activity helps in developing domain understanding as the engineer gains more knowledge about the specific domain in which the system operates. It involves gathering and documenting all the necessary information about the requirements, which will be used as a basis for further analysis and development of the system.Rate this question:
-
- 16.
This is the process where the engineer takes the unstructured collection of requirements and organize them into coherent clusters.
- A.
Domain understanding
- B.
Requirements collection
- C.
Classification
- D.
Conflict resolution
- E.
Prioritization
- F.
Requirements checking
Correct Answer
C. ClassificationExplanation
Classification is the process where the engineer takes the unstructured collection of requirements and organizes them into coherent clusters. This involves categorizing the requirements based on their similarities or common characteristics. By classifying the requirements, the engineer can better understand and analyze them, making it easier to prioritize and address them effectively.Rate this question:
-
- 17.
This is the process where the engineer is concerned with finding and resolving conflicts especially when multiple stakeholders are involved.
- A.
Domain understanding
- B.
Requirements collection
- C.
Classification
- D.
Conflict resolution
- E.
Prioritization
- F.
Requirements checking
Correct Answer
D. Conflict resolutionExplanation
Conflict resolution is the process where the engineer is concerned with finding and resolving conflicts especially when multiple stakeholders are involved. This involves identifying and addressing any disagreements or contradictions that may arise during the requirements gathering and analysis phase. It is important for the engineer to ensure that all stakeholders' needs and expectations are considered and any conflicts are resolved in order to develop a successful solution.Rate this question:
-
- 18.
This is the process where it involves interaction with stakeholders to discover the most important requirements.
- A.
Domain understanding
- B.
Requirements collection
- C.
Classification
- D.
Conflict resolution
- E.
Prioritization
- F.
Requirements checking
Correct Answer
E. PrioritizationExplanation
Prioritization is the process of determining the most important requirements by considering the needs and preferences of stakeholders. It involves analyzing and evaluating the requirements based on various factors such as business value, feasibility, urgency, and impact. Through prioritization, the most critical requirements are identified and given higher priority for implementation, ensuring that resources are allocated effectively and the most valuable features are delivered first.Rate this question:
-
- 19.
This is the process to discover if requirements are complete consistent and in accordance with what stakeholders really want from the system.
- A.
Domain understanding
- B.
Requirements collection
- C.
Classification
- D.
Conflict resolution
- E.
Prioritization
- F.
Requirements checking
Correct Answer
F. Requirements checkingExplanation
Requirements checking is the process of reviewing and evaluating the collected requirements to ensure they are complete, consistent, and aligned with the stakeholders' expectations. It involves verifying that all necessary information has been captured, identifying any conflicts or contradictions between requirements, and ensuring that the requirements are feasible and realistic. This step is crucial in ensuring that the final system meets the needs and expectations of the stakeholders.Rate this question:
-
- 20.
___________ is concerned with demonstrating that the requirements actually define the system that the customer wants. It has much in common with analysis as it is concerned with finding problems with the requirements.
Correct Answer
Requirements validationExplanation
Requirements validation is the process of ensuring that the requirements accurately reflect the system that the customer desires. It involves analyzing the requirements to identify any potential issues or problems. This process is crucial in order to prevent misunderstandings or misinterpretations of the customer's needs and to ensure that the final system meets the desired objectives. By validating the requirements, any inconsistencies, ambiguities, or missing information can be identified and addressed, ultimately leading to a more successful and satisfactory system implementation.Rate this question:
- 21.
_________ is a property which must be exhibited in order to solve some problem in the real world. This refers to requirements on software’ because it is concerned with problems to be addressed by software.
Correct Answer
software requirementExplanation
Software requirement is a property that must be exhibited in order to solve a problem in the real world. It is concerned with the problems that need to be addressed by software. In other words, software requirements are the specifications and functionalities that the software must possess in order to meet the needs and expectations of the users. These requirements define what the software should do, how it should behave, and what constraints it should adhere to. They serve as the foundation for the development and design of the software solution.Rate this question:
- 22.
__________ are statements, in natural language plus diagrams, of what services the system is expected to provide and the constraints under which it must operate. It is a high-level abstract requirements written for customers.
Correct Answer
User requirementsExplanation
User requirements are statements, in natural language plus diagrams, of what services the system is expected to provide and the constraints under which it must operate. They are high-level abstract requirements written for customers, outlining their needs and expectations from the system. User requirements serve as a foundation for the development process and help ensure that the final product meets the desired functionality and usability for the end-users.Rate this question:
- 23.
___________ is a structured document setting out detailed descriptions of the system services and constraints. It may serve as a contract between client and software developer.
Correct Answer
System requirementsExplanation
A system requirements document is a structured document that provides detailed descriptions of the services and constraints of a system. It outlines the specific needs and expectations of the client and serves as a contract between the client and the software developer. This document helps ensure that both parties have a clear understanding of what the system should do and what limitations or constraints it may have. It is an essential tool in the software development process as it helps guide the development team in creating a system that meets the client's needs and expectations.Rate this question:
- 24.
_______ means that all services required by the user should be defined
Correct Answer
CompletenessExplanation
Completeness means that all services required by the user should be defined. This indicates that in order for a system or process to be considered complete, it must include all the necessary services or components that are required by the user. In other words, nothing should be missing or left out for the system to fully meet the user's needs or requirements.Rate this question:
- 25.
________ means that requirements should have no conflicts or contradictions in the descriptions of the system facilities
Correct Answer
ConsistencyExplanation
Consistency refers to the quality of having requirements that are coherent and harmonious, with no conflicts or contradictions in the descriptions of the system facilities. This means that all the requirements should align and work together seamlessly without any inconsistencies or contradictions. It is crucial for ensuring that the system functions properly and meets the desired objectives without any conflicts or issues arising from contradictory requirements.Rate this question:
- 26.
_______ - A general intention of the user such as ease of use. ______ are helpful to developers as they convey the intentions of the system users.
Correct Answer
GoalsExplanation
Goals are a general intention of the user, such as ease of use. They are helpful to developers as they convey the intentions of the system users. By understanding the goals of the users, developers can design and develop the system in a way that meets those goals, resulting in a more user-friendly and effective system.Rate this question:
- 27.
A statement using some measure that can be objectively tested.
Correct Answer
Verifiable non-functional requirement, Verifiable non functional requirementsExplanation
Verifiable non-functional requirements are statements that can be objectively tested. These requirements focus on the performance, reliability, and usability aspects of a system, rather than its specific functionalities. They can be measured and evaluated to determine if they have been met or not. By using verifiable non-functional requirements, organizations can ensure that their systems meet certain quality standards and provide a satisfactory user experience.Rate this question:
- 28.
These often lead to much mystical mumblings, implying that a high priest of the computing fraternity is the only person who can understand them. They are however quite simple; they are the restrictions or constraints to be placed on the system and how to build it. Their purpose is to restrict the number of solutions that will meet a set of requirements. Non-functional requirements can be split into two types: ________ - These constraints are how the system should perform when it is delivered
Correct Answer
PerformanceExplanation
Non-functional requirements are constraints that dictate how a system should perform when it is delivered. Performance requirements specifically focus on the system's speed, efficiency, and responsiveness. These requirements ensure that the system meets the desired performance standards and can handle the expected workload without any performance issues. By setting performance constraints, the development team can prioritize and optimize the system's performance to meet the specified requirements.Rate this question:
- 29.
A more successful method is to prioritize requirements by using words that have meaning. Several schemes exist but a method popularized by the DSDM community is the acronym MoSCoW. This stands for: M stands for:
Correct Answer
Must have thisExplanation
MoSCoW is an acronym used to prioritize requirements. In this context, "M" stands for "Must have this." This means that the requirement is essential and must be fulfilled for the project's success. It indicates that without this requirement, the project cannot proceed or deliver the desired outcome. Prioritizing requirements using meaningful words helps ensure that the most critical needs are addressed first, allowing for more effective project planning and resource allocation.Rate this question:
- 30.
A more successful method is to prioritize requirements by using words that have meaning. Several schemes exist but a method popularized by the DSDM community is the acronym MoSCoW. This stands for: S stands for:
Correct Answer
Should have this if at all possibleExplanation
The acronym MoSCoW is a prioritization method used to categorize requirements. In this method, the "S" stands for "Should have this if at all possible." This means that the requirement is important and should be included if feasible. It indicates that the requirement is not critical, but it should be considered and implemented if it doesn't cause significant issues or delays.Rate this question:
- 31.
A more successful method is to prioritize requirements by using words that have meaning. Several schemes exist but a method popularized by the DSDM community is the acronym MoSCoW. This stands for: C stands for:
Correct Answer
Could have this if it does not affect anything elseExplanation
The letter "C" in the acronym MoSCoW stands for "Could have this if it does not affect anything else." This means that the requirement is desirable, but it is not critical and can be deprioritized if it has an impact on other requirements or constraints. It suggests that this requirement is flexible and can be adjusted based on its potential impact on other aspects of the project.Rate this question:
- 32.
A more successful method is to prioritize requirements by using words that have meaning. Several schemes exist but a method popularized by the DSDM community is the acronym MoSCoW. This stands for: W stands for:
Correct Answer
Won't have this but would like in the futureExplanation
The letter "W" in the acronym MoSCoW stands for "Won't have this but would like in the future." This means that the requirement is not essential for the current project but is desired for future development or iterations. It indicates that the requirement is not a priority at the moment but may be considered in the future.Rate this question:
- 33.
__________ means ‘ an interacting combination of elements to accomplish a defined objective. These include hardware,software, firmware, people, information, techniques, facilities, services, and other support elements, ’ as defined by the International Council on Systems Engineering (INCOSE00).
Correct Answer
SystemExplanation
The term "system" refers to an interacting combination of elements that work together to achieve a specific goal or objective. These elements can include hardware, software, firmware, people, information, techniques, facilities, services, and other support elements. This definition is provided by the International Council on Systems Engineering (INCOSE00). In other words, a system is a complex entity that involves various components and processes working in harmony to accomplish a defined objective.Rate this question:
- 34.
________ are the requirements for the system as a whole
Correct Answer
System requirementsExplanation
System requirements refer to the specifications, functionalities, and capabilities that a system must possess in order to meet the needs and expectations of its users. These requirements are essential for the overall functioning and performance of the system. They outline the hardware, software, network, and operational aspects that are necessary for the system to operate effectively. System requirements ensure that the system is able to perform its intended tasks and meet the desired objectives.Rate this question:
- 35.
In a system containing software components, ___________ are derived from system requirements
Correct Answer
Software requirementsExplanation
Software requirements are derived from system requirements in a system containing software components. System requirements outline the overall functionality and constraints of the system, while software requirements specifically focus on the functionality and constraints that pertain to the software components. By deriving software requirements from system requirements, the specific needs and specifications for the software components can be identified and addressed, ensuring that the software meets the overall goals and objectives of the system.Rate this question:
- 36.
A _________________ is a language derived from a programming language like Java or ADA. Requirements may be defined operationally using a language like a programming language but with more flexibility of expression.
Correct Answer
Programming Description Language, PDL, (PDL)Explanation
A Programming Description Language (PDL) is a language derived from a programming language like Java or ADA. It allows for defining requirements operationally, similar to a programming language, but with greater flexibility of expression. PDL enables developers to describe the functionality and behavior of a program in a more expressive and flexible manner, making it easier to understand and communicate the requirements of a software system.Rate this question:
- 37.
Non-functional classifications __________- Requirements which specify that the delivered product must behave in a particular way e.g. execution speed, reliability, etc.
Correct Answer
Product requirements, ProductExplanation
Non-functional classifications refer to requirements that specify how the delivered product should behave in certain aspects, such as execution speed and reliability. These requirements focus on the overall performance and characteristics of the product rather than its specific features or functionalities. In this case, the correct answer is "Product requirements" because it aligns with the definition of non-functional classifications as requirements related to the product itself.Rate this question:
- 38.
Non-functional classifications __________- Requirements which are a consequence of organizational policies and procedures e.g. process standards used, implementation requirements, etc.
Correct Answer
Organizational requirements, Organizational - 39.
Non-functional classifications __________-Requirements which arise from factors which are external to the system and its development process e.g. interoperability requirements, legislative requirements, etc.
Correct Answer
External Requirements, ExternalExplanation
This answer correctly identifies that non-functional classifications refer to requirements that arise from factors external to the system and its development process. These requirements can include interoperability requirements, legislative requirements, and other external factors that the system needs to adhere to. The term "external requirements" is used to describe these non-functional classifications, emphasizing that they originate from external sources.Rate this question:
- 40.
Software engineering is distinct from type of engineering in a number of ways which can make software management difficult. Some of the differences are : The software product is _______ It cannot be seen or touched. Software project managers cannot see progress.
Correct Answer
intangibleExplanation
The correct answer is "intangible". Software engineering is distinct from other types of engineering because software products cannot be seen or touched. This intangible nature of software makes it difficult for software project managers to visually track progress or measure the completion of tasks. Unlike physical engineering projects, software development requires a different approach to management and tracking progress.Rate this question:
- 41.
Software engineering is distinct from type of engineering in a number of ways which can make software management difficult. Some of the differences are : The software development process is not ________. We do not have clear understanding of the relationships between software process and product types.
Correct Answer
standardizedExplanation
The software development process is not standardized, meaning that there is no universally agreed upon set of steps or guidelines for developing software. This lack of standardization can make software management difficult because there is no clear understanding of the relationships between the software process and the types of products being developed. Without standardized processes, it can be challenging to consistently produce high-quality software and effectively manage software projects.Rate this question:
- 42.
Software engineering is distinct from type of engineering in a number of ways which can make software management difficult. Some of the differences are : Many software projects are _________ projects. Large software projects are usually different from previous projects. Rapid technological changes in computers and communications outdate previous experience. Lessons learned from that experience may not be transferable to new projects.
Correct Answer
one-offExplanation
Software projects are often one-off projects, meaning that they are unique and different from previous projects. This uniqueness is due to the rapid changes in technology, which can quickly make previous experience and lessons learned outdated and not applicable to new projects. This can make software management difficult as there is no established template or set of guidelines to follow, and each project requires a fresh approach.Rate this question:
- 43.
Risk ________ is the process of measuring or assessing risk and then developing strategies to manage the risk. In general, the strategies employed include transferring the risk to another party, avoiding the risk, reducing the negative effect of the risk, and accepting some or all of the consequences of a particular risk.
Correct Answer
managementExplanation
The correct answer is "management" because it accurately describes the process of measuring or assessing risk and then developing strategies to manage the risk. This involves various strategies such as transferring the risk to another party, avoiding the risk, reducing the negative effect of the risk, and accepting the consequences of a particular risk.Rate this question:
- 44.
A ________ is an end-point of a software process activity. It represents the end of a distinct, logical stage in the project. While a ********* is a project result that is delivered to the customer. It is usually delivered at the end of some major project phase such as specification, design, etc.
Correct Answer
milestoneExplanation
A milestone is an end-point of a software process activity. It represents the end of a distinct, logical stage in the project. It is a significant event or achievement that marks progress in the project and helps to track the project's timeline and progress. On the other hand, a deliverable is a project result that is delivered to the customer. It is usually delivered at the end of some major project phase such as specification, design, etc. Deliverables are tangible outputs that can be reviewed and approved by the stakeholders.Rate this question:
- 45.
A ********* is an end-point of a software process activity. It represents the end of a distinct, logical stage in the project. While a _______ is a project result that is delivered to the customer. It is usually delivered at the end of some major project phase such as specification, design, etc.
Correct Answer
deliverableExplanation
A deliverable is an end-point of a software process activity. It represents the end of a distinct, logical stage in the project. While a deliverable is a project result that is delivered to the customer. It is usually delivered at the end of some major project phase such as specification, design, etc.Rate this question:
- 46.
The purpose of project _______ is to identify the scope of the project, estimate the work involved, and create a project schedule. While the purpose of project ******** and ******** is to keep the team and management up to date on the project's progress. If the project deviates from the plan, then the project manager can take action to correct the problem. It involves ******** meetings to gather status from the team. When changes need to be made, change ******** is used to keep the products up to date.
Correct Answer
planningExplanation
The purpose of project planning is to identify the scope of the project, estimate the work involved, and create a project schedule. It allows the project manager to have a clear understanding of the project's objectives and the tasks that need to be completed. Additionally, project planning helps in setting realistic timelines and allocating resources effectively. By having a well-defined plan, the project manager can track the progress of the project and take necessary actions if there are any deviations from the plan. Regular meetings and change management processes are also part of project planning to ensure that the project stays on track and any necessary adjustments are made.Rate this question:
- 47.
The purpose of project ******** is to identify the scope of the project, estimate the work involved, and create a project schedule. While the purpose of project _______ and ******** is to keep the team and management up to date on the project's progress. If the project deviates from the plan, then the project manager can take action to correct the problem. It involves ******** meetings to gather status from the team. When changes need to be made, change ******** is used to keep the products up to date.
Correct Answer
monitoringExplanation
The purpose of project monitoring is to keep the team and management up to date on the project's progress. It involves regular meetings to gather status from the team and if the project deviates from the plan, the project manager can take action to correct the problem. Change control is used to keep the project's products up to date when changes need to be made.Rate this question:
- 48.
The purpose of project ******** is to identify the scope of the project, estimate the work involved, and create a project schedule. While the purpose of project ******** and ______ is to keep the team and management up to date on the project's progress. If the project deviates from the plan, then the project manager can take action to correct the problem. It involves ******** meetings to gather status from the team. When changes need to be made, change ******** is used to keep the products up to date.
Correct Answer
controlExplanation
The purpose of project control is to keep the team and management up to date on the project's progress and take action to correct any deviations from the plan. It involves regular meetings to gather status from the team and uses change control to keep the project's products up to date.Rate this question:
- 49.
The purpose of project ******** is to identify the scope of the project, estimate the work involved, and create a project schedule. While the purpose of project ********and ******** is to keep the team and management up to date on the project's progress. If the project deviates from the plan, then the project manager can take action to correct the problem. It involves ______ meetings to gather status from the team. When changes need to be made, change ******** is used to keep the products up to date.
Correct Answer
statusExplanation
The given answer "status" is correct because the sentence mentions that the purpose of project ******** and ******** is to keep the team and management up to date on the project's progress. This implies that gathering status updates from the team is an essential part of these projects. Additionally, the sentence also mentions using change ******** to keep the products up to date, indicating that monitoring and updating the status is crucial for managing any changes in the project.Rate this question:
- 50.
The purpose of project ******** is to identify the scope of the project, estimate the work involved, and create a project schedule. While the purpose of project ******** and ******** is to keep the team and management up to date on the project's progress. If the project deviates from the plan, then the project manager can take action to correct the problem. It involves ******** meetings to gather status from the team. When changes need to be made, change ____ is used to keep the products up to date.
Correct Answer
controlExplanation
The purpose of project control is to keep the team and management up to date on the project's progress and take action to correct any deviations from the plan. It involves regular meetings to gather status from the team and uses change control to keep the project's products up to date.Rate this question:
Quiz Review Timeline +
Our quizzes are rigorously reviewed, monitored and continuously updated by our expert board to maintain accuracy, relevance, and timeliness.
-
Current Version
-
Sep 05, 2023Quiz Edited by
ProProfs Editorial Team -
Mar 18, 2012Quiz Created by
Bawbawbiscuit
Back to top