Disclaimer - Alliance Digital Repository

66
lead an equal opportunity. This logic of assigning leads also had to take into account that
there were regional or district personnel who could be in the same geographical location
of the lead, but would not be allowed to receive it because their profile prohibits them
from receiving leads. It was a major milestone when the stored procedures that
performed these tasks were finally completed and working as intended.
Each of the modules that were developed for this application presented their own
challenge. When all of the modules were completely developed and tested it was a
significant milestone in this project, the reason being was that this indicated the project
was nearing completion and soon it would be used by the sales staff in real world
situations.
Since all of the testing and suggested changes to the prototype were being
performed in conjunction with the development of the other modules, the most significant
event of this project was when the application was moved from the test environment to
the production environment, available for use by all of the sales staff at ARC.
Changes to the project plan:
Change is inevitable especially when dealing with developing a piece of software.
The changes to the project plan for this project were minimal. The most significant
change occurred when the owner of the project at ARC decided that they needed a way to
upload leads that they may receive from an outside source. These leads were provided to
ARC in the form of an extensible markup language (XML) file. An administrator of the
lead management application was to be able to go to a specific page in which they would
be able to browse for the XML file they wanted to upload. Upon submitting the file a