17/10/2002 Mark Carroll

Enterprise Architectures Software Quality Lighthouse or more fog ?

Welcome

Software Quality New Zealand Incorporated

www.sqnz.org.nz

17/10/2002 Mark Carroll

Enterprise Architectures Software Quality Lighthouse or more fog ?

What is an Enterprise architecture

GartnerGartner

DRAFT

17/10/2002 Mark Carroll

Enterprise Architectures Software Quality Lighthouse or more fog ?

3 Key Elements

– TimingTimingFuture Vision, RoadMap, Current Future Vision, RoadMap, Current SituationSituation

– Marriage of Business & ITMarriage of Business & IT

– Logical SubdivisionsLogical Subdivisions Including Application ArchitectureIncluding Application Architecture

17/10/2002 Mark Carroll

Enterprise Architectures Software Quality Lighthouse or more fog ?

The Application Architecture

"An investment in structural design, standards, "An investment in structural design, standards, and integration principles supported by and integration principles supported by hardware and software which is intended to hardware and software which is intended to deliver improved enterprise capabilities or deliver improved enterprise capabilities or reduce the overall costs of software reduce the overall costs of software development and operations.” development and operations.” (Gartner) (Gartner)

"An investment in structural design, standards, "An investment in structural design, standards, and integration principles supported by and integration principles supported by hardware and software which is intended to hardware and software which is intended to deliver improved enterprise capabilities or deliver improved enterprise capabilities or reduce the overall costs of software reduce the overall costs of software development and operations.” development and operations.” (Gartner) (Gartner)

17/10/2002 Mark Carroll

Enterprise Architectures Software Quality Lighthouse or more fog ?

3 Key Elements

Objectives & PrinciplesObjectives & Principles MethodologiesMethodologies

– How things are to be done.How things are to be done. Includes Standards & Frameworks (eg: MSF, Includes Standards & Frameworks (eg: MSF,

QA guidelines, Change Control)QA guidelines, Change Control)

TechnologiesTechnologies– The Technologies things will be done with.The Technologies things will be done with.

Platforms (eg: Windows, Notes, SAS) Platforms (eg: Windows, Notes, SAS) Tools (eg: VS.NET, Lotusscript)Tools (eg: VS.NET, Lotusscript)

17/10/2002 Mark Carroll

Enterprise Architectures Software Quality Lighthouse or more fog ?

As a Lighthouse - Key Facilitators

Vision for methodologies Vision for methodologies and technologies is currentand technologies is current

Sufficient stability in Sufficient stability in Internal environment in Internal environment in terms of strategy, terms of strategy, structures, systems, staff structures, systems, staff & Resources.& Resources.

Contingencies in place for Contingencies in place for threats ,opportunities & threats ,opportunities & change. (PEST)change. (PEST)

17/10/2002 Mark Carroll

Enterprise Architectures Software Quality Lighthouse or more fog ?

As a lighthouse - Key Benefits

Identifies Business benefits and hence Identifies Business benefits and hence expectationsexpectations

Provides rationale for the identification Provides rationale for the identification of critical areas for investmentof critical areas for investment

Identifies what is in and what is out Identifies what is in and what is out permitting focuspermitting focus

Continuity - every outcome is a Continuity - every outcome is a stepping stone.stepping stone.

17/10/2002 Mark Carroll

Enterprise Architectures Software Quality Lighthouse or more fog ?

As a lighthouse - Key Benefit - Focus

Training needs analysis and executionTraining needs analysis and execution– Better trained staff have a higher probability of producing better Better trained staff have a higher probability of producing better

quality softwarequality software

Resource needs analysis and Resource needs analysis and procurement and budgetprocurement and budget– Reduced risk of resource constraints on projects pushing from Reduced risk of resource constraints on projects pushing from

Time Cost onto quality.Time Cost onto quality.

Avoid distractions and dead ends.Avoid distractions and dead ends.– Wasted time debating approaches, technologies. Using a Wasted time debating approaches, technologies. Using a

mixture of technologies and methodologies increasing both mixture of technologies and methodologies increasing both project task duration's and eventually cost of ownership.project task duration's and eventually cost of ownership.

TIMECOST

QUALITY

17/10/2002 Mark Carroll

Enterprise Architectures Software Quality Lighthouse or more fog ?Application architecture - Instruments to provide

focus

Client

Lotusscript

WinForm.net

HTMLJScript

Middle Tier

WebForm.Net

Domino classes

COM Classes from …. VS;Centura;SAS; MSOffice;& others

Active Directory

Database

Sybase

T-SQL / JAVA

SAS

JAVA

ASP.NET

.NE

T C

lass

lib

rary

ADO.NET

COM

CLR

Notes Db's

MSOffice Apps COM

CLR

17/10/2002 Mark Carroll

Enterprise Architectures Software Quality Lighthouse or more fog ?

As Fog - Key Facilitators

Protracted Protracted architecture design architecture design process.process.

Short term decision Short term decision making.making.

‘‘Parental’ Parental’ interference / conflictinterference / conflict

Vendor problemsVendor problems Lack of review Lack of review

process both routine process both routine and emergencyand emergency

17/10/2002 Mark Carroll

Enterprise Architectures Software Quality Lighthouse or more fog ?

In conclusion - Main points for Software Quality

Enterprise / Application architectures can Enterprise / Application architectures can provide a focus that will help reduce cost, time provide a focus that will help reduce cost, time to delivery and increase quality. to delivery and increase quality.

Software Quality enhancing Enterprise Software Quality enhancing Enterprise architectures need architectures need – Favourable environmental conditions for initial Favourable environmental conditions for initial

development and continued growthdevelopment and continued growth– In-built contingency & change mechanismsIn-built contingency & change mechanisms

17/10/2002 Mark Carroll

Enterprise Architectures Software Quality Lighthouse or more fog ?

Parting thought

On a clear day you can see for miles and could be excused for wondering why we even need lighthouses.

But when the weather changes ……...