Saint Columban College: Pagadian City

SAINT COLUMBAN COLLEGE
Pagadian City
COLLEGE OF COMPUTER STUDIES
Software Project Management Plan

for
Real-time Labor Cost with Online Accessibility
via Mobile App
IT Group 1
“Software Mojo”
Dela Victoria, Francis Ian

Mansing, Nerricar
Villanueva, Shiela May
May 2021
Software Project Management Plan Document Version: 4.0
Real-time Labor Cost with Online Accessibility via Mobile App Published Date: May 25, 2021
Signature
The following signatures indicate approval of the enclosed Software Requirements Specification.
Villanueva, Shiela May S.

Project Manager
Dela Victoria, Francis Ian Mansing, Nerricar

Programmer/ System Analyst Documenter
Francis Rebo P. Alegre, MIT

Adviser
Presented to and approved by the Panel Members:
Syril Glein T. Flores, MCS

Chairman
Mark Lester Catungal,MIT Danah Arnejo

Panel Client
Submitted to and accepted by:
Philipcris C. Encarnacion, MCS

Dean-College of Computer Studies
Saint Columban College
Pagadian City
Page of
Change History
Table 1. Change History
Date Reason for Changes Person who suggested Document

the changes Version
11/17/2020 Change and Edit the Adviser Version 1.0
whole document
11/28/2020 Revise Work Breakdown Adviser Version 2.0
Structure
12/14/2020 Arrange and Correct Adviser Version 2.0
Grammar on Whole
Document
4/22/2021 Estimate and Calculate Programmer Version 3.0
Budget Summary
4/22/2021 Revise Work Breakdown Adviser Version 3.0
Structure
4/22/2021 Project Organization Adviser Version 3.0
Update Structure Diagram
Preface
Software Project Management Plan (SPMP) specifies the schedule of performing all the
Page of
tasks involved in the entire duration of the capstone project as planned by the group, which
will then be monitor to finish all the works. All of the specified tasks will be performed
concerning the Group capstone project that is the development for Shake and Slurp, the
client.
To comply with all the requirements of the project, the group will refer to what has been
planned in terms of the work plan, budget summary, and the role that each member of the
team plays. A Gantt chart and a logbook guide the team where tasks to be documented.
Since the new normal implemented and because of the strict policy by the time of updating
the revised documents, the update will be sent, comply and report through online platform.
Together with the documents and the System.
Table of Contents
SIGNATURE.................................................................................................................................2
CHANGE HISTORY......................................................................................................................3
Page of
PREFACE.....................................................................................................................................4
TABLE OF CONTENTS................................................................................................................5
LIST OF FIGURE..........................................................................................................................7
LIST OF TABLES..........................................................................................................................8
1. OVERVIEW...........................................................................................................................9
1.1 Project Summary.....................................................................................................................9
1.1.1. Purpose, Scope, and Objectives..............................................................................9
1.1.2. Assumptions and Constraints.................................................................................10
1.1.3. Project Deliverables................................................................................................10
1.1.4. Schedule and Budget Summary.............................................................................11
1.2. Evolution of Plan.............................................................................................................12
REFERENCES............................................................................................................................13
2. DEFINITIONS........................................................................................................................14
3. PROJECT ORGANIZATION...................................................................................................15
3.1 External reference.............................................................................................................15
3.2 Internal structure...............................................................................................................16
4. MANAGERIAL PROCESS PLANS.........................................................................................22
4.1. Start-up plan.........................................................................................................................22
4.1.1. Estimation plan.............................................................................................................23
4.1.2. Staffing plan..................................................................................................................31
4.1.3. Resource acquisition plan.............................................................................................31
4.1.4. Project staff training plan..............................................................................................32
4.2 WORK PLAN.........................................................................................................................32
4.2.1. Work activities...............................................................................................................32
4.2.2. Schedule allocation.......................................................................................................41
4.2.3. Resource allocation......................................................................................................41
4.2.4. Budget allocation..........................................................................................................41
5.3 CONTROL PLAN..................................................................................................................41
5.3.1. Requirements control plan............................................................................................41
5.3.2. Schedule control plan...................................................................................................41
5.3.3. Budget control plan.......................................................................................................42
5.3.4. Quality control plan.......................................................................................................42
5.3.5. Reporting plan...............................................................................................................42
5.3.6. Metrics collection plan...................................................................................................42
5.3.7 Risk management plan..................................................................................................43
6. TECHNICAL PROCESS PLANS..........................................................................................43
6.1 Process Model......................................................................................................................43
6.2 Methods, tools, and techniques........................................................................................44
6.3 Product Acceptance Plan.................................................................................................45
7. SUPPORTING PROCESS PLANS........................................................................................45
Page of
7.1. Configuration management plan......................................................................................45

7.2. Verification and validation plan........................................................................................46
7.3. Documentation plan.........................................................................................................46
7.4. Quality assurance plan....................................................................................................46
7.5. Reviews and audits..........................................................................................................46
7.6. Problem resolution plan...................................................................................................47
8. ADDITIONAL PLANS.............................................................................................................47
9. PLAN ANNEXES.....................................................................................................................47
10. INDEX..................................................................................................................................50
List of Figure
Figure 1: External Interface...............................................................................................................15

Figure 2: Internal Interface.................................................................................................................16
Page of
Figure 3: Waterfall Model...................................................................................................................44
List of Tables
Table 1. Change History......................................................................................................................3

Table 2: Schedule and Budget Summary..........................................................................................11
Table 3: Evolution Plan......................................................................................................................12
Page of
Table 4: Definition of Terms...............................................................................................................14

Table 5: Responsibility Assignment Matrix (RAM)............................................................................17
Table 6: Estimation Chart..................................................................................................................23
Table 7: Staffing Plan//contract//agreement......................................................................................31
Table 8 Work Activities......................................................................................................................32
Table 9: Methods and Techniques...................................................................................................44
Table 10: Tools..................................................................................................................................44
Table 11: Product Acceptance Plan..................................................................................................37
1. Overview
This part of the management plan report gives an overview of the report. In the following
subsections purpose, scope, and objectives of the project, the project assumptions and constraints
are providing. Besides this, a list of project deliverables, a summary of the project schedule and
budget, and the plan for the evolution of the project management plan shall be provided in the
following sub-sections.
1.1 Project Summary
The details below depict a summary of the software project. It includes a discussion of the
purpose, scope, objectives, assumptions, constraints, and a summary of the schedule and
budget.
1.1.1. Purpose, Scope, and Objectives

The purpose of this document is to create systematized planning for the development of
the proposed system. It will show the analyzed team plan, design, and implementation of
the system about budgeting, scheduling, managerial, and tasking and responsibility of
each member of the team to inform the client that the developers are reliable, loyal to their
commitment, responsible and it will help to allocate resources in such manner that the
project can finish on time.
The developers will ensure that the system can process the Employee's data accurately,
the system can generate reports on real-time data of the employees that visualize, and
Page of
most importantly, the project must be functional, completed at the allocated time, and
should be within budget.
The Employee Real-Time Employee Attendance Monitoring with Mobile App for Shake and
Slurp as a capstone project for the client aims to improve the client’s process in its
establishment. To ensure the satisfaction and successful completion of the project.
1.1.2. Assumptions and Constraints
In this project, the developers assumed that the project manager together with the team is
seriously responsible for the matters discussed to them by the adviser. It is to play an
essential role in developing the risk management plan.
The following are constraints in developing the system.
1. When there is conflict in member’s schedules.
2. Due to COVID and the deadline is past due it should be the Project Manager will
update the adviser to give reports.
3. When one of the members cannot be contacted due to a communication barrier,

