Admin
Moderator
Registered: Sept 18, 2007
Posts: 80
|
|
| |
Reply with quote | #1 |
Requirements Analysis
Getting the Requirements Right
Failure to obtain accurate and complete business requirements has long been the sour note of application development. Lack of communication between the developers and business users leads to more project failures than any other single cause. Metastorm's model driven solution for requirements analysis can change that.
Metastorm ProVision® enables business and IT teams to establish consensus on how business processes should work, which business processes are best served through automation, and how technology will support those business processes. It includes detailed business models that eliminate ambiguity and provide a clear, detailed definition of business requirements. The resulting model-based deliverables are a reliable basis for designing an automated solution.
Before your organization launches its next package selection, implementation or upgrade, make sure you identify the right requirements. Metastorm ProVision will significantly reduce requirement errors and thus improve software quality.
Who does Requirements Analysis?
* System Engineers
* Business Analysts
* Developers
* Project Leaders
* Product Managers
* Design Engineers
Top 10 reasons to use Metastorm ProVision for Requirements Analysis:
1. No requirements modeling tool is easier to use! Your requirements modeling tool most likely will be used by the same analysts who use MS Office. Metastorm ProVision was designed to be intuitive for MS Office users. The portal, a powerful and easy-to-use graphical user interface for Metastorm ProVision, provides an intuitive way to graphically model and gather requirements from multiple perspectives.
2. Metastorm ProVision models provide the most effective method for gathering, visualizing and analyzing business requirements. This is further enhanced by Metastorm ProVision's ability to manage objects across models and create associations between various object types. Powerful association matrices can also display and manipulate associations between any two object types.
3. With Metastorm ProVision you see the big picture. You can define and analyze the entire requirements business domain. Metastorm ProVision contains a powerful “interpreter” which translates any model into simple English at the click of a mouse.
4. Put your requirements in class by themselves. Metastorm ProVision describes the information for a given business domain as a set of business classes. Using the Business Class Model these classes can be structured into a representation of how they fit relative to other classes in the domain. The Business Class Model also shows the three types of properties for each business class: its associations, attributes, and operations.
5. Just identifying the information is not enough. An understanding of the changes that business undergoes requires a Statechart Model. With the Statechart Model an analyst can focus on a particular business class and illustrate its lifecycle. The Statechart Model allows an analyst to depict the major stages (states) that an instance of the business class can experience, the allowable transitions between states, and the operations that transition the instance from state to state.
6. Tie information changes to business activities. Metastorm ProVision can define operations that bring about the state changes related to a business class. This provides analysts with the ability to link operations associated with each class directly to one or more activities, or link multiple business classes to a single activity through a sequence model, which describes a series of operations across of classes.
7. Automation is the key. Business activities described in Metastorm ProVision can be extended to show the specific user interfaces required to access a proposed system as well as the navigation between them. These user interfaces can also be extended to show interface mockups or images of the actual interfaces to assist in system design and documentation. Interfaces between systems can also be described using the communication model.
8. Flexibility as a rule. By using the rule object and model, business rules can be captured, organized and associated with any Metastorm ProVision object.
9. Put your requirements on a firm foundation. Metastorm ProVision provides an instrument to define and model requirements related to infrastructure components in the form of facilities, equipment and technologies.
10. The key factor in assuring requirement accuracy is visibility. Metastorm ProVision models and interpretations can be published as HTML files that can be viewed interactively by all team members. The information captured in Metastorm ProVision can also be used to facilitate training during implementation.
|
| Loading... | | |
http://www.websitetoolbox.com/tool/view/mb/external/provision
