Topic: Software Architecture

What is Software Architecture?

Def#1
The backbone of a software-intensive system or application, including its basic design, scalability and premise.

Def#2
The software architecture of a program or computing system is the structure or structures of the system, which comprise software elements, the externally visible properties of those elements, and the relationships among them.

Def#3
"Software architecture is the set of design decisions which, if made incorrectly, may cause your project to be cancelled."


Edited by moderator - 04May2007 at 11:26pm

Hi,

First Thing we need to see while using Water fall model is,
Wether we have clear requirements or not.
If we have clear Requirements then we can go ahead and implement waterfall model.

if we have clear requirements then,

Phase 1 -- Initial Phase --

Requirements are gatered and baselined, so that no changes are maded in later stages.

Phase 2 --- Analysis Phase ---

Software Requirements and HARDWARE REQUIREMENTS & also RESOURCE REQUIREMENTS should be planned here.

Phase 3 -- Design ---

HLD -- High Level Design
LLD-- Low Level Design

Tech leads will prepare the HLD
It will say abt the how the design flow

Phase 4 ---Coding ------

Coding will be done based on the Desin (HLD & LLD) & the Requirements.


Phase 5 ----- Testing---

Testing will be done based on the Requirements on the Code.

Phase 6 ---- Delivery & Maintaninance

Deliver of the Project or Product is planned & also Maintainance is also planned.

----------So thats how WaterFall model Works out---------


This model is an advantage model only if the Requirements are Baselined at the Phase 1.



Edited by vbob3 - 17Aug2007 at 11:31pm