the remaining team will be work on the unfinished task.
4. When there is no teamwork.
5. When the group fails to comply with the scheduled task.
The following are assumptions in developing the system.
1. The project manager together with the team will be responsible for every matter.
2. The members will be shaped and discuss matters.
3. When new normal applied, the users will be must be oriented via Zoom or any
other online media platforms.
4. The users must be oriented with the flow of the software.
Page of
5. Must have a backup of the Database in case of data errors.
1.1.3. Project Deliverables
The following items refer to all the deliverables that expected to be submitted by the
development team:
Complete Software System for client
Software Project Source Code
Project Documentation:
o System Requirements Specifications (SRS)
o Software Project Management Plan (SPMP)
o Software Design Description (SDD)
o Software Test Document (STD)
Memorandum of Agreement.
Approval Sheet.
1.1.4. Schedule and Budget Summary

This section specifies the schedule and the budget for software development. The
duration, personal requirements, and budget of each workflow are the following:
Table 2: Schedule and Budget Summary
Activities Schedule Budget

Duration
₱ 12,000.00
PHASE 1: Initiation 1 month
PHASE 2: Information Gathering ₱ 22,000.00
23 days
PHASE 3: Requirement Specification ₱ 60,000.00
2 months
PHASE 4: Planning ₱ 49,000.00
2 months
PHASE 5: Designing ₱ 56,000.00
2 months
Page of
PHASE 6: Coding ₱ 106,000.00

5 months
PHASE 7: Testing ₱ 11,000.00
1 month
PHASE 8: Deployment ₱ 8,000.00
1 week
PHASE 9: Maintenance ₱ 15,000.00
20 days
Total: ₱ 352,000.00
1.2. Evolution of Plan
This SPMP is evolved from the Initial Plan of the project that is a simple version of this
document. Hence, this document is developed by the Software Mojo Group Members.
There are three scheduled versions of this plan. The following table summarizes the
scheduled versions.
Table 3: Evolution Plan
Version Description of Version Date Released

Beta version Change the Reference Version of March 2020
the Document
Alpha version Edit and Update the Schedule and January 2021
Budget Summary Version of the
Documents
Dry run version April 2021
Arrange an updated version of the
Roles and Responsibilities Version
of the Documents
Final version May 2021
Finalize the Roles and
Responsibilities
Page of
References
Web:
 Jackmon, L. (2009, December 11). Software Project Management Plan: Structure

& Examples. Software Project Management Plan: Structure & Examples.
https://study.com/academy/lesson/software-project-management-plan-structure-
examples.html
 Tutorials Point. (2006). Software Project Management by Tutorial points. Software
Project Management.
https://www.tutorialspoint.com/software_engineering/software_project_management.html
 Software Sustainability Institute. (2012). Writing and using a software
management plan. https://www.software.ac.uk/resources/guides/software-
management-plans
 IEEE. (1988, August 31). 1058.1-1987 - IEEE Standard for Software Project
Management Plans. IEEE Standard | IEEE Xplore.
https://ieeexplore.ieee.org/document/25325
 GeeksforGeeks. (2019, May 2). Software Engineering | Software Project

Management Plan (SPMP).
https://www.geeksforgeeks.org/software-engineering-software-project-
management-plan-spmp/
Page of
Book:
 John W. Satzinger, Robert B. Jackson and Stephen D. Burd, Copyright 2009

course Technology, Engage Learning in a Changing World “Strategic Planning”
Page 17
 Coombes, Hilary – Research using I.T; Copyright Hilary Coombes 2001, Published
by Palgrave Year 2001
2. Definitions
The documents containing the definition of all terms and acronyms required to understand
the SPMP.
Table 4: Definition of Terms
Terms Definition
IEEE Institute of Electrical and Electronics Engineers
SPMP (Software Project Management Plan) Defines the project management plan. It how
a project is going to be carried out. It outlines the
scope, goals, budget, timeline, and deliverables
of a project, and it's essential for keeping
a project on track.
Data Visualization A general term that describes any effort to help
people understand the significance of data by
placing it in a visual context.
a collection of structured information, or data,
DB (Database) typically stored electronically in a computer
system
RAM (Random Access Memory) A memory that temporarily stores the files you
are working on.
The waterfall model is a classical model used in
the system development life cycle to create a
Page of
system with a linear and sequential approach. It

Waterfall Model is termed as waterfall because
the model develops systematically from one
phase to another in a downward fashion
3. Project organization
This clause of the SPMP shall identify interfaces to organizational entities external to the
project; describe the project’s internal organizational structure; and define roles and
responsibilities for the project.
3.1 Internal reference
Francis Rebo P.
Shiela May S. Villanueva Alegre,MIT
Project Manager Adviser
Francis Ian Dela Syril Glein T. Mark Lester Philipcris C.

Victoria Nerricar Mansing Catungal,
Flores,MCS Encarnacion, MCS
Programmer/System Documenter MIT
Panel CCS- Dean
Analyst Panel
Dr. Genesis Naparan

Research Coordinator
Figure 1: Software Mojo Organizational Chart

The Internal Structure of this Project is the Shake and Slurp Business will be guided to
create a new developed System in which the User Interface and External phase of the
System which is the Real-Time Employee Attendance Monitoring with Mobile Application
Page of
developed by the Software Mojo Researchers and will be checked and updated by the
Research Coordinator or Panelist.
3.2 External structure
Danah Arnejo
Owner/Client
SHIELA MAY VILLANUEVA

Project Manager
Supervisor/Cashier
Figure 2: Shake and Slurp Organizational Chart
The External Structure of this Project the project and new developed System Real-
Time Employee Attendance Monitoring with Mobile Application developed will be managed
by the Project Manager and to be developed by the Programmer of the Group and to be
documented by the Documenter. When developing the System together with the
documents it will be checked by the Adviser to finalized the Research Study.
Page of
3.3 Roles and Responsibilities
Everyone should understand their role and each other if there are problems that the team may
encounter shortly, and by having teamwork, the team accomplishes their overall objectives and
goals.
Table 5: Responsibility Assignment Matrix (RAM)

Real-time Labor Cost with Online Accessibility via Mobile App
Status
Dela Victoria, Francis

Villanueva, Shiela May
Mansing, Nerricar
(L) LEADER
(D) Documenter
(R) REVIEWER
Task# WBS Activities
Real-time Labor Cost with

1 Online Accessibility via Mobile
App
Initiation
1 1.1.1 Staffing C R L D ✓ ✓ ✓
3 1.1.2 Look for Clients C R L D ✓ ✓ ☓
4 1.1.4 Meeting with Adviser C R L D ✓ ✓ ✓
5 1.1.5 Prepare for the possible C R L D ✓ ✓ ✓
questions to the client
6 1.1.6 Deciding Possible system to C L R D ✓ ☓ ✓
propose
2.2 Information Gathering
7 2.2.1 Gather Information about the C D L R ✓ ☓ ☓
establishment
8 2.2.2 Interview the client about what C R L D ✓ ✓ ✓
is lacking in the establishment
Page of
9 2.2.3 Business Process Observation C L R R ✓ ☓ ✓

