Arnima Jain | Freelancer Business Analyst Consultant Vodafone (Sample Document)

Business Analyst Consultant - Vodafone (Sample Document)

Table of Contents A. REQUIREMENT OVERVIEW .........................................................................................................................2 B. TECHNICAL ARCHITECTURE......................................................................................................................2 C. PROPOSED SOLUTION ...................................................................................................................................3 D. PROJECT APPROACH .....................................................................................................................................3 E. FUNCTIONALITY .............................................................................................................................................3 F. NON-FUNCTIONAL PREREQUISITES ....................................................................................................... 12 G. OUT OF SCOPE ................................................................................................................................................ 14 H. MOBILE APPLICATION DEVELOPMENT FEASIBILITY ..................................................................... 15 I. PROJECT RISKS.............................................................................................................................................. 15 J. WORK EXECUTION BY TEAM.................................................................................................................... 16 K. HOSTING ENVIRONMENT (DEPLOYMENT PLATFORM) ................................................................... 16 L. ARCHITECTURE............................................................................................................................................. 17 M. CLIENT PROVIDED DETAILS (RECEIVED DURING ANALYSIS) ...................................................... 17 N. PROJECT PRE-REQUISITES ........................................................................................................................ 17 O. PROJECT RESPONSIBILITY ........................................................................................................................ 17 P. ASSUMPTIONS ................................................................................................................................................ 18 Q. DISCLAIMER ................................................................................................................................................... 18 R. DELIVERABLE DATE .................................................................................................................................... 18 S. PROJECT SCHEDULE .................................................................................................................................... 19 T. DELIVERABLES .............................................................................................................................................. 19 U. SOFTWARE DEVELOPMENT PROCEDURE ............................................................................................ 19 V. WARRANTY ..................................................................................................................................................... 20 W. MAINTENANCE & SUPPORT (EXTRA COSTS) ....................................................................................... 20 X. CHANGE REQUEST PROCEDURE ............................................................................................................. 20 Y. USER ACCEPTANCE TESTING ................................................................................................................... 21 A. Requirement Overview The client wants to develop a mobile application, which will provide the user with various functionalities. The user can access to various details such as program launched by the organization, view various announcements by the organization, and apply/register for the schemes. The client also wants Our Company to provide users with the program basic details, its highlights and term and condition. The users can share/comment/like/dislike the announcement. The user can also provide their valuable feedbacks B. Technical Architecture C. Proposed Solution Our Company will develop Mobile Applications in android & IOS platform .Our Company will develop the mobile application so the users of Vodafone can access to the details of the program launched by the organization, basic program information with highlights of the program, terms & condition. To provide the user with the announcements functionalities, to display the users with the latest announcements made. All the latest announcements will be added by the admin. The user can view the announcements and can share/comment/like or dislike the announcements. In addition, the user will also will be asked to provide their valuable feedback as and when it is necessary. Our Company will also provide the technical Support & Maintenance of the Application with Patch Updates/ Application Upgrades. D. Project Approach-. Art Document/Workflow PDF document Application Designing Application Development Alpha Delivery Bug Fixing of Alpha Delivery Beta Delivery Bug Fixing Live Delivery on Respective Store E. Functionality 1. Registration 1.1. User Functionality: 1.2. The User can register itself into the application for getting the further functionalities from the application. The user one registered into the application will get all the latest updates, announcements. To register oneself into the application the user will get the following screen:- Register with Vodafone Enter Your Number: Create Login ID:Create Password: Re-enter Password: Confirm to the term and condition Submit Reset 2. Login: The user can login into the application to view the detailing as per his or her needs. Log In Your Login ID:Your Password: Sign In 2.1. After logging into the application the user will get a greeting page “Welcome to Vodafone.” 2.2. The user can see various tabs in the page. The tabs will be as follows: 2.2.1. My Profile 2.2.2. My Plan 2.2.3. Program Details 2.2.4. Announcements 2.2.5. Schemes 3. Forgot Password: If the user forgets his or her password the user can click on the forgot password link. Forgot Password E- mail: Submit Reset 3.1. The user can enter his/her registered e-mail address and the user will receive change password link on their requested mail ID 3.2. The user may click on the following link and can change its password. Once the user will click on the following link the user will be re-directed to the following page Create a new Password Current Password New Password Confirm New Password: Set Password 3.3. The user’s password will be changed successfully. 4. Manage Profile: The user can manage his or her profile. The user can manage or change the following details:My Profile: Change Profile Picture Name: Phone Number: Login ID: Password 5. Push Notification: The user will be notified with the alerts or announcements. The push notification is particularly to notify the user when the user is not using the application. Therefore, the users do not miss out any important alerts. 6. My usage: The entire registered user will get 100 MB. Therefore, the user can keep a track of the data they are having and left with, when the data will be expired. 7. Program Details: The user can view the program details. The users will see two tabs:- 1st) Upcoming Event 2nd) Past Events 7.1. Past Events & Upcoming Event: The user can see the list of upcoming events and the list of past events. The user will see the list as follows: Past Events Upcoming Events Date Title Date Title Time View Event Time View Event Program Details Event details About the Event Schedule Venue Day Map Time Gallery Layout Plan Terms & Condition The user can select from the drop-down menu. The user can apply/register to the event by clicking on any of the following option. 7.2. Highlights: The user can see the highlights of the particular events also. Highlights of the event (Name of the Event) 1) 2) & so on 7.3. Apply/Register for the scheme: - The user will have the following details in the particular tab. The user will get the list of events and the user will get the options of applying or registering itself for the event. The user can view the upcoming events or the event that is today itself. Event Title1 Day Time Tag Line [Drop-Down] Interested/ Maybe Going Not Going Event Title2 Day Time Tag Line [Drop-Down] Interested/ Maybe Going Not Going Event Title 3 Day Time Tag Line [Drop-Down] Interested/ Maybe Going Not Going 7.3.1. After selecting the preferred option from the drop-down list, if the user selects the going option then the user will be re-directed to a form filling page where the user has to register itself if the user is interested in going for the event. 7.3.2. The following form will appear:Event Registration Form First Name: Last Name: Gender: [Drop-Down] Address: City: State: Zip-Code Send E-mail Confirmation to:- Phone Number: 7.3.3. The user will register itself for the event by filling up the following form. The user will get a confirmation mail after the user has registered itself for the event as per the e-mail mentioned by the user. 8. Announcements: Announcements regarding any upcoming events or program the user will get the announcement. The users can like/dislike/comment/share the announcement accordingly. Announcement Announcement Title Date Year Announcement Information Like/share/Dislike/Comment 9. Feedbacks: The users can provide with their valuable feedback. Feedback Form Enter name: Enter E-mail: Rate your Experience: Overall Experience- Rate from 1-5 Recommendable or sharable content- Rate from 1-5 Content is relevant or useful-Rate from 1-5 Easy to use- Rate from 1-5 Short Description:- Submit 10. Administrative Functionality 10.1. Manage Profile 10.1.1. The admin can manage, view, and edit his /her profile. My Profile: Name: Phone Number: Login ID: Change Profile Picture Password: 10.2. Manage Users: The admin will manage the users registered on the application. The admin will sub-admin and will have particular rights & privileges. Manage Users & Sub-admin Actions Username Name E-mail Status(Active or disabled) Last Login View Edit Delete The admin will have sub-admin. The sub-admin will have rights and privileges and the can perform certain task. The sub-admin can create an even, view or can edit it accordingly to the rights and permission given by the admin. 10.3. Role & Responsibilities: The admin will give the rights and privileges to the users and the sub-admin. 10.3.1. The admin will get a drop-down option so it can choose its user. 10.3.2. User-Type:- (drop-Down) Users or sub-admin User or group ReadOnly Edit Add Delete Add Images Add Files 10.3.3. The super-admin will also approve the content. The sub-admin will upload the content, it will go to the super-admin for approval, and the super-admin will approve the content accordingly. Content Published Content(Count) ID Title Author Updated Unapproved Content(Count) Request status Operation (Approved/Pending/Cancelled) Date Year Edit View Delete 10.4. Program Details: The admin will update the events upcoming in different cities. The admin will update basic program details, Schedule, Venue, and gallery. The program logo will also be display with the organizations logo (Vodafone) and the logo of the partner associated with the event. Title of the Event: Location: Start Date/ Time: End Date/Time: Privacy: (drop-down) open or close Day: Event DetailEvent Photo/Video: Create Event Cancel The admin can view the program detail as follows: Event [Add New] Search Event: [ ] All (14) Action:- [Show all dates] [Show all event dates](Drop-Down) Title Published Date Event Date Venue Added By 10.5. Apply /Register for the scheme: The Admin will be notified with the number of user that is going in the event. The admin will have the number of counts of the user interested/maybe, going and not going. Event 1 Going Interested/Maybe Not-Going 11 5 6 Going Interested/Maybe Not-Going 11 5 6 Event 2 10.6. Announcements: The admin will update the users with the upcoming events by giving announcements regarding it. Announcement Title: Announcement Body: Visible From: Expired At: Add Announcement 10.3.1. The admin can view the announcement as follow: Announcements Title Author Status(Published or Draft) Date 10.7. Feedback: The admin can view the user’s valuable feedback. The admin can view the feedback as follows : Feedback ID Feedback Date E-mail Approved Status (Yes/No) Action View Delete Make Approve 10.8. Reports: The admin will have reports of all the records. The admin will have reports as follows:Reports Reports Date File Report Name Report By Action View Delete 10.8.1. The number of user registered 10.8.2. Number of feedback received. 10.8.3. The number of users “going” & registered 11. Design Integration (If Client is provided the designs): a. Logo / Branding and Graphics will be provided by Client for both iPhone/iPad applications. b. All designs will be specific to requirements and in layers PSD format. c. No revisions or changes to the PSD’s would need to be done once received. d. Our Company would be converting the PSD to PNG as required for Application development. e. Our Company will do design integration of the requisite PNG’s to the Apps. f. Splash screen needs to be developed form PSD. g. The application will have some level of animation in splash screen but extensive animations will not be part of the scope. 12. Mobile Application Download: 12.1. The users will be able to download application from respective Mobile Store or web site for which stores are not available. 12.2. The client will provide store account credentials to deploy application on respective mobile store. F. Non-Functional Prerequisites 1. User Environment: The application will be compatible to the following mobile OS versions for each platform: 1.1. iPhone: iPhone will run on iPhone device having 8.0 OS or higher version 1.2. iPad: iPad application will run on iPad device having OS 8.0 or higher version. 1.3. Android: Android application will run on Android OS 4.4 or higher version. 2. Device Resolutions: Platform iOS Android Device OS Resolutions iPhone 5c, 6, 6s iOS 8+ iPad 2,3,4 iOS 8+ Android Smartphones OS 4.4+ 960x640, 1136x640, and 750 x-x768 and 2048x-x600, 1280x768, 1280x720, 1080x1920, 1920x1200 3. Orientations: 3.1. iPhone 3.2. iPad 3.3. Android 4. Modes: 4.1. iPhone 4.2. iPad 4.3. Android 5. Analytics: Client will provide Google Analytics code for implementation. This will help give the client a better view on the usage statistics. G. Out of Scope The following are NOT covered in the scope of this document. Our Company can provide the services at an extra cost. 1. General 1.1. Any functionality other than mentioned under Functional Requirement. 1.2. Any Installation – Support - Communication for 3rd Party software’s other than Suggested by Our Company or mentioned under functionality requirements. 1.3. Hardware Compatibility – Identification for Deployment platform. 2. Database 2.1. Database Support on Client’s server. Our Company will install and configure the required database. 2.2. Database Migration. Our Company can provide Data Migration services at an extra cost. OR In Data Migration Services – Image editing or correction is NOT in scope. 2.3. Client will upload all data related to the application to the database. OUR COMPANY will ONLY upload those data that is necessary for testing of the project limited to 30 records. 3. Revisions 3.1. Any revisions in Graphics / Design after approval of ART DOCUMENT/ PDF Workflow Document would fall under Change Request and charged extra as applicable. 3.2. Product related research, photo search; photography is NOT covered in this scope. 3.3. Our Company will provide Store deployment only once. A repeat deployment would cost extra as applicable. 4. Documentation 4.1. User Guide and Application Manual are NOT in the scope of this document. 5. Licenses 5.1. Any Scripts, Extensions, Licenses, Modules, codebase etc. if need to be purchased in the course of development is NOT in the scope of Our Company and the Client will need to purchase the same and provide for integration implementation. 6. Any Functional changes required during development stage due to design provided by client may lead to change request if exceeds 4 hours of work. 7. Limitations of 3rd party applications, tools, etc. will be out of scope of this project. 8. The Web Services API is ready with complete documentation for immediate study and implementation. No functional development or enhancement of the same is in scope of this document. 9. Promotions, Offers, Discounts, Exciting Plans, Deals, Bill & Payment, Topups, Store Locator, Account Details, Chat Option and Recharge is not in scope of this document. H. Mobile Application Development Feasibility 1. For Windows Mobile there are different version of OS – We will check developed build for next OS version and if functionality will not be working due to change in APIs with different version of OS in mobile than separate developed will be required and same will be considered as additional under Change Request procedure and charged extra as applicable. I. Project Risks The following are the risk factors for the project. 1. Delay in approvals and sign-off on this document by client, and during the various stages of the project. 2. Delay by client in providing information like specifications, navigation details, Content, FTP, and Database access with full rights etc., as well as clarifications on queries from developer. 3. Designs have not been finalized / shown at the proposal stage – extra elements like animations, screens, etc. if built during designing, could hamper the project effort and costs estimates, resulting in Change Requests. 4. Questions unanswered at the project start up may lead to Change request if the requirement as understood by the team is not clear enough. 5. If there is delay in signing and Open Source or Codebase version mentioned in this document is no longer available for usage – there could be a change request for any compatibility issues or customization difficulties faced due to the change in codebase version. 6. Customization to 3rd Party ready codebase (if required) may not be achievable to requirements or if achievable may impact (on higher side) the cost and delivery schedules. We assume client understands the same. 7. iPhone Developer Program License Agreement section 3.3.1, the use of non-public APIs is not permitted. 8. Internet Connection should be established to access server side features from the application. 9. If the Application has to run in 4G - Application will run only in the 3G enable mobile devices. 10. If the Web Server / Web Services Ready - Client claims the web services are ready with documentation – but we have not checked the same to authenticate the claim. 11. Risk Factor – Technical Feasibility points - Real time testing will be required to validate the Technical Feasibility, hence a Risk. 12. When we submit application with Password protected areas that are not open to free registration - we also need to provide a test user that has access to the entire application. 13. To integrate Google map Integration in the application, for unsupported locations, thus non-availability of such locations in Google map. 14. Social media or 3rd party login may not function every time, due to API changes by providers. J. Work Execution by team 1. 2. 3. 4. 5. 6. Designing + Design Integration PDF Screen Flow Document Server Side Development / Management Web service Development, Integration & Documentation Programming / Coding / Testing Store Deployment for Native Apps K. Hosting Environment (Deployment Platform) 1. iPhone: IPhone 8.0+ 2. iPad: iPad OS 8.0+ 3. Android: Android device having OS 4.4+ L. Architecture 1. Development Environment – Software 1.1. iPhone: iPhone SDK 3.0 with Mac OS v10.5.7 or later 1.2. iPad: iPhone SDK 3.2.2 with XCode Version 3.2 1.3. Android: Android SDK 4.0 with Eclipse 4.5 2. Database Requirements 2.1. iPhone: SQLite 3.0 2.2. iPad: SQLite 3.0 2.3. Android: SQLite 3.0 M. Client Provided Details (Received during Analysis) 1. Client Document N. Project Pre-requisites The following are the requirements that need to be supplied to Our Company before start of the project. 1. Database details with full rights. 2. Logo and Graphics required for the mobile application. 3. UI Graphics required for the Mobile Application in PSD format (only if designs to be provided by client). 4. Web Services API details. (if required) 5. Design details and specifications. 6. Text in Word Document format. 7. Sample Data for Testing (not more than 30 records) 8. iTunes, Google Play Store, Windows Phone account credentials for Application upload 9. Coding standards and style 10. Our Company Suggests using SSL for web application that uses Web Services. Without SSL certificate implementation, the data that is being transferred over web services API may become vulnerable, could be hacked and can be misused. O. Project Responsibility Vodafone Responsibility Our Company’s Responsibility Mobile Application Design Design Extraction & Integration with Mobile Application Do UAT of Mobile Applications Do Bug Fixing of reported Bugs Upload Applications on respective Stores Do Store Testing once applications are on store. P. Assumptions 1. A full-time subject matter expert will be provided by the client, to enable real-time decisions during the development project. 2. Once this document is approved and signed-off, it supersedes any other documents provided by Client prior to sign-off. 3. Our Company will also provide a full-time subject matter expertise assigned to the project as well as a full-time Site General Manager who is empowered to make realtime decisions. 4. The Client has provided a site map and schema with technical details that has helped create this document however once this document is approved it supersedes any other documents provided by Client before or after approval of this document. 5. Our Company is not responsible for the development and/or operational performance of any 3rd party partners/tools as selected by Client. 6. Client will perform quality assurance to validate features requirements as per requirements document. 7. Performance of the application depends on the hardware selected, bandwidth allocated, size of data and concurrent users. 8. Logo / Branding are not a part of the project. 9. No E-Commerce functionality is required. 10. The application is in single language – English. 11. Tablet and Phone designs and functional flow will be same with only difference in screen size. 12. The client has a ready web server with complete database. Q. Disclaimer 1. Whilst some screen illustrations have been provided, these are neither comprehensive nor authoritative. It is expected that the final layouts / functionalities will be provided after a full Art Document / PDF Workflow Document is done by the development team. The SRS / Prototype will detail the exact requirements of each page in the system 2. Development Team Responsibility will cease if the application is rejected due to any Mobile Store Policy non-compliance. Though the development team will be responsible for any bugs or errors in coding corrections (if the reason for rejection). 3. At this proposal Stage, we do not check all feature prototyping and or feasibility testing. R. Deliverable Date 1. 2. 3. 4. 5. Total Project Time: xx Business days* Project execution will begin within 5 days of approval of the project. Our Company will define the project timelines, milestone in consultation with you. Our Company is responsible to deliver the software as per time agreed. Any delay in Approvals, Artifacts, and Project Requirements etc. would affect the project execution and result in putting the project on hold after three reminders. Once a project goes on HOLD, the production team will re-schedule and re-estimate the project plan. 6. Any delay of the delivery date after start of the project will be subject to clearance from the Our Company Management. * Time specified assumes all approvals will be received within 24 hours of submission and all Project requirements are furnished on time eg. Design specifications, Web Services etc. S. Project Schedule Date* Day 1 Day 2 Day 3 Day 4 Day 5 Activity Project Approved Project Kick Off Project Understanding & Designing Starts Android Development Starts Client Design Review T. Deliverables 1. 2. 3. 4. 5. 6. Project Plan Approved Designs in PSD Format PDF Screen flow Document Web Service API Details Documentation Mobile project codebase in zipped folder Backend/Website codebase in zipped folder U. Software Development Procedure 1. Our Company will come up with clear specification of the software, and Client must agree on the software specification. In your case, the specification is already defined in the Scope of Work above. 2. Our Company will appoint a Project Leader on the project as single point of contact for communication over Email, Phone, Yahoo, MSN, and Skype. 3. Our Company will send updates on daily/weekly/fortnightly basis for the project progress depending on the size of the project. 4. Our Company will open FTP account for downloading the software developed for testing purpose. 5. Our Company will deploy a team of Programmer, System Analyst / Project Leader team for executing the project offshore. This team size can be altered as per project requirements. 6. Our Company will provide technical support via Email, phone, Messenger services only. 7. Our Company will be using their indigenously developed coding standards and style for the application – if the Client has any specific standards to be followed then they must be sent to the development team before start of project in a comprehensive technical document. V. Warranty 1. iPhone and iPad– As the code is pre-approved by the store before Application is Live on the store – no warranty is required. 2. Other Platforms – 10 days from date of Beta Release. 3. Warranty does not include any functional enhancements that are NOT covered under Point E - Functionalities. Functional Enhancements or changes after 10 days would be charged as per actual. W. Maintenance & Support (extra costs) Our Company will provide maintenance and Support after the Warranty period is over under the following terms and conditions. 1. The Bug / Request will need to be submitted to Our Company by Email. 2. Each Bug / Request will be given a High, Medium or Low priority by the client. 3. Our Company will take a lead-time of 24 to 48 hours to revert back on the task status depending on the priority defined by the client. 4. High Priority will be attended first, medium next and Low as least level. 5. High Priority will be attended before and even during attendance to a Low priority task. i.e. If the developer is working on a low priority task and receives a High priority task, he / she will stop work on the low priority one and attend the high priority task. 6. Only one developer will work at a time for the maintenance and support. 7. In certain complex cases – Our Company may not be immediately be able to rectify or support on ASAP basis due to technical reasons and the client needs to understand the same. X. Change Request Procedure 1. Change requests will be collected and managed by the Project Leader. 2. Proper analysis of the change will be performed and an impact analysis and dependencies will be conducted to arrive at an execution plan for the same by the project leader in accordance with the Project Manager and the Business Analyst. 3. Project Leader will get the approval of the additional efforts from the client. 4. The Change Request may or may not be approved by the client. 5. On approval by the client the Change Request will be: 5.1. Invoiced as per the rates finalized under the commercial contract 5.2. The requested changes will be incorporated into the project schedule, executed and implemented. 6. The Change Request could include but not limited to: 6.1. Additional functionalities to be developed like reports, functional modules etc. 6.2. Deviation in functional flow of the application or a particular module. 6.3. Changes in reports, screens, design, number of page etc. 7. The Change Request will affect the delivery date and increase the project costs. 8. There may be other Change Request Processes introduced to the project during the Planning and Design Phase. 9. Social Media or 3rd party login integration may have repeat work due to changes in API from providers. These additional changes will be charged extra in change request. Y. User Acceptance Testing 1. Client will be given 15 days to do UAT, if the client does not revert back within the same period, the application will be deemed to be accepted as received - the project warranty period would be initiated and project considered as completed after warranty. 2. All bugs/issues found by client during UAT will be submitted in single batch only, so the team can work on all issues comprehensively instead of in fractured manner.