Software requirements engineering is the process of determining what is to be produced in a software system. It has the widely recognized goal of determining the needs for, and the intended external behavior, of a system design.
The four specific steps in software requirements engineering are: requirements elicitation, requirements analysis, requirements specification, and requirements validation. The importance of high quality software requirements, long recognized as the foundation from which all software work follows, cannot be overstated. Arriving at a shared vision of the product to be developed is one of the greatest challenges facing the software project team, and customer involvement is among the most critical factors in software quality. This course will give participants a number of best practices, based upon the Software Engineering Body of Knowledge (SWEBOK), so that they can improve the quality of the requirements elicitation and development process in their organization. Characteristics of high quality requirements specifications are completeness, conciseness, accuracy, modularization, prioritization, analysis, and verification. Ultimately, the techniques presented reduce project risk, improve product quality, and allow for effective control of requirements volatility – all measures for increasing the likelihood of a successful software project.

Format: Asynchronous
Nominal duration: Self-paced Learning – Approximate Time: 4 hours
Professional Development Hours (PDH) : 4
Continuing Education Credits (CEU) : 0.4

This course is frequently bought together with exam:
Software Requirements Course & Exam Bundle

Upon completion of this course, the student will be able to:

1. Develop effective functional and non-functional requirements that are complete, concise, correct, consistent, testable and unambiguous.
2. Select the appropriate requirements elicitation techniques to identify requirements.
3. Design a set of software models to be used to flesh out hidden requirements and drive clarity into the system functional requirements
4. Effectively analyze requirements and prioritize accordingly.
5. Perform requirements engineering in the context of the most common software development life cycles and processes.
6. Create a requirements specification to communicate requirements to a broad set of stakeholders.
7. Utilize various requirements validation techniques to critically evaluate their requirements to identify defects
8. Manage change to requirements