See the word doc section 5.0 ad 6.0 that's all I need. Team data file has the information of roles
SOFTWARE PROJECT MANAGEMENT PLAN (SPMP)
1.0 Introduction
Chocoholics Anonymous (ChocAn) is an organization dedicated to helping
people addicted to chocolate in all its glorious forms. Members of ChocAn
pay a monthly through a third party known as Acme.For their membership,
members get to enjoy unlimited consultations and treatment with healthcare
professionals. Once a week, a record consisting of electronic funds (EFT) data
is sent to banking computers which ensure that each provider’s bank is credited
with the appropriate amount for the effort.Code Linguistics has been awarded the
contact to write only the ChocAn data processing software.
1.1Problem statement
Our goal is to design a system that can handle all the necessary information coming in and going out of ChocAos data center efficiently.With the amount of data being transferred; privacy will be a huge priority. The database will contain sensitive information such: medical records, payment information, members and providers credentials, etc. The system will need to keep an up-to-date list of members and providers. This will minimize the amount of data that needs to be saved and the problems that come with handling it. In the description of the project, the team noticed a few places where human error could occur easily. The system will minimize this by the integrations of drop-down boxes, search bars and automatic information matching.Once information is entered by either a member or a provider; the system will provide a functionality that will allow the user to double verify and confirm their inputs.
1.2 Project scope
1.2.1 Inclusions
A description of the software is presented. Major inputs, processing functionality and outputs are described without regard to implementation detail.
Every member has a plastic card embossed with the member’s name and a nine-digit member number. A magnetic strip incorporated into the card encloses all their information. The providers are given a specially designed ChocAn computer terminal. They are allowed access to their terminal by entering their provider number. Members’ and providers’ data will be stored in the ChocAn Data Center, where they will be updated daily by the operators. Suspended or retired members will be automatically deleted from the active member/provider list on a daily basis. At the beginning of a session, the members give their card to the provider who uses the terminal to validate their membership. The provider will no longer be required to enter information after the member has been validated.The system will automate the rest of the entries.Service sessions for each provider will be in a drop down brown box tailored to their position.The system will will populate all the information on the screen to give the users an opportunity to verify their inputs before saving the information to the system. Whenever data is received from a user; double verification will be required by the system. Weekly, the members and providers will receive a report if the system recorded that they had sessions(s). If the member sees an unknown session on their report, they can either submit a notice through the website or call ChocAn. All activities/transactions will be recorded by the system.Since the system will handling a large amount of sensitive information, the database should be secure. Members and providers credit card/payment or any other personal identification information will be encrypted.Only necessary personnel of ChocAn will be given access to these data.
1.2.2 Exclusions
List any exclusions from the project
Communication software
Designing the ChocAn provider’s terminal
Software needed by the Acme Accounting Services
Implementation of the EFT component
1.3 Major software functions
A functional decomposition of the software (for use during estimation and scheduling) is developed here. May be outline/bullet points or decomposition diagram format.
Encrypted personal information
List of active active members and providers
Automation tools ( drop-down boxes, search bar, automatic information matching )
Double verification
Recording activities and transactions
Automated weekly reports
1.4 Performance/Behavior constraints
Any special requirements for performance or behavior are noted here. Non-functional constraints such as on-line response time or batch window timeframe to complete processing.
Not sure what to write here
1.5 Management and technical constraints
1.5.1 Management constraints
Any special constraints that affect the manner in which the project will be conducted (e.g., limited resources or 'drop dead' delivery date) are noted here.
1.5.2 Technical constraints
Any special constraints that affect the technical approach to development are noted here.
2.0 Project Estimates
This section provides cost, effort and time estimates for the projects
2.1 Historical data used for estimates
Describes the historical data that is relevant to the estimates presented. This is, what historical work can be used as the basis for your estimations (e.g. prior classwork projects, work projects)
2.2 Initial Estimate
Based solely on 1.0 and 2.1 details provide.
2.2.1 SPMP Completion Estimate
Estimated effort in hours to complete SPMP
2.2.2 Overall project estimate
2.2.2.1 Line-of Code Estimate
What is the estimated lines of code to complete project
2.2.2.2 Function Estimate
What is the count of the funtionality listed in 1.3
2.2.2.3 Tasks Estimate
What are high level tasks to complete (this is not a project plan) but tasks to think about for this estimate
2.2.2.4 Total overall project time estimate in hours of effort
Team consensus on overall effort based on estimated values in 2.2.2.1 – 2.2.2.3 plus 2.2.1 and project management effort
2.3 Estimation techniques applied and results
A description of each estimation technique and the resultant estimates are presented here. DO NOT COMPLETE THIS SECTION UNTIL REMAINDER OF SPMP IS COMPLETED AND REVIEWED!
2.3.1 Estimation technique 1 – lines of code
Tables or equations associated with lines of code estimation technique m are presented. Re-estimate lines of code based on completed SPMP.
2.3.2 Estimate for technique 1 – lines of code
Estimate in hours generated for lines of code technique.
2.3.3 Estimation technique 2 – function points
Re-estimate functionality and apply function point counting technique based on completed SPMP.
2.3.4 Estimation technique 3 – process/task
Tables or equations associated with lines of code estimation technique m are presented. Re-estimate effort based on actual tasks defined in completed SPMP.
2.3.5 Estimate for technique 3 – process/task
Estimate in hours generated for process/task technique.
2.4 Reconciled Estimate
The final cost, effort, time (duration) estimate for the project (at this point in time) is presented here. Explain your rationale for these numbers compared to the three techniques above.
2.5 Project Resources
People, hardware, software, tools, and other resources required to build the software are noted here.
3.0 Risk Management
This section discusses project risks and the approach to managing them.
3.1 Project Risk Table
Each project risk is described. Name of risk, probability, impact, mitigation and contingency plan
3.2 Overview of Risk Mitigation, Monitoring, Management
How will Risk Mitigation, Monitoring and Management be handled. Communication plan, when to apply the mitigation strategy, etc.
4.0 Project Schedule
This section presents an overview of project tasks and the output of a project scheduling tool.
4.1 Project task set
The process model, framework activities and task set that have been selected for the project are presented in this section.
4.2 Task network
Project tasks and their dependencies are noted in this diagrammatic form.
4.3 Timeline chart
A project timeline chart is presented. This may include a time line for the entire project or for each staff member.
5.0 Staff Organization
The manner in which staff are organized and the mechanisms for reporting are noted.
5.1 Team structure
The team structure for the project is identified. Roles are defined.
5.2 Management reporting and communication
Mechanisms for progress reporting and inter/intra team communication are identified.
6.0 Tracking and Control Mechanisms
Techniques to be used for project tracking and control are identified.
6.1 Quality assurance and control
An overview of SQA activities is provided. This is an outline at this point and will be used to create a detailed plan later in the project.
6.2 Change management and control
An overview of SCM activities is provided on how changes will be handled – communication of a change, how decision made of approval, defer or reject change request.
6.3 Tools
What tools will be used to control access and versioning of artifacts.
7.0 Appendix
Supplementary information is provided here.
