Hi,
Most organizations have some experience gathering and documenting business and technical requirements for new and existing applications. However, reconciling these requirements to make sure that there is consistency between them is difficult particularly with free text type approaches that use techniques such as use cases or user stories. Add to this the need to have system requirements reference but not re-specify business processes, rules, events and entities already specified in the business specification and things become even more complex.
The requirements management course is designed to help organizations strengthen their requirements elicitation, documentation and analysis capabilities. This requirements management training course features facilitated workshops and mentoring activities that help refine an organizations ability to elicit, document, and trace requirements through the project life-cycle. In addition, the course focuses on the relationship between an automation specification and a business specification showing the proper way to integrate the two to avoid the duplication and rework endemic to an unintegrated approach.
The workshops and activities focus on seven requirements disciplines:
-- Introduction To Requirements Management
Requirements Management is the systematic approach to finding, documenting, organizing and tracking the changing requirements of a system. Your project team will attend a one-day seminar that introduces concepts important to successfully managing requirements throughout the entire project lifecycle.
-- Requirements Management Planning
Requirements Management Planning involves defining a requirements and documentation traceability strategy for a specific development project. Because of the uniqueness to each organization, a "one-size-fits-all" approach to requirements tracking will not suffice. The members of your team responsible for managing the project infrastructure will participate in a short requirements management planning session which will culminate in a Requirements Management Plan document that states the standards for eliciting, documenting, and tracing requirements. It will take into account existing organizational standards and documentation to describe relevant sections of the document.
-- Leveraging a Requirements Repository
If the team is planning to utilize a requirements repository, EA can help an organization configure the tool to implement the documented plan. First steps in configuring the tool, however, will be training tasks to ensure two things:
Tool Administrators are trained in configuring the tool so that the configuration and maintenance can be an ongoing task that doesn't require continued assistance.
Users of the tool will be trained in usage techniques including Requirements Documents, Importing and Exporting, "Tagging Requirements, Traceability, and Custom Views and Reports.
-- Requirements Refactoring
Once business requirements are known, they must be further analyzed and formed into requirements that are expressed in the context of the solution to be built. Further, though business requirements are expressed in the language of the business user, your development team requires specifications that are in the language of the designer and implementer. Requirements Refactoring is the evolution that the initial requirements undergo as they become realized into software and other supplemental requirements. They are the basis for the project team producing design detail and actual software components. Your team will learn how each transformation is made in an effort to make the next activities in the workflow more efficient.
-- Visioning
Facilitated learning and mentoring workshops designed to produce actual project business requirements. Workshops focus on clearly identifying the problem and its solution needs, then determining the features of the solution.
-- Use-Case Modeling
Known also as Use-Casing, facilitated workshops that enable your team to produce working use-case models that trace to the business requirements. Your team will learn how to place boundaries on the functionality that the system will display as well as the description of the user and external system interaction with the system being delivered.
-- Use Case Analysis
Facilitated learning and mentoring workshops designed to produce a project team analysis model. The analysis model incorporates various artifacts that help define how the system will realize the requirements supported by the use-case, including, but not limited to, class/object diagrams, logical user interface diagrams and sequence diagrams. The team learns how to map business functionality to responsible system or sub-system components and the system interactions between them.
And lot more factors also involved.....
i hope it might help you
R.K
Main Topics
Browse All Topics
by: TommyTupaPosted on 2006-09-05 at 20:46:45ID: 17460567
Functional Requirements answer the questions 'what is the system supposed to do' and 'how will it behave'. Business rules are constraints that help define the behavior. Example 1: Email is to be archived after 90 days. The 90 days is the business rule. Example 2: Billing Information must be stored for each contact. The fact that the record cannot be saved without billing information is the business rule.
As you are well aware requirements gathering is an art unto itself so its usually the responsibility of the vendor to do the requirements gathering then create a scope of work. Typically you'll be creating an RFP with functionality such as the one shown here:
http://www.krl.org/Know%20