BSA385 Technical Article Document: Frequent Shopper Program

Preview (6 of 17 Pages)

100%

BSA385 Technical Article Document: Frequent Shopper Program - Page 1 preview image

Loading page ...

Running Head: TECHNICAL ARTICLE DOCUMENT: FREQUENT SHOPPER PROGRAM1Technical Article Document: Frequent Shopper ProgramBSA385In developing a Frequent Shopper Program (FSP) for Kudler Fine Foods, Smith SystemsConsulting (SSC) has outlined both logical and physical models for the project, detailing thenecessary hardware, software, and network requirements. Discuss how the logical and physicalmodels of the FSP are integrated to ensure system functionality. In your response, address theroles of database management, hardware infrastructure, and security controls in the program'ssuccess. Your answer should be between 600-800 words.

BSA385 Technical Article Document: Frequent Shopper Program - Page 2 preview image

Loading page ...

BSA385 Technical Article Document: Frequent Shopper Program - Page 3 preview image

Loading page ...

TECHNICAL ARTICLE DOCUMENT: FREQUENT SHOPPER PROGRAM2Frequent Shopper Program: Technical Article DocumentKudler Fine Foods (KFF) is a specialty food store chain in the San Diego, California.KFF contracted Smith Systems Consulting to develop the Frequent Shopper Program (FSP).FSP will monitor customer purchasing history and accumulate them as redeemable loyalty pointswhich customers can use for gift itemsand other products or services available through externalpartner companies. The Sales and Marketing page section of KFF’s intranet site describes thestrategic purpose of the Frequent Shopper Program.Smith Systems Consulting (SSC) provides information technology (IT) services andconsulting, which include developmental solutions, IT integration, strengthening, analysis,design, and implementation (Apollo Group, 2004). SSC will submit a proposal to KFF thatdetails the development processes of the FSP project. This paper is a technical article documentthat lists the project’s logical and physical models, which includes hardware, network, software,database, controls, and other development related tools.Logical and Physical ModelsLogical and physical models are representations of the key elements and processes of asoftwaredevelopment. The logical model describes the processes, especially data, in as muchdetail as possible, without givingregardto how the system will be physically implemented.Logical data models includeentities and relationships among themand how data flows from oneprocess or entity to another.The physical model, on the other hand,delineatesthe physical implementation of thesystem, whichanswershow the logical model will be implemented physically. The physical

BSA385 Technical Article Document: Frequent Shopper Program - Page 4 preview image

Loading page ...

TECHNICAL ARTICLE DOCUMENT: FREQUENT SHOPPER PROGRAM3model isa modified version of the logical model, intended particularly to work with a specificset of software and hardware components (Hoberman, 2009).Logical Modelofthe FSP In-Store OperationThe new Frequent ShopperProgram will add changes to the existing functions of KudlerFine Foods operations. When a customer initiates a transaction, the cashier clerk will ask if thecustomer is already a member of the Frequent Shopper Program. When the customer is not amember and does not want to participate, the transactionexecutesimmediately, and the receiptgivento the customer.Oppositely, if the customer is indeed a member, the card scanner willscan his card and his information is matched fromthelocaldatabase. Depending on his purchasepatterns and history,the FSP will issuediscounts and points to the customer. If the customerwants to participate by becoming a new member, customer information will beentered tothesystem, andanew member cardisproduced. The card willbe scanned, thetransactionwillexecute,andthenew informationisuploaded to the database. The points and rewardsinformation will be printed on the receipt andgivento the customer. Figure 1 shows the low-level data flow diagram of the proposed new system, which includes the basicprocessesdescribed above. The high-level data flow diagram includes additional details such as data flowto and from databases, and how each database is designed with specific tables.