10 2.2.4 Enumerating problems in the C L D D ✓ ✓ ☓
business process
11 2.2.5 Defining the scope of the C L R R ✓ ☓ ☓
proposal
12 2.2.6 Creating the prototype C L R D ✓ ✓ ✓
13 2.2.7 Meeting with the adviser for C R L L ✓ ✓ ✓
finalization
14 2.2.8 Presentation of the proposal C L R D ✓ ✓ ☓
3.3 Requirements Specification
15 3.3.1 Start Creating SRS Documents C R R D ✓ ✓ ☓
16 3.3.2 Creating the Introduction of the C R R D ✓ ✓ ☓
SRS
17 3.3.3 Creating the Purpose of the C R R D ✓ ✓ ✓
SRS
18 3.3.4 Creating the Scope of the SRS C R R D ✓ ✓ ✓
19 3.3.5 Creating the definition of terms C R R D ✓ ☓ ✓
used in the SRS
20 3.3.6 Search References C R R D ✓ ☓ ✓
21 3.3.7 Creating the overview C R R L ✓ ☓ ☓
22 3.3.8 The MOA has been signed by C R L L ✓ ✓ ✓
the client and notarized
23 3.3.9 Created the Overall DescriptionC R L D ✓ ☓ ✓
24 3.3.10 Created the Product C D R R ✓ ✓ ☓
Perspective
25 3.3.11 Created the use cases Product C D R D ✓ ☓ ☓
Function
26 3.3.12 Created the User C D R D ✓ ✓ ✓
Characteristics
27 3.3.13 Listed all the Constraints C R R L ✓ ✓ ☓
28 3.3.14 Listed all Assumptions and C R L D ✓ ✓ ✓
Dependencies
29 3.3.15 Created the use cases of the C L R R ✓ ✓ ☓
Specific Requirements
30 3.3.16 Created the External Interface C D R D ✓ ✓ ✓
Requirements
31 3.3.17 Added all the User Interface C L R D ✓ ☓ ☓
32 3.3.18 Hardware Interface C R R L ✓ ☓ ✓
33 3.3.19 Software Interface C R L D ✓ ✓ ☓
34 3.3.20 Functional Requirements C L R R ✓ ☓ ✓
35 3.3.21 Performance Requirements C L R D ✓ ✓ ✓
36 3.3.22 Design Constraints C L R D ✓ ☓ ✓
Page of
37 3.3.23 Software System Attributes C R R L ✓ ✓ ☓

38 3.3.24 Other Requirements C R L D ✓ ✓ ✓
39 3.3.25 To be checked by the editor C L R R ✓ ✓ ✓
and adviser
40 3.3.26 Finalization of SRS document C L R D ✓ ✓ ✓
4.4 PLANNING
27 4.4.1 Created the Work Breakdown C R L R ✓ ✓ ✓
Structure
28 4.4.2 Overview C R D R ✓ ☓ ✓
29 4.4.3 Project Summary C R D R ✓ ✓ ✓
30 4.4.4 Purpose, Scope, and C R D R ✓ ✓ ✓
Objectives
31 4.4.5 Assumptions and Constraints C R D R ✓ ☓ ✓
32 4.4.6 Schedule and Budget C R D R ✓ ✓ ✓
Summary
33 4.4.7 Evolution of Plan C R D R ✓ ✓ ✓
34 4.4.8 Reference C R D R ✓ ☓ ✓
35 4.4.9 Definition C R D R ✓ ✓ ✓
36 4.4.10 Project Organization C R D R ✓ ✓ ✓
37 4.4.11 External Interface C R D R ✓ ☓ ✓
38 4.4.12 Internal Structure C R D R ✓ ☓ ✓
39 4.4.13 Estimation Plan C R D R ✓ ✓ ☓
40 4.4.14 Work Plan C R D R ✓ ✓ ☓
41 4.4.15 Work Activities C R D R ✓ ✓ ✓
42 4.4.16 Schedule Allocation C R D R ✓ ✓ ✓
43 4.4.17 Resource Allocation C R D R ✓ ☓ ✓
44 4.4.18 Budget Allocation C R D R ✓ ✓ ✓
45 4.4.19 Control Plan C R D R ✓ ✓ ✓
46 4.4.20 Requirements Control Plan C R D R ✓ ☓ ☓
47 4.4.21 Budget Control Plan C R D R ✓ ☓ ✓
48 4.4.22 Quality Control Plan C R D R ✓ ✓ ✓
49 4.4.23 Reporting Plan C R D R ✓ ✓ ☓
50 4.4.24 Project Closeout Plan C R D R ✓ ✓ ✓
51 4.4.25 Technical Process plan C R D R ✓ ✓ ✓
52 4.4.26 Process Model C R D R ✓ ☓ ✓
53 4.4.27 Methods, Tools, and C R D R ✓ ✓ ☓
Techniques
54 4.4.28 Infrastructure Plan C R D R ✓ ☓ ✓
55 4.4.29 Product Acceptance Plan C R D R ✓ ✓ ✓
Page of
56 4.4.30 Supporting process plan C R D R ✓ ☓ ✓

57 4.4.31 Verification and Validation Plan C R D R ✓ ✓ ✓
58 4.4.32 Documentation Plan C R D R ✓ ☓ ✓
59 4.4.33 Quality Assurance Plan C R D R ✓ ☓ ✓
60 4.4.34 Reviews and Audits C R D R ✓ ✓ ✓
61 4.4.35 Problem Resolution Plan C R D R ✓ ✓ ✓
62 4.4.36 Process Improvement Plan C R D R ✓ ✓ ✓
63 4.4.37 To be checked by the adviser C L L L ✓ ✓ ✓
and editor
5.5 DESIGNING
64 5.5.1 Developed process of the C L R L ✓ ✓ ☓
system
65 5.5.2 Checked the design of the C L R R ✓ ✓ ✓
system
66 5.5.3 Checked if the button and labels C L R R ✓ ✓ ☓
are well organized
67 5.5.4 Screenshots of every module C L R L ✓ ☓ ✓
of the system
68 5.5.5 Created the diagrams C L R R ✓ ☓ ✓
69 5.5.6 Process Interface C L R R ✓ ☓ ☓
70 5.5.7 Detailed Design C L R L ✓ ☓ ✓
71 5.5.8 Data Detailed Design C L R R ✓ ☓ ✓
72 5.5.9 To be checked by the editor C L L L ✓ ✓ ☓
and adviser
6.6 CODING
73 6.6.1 Login Form Page C L R D ✓ ✓ ✓
74 6.6.2 User List(Online) C L R D ✓ ✓ ✓
75 6.6.3 New User Page C L R D ✓ ☓ ☓
76 6.6.4 Add New user Page C L R D ✓ ✓ ✓
77 6.6.5 Added comments in every C L R D ✓ ☓ ☓
function used in the coding
78 6.6.6 Developed process of the C L R D ✓ ✓ ☓
system (Modules)
79 6.6.7 User Authentication C L R D ✓ ☓ ☓
80 6.6.8 Edit User Page(Frontend) C L R D ✓ ✓ ✓
81 6.6.9 New User Page(Backend) C L R D ✓ ✓ ✓
82 6.6.10 Deactivate/Re-activate C L R D ✓ ☓ ☓
User(Backend)
83 6.6.11 File Management (Admin) C L R D ✓ ☓ ✓
84 6.6.12 Image local saving changed to C L R D ✓ ✓ ✓
mysql
85 6.6.13 Employees Form C L R D ✓ ✓ ✓
Page of
86 6.6.14 Employees-page(Frontend) C L R D ✓ ☓ ☓
87 6.6.15 New Employees C L R D ✓ ✓ ✓
page(Frontend)
88 6.6.16 Edit Employee(Frontend) C L R D ✓ ✓ ✓
89 6.6.17 Supervisor Form C L R D ✓ ☓ ✓
90 6.6.18 Activity Log(Frontend) C L R D ✓ ✓ ✓
91 6.6.19 Manage Job Types C L R D ✓ ✓ ✓
92 6.6.20 Reports form C L R D ✓ ☓ ✓
93 6.6.21 Shift Schedules C L R D ✓ ✓ ✓
Page(Frontend)
94 6.6.22 Employees History Form C L R D ✓ ☓ ☓
95 6.6.23 Reports History Form C L R D ✓ ☓ ☓
96 6.6.24 Breakdown of Synopsis C L R D ✓ ☓ ☓
97 6.6.25 Checked the module that is C L R D ✓ ✓ ☓
been done
98 6.6.26 Worked the other module that C L R D ✓ ✓ ☓
is the lack in the process
99 6.6.27 Checked the system to the C L R D ✓ ✓ ☓
adviser
100 6.6.28 Worked on the suggestions of C L R D ✓ ✓ ☓
the adviser
101 6.6.29 Check and Worked the C L R D ✓ ✓ ☓
suggestions of the client
102 6.6.30 To be checked by the adviser C L R D ✓ ☓ ☓
103 7.7 Testing
104 7.7.1 Create software Test Plan C R R L ✓ ☓ ☓
105 7.7.2 Tested software to the C L L L ✓ ✓ ☓
hardware interface
106 7.7.3 Tested the Main business C L L L ✓ ✓ ☓
process
107 7.7.4 Tested the Employee process C L L L ✓ ☓ ☓
interface
108 7.7.5 Planned weekly statistical C L L L ✓ ✓ ☓
report test
109 7.7.6 Tested a Dry-run for the C L L L ✓ ✓ ✓
Software and App
110 7.7.7 Researchers and Adviser C L L L ✓ ✓ ✓
Tested the Software
111 7.7.8 Presented the Software and C L L L ✓ ✓ ✓
Application to the Client
LEADER 50 25 18
Page of
DOCUMENTER 5 36 56
REVIEWER 58 66 48
TOTAL C 113 127 122
LEGEND PERSONNEL
C-omplete Francis Dela Victoria (Programmer/System Analyst)
P-ending Shiela May S. Villanueva (Project Manager)

