The 7-phase methodology adopted at GIL is designed to build one over the other - taking the outputs from the previous stage, adding additional effort, and producing results that leverage the previous effort and are directly traceable to the previous stages. This top-down approach is intended to result in a quality product that satisfies the original intentions and requirements of the customer.
The first phase is the requirements definition stage wherein requirements gathering process takes as its input the goals identified in the business requirement specifications and system requirement Specifications. Goals identified in the initial market survey and customer interactions are refined into a set of one or more requirements in the business requirement Specifications. System requirement specifications defines the major functions of the intended application which includes Software Application, Hardware and Networking details. Risks are identified and mitigation plans established at both the BRS
and SRS levels.
The planning stage establishes a bird's eye view of the intended software product, and uses this to establish the basic project structure, evaluate feasibility and risks associated with the project, and describe appropriate management and technical approaches.
The most critical section of the project plan is a listing of high-level product requirements, as defined in the BRS and SRS. All of the software product requirements to be developed during the requirements definition stage flow from one or more of these goals. The outputs of the project planning stage are the Configuration Management Plan, the Quality Assurance Plan, and the Project Plan, with a detailed listing of scheduled activities for the out stages. Once the scope and system specs are decided, the allocation of work to the personnel is done during this phase.
The design stage takes as its initial input the requirements identified in the approved SRS as well as the scheduling identified in the Project Plan stage. For each requirement, a set of one or more design elements will be produced as a result of inputs received from the interviews, workshops, and/or prototype efforts developed on interacting with the client. Design elements describe the desired software features in detail, and generally include Design Flow Diagrams, System Flows, Screen Layout Diagrams, Pseudo code, Database Diagrams and a complete Entity-Relationship diagram with a full Data Dictionary. These design elements are intended to describe the software in sufficient detail in order that the skilled programmers may develop the software with minimal additional input.
The development stage takes as its primary input the design elements described in the approved design document. For each design element, a set of one or more software artifacts will be produced. Software artifacts include but are not limited to menus, dialogs, data management forms, reports, and specialized procedures and functions. Appropriate test cases are developed for each set of functionally related to software artifacts, and an online help system is developed to guide users in their interactions with the software.
During the course of the project development, pilot demonstrations are carried out to make sure that the client's needs are addressed as per the exact requirements, to guarantee complete customer satisfaction. The Design and Development process at Gallops is constantly subjected to monitoring and scrutiny for maintaining a distinct standard of quality at all stages. Once the pilot project is demonstrated and changes or modifications in design and development identified, the mainstream development resumes.
During the integration and test stage at GIL, the software artifacts, online help, and test data are migrated from the development environment to a separate test environment (client side environment is simulated in the testing department). At this point, all test cases are run to verify the correctness and completeness of the software. Successful execution of the test suite confirms a robust and complete migration capability.
Successful execution of the test suite is a prerequisite to acceptance of the software by the customer. After customer personnel have verified that the initial production data load is correct and the testing has been executed with satisfactory results, the customer formally accepts the delivery of the software.
The primary outputs of the installation and acceptance stage include the archived software artifacts as well as the archived project plan, and a memorandum of customer acceptance of the software. At this point the project is "locked" by archiving all software items, the source code, and the documentation for future reference.
GIL understands that a project is always a long lasting commitment with the client and hence support and maintenance at our organization form an integral part of the project management. Keeping the client's technology investment operating at maximum efficiency is a vital element for the success of our project and that is why we have created a fully dedicated Technical Services and Support Team that remains on call for an uninterrupted 24x7 hours. Our role is to allow our customers to focus on their primary business mission, while we work as their trusted partner to support their ever-changing business needs.
• After deployment, the Installation Team hands all documentation over to the client and to the Technical Support at GIL. If needed, the team creates maintenance documents for the client Data Administrator. Finally, the client is asked to complete a satisfaction survey and set up routes of contact for any future services that we may be able to provide.
Deliverables that can be expected in Post Acceptance:
• Maintenance documents
• Site Visit Details
• Customer Satisfaction Index
• Complete set of project documentation
Once the implementation is complete, the Installation Team hold workshops with the in charge at the client side to familiarize them with daily use of the customized software application, including how to run sourcing events and manage data. Depending on the client's needs, the team will also provide instruction to the client's suppliers, or train the client side team to lead such training sessions.
What makes gallops different from its other counterparts is its total commitment towards its valued clientele and gallops ensures customer satisfaction by constantly monitoring the customer satisfaction index even long after a project is successfully implemented.
|