 |
|
Project managers, business analysts, software engineers, software developers, technical leads, requirements analysts, user representatives, technical writers, software quality assurance professionals any stakeholder engaged in eliciting, documenting, analyzing or managing software requirements.
|
|
Course Description
Requirements creep. Gold-plating. Unmanageable change requests. Requirements defects compounded in design and coding stages. These commonly experienced and costly issues in software development stem from a single source: unsuccessful elicitation of software requirements. 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. [Karl Weigers] This course will give participants a number of best practices, reinforced with exercises, so that they can improve the quality of the requirements elicitation and development process in their organization.
Characteristics of high quality requirements specifications are presented those that are complete, concise, accurate, modular, prioritized, analyzed, verified and testable. 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.
Upon completion of this course, the participant should be able to:
- Recognize and classify different types of requirements information
- Select and apply best practices for requirements elicitation, analysis, specification, validation, and management
- Critically evaluate requirements statements for ambiguity and other problems
- List the product, project and people competencies, from the Software Quality Institute (SQI) Body Of Knowledge (BOK), that are necessary for successful requirements gathering
- Describe requirements management in connection to the SEI CMM
- Describe Critical Success Factors and how they apply to software requirements
- Describe the criticality of accurate requirements elicitation for the success of software development
- Identify the characteristics of a well-written requirement (e.g., primitive, testable)
- Execute Interviewing, Brainstorming, Mind Mapping, FAST, JAD and Use Case techniques for eliciting requirements
- Discuss the challenges of gathering software requirements
Drawing upon recognized experts in the field, the participant will learn:
- How to gather and analyze software requirements, from G. Weinbergs published steps of Problem Recognition (discovery, gathering); Refinement (evaluation, synthesis); Modeling (paper, prototype); Specification (packaging, SRS); and Review (inspection, gate).
- How to understand what the customer wants, per Roger Pressman, with discussions on requirements analysis and negotiation (analyzing need, negotiating a reasonable solution).
- How to effect win conditions, per Barry Boehm. Negotiation, mutual gain, trade-offs and win-win agreements apply when prioritizing requirements and preparing them for the specification activities.
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. This process is regarded as one of the most important parts of building a software system. The four specific steps in software requirements engineering are: requirements elicitation, requirements analysis, requirements specification, and requirements validation.
This course will cover:
- Definitions What is a Software Requirement?
- Types of Software Requirements
- What Makes a Good Software Requirement?
- Requirements Elicitation Methods
- Interviews
- Brainstorming
- Mind Mapping
- Facilitated Application Specification Techniques (FAST)
- Joint Application Design
- Use Cases
- Guidelines for Writing Quality Requirements
- Challenges in Eliciting Requirements
- Requirements and Quality Function Deployment
- Prioritization of Requirements and Feature Sets
Benefits: Participants will learn practical and effective techniques for eliciting and capturing requirements. They will be able to: distinguish worthy requirements from those that are not high quality; classify and prioritize requirements; and assess the state of their organizations existing practices. Practice with hands-on exercises, based on a case study and led by an instructor, will illustrate strategies for success.
This course in Software Requirements Elicitation Complements all other courses in the SQI curriculum. It is particularly useful when taken with:
- Creating a Software Requirements Specification
- Essentials of Software Engineering (problem solving, using both process and data views of a system, structured and Object-Oriented techniques for modeling requirements, software design concepts, and software estimation).
Contact Information
Theresa
Dobbs
Sr. Manager
tdobbs@mail.utexas.edu
(512)
471-4875 |
Course Location
J. J. Pickle Research Campus
Commons Building, Room 1.112G
10100 Burnet Road
Austin, TX 78758
Telephone: (512) 471-5898
Fax: (512) 471-3679
For a map and information on
parking, visit this link. |
|
Attendance Policy
A 90% attendance rate is required in order to earn Continuing Education Units (CEUs) and certificates of completion.
|
Cancellation Policy
A full refund, less a $100.00 processing fee, will be given for all cancellations or transfers if notification is received on or before two weeks prior to the beginning of the course. Refunds will not be given for cancellations received after this date. Substitutions may be made anytime prior to the first day of class. The CLEE programs are subject to cancellation if too few people enroll, in which case a full refund will be given.
|
|
Hotel Information
|
Payment Policy
The Center for Lifelong Engineering Education policy states that as of January 2010, the payment due date for all courses is two weeks prior to the class start date. Full payment must be received prior to attending the class. The exceptions to this rule are individuals attending on a company-generated purchase order (PO) or state employees. These individuals need to identify themselves as such and provide appropriate supporting documentation. The final opportunity to gain entry to the course will be to make full payment on-site during check-in on the first day of class.
|
|