N-ot complete Nerricar D. Mansing (Documenter)
4. Managerial process plans
The Software Management Plan (SPMP) shall specify the project management process.
This clause must be coherent with the statement of project scope and must include the
project start-up plan, risk management plan, project work plan, and project control plan.
4.1. Start-up plan
This subclause of the SPMP shall specify the estimation plan, staffing plan, resource
acquisition plan, and training plan. Depending on the size and scope of the project, these
plans may be incorporated directly or by reference to other plans.
Page of
4.1.1. Estimation plan

This sub-clause specifies the cost and schedule for conducting the project as well as
methods and techniques to be used to estimate project cost, schedule, and resource
requirements.
Table 6: Estimation Chart

Estimation Chart
Task # WBS # Deliverable or Work Product Duration Cost
1 Initiation 10 days ₱ 12,000.00

1.1 Staffing 1 day ₱ 2,000.00
1
1.2 Look for Clients 1 day ₱ 2,000.00
2
1.3 Meeting with Adviser 1 day ₱ 2,000.00
3
1.4 Prepare for the possible questions 4 days ₱ 2,000.00
4 to the client
1.6 Deciding Possible system to 3 days ₱ 4,000.00
6 propose
2 INFORMATION GATHERING 31 days ₱ 25,000.00
2.1 Gather Information about the 5 days ₱ 5,000.00
7 establishment
2.2 Interview the client about what 3 days ₱ 2,000.00
8 are the lacking in the
establishment
2.2 Business Process Observation 4 days ₱ 3,000.00
9
2.4 Enumerating problems in the 7 days ₱ 5,000.00
10 business process
2.5 Defining the scope of the proposal 4 day ₱ 3,000.00
11
2.6 Creating the prototype 4 days ₱ 3,000.00
12
2.7 Meeting with the adviser for 3 days ₱ 2,000.00
13 finalization
2. 8 Presentation of the proposal 1 day ₱ 2,000.00
14
3 REQUIREMENTS ₱ 60,000.00
2 months
SPECIFICATION
Page of
3.1 The MOA has been signed by the 3 days ₱ 2,000.00

20
client and notarized
3.2 The client has been approved the 3 days ₱ 2,000.00
21
proposal of the group
3.3 The group have been defined the 3 days ₱ 2,000.00
22
scope of the system
3.4 The adviser and the group agreed 3 days ₱ 2,000.00
23
the proposal
3.5 Revised of SRS Documents 3 days ₱ 2,000.00
24
3.5.1 Created the Introduction 4 days ₱ 3,000.00
25
3.5.2 Created the Purpose 4 days ₱ 3,000.00
26
3.5.3 Created the Scope 4 days ₱ 3,000.00
27
3.5.4 Listed the Definition 4 days ₱ 3,000.00
28
3.5.5 Searched References 5 days ₱ 5,000.00
29
3.5.6 Created the Overview 3 days ₱ 2,000.00
30
3.6 Created the Overall Description 3 days ₱ 2,000.00
31
3.6.1 Created the Product Perspective 3 days ₱ 2,000.00
32
3.6.1.1 Created the use cases Product 3 days ₱ 2,000.00
33
Function
3.6.2 Created the User Characteristics 3 days ₱ 2,000.00
34
3.6.3 Listed all the Constraints 3 days ₱ 2,000.00
35
3.6.4 Listed all Assumptions and 3 days ₱ 2,000.00
36
Dependencies
3.7 Created the use cases of the 3 days ₱ 2,000.00
37
Specific Requirements
3.7.1 Created the External Interface 3 days ₱ 2,000.00
38
Requirements
3.7.1.1 Added all the User Interface 3 days ₱ 2,000.00
39
3.7.1.2 Hardware Interface 3 days ₱ 2,000.00
40
3.7.1.3 Software Interface 3 days ₱ 2,000.00
41
3.8 Functional Requirements 3 days ₱ 2,000.00
42
Page of
3.9 Performance Requirements 3 days ₱ 2,000.00

43
3.9.1 Design Constraints 3 days ₱ 2,000.00
44
3.9.2 Software System Attributes 3 days ₱ 2,000.00
45
3.9.2 Other Requirements 3 days ₱ 2,000.00
46
3.10 To be checked by the editor and 3 days ₱ 2,000.00
47
adviser
3.11 Finalization of SRS document 3 days ₱ 2,000.00
48
4 PLANNING 3 months ₱ 50,000.00
4.2 Group meeting 2 days ₱ 1,000.00

49
4.3 Created the Work Breakdown 2 days ₱ 1,000.00
50
Structure
4.4.1 Project Summary 2 days ₱ 1,000.00
52
4.4.1.1 Purpose, Scope and Objectives 2 days ₱ 1,000.00
53
4.4.1.2 Assumptions and Constraints 2 days ₱ 1,000.00
54
4.4.1.3 Schedule and Budget Summary 2 days ₱ 1,000.00
55
4.4.2 Evolution of Plan 2 days ₱ 1,000.00
56
4.5 Reference 2 days ₱ 1,000.00
57
4.6 Definition 2 days ₱ 1,000.00
58
4.7 Project Organization 2 days ₱ 1,000.00
59
4.7.1 External Interface 2 days ₱ 1,000.00
60
4.7.2 Internal Structure 2 days ₱ 1,000.00
61
4.7.3 Roles and Responsibilities 2 days ₱ 1,000.00
62
4.8 Managerial Process Plans 2 days ₱ 1,000.00
63
4.8.1 Start-up Plan 2 days ₱ 1,000.00
64
4.8.1.1 Estimation Plan 2 days ₱ 1,000.00
65
Page of
4.8.1.2 Staffing Plan 2 days ₱ 1,000.00

