3.1 Comprehensive Method

	The architectural aspects of a software application to some extent at a fairly high level or from a restricted
	perspective.

	The necessity of a comprehensive approach to architecting the end-to-end distributed solutions becomes more
	and more evident, demanding a systematic disciplined way.

	To facilitate the creation, organization, and management of the architecture assets and solutions at different
	levels in a large organization, design procedures are established.

	Design philosophy includes design principles, part of which were adapted from TOGAF (The Open Group) but
	significantly are modified/expanded to be tailored to the services-oriented distributed application development
	process:

		Business Principles: Primacy of principles, Maximize benefit, Active engagement, Compliance with
		regulations, IT accountability, Innovations.

		Technical Principles: Flexibility, Responsive change management, Requirement scope control, Technology
		standardization, Interoperability.

Solution Principles: Ease of use, Technology independence, Common services and components.

3.1 Comprehensive Method

		Data Principles: Data asset, Data ownership, Common vocabulary and meta-data, Shared data, Data
		access, Data security.

		Service Principles: Encapsulation, Loose coupling, Contract, Reusability, Composability, Autonomy,
		Statelessness, and Discoverability.

General Approach:

The Model-centric Architecting Process (MAP) is designed in this work as a multi-disciplinary approach.

		It defines a comprehensive method to control the application design and development practices for the
		quality delivery of information systems.

		The MAP framework is a holistic discipline to help analyze and strategize the thought process, methods,
		trade-offs, and patterns in the architecture design.

		MAP forms a common baseline to implement service-oriented architecture, integration, process and
		management in information systems.