Disclaimer - Alliance Digital Repository

More documents

Recommendations

Info

69 Using the Internet site of ARC as a template for this application was an excellent decision. The pull-down menu system allowed for restricted access to different modules based on a user’s roles, and the layout was well received by both the users and management at ARC. One of the most notable areas where the project did not go as planned was in the communication between this author and ARC regarding deadlines. A project plan was developed so that specific modules would be designed on a schedule. The problem was getting ARC to dedicate the staff needed to thoroughly test these modules and to report any bugs that were found. By not allocating proper resources in terms of personnel to the testing of the project, ARC increased the risk of not having the application developed in the timeframe they wanted. Another area where the project went wrong was in failing to thoroughly test the speed of the application at its maximum usage. Having failed to do this the application began to slow a few months following implementation. ARC was not willing to put the application through aggressive testing due to the urgency of implementing it into the production environment. Their thought was to allow users to do performance testing in the production environment and then revisit any issues that may arise. Final testing of an application in the production environment is not the suggested way of performing stress testing. Project variables and their impact on the project: The most significant variable that impacted this project was the speed of the application after it was deployed to the production environment and in use by hundreds of
70 sales staff throughout the United States. In the first nine months of the application being in use, more than 15,000 leads were entered into the system, which averages to approximately 55 leads per day. Despite the fact that the application was designed to handle a large number of records, being able to test it with that number of records was unrealistic. Approximately four months into the application’s use there was a noticeable difference in the speed when compared to the speed when it was first deployed. As more and more leads and users were added to the system the queries and logic to determine what users had access to other users and what leads users can see began to take its toll. For the average user this did not have as much of an impact as it did for those users who were in management roles in the system. These users, since they had subordinates they could assign leads to and subordinate leads they could look at, would experience a wait time of about ten to fifteen seconds when accessing the pages that would find their subordinates. While this is not a long time to wait it was too long for these users. This issue was resolved through better use of indexes on the backend database and through the use of hints in the front-end SQL queries. Another variable that impacted the project was the underestimation of the learning curve that would be involved for both the users and administrators of the system. Having developed the system, this author believed that the interface was intuitive and that the application flowed consistently. The initial testing of the application with a small group of users also revealed its intuitive design. However, once the application was deployed there were multiple problems with users not knowing where to go to perform certain tasks. This may have been partly due to the minimal training ARC provided, but could also be attributed to the user interface. The impact of this issue was that users were
Page 1 and 2:
Regis University School for Profess
Page 3 and 4:
Regis University School for Profess
Page 8 and 9:
An Abstract of a Project/Practicum
Page 10 and 11:
Table of Contents Chapter 1 - Intro
Page 12 and 13:
List of Figures Figure 1 - Web Appl
Page 14 and 15:
1 Chapter 1 - Introduction Statemen
Page 16 and 17:
3 ARC needed this repository for al
Page 18 and 19:
5 Summary: Affordable Residential C
Page 20 and 21:
7 Chapter 2 - Review of Literature
Page 22 and 23:
9 management capabilities (Chen and
Page 24 and 25:
11 administration (Beynon-Davies, 2
Page 26 and 27:
13 successful which relate to the s
Page 28 and 29:
15 Developer’s Guide”, n.d.). D
Page 30 and 31:
17 subsystems that were previously
Page 32 and 33: 19 incorporated into a collection o
Page 34 and 35: 21 with Web-based applications in m
Page 36 and 37: 23 making sure their servers, espec
Page 38 and 39: 25 Research methods to be used: The
Page 40 and 41: 27 concerning the security of their
Page 42 and 43: 29 Chapter 3 - Methodology Life Cyc
Page 44 and 45: 31 was the custom built application
Page 46 and 47: 33 Lead Assignment: The procedure A
Page 48 and 49: 35 Review of deliverables: The deli
Page 50 and 51: 37 When the project began ColdFusio
Page 52 and 53: 39 MX licenses, as well as the othe
Page 54 and 55: 41 Figure 7 - Required Lead Informa
Page 56 and 57: 43 ColdFusion for their internal in
Page 58 and 59: 45 All of the tables were created w
Page 60 and 61: 47 After numerous revisions the own
Page 62 and 63: 49 If a user forgets their password
Page 64 and 65: 51 Figure 18 - Create Profile Page
Page 66 and 67: 53 want to delete. When the profile
Page 68 and 69: 55 Figure 25 - Show Leads Page (Dar
Page 70 and 71: 57 Figure 28 - Lead Documents Page
Page 72 and 73: 59 When the user closes a lead they
Page 74 and 75: 61 Since certain users are allowed
Page 76 and 77: 63 FORGOT_PWD table. In addition, n
Page 78 and 79: 65 in a module or changes to a modu
Page 80 and 81: 67 stored procedure would parse the
Page 84 and 85: 71 hesitant to use the application
Page 86 and 87: 73 management. There was not any da
Page 88 and 89: 75 Summary of results: This project
Page 90 and 91: 77 Chapter 5 - Lessons Learned and
Page 92 and 93: 79 What would have been done differ
Page 94 and 95: 81 logic that is currently in the f
Page 96 and 97: 83 Although the project met initial
Page 98 and 99: 85 Liao, Shu-Hsien (2005). Expert s
Page 100 and 101: Appendix A 87
Page 102 and 103: 89 Appendix C Design and Implementa
Page 104 and 105: 91 The Internet as a Portal Can be
Page 106 and 107: 93 Components of a Database backed
Page 108 and 109: 95 Web Methodologies Web applicati
Page 110 and 111: 97 Project History Application Req
Page 112 and 113: 99 ARC’s Design Idea Final Design
Page 114 and 115: 101 Application Features Automatic
Page 116 and 117: 103 Next Evolution of the Project
Page 118 and 119: 105 Annotated Bibliography .NET Fra
Page 120 and 121: 107 design; and specific logical de
Page 122 and 123: 109 This website defines a relation
Page 124 and 125: 111 Standing, Craig (2002). Methodo
show all

Disclaimer - Alliance Digital Repository

Create successful ePaper yourself

Delete template?

Save as template?