home

Articles

Blog

Books

Tools

Links

FAQ Page


Software Architect

Google
 
Web www.software-risk.co.uk

What is a Software Architect?
The term Software Architect has become a fashionable job title to have within the development teams. A lot of the time the title is quite wooly and could be more accurately described as senior developer or code guru.

Highly structured frameworks and processes have defined this term. An example it the Rational Unified Process (RUP). Thus "The Software Architect has overall responsibility for driving the major technical decisions, which are expressed as software architecture."

The rationale for such decisions is also required. There is an implicit duty on the Architect to ensure that the decisions made are actually carried out in practice.

Who is a Software Architect?
Due to the "big picture" viewpoints from which a software architect approaches his job, he has to have a good grasp of the technological issues involved in the project. Thus they tend to be experienced developers who have worked on multiple platforms and technologies.

Note that in the RUP , a role such as Software Architect does not refer to an individual. The "role" of software architect is a set of skills and competencies.

When does a Software Architect do her job?The major workload for the archictect is in the early stages of development. Here is where the large technology decisions are made. Fat/thin? SQL Server or Oracle?

In the case of the RUP, the most important phase is elaboration. The aim here is to mitigate the risk of failure through making the wrong architectural decisions. However work is still needed in Inception and Construction. Minimal work will occur in Transition.

How does a Software Architect do her job?Typical activities of the architect are to identify and document architecturally significant aspects of the system. "Significant aspects" include major requirements, design, implementation, deployment views.

The architect does need to supply the rationale and justification for her decisions. This involves juggling the concenrs of stakeholders, showing the mitigation of risk, communication and enforcement.

Related Articles
Stakeholders
Design risk
Reuters Completes VoIP Rollout
CMMI: directing implementation
CMMI: design review
Business Designer
architectural pattern
architectural baseline

Similar Areas

Software Development Items

Process Improvement Items

Software Architecture Items

Risk Management Items

Selected Books
Rational Unified Process Made Easy, The: A Practitioners Guide to the RUP

Adopting the Rational Unified Process : Success with the RUP

MCSD Self-Paced Training Kit: Analyzing Requirements and Defining Microsoft .NET Solution Architectures- Exam 70-300

UML Profile for Framework Architectures, The

Evaluating Software Architectures

Information Architecture for the World Wide Web, 2nd Edition

Real-Time Design Patterns: Robust Scalable Architecture for Real-Time Systems

Beyond Software Architecture

Keywords

major technical decisions

elaboration

inception

major requirements

design

implementation

deployment views

stakeholders

mitigation of risk

communication


See our Sarbanes-Oxley compliance, load testing and Financial Glossary pages.
Articles   Books   FAQ Page   home   Jobs   Links   Reviews Page   Tools  
Booklist   books   Measurement   Testing   Tools