Spmp updated checked 29

Saint Columban College

COLLEGE OF COMPUTER STUDIES

Software Project Management Plan

for

SCC Newscast System

Mach5

Almonte, Jelly Mae P.

Baltazar, Jessaneth B.

Ching Carl Angelo L.

Ihara Jr, Noel B.

Salazar, Ragde Ama T.

Signature

The following signature indicates approval of the enclosed Software Project Management Plan Document.

Noel B. Ihara Project manager

Jelly Mae. P. Almonte Carl Angelo L. Ching System Analyst Programmer

Ragde Ama T. Salazar Jessaneth B. Baltazar Quality Assurance Documenter

Mr. Neil Owen B. Jandugan Adviser/Editor

Submitted and accepted by:

Mr. Philipcris C. Encarnacion , MCS CCS Dean

Change HistoryTable 1

Revisions Date Reason For Changes Person who

suggested the

changes

Group Name June 16, 2014 Team Celeron change its name to

Mach5 because the meaning of

Celeron itself does not suit the group’s

characteristics.

Jessaneth B. Baltazar

(Documenter)

Title Name September 8,2014 The title of the study was changed

from E-Bulletin to SCC Newscast

System to make it more suitable with

the proposed system.

Ragde Ama T. Salazar

(QA Tester)

List of tables October 24, 2014 The numbering of the tables was

changed and was properly ordered.

Mrs. Janus A. Naparan

(Client)

Purpose, scope

and objectives

October 24, 2014 The sentence construction of the

purpose, scope and objectives was

improved.


(Client)

Schedule and

budget summary

October 24, 2014 The exact breakdown of the schedule

and budget summary were specified.


(Client)

Evolution of plan October 24, 2014 The evolution of plan was changed

and a Gantt chart was presented.


(Client)

Definitions October 24, 2014 The definitions was changed and

stated in complete sentence.


External

interface

October 24, 2014 The external interface was improved

and was changed into a diagram.

Mr. Neil Owen B.

Jandugan

(Adviser)

Internal structure October 24, 2014 The group changed the internal

structure to correct what is wrong on

the diagram.

Mr. Syril Glenn Flores

(Panel)

External October 24, 2014 The group changed the external Mr. Syril Glenn Flores

structure structure to correct what is wrong on

the diagram.

(Panel)

Budget Control

plan

October 24, 2014 The budget control plan was revised

into a paragraph form.

Mr. Francis Rebo

Alegre

(Panel)

Preface

The purpose of this document is to specify the project plan to develop the SCC Newscast system. This document

outlines a brief plan about how the project will be shape. It also includes the milestones and deliverables. The

Software Project Management Plan (SPMP) document will serve as a guide for the student, developing the

product as part of the project. Updates of this document will serve to record the progress of the project.

Table of ContentsSignature....................................................................................................................................................................................2Change History..........................................................................................................................................................................3Preface........................................................................................................................................................................................5Table of Contents.......................................................................................................................................................................6List of Figures............................................................................................................................................................................8List of Tables..............................................................................................................................................................................91. Overview...............................................................................................................................................................................10

1.1. Project Summary............................................................................................................................................................................ 101.1.1. Purpose, scope and objectives...............................................................................................................................................101.1.2. Assumptions And Constraints...............................................................................................................................................101.1.3. Project deliverables...............................................................................................................................................................111.1.4. Schedule and Budget Summary.............................................................................................................................................11

1.2. Evolution of plan............................................................................................................................................................................ 122. References............................................................................................................................................................................193. Definitions ...........................................................................................................................................................................204. Project organization............................................................................................................................................................25

4.1. External interface ..........................................................................................................................................................................254.2. Internal Structure ...........................................................................................................................................................................254.3. Roles and Responsibilities..............................................................................................................................................................26

5. Managerial process plans...................................................................................................................................................275.1. Start-Up Plan ................................................................................................................................................................................27

5.1.1. Estimation plan ....................................................................................................................................................................275.1.2. Staffing plan .........................................................................................................................................................................275.1.3. Resource acquisition plan ....................................................................................................................................................275.1.4. Project staff training plan ....................................................................................................................................................27

