Project Management

I am choosing the Project Proposal assignment for a system that will provide customer information on an Insurance Protection Program for phones. The stat date will be February 1, 2016 and the completion date will be December 31, 2016.  The project will need 10 team members who have SQL database service experience.  The determined budget will be 2.0 million dollars which I have included $500, 00 thousand for any hidden cost.

. As you move forward with future assignments, all different components of the project are constructed leading to a final compilation, and presentation, of your project.hree to four (3-4) page paper in which you:

  1. Propose a project idea, and explain a selection method for selecting the project (i.e., financial or non-financial method). Provide a rationale for your proposal.
  2. Construct the objectives of the project in terms of a problem which it solves or an opportunity which it capitalizes on.
  3. Create a scope statement (using the template on page 105 of the textbook) for your project. Make sure to include all necessary components of the scope statement.
  4. Format your assignment according to the following formatting requirements:
    1. Typed, double spaced, using Times New Roman font (size 12), with one-inch margins on all sides.
    2. Include a cover page containing the title of the assignment, the student’s name, the professor’s name, the course title, and the date. The cover page is not included in the required page length.

Scope Statement below:

PROJECT OBJECTIVE:  To implement a system that will provide customer information on an insurance Protection Program for devices by 12/31/2016

DELIVERABLES:

  • Project Plan Proposal
  • Analysis each phases to build functionality
  • Design  the Prototype
  • Validation and Contraction  of Prototype
  • Training material and technical requirements
  • UAT of the Business Validation of Packaged Release

MILESTONES

  • Project Plan Proposal  02/1/2016
  • Software Model          04/01/2016
  • System Design (diagrams of sequences, components, DB Model) 06/01/2016
  • System Prototype 08/01/2016
  • Software development  09/01/2016
  • UAT   10/01/2016 – 11/30/2016
  • Launch Planning  11/01/2016
  • Training material  11/01/2016
  • Software Complete  12/01/2016

TECHINAL REQUIREMENTS

  • Product perspective
    • System Interfaces
    • Hardware interfaces
    • Software interfaces
    • Communication Interfaces
    • Memory Constraints
    • Operations
    • Site Adaptation Requirements
  • Specific requirements
    • External interface requirements
    • Functional requirements
    • Performance requirements
    • Design constraints
      • Standards Compliance
    • Logical database requirement
    • Software System attributes
      • Reliability
      • Availability
      • Security
      • Maintainability
      • Portability
    • Other requirements

LIMITS AND EXCLUSIONS

  • The software will meet all requirement for End User Acceptance and meet all requirement for Data Security
  • Training will be Train the Trainer
  • Updates will be done nightly between 12AM and 6AM
  • Upgrades will be scheduled

CUSTOMER REVIEW

Business Owners, Business Subject Matter Expert, End User