|
|
|
Each of courses is workshop oriented with exercises adapted from real projects to give the attendees practical skills which they can apply immediately. The Writing Testable Requirements course is a three-day techniques and process-oriented class that focuses on problem avoidance by teaching how to write requirements correctly the first time. This course furnishes writing style guidelines for describing all types of processes and data. It also will ensure that requirements are written to a level of detail required to ensure that a sufficient set of test cases to validate the system's functionality are designed from the requirements. Writing Testable Requirements is student-paced and participants are encouraged to bring sample from their own projects to evaluate during class. The third day of the class is a working session spent on an expanded set of class exercises and/or working on requirements from the students' projects. Writing Testable Requirements-Course Description
WRITING TESTABLE REQUIREMENTS ON AGILE PROJECTS The Writing Testable Requirements course is a three-day techniques and process-oriented class that focuses on problem avoidance by teaching how to write requirements correctly the first time. This course furnishes writing style guidelines for describing all types of processes and data. It also will ensure that requirements are written to a level of detail required to ensure that a sufficient set of test cases to validate the system’s functionality are designed from the requirements. For those using Agile methodologies the course will interweave how the various topics apply in getting from User Stories to detailed Functional Specifications by the end of the release. This ensures that no technical debt is accrued from release to release. It also addresses creating an end state vision of the application’s scope giving you a portfolio view. This makes it easier to manage the master backlog. (See the detailed outline below for how the Agile topics are addressed.) Writing Testable Requirements is student-paced and participants are encouraged to bring sample from their own projects to evaluate during class. The third day of the class is a working session spent on an expanded set of class exercises and/or working on requirements from the students’ projects. Writing Testable Requirements On Agile Projects - Course Description
FINDING AMBIGUITIES IN REQUIREMENTS The Finding Ambiguities in Requirements course is a one-day process-oriented class that provides a powerful, yet practical method for ensuring that specifications are clear, concise and unambiguous. This course also teaches students to ensure that requirements are written to a level of detail required to produce a sufficient set of test cases to validate the system's functionality. The level of detail required for testing does not add anything unique to the standard for developing requirements specifications. This same level of detail is needed by all project team members who need to validate that all requirements are being addressed. Students will learn how to identify ambiguities in specifications, the ambiguity review process and how to apply the course concepts when reviewing specifications in any format. Finding Ambiguities In Requirements Course Description.pdf
The Requirements-Based Testing course is a three-day process-oriented class that provides students with a set of practical, yet rigorous techniques for testing the requirements to ensure that they are complete, consistent, accurate and unambiguous. Students will also learn how to design a necessary and sufficient set of test cases to validate that the design and code fully implement all of the functional requirements.
ACCEPTANCE TEST DRIVEN DEVELOPMENT USING The Acceptance Test Driven Development using Requirements-Based Testing (RBT) course is a three-day process-oriented class that provides students with a set of practical, yet rigorous techniques for testing the requirements to ensure that they are complete, consistent, accurate and unambiguous. Students will also learn how to design a necessary and sufficient set of test cases to validate that the design and code fully implement all of the functional requirements. The challenge for those using Agile methodologies is that the tester does not initially have a detailed specification from which to derive tests. The process is driven by User Stories. RBT is the process to use for Acceptance Test Driven Development (ATDD). It helps drive down the level of detail resulting in the tests that can act as a surrogate for traditional specifications for user reviews. From those tests a detailed set of requirements can be derived. This avoids accruing any technical debt – i.e. the degree to which the specifications, the code, and the tests are out of sync. It also avoids testing being a sprint behind the coding effort. Requirements-Based Testing Course Description The Code-Based Testing seminar presents a method called Code Analysis. This method is used to identify data flows within the program code. Code Analysis is applied to the special issues in designing test libraries that cover one hundred percent of data flows, testing asynchronous interactions, testing maintenance changes, and reverse-engineering logical rules from code. Useful methods for scaffolding code-under-test will be taught, allowing all exception handling to be tested....even those functions invoked only by error conditions within hardware and operating system software. This approach increases your code coverage by 35% to 40% over traditional statement and branch vector coverage. Code Based Testing Course Description v
|