What are the requirements that identify the technical constraints or define the conditions under which the product must perform?

There are a number of different types of requirements that Users, System Engineers, and Program Managers will have to develop on an acquisition program through its life-cycle. These requirements range from very high-level concept-focused to very specific for a part. The main types of requirements are:

• Functional Requirements
• Performance Requirements
• System Technical Requirements
• Specifications

Definition: A requirement is a statement that identifies a product or process operational, functional, or design characteristic or constraint, which is unambiguous, testable or measurable, and necessary for product or process acceptability. (ISO/IEC 2007)

Functional Requirements

A functional requirement is simply a task (sometimes called action or activity) that must be accomplished to provide an operational capability (or satisfy an operational requirement). Some functional requirements that are associated with operations and support can be discerned from the needed operational capability (see Operational Requirements). Others often result only from diligent systems engineering. Experience in systems engineering has identified eight generic functions that most systems must complete over their life cycle: development, manufacturing, verification, deployment, training, operations, support, and disposal. These are known as the eight primary system functions. Each must usually be considered in identifying all the functional requirements for a system.

Performance Requirements

A performance requirement is a statement of the extent to which a function must be executed, generally measured in terms such as quantity, accuracy, coverage, timeliness, or readiness. The performance requirements for the operational function and sometimes a few others often correlate well with the statement of the needed operational capability as developed by the Joint Capabilities Integration and Development System (JCIDS) Process. The statement of other performance requirements usually requires thorough systems engineering.

System Technical Requirements

Result in both allocated and derived requirements.

• Allocated Requirements: flow directly from the system requirements down to the elements of the system.
• Derived Requirements: dependent on the design solution (and so are sometimes called design requirements). They include internal interface constraints between the elements of the system.

Specifications

A specification is a detailed, exact statement of particulars, especially a statement prescribing materials, dimensions, and quality of work for something to be built, installed, or manufactured. The overall purpose of a specification is to provide a basis for obtaining a product or service that will satisfy a particular need at an economical cost and to invite maximum reasonable competition. By definition, a specification sets limits and thereby eliminates, or potentially eliminates, items that are outside the boundaries drawn. A good specification should do four (4) things:

1. Identify minimum requirements
2. List reproducible test methods to be used in testing for compliance with specifications
3. Allow for a competitive bid
4. Provide for an equitable award at the lowest possible cost.

– The document that defines the proper organization for all armed-forces specifications is MIL-STD-961E “Defense and Program-Unique Specification Format and Content”.

AcqNotes Tutorial

AcqLinks and References:

Updated: 6/28/2022

Rank: G1

Now that we know how to define project scope and identify it, let us cover a few FAQs on the same topic. Project managers have to carefully identify, assess and manage constraints because they have a direct impact on whether or not the team can finish the project on time, within budget and within scope. Technical Requirements that identify the technical constraints or Requirements define conditions under which the system must perform. Analyzing the stakeholder requirements to check completeness of expected services and operational scenarios operational scenarios, conditions, operational modes, and constraints. Q.

At a minimum, as the project begins, assumptions and constraints must be defined for one or more of the following elements: Key project member’s availability As a result I’ve modified the way I explain Operating Requirements and use it as an opportunity to describe the difference between the two types of content. Definition: System-level technical requirements is a general term used to describe the set of statements that identifies a system's functions, characteristics, or constraints. The main responsibility of the analyst is the discovery, analysis, documentation, and communication of requirements.

Technical Constraints. In this example, constraints are the things you cannot change but that you need to be aware of … A definition of the problem you intend to solve. Assumptions are factors that are believed to be true, but have not been confirmed.Assumptions may affect all aspects of the project and pose a certain degree of risk if they do not prove to be true. Requirements define the needs of the project to provide best of its utility and benefits.

Identify factors other than requirements that may affect which solutions are viable. Description . Make the solution space broad. Use Smartsheet’s customizable Requirement Collection Checklist to turn your technical requirements document into an organic checklist that you can share with your entire team and stakeholders. Contrast with the options: The constraints could be captured as a requirement. The project scope includes the major deliverables of a project, key milestones, and requirements. If they aren’t clear or analysis is not done properly, it might lead to failure of the project no matter how good the concept and design is. Q.

Constraints can be a little confusing because of their overlap with business rules and technical requirements. - Identify the stakeholder requirements or organziational limitation that impose unavoidable constraints. Objectives and constraints. - Identify and define the required system functions. Requirements and Constraints A constraint is a statement of restriction that modifies a requirement or set of requirements by limiting the range of acceptable solutions. They are high-level constraints and often defined when the project starts: for example, time, budget, resources, etc. Requirements are conditions or capabilities that are needed by stakeholders to make effective use of the product, or to satisfy contractual terms, regulations, specifications or other constraints. Step 5 “Identify Ground Rules and Assumptions”. Defining the system requirements and their rationale rationale. Changes to these constraints are rare. 2.3.1 Objectives must be stated so that it is clear what proposals are intended to achieve. Similar to business constraints, technical constraints represent any of a number of technical issues and obstacles that will impact the network design. There are several types of requirements: business, user, functional, quality/technical and implementation requirements define the product in varying degrees of detail and from different perspectives. Based on the user requirement for search results, a system requirement can be:

