Disclaimer - Alliance Digital Repository

More documents

Recommendations

Info

29 Chapter 3 – Methodology Life Cycle models followed : This project consisted of developing a Web-based application that was used as a CRM tool. Since an application was designed, coded, and implemented it was fitting to use the Software Development Life Cycle (SDLC) and a somewhat modified ancillary model, the Prototyping Life Cycle which was discussed earlier in this paper and depicted in Figure 4. According to Fioravanti (2005), there are two Prototyping Life Cycles that one can use in application development. The first is called the throw-away prototype and is usually used in a rapid application development (RAD) project/environment and the second is the real life cycle in which follows more methodical development (Fioravanti, 2005). While this project needed to be developed rather rapidly the throw-away prototype just did not seem to be as suitable for the project as the true Prototyping Life Cycle. The phases of this life cycle allowed for rapid development, but also, for the flexibility of going back to previous phases and building on itself; similar to the Spiral Life Cycle. 1. Requirements: The application was built from the requirements given to this author by the owner of the project at ARC. The requirements gathering phase consisted of meeting with management personnel at ARC to gain a thorough understanding of the goals they wanted to accomplish with the application. These requirements were then used throughout the project and were revisited during development of the individual project modules. Once all of the requirements were met the application was deemed complete.
30 2. Fast Project: The first time this phase was encountered the primary focus was for ARC to define in detail how the user interface should look and feel to the users of the application. From these recommendations, this author proposed an interface and menu style that suited ARC’s needs. Also, this interface implemented the requirements specified in the first requirements gathering (Fioravanti 2005). 3. Prototyping: In the prototyping phase actual coding began. The database was designed, constraints were put in place on table columns and the coding of certain stored procedures and functions applicable to the first requirements phase were developed. Fioravanti (2005) states that in this phase the coding approach resembles that of RAD in which visual tools improve development speed and also allow the generation of pseudo-code. For this application the use of Macromedia HomeSite+ and Quest Software’s Toad for Oracle was a fundamental aide in its development. 4. Requirements Review: The requirements review phase was visited multiple times throughout the project. During this phase ARC looked at the prototype that was developed based on their initial requirements, and subsequently approved or denied particular modules that were completed. Often times during this phase new requirements were added, which, eventually, when the necessary changes were made, moved the application from a prototype to a finished product. 5. Engineered Product: The engineered product was the culmination of all the revisions to the prototype and the end result of the Prototyping Life Cycle. The engineered product had been previously tested for any bugs and to ensure that all required functionality was implemented. For this project the engineered product
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 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 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?