5.2. Work Plan ...................................................................................................................................................................................... 285.2.1. Work Activities......................................................................................................................................................................285.2.2. Schedule Allocation...............................................................................................................................................................285.2.3. Resource Allocation..............................................................................................................................................................285.2.4. Budget allocation..................................................................................................................................................................29

5.3. Control Plan ................................................................................................................................................................................... 291.3.1.Requirements Control Plan ...................................................................................................................................................291.3.2.Schedule Control Plan ..........................................................................................................................................................291.3.3.Budget control plan................................................................................................................................................................301.3.4.Quality control plan...............................................................................................................................................................301.3.5.Reporting plan ......................................................................................................................................................................301.3.6.Metrics collection plan ..........................................................................................................................................................301.3.7.Risk management plan...........................................................................................................................................................305.3.8 Project closeout plan..............................................................................................................................................................31

6. Technical process plans ....................................................................................................................................................326.1. Process Model................................................................................................................................................................................326.2. Methods, tools, and techniques.......................................................................................................................................................326.3. Infrastructure Plan..........................................................................................................................................................................326.3. Product Acceptance Plan................................................................................................................................................................32

7. Supporting process plans ...................................................................................................................................................337.1. Configuration management plan ....................................................................................................................................................337.2. Verification and validation plan .....................................................................................................................................................337.3. Documentation plan .......................................................................................................................................................................337.4. Quality assurance plan ...................................................................................................................................................................337.5. Reviews and audits.........................................................................................................................................................................338.0 Additional Plans.............................................................................................................................................................................. 33

9. Plan Annexes.......................................................................................................................................................................3410. Index..................................................................................................................................................................................35

Software Project Management Plan SCC Newscast System

Document Version: 3.0Published Date: 27 October 2014

Page 7 of 35



List of Figures

Figure 1: Evolution of Plan…………………………………………………………………..............................12-17Figure 2: External Interface……….…………………………………………………………………………….…….24Figure 3: Internal Interface ………………………………………………………………………..………………….24

Page 8 of 35



List of TablesTable 1: Change History…………………………………………………………………………………….……..3-4Table 2: Schedule and Budget Summary………………………………………………………...……….……...11Table 3: Definitions………………………….………………………………………………………………...…19-23Table 4: Roles and Responsibilities……...………………………………….………………………………….…26Table 5: Work activities……………………………………………………………………………………….…….28Table 6: Budget Allocation…..……………………………………………………………………………..……….29

Page 9 of 35



1. Overview

1.1. Project Summary

1.1.1. Purpose, scope and objectives

The scope of this project includes assumptions on where the project is based; and constraints of the project such as schedule, budget and resources, software to be released, and product interfaces.

Project deliverables also include the list of task that will be delivered to the clients, delivery dates and qualities required to satisfy the terms of the project agreement.

Schedule and budget summary provides a summary of the schedule and budget for the software project. The level of detail should be restricted to an itemization of the major work activities and supporting processes.

Project organization that will identify interfaces to organizational entities external to the project and internal and defines the roles and responsibilities for the project.

The purpose of this document is to highlight the managerial plan for the SCC Newscast system with a goal of improving the user’s productivity by automating his/her work.

The objective is to enhance the user’s productivity by scheduling the tasks needed to be done in a specific duration. The task assignment is given respectively and should be followed according to the work plan.

1.1.2. Assumptions And Constraints

The prototyping and documentation of the project shall be finished on October 4, 2014, at the end of the first semester, S.Y. 2014-2015, of Capstone 1 Project course. All codes shall be written in C# language. The system shall be standalone application in PC environment on MS Windows XP, Windows 7. The system is easy to install.When the team develops the system, the group will need a budget in supplying the requirements needed to establish the system.

The project has the following constraints:

• TIME- The duration for the project design is one school year.- By the end of the 2nd semester, the software product is installed at the Information Office. The set-up of the computers and other hardware, and the orientation for the users may take several hours.

Page 10 of 35



