|
At Turner
Software & Services,
we prefer to take an
architectural view of your business. When you begin with a
Technical Architecture, you consider the business reasons
for an implementation project. We develop the
essential blueprint to insure your computing resources are
being used to solve your actual business issues.
(Click on picture for a larger
image)
This process allows all
stakeholders to express their needs and concerns about the
use of technology in the business. It also provides the
developer an opportunity to become intimately familiar with
the business environment and any technical issues that might
surface.
In building a Technical
Architecture, we begin with your key business drivers to
identify goals, principles, models and standards for using
Information Technology in your business. Four views are
developed to fully explore your project from a business,
functional, technical and implementation perspective. These
views answer the key questions of strategic planning for
systems implementation:
- The Business View: Why do we need a system to be
developed?
- The Functional View: What does the system need to
accomplish?
- The Technical View: How will the technology be used to
accomplish its results?
- The Implementation View: With what tools and
technologies will the system be developed?
In each view, guiding principles lead to rationales,
implications, obstacles and actions. The information
gathered in each view leads logically to produce the guiding
principles for the development of the next view. This
process results in a Technical Architecture which is used to
direct the development of a business solution.
A Technical Architecture is like a blueprint for building
your system. With it, the implementation team will have a
set of unambiguous instructions for putting your system
together. If during implementation, any practical details
cause a change in the plans, the architecture is easily
updated to reflect the changes. The chain of justification
for each implementation detail is clearly laid out based on
your original business drivers. If your assumptions change,
it is easy to see what impact it will have on systems
development. |
