Software Engineering Final Exams -

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.

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.

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.

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.

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.

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.

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.

The correct answer is Stability. The explanation for this answer is that one of Lehman's Laws in the evolution of proprietary software is the conservation of organizational stability. This means that the average effective global activity rate in an evolving E-type system remains stable over the product's lifetime. In other words, the level of activity and productivity within the organization remains relatively constant over time. This stability is an important factor in the evolution and success of proprietary software.

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.

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.

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.

The correct answer for this question is "time". In software project management, time management is crucial to ensure that the software is delivered within the specified timeframe and according to the project schedule. It involves planning and scheduling activities to meet deadlines and deliver the software on time. Time management also ensures that the project stays on track and meets the requirements of the organizations involved in the development and procurement of the software.

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.

The given correct answer for this question is "management". Software project management refers to the process of organizing, planning, and scheduling software projects. It involves activities that ensure the timely delivery of software according to the specified requirements of the organizations involved in its development and procurement.

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.

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.

According to Lehman's Laws, E-type systems (which refer to evolving or software systems) must undergo continual adaptation or else they will gradually become less satisfactory. This means that as technology and user needs change, the software must also change in order to remain effective and meet the evolving requirements.

not-available-via-ai

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.

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.

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.

The declining quality of E-type systems is a result of not adapting and maintaining them to operational environment changes. This means that if the systems are not regularly updated and adjusted to meet the changing needs and demands of the environment they operate in, their quality will appear to decline. Therefore, it is important for proprietary software to be constantly monitored and modified to ensure that it remains effective and efficient in its operational environment.

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.

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.

not-available-via-ai

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.

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.

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.

E-type programs are embedded in the real world and become part of it, thereby changing it. This type of program creates a feedback system where the program and its environment evolve together. E-type programs are typically used in complex and dynamic systems, such as artificial intelligence, robotics, and simulations. They are designed to adapt and learn from their environment, making them capable of evolving and improving over time.

Lehman's Laws describe a set of behaviors in the evolution of proprietary software. One of these laws states that as an E-type system (a complex software system) evolves, it becomes more complex unless work is done to maintain or reduce its complexity. Therefore, the correct answer to the question is "complexity."

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.

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.

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.

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.

not-available-via-ai

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.

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.

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.

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.

S-type programs are those that can be specified formally. This means that these programs have a clear and precise definition or specification that can be written down in a formal language or notation. This allows for a systematic and rigorous approach to analyzing and verifying the behavior and correctness of these programs. By classifying programs into different types based on their formal specification, Lehman and Belady provide a framework for understanding and categorizing the characteristics and properties of different programs.

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.

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.

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.

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.