|
||||||
|
|
Requirements Analysis Phase This is the first and most critical step in our Corporate Application Development process, which conventionally spans one to two weeks. During this phase, we work with the client's users, IT professionals and executives to identify key information including: Executive requirements, critical success factors, roles and responsibilities, high-level business requirements, project scope and cost estimates, initial logical data model, and application architecture. We also matrix the applications functionality and prioritize each function by its business benefit and technical complexity. This provides the team with a "road map" from which to deploy the solution. Design Phase During this phase, the design specifications are created, detailing the new system down to the level of program and file specifications. Several areas of design-application, database, network, architecture and package selection are performed concurrently, and the results are then integrated to produce the total systems solution. Construction Phase The Construction Phase is the build stage. During this phase, the products specified in the Detailed Program Specifications are written and tested. The database is populated with test data and new hardware configurations are tested. Finally, the system is tested as a whole and preparations are made for user acceptance testing. Documentation and Training Phase The Documentation and Training phase occurs concurrently, and in synchronization with the Construction and Acceptance phases. The objective of this stage is to transfer to the users and operations staff the knowledge of the new system that has been accumulated in the preceding phase. The users are prepared in this stage for performing the acceptance testing and eventually adopting the new system. Acceptance Phase During the Acceptance phase, users review the completed system and evaluate it for conformance to expectations and the Requirements Document. Support Phase The activities of the Support phase entail everything that follows cutover, from monitoring and reporting on system performance to managing change control procedures. Project Management Approach Project Status Reporting Project tracking and progress reporting are critical to the successful completion of any project. To help ensure that the project stays on schedule, weekly status reports will be developed by the Project Manager(s) and delivered to the Steering Committee. Project status will be closely monitored and reported through the following targets:
Quality Management processes have been engineered into SCG's project management approach. Our focus is to "build quality in" to the work products produced, and not to "inspect quality in" at the deliverables' completion. This is accomplished through the following:
|
|
|||||||||||||||||
|
||||
|
||||