Service Request SR-kf-013
Service Request SR-kf-013 for Kudler Fine Foods.
University of Phoenix
Systems upgrades or request for services are a necessary stipulation of the business world. This operation allows for upkeep of current systems and the implementation of new programs. It is through this that the identification, design, and implementation of this program that will help to further enhance Kudler’s standing in the community and its commitment to its customers and suppliers. Service request
The objective of this project request is to track purchases of individual customer’s. The customer purchases will be tracked and accumulated as loyalty points for redemption by the customer for gift items, specialty foods and other products or services as made available through partnerships with other external companies. The strategic purpose of the Frequent Shopper Program isto provide a system by which this process can be implemented and maintained. The object here is to create a business/systems requirements document as it is related to or for the development of the Frequent Shopper Program system to meet the objective of this request. Process design is defined as being Activities_ involved in determining the _workflows_ and implementation _requirements_ for a particular _process. (http://www.businessdictionary.com/definition/process-design.html, retrieved 4 Jan 2010) Having made this distinction it is possible to further refine these operations to this service request. The first objective is to identify the type of system design that is the most efficient and cost effective. Since this system is going to be dealing with fluctuating and exponentially expanding data from multiple sources for multiple accounts it is going to need to be self adaptable. Apply the tools of systems analysis to describe the information systems architecture in terms of data, processes, interfaces, and network. Among the many procedures that can be used in the process is the SLDC. “Systems Development Life Cycle (SDLC) is any logical process used by a systems analyst to develop an information system, including requirements, validation, training, and user (stakeholder) ownership. Any SDLC should result in a high quality system that meets or exceeds customer expectations, reaches completion within time and cost estimates, works effectively and efficiently in the current and planned Information Technology infrastructure, and is inexpensive to maintain and cost-effective to enhance.” (http://en.wikipedia.org/wiki/Systems_Development_Life_Cycle, retrieved 13 Jan 2010) o Supporting Measures for Success: Specify tangible measures for determining the relative degree of success of the completed project. The measures must correlate with the goals specified in the first section of this deliverable. o Summary of Project Feasibility: Include specific operational, technical, and economic feasibility analysis. Operational and technical issues should specify how each issue will be addressed. The economic analysis must include quantified specific benefit and cost areas. Current Business Process Summary: Provide a flowchart and a separate high-level logical data flow diagram of the current process. o Proposed System Requirement List: List specific individual requirement needs in measurable and objective terms. Describe the information-gathering techniques and design methods you would propose to use for the project. The first area of concern is to describe the information-gathering techniques and design methods you would propose to use for the project. First and foremost, it is remember that this is all part of the systems development cycle or SLDC for short. In order to proceed in an efficient and professional manner, it has been found through trial and error that this entire procedure can be accomplished in a two stage procedure. The first of these is broken down into the following...
Please join StudyMode to read the full document