Page 238 - DCAP307_PLANNING_AND_MANAGING_IT_INFRASTRUCTURE

Planning and Managing IT Infrastructure

Notes 14.3.3 Step No.3 – Even if you use Proven Pattern, Write Skeleton that
Proves your Architecture

After you’ve got in mind what architecture you are going to use test it. Write simple system or
systems based on the chosen architecture to demonstrate you ideas and test those ideas against
enterprise needs. I also add checks for performance and scalability. Keep those skeletons that are
required to use in up coming steps. If your skeletons find out any problems or you find out that
one of enterprise needs, rules constraints didn’t meet, then go back to step 2.

!
Caution Don’t continue to step 4 until you are totally convinced that you meet all your
targets.
In this step we use to show our skeleton systems to several group leaders and hear what they
have to say about it.

14.3.4 Step No.4 – Write and Publish Architecture Documents and
Diagrams

This is the tedious step but important one. The output should be several diagrams that demonstrate
the architecture and documents contain every one of the architecture rules and constraints that
yield from the architecture that you chose. Try to split those rules by the viewpoint that is
mentioned in step 2. Don’t forget that your documents will be the base for designers and
developers so write them as clear as you can.

14.3.5 Step No.5 – Convince Architecture users why this Architecture is
the Right One

Convince other is the toughest step. After you sure that you finished with architecture and
published it so others can read your architecture it’s time to convince the people that goanna use
your architecture that this is the right choice. If your user doesn’t convince that you done the
right decisions they probably try to workaround your architecture. Use your skeleton system
together with a lot of patience and start convinces groups of your users that your architecture
works. Keep your mind open; if your users come up with problems that influence development
process refer that issue. If that step raise problems that needs changes in your work that you
done by now, change your work. It’s better to adjust your work to developers needs then they
won’t accept your work and won’t follow your architecture.

14.3.6 Step No.6 – Write Infrastructure that Support your Architecture

After you convince everyone that you have the right architecture it’s time to write down
infrastructure that will support your architecture (if you set MVC as visualisation pattern,
supply infrastructure that implement MVC). That infrastructure should help developers to follow
architecture with minimum effort.

Did u know? Architecture infrastructure is usually good place to implement system
infrastructure that set at engineering viewpoint.

232 LOVELY PROFESSIONAL UNIVERSITY