• STAFFThe Information personnel will be required for the consultation for the system design and process of the system. The Information Office personnel can also consult the team/developers, when necessary.

1.1.3. Project deliverables

This project deliverables listed below should be provided before the completion of the system. Documents are used to be presented to the client. It represents the internal system such as the capabilities, scope and limitations, and etc. It will also present the Approval sheets, Software Requirement Specifications (SRS), Software Project Management Plan (SPMP), Software Design Description (SDD) and Software Testing Design (STD).

Project Deliverables:

-Documents

-Project Proposal

-Use Case

-SRS

-SPMP

-SDD

-STD

-The SCC Newscast System

1.1.4. Schedule and Budget Summary

Table 2

Month Expenses

June

Record Book ₱ 35.00

Clear Book ₱ 45.00

Transportation ₱ 100.00

July Printing expenses for SRS Document ₱ 100.00

August Transportation ₱ 200.00

Others ₱ 100.00

September Transportation ₱ 200.00

Page 11 of 35

DSA OFFICE, 10/27/14

Spell out then enclose abbrev. in parenthesis



October Printing expenses for SRS Document ₱ 90.00

Printing expenses for SPMP Document ₱ 204.00

Printing expenses for SDD Document ₱ 156.00

Electricity ₱ 500.00

Others ₱ 310.00

TOTAL ₱ 2,040.00

1.2. Evolution of plan

Figure 1

Page 12 of 35



Page 13 of 35


Make this clearer and label this figure.



Page 14 of 35



Page 15 of 35



Page 16 of 35



Page 17 of 35



Page 18 of 35



2. References

IEEE Std 1058-1998 IEEE standard for software project management plans.

Page 19 of 35



3. Definitions Table 3

Term Definition

Acquirer

The individual or organization that specifies requirements for and accepts delivery of a new or modified software product and its documentation.

Additional PlanContains additional plans required to satisfy product requirements and contractual terms.

BaselineA work product that has been formally reviewed and accepted by the involved parties. A baseline should be changed only through formal configuration management procedures.

Budget AllocationProvides a detailed breakdown of necessary resource budgets for each of the major work activities in the work breakdown structure.

Budget Control Plan

Specifies the control mechanisms to be used to measure the cost of work completed, compare planned cost to budgeted cost, and implement corrective action when actual cost does not conform to budgeted cost.

Configuration Management Plan

Contains the configuration management plan for the software project, to include the methods that will be used to provide configuration identification, control, status accounting, evaluation, and release management.

Control Plan

Specifies the metrics, reporting mechanisms, and control procedures necessary to measure, report, and control the product requirements, the project schedule, budget, and resources, and the quality of work processes and work products.

Database It is where the collections of all the information being stored.

Documentation PlanContains the documentation plan for the software project, to include plans for generating non-deliverable and deliverable work products.

Estimation PlanSpecifies the cost and schedule for conducting the project as well as methods, tools, and techniques used to estimate project cost, schedule, resource requirements, and associated confidence levels.

External InterfaceDescribes the organizational boundaries between the project and external entities.

IEEE The Institute of Electrical and Electronics Engineers (IEEE) is a membership organization that includes engineers, scientists and

Page 20 of 35


State all definitions in sentences



students in electronics and allied fields.

Infrastructure Plan

Specifies the plan for establishing and maintaining the development environment (hardware, operating system, network, and software), and the policies, procedures, standards, and facilities required to conduct the software project.

Internal StructureDescribes the internal structure of the project organization to include the interfaces among the units of the software development team.

Methods, tools, and techniques

Specifies the development methodologies, programming languages and other notations, and the tools and techniques to be used to specify, design, build, test, integrate, document, deliver, modify and maintain the project deliverable and nondeliverable work products. In addition, the technical standards, policies, and procedures governing development and/or modification of the work products shall be specified.

Metrics Collection PlanSpecifies the methods, tools, and techniques to be used in collecting and retaining project metrics.

MilestoneMilestone is an event that receives special attention. It is often put at the end of a stage to mark the completion of a work package or phase.