66
4.8.1.3 Resource Acquisition Plan 2 days ₱ 1,000.00
67
4.8.1.4 Project Staff Training Plan 2 days ₱ 1,000.00
68
4.9 Work Plan 2 days ₱ 1,000.00
69
4.9.1 Work Activities 2 days ₱ 1,000.00
70
4.9.2 Schedule Allocation 2 days ₱ 1,000.00
71
4.9.3 Resource Allocation 2 days ₱ 1,000.00
72
73 4.9.4 Budget Allocation 2 days ₱ 1,000.00
4.10 Control Plan 2 days ₱ 1,000.00

74
4.10.1 Requirements Control Plan 2 days ₱ 1,000.00
75
4.10.2 Schedule Control Plan 2 days ₱ 1,000.00
76
4.10.3 Budget Control Plan 2 days ₱ 1,000.00
78
4.10.3 Quality Control Plan 2 days ₱ 1,000.00
79
4.10.5 Reporting Plan 2 days ₱ 1,000.00
80
4.10.6 Metrics Collection Plan 2 days ₱ 1,000.00
81
4.10.7 Risk Management Plan 2 days ₱ 1,000.00
82
4.10.8 Project Closeout Plan 2 days ₱ 1,000.00
83
4.10.9 Technical Process plan 2 days ₱ 1,000.00
84
4.11.1 Process Model 2 days ₱ 1,000.00
85
4.11.2 Methods, Tools, and Techniques 2 days ₱ 1,000.00
86
4.11.3 Infrastructure Plan 2 days ₱ 1,000.00
87
4.11.4 Product Acceptance Plan 2 days ₱ 1,000.00
88
4.12 Supporting process plan 2 days ₱ 1,000.00
89
4.12.1 Configuration Management Plan 2 days ₱ 1,000.00
90
Page of
4.12.2 Verification and Validation Plan 2 days ₱ 1,000.00

91
4.12.3 Documentation Plan 2 days ₱ 1,000.00
92
4.12.4 Quality Assurance Plan 2 days ₱ 1,000.00
93
4.12.5 Reviews and Audits 2 days ₱ 1,000.00
94
4.12.6 Problem Resolution Plan 2 days ₱ 1,000.00
95
4.12.7 Subcontractor Management Plan 2 days ₱ 1,000.00
96
4.12.8 Process Improvement Plan 2 days ₱ 1,000.00
97
98 4.13 To be checked by the adviser and 2 days ₱ 1,000.00

editor
5 DESIGNING ₱ 60,000.00
2 months
5.2 Developed process of the system 3 days ₱ 2,000.00
99
5.3 Group meeting 3 days ₱ 2,000.00
100
5. 5 Checked if the button and labels 3 days ₱ 2,000.00
102
are well organize
5.6 Screenshots every module of the 3 days ₱ 2,000.00
103
system
5.7 Created the diagrams 3 days ₱ 2,000.00
104
5.8 Introductions 3 days ₱ 2,000.00
105
5.8 1 Purpose 3 days ₱ 2,000.00
106
5.8.2 Scope 3 days ₱ 2,000.00
107
5.8.3 Definitions and Acronyms 3 days ₱ 2,000.00
108
5.9 References 3 days ₱ 2,000.00
109
5.9.1 Decomposition Description 3 days ₱ 2,000.00
110
5.10 Module Decomposition 3 days ₱ 2,000.00
111
5.10.1 Concurrent Process 3 days ₱ 2,000.00
112
Decomposition
5.10.2 Data Decomposition 3 days ₱ 2,000.00
113
Page of
5.10.3 Dependency Description 3 days ₱ 2,000.00

114
5.10.3.1 Inter-module Dependencies 3 days ₱ 2,000.00
115
5.10.3.2 Inter-process Dependencies 3 days ₱ 2,000.00
116
5.11 Data Dependencies 3 days ₱ 2,000.00
117
5.12 Interface Description 3 days ₱ 2,000.00
118
5.12.1 Module Interface 3 days ₱ 2,000.00
119
5.12.2 Process Interface 3 days ₱ 2,000.00
120
5.13 Detailed Design 3 days ₱ 2,000.00
121
5.13.1 Module Detailed Design 3 days ₱ 2,000.00
122
5.13.1.1 Data Detailed Design 3 days ₱ 2,000.00
123
5.14 Appendix 3 days ₱ 2,000.00
124
5.15 Index 3 days ₱ 2,000.00
125
5.16 Annexes 3 days ₱ 2,000.00
126
5.17 To be checked by the editor and 3 days
127 ₱ 1,800.00
adviser
6 CODING 7 Months ₱80,000.00
6.1 Added comments in every function 5 days

128 ₱ 5,000.00
use in the coding
6.2 Developed process of the system 3 weeks
129 ₱ 20,000.00
(Modules)
6.2.2 File Management (Admin) 5 days
131 ₱ 3,000.00
6.2.3 Patient Form
132 5 days ₱ 3,000.00
6.2.4 Stock-in form 5 days
133 ₱ 3,000.00
6.2.5 Consultation form 5days
134 ₱ 3,000.00
6.2.6 Inventory form 5 days
135 ₱ 3,000.00
6.2.7 Reports form
136 5 days ₱ 3,000.00
Page of
6.2.8 Medical History form 5 days

137 ₱ 3,000.00
6.2.9 Data visualization 5 days
138 ₱ 3,000.00
6.2.9.1 Breakdown of Synopsis form 5 days
139 ₱ 3,000.00
6.2.9.2 Breakdown of Consultation form
140 5 days ₱ 3,000.00
6.2.9.3 Breakdown of Trends (Synopsis 5 days
141 ₱ 3,000.00
Comparison Per Year)
6.2.9.4 Breakdown of (Trends Synopsis 5days
142 ₱ 3,000.00
form)
6.2.10 File Management (User) 5 days
143 ₱ 3,000.00
6.2.11 File Management (Medicine)
144 5 days ₱ 3,000.00
6.2.12 File Management (Course) 5 days
145 ₱ 3,000.00
6.2.13 File Management (Synopsis) 5days
146 ₱ 3,000.00
6.2.14 Stock-out form 5 days
147 ₱ 3,000.00
6.3 Group meeting
148 5 days ₱ 3,000.00
6.4 Checked the module that is been 5 days
149 ₱ 3,000.00
done
6.5 Worked the other module that is 5days
150 ₱ 3,000.00
lack in the process
6.6 Group Meeting 1 week
151 ₱ 3,000.00
6.7 Planning
152 5 days ₱ 3,000.00
6.8 Meeting with the adviser 1 week
153 ₱ 3,000.00
6.9 Checked the system to the client 5days
154 ₱ 3,000.00
6.10 Group meeting 5 days
155 ₱ 3,000.00
6.11 Worked the suggestions of the
156 5 days ₱ 3,000.00
client
6.12 To be checked by the adviser
157 5 days ₱ 3,000.00
7 Testing 1 month ₱ 11,000.00
7.1 Create software Test Plan
158 3 days ₱ 1,000.00
Page of
7.2 Tested software to hardware

