Here at End-to-End Computing (EEC) LLC, we take pride in developing applications that not only meets your need but exceed your expectation. We follow the Application Development Life Cycle below to ensure you get what you paid for and more.
Requirement Analysis and Gathering
- During the Requirements Phase, automation needs of the business functions are collected and quantified. The requirements include business rules that govern the work of the user, definition of specific business functions or processes, and levels of security needed to protect the business’ information. Also in this phase, we recommend a Change Control Board (CCB) be established. The purpose of the CCB is to receive all proposed changes to the requirements, decides if the proposed change should be applied to the system and if accepted, and places a priority on the incorporation of the changes to the system. This Board is comprised of business function and IT representatives.
- Also in the analysis phase the requirements we gathered, are used to create report definitions and layouts, screen definitions and layouts, data element definitions, workflow diagrams, and security matrices. This phase culminates in the creation of a “logical” model of the application.
- In the design phase the logical model developed in the analysis phase, is used to develop a “physical” model of the application. The physical model contains business object logic, database schemas identifying relationships, web object design and layout, report calculations and processing, and the security object definition.
- In the coding/development phase the individual objects or components of the application are coded from the physical model. Once the system objects have been developed, they are gathered and connected together (integrated) to create a working application. The integrated application is placed on a staging server for testing. Throughout the development phase we use source code analysis tools to help zero in potential vulnerabilities such as Cross-Site Scripting, Buffer Overflow, etc.
Software Quality Assurance
- The testing phase encompasses three testing stages; component testing, requirements testing, and acceptance testing. During component testing, all objects are tested to ensure they work together as specified by the physical design. Once the components are tested and the system operates as designed, the application is tested against the requirements gathered in the requirements phase of development. Once the requirements testing stage is completed, the system is presented to the business function for acceptance testing. In all testing stages, defects are identified and returned to the development/coding phase for correction.
- The deployment phase contains two stages; a three- to six-month pilot is recommended to ensure training and acceptance by the users followed by a full deployment. At the conclusion of the pilot, the finished application is placed on a production server. Users are trained, user guides are delivered, and the system is distributed. The application is then maintained by our support team if maintenance is acquired.
In the maintenance phase the deployed application is maintained through scheduled backups. Any changes to the application are presented to the Change Control Board for approval. If a change or enhancement has been approved by the CCB, it is presented to the Requirements Team and the software development life cycle begins again.