Problem Resolution PlanSpecifies the resources, methods, tools, techniques, and procedures to be used in reporting, analyzing, prioritizing, and processing software problem reports generated during the project.

Process Improvement PlanIncludes plans for periodically assessing the project, determining areas for improvement, and implementing improvement plans.

Process Model

Defines the relationships among major project work activities and supporting processes by specifying the flow of information and work products among activities and functions, the timing of work products to be generated, reviews to be conducted, major milestones to be achieved, baselines to be established, project deliverables to be completed, and required approvals that span the duration of the project.

Product Acceptance PlanSpecifies the plan for acquirer acceptance of the deliverable work products generated by the software project.

Project AgreementA document or set of documents baseline by the acquirer and the supplier that specifies the conditions under which the project will be conducted.

Page 21 of 35



Project Closeout Plan

Contains the plans necessary to ensure orderly closeout of the software project. Items in the closeout plan should include a staff reassignment plan, a plan for archiving project materials, a plan for post- mortem debriefings of project personnel, and preparation of a final report to include lessons learned and analysis of project objectives achieved.

Project deliverable A work product to be delivered to the acquirer

Project Staff Training PlanSpecifies the training needed to ensure that necessary skill levels in sufficient numbers are available to successfully conduct the software project.

Quality Assurance Plan

Provides the plans for assuring that the software project fulfills its commitments to the software process and the software product as specified in the requirements specification, the SPMP, supporting plans, and any standards, procedures, or guidelines to which the process or the product must adhere.

Quality Control PlanSpecifies the mechanisms to be used to measure and control the quality of the work processes and the resulting work products.

Reporting Plan

Specifies the reporting mechanisms, report formats, and information flows to be used in communicating the status of requirements, schedule, budget, quality, and other desired or required status metrics within the project and to entities external to the project.

Requirements Control PlanSpecifies the control mechanisms for measuring, reporting, and controlling changes to the product requirements

Resource Acquisition PlanSpecifies the plan for acquiring the resources in addition to personnel needed to successfully complete the project.

Resource AllocationProvides a detailed itemization of the resources allocated to each major work activity in the project work breakdown structure.

Reviews and AuditsSpecifies the schedule, resources, and methods and procedures to be used in conducting project reviews and audits.

Risk Management PlanSpecifies the risk management plan for identifying, analyzing, and prioritizing project risk factors.

Schedule AllocationProvides scheduling relationships among work activities in a manner that depicts the time-sequencing constraints and illustrates opportunities for concurrent work activities.

Page 22 of 35



Schedule Control Plan

Specifies the control mechanisms to be used to measure the progress of work completed at the major and minor project milestones, to compare actual progress to planned progress, and to implement corrective action when actual progress does not conform to planned progress.

SPMP Software Project Management Plan is the art and science of planning and leading software projects. It is a sub-discipline of project management in which software projects are planned, implemented, monitored and controlled.

Staffing PlanSpecifies the number of staff required by skill level, the project phases in which the numbers of personnel and types of skills are needed, and the duration of need.

Start-up PlanSpecifies the estimation plan, staffing plan, resource acquisition plan, and training plan.

Subcontractor Management Plan

Contains plans for selecting and managing any subcontractors that may contribute work products to the software project.

SupplierAn organization that develops some or all of the project deliverables for an acquirer.

Supporting Process PlanContains plans for the supporting processes that span the duration of the software project.

Technical Process Plan

Specifies the development process model, the technical methods, tools, and techniques to be used to develop the various work products; plans for establishing and maintaining the project infrastructure; and the product acceptance plan.

User A person who uses or interacts with the said system.

Verification and Validation PlanContains the verification and validation plan for the software project to include scope, tools, techniques, and responsibilities for the verification and validation work activities.

Work ActivitiesSpecifies the various work activities to be performed in the software project.

Work ActivityA collection of work tasks spanning a fixed duration within the schedule of a software project.

Work PackageA specification of the work that must be accomplished to complete a work task.

Work Plan

Specifies the work activities, schedule, resources, and budget details for the software project.

