The RAVEN Blog

Once all the project requirements have been successfully elicited, specified, and confirmed, you need to keep track of them throughout the development process to ensure they are being implemented in accordance with business needs. While in a perfect world all requirements would be 100% accurate and could be implemented exactly as specified, the reality is that changes will occur and you must be prepared to deal with them. This means having a way of identifying and organizing the requirements so you can maintain control as changes begin to surface, and can quickly trace the changes back to the original requirements and verify they are acceptable to stakeholders. It also means making sure that accepted changes are reflected in all the project documentation so you have a complete history available for future reference as necessary.

In this webinar you will learn how to:
• Identify, organize, and manage the project requirements
• Track the implementation status of requirements under development
• Review and process requirements changes made during implementation
• Update requirements documentation and other artifacts to reflect changes
• Facilitate end-user acceptance testing of the completed software application

Watch it now!

Before they are implemented by the development team, you ask the stakeholders to review and confirm that the project requirements are clear, complete, and accurate. This activity is either performed by having stakeholders individually review and comment on the requirements artifacts and specification documents, or by scheduling and facilitating requirements review meetings with groups of stakeholders. Regardless of the approach, the goal is to validate that your understanding of the requirements are correct and, if not, to update them accordingly.

In this webinar you will learn how to:
• Plan requirements review sessions with end users and stakeholders
• Prepare requirements review packages for delivery to the review team
• Facilitate requirements review sessions or monitor independent reviews
• Collect and selectively incorporate feedback from reviewers
• Secure requirements sign-off or approval from key project stakeholders

Watch it now!

After the requirements elicitation meetings, you spend time compiling, analyzing, and organizing your notes so you can flesh out the requirements in more detail. This is when you finalize the glossary of business terms for the project, model business processes and use cases, generate visual diagrams, and define both the functional and non-functional requirements associated with each capability. These detailed requirements also include business rules to be enforced or screen mock-ups that give end users a sense of how the application will look. Finally, in this phase you take what you’ve defined and produce detailed requirements specifications.

In this webinar you will learn how to:
• Create sharable glossary of business terms, including actors and objects
• Model business processes, business use cases, and system use cases
• Define requirements associated with business processes and use cases
• Analyze and refine business processes and use cases as required
• Develop and publish requirements specifications and other documents

Watch it now!