Requirements Fundamentals
This Requirements Fundamentals Course provides industry terminology and lays a solid foundation for advancing your career. It will help you better understand the roles that contribute to good requirements, an iterative requirements management process, three levels and four types of requirements, as well as a proven approach to requirement activities. This course contains 8 modules, 30 lectures, 26 quizzes, 4 downloadable quick reference job aids, and over 3 hours of on demand video content.
Click on the title of the lesson that you would like to view below.
1. Requirements Fundamentals Introduction
Lessons
2. Requirements Roles
Lessons
3. The Quest for Good Requirements
Lessons
4. Requirements Hierarchy (Levels)
Lessons
5. Requirement Types
Lessons
6. Requirements Management Process Stages
Lessons
7. Requirements Quest Approach
Lessons
8. What Requirements are Not
Lessons
- Accessibility
- The extent to which the software system can be used by people with the widest range of capabilities to achieve a specified goal in a specified context of use.
- Access Security
- The extent to which the system is safeguarded against deliberate and intrusive faults from internal and external sources.
- Assumption
- An influential factor for the development of requirements that is believed to be true, but is yet to be validated.
- Availability
- The degree to which users can depend on the system to be up (able to function) during “normal operating times”.
- Business Requirement
- A specification that describes WHY the project is being done, and WHAT the project team is expected to accomplish.
- Confidentiality
- The degree to which the software system protects sensitive data and allows only authorized access to the data.
- EARV
- An acronym that represents the iterative nature of the requirements development discipline, standing for: Elicitation, Analysis, Representation, and Validation.
- EARVC
- An acroynm for the iterative process of eliciting, analyzing, representing, and validating the requirements to establish a baseline and more effectively control future changes to the requirements.
- Efficiency
- The extent to which the software system handles capacity, throughput, and response time.
- Elicitation
- Any activity, casual or structured wherein the Requirements Producer is actively working with stakeholders or business artifacts to further refine the clarity and consistency in the requirements.
- Flexibility
- The ease with which the software can be modified to adapt to different environments, configurations, and user expectations.
- Functional Requirement
- A specification that describes functionality that must be built into the system to enable the users to perform their goals or tasks. Functional requirements identify the processing that the system must perform on the inputs of information and materials to prepare and present outputs of information and materials.
- Installability
- The ease with which a software system can be installed, uninstalled, or reinstalled into a target environment.
- Integrity
- The degree to which the data maintained by the software system are accurate, authentic, and without corruption.
- Interoperability
- The extent to which the software system is able to couple or facilitate the interface with other systems.
- Maintainability
- The ease with which faults in a software system can be found and fixed.
- Modifiability
- The degree to which changes to a software system can be developed and deployed efficiently and cost effectively.
- Nonfunctional Requirement
- A specification of HOW WELL a software system must function.
- Operation
- In a classification of nonfuntional categories, a group that describes the user needs for using the functionality of a system. The user perceives the system as tool to automate tasks.
- Portability
- The ease with which a software system can be transferred from its current hardware or software environment to another.
- Reliability
- The extent to which the software system consistently performs the specified functions without failure.
- Requirement Producer
- Any individual who is responsible for capturing the requirements. In more explicit terms, the Requirement Producer is any individual who is responsible for driving the process of eliciting, analyzing, representing, validating, and managing changes to the requirements.
- Requirement Receiver
- Any individual who is responsible for developing a solution to the defined requirements.
- Requirement Supplier
- Any individual who is responsible for defining the business and user needs to be satisfied.
- Requirement Supporter
- Any individual who is responsible for assisting the Producers, Suppliers, and Receivers in applying the requirements management process. The Requirement Supporters review the requirements, as well as the requirements approach, to offer suggestions for improvement on future project efforts. That is, they are process champions and support the activities of the process and look for ways to improve the process.
- Requirements Analysis
- The process of analyzing the information elicited, resolving conflicts, documenting assumptions, constraints, and dependencies, and working with the stakeholders to establish priorities.
- Requirements Change Control
- The process of maintaining a set of approved or baselined requirements throughout the lifecycle of the development project.
- Requirements Elicitation
- The process of identifying stakeholder classes, defining the project scope, identifying requirement sources, and applying techniques to gather the information.
- Requirements Representation
- The process of specifying the business needs using a combination of graphical models and textual documents.
- Requirements Validation
- The process of reviewing the represented information with the stakeholders for quality characteristics such as completeness, correctness and feasibility.
- Reusability
- The extent to which a portion of the software system can be converted for use in another system.
- Revision
- In a classification of nonfuntional categories, a group that describes the user needs for changing source code or data that drive the system. The user perceives the system as a set of programmed language statements.
- Safety
- The degree to which a software system prevents harm to people or damage to the environment in the intended context of use.
- Stakeholder
- In the context of requirements management, any individual that a Requirement Producer (for example, business analyst) is likely to engage with directly or indirectly during the requirements development and management processes.
- Scalability
- The degree to which the system is able to expand its processing capabilities upward and outward to support business growth.
- Stakeholder Profiling
- In requirements management, a technique for identifying the topics of expertise, the stakeholders who have proficient and expert-level knowledge of the topics of expertise, and a tool for planning the engagement of stakeholders.
- Subject Matter Expert (SME)
- A person that beholds an immense amount of knowledge about a single subject, and can therefore be considered an expert.
- Survivability
- The extent to which the software system continues to function and recovers in the presence of a system failure.
- Transition
- In a classification of nonfuntional categories, a group that describes the user needs for managing the upkeep of the software. The user perceives the system similar to hardware.
- Usability
- The ease with which the user is able to learn, operate, prepare inputs, and interpret outputs through interaction with a system.
- User
- In the context of software requirements, anyone who affects or is affected by the system under development. A user is anyone or anything that provides inputs to the system and receives outputs from the system.
- User Requirement
- A specification that describes user goals or tasks that the users must be able to perform through interaction with the system.
- Verifiability
- The extent to which tests, analysis, and demonstrations are needed to prove that the system will function as intended.
Four Core Models for Scoping Requirements
Do you want to feel confident that you haven’t missed requirements? In this course you will learn how to illustrate various aspects of requirements scope utilizing the following diagrams: Relationship Map, Use Case Diagram, Context Diagram, and Process Map. This course includes 6 modules, 21 lessons, 21 quizzes, and over 2 hours of videos content.
Nonfunctional Requirements
Learn how to better elicit the complex and often overlooked nonfunctional requirements through gaining a better understanding of these requirements. In this course you will learn how to categorize and elicit nonfunctional requirements more effectively. This course includes 5 modules, 32 lectures, 32 quizzes, and nearly 5 hours of videos content.
Stakeholder Profiling
Learn how to more effectively identify, negotiate for, and engage the necessary stakeholder resources for your next project through the power of stakeholder profiling. This course includes 9 modules, 31 lectures, 20 quizzes, 3 downloadable quick-reference job aids, 2 hours of on-demand videos, and a complimentary PDF of ‘Chapter 2: Involve the Right Stakeholders’ from Roxanne Miller’s book The Quest for Software Requirements.
Stakeholder Profiling
Learn how to more effectively identify, negotiate for, and engage the necessary stakeholder resources for your next project through the power of stakeholder profiling. This course includes 9 modules, 31 lectures, 20 quizzes, 3 downloadable quick-reference job aids, 2 hours of on-demand videos, and a complimentary PDF of ‘Chapter 2: Involve the Right Stakeholders’ from Roxanne Miller’s book The Quest for Software Requirements.
Stakeholder Profiling
Learn how to more effectively identify, negotiate for, and engage the necessary stakeholder resources for your next project through the power of stakeholder profiling. This course includes 9 modules, 31 lectures, 20 quizzes, 3 downloadable quick-reference job aids, 2 hours of on-demand videos, and a complimentary PDF of ‘Chapter 2: Involve the Right Stakeholders’ from Roxanne Miller’s book The Quest for Software Requirements.