This week's book giveaway is in the JavaFX forum.
We're giving away four copies of Introducing JavaFX 8 Programming and have Herbert Schildt on-line!
See this thread for details.
The moose likes Agile and Other Processes and the fly likes Architecture and SDLC Big Moose Saloon
  Search | Java FAQ | Recent Topics | Flagged Topics | Hot Topics | Zero Replies
Register / Login

Win a copy of Introducing JavaFX 8 Programming this week in the JavaFX forum!
JavaRanch » Java Forums » Engineering » Agile and Other Processes
Bookmark "Architecture and SDLC" Watch "Architecture and SDLC" New topic

Architecture and SDLC

Pradeep bhatt
Ranch Hand

Joined: Feb 27, 2002
Posts: 8927

Hi all,
During which phase of the SDLC does an Architect start off his/her job?

Lasse Koskela

Joined: Jan 23, 2002
Posts: 11962
During which phase of the SDLC does an Architect start off his/her job?
According to which process?

Author of Test Driven (2007) and Effective Unit Testing (2013) [Blog] [HowToAskQuestionsOnJavaRanch]
Valentin Crettaz
Gold Digger

Joined: Aug 26, 2001
Posts: 7610
Please have a look at the following article by Martin Fowler : Who Needs an Architect?.
It provides an excellent view of what an architect is and what architecture REALLY is, i.e. somebody who makes a bunch of design models in UML is NOT an architect.

[Blog] [Blogroll] [My Reviews] My Linked In
Pradeep bhatt
Ranch Hand

Joined: Feb 27, 2002
Posts: 8927

Originally posted by Lasse Koskela:
According to which process?

Stan James
(instanceof Sidekick)
Ranch Hand

Joined: Jan 29, 2003
Posts: 8791
In RUP you look at architecture very early. Some of the most basic business requirements go right to architecture ... "Users include sales agents on the road in 50 states" tells you something very important day one. Architectural proofs can begin as soon as you think you know something like that. See Scott Ambler's modified lump chart or whale chart . That early "implementation" activity is architecture spikes.
XP is into early architectural spikes, too, but it also talks a lot about deferring architecture decisions and letting it emerge. (No conflict - defer the decision, then spike the decision to make sure it works.) That's mostly a great idea (note: I'm agreeing here!) but XP is about generating code and doesn't often mention dependencies on other people. If it's going to take the network engineers months to get an infrastructure set up, you better think about it early!

A good question is never answered. It is not a bolt to be tightened into place but a seed to be planted and to bear more seed toward the hope of greening the landscape of the idea. John Ciardi
I agree. Here's the link:
subject: Architecture and SDLC
It's not a secret anymore!