Team 23 Project Plan Customer Loyalty Program For Small .
Team 23 Project PlanCustomer Loyalty Program forSmall BusinessesClients - Jay NamboorAdviser - Dr. GovindarasuMembers:Christopher Waters, Van Nguyen , andWilliam TranTable of contentsProject Plan 1
1. Problem/need statement2. Concept sketch2.1 use cases3. System block diagram4. System description5. Operating environment6. User interface description7. Functional requirements8. Non-functional requirements9. Market survey10. Deliverables11. Work plan11.1 - Work Breakdown11.2 - Task Breakdown11.3 - Project Schedule11.4 - Project team information11.5 - Communication Management11.6 - Risks and Risk Management3458991010111113131314161717181 - Problem/need statementWe propose creating a mobile customer loyalty application to increase business for smallbusinesses. Such an application will encourage customers to patronize local businesses byoffering them reward incentives on goods and services they already purchase. It will aim toreplace existing reward incentives such as punch cards and coupons by providing a moreProject Plan 2
convenient system for both the consumer and business.Our primary customer will be iapps24, a smart-phone application development company basedin Des Moines who have sought Iowa State University students to begin development on thisapplication.Project Plan 3
2 - Concept SketchFigure 2.1. Shows how the user and the merchant can interact with our applicationProject Plan 4
2.1 Use CasesUse CasePrimary Actor(s)PreconditionSummaryOutcomeUC-1 CreateaccountCustomers andmerchantsUsers have todownload theappCustomers/Merchants entera username,password, andselect a role thatthey want for anew account tobe createdNew accountis created andit’s going to beadded to thesystemUC-2 Login/logoutCustomers andmerchantsMust be amemberCustomers/Merchants entertheir usernameand passwordSystem willredirect useraccording totheir role.UC-3 Createloyalty cardMerchantsMust be loggedin.Merchants canmanage/createloyalty card.New loyalty cardis created/editedinto system.UC-4 Expireloyalty cardMerchantsMust be loggedin.Merchants canexpire a loyaltycard if theychoose to.Loyalty card isno longer valid.UC-5 VerifypunchesMerchantsCustomermust havedownloaded theloyalty card forthat merchant.The punch willbe verified.If it issuccessfullyverified, user’scard will getupdated withpunch.UC-6 VerifyrewardMerchantsCustomer musthave collectedall requirednumber ofpunches.Merchant willbe able to verifythe user hascollected all thepunches.Once verified,user will get therewardProject Plan 5
UC-7 SearchbusinessesCustomernoneUsers cansearch forrestaurantsbased onthe name, bylocation, by gps.The systemwill return a listof businessesbased on thesearch criteria.UC-8 Selects acardCustomerMust be loggedinUser can selectloyalty cardsthey wantfrom specificbusinesses.Loyalty card willbe selected.UC-9 DownloadcardCustomerCustomers musthave selected acard.Customer wantsto downloadthe specificloyalty card theyselected.Card isdownloaded andstored into thesystem.UC-10 RedeempunchCustomerCustomer has tohave purchaseda productCustomersgetting a punchafter purchasinga product.Punch isupdated intocard andupdated in thesystem.UC-11 RedeemrewardCustomerCustomersmust have acompletedpunch cardCustomer hascompletedpunch card.Customer maylet store verify, ifsuccessful, theywill be given thereward. Rewardredemption willbe stored in thesystemUC-12 StorehistoryDatabasenoneRedeemedloyalty card isstored into thesystem databaseThe systemcan now returnthe history of aloyalty card ifrequested.UC-13 Merchantquery historyMerchantMust be amerchant user.Merchants canview historyof redeemedloyalty cards fortheir businessneedsSystem willreturn therequested loyaltycards.Project Plan 6
UC-14 Customerquery historyCustomerMust be aCustomerCustomer canview his/her ownhistory of loyaltycards.System willreturn therequested loyaltycards.Figure 2.2 This is a use case diagram of actors Customer and MerchantProject Plan 7
3 - System block diagramFigure 3.1. System Block DiagramProject Plan 8
4 - System descriptionWe are looking to create mobile customer loyalty application. The application will allow formerchants to create reward based incentives for their business. The rewards will be based upona traditional punch card system, but stored electronically in the user’s phone. The merchantswill also be able to expire rewards and set expiration dates at any time. (Each reward card willhave a disclaimer for what happens if the reward is not available at the time of redemption).Merchants will be able to verify punches and reward redemptions at the time of purchase.Customers will be able to search the app for available punch cards at local businesses by GPSand name based searching. When a customer finds a punch card they plan on using, theycan download it directly to their phone. The punch card will have information on what type ofpurchase will qualify for a punch. When a customer earns the required number of punches, theywill be able to collect a reward.History of punch cards will be stored on a server database. Merchants will be able to viewinformation about the number of punch cards redeemed at their store, but not about theindividuals who redeemed them. Customers can view their personal history of redeemed punchcards.5 - Operating environmentThe system will run on Android and iOS mobile devices. The mobile devices will utilize a localSQLite database to store information about a user’s current loyalty cards. There will also bea MySQL database on a server that will store information about businesses, completed cardhistory, and loyalty card templates. Merchants will be able to create loyalty card templatesfrom their mobile device and upload them to the server. Customers will be able to downloadloyalty cards to their phone and store the information in their local database. Once downloaded,the customer can collect punches on qualifying purchases. After a predetermined number ofpunches, the customer earns a reward.Project Plan 9
6 - User interface descriptionThe User Interface for the system will be displayed on a mobile device with a touch screendisplay. The user will be presented with menu items and icons to navigate the system, includinga tabbed interface to switch between user profile, card information, and business searching.7 - Functional requirements The system shall allow the user to login and logout.The system shall allow the user to create an accountThe system shall allow merchants to create loyalty cardsThe system shall allow merchants to expire existing loyalty cardsThe system shall allow merchants to verify customer punchesThe system shall allow merchants to verify customer rewardsThe system shall allow customers to search for local businessesThe system shall allow customers to select loyalty cardsThe system shall allow customers to download loyalty cardsThe system shall allow customers to redeem punchesThe system shall allow customers to redeem rewardsThe system shall allow the database to store a history of completed punch cardsThe system shall allow the merchant to view card history for their businessThe system shall allow the customer to view personal card history for completed rewards8 - Non-functional requirementsProject Plan 10
The system shall be developed using the Appcelerator SDKThe system shall use an encrypted SQLite database for local storage to prevent otherapplications from interacting with a user’s card dataThe system shall utilize hashing verification for punch a reward verification9 - Market SurveyOur mobile rewards platforms rests on the cusp of two of the largest and most rapidlyexpanding industries- online advertising and the mobile application space. Analystfirm research2guidance estimates that the mobile application space will becomea “15.65 billion [US Dollar] business in 2013.” The New York Times reports that in2009 “worldwide spending on mobile advertising amount[s] to 1.4 billion [USDollars].” Together the market is worth nearly 18 billion US Dollars. The current state ofthe mobile phone market reflects that Apple, Android and Windows phone account for69% of the market. However, with Blackberry use in sharp decline and windows phoneundergoing steep increase in user-ship, it is clear that the top market contenders will beApple, Android, and Windows phone. Our cross platform application and will inherentlyrun on Android and Apple phones. The potential for a new and revolutionary product inthis market space is staggering.Figure 9.1. This graph demonstrates the market capitalization of the various mobile operating systems. 9Notice smartphones have 40% of the cell phone market and continues to growth.i) Mobile Application SpaceProject Plan 11
Figure 9.2. This figure illustrates the research2guidance’s prediction of the enormous growth in revenueof mobile apps from 2012 to 2015 where it will reach 100.1 billion usd.7Analyst firm research2guidance recently published a study of the mobile applicationspace. The study indicates that the mobile application market will grow from a 1.94billion US Dollar business in 2009 to a 15.65 billion business in 2013. This growthrate of nearly 807% and is a clear indicator of the current and future strength of thismarket.Research2guidance also indicates that the smartphone user base to grow from100 million to 1 billion in that same time frame; this is a 1000% growth rate. This growthrate is an indication of a transition from the laptop or desktop computer to a smallerand more portable medium. Companies will have no choices but to follow this trend,increasing their exposure in the mobile advertising arena especially when we considerthat “currently, only 10% of the Fortune 2000 companies are engaging their customerbase with a mobile application.” (source: BRG)One can examine a clear and definitiveneed for an advertising platform catering to companies transitioning to the mobilespace.ii) Mobile Advertising MarketThe New York Times reports that in 2009 “worldwide spending on mobile advertising amount[s] to 1.4 billion [US Dollars].” The number in 2010 was “ 1.6 Billiongenerated in 2010.”(Source: IT research firm Gartner)However, research2guidance alsoindicates that the smartphone user base will grow from 100 million to 1 billion in thatsame from 2009 to 2013; this is a 1000% growth rate and as the number of internetconnected user increases this will drive mobile advertising revenue into double digitgain, year afterProject Plan 12
10 - DeliverablesThese are artifacts that will we will need to turn in. Project Plan 1st Revision Project Plan 2nd Revision Design Document 1st Revision Design Document Final Revision Project Plan Final Revision Presentation Customer Loyalty Application for IOS/Android11 - Work planThis section will discuss how the work is broken up into smaller modules. It will also discuss theschedule in which the work is done.11.1 Work BreakdownFigure 11.1 Shows our work breakdown structure.Project Plan 13
11.2 Task BreakdownTaskSummaryTime FrameProject Plan Rev19/14 - 9/28Project Plan Rev29/29 - 11/9Project Plan Final11/10 - 11/29Requirement Gathering9/14 - 9/28ResearchDesign DocumentLearn technologiesrequired to /29 - 10/27Project Plan 14
Design Document FinalRev10/28 - 11/29Implementation ServerSideDatabaseDesign and creation ofdatabase10/15/12 - 11/04/1213 weeksVerification EncryptionHandles the redemptionof punches11/26/12 - 12/16/1243 weeksCard ManagerManages and cardrequests11/26/12 - 12/16/1233 weeksHIstory ManagerHandles storing andretrieving previouscompleted cards11/05/12 - 11/25/1223 weeksAccount ManagerHandles anything thatinvolves accounts11/05/12 - 11/25/1223 weeksBusiness ManagerHandles anything thatinvolves businesses.11/05/12 - 11/25/1223 weeksPhone UIEntire UI10/15/12 - 3/15/13115 weeksPunch Card/RewardVerificationModule handlesverification of punches12/17/12 - 01/06/1343 weeks01/07/13 - 01/27/1353 weeksClient SideLoyalty CardHistory ViewerLets users view previouscards01/28/13 - 02/17/1373 weeksAccountHandles the login/logoutof user and creation ofaccounts.11/05/12 - 11/25/1223 weeksBusinessHandles the searching ofbusinesses12/17/12 - 1/6/1363 weeksProject Plan 15
DatabaseStores data such asprevious cards.10/15/12 - 11/04/1213 weeksCard SynchKeeps card data syncedwith server1/28/13 - 2/17/1363 weeksUnit TestingEach Module will betestedUnit testingincluded duringimplementationSystem TestingAs Modules are3/16 - 4/20integrated, they will betested as a system. Thiscould mean modifying anymodule.719 weeksTesting11.3 Project ScheduleProject Plan 16
Figure 11.1 Project Schedule - Please note: Shaded black means percentage done. Also, somemodules are done before the scheduled starting date,meaning we are ahead of schedule. Wewill be pulling in modules as needed if they are finished early.Project Plan 17
11.4 Project Team InformationProject manager: Christopher WaltersHe is in charge of setting up weekly meeting with the advisor and the client. He alsomanaging communication between client, advisor, and team members.Project planner: William TranHe is in charge of weekly report, team weekly meeting, and divided up tasks amongteam members.Website master: Van NguyenShe is in charge of creating, designing, and update team website.Developer: Van Nguyen, Christopher Walters, and William TranAll of us are in charge of creating the project plan, design documents, gatheringrequirements, and implementing the application.11.5 Communication ManagementTeam Communication:Communication MethodTimeSummaryWeekly meetingSunday @ 4:30-5:30,Wednesday @ 7-8Meet on sunday to go overour to do list and distributeworks among team members.Meet on Wednesday forworks progression updateand add more works.EmailAnytimeUse email for questions orrescheduling purposeAdvisor and Team Communication:Project Plan 18
Communication MethodTimeSummaryWeekly meetingWednesday @1-2Meet on Wednesday toprovide the advisor our workprogress and future plan.EmailAnytimeUse email for questionsClient, Advisor, and Team Communication:Communication MethodTimeWeekly meetingEmailSummaryMeet once a week to providethe client our work progress,future plan, and ask clientquestions or answer theirquestions.AnytimeUse email for questions11.6 Risks and Risk ManagementRiskMitigationR1. Losing a teammemberWe will contact our advisor.R2. Limitedexperience ofAppceleratorWe will begin learning the Appcelerator framework as early aspossibleR3. None of us havea mac to do IOSdevelopment.We will use macs on campus for development.R4. The scheduleplanned might not berealistic, because ofR2.We will begin implementation as modules are designed.Project Plan 19
Project Plan 20
history, and loyalty card templates. Merchants will be able to create loyalty card templates from their mobile device and upload them to the server. Customers will be able to download loyalty cards to their phone and store the information in their local database. Once downloaded,
team xl team 2. t050710-f xl team 3. t050907-f xl team xl team 4. t050912-f xl team xl team 5. t050825-f xl team xl team 6. t050903-f xl team. 2 7. t050914-f xl team xl team 8. t061018-f xl team 9. t061105-f xl team name xl team 10. t060717-f xl team xl team 11. t070921-f xl team xl team xl team 12. t061116-f xl team. 3 13. 020904-f name/# xl .
Customer satisfaction has identified as an important influencer on customer loyalty. Further, customer trust impacted by customer satisfaction which proved that customer satisfaction is an antecedent of customer trust. Moreover, an indirect relationship between customer satisfaction and loyalty through customer trust was observed.
Round 3 Game 1 Game 2 Game 3 Game 4 Team 1 Team 7 Team 8 Team 2 Team 6 Team 5 Team 4 Team 3 Continuing the method, which team plays Team 7 in Round 4? Team . 14 Infection Model This is a simple example of how people in a community might become infected with a disease. O
Challenges of Project Development in non-Software Factories Not always they have big project, lots of changes request, small demands, . Project Based Sample Structures (Client Samples) 5 (AGILE) (TRADITIONAL) . Plan Project Sprint Plan Project WBS Plan Project Test Plan Project Master Test Plan Product Test Plan
team members throughout the contest with each team member losing at least 10 pounds, the team name will be placed in a drawing for one of three grand prizes. The First Team drawn will win 250 each, The Second Team drawn, 500 per team member, and the Third Team drawn will win 1,000 per team member. Team CAVHCS is already off to a great start. The
U13 GIRLS DIVISON 1 6 teams 3 game round-robin with one cross-over After round-robin, 1 v 1, 2 v 2, 3 v 3 Game 1 Game 2 Game 3 Total Place Field Home Score Away Score Team Pts /- Saturday 10:30am Burnett 1 Team A Team B Orange Pool 10:30am Burnett 2 Team D Team E A Richmond FC Strikers 12:00pm Boyd Red Team C Team F B CMF Xtreme 3:30 pm Burnett 1 Team F Team D C Comox
Tim Moore 2006 (Third Team) Todd Ptacek 2007 (Second Team) Patrick Smyth 2009 (First Team) Andrew Hills 2012 (Third Team) Logan Renwick 2013 (Second Team) 2013 - 60m Hurdles, Indoor 4x400m Relay, 2014 (First Team) Women Theresa Rice 2009 - 3,000m, 10,000m1989 (First Team - XC) Alison Klemmer 1999 (Third Team) 2000 (Second Team)
Human Resources Management Human Resources Management HR Management Planning Responsibility & Authority Labor Compliance Labor Relations Acquire Project Team Organization Craft Hiring Develop Project Team Manage Project Team Close Project Team Project Human Resource Management includes the processes that organize, manage, and lead and close the .
