Disclaimer - Alliance Digital Repository

More documents

Recommendations

Info

47 After numerous revisions the owner of the project at ARC approved the application and they had a final engineered product to be moved to the production environment for real world use. If any bugs were found with the system at this stage the author had to fix the bugs in the development environment, then the fixes were moved to the test environment for testing by certain individuals, in particular those who found the bugs, and finally the fixes were moved to the production environment. To implement the system to the test and production environments new schemas needed to be created by the DBA in those environments. In addition, the Web pages that were developed for the system were copied to a designated folder in the Web root directory on these servers. In order to make the application separate from other Internet applications at ARC, a sub domain name of ARC’s parent domain was created, as well as a virtual directory in Internet Information Server that pointed to the location of the application files. To create the database objects on the test and production servers multiple structured query language (SQL) scripts were created; one for the tables, one for the functions and procedures, one for the other database objects, including sequences, triggers, views and custom data types, and finally one for the static data of the database. The scripts were then executed in these environments by the DBA. Equally vital to the implementation of the final product was the creation of a data source connection. The datasource was created in the ColdFusion Administrator to allow ColdFusion to access the application’s database. The following section will provide details of the application. This will be done through the use of screen shots of the individual modules.
48 The Application: When a user first enters the universal resource locater (URL) of the application into their browser they are presented with the Welcome screen in Figure 12, instructing them to sign in. Figure 12 - Welcome screen of the application (Darschewski, 2006). Security/Profile - The security portion of the application is composed of multiple screens and also consisted of a few stored procedures. The initial step in creating a user for the application is for an administrator to log in as seen in Figure 13. Figure 13 - Login Page (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 56 and 57: 43 ColdFusion for their internal in
Page 58 and 59: 45 All of the tables were created w
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?