Please enable JavaScript.
Coggle requires JavaScript to display documents.
REQUIREMENTS - Coggle Diagram
REQUIREMENTS
Requirements
Analysis
Working toward collaboration
The job of a requirements engineer is to identify areas of commonality (i.e., requirements on which all stakeholders agree) and areas of conflict or inconsistency (i.e., requirements that are desired by one stakeholder but conflict with the needs of another stakeholder).
Requirements engineering
The broad spectrum of tasks and techniques that lead to an understanding of requirements is called requirements engineering.
Inception
At project inception, you establish a basic understanding of the problem, the people who want a solution, the nature of the solution that is desired, and the effectiveness of preliminary communication and collaboration between the other stakeholders and the project team.
The final desicion?
Sometimes, stakeholders collaborate by providing their view of requirements, but a strong “project manager”(e.g., a business manager or a senior technologist) may make the final decision about which requirements make the cut.
How does a project get
started?
The business community (e.g., business managers, marketing people, product managers) define a business case for the idea, try to identify the breadth and depth of the market, do a rough feasibility analysis, and identify a working description of the project’s scope.
Recognizing multiple
viewpoints
You should categorize all stakeholder information (including inconsistent and conflicting requirements) in a way that will allow decision makers to choose an internally consistent set of requirements for the system.
What is a stakeholder?
Anyone who has a direct interest in or benefits from
the system that is to be developed.
How are they?
They are business operations managers, product managers, marketing people, internal and external customers, end users, consultants, product engineers, software engineers, support and maintenance engineers, and others.
Requirements engineering
Why is it difficult to gain a clear understanding of what the customer wants?
Ask the customer, the users, and others what the objectives for the system or product are, what is to be accomplished, how the system or product fits into the needs of the business
Elaboration
This task focuses on developing a refined requirements model that identifies various aspects of function, behavior, and information.
Validation
Examines the specification to ensure that all requirements have been stated unambiguously; that inconsistencies, omissions, and errors have been detected and corrected
Specification
A standard template should be developed and used for a specification, arguing that this leads to requirements that are presented in a consistent and therefore more understandable manner..
Negotiation
It isn’t unusual for customers and users to ask for more than can be achieved, given limited business resources. It’s also relatively common for different customers or users to propose conflicting requirements, arguing that their version is “essential for our special needs.”
FUNCTIONAL REQUIREMENTS
USER REQUIREMENTS
Are statements, in a natural language plus diagrams, of what services the system is expected to provide to system users and the constraints under which it must operate.
SYSTEM REQUIREMENTS
Are more detailed descriptions of the project functions, services, and operational constraints. Should define exactly what is to be implemented. It may be part of the contract between the system buyer and the project developers.
WHO READ THE REQUIREMENTS
DOCUMENT?
Are not usually concerned with how the system will be implemented and may be managers who are not interested in the detailed facilities of the system.
NON-FUNCTIONAL REQUIREMENTS
These are constraints on the services or functions offered by the system. They include timing constraints, constraints on the development process, and constraints imposed by standards.
FAILING TO MEET IT
Project users can usually find ways to work around a product function that doesn’t really meet their needs However, failing to meet a non-functional requirement can mean that the whole product is unusable.
IMPLEMENTATION OF THIS
A single non-functional requirement, may generate a number of related functional requirements that define new system services that are required. In addition, it may also generate requirements that restrict existing requirements.
CLASSIFICATION
External requirements
This broad heading covers all requirements that are derived from factors external to the system and its development process. These may include regulatory requirements that set out what must be done for the system to be approved for use by a regulator.
Organizational requirements
These requirements are broad system requirements derived from policies and procedures in the customer’s and developer’s organization.
Product requirements
These requirements specify or constrain the
behavior of the product.