Page 237 - DCAP307_PLANNING_AND_MANAGING_IT_INFRASTRUCTURE

Unit 14: Enterprise Architecture

Notes
Example: Such a list could contain the following points:

 Our goal is to develop competitive intelligent system of systems (SOS) to enable enterprise
to be aware of potential threats.
 Every system represents one entity in our competitive intelligence SOS.

 Every system (entity) build from 3 layers (Visualisation, business logic and data provider).
We want any system to supply and consume every one of those layers from/to other
systems.

 Enable the user to show different entities visualisation on single page is a must. User can
add visualisation layers of entities dynamically.

 Other entities (systems) should be added to SOS with minimum work.
 From the user point of view, he is working against one system. He doesn’t care that
systems develop by different development groups.

 All systems should be available 24*7. Even in maintains process.
 We want to minimise deployment of software to user’s station.
 Systems should be followed the same development paradigm and system flow in order to
enable using and adding infrastructures services.

 Systems and infrastructure should be based on Microsoft solutions.

14.3.2 Step No.2 – Set Architecture

In this step you should follow one of the architecture frameworks in order to create match
architecture. Usually, most of the framework split this work into several viewpoints. Every
viewpoint set different aspect of the architecture and usually every viewpoint is depending on
the previous viewpoints. Most infrastructure split architecture into five viewpoints:

1. Business – Which we already describe.
2. Information – this viewpoint deals just with the data aspects of your architecture. In that
viewpoint you should set which data your architecture should address (data storage, state
data, transactions, etc’) and how you decide to achieve it (relational DB, OODB, ORM,
optimistic lock, etc’).

3. Computational – Here you need to decompose needed functionality and build components
that should perform needed functionality.
4. Engineering - This view point should set given architecture needed to create components
and where every component should work eventually (layers, nodes and physical position).
5. Technical – Just in the end of the process after information, Computational and engineering
set up it’s time to decide which tools we should use in order to fulfil the previous
requirements (Oracle, SQL Server, cache AB, Java spaces, etc).
In this step we usually use to go through proven architectural patterns in order to find the right
architecture for the given need with respect to business needs, rules and constraints. One piece
of advice, use just proven patterns. Don’t tempt to use patterns that not used in production – real
life systems, even if you convinced that this architecture pattern match perfectly your needs.
Using non-proven patterns could cost you a lot in developing stage.

LOVELY PROFESSIONAL UNIVERSITY 231