159 3 days ₱ 1,000.00
interface
7.3 Tested the Main business process
160 3 days ₱ 1,000.00
7.4 Tested the Employee process
161 3 days ₱ 1,000.00
interface
7.5 Planned weekly statistical report
162 1 week ₱ 1,000.00
test
7.6 Group Meeting
163 3 days ₱ 500.00
164 1 week ₱ 2,000.00
adviser
7.8 Checked the system to the client
165 2 days ₱ 1,000.00
7.9 Group meeting
166 2 days ₱ 1,000.00
8.0 Work the suggestions of the client
167 3 days ₱ 1,000.00
168 3 days ₱ 500.00
4.1.2. Staffing plan

The table below shows the members involved in developing the project. The table
summarizes the affiliation of all group members, the phase of every member assign, and
the working hours.
Table 7: Staffing Plan//contract//agreement
Human Resource Type Affiliation to Work (Days) Key Project Budget

Project Phases
Project Manager Villanueva. Full time Planning 3, 500

Shiela May S.
Page of
Programmer//System Dela Victoria, Full time Design, Coding 2,000

Analyst Francis and Analyze
Documenter Mansing, Full time Documents 1,000

NerrNerricar
4.1.3. Resource acquisition plan

The group based the study on the IEEE Standard for Software Project Management Plan.
For example, a reference like google.com and other sites that serve as a guide in
developing the software. The developers will contact their client anytime if there is a need
for other resources like for example the client offer their office.
The resources that the group has:

 Laptop/Desktop for the software development and documentation.
 Internet connection
 Single motor for the transportation of the group to the client.
The System uses Android Studio for developing the mobile application,
Node.js for developing the system, and No SQL and firebase for the
databases.
4.1.4. Project staff training plan

The group members are already remembered their task. The developers can also
manage to work as a team and can develop a functional system. The purpose of this
project is to also learn and develop each participant's skills in software projects' task
fields.
4.2 Work plan
Page of
Work activities should decompose a level that exposes all project risk factors and allows
an accurate estimate of resources requirements and schedule duration for each work
activity.
4.2.1. Work activities

All types of work that need to be finished and their expected time can be described in the
table below.
Table 8: Work Activities

Work Activities
ID WBS # Task Name Predecessor Successor

#
1 Initiation
1.1 Meeting with adviser
1
1.2 Group meeting 1 3, 4
2
1.3 Create a group contract 2 4,5, 6
3
1.4 To be check by the adviser 3 5
4
1.5 Signing of contract 4 6, 7, 8
5
1.6 Start the revising 5 7
6
1.7 Preparing for the possible questions
7 1 8
to the client
1.8 Deciding the possible system to
8 1, 2 9
propose
2 INFORMATION GATHERING
2.1 Group meeting 8 10, 11, 12,

9
13
2.2 Interview the client about what are 9 11, 12,13,14
10
the lacking in the system
development
2.2 Researched more about Data 9 12, 13
11
Visualization
Page of
2.4 Business process of the client have 9 13

12
been analyzed by the group
2.5 Created again the new ERD of the 12 14, 15, 16
13
system
2.6 Analyzed the other module to be 13 15
14
develop
2.7 New ERD to be checked by the 9 16, 17, 18
15
adviser
2. 8 Finalized the entities and attributes 15 17
16
2.9 Group Meeting
17 16 18, 19
2. 10. The group have identified the
18 17 19
problems of the business
2.11 Group meeting with the adviser, and
19 18 20
the client
3 REQUIREMENTS SPECIFICATION
3.1 The MOA has been signed by the 19 21

20
client and notarized
3.2 The client has been approved the 19 22
21
proposal of the group
3.3 The group have been defined the 19 23
22
scope of the system
3.4 The adviser and client agreed the 20, 21 24
23
group proposal
3.5 Revised of SRS Documents 24 25
24
3.5.1 Created the Introduction 24 25
25
3.5.2 Created the Purpose 25 26
26
3.5.3 Created the Scope 25, 26 28
27
3.5.4 Listed the Definition 25,26,27 29
28
3.5.5 Searched References 25,26,27,28 30
29
3.5.6 Created the Overview 29 31, 32, 33,
30
34
3.6 Created the Overall Description 30 32
31
3.6.1 Created the Product Perspective 30, 31 33, 34
32
3.6.1.1 Created the use cases Product 32 34
33
Function
Page of
3.6.2 Created the User Characteristics 30, 31, 32 35

34
3.6.3 Listed all the Constraints 26, 27 36
35
3.6.4 Listed all Assumptions and 26, 27, 35 37
36
Dependencies
3.7 Created the use cases of the Specific 31 38
37
Requirements
3.7.1 Created the External Interface 35, 36, 37 39
38
Requirements
3.7.1.1 Added all the User Interface 38 40
39
3.7.1.2 Hardware Interface 37, 38 41
40
3.7.1.3 Software Interface 40 42
41
3.8 Functional Requirements 40, 41 43, 44, 45
42
3.9 Performance Requirements 42 44
43
3.9.1 Design Constraints 38, 39, 40 45
44
3.9.2 Software System Attributes 44 46
45
3.9.2 Other Requirements 42, 43 47
46
3.10 To be checked by the editor and 25- 46 48
47
adviser
3.11 Finalization of SRS document 25,47 48
48
4 PLANNING
4.2 Group meeting 48 50, 51

49
4.3 Created the Work Breakdown 49 69, 70
50
Structure
4.4 Overview 52
51
4.4.1 Project Summary 51 53
52
4.4.1.1 Purpose, Scope and Objectives 51, 52 54
53
4.4.1.2 Assumptions and Constraints 54 55
54
4.4.1.3 Schedule and Budget Summary 54 56
55
Page of
4.4.2 Evolution of Plan 48,51 57

56
4.5 Reference 56 58
57
4.6 Definition 51 - 57 59
58
4.7 Project Organization 53, 54 60
59
4.7.1 External Interface 59 61
60
4.7.2 Internal Structure 59, 60 62
61
4.7.3 Roles and Responsibilities 61 63
62
63 4.8 Managerial Process Plans 62 64
4.8.1 Start-up Plan 63 65, 66, 67

64
4.8.1.1 Estimation Plan 64 66, 67, 68
65
4.8.1.2 Staffing Plan 65 68
66
4.8.1.3 Resource Acquisition Plan 66 68
67
4.8.1.4 Project Staff Training Plan 67 69
68
4.9 Work Plan 63 70
69
4.9.1 Work Activities 62, 65, 70 71
70
4.9.2 Schedule Allocation 70 72
71
4.9.3 Resource Allocation 71 73
72
4.9.4 Budget Allocation 65, 67, 70 74
73
4.10 Control Plan 73 75
74
4.10.1 Requirements Control Plan 74 76
75
4.10.2 Schedule Control Plan 75 77
76
4.10.3 Budget Control Plan 73 78
78
4.10.3 Quality Control Plan 78 79
79
4.10.5 Reporting Plan 80 82
80
Page of
4.10.6 Metrics Collection Plan 80 82

81
4.10.7 Risk Management Plan 81 83
82
4.10.8 Project Closeout Plan 82 84
83
4.10.8 Technical Process plan 83 85
84
4.11.1 Process Model 84 86
85
4.11.2 Methods, Tools, and Techniques 85 87
86
4.11.3 Infrastructure Plan 85 88
87
88 4.11.4 Product Acceptance Plan 87 89
4.12 Supporting process plan 88 90

