Disclaimer - Alliance Digital Repository

More documents

Recommendations

Info

43 ColdFusion for their internal intranet applications it was fitting that this project be developed using that server-side programming language. Although ARC was using ColdFusion alternative programming languages were researched to see if they would be more suitable for the development of the application. Microsoft’s ASP.NET, as well as PHP, were potential candidates for developing this application. This author had some experience programming in all three of these languages, but using ColdFusion made the most sense for ARC for the simple fact that its IT staff would be able to better maintain and modify the application after the project has ended. Once the development language was decided it was necessary to decide on a RDBMS system. As was the case with the development language, ARC was currently using Oracle 9i for other database applications so it made sense to use that system for this project. To accommodate the needs of the application a new schema was created where the tables, stored procedures, functions and other database objects required by the application were created. The database administrator (DBA) at ARC insisted on using the same database that ARC uses for most of their other Web-based applications, as well as their data warehouse. In this database a new schema was created, referred to as leadmanagement, for the CRM application. When designing the database this author attempted to normalize the tables as much as possible with emphasis on storing related data in the same tables, while also concentrating on eliminating the possibility of redundant data, which is the suggested database design strategy. The majority of the table structures were relatively simple. There were, however, some difficulties expressing the sales staff’s organizational hierarchy and job roles in
44 table form, as well as the hierarchy of assigning leads. This issue was resolved by creating a table with multiple columns; the ID column would contain a unique ID, the NAME column would hold the logical name of the job role, while the remaining columns would hold the job role ID’s which the named job role can create (CCx columns) accounts for, i.e. a Sales and Leasing Agent can only create accounts in the system for Sales and Leasing Agents and Community Managers, this is depicted in Figure 9. Figure 9 - Job roles and job role creation hierarchy (Darschewski, 2006) The method used for the hierarchy of assigning leads is similar to the one used in the JOB_ROLE_RIGHTS table; this is depicted in table form in Figure 10. The JRRID column is a foreign key to the JOB_ROLE_RIGHTS table’s ID column. The ALx (where x is a number from 1 to 10) columns refer to the job roles that the JRRID column can assign sales leads to. Figure 10 - Assignment of leads hierarchy represented in table form (Darschewski, 2006)
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 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 82 and 83: 69 Using the Internet site of ARC a
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?