You have been made a project manager in charge of 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
• A software requirement specification (SRS) document
• A cost estimate and service level agreement for the system.

The software requirements specification (SRS) document is posted on BB. Please note: The requirements specification document (which includes some user interfaces) has been picked up from the web and it's used as a reference only for this exercise; it has been created by another organization).

SRS: Software Requirements Specification for SplitPay Version 1.0 approved ZILDOR, Inc. February 9, 2011

Prepared by:	Rick Aasen	Ed Carlisle
Nick Carson
Leland Cerauskis	Eric Jeffers	Travis Green
Blake Matson	Josh Ritchey	Phuong Vo

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.

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.

Create a formal Project Initiation Document (PID) for the Case Study in the SRS with your team members. You should review your PID with all your group members prior to submission, else your grade may not be as you expect. Safe Assign is active and students should be aware of school academic integrity rules.

Your PID must include, but not limited to the following:

Component	Value	Note
Cover letter		Proper English and format, formal
Cover page		Complete, creative
Executive Summary		Captures project essence, brief, English
Introduction		Introduces stakeholders and the project, requirements
Business Description		Mission, Goals, Problem Statement
Stakeholder Analysis		Registry, Influence/Power, who are the stakeholders
Methodology		Your chosen methodology in carrying out this project and why
SWOT		Strength, Weakness, Opportunities, Threats
System Request		User, functional, and non-functional requirements
Feasibility		Full feasibility analysis of the project
Summary		Next steps?