Gaffr.net takes the guess work out of constant change

Gaffr.net is a repository builder used by enterprise- and information architects to document the collected knowledge about what it is that make a business tick.

Having a documented repository off all the assets in form of processes, information, taxonomy, information-use per process step and the rules that control the dynamics of the information is desired in most businesses. To keep this ever changing web of information up to date used to be hard work; Gaffr.net solves this and will let you take control.

With Gaffr.net you catch the basic business processes - naming them and defining their steps so that everyone can see and start to use the terminology when formulating requirements.

With Gaffr.net you build class models that define the information used by the organization in UML class diagrams. You can add rich text documentation for all artifacts so that the Gaffr.net model can act as the dictionary and taxonomy for the business. This will enable your stakeholders to share a common language - the first step for communication.

With Gaffr.net you define the state machines that describe the dynamic behavior of your information. Gaffr.net let you define guards and effects in object constraint language (OCL).

With Gaffr.net you can define how the information is used by a user interface (UI) that solves a use case. Not only does this make it easier for non developers to say "yes" or "no" to solutions, but it also remove all uncertainty otherwise left to implementers.

With Gaffr.net you can execute your model and let users test run their requirements.

Having an up to date idea on how your business work is just common sense. How do you solve this today? If you do not; is it not very hard to know how proposed changes will affect the rest of the business?

When a requirement state that you should add, drop or change a piece of information how do you know what processes that will be affected?

When you have your business modeled in Gaffr.net you will see all associations between information and processes and you will know instantly if a requirement is realistic or not and what effect it will have.

DOWNLOAD

If you cannot model a specification with Gaffr.net you should not send it to production. If you can model the specification with Gaffr.net use ECO to produce.