Consider the most complex type: enterprise software that is an organization within an organization, having itself customers, systems and administrative functions. The world in which the enterprise’s effects will be felt, evaluated, and accepted is the customer domain containing, among other things, internal and external customers, and others systems. The enterprise interacts with its environment, the customer domain, to generate some effects and satisfy customer requirements. The interaction consists of the sharing of some phenomena, forming the interface between the enterprise and the customer domain. The external behavior of the enterprise, the interaction at the interface, is described as business requirements. There is regularity and order in the customer domain, the type of customers, their attributes and needs, and rules they go by etc that are relative unchanging. We can describe customer domain phenomenon as a theory. The theory, C, is the underlying property of the customer domain independent of the enterprise. The argument is that if customer domain has property C, by adding enterprise to the domain, customer requirements will be satisfied.

Business solution is the complete specification of business requirements, customer theory, and customer requirements. Business requirements are described as business process map defined as business solution that meets customer requirements. Customer theory unravel customer domain in its entirety including hidden aspects, hence explain and predict events in the customer domain.

In providing the business solution to our client, we help your team define project scope by analyzing customer domain to gain complete knowledge about customers and their needs. We then map out business processes that will generate effects in the customer domain whereby customer needs are met. It communicates precisely what business-needs are or cancel the project when the customer theory is not obtainable that indicts the chaotic condition in the customer domain.