2020 what are the requirements that identify the technical constraints or define the conditions.

Reference: Sommerville, Software Engineering, 10 ed., Chapter 4

Requirements engineering (RE) is the process of establishing the services that the customer requires from a system and the constraints under which it operates and is developed. The requirements themselves are the descriptions of the system services and constraints that are generated during the requirements engineering process. Requirements may range from a high-level abstract statement of a service or of a system constraint to a detailed mathematical functional specification. As much as possible, requirements should describe what the system should do, but not how it should do it.

Two kinds of requirements based on the intended purpose and target audience:

Three classes of requirements:

Functional requirements describe functionality or system services. They depend on the type of software, expected users and the type of system where the software is used.

• Functional user requirements may be high-level statements of what the system should do.
• Functional system requirements should describe the system services in detail.

Problems arise when requirements are not precisely stated. Ambiguous requirements may be interpreted in different ways by developers and users. In principle, requirements should be both

• Complete: they should include descriptions of all facilities required, and
• Consistent: there should be no conflicts or contradictions in the descriptions of the system facilities.

In practice, it is impossible to produce a complete and consistent requirements document.

Non-functional requirements define system properties and constraints e.g. reliability, response time and storage requirements. Constraints are I/O device capability, system representations, etc. Process requirements may also be specified mandating a particular IDE, programming language or development method. Non-functional requirements may be more critical than functional requirements. If these are not met, the system may be useless.

Non-functional requirements may affect the overall architecture of a system rather than the individual components. A single non-functional requirement, such as a security requirement, may generate a number of related functional requirements that define system services that are required. It may also generate requirements that restrict existing requirements.

Three classes of non-functional requirements:

Non-functional requirements may be very difficult to state precisely and imprecise requirements may be difficult to verify. If they are stated as a goal (a general intention of the user such as ease of use), they should be rewritten as a verifiable non-functional requirement (a statement using some quantifiable metric that can be objectively tested). Goals are helpful to developers as they convey the intentions of the system users.

The system's operational domain imposes requirements on the system. Domain requirements may be new functional or non-functional requirements, constraints on existing requirements, or define specific computations. If domain requirements are not satisfied, the system may be unworkable. Two main problems with domain requirements:

Processes vary widely depending on the application domain, the people involved and the organization developing the requirements. In practice, requirements engineering is an iterative process, in which the following generic activities are interleaved:

• Requirements elicitation;
• Requirements analysis;
• Requirements validation;
• Requirements management.

Software engineers work with a range of system stakeholders to find out about the application domain, the services that the system should provide, the required system performance, hardware constraints, other systems, etc. Stages include:

Closed (based on pre-determined list of questions) and open interviews with stakeholders are a part of the RE process. User stories and scenarios are real-life examples of how a system can be used, which are usually easy for stakeholders to understand. Scenarios should include descriptions of the starting situation, normal flow of events, what can go wrong, other concurrent activities, the state of the system when the scenario finishes.

Use-cases are a scenario-based technique in the UML which identify the actors in an interaction and which describe the interaction itself. A set of use cases should describe all possible interactions with the system.

Problems to look for during requirements elicitation and analysis:

• Stakeholders don't know what they really want.
• Stakeholders express requirements in their own terms.
• Different stakeholders may have conflicting requirements.
• Organizational and political factors may influence the system requirements.
• The requirements change during the analysis process.
• New stakeholders may emerge and the business environment may change.

Requirements specification is the process of writing down the user and system requirements in a requirements document. User requirements have to be understandable by end-users and customers who do not have a technical background. System requirements are more detailed requirements and may include more technical information. The requirements may be part of a contract for the system development and it is important that these are as complete as possible.

In principle, requirements should state what the system should do and the design should describe how it does this. In practice, requirements and design are inseparable.

User requirements are almost always written in natural language supplemented by appropriate diagrams and tables in the requirements document. System requirements may also be written in natural language but other notations based on forms, graphical system models, or mathematical system models can also be used. Natural language is expressive, intuitive and universal. This means that the requirements can be understood by users and customers.

Structured natural language is a way of writing system requirements where the freedom of the requirements writer is limited and all requirements are written in a standard way. This approach maintains most of the expressiveness and understand-ability of natural language but ensures that some uniformity is imposed on the specification.

Requirements validation is concerned with demonstrating that the requirements define the system that the customer really wants. Requirements error costs are high so validation is very important.

What problems to look for:

• Validity: does the system provide the functions which best support the customer's needs?
• Consistency: are there any requirements conflicts?
• Completeness: are all functions required by the customer included?
• Realism: can the requirements be implemented given available budget and technology?
• Verifiability: can the requirements be checked?

Requirements validation techniques:

• Verifiability: is the requirement realistically testable?
• Comprehensibility: is the requirement properly understood?
• Traceability: is the origin of the requirement clearly stated?
• Adaptability: can the requirement be changed without a large impact on other requirements?

Requirements management is the process of managing changing requirements during the requirements engineering process and system development. New requirements emerge as a system is being developed and after it has gone into use. Reasons why requirements change after the system's deployment:

• The business and technical environment of the system always changes after installation.
• The people who pay for a system and the users of that system are rarely the same people.
• Large systems usually have a diverse user community, with many users having different requirements and priorities that may be conflicting or contradictory.