Implements a full deployment using the Sure Step methodology, focusing on consultants conducting gap analysis based on client processes and requirements gathered during interviews, and fulfilling client needs through customized development.
The phases and tasks of the complete import service are as follows:
- Analysis stage: requirement analysis, process confirmation
- Design stage: difference analysis, prototype establishment
- Development stage: custom development and test environment establishment
-
Business Process Requirements Interview:
Through the interview questionnaire, the future business process and functional requirements are understood and recorded, and the format of the existing report is collected. -
Writing and Validating Requirements Interview Transcripts:
According to the conclusion of the business process requirements interview meeting, a 'requirements interview record' document is generated, which is signed by the participants as the basis for drawing the future operation process.
After the system is launched, explain the future (To-Be) system function specifications and operation flow chart.
- The To-Be Flow is subject to repeated confirmation by both parties, and during the confirmation process, the To-Be Flow diagram is adjusted.
- The future operation proposal is based on the confirmed future operation flow chart (To-Be Flow), and contains the actual steps and screens in the prototype system, which is the definition of the scope and function of the system launch by both parties, and is also the standard for acceptance by both parties.
- The future work proposal needs to be confirmed by both parties, and in the process of confirmation, the content of the original future work proposal needs to be adjusted.
On the To-Be Flow diagram, some jobs are not available in the existing Microsoft Dynamics system and must be custom developed, these are called gaps, and custom lists are generated after difference analysis and comparison.
- The customized list is a description of the functions and requirements to be customized on the system, and contains the documents to be delivered by the consultant, as well as the estimation of the time required for development and testing, which needs to be confirmed and signed by both parties, which is the definition of the scope and function of the customized development of the system by both parties, and is also the standard process confirmation of the acceptance of the customized functions by both parties.
- The customized list needs to be confirmed by both parties, and the content of the original customized list needs to be adjusted during the confirmation process.
Based on the confirmed To-Be Flow as a blueprint, we will adjust the configuration of the system and make a trial transaction with the aim of establishing a tangible prototype system that will serve as the basis for communication and confirmation between the two parties.
For the custom project that needs to provide a functional design document in the custom list, the custom development can only be carried out after both parties confirm the content and sign it, and the custom development steps are as follows:
- Carry out custom program development
- Unit test the completed custom program
- Functional testing and acceptance of customized programs with seed personnel
- Writing Technical Design Documents
Prepare the main file data required by the user test environment, and use it as the basis for future launches.
- Prepare the test environment for guest process acceptance and user testing, and set up and test the To-Be system transaction before use.
- The test environment should be set up to include existing data (vendors, customers, materials) as much as possible, and any data conversions (changes in coding principles, duplicate data collation) need to be processed at this time before they can be performed during user testing.