Detailed Design Process
Design
Preliminary Design Model [Placeholder]
Tradeoff Approach Though an ultimate and extravagant system is desired for Kudler Fine Foods’ Frequent Shopper Program, it is likely that some tradeoffs will have to be made to ensure that the project remains feasible for the company. In designing the Frequent Shopper Program for Kudler Fine Foods, it is important to consider certain tradeoffs of the project, in terms of costs, the schedule of the project, and the performance of the system, regardless of which approach is chosen (University of Phoenix, 2012). However, each approach that could be used for the system’s design must include mandatory requirements and comply with all laws, regulations, and guidelines for financial information, security, and privacy.
Concerning costs. If costs and Kudler’s budget are the most important requirements, some tradeoffs for the system’s design would be only implementing mandatory requirements of the system and performing the minimal amount of required testing to ensure the system will function (Valacich et al., 2012). However, this approach may have more risks and possible problems that may be missed within the system and would not include more options for customers of the Frequent Shopper Program.
Concerning schedule of project. Currently, there is not an exact specified date for the completion of the Frequent Shopper Program; however, the scheduled goal of the project’s completion appears to be before Kudler’s next first quarter of sales (Apollo Group, 2011d). To meet this schedule, some optional design features of the program, such as the website that users can check and redeem points for prizes, may not be done within the project’s timeline. This feature may be added at a later time. It is also possible that some time towards thorough testing that may affect the performance of the system may also be sacrificed to meet the schedule of the project as well; instead, as a minimum requirement, the main sections of the system
Preliminary Design Model [Placeholder]
Tradeoff Approach Though an ultimate and extravagant system is desired for Kudler Fine Foods’ Frequent Shopper Program, it is likely that some tradeoffs will have to be made to ensure that the project remains feasible for the company. In designing the Frequent Shopper Program for Kudler Fine Foods, it is important to consider certain tradeoffs of the project, in terms of costs, the schedule of the project, and the performance of the system, regardless of which approach is chosen (University of Phoenix, 2012). However, each approach that could be used for the system’s design must include mandatory requirements and comply with all laws, regulations, and guidelines for financial information, security, and privacy.
Concerning costs. If costs and Kudler’s budget are the most important requirements, some tradeoffs for the system’s design would be only implementing mandatory requirements of the system and performing the minimal amount of required testing to ensure the system will function (Valacich et al., 2012). However, this approach may have more risks and possible problems that may be missed within the system and would not include more options for customers of the Frequent Shopper Program.
Concerning schedule of project. Currently, there is not an exact specified date for the completion of the Frequent Shopper Program; however, the scheduled goal of the project’s completion appears to be before Kudler’s next first quarter of sales (Apollo Group, 2011d). To meet this schedule, some optional design features of the program, such as the website that users can check and redeem points for prizes, may not be done within the project’s timeline. This feature may be added at a later time. It is also possible that some time towards thorough testing that may affect the performance of the system may also be sacrificed to meet the schedule of the project as well; instead, as a minimum requirement, the main sections of the system
References: Apollo Group, Inc. (2011b). Kudler Fine Foods. Intranet: Home – Kudler Fine Foods. Retrieved from BSA/375 – Fundamentals of Business Systems Development course website. Apollo Group, Inc. (2011c). Kudler Fine Foods. Sales & marketing – Marketing overview. Retrieved from BSA/375 – Fundamentals of Business Systems Development course website. Apollo Group, Inc. (2011d). Kudler Fine Foods. Sales & marketing – Sales plan 2007. Retrieved from BSA/375 – Fundamentals of Business Systems Development course website. Apollo Group, Inc. (2011e). Smith Services Consulting Incorporated. Service request: Kudler Fine Foods. Retrieved from BSA/375 – Fundamentals of Business Systems Development course website. Apollo Group, Inc. (2011f). Kudler Fine Foods. Information Technology – Network. Retrieved from BSA/375 – Fundamentals of Business Systems Development course website. Apollo Group, Inc. (2011g). Kudler Fine Foods. Finance and Accounting - Point of Service (POS) Procedures. Retrieved from BSA/375 – Fundamentals of Business Systems Development course website. Apollo Group, Inc Scheid, J. (2010). An example of operational feasibility. Retrieved from http://www.brighthubpm.com/project-planning/72872-an-example-of-operational-feasibility/ Umiker-Sebeok, J University of Phoenix. (2012). Syllabus. Retrieved from University of Phoenix College, BSA/375 – Fundamentals of Business Systems Development course website. Valacich, J. S., George, J. F., & Hoffer, J. A. (2012). Essentials of systems analysis and design (5th ed.). Retrieved from University of Phoenix eBook Collection database.