Page 23 of 35



Work ProductAny tangible item produced during the process of developing or modifying software.

Work Task The smallest unit of work subject to management accountability.

Page 24 of 35



4. Project organization

4.1. External interface

Figure 2

Ihara as a project manager meets with the client weekly to discuss possible revisions and modification.

4.2. Internal Structure

Figure 3

All the work on this project will be performed by Ihara, Baltazar, Salazar, Almonte and Ching. Ihara as a project manager meets with the team weekly to discuss possible changes and modification.

Page 25 of 35


Include adviser, label of the diagram and to be included in the list of figures. Insert description of the relationship of each component in the diagram.


Include explanation of the relationship between the client and project manager.


Change and then label it as figure ___ to be included in the list of figures.


Include explanation of the relationship between the client and project manager.



4.3. Roles and Responsibilities

Table 4

ROLE RESPONSIBILITIESProject Manager He/She:

1.Plans, organizes, coordinates, control the activities of the group2. Has the overall responsibilities for the success of the project. 3. Leads the team in producing, assessing, updating, and reporting

on the plan.4. Review of testing results and defects to determine/assess impact

to overall project plan and implementation schedule.5. Review and Approval of the testing strategy, approach, and

plans.Programmer He/She:

1. Assist with design, analysis, maintenance, documentation, and testing of software.

2.Code, debug, test, and document routine application programs3. Design new systems or enhancements to existing systems.

4. Verify that system meets performance criteria.5. Advise or train users regarding the technical aspects and use of

standard software packages.6. Design/modify, code, debug, test, and document moderately

complex application systems.Quality Assurance He/She:

1. Responsible for management of all Quality Assurance functions include planning, strategy, testing execution and tools.

System Analyst He/She:1. Collect information to analyze and evaluate existing or proposed

systems.2. Prepare detailed flow charts and diagrams outlining systems

capabilities and processes.3. Select among authorized procedures and seek assistance when

guidelines are inadequate, significant deviations are proposed, or when unanticipated problems arise.

4. Write and maintain system documentation.Documenter He/She:

1. The documenters kept detailed meeting minutes.2. Make sure the documents are complete.

Page 26 of 35



5. Managerial process plans

5.1. Start-Up Plan

5.1.1. Estimation plan

As previously stated, the total development time is estimated to be one school year, one school year is divided into two semesters.

Each semester will cover part of the Gantt chart that was created at the beginning of the project through Microsoft Excel. Gantt chart excel-based will be used to produce and to track a schedule that includes milestones for the project.

At the beginning of each work phase, The Mach5 team will have to check the Gantt chart to define the tasks and schedules. The Mach5 team will assess its status once a week and update and distribute the schedule accordingly. Every topic listed in Gantt chart will be reviewed by using formal review methods.

5.1.2. Staffing plan

In the first semester, the managerial committee which include Noel Ihara Jr. as the Project Manager, Jessaneth Baltazar the Documenter and Jelly Mae Almonte the System Analyst will be the head in assigning and documenting with the help of the Programmer Carl Ching and Quality Assurance Ragde Ama Salazar. For the second semester the Project Manager, Programmer and Quality Assurance will be the head in finalizing the system with the assistance of Documenter and System Analyst.

5.1.3. Resource acquisition plan

All necessary hardware, software case tools for the project are already available. The system will be installed on a computer unit, one in the Information Office as a server and one in each department namely, the College of Business Education, College of Computer Studies and College of Teachers Education Arts and Sciences as a client which is ready to use.

5.1.4. Project staff training plan

No additional staff training is needed for this project.

Page 27 of 35



5.2. Work Plan

5.2.1. Work Activities

Table 5

Week 1 SRS Chapter 1 Introduction and Chapter 2 Overall Description documentation.Week 2 SRS Chapter 3 Specification requirementsWeek 3 SPMP Chapter 1 Overview, Chapter 2 References, Chapter 3 Definition, Chapter 4 Project

