Disclaimer - Alliance Digital Repository

65
in a module or changes to a module were needed, these changes could be fixed when time
permitted. Bugs found during the testing of the application could have potentially
impacted meeting the deadlines for subsequent modules, depending on the severity of the
bug. The timeframe for the entire project, as well as each individual module, can be seen
in Appendix B.
Significant events/milestones in the project:
This project presented a number of significant milestones. One of the major
milestones in this project occurred near the beginning. This was when a complete
understanding of the business processes, business logic and goals that ARC was trying to
achieve, by implementing the application and by developing the application rather than
using an off the shelf CRM solution, was attained.
Another major milestone occurred upon the completion of the design of the
database for the system. It was imperative for the application to have an efficient
database design which was normalized as much as possible because of the amount of data
that could potentially be stored in this database. An un-normalized database could have
proven to be detrimental to the application due to the effects it could have had on its
performance.
During the development of this project one of the more challenging issues was
programmatically routing leads that were entered into the system by members of the call
center. These leads needed to be routed to the correct agent based on the location of the
lead, as well as the language preference of the lead. What made this a challenge was that
a round robin approach was needed to allow each of the agents who could receive the