Ecotech Delivery Model around the basic SDLC

Ecotech delivery processes, using the basics of standard SDLC model, has evolved over a period, through developing delivering projects successfully – tailor made for various project sizes, for different clients spread across the world, using suitable project management methodologies, meeting varying business needs and budgetary expectation levels of clients.

All our delivery models take the following base factors into consideration:

• Project Size and commitment from client
• Client’s Business objectives and budgetary constraints
• Time available for Go to market

 
 
 
 
 

Ecotech Delivery Model involves the basics of Software Development Life Cycle (SDLC) Process and the Testing Life Cycle (TLC) Process.

The diagrammatic representation of the SDLC methodology phases followed at Ecotech is as shown below:

• At the commencement of the project, Ecotech will have meetings with the Project Owners and their team from the client’s side and all the departments within the client organization, who have a stake in the project.
• The Detailed Planning Phase will identify all internal organizational dependencies and the deliverables expected from each group identified as integral to the project.
• This phase also helps in developing a shared vision that gets the buy in, from various departments that are involved.
• Before the project development, a thorough analysis of the requirements of the clients is carried out. This is done in the following four steps:
  • Elicitation – I ask questions, you talk, I listen
  • Validation – I analyze, I ask follow-up questions
  • Specification – I document, I ask follow-up questions
  • Verification – We all agree
• This stage involves the following:
  • Interviews and Research— Gain a detailed understanding of the project.
  • Strategic Decisions—Team leaders review scenarios and verify that the correct problem to solve has been identified.
  • Develop Process flow documents, per-module and per-page functional specifications.
  • Develop Use Cases and finalize the project plan.

• Integrate requirements and conceptual design into detailed design. Gather and define processing requirements and navigation prototypes.
• Prototyping of GUI and System Features—Navigational scripts are created to simulate screen flow and gain initial user feedback.
• Through the Prototypes a clear understanding of the process and navigation is presented to the client. Depending upon the feedback from the client, the project advances to the next phase i.e. Development phase.

• Engineer — Develop user interface, object model, technical design, standards and processes and security requirements.
• Code with Best of Breed Tools— the most successful solutions are only as strong as each of their components.

• A test strategy is an outline that describes the testing portion of the software development cycle. It is created to inform project managers, testers, and developers about some key issues of the testing process. This includes the testing objective, methods of testing new functions, total time and resources required for the project, and the testing environment.
• In this stage test cases are generated. The project undergoes rigorous testing before its actual implementation. Once the project has been successfully tested for its functionality and the desired results, the project is then deployed on the client side.
• It is a process-driven approach with specific steps to help define and attain goals.
• The most popular tool used for quality assurance consists of four steps: Plan, Do, Check, and Act. These steps are commonly abbreviated as PDCA.
• The four quality assurance steps within the PDCA model stand for:
  • Plan: Establish objectives and processes required to deliver the desired results.
  • Do: Implement the process developed.
  • Check: Monitor and evaluate the implemented process by testing the results against the predetermined objectives
  • Act: Apply actions necessary for improvement if the results require changes
• After the execution of test cases the bugs are reported to the developers.The developers resolve these bugs and release the software to the client for User Acceptance Testing (UAT). After UAT, if the Client accepts the software, then the software is delivered otherwise it is sent back to the developers.

• Training of Operations Staff — Training that may have been received throughout the process is now solidified as their role in application operation increases.
• Training of End-Users — Functional end-users receive documentation, support options and training instructions.
• Training of Technical Staff — Mentoring and technology transfer are provided to client’s internal technical team.

• This is the last stage after the completion of the project. In this stage, the problems are resolved in the system which are not found during the development life cycle, and those that come up after its practical use starts.
• This phase involves the following:
  • System Management — Network, System and Application are subject to ongoing review and assessment.
  • System Maintenance — Bugs are fixed and feature enhancements may be implemented.
  • Help Desk — End-users remain productive through responsive support offerings.