  Enterprise Architecture defines the overall form and function of systems
across an enterprise involving the stakeholders and providing a framework,
standards and guidelines for project-specific architectures. Project-specific
Architecture defines the form and function of the systems in a project or
program, within the context of the enterprise as a whole with broad scope and
business alignments. Application-specific Architecture defines the form and
function of the applications that will be developed to realize functionality of
the system with narrow scope and technical alignments. Because of the magnitude
and complexity of any enterprise integration project, a major engineering and
operations planning effort must be accomplished prior to any actual integration
work. As the needs and the requirements vary depending on their volume, the
entire enterprise problem can be broken into chunks of manageable pieces. These
pieces can be implemented and tested individually with high integration effort.
Therefore it becomes essential to analyze the economic and technical
feasibility of realizable enterprise solution. It is difficult to migrate from
one technological and business aspect to other as the enterprise evolves. The
existing process models in system engineering emphasize on life-cycle
management and low-level activity coordination with milestone verification.
Many organizations are developing enterprise architecture to provide a clear
vision of how systems will support and enable their business. The paper
proposes an approach for selection of suitable enterprise architecture
depending on the measurement framework. The framework consists of unique
combination of higher order goals, non-functional requirement support and
inputs-outcomes pair evaluation. The earlier efforts in this regard were
concerned about only custom scales indicating the availability of a parameter
in a range.