OrganizationWeek 4 SPMP Chapter 5 Managerial Process Plans and Finalizing SRS and SPMP.Week 5 SPMP Chapter 6 Technical Process Plans and Supporting Process Plans.Week 6 SDD Chapter 1 Introduction and Chapter 2 References.Week 7 SDD Chapter 3 Decomposition Description and Chapter 4 Dependency Description.Week 8 SDD Chapter 5 Interface Description.Week 9 SDD Chapter 6 Detailed Design.Week 10 SDD Chapter 7 Appendices and Chapter 8 Index.

5.2.2. Schedule Allocation

The project duration is constrained to one semester (prelim, midterm, semi-finals, and finals), with final deliverables due in the mid of October 2014. We will control our schedule with main artifacts.

5.2.3. Resource Allocation

The whole team member will work separately on their assigned task. The Project manager Noel Ihara will acquire the role of monitoring the daily progress of the members, oversee implementation and the Quality assurance Ragde Ama Salazar is responsible for overall quality, and interact with the client. Team members will meet at the end of each day and discuss problems and progress. Formal meeting with the client will be held at the end of each week to report progress and determine if any changes needed to be made. The Project manager will ensure that schedule and budget requirements are met. The Project manager will be also responsible for the risk management.

Minimizing faults and maximizing user-friendliness will be the project manager’s top priorities. The documenter Jessaneth Baltazar has the overall responsibility for all documentation and has to ensure that it is up to date.

Page 28 of 35



5.2.4. Budget allocation

Table 6

Budget Allocation Cost

Printing Expenses for SRS, SPMP, SDD Documents

₱ 550.00

Transportation ₱ 500.00

Electricity ₱ 500.00

Record Book ₱ 35.00

Clear Book ₱ 45.00

Others ₱ 410.00

TOTAL ₱ 2, 040.00

5.3. Control Plan

Any major changes that affect the budget of the project have to be approved by the project manager and documented by the documenter. No outside quality assurance personnel are involved. The benefits of having someone other than the individual who carried out the development do the testing will be accomplished by each person testing another person’s work products.

The project manager will be responsible for ensuring that the project is completed on time and within the estimated budget. This will be accomplished through daily meetings with the team members. At each meeting, the documenter and the system analyst will present the day’s progress and problems. The project manager will determine whether they are progressing as expected and whether they are following the specificationdocument and the project management plan. Any major problems faced by the team members will immediately be reported to the project manager.

1.3.1. Requirements Control Plan

Requirement will be managed in use case description of SRS as requirements are changed. More detailed Requirement Management Plan Ver. 1.1

1.3.2. Schedule Control Plan

Page 29 of 35


Insert number and label



Our team’s planning manager will maintain the schedule in a project document. The planning manager will be responsible for gathering the individual tasks for each team member and supervise us to ensure the development of our system’s documentation and the like. If schedule is not on track, our team will follow a schedule control meeting.

1.3.3. Budget control plan

The budget is handled through funding and is limited in which it has to be consume properly. It will be handled personally by one of the team members and every fund will be recorded at the Microsoft excel document to ensure its exact amount funded. Any expenses will be consulted to every member.

1.3.4. Quality control plan

The quality manager will generate a separate Quality Control Plan document. From this document, checklists and other evaluation measures will be determined necessary or otherwise.

Weekly meetings and reviews at the end of each phase will be the main mechanisms that our team will use to control the quality of the work process and the resulting work.

In addition, our adviser will monitor quality control throughout the project by the mentoring. Each member is encouraged to consult our mentor who will meet with the team on a regular class schedule (Mondays and Thursdays of the month) to review individual and group progress and to address any managerial or technical issues or questions. The mentor is encouraged to review the team’s work products and to ask questions to determine the health and progress of the project.

1.3.5. Reporting plan

General ReportingThe team will use a set of applications and methods available from the template given to us by our mentor to communicate to the client, mentors, and advisors to the status of requirements, schedules, quality, and other desired or required status metrics for the team project.

Internal ReportingTeam members will submit individual document to the planning manager every Monday and Thursday as regards to their assigned tasks. The planning manager will consolidate all files and present it to the mentor for checking and approval. Additionally, the team is required to see and consult the mentor to discuss the project’s current progress, unresolved issues, and need for assistance.

