Sunday, November 27, 2005

Software Construction Methods

yeah now lets get back to business and talk stuff related to job and BA's rather then discussing things a BA should know or shouldnt.. i am sure anything mentioned here wont harm a BA. I know that even if a BA doesn's even know all these stuff he can survive.. yeah he can survive in IT industry alright/... but well never mind.. lets talk about software construction methods :

To mention a Few related to and important for BA's :

  • Waterfall Method
  • Rational Unified Process (RUP)
  • RAD methodology
  • Synchronize & Stabilize Methodology
  • Prototype Model

Waterfall Method :
Here development is seen as flowing steadily downwards (like a waterfall) through the various phases of (SDLC) requirements analysis, design, implementation, testing (validation), integration, and maintenance. The term was introduced in 1970 by W. W. Royce; ironically, Royce himself advocated an iterative approach to software development. Royce originally proposed what is now known as the waterfall model as an example of a system that he argued "is risky and invites failure"

The following phases are followed PERFECTLY in order in waterfall method:

1. Requirements specification

2. Design

3. Construction (aka: implementation or coding)

4. Integration

5. Testing and debugging (aka: verification)

6. Installation

7. Maintenance

Anyhow this method has recieved severe crticism, just follow a couple of links to know how much people love (?) Waterfall... (seems this waterfall has made a lot of people wet ;-) )

Do read them.. even if one loves it or hates it.. one should surely know what are the aspects that could be be crticised or appreciated... what say..

enough blogging for the day.. or night? yeah pretty late.. lets call it a night


Post a Comment

<< Home