Custom Software Development
Compri Consulting provides custom software solutions to meet just about any requirement. Our software development life cycle (SDLC) model has been refined to manage risk, maximize quality, minimize cost, and improve time-to-market for your project. This model provides an 8-step, repeatable, managed process that brings predictable results to every project. Results include:
- Better requirements specification
- More powerful design evaluation
- Enhanced quantitative project management techniques
- Better control of products and processes
- Better project risk management
- Significantly reduced costs
- High customer satisfaction
The Compri SDLC includes eight (8) phases during which defined IT work products are created or modified. Not every project will require that the phases be sequentially executed. However, the phases are interdependent. Depending upon the size and complexity of the project, phases may be combined or may overlap.
1. Planning Phase
The initiation of a system (or project) begins when a business need or opportunity is identified. Once a business need is approved, the approaches for accomplishing the concept are reviewed for feasibility and appropriateness. The concept is further developed to describe how the business will operate once the approved system is implemented. To ensure the products and /or services provide the required capability on-time and within budget, project resources, activities, schedules, tools, and reviews are defined. Additionally, security certification and accreditation activities begin with the identification of system security requirements and the completion of a high-level vulnerability assessment.
2. Requirements Analysis Phase
Functional user requirements are formally defined and delineate the requirements in terms of data, system performance, security, and maintainability requirements for the system. All requirements are defined to a level of detail sufficient for systems design to proceed. All requirements need to be measurable and testable and relate to the business need or opportunity identified in the Planning Phase. A software project test plan is developed that describes the objectives, scope, approach, and focus of the software testing effort.
3. Design and Initial Development Phase
The physical characteristics of the system are designed during this phase. The operating environment is established, major subsystems and their inputs and outputs are defined, and processes are allocated to resources. Everything requiring user input or approval must be documented and reviewed by the user. The physical characteristics of the system are specified and a detailed design is prepared. Subsystems identified during design are used to create a detailed structure of the system. Each subsystem is partitioned into one or more design units or modules. Detailed logic specifications are prepared for each software module.
4. Implementation Phase
The detailed specifications produced during the design phase are translated into hardware, communications, and executable software. Software is unit tested, integrated, and retested in a systematic manner. Hardware is assembled and tested.
5. Testing and Integration Phase
The various components of the system are integrated and systematically tested by QA professionals. This phase involves integration testing of combined parts of an application to determine if they function together correctly. System testing is performed to cover all combined parts of the system.
6. Evaluation
The user tests the system to ensure that the functional requirements, as defined in the functional requirements document, are satisfied by the developed or modified system. Prior to installing and operating the system in a production environment, the system is stress tested, and undergoes certification and accreditation activities.
7. Release
The system or system modifications are installed and made operational in a production environment. The phase is initiated after the system has been tested and accepted by the user. This phase continues until the system is operating in production in accordance with the defined user requirements.
8. Support
The system operation is ongoing. The system is monitored for continued performance in accordance with user requirements, and needed system modifications are incorporated. The operational system is periodically assessed through In-Process reviews to determine how the system can be made more efficient and effective. Operations continue as long as the system can be effectively adapted to respond to an organization’s needs. When modifications or changes are identified as necessary, the system may reenter the planning phase.