For reference, you need to download SPLITPAY SRS DOCUMENT from google

You have been made a Project Manager in charge of a system development project that is aimed at developing a client/server application that allows people to split and track costs and debts. The client portion of the application will run on an android device. The project is being funded by the Vice President of Mobile Apps. Other stakeholders include the VPs of the Legal department, Users, Hardware, and Finance.

Along with the new position you get:

• A development team to work with on the project
• A software requirement specification (SRS) document
• A cost estimate and service level agreement for the system.
• A systems analysis and design document for the project.

Page 5 of the requirements specification document will give you a quick overview. Appendix B (page 45) gives you more details. Please read Appendix B carefully.

Pictures Attached below for this.

Your team consists of developers, systems analysts, designers, and testers; a breakdown of skill/expertise required for development is included on page 42 of the requirements document. Ensure to read the Entire SRS document to understand the requirements clearly.

1. Focusing on the core features as specified in the case study, create a summarized Project Plan for the project indicated in the SRS. You should review your Project Plan with all your group members prior to submission.
2. 

Software Requirements Specification for SplitPay Version 1.0 approved ZILDOR, Inc. February 9, 2011 Prepared by: Rick Aasen Leland Cerauskis Ed Carlisle Eric Jeffers Inch Fitchou Nick Carson Travis Green nhunnnn ako atran 10. APPENDIX B PROJECT PROPOSAL Group 1492: Software Application Proposal Working title: Platform: SplitPay Android (2.2+), predominantly Java programming MOTIVATION We are designing an application that facilitates the process of paying off shared expenses. In other words, we want to make it easier to pay for things as a group. This is relevant in many different situations, ranging from every day transactions (friends splitting the cost of dinner), to recurring payments (roommates paying rent), to a more professional setting a team of professionals making business transactions). Depending on the number of people and/or the amount of money involved, these situations can get very complicated. PROBLEM STATEMENT The problems we aim to alleviate with this app include the following: Difficulty of calculating divided costs Unfair or imbalanced payments amongst individuals Lack of accountability for money owed Difficulty remembering payments already made, outstanding debts, etc. The app we design will solve these problems and several more. Consequently, we will include the following functionalities: Automatic calculation of money owed by each member of the group Customizable formula for splitting costs Transaction history (including all payments made & costs incurred by each individual) We will also add the following features, which extend beyond the simple task of dividing costs: Support for multiple transactions which can take place over extended periods of time Automatic notifications, alerting users of outstanding debts and/or other relevant info Transaction synchronization, keeping each group member up to date at all times PayPal integration, allowing for easier transactions Receipt storage, which allows the user(s) to save photos of receipts associated with particular purchases/expenses E-mail and print functions, allowing non-Android users to obtain copies of transactions NOTE: Some of these features are not part of our core design and will only be added if time permits. Software Requirements Specification | OBJECTIVES Beyond Implementing the above features, there are a number of additional objectives we must accomplish as a team. First and foremost, as a group we must familiarize ourselves with the Android platform, as this will lay the groundwork for future development. Additional objectives include the following: Develop a timeline detailing each stage of development Establish well-defined roles for each member of the group Create detailed software specifications Ensure each member is up to speed and completing work on time Form a testing framework to simplify the debugging process Create a fully-functional, bug-free application METHODOLOGY We will be dividing the team into 3-4 subgroups, including some or all of the following: Research/Documentation, Android/Java Implementation, Server/Web, and GUI & Graphics. In addition, we will divide the development process into several discrete stages. The first stage will be dedicated to getting everyone in the group acclimated to the new development platform. We will do this by finding and sharing resources (documentation, sample code, etc.), as well as running through the set-up process for the Android SDK as a group. Before beginning development, we will establish documentation guidelines and testing frameworks in order to enhance maintainability and prevent bugs in the long run. Next, we will work up specifications, establish deadlines, define roles, and allocate tasks to each group member. We plan on dividing up the development process into two central phases, core development and feature development. Core development will involve implementing the essential aspects of our application (calculator, transaction history, auto-sync, etc.), whereas feature development will encompass any additions which extend the app's capabilities (PayPal, advanced GUI, e-mail/print functions, etc.). We will implement these additional features in order of priority (which we will establish before beginning development). HISTORY There are several applications on the market" which are similar to our proposed app (examples include Bills Are In, Share a Bill, Split a Bill, Fair Share, and Xpense Split). A majority of these are web-based applications with little or no mobile functionality. In addition, they all require users to set up an account before they can utilize their services. The remaining apps we found were limited to the ios platform, leaving the Android market open. Furthermore, we plan on adding some features which are not currently available in any of these applications. Google splitpay srs document Q All Images Shopping D Videos E News More Tools About 1,330 results (0.54 seconds) https://www.studocu.com> > Soitware engmeening Software Requirements Specification for SplitPay Version 1.0 The purpose of this Software Requirements Specification (SRS) document is to provide a detailed description or te Tunctions or copiit ay system. People also search for splitpay project plan online payment application srs https://studylib.net> ... > Computer Science : Software Requirements Specification for SplitPay - StudyLib 4533 SPLITPAY Software Requirements Specification 1. INTRODUCTION 1.1 PURPOSE The purpose of this Software Requirements Specification (SRS) document is to ... https://silo. tips > download > zildor-inc-software-d... PDF : Software Design Document ZILDOR, INC. Software Design Document. SplitPay. Rick Aasen. Ed Carlisle software requirement specification (SRS) document is written for a... While the https://www.scribd.com > document 20200923142934s.. : 20200923142934software Requirements Specification Splitpay The purpose of this Software Requirements Specification (SRS) document is to provide a. Software Requirements Specification 7. KEY RESOURCE REQUIREMENTS External Resource Issues/Constraints Major Project Skill/Expertise Activities Required Internal Resource Create a Server application Database systems & servers experience Internet Nick and Eric have general knowledge in this field No physical server; limited number of team members with SQL/PHP experience Internet Sync the Server to the Application Application networking with online servers Nick and Eric have general knowledge in this field Possible compatibility issues Design the Interface Android Developers community; published examples Design & usability Josh has extensive experience; familiarity digital design with Android GUI experience; Rick design has experience with human-computer interaction (HCI) Schedule conflicts; physical constraints of handset screen resolution Design an algorithm Knowledge & experience designing mathematical algorithms All members have taken data structures and algorithms Android Developers community; published examples Potential schedule conflicts Implement an algorithm Familiarity with the Android development environment Potential schedule conflicts All team members have Java programming experience Android Developers community; published examples Android emulators are publicly available for testing Implement the interface Familiarity with Android GUI implementation Potential schedule conflicts All team members have Java programming experience Android Developers community; published examples Android emulators are publicly available for testing SPLITPAY Software Requirements Specification 43 8. OTHER REQUIREMENTS A database for SplitPay calls for a server side implementation that holds information for the users, groups, bills, transactions, as well as all the relationships involved. The database will be using MySQL. The following provides an example of information that may be stored in the database: Users: ID, Name, phone number, email, PayPal username Groups: ID, Name, Members Bills: ID, Name, Owner, Group, Cost, Receipt, Date, Time Transactions: ID, Members Involved, Group, Date, Time, Amount The server will be configured on a Linux platform, and through use of PHP will allow interaction and processing in conjunction with the database. Processes to be done on the server include: pushing/pulling data, updating data, and generating notifications