|
Why do managers need capable architects? Because projects go wrong without them. Because capable
architects reduce the risks and costs of IS/IT work. |
|
||||
|
Conditions of use….FAQS….Feedback….Community….Value proposition….Training
for Architects….Certificates
for Architects….News…. |
|||||
|
|
|||||
|
Capable Architects assure quality |
Capable Architects manage risks |
Capable Architects help managers |
|
||
|
The shape solutions so
that ·
applications
meet user requirements, ·
business processes are
improved through better information being provided and data entry effort
being reduced, and ·
data qualities (security, integrity, etc.) are
maintained. |
They
spot and strive to resolve any risk or issue that threatens the cost or
delivery of solutions to be developed. |
To
meet IT management goals. To rationalise an enterprise’s technology and application
portfolios. To “develop, maintain, and facilitate the implementation of a sound
and integrated IT architecture” (reference below). |
|
||
|
Are your architects capable?
Do they follow best practices? Are they certificated to an industry standard? Do you want to grow your
software architects into solution and enterprise architects? Click on Training
for Architects above. |
|||||
The Clinger Cohen Act
|
|||||
|
The quote above is from the Clinger Cohen Act. The act defines
IT and IT architecture. To summarise: IT = automated data processing
resources, including applications, databases, technologies and everything
needed for IS development and IT operations. IT architecture = an integrated
framework for evolving/maintaining/acquiring IT to achieve strategic goals
and information resources management goals. |
The law
is designed to improve the way IT is acquired and managed by US federal
government agencies. However,
it captures goals relevant to IT management in all countries and in the
private sector. Capable architects help managers with several of the goals
defined in the act, which are summarised as follows. |
Follow business imperatives: The business goals come first. IT work
must map to the business mission. IT projects must start with user
requirements and end with measurable business process improvement. Improve
business processes by providing quality information to actors and reducing
data entry effort. Plan with due care: Make a business case for IT work to be
done. Plan for incremental development of IT. Offer modular contracts. Share
data processing projects and resources to accomplish shared missions.
Identify and manage IT risks. |
Manage the IT budget responsibly: Ensure money
for acquiring and managing IT work is spent wisely. Justify money spent with
reference to business cases. Manage the technology and application portfolios: Keep data
secure. Assure interoperability through following standards. Maintain a comprehensive
IT architecture repository. Follow a methodology based on best practices: Study best practices for information
resources management. Train people in them. Maintain the required skills and
capabilities. |
||