Customer Mobile Application for Retail - Reciept Manager
Objective: Customer Mobile Application for ABC Retail Inc Abstract: ABC Retail Inc is a grocery retailer running over 100 brick and mortar stores all over the country. The major pain point for their customers is returns process. So far, the retailer has been issuing a physical receipt to the customers after successful purchase. The customers are facing difficulty in cases where the receipt is lost or mutilated when they go for returns. Transaction receipt is a mandatory piece of document required by the retailer to process returns. To improve the returns process, the retailer wants to issue electronic receipt and manage them on behalf of their customers. End Users:Customers Story Board : 1. Customer walks into the store. 2. After purchase, at the checkout counter, the customer provides his/her membership details. The point of sales system generates an electronic receipt and ties it to the customers account maintained by the retailer. The e-receipts are stored on the retailers store/central server. 3. Customer opens Receipt Manager mobile application on his phone and synchronizes with the store systems and retrieves the latest transaction receipt(s). 4. Customer verifies the e-receipt and approves the transaction details on the phone. [The reference to the e-receipt can be stored on the phone application and retrieved from store systems. The phone app should be able to tag reference to the receipt with meaningful keywords for later search, archives and deletes]. 5. Upon approval, the customer pays for the purchase and walks out of the store. Returns Process 1. Customer walks to a customer care center at the retail store. 2. Customer pulls the e-receipt from the phone application by searching through referenced receipts on the application. [The search should cover both data on phone aswell as the data stored on the store systems. But, it should be transparent to the customer] 3. The point of sales system at the customer care section verifies the receipt and processes returns. [The system, Receipts Manager, should enable auto expiry of e-receipts based on returns policy.] Other Relevant Info : 1. Retailer hosts customer, transaction and receipt details on their store/central server. 2. Connection to the store server will be over wifi or internet. 3. There are four major entities involved in the whole solution viz mobile app, Receipt Manager, Checkout System, and Customer Care System. Receipt Manager runs on a store server and provides all the logic to manage receipts for a customer. Checkout system runs on a cash register in the store and can upload/download receipts to/from the store server. Customer Care System processes returns for any given transaction. Non - functional requirements: User Experience: Application should be adaptive enough to render on multiple devices with various form factors. Security: All transaction should be over secured channel (SSL). Application Management:Application should offer direct update facility (Android / iOS) so that customer need not to go to application stores to update application and also application versions should be controlled from backend administrative console itself. Target Operating Systems: Application should be developed as hybrid mobile app and must be tested with: 1) At least one of the physical smart phone Device OS (Android, iOS, BlackBerry, Windows Phone) as download and installable App 2) Minimum of 2 smart phone SDK emulators (Android, iOS, BlackBerry, Windows Phone) 3) Mobile Web Browser/Mobile Browser Simulator. Application Screen shots on all of the above needs to be submitted as part of project submission.
2. Customer Mobile Checkout Appllication for Retail Industry Objective: Customer Mobile Application for ABC Retail Inc Abstract: ABC Retail Inc is a grocery retailer running over 100 brick and mortar stores all over the country. Checkout at their stores has been a major pain point for their customers. They want to improve the shopping experience for the customers by enabling them to use smart phones for checkout process. End Users:Shoppers/Customers Story Board : 1. A customer walks into a ABC Retail Inc store. 2. Opens the Shop Smart mobile application on his/her smart phone. 3. The customer starts building shopping cart on their phone by scanning items of interest and puts the scanned items into the physical cart as well. (Product scanner is provided by the application which uses inbuilt camera for scanning). The cart details are persisted onto a store server. 4. Once customer wishes to checkout, a Checkout Barcode is generated on the phone by the application. The barcode encodes the key to the shopping cart built by the customer. 5. Customer walks to a designated checkout area called, Checkout Station, in the store and presents the Checkout Barcode to the Checkout Station. A Checkout Station is a regular checkout register which are not manned by a Store Cashier. It is similar to a Self Checkout register in a store with an exception that the items need not be scanned at the register. 6. Checkout Station reads the barcode and downloads the shopping cart details from store server and presents the receipt after successful payment. 7. A notification is sent to the customer phone as an acknowledgement of successful transaction. Customer walks out of the store after the purchase. Other Relevant Info : 1. Retailer hosts product catalog on their store server. 2. Connection to the store server will be over wifi or internet. 3. There are three major entities involved in the whole solution viz mobile app, cart builder and checkout system. Cart builder runs on a store server and provides all the logic to build a cart. Checkout system runs on a cash register in the store and can download the cart details from the store server for the given transaction code. Payment need not be done from the phone. It would be the responsibility of the checkout system. Non - functional requirements: User Experience: Application should be adaptive enough to render on multiple devices with various form factors. Security: All transaction should be over secured channel (SSL). Application Management: Application should offer direct update facility (Android / iOS) so that customer need not to go to application stores to update application and also application versions should be controlled from backend administrative console itself. Target Operating Systems: Application should be developed as hybrid mobile app and must be tested with: 1) At least one of the physical smart phone Device OS (Android, iOS, BlackBerry, Windows Phone) as download and installable App 2) Minimum of 2 smart phone SDK emulators (Android, iOS, BlackBerry, Windows Phone) 3) Mobile Web Browser/Mobile Browser Simulator. Application Screen shots on all of the above needs to be submitted as part of project submission. Tools & Technologies: IBM Worklight JQuery Mobile / Dojo Mobile / Sencha Mobile Tomcat / Jetty webserver on store server to host Receipt Manager System. Derby / DB2 (Database) / MySQL (persist e-receipts and transaction) Third party JavaScript / REST APIs as appropriate
3. Customer Ordering Mobile App of a Pizza house Objective: Customer Mobile Application for MFPizza. Abstract: MFPizza sells pizzas and has around 40 outlets around the city. Today they offer order booking facility to customer through telephone/call center and online web. They plan to extend online order booking facilities to smart phones to reach more customers. End Users: Customers Functional Requirements: Mobile application will publish complete catalog of pizzas with possible add-on options and customers should be able to prepare and customize an order as per their preference. Customers should also be able to customize and place an order from their previous order list or favorite orders list. Mobile application should be able to receive push notifications as per existing offers available in specific location stores. Customers should be able to locate a nearby store from the application with appropriate driving directions. Mobile application should also offer customer login with user ids of social networking sites like Facebook, Google etc. Non - functional requirements: User Experience: Application should be adaptive enough to render on multiple devices with various form factors. To make customer experience best advanced capabilities like geo-location, augmented reality and mashups should be used. Application Analytics: MFPizza also need application usage analytics such as orders coming in from specific geo location / area, application access on multiple target device operating systems, daily hits, new users etc. Security: All data stored offline as part of application must be encrypted, connectivity to mobile server should be over SSL and each of the backend service exposed must be protected. Application Management: Application should offer direct update facility (Android / iOS) so that customer need not to go to application stores to update application and also application versions should be controlled from backend administrative console itself. Target Operating Systems: Application should be developed as hybrid mobile app and must be tested successfully on one of the smart phone Device OS (Android, iOS, BlackBerry, Windows Phone) and Mobile Web Browser. Tools & Technologies: IBM Worklight JQuery Mobile / Dojo Mobile / Sencha Mobile WebSphere Liberty (Application Sever) Derby / DB2 (Database) IBM JazzHub Third party JavaScript / REST APIs as appropriate 4. Insurance's Field Sales Representative App Objective: Smartphone Application for MFInsurances field sales representatives Abstract: MFInsurance is insurance company with presence in more than 200 cities. Companys sales organization consists of more than 2000 field representatives. MFInsurance plan to introduce smart phone application for field sales reps to improve productivity of sales force. Application will allow field reps to discuss various policies options with customers/ prospects while in field. End Users: MFInsurance field sales reps Functional Requirements: Smartphone application developed for field sales reps will provide detailed information about companys insurance products and ongoing offers which can be discussed with customer prospects in field. Field sales reps will be able to maintain their daily calendar activities like daily appointments, meeting notes, customer follow ups required and missed meetings. Mobile application will help field sales reps to capture customer information and customer opted policies information in the application with appropriate customer signature, which will be immediately be synchronized with backend policy issuance database. Mobile application should also help field sales reps to track history of customer prospects and status of existing customer policies. Application is supposed to work in online and offline mode where all the content related to products get synchronized from backend content management repository on regular intervals and is available in offline mode. Application will also help field sales representatives to maintain their sales quota and territory profile for sales visibility purposes. Non - functional requirements: User Experience: Application should be adaptive enough to render on multiple devices with various form factors. Application Analytics: MFInsurance also need application usage analytics such as orders coming in from specific geo location/ cities, application access on multiple target device operating systems, daily hits, new users etc. Security: All data stored offline as part of application must be encrypted or available with password access only, connectivity to mobile server should be over SSL and each of the backend service exposed must be protected. Application Management: Application should offer direct update facility (Android / iOS) so that customer need not to go to application stores to update application and also application versions should be controlled from backend administrative console itself. Target Operating Systems: Application should be developed as hybrid mobile app and must be tested with: 1) At least one of the physical smart phone Device OS (Android, iOS, BlackBerry, Windows Phone) as download and installable App 2) Minimum of 2 smart phone SDK emulators (Android, iOS, BlackBerry, Windows Phone) 3) Mobile Web Browser/Mobile Browser Simulator. Application Screen shots on all of the above needs to be submitted as part of project submission. 5. Telecom Self Service Application Objective: Customer self service app for MFTelecom. Abstract: MFTelecom is a telecom provider which offers cellular, landline and broadband connections to customers in multiple states of India. Organization wants to reduce customer service cost and has decided to introduce a mobile application for smart phone users. This application will offer deeper engagement with customers and will improve customer satisfaction. End Users: Customers Functional Requirements: Self service application offered to MFTelecom customers will allow customer to configure their all set of accounts (landline, cellular, broadband etc) on smart phone itself and customers can raise all service requests from this application interface. This application will also allow customers to check all previous bills, payment history, and unbilled balance and value added services activated on the connections. Application will also inform end users with push notifications based upon customers profile and preferences. Application should also be integrated with payment gateway systems to make final bill payments from the application. Application should allow end users to login with social networking user ids like facebook account, google account etc. Non - functional requirements: User Experience: Application should be adaptive enough to render on multiple devices with various form factors. To make customer experience best advanced capabilities like geo-location, augmented reality and mashups should be used. Application Analytics: MFTelecom also need application usage analytics such as requests coming in from specific geo location / area, application access on multiple target device operating systems, daily hits, new users etc. Security: All data stored offline as part of application must be encrypted, connectivity to mobile server should be over SSL and each of the backend service exposed must be protected. Application Management:Application should offer direct update facility (Android / iOS) so that customer need not to go to application stores to update application and also application versions should be controlled from backend administrative console itself. Target Operating Systems: Application should be developed as hybrid mobile app and must be tested with: 1) At least one of the physical smart phone Device OS (Android, iOS, BlackBerry, Windows Phone) as download and installable App 2) Minimum of 2 smart phone SDK emulators (Android, iOS, BlackBerry, Windows Phone) 3) Mobile Web Browser/Mobile Browser Simulator. Application Screen shots on all of the above needs to be submitted as part of project submission.
6.E-Detailing App - Digitalization of Brouchers / catalogs for specific products (completely customizable) Topic Details Coming Soon 7.Employee Information App - Internal HR application for information access and approvals Topic Details Coming Soon 8.Expense Tracker - Anytime access to update all expenses quickly ... and monitor Objective: Mobile Application for tracking daily expenses and planning for future expenses. Abstract: MFExpense Tracker is an smart phone application which allows you to record your fixed, variable daily expenses and report effectively on the same. Application will help customers to plan their future expenses as per the past history of expenses. End Users: Customers Functional Requirements: This smart phone application should allow end users to record all sort of daily expenses like grocery, medical, education, entertainment, automobile, insurance etc. It should also help customers to analyze fixed expenses versus variable expenses. Application should report these expenses in very useful manner for user to help him make decision about future expenses. Application need to work in online as well as offline mode. In offline mode application will allow expenses to be recorded and saved locally on the device and this local expense records should be synchronized with backend database as soon as server connectivity is available. Application should also allow end user to set threshold values for monthly expenses and appropriate push notifications should be sent to user whenever expenses exceed these threshold values. Mobile application should also offer customer login with user ids of social networking sites like Facebook, Google etc.. Non - functional requirements: User Experience: Application should be adaptive enough to render on multiple devices with various form factors. To make customer experience best advanced capabilities like geo-location, augmented reality, reporting and mashups should be used. . Application Analytics: MFExpense Tracker also need application usage analytics such as expense data coming in from specific geo location / area, application access on multiple target device operating systems, daily hits, new users etc. . Security: All data stored offline as part of application must be encrypted, connectivity to mobile server should be over SSL and each of the backend service exposed must be protected. Application Management: Application should offer direct update facility (Android / iOS) so that customer need not to go to application stores to update application and also application versions should be controlled from backend administrative console itself. Target Operating Systems: Application should be developed as hybrid mobile app and must be tested with: 1) At least one of the physical smart phone Device OS (Android, iOS, BlackBerry, Windows Phone) as download and installable App 2) Minimum of 2 smart phone SDK emulators (Android, iOS, BlackBerry, Windows Phone) 3) Mobile Web Browser/Mobile Browser Simulator. Application Screen shots on all of the above needs to be submitted as part of project submission. Tools & Technologies: IBM Worklight JQuery Mobile / Dojo Mobile / Sencha Mobile WebSphere Liberty (Application Sever) Derby / DB2 (Database) IBM JazzHub Third party JavaScript / REST APIs as appropriate Team Size: 1 3 students
9.Furniture Shop / Grocery shop - Online retail stores , store locator, shipment tracker etc. Topic Details Coming Soon 10.Learning Management System App - Completely customization which support HTML5 contents / images Topic Details Coming Soon 11.Loyalty Program Management - generalized which can be customized for any industry Topic Details Coming Soon
12.Medical Representatives App - Sales Man app but customized for pharmaceutical companies Objective: Smartphone Application for MFPharmas medical representatives Abstract: MFPharma is a pharmaceutical company with more than 20 products in market. Companys sales organization consists of more than 1000 medical representatives introducing MFPharmas products in different cities all across India. MFPharma plan to introduce a mobile application for medical reps to discuss about companys products and log sales orders from various chemist shops. End Users: MFPharmas medical representatives Functional Requirements: Smartphone application developed for medical representatives will provide detailed information about companys products and ongoing offers which can be discussed with doctors and chemists. Medical representatives will be able to maintain their daily calendar activities like daily appointments, meeting notes, and missed meetings. Mobile application will help medical representatives to capture sales orders from various chemist shops and log in to backend order management system directly from the chemists shop itself. They should also be able to track history and status of all past orders from the mobile application. Application is supposed to work in online and offline mode where all the content related to products get synchronized from backend content management repository on regular intervals and is available in offline mode. Application will also help medical representatives to maintain their sales quota and territory profile for sales visibility purposes. Non - functional requirements: User Experience: Application should be adaptive enough to render on multiple devices with various form factors. Application Analytics: MFExpense Tracker also need application usage analytics such as expense data coming in from specific geo location / area, application access on multiple target device operating systems, daily hits, new users etc. . Security: All data stored offline as part of application must be encrypted or available with password access only, connectivity to mobile server should be over SSL and each of the backend service exposed must be protected Application Management: Application should offer direct update facility (Android / iOS) so that customer need not to go to application stores to update application and also application versions should be controlled from backend administrative console itself. Target Operating Systems: Application should be developed as hybrid mobile app and must be tested with: 1) At least one of the physical smart phone Device OS (Android, iOS, BlackBerry, Windows Phone) as download and installable App 2) Minimum of 2 smart phone SDK emulators (Android, iOS, BlackBerry, Windows Phone) 3) Mobile Web Browser/Mobile Browser Simulator. Application Screen shots on all of the above needs to be submitted as part of project submission. 13.Meter Reading App - Camera integration , GPS location integration Topic Details Coming Soon 14.Online Chat App - focus on enterprise Collaboration, skills search and anywhere communication at low cost Topic Details Coming Soon 15.Sales Man App - generalized app for sales force of any organization. Topic Details Coming Soon 16.Student Management - Student records, Attendance, Exam schedules, fee schedules, notifications to parents etc Topic Details Coming Soon