1.3.6. Metrics collection plan

Each team member will submit individual progress and every Monday and Thursday, each member will report productivity on the tasks assigned, tasks done or not done, problems, hours planned, actual hours, and future plans ate every week status meeting. The planner manager will consolidate the data and will analyze the efforts spent per programmer every week.

1.3.7. Risk management plan

The risk factors and the tracking mechanisms are as follows. There is no existing product with which the new prod

Page 30 of 35



uct can be compared. Accordingly, it will not be possible to run the product in parallel with an existing one. Therefore, the product should be subjected to extensive testing. The client is assumed to be inexperienced with computers. Therefore, special attention should be paid to the analysis workflow and communication with the client. The

product has to be made as user‐friendly as possible. Because of the ever‐present possibility of a major design fau

lt, extensive testing will be performed during the design workflow. Also, each of the team members will initially test his or her own code and then test the code of another member. The QA will be responsible for integration testing and in charge of product testing. The information must meet the specified storage requirements and response time.This should not be a major problem because of the small size of the product, but it will be monitored by Noel Ihara throughout development.

There is a slim chance of hardware failure, in which case another machine will be leased. If there is a fault in the compiler, it will be replaced

5.3.8 Project closeout plan

Not Applicable here.

Page 31 of 35



6. Technical process plans

6.1. Process Model

The Unified Process will be used. (Show the process diagram)

6.2. Methods, tools, and techniques

The workflows will be performed in accordance with the Unified Process. The product will be implemented in C#.

6.3. Infrastructure Plan

The product will be developed using Visual Studio running under windows 8.1 on a Laptop.

6.3. Product Acceptance Plan

Acceptance of the product by our client will be achieved by following the steps of the Unified Process.

Page 32 of 35



7. Supporting process plans

7.1. Configuration management plan

The server workstation and the client workstation must be connected to a local area network and a unique IP address to prevent further error such as IP conflict. The server workstation must also set the output screens or the LCD TV connected into an extended display with the corresponding resolution of 1366x768 landscape as a screen orientation.

7.2. Verification and validation plan

Verification and validation plan is procedures that are used together for checking that a product, service, or system meets requirements and specifications and that it fulfills its intended purpose.

7.3. Documentation plan

Documentation is distributed manually inside a folder which contains detailed paper documentations.

7.4. Quality assurance plan

The quality assurance performs a benchmark when the system is finished to define glitches of the system and the accuracy of each function. Formulate a possible situation that makes the system down and planning a solution to each glitches and bugs.

7.5. Reviews and audits

The SPMP specifies the plan, schedule and methods will be used in conducting product reviews and audits. So far, the only products that Mach5 has created are documents and the methods for their review. It is expected that in the future the details about the review and audits will be maintained within the Mach5 plan.

8.0 Additional Plans

Additional components:

Security:

A username and a password will be needed to use the product to maximize the security purposes.

Training:

Training will be performed with regards to the software functions and the steps on how to use the system function efficiently by Carl at time of delivery. Because the product is straight forward to use, 1 day should be sufficient for training. Carl will answer questions at no cost for the first year of use.

Page 33 of 35



9. Plan AnnexesPlan Annexes is part of the system or an addition to a main structure or it can be an attachment to current plans and used as append or attach especially to a larger or more significant thing.

Page 34 of 35



10. Index

Constraints 8, 9, 14Control plan 14, 15, 22Dissemination 8, 9Documentation 13, 16, 18, 19, 21, 22, 25Documentation Plan 16, 25Product 9, 13, 14, 15, 16, 21, 22, 23, 24, 25Project 8, 9, 12, 13, 14, 15, 16, 17, 18, 20, 21, 22, 23Project deliverables 8, 9, 13, 15Purpose 8, 25,Reporting plan 15, 23Risk management 15, 21, 23Table of contents 5Workflow 21, 23, 24

Page 35 of 35

Technology

Spmp updated checked 29