Chrysalis Solutions, Inc.
Home About Why CS Services Delivery Clients Contact
Systems Development Life Cycle - Waterfall Model
Systems Development Life Cycle - Waterfall ModelWe deliver our products and services and our clients' systems using Waterfall model of Systems Development Life Cycle (SDLC). Typically the full cycle of Waterfall involves the following phases: Initiation and Planning, Requirements Gathering and Systems Analysis, Systems Design, Implementation, Integration and Testing, Acceptance and Deployment, and Maintenance.
  • Initiation and Planning: Establishes a high-level view of the intended project and determines its goals.
  • Requirements Gathering and Systems Analysis: Defines project goals into defined functions and operation of the intended application. Analyzes end-user information needs.
  • Systems Design: Describes desired features and operations in detail, including screen layouts, business rules, process diagrams, pseudocode and other documentation.
  • Implementation: The real code is written here.
  • Integration and Testing: Brings all the pieces together into a special testing environment, then checks for errors, bugs and interoperability.
  • Acceptance and Deployment: The final stage of initial development, where the system is put into production and runs actual business.
  • Maintenance: What happens during the rest of the system's life: changes, correction, additions, moves to a different computing platform and more. This goes on seemingly forever.
Systems Development Life Cycle - Agile Model
An Agile model of SDLC often works best in the fast paced and frequent changing and improving environment. The core focus is focus on being iterative and collaborative. The high-level Agile life cycle is as follows:
  • Iteration -1: Select the project (pre-project planning).
  • Iteration 0 (Warm Up): Initiate the project.
  • Construction Iterations: During the Construction Iterations, we deliver high-quality working system which meets the changing needs of our clients.
  • Release Iterations (End Game): During the Release Iterations, also known as the "end game", we transition the system into production.
  • Production: The goal of the Production Phase is to keep systems useful and productive after they have been deployed.
  • Retirement: The goal of the Retirement Phase is the removal of a system release from production, and occasionally even the complete system itself, an activity also known as system decommissioning or system sunsetting.
Systems Development Life Cycle - Agile Model
Systems Development Life Cycle - Iterative Model
An Iterative model is developed in response to the weaknesses of Waterfall model. It starts with an Initial Planning and ends with Deployment with the cyclic interactions in between. An Iterative model consists of repeating the following phases in sequence: Systems Development Life Cycle - Iterative Model
  • Planning and Requirements:  Project scope is identified. Requirements are gathered and analyzed. Iteration should eventually result in a Planning and Requirements phase that produces a complete and final specification of requirements.
  • Design and Implementation:  A working architecture is delivered. A solution to meet the requirements is designed. This may be a new design, or an extension of an earlier design.
  • Deployment and Test:  The system is coded, integrated and tested from analysis, design, implementation, and testing of the functional requirements..
  • Review and Evaluation:  The system is evaluated, the current requirements are reviewed, and changes and additions to requirements proposed.
Rapid Application Development
When our clients require faster development and delivery of the systems, we also have the experience with Rapid Application Development (RAD) methodology. Instead of full cycle of SDLC, RAD focuses on building applications in a very short amount of time; traditionally with compromises in usability, features and/or execution speed.

The full lifecycle stages of RAD we typically use include Requirements Planning, User Design, Construction and Implementation. Also described are typical Pre- and Post- Project Activities.
  • Pre-Project Activities:  As with any project it is vital to identify the details of the project in some form of document such as a Project Management Plan (PMP). Some details are determined and approved by our clients at this stage, such as strategies, development schedule, deliverables, standards, tools and technologies to be used, desired end result, and financial considerations including budget and cost of tools.
  • Requirements Planning:  Also known as the Concept Definition Stage, this stage defines the business functions and data subject areas that the system will support and determines the system's scope.
  • User Design:  Also known as the Functional Design Stage, this stage models the system's data and processes and to build a working prototype of critical system components.
  • Construction:  Also known as the Development Stage, this stage completes the construction of the physical application system, builds the conversion system, and develops user aids and implementation work plans.
Rapid Application Development
  • Implementation:  Also known as the Deployment Stage, this stage includes final user testing and training, data conversion, and the implementation of the application system.
  • Post-Project Activities:  Final deliverables are handed over to our clients and such activities are performed that will benefit future projects. Specifically it is our best practice to review and document project metrics, organize and store project assets such as reusable code components, Project Management Plan, User Design Specs and User Manual.
 Copyright © 2011-2012 Chrysalis Solutions, Inc. All Rights Reserved.
Chrysalis Solutions, Inc. | 410 Westchester Avenue, Suite 101 | Port Chester, NY 10573 
Telephone: (917) 470-3367 | Facsimile: (801) 922-2897 | Email: 

Web Designed and Developed by Chrysalis Solutions, Inc.