A large number of information technology implementations either do not meet the end-users' business requirements, do not fit into the company's IT infrastructure or in the worst case scenario are never finished. To avoid such problems, the software industry has adopted the notion of a software engineering lifecycle. The heart of the lifecycle is the identification of the functions, tasks and performance criteria for the planned system known in the industry as the Requirements Definition.

Creating a custom application requires a disciplined approach similar to that required for designing a large building or an airplane. Concepts and ideas must be translated into formats that can be used by skilled craftsman. Building an airplane or large building requires highly detailed blueprints and architectural design documents. The building of a software application requires no less.

The development of the blueprints for software applications is the most important part of a systems project. If the blueprint is flawed the finished product will be flawed. The blueprint must reflect the expectations and performance requirements of the customer.

Consilium has refined its approach for the development of software building blueprints over many successful engagements. Consilium works closely with the customer to define and facilitate Joint Application Development (JAD) sessions to create a project environment that engages the stakeholders in each stage of design to develop the following system building products:

• Overall Business Description
• Business Process Models
• Entity Relationship Diagram
• Matrix of System Roles, Responsibilities and Access

In the end, spending a significant amount of time on gathering business requirements reduces the overall project timeline.