89
4.12.1 Configuration Management Plan 89 91
90
4.12.2 Verification and Validation Plan 90 92
91
4.12.3 Documentation Plan 91 93
92
4.12.4 Quality Assurance Plan 92 94
93
4.12.5 Reviews and Audits 93 95
94
4.12.6 Problem Resolution Plan 94 96
95
4.12.7 Subcontractor Management Plan 95 97
96
4.12.8 Process Improvement Plan 96 98
97
4.13 To be checked by the adviser and 51-97 99
98
editor
5 DESIGNING
5.2 Developed process of the system

99 99 100
5.3 Group meeting
10 99 101
0
5.4 Checked the design of the system
10 100 102
1
5. 5 Checked if the button and labels are
10 101 103
Page of
well organize
2
5.6 Screenshots every module of the
10 102 104
system
3
5.7 Created the diagrams
10 103 105
4
5.8 Introductions 100 106
10
5
5.8 1 Purpose 105 107
10
6
10 5.8.2 Scope 106 108

7
5.8.3 Definitions and Acronyms 107 109
10
8
5.9 References 108 110
10
9
5.10 Decomposition Description 109 111
11
0
5.10.1 Module Decomposition 110 112,113,114
11
1
5.10.1 Concurrent Process Decomposition 111 113, 114
11
2
5.10.2 Data Decomposition 112 114
11
3
5.10.3 Dependency Description 113 115
11
4
5.10.3.1 Inter-module Dependencies 112,113, 114 116
11
5
5.10.3.2 Inter-process Dependencies 115 117
11
6
5.11 Data Dependencies 113, 114 118
11
7
Page of
5.12 Interface Description 115, 116 119

11
8
5.12.1 Module Interface 118 120
11
9
5.12.2 Process Interface 119 121, 122
12
0
5.13 Detailed Design 120 122
12
1
5.13.1 Module Detailed Design 121 123
12
2
5.13.1.1 Data Detailed Design 122 124
12
3
5.14 Appendix 123 125
12
4
5.15 Index 124 126
12
5
5.16 Annexes 125 127
12
6
5.17 To be checked by the editor and
12 101-126 128
adviser
7
6 CODING
6.1 Added comments in every function

12 129 129
use in the coding
8
6.2 Developed process of the system
12 128 130
(Modules)
9
6.2.1 User Authentication
13 129 131
0
6.2.2 File Management (Admin)
13 130 132
1
6.2.3 Patient Form
13 131 133
2
Page of
6.2.4 Stock-in form

13 131 134
3
6.2.5 Consultation form
13 131 135
4
6.2.6 Inventory form
13 131 136
5
6.2.7 Reports form
13 130 137
6
6.2.8 Medical History Form
13 132-135 138
7
6.2.9 Data visualization 132-37 139
13
8
6.2.9.1 Breakdown of Synopsis form 138 140
13
9
6.2.9.2 Breakdown of Consultation form 138 141
14
0
6.2.9.3 Breakdown of Trends (Synopsis 138 142
14
Comparison Per Year)
1
6.2.9.4 Breakdown of (Trends Synopsis 138 143
14
form)
2
6.2.10 File Management (User) 138 144
14
3
6.2.11 File Management (Medicine) 131 145
14
4
6.2.12 File Management (Course) 134,135 146
14
5
6.2.13 File Management (Synopsis)
14 134, 135 147
6
6.2.14 Stock-out form
14 132 148
7
6.3 Group meeting
14 132 149
8
Page of
6.4 Checked the module that is been

14 132,133,134, 150
done
9 145, 146
6.5 Worked the other module that is lack
15 132, 133, 151
in the process
0 134, 145, 146
6.6 Checked the system to the adviser
15 145, 146,148, 152
1 149, 150
6.7 Group meeting
15 145, 146,148, 153
2 149, 150
15 145, 146,148, 154
adviser
3 149, 150
15 145, 146,147, 156
4 148, 149, 150
6.10 Group meeting
15 150 157
5
6.11 Worked the suggestions of the client
15 156 158
6
15 145 159
7
7 Testing 149, 150 160
7.1 Create software Test Plan
15 159 161
8
7.2 Tested software to hardware
15 129- 160 162
interface
9
7.3 Tested the Main business process
16 161 163
0
7.4 Tested the Employee process
16 162 164
interface
1
7.5 Planned weekly statistical report test
16 161 165
2
6.7 Group meeting
16 164 166
5
Page of

16 164 167
adviser
6
16 164, 165 168
7
6.10 Group meeting
16 167 169
8
6.11 Work the suggestions of the client
16 167, 168 170
9
17 165-169 171
0
4.2.2. Schedule allocation

The project duration is good for 12 months, with deliverables in May 2021. The team must be
flexible for schedules in case conflicts arise.
4.2.3. Resource allocation

The project duration is constrained to the school year 2020 - 2021 with final deliverables.
The project starts in October 2020 and must end approximately May 2021. The team will
control the schedule but the project manager will oversee the implementation, be
responsible for the overall quality and interact with users. Group members will have
discussed the problem encountered and so on the progress and determine if any
changes need to be made.
4.2.4. Budget allocation

The expenditures of the team comprise the budget for transportation, team allowance,
supplies, and printing costs of the documents. For the breakdown of the overall budget,
refer to the table of Work Activities.
5.3 Control plan

The Software Mojo group will be responsible for ensuring that the project will be delivered
Page of
on time and within budget. In case of a malfunction / technical problem of the system, the
users will contact the system analyst or the programmer for assistance.
5.3.1. Requirements control plan

The requirements control plan will manage based on the Software Requirement
Specification whenever there is a change on the document.
5.3.2. Schedule control plan
The Project Manager will maintain the schedule in a project document. The Project
Manager will be responsible for gathering the individual tasks for each member and
making the status report. If the schedule is not on track, the Group will follow have a
schedule control meeting. To meet the schedules on time the Project Manager will monitor
group members every meeting and everyone should pass an output that has been assign.
5.3.3. Budget control plan

The Project Manager is assigned to keep the money properly. Expenses may include
printing of documents, gasoline, snacks, and meals of the members.
5.3.4. Quality control plan

Weekly meetings and reviews at the end of each phase will be the main mechanism that
the team will use to control the quality of the work process and the resulting work. The
adviser must see to it that documents are properly written of the system is accomplished.
5.3.5. Reporting plan
Internal Reporting
All the developers of The Software Mojo Group will submit the finished task based on the
schedule of the Project manager. The internal reporting happens once a week together
with the adviser.
Logbook is a book where the members of the group attached their signatures every
Page of
meeting for their attendance.
Messenger is a group chat on social media where members of the group can
communicate.
5.3.6. Metrics collection plan

Each member is required to report the tasks assigned either done or not done, problems,
status, or plans at every meeting of the group. The project manager will manipulate the
data given by the group members and analyze the efforts spent per developer.
5.3.7 Risk management plan

The following are identified risks:
 The group will conduct over time if there are requirements that need to be
submitted immediately.
 The group shall have a backup copy of the system and all the important
documents.
 Communication in the group is very important. The assigned person should be

actively involved in all work to be able to replace his counterpart.
6. Technical process plans
This section of the SPMP gives an overview of the technical process that will follow in the
project. It covers the process models, tools, and methods that the developers will use.
6.1 Process Model

The group project will use the Waterfall model to illustrate the software development
process of the project. This means that any phase in the development begins only if the
previous phase is complete. As such, the project phases with start, finish dates, and goals
for each phase are outlined in the table below.
Page of
Figure 3 : Waterfall Model

Describe the Model of the system.
The table below describe the requirements gathering, Analysis, Design of the System,
Coding, Testing and then Operations or Deployment of the system must be thoroughly
analyzed and properly documented.t his phase also includes the necessary support and
maintenance to ensure the application is working correctly and is up to date.
6.2 Methods, tools, and techniques
Table 9 : Methods and Techniques
Category Methods and Techniques

