Thursday, September 29, 2005

Role of BA in the system development life cycle

Role of BA in the system development life cycle

The BA plays a central role in the system development life cycle (SDLC). In general terms, the SDLC contains well-defined phases which are executed by the project team:

  • A business idea or request,
  • Feasibility (business case)
  • Planning (business requirements, functional requirements)
  • Delivery (Coding, execution of activities)
  • Testing (test cases, unit testing, integration testing, user acceptance testing)
  • Implementation (roll out of the idea or request)
  • Close out (documentation, post implementation review)

This is also known as project methodology. A version of the SDLC is part of many different Project Methodologies such as RAD, SDM, Rational Unified Process.

The BA will provide different services during the SDLC:

  • Assisting with the Business case
  • High level feasibility
  • Gathering of the requirements
  • Designing and/or reviewing test cases
  • Processing change requests
  • Tracing the requirements during implementation (traceability matrix).
  • Manage scope
  • Acceptance, Installation, deployment

Tuesday, September 20, 2005


System Development Life Cycle (SDLC)

It is used by a systems analyst/ Business Analyst to develop an information system, including requirements, validation, training, and user ownership through investigation, analysis, design, implementation and maintenance. SDLC is also known as information systems development or application development. An SDLC should result in a high quality system that meets or exceeds customer expectations, within time and cost estimates, works effectively and efficiently in the current and planned information technology infrastructure, and is cheap to maintain and cost-effective to enhance.
SDLC is a systems approach to problem solving and is made up of several phases, each comprised of multiple steps,Namely:
(Also Known as-Classic Life Cycle Model (or) Linear Sequential Model (or) Waterfall Method)

  • Requirement Gathering : The existing system is evaluated. Deficiencies are identified. This can be done by interviewing users of the system and consulting with support personnel
  • Analysis and Design : New system requirements are defined, proposed system is designed. Plans are laid out concerning the physical construction, hardware, operating systems, programming, communications, and security issues
  • Implementation and Testing: Users of the system must be trained in its use, and all aspects of performance must be tested. If necessary, adjustments must be made at this stage.
  • Deployment: he system is put into use. This can be done in various ways. The new system can phased in, according to application or location, and the old system gradually replaced. In some cases, it may be more cost-effective to shut down the old system and implement the new system all at once
  • Maintainence: Exhaustive evaluation. Maintenance must be kept up rigorously at all times. Users of the system should be kept up-to-date concerning the latest modifications and procedures.
Credits: Wikipedia,, & Ofcourse myself ;-)