This document is a step-by-step guide of modelling use case in inteGREAT. This will help you to understand how to create and model use cases in inteGREAT,how to set primary or basic flow, how to set use case properties and to associate actors.

Each step is followed by a screen shot for better understanding.
Click here to read full [...]

This article will discuss the problem of redundancy as it pertains to the requirement development, the costs associated with this problem, introduce the solution, and then show how to alleviate these redundancies, and promote requirements reuse.
It will cover and explain the problem of redundant requirements , costs associated with requirement redundancies, and compare this [...]

Let us take a step back and look at how the software application development space and the database design industry both found ways to reduce redundant data and to promote information reuse.
Legacy vs. Normalized Database Programming:
Data redundancy and repetition was a major issue in early database design. This inefficiency resulted in both performance issues, and [...]

InteGREAT Requirements Platform:
eDev Technologies has created a requirements development platform called inteGREAT. The tool allows business analysts, developers, QA teams and project managers to reuse information and produce ‘normalized requirements’. We define normalized requirements as information that is unique and does not contain any redundancy.
Reuse requirements at the application level:
Business rules and data elements are [...]

Redundancy in Requirements Definition:
Organizations define requirements on an ongoing basis. Various groups within larger organizations are redefining the same information over and over again. It is important to understand the cost associated with redundant requirement definition, and to find ways to reuse predefined requirements.

Examples of Requirements Redundancy:
1.      Business rules are redefined across multiple applications.
2.      Data [...]

The biggest challenge arises when change requests are made during the software development or UAT phase. These changes impact requirements specification,design, and coding and test documentation. Not too dissimilar from a house of cards, one significant change can jeopardize the continuity of the requirements and test documentation package.
Solution – inteGREAT:
Using the inteGREAT tool set, users [...]

Using inteGREAT would eliminate inconsistencies in requirements documentation, increase team moral, enhance maintainability, and increase team productivity. This is accomplished through requirements reuse and repurposing of requirement definitions  into diagrams and documentation.
Additional benefits are:
·    Communication is improved – information is defined within inteGREAT. Stakeholders from various teams within the organization can process and understand the information [...]