Meetings
Requirements gathering
Interviews
Consultation/Advising
Model structural aspects of the
Formal specification and analysis
requirements and design
Table 10 : Tools
Page of
Category Tools
Compiler Node.js
Operating System Windows 10
Database: NoSql
Software Development Languages
IDE: Navicat
Language:
Design Photoshop
Documents MS Word
Diagrams Astah Community
6.3 Product Acceptance Plan
The product acceptance plan is an agreement between a client and the researchers that
states the tasks that need to be completed and the criteria that must be met to get final
approval from the client at the end of the project plan. The said activity, held at Gaisano
Capital where one of the shake and slurp businesses is in the area. Ms. Danah Arnejo
together with the team accept our system together with our product box with manual inside
on May 17, 2021, and followed by signing the MOA and certificate of acceptance on May
18, 2021,
7. Supporting process plans

This section of the SPMP will include the methods for the supporting processes that are
part of the software project. These plans include a configuration management plan,
verification and validation plan, documentation plan, quality assurance, reviews and audits,
problem resolution plan, subcontractor management plan, and process improvement plan.
7.1. Configuration management plan

All project deliverables are restrained configuration items. The configuration item was
Page of
termed after the document SRS, SDD, and followed by the variety figure.
7.2. Verification and validation plan

The project manager and tester will verify the system if the requirements are finished. The
team members are also involved in the testing phase of the system.
7.3. Documentation plan

Some deliverables will form during the life cycle of the project. The list of documents that
will be created includes:
Software Requirement Specification (SRS) - defines the functionality that is
required by the user.
Software Project Management Plan (SPMP) – identifies the project
management plan for the entire project study.
Software Design Description (SDD) – defines the design description of the
project.
Software Test Design (STD) – establishes the testing result of the project
7.4. Quality assurance plan

The Project manager will check every week if the group accomplishes their assigned task
to ensure the quality of the system and the deliverables.
7.5. Reviews and audits

The reviewers will finish every document or part of the project. The audit is at the end of
every paper. Every expense should be knowledgeable to each group member. If in case
that the costs will exceed the budget, the project manager will manage and be aware of
the money that had been used and liquidated or reported.
This section will describe the review, schedule, and methods used to conduct project
reviews and audits.
The table headings are defined as follows:
 Review/Audit: the review/audit type described by the remaining columns in the
row.
Page of
 Schedule: the scheduled basis for the review meetings.

 Method: a characterization of what will be finalized in the review.
7.6. Problem resolution plan

This sub-clause of the SPMP shall specify the resources, methods, tools, techniques, and
procedures to be used in reporting, analyzing, prioritizing, and processing software
problem reports generated during the project. The problem resolution plan should indicate
the roles of development, configuration management, the change control board, and
verification and validation in problem resolution work activities. Efforts devoted to problem
reporting, analysis, and resolution should be separately reported so that rework can be
tracked and process improvement accomplished.
8. Additional Plans
This clause of the SPMP shall contain additional plans required to satisfy product
requirements and contractual terms. Additional plans for a particular project may include
plans for assuring that safety, privacy, and security requirements for the product are met,
special facilities or equipment, product installation plans, user-training plans, integration
plans, system transition plans, product maintenance plans.
9. Plan Annexes
The following photo documentation is the actual event that happened upon signing the
Memorandum of agreement, Certificate of Acceptance, and receiving the product box
together with the manual.
Page of
10. Index
Page of
A project.......iv, 1, 2, 4, 5, 6, 7, 8, 9, 14, 15, 23, 24, 33,

34, 35, 36, 38, 39, 40
Acceptance...........................vi, viii, 12, 19, 29, 38, 41
R
D
Real-Time.........................................................1, 8, 9
Database........................................................3, 7, 37 Reference...............................................4, 11, 17, 27
deliverables.....................................1, 3, 6, 33, 38, 39 resources............................................1, 5, 23, 24, 40
M S
Monitoring.........................................................1, 8, 9 Software....i, ii, iv, 3, 4, 5, 6, 8, 11, 13, 14, 17, 23, 27,
34, 35, 37, 39
P System......ii, iv, 3, 8, 9, 11, 14, 17, 23, 24, 27, 36, 37
systematized.............................................................1
plan....iv, v, vi, 1, 2, 4, 5, 6, 12, 14, 15, 18, 19, 23, 24,
29, 34, 35, 38, 39, 40
Page of

Saint Columban College: Pagadian City

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Saint Columban College: Pagadian City

Uploaded by

Copyright:

Available Formats

SAINT COLUMBAN COLLEGE

COLLEGE OF COMPUTER STUDIES

Software Project Management Plan

Real-time Labor Cost with Online Accessibility

via Mobile App

Dela Victoria, Francis Ian

Villanueva, Shiela May S.

Dela Victoria, Francis Ian Mansing, Nerricar

Francis Rebo P. Alegre, MIT

Presented to and approved by the Panel Members:

Syril Glein T. Flores, MCS

Mark Lester Catungal,MIT Danah Arnejo

Submitted to and accepted by:

Philipcris C. Encarnacion, MCS

Table 1. Change History

Date Reason for Changes Person who suggested Document

7.1. Configuration management plan......................................................................................45

Figure 1: External Interface...............................................................................................................15

Figure 3: Waterfall Model...................................................................................................................44

Table 1. Change History......................................................................................................................3

Table 4: Definition of Terms...............................................................................................................14

1.1 Project Summary

1.1.1. Purpose, Scope, and Objectives

1.1.2. Assumptions and Constraints

1. When there is conflict in member’s schedules.

3. When one of the members cannot be contacted due to a communication barrier,

4. When there is no teamwork.

5. When the group fails to comply with the scheduled task.

The following are assumptions in developing the system.

2. The members will be shaped and discuss matters.

4. The users must be oriented with the flow of the software.

5. Must have a backup of the Database in case of data errors.

1.1.3. Project Deliverables

1.1.4. Schedule and Budget Summary

Table 2: Schedule and Budget Summary

Activities Schedule Budget

PHASE 6: Coding ₱ 106,000.00

1.2. Evolution of Plan

Table 3: Evolution Plan

Version Description of Version Date Released

 Jackmon, L. (2009, December 11). Software Project Management Plan: Structure

 Software Sustainability Institute. (2012). Writing and using a software

management plan. https://www.software.ac.uk/resources/guides/software-

Management Plans. IEEE Standard | IEEE Xplore.

 GeeksforGeeks. (2019, May 2). Software Engineering | Software Project

 John W. Satzinger, Robert B. Jackson and Stephen D. Burd, Copyright 2009

Table 4: Definition of Terms

IEEE Institute of Electrical and Electronics Engineers

system with a linear and sequential approach. It

3.1 Internal reference

Francis Ian Dela Syril Glein T. Mark Lester Philipcris C.

Dr. Genesis Naparan

Figure 1: Software Mojo Organizational Chart

3.2 External structure

SHIELA MAY VILLANUEVA

Figure 2: Shake and Slurp Organizational Chart

3.3 Roles and Responsibilities

Table 5: Responsibility Assignment Matrix (RAM)

Dela Victoria, Francis

Real-time Labor Cost with

9 2.2.3 Business Process Observation C L R R ✓ ☓ ✓

37 3.3.23 Software System Attributes C R R L ✓ ✓ ☓

56 4.4.30 Supporting process plan C R D R ✓ ☓ ✓