The approach in developing the new Cynergi point-of-sale application is a “best of both” approach that will incorporate the best features from the current High Touch and RSSS systems. As we have analyzed both systems, we’ve realized that the two systems (HT/RSSS) have a lot of the same features and functionality. There are, however, differences between the two systems in how some of the features work, differences referred to as “GAPS”. Through the process of analyzing both systems, we’ve identified GAPS that need to be addressed in order to ensure that the Cynergi application offers the best of both systems.
The purpose of this document is to provide some background about the process we are using to work through the GAP items – a process called the “Waterfall Development Model”. This model involves six different steps that are worked through in order for all GAP items. The six different steps include:
- Requirements Gathering
- High-Level Business Design
- High-Level Technical Design
- Detailed Design
- Construction
- System and User Acceptance Testing
Requirements Gathering:
This is the first step in the process and involves documenting each GAP item to determine what the specific feature provides for the end user. The point of this step is to determine what problem or need the feature is suppose to solve…and to ensure that the feature will in fact fill that need.
High-level Business Design:
Once the requirements have been documented, the Business Analysts work to conceptualize and document how the GAP feature will work, specifically, how the feature will solve the problem or fill the need for the user. Consideration is also given toward how the feature will work with existing features and possible system enhancements that may be developed in the future. Developers work with the Business Analysts during this stage to help determine if the feature is actually doable from a technical standpoint.
High-level Technical Design:
This step is performed primarily by Developers working with the Business Analysts to document and confirm how to build the feature so that it functions as it was designed by the Business Analyst during the High-Level Business Design phase.
Detailed Design:
This stage of the process is performed exclusively by the Developers and is very technical. This process involves the Developer documenting what specific types of data fields and tables need to be brought together and coded so that the right data is trapped and the proper result or solution is produced.
Construction:
This phase of the process is sometimes referred to as “coding”…and is the actual input of the characters that make up the various lines of code in the software. This is what most people think of when they hear the term “programming”.
System Testing and User Acceptance Testing (UAT):
Testing is the last step in the process and involves two different types of testing. Testing is usually conducted by the Developer, and confirms that the specific GAP feature works from a technical standpoint. User Acceptance Testing is usually conducted by a Business Analyst, and this testing confirms that the feature performs as it was designed to perform in the High-Level Business Design phase and ensures that it actually solves the problem or fills the need in which the feature was designed.
Each of the six steps outlined in this document will be performed for each of the GAP items. Once all of the GAP items have been through this process and are tested, the overall application will be tested from the standpoint of running an RTO business. From there, it’s on to beta testing, which involves deploying the new application to a few select stores for field testing. Once the beta testing is complete the application will be made available to the general client-base.
While Project Fusion is well underway, there is still a lot to do before all GAP items have been analyzed, coded and added to the Cynergi application. As we work through this process, we will get a clearer picture of the differences between the current-state HT and RSSS systems and the new Cynergi application. Once we’re through all GAP items, we’ll produce a list of features and functions that differ between both current-state systems and Cynergi. Look for that document to be published in March 2011.