Software Engineering Final Exams -

This is the process to discover if requirements are complete consistent and in accordance with what stakeholders really want from the system.

• Domain understanding

• Requirements collection

• Classification

• Conflict resolution

• Prioritization

• Requirements checking

A source of requirement where the requirement will be derived from the environment in which the software will be executed.

• Goals

• Domain Knowledge

• Stakeholders

• Operational Environment

• Organizational Environment

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.

• Domain understanding

• Requirements collection

• Classification

• Conflict resolution

• Prioritization

• Requirements checking

A source of requirement where the engineer himself will have to acquire knowledge from the specific application domain

• Goals

• Domain Knowledge

• Stakeholders

• Operational Environment

• Organizational Environment

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.

• Users

• Market Analysts

• Customers

• Software Engineers

• Regulators

This is the process where the engineer is concerned with finding and resolving conflicts especially when multiple stakeholders are involved.

• Domain understanding

• Requirements collection

• Classification

• Conflict resolution

• Prioritization

• Requirements checking

A type of software stakeholder who are needed to establish what the market needs and to act as proxy customers.

• Users

• Market Analysts

• Customers

• Software Engineers

• Requlators

A set of behaviors in the evolution of proprietary software also known as the Lehman's Laws which are as follows:   Conservation of Organisational  ______ (invariant work rate) - The average effective global activity rate in an evolving E-type system is invariant over product lifetime.  

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.

A source of requirement where the engineer must identify, represent and manage the 'viewpoints' of many different types of stakeholders

• Goals

• Domain Knowledge

• Stakeholders

• Operational Environment

• Organizational Environment

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.

• Users

• Market Analysts

• Customers

• Software Engineers

Software project ********** is the organizing, planning and scheduling of software projects. It is concerned with activities involved in ensuring that software is delivered on ______ and on schedule and in accordance with the requirements of the organizations developing and procuring the software.

This is the process where the engineer takes the unstructured collection of requirements and organize them into coherent clusters.

• Domain understanding

• Requirements collection

• Classification

• Conflict resolution

• Prioritization

• Requirements checking

This is the process where it involves interaction with stakeholders to discover the most important requirements.

• Domain understanding

• Requirements collection

• Classification

• Conflict resolution

• Prioritization

• Requirements checking

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

A set of behaviors in the evolution of proprietary software also known as the Lehman's Laws which are as follows:     Continuing _____ — E-type systems must be continually adapted or they become progressively less satisfactory  

A set of behaviors in the evolution of proprietary software also known as the Lehman's Laws which are as follows: Self Regulation — E-type system evolution process is self regulating with distribution of ******** and ______ measures close to normal.

Software project ________ is the organizing, planning and scheduling of software projects. It is concerned with activities involved in ensuring that software is delivered on ______ and on schedule and in accordance with the requirements of the organizations developing and procuring the software.

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.

• Domain understanding

• Requirements collection

• Classification

• Conflict resolution

• Prioritization

• Requirements checking

A source of requirement where it refers to the overall, high level objectives of the software or critical success factor

• Goals

• Domain Knowledge

• Stakeholders

• Operational Environment

• Organizational Environment

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.

________ means that requirements should have no conflicts or contradictions in the descriptions of the system facilities

A set of behaviors in the evolution of proprietary software also known as the Lehman's Laws which are as follows: Declining Quality — The quality of E-type systems will appear to be declining unless they are rigorously maintained and adapted to operational _______ changes.

The term ________ is used to refer to anyone who should have direct or indirect influence on the system requirements.

Many application domains such as banking and public transport are regulated. Software in these domains must comply with the requirements of the ________

• Users

• Market Analysts

• Customers

• Software Engineers

• Regulators

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:

________ are the requirements for the system as a whole

A set of behaviors in the evolution of proprietary software also known as the Lehman's Laws which are as follows: Self Regulation — E-type system evolution process is self regulating with distribution of ______ and ******* measures close to normal.

Lehman and Belady classified programs into three types: ______ programs are embedded in the real world and become part of it, thereby changing it. This leads to a feedback system where the program and its environment evolve in concert.

A set of behaviors in the evolution of proprietary software also known as the Lehman's Laws which are as follows:       Increasing _______ — As an E-type system evolves it becomes more complex unless work is done to maintain or reduce it  

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

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

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.

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.  

Lehman and Belady classified programs into three types:     ______ programs are those that cannot be specified. Instead, an iterative process is used to find a working solution.  

_______ means that all services required by the user should be defined

In a system containing software components, ___________ are derived from system requirements

It is a process that involves all of the activities required to create and maintain a system requirements document

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.

Lehman and Belady classified programs into three types: ______ programs are those that can be specified formally.

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

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

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.

Non-functional classifications __________- Requirements which specify that the delivered product must behave in a particular way e.g. execution speed, reliability, etc.

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.

A set of behaviors in the evolution of proprietary software also known as the Lehman's Laws which are as follows: Continuing ______ — The functional content of E-type systems must be continually increased to maintain user satisfaction over their lifetime.

_______ - A general intention of the user such as ease of use. ______ are helpful to developers as they convey the intentions of the system users.

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.