Agile Model || Information System Development || Bcis Notes

Agile Model

Agile Model is a very important software development life cycle models. Agile SDLC model is a combination of iterative and incremental process models with a focus on process adaptability and customer satisfaction by rapid delivery of working software products. Agile Methods break the product into small incremental builds. These builds are provided in iterations. The different phases of the agile model as are:

The Agile Model || Information System Development || Bcis Notes

  • Planning
  • Requirements Analysis
  • Design/Development
  • Unit Testing and
  • Acceptance Testing


  • Agile planning is a project planning method that estimates work using self-contained work units called iterations or sprints. Sprints are periods of 1-3 weeks in which a team focuses on a small set of work items, and aims to complete them.

Requirements Analysis

  • Requirements analysis focuses on the tasks that determine the needs or conditions to meet the new or altered product or project, taking account of the possibly conflicting requirements of the various stakeholders, analyzing, documenting, validating, and managing software or system requirements. Requirements analysis is critical to the success or failure of a systems or software project. The requirements should be documented, actionable, measurable, testable, traceable, related to identified business needs or opportunities, and defined to a level of detail sufficient for system design.


  • It is the most crucial phase in the development of a system. The logical system design arrived at as a result of system analysis and is converted into physical system design.

A Unit testing

  • A unit test, as Agile teams understand the term, is a short program fragment written and maintained by the developers on the product team, which exercises some narrow part of the product’s source code and checks the results.

Acceptance testing

  • Acceptance testing. is a term used in agile methodologies, such as Extreme Programming, referring to the functional testing of a user story by the software development team during the implementation phase. The customer specifies acceptance criteria for a given story to be implemented.

You may also like The V-Model 

Be the first to comment

Leave a Reply

Your email address will not be published.