Software Project Management Plan

COMASYS
Software Project Management Plan
Version: SPMP 1.0
Date of issue: 13/01/2015
Prepared by
Çağrı KILIBOZ (cagri.kiliboz@metu.edu.tr)
Fatih ÜNVER (fatih.unver@metu.edu.tr)
Seval ÜNVER (unver.seval@metu.edu.tr)
COMASYS SPMP | 1

Signatures
The page where signatures of the people who is responsible for approving this SPMP are exists.
I certify that the information in this application is complete and accurate to the best of my knowledge.
Name Surname Profession Signature Date Signature
Prof. Dr. Onur Demirörs Project Advisor
Murat Salmanoğlu Committee Member
I certify that the information in this application is complete and accurate to the best of my knowledge and I am
going to do my responsibilities on time to complete this project successfully.
Name Surname Profession Signature Date Signature
Çağrı Kılıboz Project Manager
Fatih Ünver Senior Software Engineer
Seval Ünver Senior Software Engineer
COMASYS SPMP | 2

Change History
Version # Date Changes Description Change Request #
1.0 13/01/2015 Baseline Version Baseline Version of
SPMP is created.
COMASYS SPMP | 3

PREFACE
This Software Project Management Plan (SPMP) contains the overall management plan of the project
CONFERENCE MANAGEMENT SYSTEM (COMASYS) by giving extended information about the project.
COMASYS Project SPMP is prepared according to ISO/IEC/IEEE 16326 (First edition 2009-12-15), IEEE
Standard for Software Project Management Plans.
The primary audience is the project advisor, Prof. Dr. Onur Demirörs and member of the committee,
Murat Salmanoğlu.This SPMP document will serve as a guide for the employees, developing the product as
part of the project. Updates of this document will serve to record the progress of the project.
The purpose of this document is to specify the project plan to develop the COMASYS project. This plan
contains purpose, scopes, objectives, assumptions and constraints of the project. In addition to this, project
organization is defined. The document outlines a brief plan about how the project is to be shaped and also
includes the milestones and deliverables. As a summary, there are plans in this document which are
Estimation Plan, Staffing plan, Resource Acquisition Plan, Project Staff Training Plan, Project Work Plans,
Work Activities, Schedule Allocation, Resource Allocation, Budget Allocation, Procurement plan. Moreover,
assessment and control plans are demonstrated.
COMASYS SPMP | 4

LIST OF FIGURES
Figure 1. Water-Fall Process Model (Page 15)
Figure 2. Infrastructure Plan (Page 16)
Figure 3. Project Organization Schema (Page 19)
Figure 4. Database Schema (Page 21)
Figure 5. Work Breakdown Structure (Page 26)
Figure 6. Software Modules (Page 27)
COMASYS SPMP | 5

LIST OF TABLES
Table 1. Schedule Summary (Page 12)
Table 2. Project Stakeholders (Page 17)
Table 3. Advisory & Approval Committee Members (Page 17)
Table 4. Team Members (Page 18)
Table 5. Responsibilities In The Project (Page 19)
Table 6. Role Distributions Among Team Members (Page 25)
Table 7. Budget Allocation (Page 28)
Table 8. Decision Management (Page 32)
Table 9. Risk Impact (Page 34)
Table 10. Risk Probability (Page 34)
Table 11. Description of Risk Matrix (Page 34)
Table 12. Risk Level Matrix (Page 35)
Table 13. Risk 1 (Page 36)
Table 17. Metrics (Page 38)
Table 18. Cosmic Measurement Details Matrix (Page 40)
Table 19: Short Gantt Chart to see the Dates (Page 24)
COMASYS SPMP | 6

TABLE OF CONTENTS
PREFACE
LIST OF FIGURES
LIST OF TABLES
TABLE OF CONTENTS
1. OVERVIEW
1.1. Project Summary
1.1.1. Purpose, Scope, and Objectives
1.1.2. Assumptions and Constraints
1.1.3. Project Deliverables
1.1.4. Schedule and Budget Summary
1.2. Evolution of the plan
2. REFERENCE MATERIALS
3. DEFINITIONS, ACRONYMS, AND ABBREVIATIONS
4. PROJECT CONTEXT
4.1. Process model
4.2. Process improvement plan
4.3. Infrastructure plan
4.4. Methods, tools and techniques
4.5. Product acceptance plan
4.6. Project organization
4.6.1. External interfaces
4.6.2. Internal interfaces
4.6.3. Authorities and responsibilities
5. PROJECT PLANNING
5.1. Project initiation
5.1.1. Estimation Plan
5.1.2. Staffing plan
5.1.3. Resource Acquisition Plan
5.1.4. Project Staff Training Plan
5.2. Project Work Plans
5.2.1. Work Activities
5.2.2. Schedule Allocation
5.2.3. Resource Allocation
5.2.4. Budget Allocation
5.2.5. Procurement plan
6. PROJECT ASSESSMENT AND CONTROL
6.1. Requirements management plan
6.2. Scope change control plan
6.3. Schedule control plan
6.4. Budget control plan
6.5. Quality assurance plan
6.6. Subcontractor management plan
COMASYS SPMP | 7

6.7. Project closeout plan
7. PRODUCT DELIVERY
8. SUPPORTING PROCESS PLANS
8.1. Project supervision and work environment
8.2. Decision management
8.3. Risk management
8.4. Configuration management
8.5.1. Documentation
8.5.2. Communication and publicity
8.6. Quality assurance
8.7. Measurement
8.8. Reviews and audits
8.9. Verification and validation
9. Additional plans
10. End Matter
10.1. Annexes
10.1. ANNEX A: Cosmic Measurement of SRS v1.0
10.1. ANNEX B: Review Form
10.1. ANNEX C: GANTT CHART
COMASYS SPMP | 8

1. OVERVIEW
1.1. Project Summary
1.1.1. Purpose, Scope, and Objectives
COMASYS is a tool for organization and management of professional and scientific conferences.
COMASYS is independent and totally self-contained product that allows the users to access to conferences
and to manage them. Thus, it will not be integrated with other projects. It will be a replacement for commercial
conference management tools.
The COMASYS will be used extensively by the conference managers to administer and organize
academic conferences in for METU and provide an interface for academicians to contribute the managed
conferences. In other words, it helps the users to find information about the active conferences which is
provided by technical program committee of the related conference. In addition, COMASYS provides
opportunity for technical program committee to manage all administrative and organizational tasks of a
conference. To satisfy these objectives, a detailed software requirement specification (SRS) document is
prepared to capture the actual needs of the organization.
COMASYS allows the users to access to conferences and to manage them. The COMASYS shows
users information about the active conferences which is provided by Technical Program Committee(TPC) of
the related conference. In addition, the COMASYS provides opportunity for TPC to manage all administrative
and organizational tasks of a conference. These tasks are:
● To create, delete, update, and display conferences.
● To manage conference progress.
● To create, delete, and update accounts for uploading and reviewing abstracts and papers on the
system.
Also, COMASYS will offer a permanent ID for its users. The system will support multiple conferences at
the same time. With these permanent IDs, the users can access to all conferences or similar events
simultaneously. Since the system can be accessed via single permanent ID, the user does not need to
remember many passwords for multiple conference systems.
COMASYS SPMP | 9

This document is going to be offered to the university for approval. Based on the approved SRS
document, a technical software design document that describes the overall system architecture, software
modules and interaction among the modules is going to be prepared. This document will be baselined
internally after it satisfies the standards of our company for the following software development process.
Additionally, a formal test procedure (test plan and test case) is going to be offered and customer commitment
is going to be acquired. After the installation and delivery of user manual to the customer, the final product is
going to be verified using the approved test procedure.
The project scope is limited by the COMASYS contract between our company and METU. The system is
going be a standalone software program that does not interact with any of the existing METU softwares.
1.1.2. Assumptions and Constraints
Software development process should satisfies our company standards which is compatible with level
five CMMI. The approved budget for the project is 100.000 TL. Thus, the project cost should not exceed this
limit. Although it is not strict, the planned project termination date is 23.06.2015.
No maintenance activity is conducted after the delivery of the system. If it is requested, it will be a
subject of another contract. The employees assigned to our project have standard work hour policy of the
company which is 9 hour per weekdays.
There must be Internet connection. Also, the browser which is used for opening the COMASYS should
be HTML 5 compatible.
No system hardware will be provided. The infrastructure of the developed software shall be supplied and
maintained by the customer. The system shall work on Windows Server.
The COMASYS system will have .Net and MSSQL based software. For developing the software C#
language and MSSQL database will be used. The system shall support “.xls” and “.pdf” file formats for
uploading, downloading. The system shall encrypt the passwords of the users registered in the database with
MD5 encryption technique.
The system shall have capacity for up to 1 million user accounts. At any point in time, no more than 100
simultaneous users shall be able to make transactions (upload paper, download paper, view profile, edit
COMASYS SPMP | 10

profile etc.) for conferences in the system. The system shall a have capacity for up to 10.000 users to login
the system simultaneously for each conferences. The database capacity shall be limited to the server capacity
which is 3 TB. 95% of the responses shall be within 2 sec. User operation on data (for e.g. sorting of data in a
column) shall be in 5-19 seconds. Each page shall be loaded less than 4 seconds under normal network
conditions and system conditions. When user do not active on the system for 60 minutes, system shall
automatically logout the user from the system.
The main system will have a login history for recording system administrators’ activities on the system.
Administrators’ static IP addresses will be on the system and they could only login to the system from only
these IP addresses.
The project shall be distributed under GNU General Public License version 2 or any later version. GNU
General Public License is for using, changing and redistributing the software freely.
1.1.3. Project Deliverables
Project deliverable Delivery date Delivery location Delivery package
Software Project
Management Plan
(SPMP)
13.01.2015 METU Information
Technologies
Department
Soft copies of the document will be sent to
official e-mail address. Hard copies of the
document will be posted to delivery location.
Software
Requirements
Specification (SRS)
Technologies
Department
Updated SRS 24.03.2015 METU Information
Technologies
Department
Software Design
Document (SDD)
Technologies
Department
Updated SDD 07.05.2015 METU Information
Technologies
Department
COMASYS SPMP | 11

Test Plan and Test
Cases
Technologies
Department
Updated Test Plan
and Test Cases
Technologies
Department
User and Installation
Manuals
Technologies
Department
Final Product 23.06.2015 METU Information
Technologies
Department
Source codes and all executables will be
written on a DVD and posted to delivery
location.
1.1.4. Schedule and Budget Summary
Approved estimated budget is 100.000 TL. The budget is calculated according to schedule in 5.2.2.
Schedule Allocation and Cosmic Measurement Method. After calculation of the number of the staff required in
the project, costs are calculated as shown in 5.2.4. Budget Allocation and 6.4. Budget control plan.
A tentative schedule is as shown below in table 1. In addition to this, detailed schedule is given in the
5.2.2. Schedule Allocation and 6.3. Schedule control plan. The schedule covers 23 weeks.
Item Due Date
Submission of the Software Project Management Plan (SPMP) 13.01.2015
Project Start 17.02.2015
Submission of the Software Requirements Specification (SRS) 17.03.2015
Review of the SRS (with customer) 19.03.2015
Submission of the Updated SRS 24.03.2015
Submission of the Software Design Document (SDD) 05.05.2015
Review of the SDD (with customer) 07.05.2015
COMASYS SPMP | 12

Submission of the Updated SDD 12.05.2015
Test and Delivery of the Final Product 23.06.2015
Table 1. Schedule Summary
1.2. Evolution of the plan
This Project Management Plan is created and maintained using standard version control processes.
Page 2 of this document outlines Plan Approvers. Page 3 of this document outlines the Document History and
versions. The SPMP is going to be submitted to Approvers at 13.01.2015 as the schedule plan defined.
Schedule summary can be seen in 1.1.4. Schedule and Budget Summary. These sections should be updated
if there is a major change in one of the following subjects: scope,budget,schedule. The change should be
done in an integrated manner among the subjects.
2. REFERENCE MATERIALS
● 16326-2009 - ISO/IEC/IEEE International Standard Systems and Software Engineering,
http://standards.ieee.org/findstds/standard/16326-2009.html
● COSMIC Method v4.0 Measurement Manual, April 2014, http://www.cosmicon.com/
● Software Requirements Specifications(SRS V1.0) for COMASYS, Issue date 24.04.2014.
COMASYS SPMP | 13

3. DEFINITIONS, ACRONYMS, AND ABBREVIATIONS
Definitions
● User: The person who uses the COMASYS to view and register available conferences.
● Author: The person who uploads his/her abstract or paper for applied conferences in COMASYS.
● Technical Program Committee Chair: The person who can create and update conferences,
assign papers & abstracts to reviewers, accept and reject papers & abstracts in COMASYS.
● Program Committee Member: The person who can view, select, evaluate and download papers
& abstracts in COMASYS.
● System Administrator: The person who can manage logged bugs and enter information in
COMASYS.
Acronyms
● CFP: Cosmic Function Point
● COMASYS: Conference Management System
● COSMIC: Common Software Measurement International Consortium
● DM: Data Movement
● ETA: Estimated Time Allocation
● FP: Function Point
● FUR: Functional User Requirement
● HTML5: HyperText Markup Language
● IEEE: The Institute of Electrical and Electronics Engineers
● METU: Middle East Technical University
● MSSQL: Microsoft SQL Server which is a Database Management System
● OOI: Object of Interest
● PM: Project Manager
● SDD: Software Design Document
● SPMP: Software Project Management Plan
● SRS: Software Requirement Specification
● STP: Software Test Plan
● TPC: Technical Program Committee
COMASYS SPMP | 14

4. PROJECT CONTEXT
4.1. Process model
In the COMASYS projects, the waterfall software life cycle will be utilized. In the guide of the PMP,
firstly, all software requirements will be determined, documented for the customer. After the approval, system
level design process is conducted. The development activities will follow the company standards and will be a
realization of the prepared design document. Next, the developed software will be tested based on the
approved test documents. The water-fall process model of this project can be seen in Figure 1.
Figure 1. Water-Fall Process Model
4.2. Process improvement plan
During the course of the project, a progress and process evaluation meeting within the company will be
held. In this meeting, project members will assess the project, determining areas for improvement, and
discuss possible implementations for the improvements.
Progress meetings are done on every Friday at 9 AM in the meeting room 1. The participants are project
manager and all other internal project members.
COMASYS SPMP | 15

Steering group meetings are done on every Monday at 9 AM in the meeting room 1. The participants are
project manager, stakeholders and approval committee members.
These meetings are highly related with the problem resolution and timings of milestones. The general
flow of project and fulfillment percentages can be viewed from demo environment. The reviews are
determined during development process.
4.3. Infrastructure plan
The existing hardware capabilities (development computer, servers) of the company will be utilized. All
the required software for the development environment will be stored in a public repository for all developers
to access freely. The development and test servers will be separate. After the development activities finished,
developed product will be moved to the test servers. The test activities in the project will be done in isolated
test servers. The development and test servers are going to be Windows Servers. The development
environment is Visual Studio of Microsoft. Development and test databases are going to be Microsoft SQL
Server. The main infrastructure can be seen at Figure 2.
Figure 2. Infrastructure Plan
COMASYS SPMP | 16

4.4. Methods, tools and techniques
In the project, the software logic will be implemented in C# programming language. Since the application
will be web-based, user interface design will be realized in HTML5. The data will be stored MSSQL database
system.
All the processes in software life cycle will be compatible with CMMI level 5. A use case driven approach
will be followed. Software design will support UML design techniques and diagrams.
4.5. Product acceptance plan
The document based deliverables such as SRS, SDD will first reviewed by the customer. The final
versions of these documents should be approved by the customer. The formal test cases that is approved by
the customer will be used for the software verification. Testing methods for each requirement will be specified
in this document. The acceptance of the product will be based on the results of the formal tests.
4.6. Project organization
4.6.1. External interfaces
Project external interface consists of project stakeholders and approval committee members. Project
Stakeholders are defined in the Table 2 and Advisory & Approval Committee Members are defined in the
Table 3.
Project Stakeholders
Project Beneficiaries Conference organizers, Authors, Editors
Project Sponsor Middle East Technical University
Table 2. Project Stakeholders
Advisory & Approval Committee Members
Project Advisor Prof. Dr. Onur Demirörs
COMASYS SPMP | 17

Committee Member Murat Salmanoğlu
Table 3. Advisory & Approval Committee Members
4.6.2. Internal interfaces
The project is going to be developed by three members, who are software engineers. Each team
member has the equal responsibility during the project preparation and has at least one major role and more
than one minor role. Team members are defined in the Table 4.
A steering group meeting will be held every week to discuss progress, problems and issues. The
participants of this meeting are going to be the project stakeholders, advisory & approval committee members
and project manager. Project communication between external and internal interfaces is going to be done via
Project Manager. As described in 4.2. Progress Improvement Plan, steering group meetings are done on
every Monday at 9 AM in the meeting room 1.
There is going to be another meeting between internal team members and project manager. This
meeting is going to be progress meeting of this project and group members is going to discuss what is going
on so far. As described in 4.2. Process Improvement Plan, process meetings are done on every Friday at 9
AM in the meeting room 1.
Team Members
Software Engineer Çağrı Kılıboz
Software Engineer Fatih Ünver
Software Engineer Seval Ünver
Table 4. Team Members
Project organization schema can be seen at Figure 3. The member roles are defined in 4.6.3. Authorities
and responsibilities. Detailed role distributions among team members are given in 5.1.2. Staffing plan.
COMASYS SPMP | 18

Figure 3. Project Organization Schema
4.6.3. Authorities and responsibilities
The responsibilities in the project are shown in the Table 5. Detailed role distributions among team
members are given in 5.1.2. Staffing plan.
Role Description
Project Manager Project manager provides success coordination between team members and
project units. PM responsible for distribution of duties and roles. PM checks
whether schedule, cost and workflows are on the rails or not.
Backend Developer Backend developer develops the main program. The tasks are assigned by
Project Manager.
Frontend Developer Frontend developer is responsible for web design and web-based jobs like
interface and manipulations. The tasks are assigned by Project Manager.
Tester Tester tests general program segments and controls the requirements. Tester
informs the problems to project manager. Tester runs test cases as given in the
COMASYS SPMP | 19

test plan.
Database Specialist Database specialist creates the database schema and writes database scripts.
Table 5. Responsibilities In The Project
5. PROJECT PLANNING
5.1. Project initiation
5.1.1. Estimation Plan
Project estimation is done with Cosmic Measurement Tool by measuring SRS document. To find out
correct data groups, the database schema is created like the Figure 4.
COMASYS SPMP | 20

Figure 4. Database Schema
COMASYS SPMP | 21

Cosmic measurement details are given in Annexes 10.1. Annex A: COSMIC Measurement of SRS v1.0.
According to Cosmic measurement, the cosmic function point of this project is 123.
1. PROJECT MANAGEMENT 174 days 01.01.2015 23.06.2015
1.1. Planning 152 days 01.01.2015 01.06.2015
1.1.1. Software Project Management Plan
(SPMP)
13 days 01.01.2015 13.01.2015
1.1.2. Software Reqirement Specifications
(SRS)
63 days 14.01.2015 17.03.2015
1.1.3. Software Design Document (SDD) 49 days 18.03.2015 05.05.2015
1.1.4. Software Test Plan (STP) 27 days 06.05.2015 01.06.2015
1.2. Review & Control 21 days 16.01.2015 04.06.2015
1.2.1. Updated SPMP 7 days 18.03.2015 24.03.2015
1.2.2. Updated SRS 7 days 18.03.2015 24.03.2015
1.2.3. Updated SDD 2 days 06.05.2015 07.05.2015
1.2.4. Updated STP 3 days 02.06.2015 04.06.2015
1.2.5. Progress Meetings 23 hours 16.01.2015 19.06.2015
1.2.6. Steering group meetings 23 hours 19.01.2015 22.06.2015
1.3. Project Closeout 1 day 23.06.2015 23.06.2015
1.3.1. Final Report of Lessons Learnt 1 day 23.06.2015 23.06.2015
1.3.2. Product Delivery 1 day 23.06.2015 23.06.2015
1.3.3. Reassignment of Project Members 1 day 23.06.2015 23.06.2015
2. SYSTEM DESIGN 49 days 18.03.2015 05.05.2015
2.1. Backend Design 49 days 18.03.2015 05.05.2015
2.1.1. Database Design 10 days 18.03.2015 27.03.2015
2.1.2. Infrastructure Design 6 days 28.03.2015 02.04.2015
2.1.3. Technical Architecture 15 days 03.04.2015 17.04.2015
2.1.4. Activity Diagram of Program 9 days 18.04.2015 26.04.2015
2.1.5. Class Diagram of Program 9 days 27.04.2015 05.05.2015
COMASYS SPMP | 22

2.2. Frontend Design 33 days 03.04.2015 05.05.2015
2.2.1. User Interface Design on Photoshop 24 days 03.04.2015 26.04.2015
2.2.2. Enhancements on User Interface 9 days 27.04.2015 05.05.2015
3. SYSTEM DEVELOPMENT 31 days 06.05.2015 05.06.2015
3.1. Backend Development 31 days 06.05.2015 05.06.2015
3.1.1. Database Design Implementation 2 days 06.05.2015 07.05.2015
3.1.2. Software Program Implementation 29 days 08.05.2015 05.06.2015
3.1.2.1. User Module 6 days 08.05.2015 13.05.2015
3.1.2.2. Conference Module 6 days 14.05.2015 19.05.2015
3.1.2.3. Submission Module 6 days 20.05.2015 25.05.2015
3.1.2.4. Reviewer Module 6 days 26.05.2015 31.05.2015
3.1.2.5. Admin Module 5 days 01.06.2015 05.06.2015
3.2. Frontend Development 31 days 06.05.2015 05.06.2015
3.2.1. User Interface on HTML&CSS 31 days 06.05.2015 05.06.2015
4. SYSTEM TEST 17 days 06.06.2015 21.06.2015
4.1. Module & Subsystem Test 12 days 06.06.2015 17.06.2015
4.1.1. Unit Testing 4 days 06.06.2015 09.06.2015
4.1.2. User Interface Testing 2 days 10.06.2015 11.06.2015
4.1.3. System Functionality Testing 4 days 12.06.2015 15.06.2015
4.1.4. Defect Classification, Tracking & Metrics 2 days 16.06.2015 17.06.2015
4.2. Validation & Verification Test 5 days 17.06.2015 21.06.2015
4.2.1. System Integration Testing 1 day 17.06.2015 17.06.2015
4.2.2. System Acceptance Testing 1 day 18.06.2015 18.06.2015
4.2.3. System Validation 1 day 19.06.2015 19.05.2015
4.2.4. System Verification 1 day 20.06.2015 20.06.2015
4.2.5. Performance Testing 1 day 21.06.2015 21.06.2015
5. INSTALLATION 9 days 10.06.2015 23.06.2015
COMASYS SPMP | 23

5.1. Installation Planning & Implementation 9 days 10.06.2015 23.06.2015
5.1.1. User & Installation Manuals 6 days 10.06.2015 15.06.2015
5.1.2. Train Users 2 days 22.06.2015 23.06.2015
5.1.3. Deploy Software 1 day 23.06.2015 23.06.2015
6. SUPPORT SERVICES 1 year 10.06.2015 23.06.2016
6.1. Quality Assurance 9 days 10.06.2015 18.06.2015
6.1.1. Quality Plan 6 days 10.06.2015 15.06.2015
6.1.2. Quality Verification 3 days 16.06.2015 18.06.2015
6.2. Support 1 year 23.06.2015 23.06.2016
6.2.1. Support on Emailing Service 1 year 23.06.2015 23.06.2016
6.2.2. Bug Fixes on Report 1 year 23.06.2015 23.06.2016
Table 19: Short Gantt Chart to see the Dates
In order to estimate the project schedule, we used the COSMIC size measurement techniques. To make
a more precise estimation, we divide the software into modules. Next, we compared the companies previous
project performance. Using the data (COSMIC size measurements, entered timesheets, project schedules )
collected from the previous projects, we produced the above schedule. The frontend development of the
project is planned to be developed by 2 developers. Similarly, 2 employee shall perform test activities. It is
predicted that one person is enough to accomplish database related modules and development based on the
experience of the previous projects.
Although the collected data is reliable, there are some uncertainties of the projects because the project
team did not develop a similar product before. Therefore, we cannot be very sure of the performance but the
estimated calendar is flex enough to cover the possible errors in performance calculation.
The project calendar is planned to be updated at the start of each month. In these updates, the COSMIC
size measurements shall be re-made. The performance data of the past modules shall be calculated. The
newly calculated values are taken into account to estimate the remaining parts of the project.
COMASYS SPMP | 24

5.1.2. Staffing plan
No extra staff will be hired during this project. Three members of the core group will be enough for a
project of this scale which is each contracted.
Role Çağrı Kılıboz Fatih Ünver Seval Ünver
Project Manager ✓
Backend Developer ✓ ✓ ✓
Frontend Developer ✓ ✓
Tester ✓ ✓
Database Specialist ✓
Configuration Management Specialist ✓
Table 6. Role Distributions Among Team Members
5.1.3. Resource Acquisition Plan
No extra computer or server is needed because the system is going to be designed, implemented and
tested in company’s existing computers. The needed hardware on customer side is going to be provided by
customer itself. The other needed softwares are going to be acquired from open source softwares.
5.1.4. Project Staff Training Plan
Project staff will not be trained especially for or during this project, but naturally some new information
concerning for example the algorithm and the user interface has to be acquired in order to deliver a usable
product. Purpose of this project is to also learn and develop each participant's skills in software projects' task
fields.
COMASYS SPMP | 25

5.2. Project Work Plans
5.2.1. Work Activities
Work breakdown structure(WBS) can be seen in Figure 5 below. According to WBS, the project has 18
work activities (6 tasks and 12 subtasks) and 39 work packages.
Figure 5. Work Breakdown Structure
COMASYS SPMP | 26

Software has been divided into 5 modules to make it easier to implement. These modules are defined as:
1. User Module
2. Conference Module
3. Submission Module
4. Reviewer Module
5. Admin Module
So these modules have to be finished in Software Program Implementation work package.
Figure 6. Software Modules
5.2.2. Schedule Allocation
COMASYS project starts at 13/01/2015 and ends at 23/06/2015. The project schedule is given in Annex
C as Gantt Chart.
5.2.3. Resource Allocation
There is no additional resources needed in the project, the existing resources will be used and those are
enough the staff of the project.
COMASYS SPMP | 27

5.2.4. Budget Allocation
The total budget of the project is 100.000 TL. This price was calculated according to the COSMIC
Functional Measurement as shown Annex A. The hardware and software resources are belongings of
existing hardwares and softwares and no additional resource is required for the project. So the resources
required for the project other than human resource are not included in the budget.
The budget allocation is made based on each staff’s work hours. In calculation of staff costs an hourly
rate of each staff is assumed as 30 TL for standard work time. For project manager there is 6,60 TL extra
cost. Any staff can work 9 hours at business days.
Summary of cost allocation for project staffs is ilustrated below.
Weeks Work Std. Rate Cost
Çağrı Kılıboz 23 1035 hrs 36,60 TL/hr 37.900 TL
Fatih Ünver 23 1035 hrs 30 TL/hr 31.050 TL
Seval Ünver 23 1035 hrs 30 TL/hr 31.050 TL
Total Cost 100.000 TL
Table 7: Budget Allocation
5.2.5. Procurement plan
There is not a procurement plan for the project.
6. PROJECT ASSESSMENT AND CONTROL
6.1. Requirements management plan
The project requirements may subject to change if the customer needs changes or a technical difficulty
is encountered that has a major effect during the development. Change request that made after the approval
of the SRS document will be evaluated in a joint meeting. The impacts of the change request is evaluated
using size measurement techniques (COSMIC). Its effects on the other critical factors such as budget,
COMASYS SPMP | 28

schedule will be computed using the traceability matrix. In the case of delay or increase in cost, written
approval of the both parties will be seeked. Upon approval, the change request for SRS will be reflected to
related documents and products.
6.2. Scope change control plan
The scope control will be performed in terms of approved project schedule. Any activities that is not in
the approved project schedule will be considered out of scope. If such activities are found or requested, it’s
effects on the project is evaluated with the same approach in section 6.1. In the case of delay or increase in
cost, written approval of the both parties will be seeked. Upon approval, the change request for project
schedule will be reflected to related documents and products.
6.3. Schedule control plan
Project manager will be the main responsible for schedule control mechanism. He shall perform project
progress meeting with the participations of all project members in every two week to keep track of the project
schedule. In this meeting, each team members should report to the project manager about the followings:
- tasks that have been completed
- remaining task that yet to be completed
- where they should be according to project schedule
- Opinions about the whether the remaining work is doable according to schedule
Additionally, basic functionality tests shall be performed after the developers notify that a functionality is
completed. The project manager will assess the project progress and perform an earned value analysis
based on the functionality test reports and progress meetings.
Schedule Performance Index (SPI) = Earned Value (EV)/Planned Value (PV)
If SPI is less than 0.9 (10% margin is due to schedule buffer), he will need to take precautions to prevent
a major slippage in the schedule. he shall try to determine the root cause of the delay problem. If possible, he
shall try to eliminate the problems. Additionally, he and the developer responsible for the delay will try to
increase the efficiency of the work done. In this stage, the time devoted for each task may be rearranged to
stay in the schedule. Any update in the schedule will be announced to project stakeholders and members..
COMASYS SPMP | 29

When the above procedure cannot fix the schedule problem, the project manager should inform the
customer immediately and negotiate with the customer about the possible delay. He will reason with the
customer about the causes of the possible delay. If an agreement is not achieved, the project manager is to
prepare an overtime schedule plan and the team members are to do overwork.
If SPI is greater than 1.0, project is “AHEAD” of schedule. In this scenario, the project manager may use
his initiative to re-arrange the work schedule to devote more time for risky tasks. Any update in the schedule
will be announced to project stakeholders and members..
6.4. Budget control plan
SPMP Budget Control Plan specifies the control mechanisms to be used to measure the cost of work
completed, compare planned cost to budgeted cost. Our budget is not much complex since there is no tax
and rent for our development team. Therefore only budget control is related to salaries. We will control
manually if the total salary is as it is expected during 23 weeks. If an unexpected cost item arises, it will be
evaluated according to budget control plan.
Project manager will be the main responsible for budget control mechanism. He shall perform cost-
performance analysis after each level 3 work activity in WBS is completed with the following earned value
approach.
Cost Performance Index (CPI) = Earned Value (EV)/Actual Cost (AC)
In the case that cost performance index is below 0.9, the causes of unbudgeted spent will be
questioned. The project manager shall investigate the problem and take necessary action to reduce the
remaining cost of the project. If it cannot be achieved, the unbudgeted amount will be compensated from the
company’s other resources. The project budget allocation plan is also updated according to the changes
applied in budget allocation
COMASYS SPMP | 30

6.5. Quality assurance plan
The project needs to be managed and delivered under certain constraints.
Traditionally, these constraints have been listed as scope, time and cost. The
time constraint refers to the amount of time available to complete a project. The
cost constraint refers to the budgeted amount available for the project. The
scope constraint refers to what must be done to produce the project’s end result.
These are also referred as the “Project Management Triangle”, where each side
represents a constraint. Now, if one side of the triangle change then other sides
of the triangle change automatically. For example if we change the scope of the
project then it affects the both the time and cost of the project. Therefore, we will use performance tests and
acceptance tests for the overall quality of our product. Plan will be not to go further unless these tests give
good results. The detailed quality assurance plan is going to be prepared later and its verification is going to
be done.
6.6. Subcontractor management plan
In the scope of this project, there will be no subcontractor.
6.7. Project closeout plan
All the details about the post-mortem debriefings, report on the lessons learnt, project objectives and the
milestones achieved are going to be mentioned in a final report. To closeout the project all delivery items have
to be delivered correctly. The final software and documents should be delivered with electronic version. After
the project deliveries are done, the staff is going to be reassigned to another project.
7. PRODUCT DELIVERY
Final product is going to be delivered in 23.06.2015 with electronic copy. The installation on customer
server is going to done at the same time. After the installation on customer server, whenever a professional
help is requested by the users of the system, we will support the project for the first year without any cost for
COMASYS SPMP | 31

customer. However, after the first year, fix cost will be applied for support and the cost will be determined
later. To learn about closeout plan, look at the 6.7. Project closeout plan.
8. SUPPORTING PROCESS PLANS
8.1. Project supervision and work environment
All development and test activities will be performed in METU technopolis office of the company.
The project supervisioning and tracking task will be managed using companies own tracking interface
namely JIRA. Project manager defines each work task with allocated time and assign these duties to the
project members in JIRA. Project members will discuss task related topics under the defined task in JIRA.
Each developer is responsible for entering the worklog at the end of each day for every work task assigned to
them. Project manager shall keep track of the performance of each employee through JIRA.
Additionally, the company uses SAP to track budget of the projects. Each developer is required to enter
timesheets for the assigned WBS elements at the end of each week.
8.2. Decision management
The following table categorizes decision needed circumstances and explain the decision making
methodology:
Need for decision Decision parties Decision methodology Outcome
Technical trade-off Project manager,
Developers
Alternatives are verbally
discussed in a technical
meeting
One of the
alternatives has been
chosen
Reported software or
hardware problem needing
resolution
Project manager,
Developers
Alternatives are verbally
discussed in a technical
meeting
One of the
alternatives has been
chosen
Action needed in response
to risk
Customer, project
manager
Effects of the risk are
discussed and possible
resolution approaches are
Risk resolution is
offered
COMASYS SPMP | 32

presented.
Delays in project schedule Customer, project
manager
Causes of the delay are
discussed and possible
resolution approaches are
presented.
Solution to the
project schedule is
offered or project
schedule is updated
Table 8: Decision Management
8.3. Risk management
Organizational Structure
There is not a risk specialist in the organization for the project. Project Manager will create a risk
board and be the head of risk board and risk board will be open to all project members.
Project Manager will be responsible for keeping and managing the risk management plan.
Risk Identification
All project members can identify and submit risk for the project. Risk identifiers shall submit a risk
expression, risk condition and consequences of the risk.
Risk Analysis
Risk analysis will be conducted by risk board. Identified risk will be analyzed and the probability
of their occurrence and the consequences of the risk will be identified. The issues that will be considered for
determining degree of the consequences of the risk are as follows.
- Effect on project schedule
- Cost of required effort
- Overhead costs
- Penalty Costs
There are five levels defined for the risks based on the impact of risk on project cost.
COMASYS SPMP | 33

Level Impact on Total Project Cost
1 [0,1]
2 [1,3]
3 [3,5]
4 [5,10]
5 [10,100]
Table 9: Risk Impact
Risks are also categorized according to occurrence probability.
Level Impact on Total Project Cost
1 % [0,20]
2 % [20,40]
3 % [40,60]
4 % [60,80]
5 % [80,100]
Table 10: Risk Probability
Risk level is assessed according to the impact level and occurrence probability level. Risk level matrix
is used to identify risk priority. There are three levels of risk priorities.
Risk Level Impact on Total Project Cost
Low
The risks, in this category, contain minimum risk, and it may be
continued with these activities as planned.
Medium
The risks, in this category, contain some level risk, and it should be
considered what can be done to manage risk.
High
The risks, in this category, are highly likely to occur, and the risk
management approaches shall be done to mitigate risk to the
acceptable level.
Table 11: Description of Risk Levels
COMASYS SPMP | 34

Risk Level
Probability of
Risk
Level 5 Medium Medium High High High
Level 4 Low Medium Medium High High
Level 3 Low Medium Medium Medium High
Level 2 Low Low Medium Medium Medium
Level 1 Low Low Low Low Medium
Level 1 Level 2 Level 3 Level 4 Level 5
Impact of
Risk
Table 12: Risk Level Matrix
Risk Handling
Response plans will be implemented to handle risks. Identified risks will be reviewed by the risk
board and necessary actions will be implemented to mitigate risk.
Risks
The risk identified for COMASYS project is given in this section of document.
Risk 1
Definition Project time is limited and project has high priority, there may not be enough
time to correct misunderstandings and faults.
Probability Level 3
Impact Level 4
Priority Medium
Mitigation Approaches - Project group meetings should be conducted to monitor progress.
COMASYS SPMP | 35

- The possible extra time for the project may be defined and this time
may use for correcting misunderstandings and faults.
Tracker
Table 13: Risk 1
Risk 2
Definition Personnel assigned to the project may not have enough skill to complete
task
Probability Level 1
Impact Level 4
Priority Low
Mitigation Approaches - In case of necessity, new training should be arranged.
Tracker
Table 14: Risk 2
Risk 3
Definition Project budget may not be enough to complete project
Probability Level 2
Impact Level 5
Priority Low
Mitigation Approaches - Budget plan should be reviewed to control all of the activities are
included in the plan.
- All of the changes in the requirements should be assessed for
budget plan.
Tracker
Table 15: Risk 3
Risk 4
Definition Since the person in project is limited and there is not too much people in
COMASYS SPMP | 36

project, if any person in project can not complete any step, whole project
may be delayed.
Probability Level 3
Impact Level 5
Priority Medium
Mitigation Approaches - Some other people may find for exceptional situations.
Tracker
Table 16 Risk 4
8.4. Configuration management
Project manager shall be responsible for identifying configuration items, creating baselines throughout
the project and performing controlled change control on identified configuration items. The change requests to
any of the configuration item will be evaluated by the project manager. If the requested change is approved,
the project manager will perform the followings per change request:
- Log the source of change request
- Log analysis of change request
- Review and verify the changes applied
- Baseline the configuration item with versioning
- Notify the related parties (developers, customers)
8.5. Information Management
There is not an information management specialist on this project. Project manager and project
members will arrange information management.
8.5.1. Documentation
In this section, the information that how documentation will generate and review will specify. There are
four document will prepared in the project. The first documentation is SPMP. It will be prepared until
COMASYS SPMP | 37

13.01.2015 via MS Office Word program. Secondly, SRS will be prepared until 17.03.2015 via MS Office
Word program.Therefore, the review of SRS will be prepared until 24.03.2015 via MS Office Word program.
Thirdly, SDD according to updated SRS will be prepared until 05.05.2015 via MS Office Word program.
Therefore, the review of SDD will be prepared until 07.05.2015. Finally, user and installation manuals will be
prepared until 15.06.2015 via MS Office Word program.
8.5.2. Communication and publicity
All the documents are available for all project members and advisor. Also, there will be public server
including documents for all project members and advisor.
8.6. Quality assurance
There is not a special quality assurance group for the project. The members of the project will also be
the quality assurance group. Quality assurance group is responsible for reviewing SRS, SPMP, and SDD
documents by using review form which is given in Annex B and review findings will be evaluated through joint
meetings.
8.7. Measurement
The following table contains the list of metrics that will be collected throughout the project (metric, unit,
collection plan)
Metric Definition Unit Collection Plan
Effort per task The effort spent on a
task defined in JIRA
Staff hours Daily using JIRA work
log
Work time Number of hours the
employee spent on the
project in a week
Staff hours Weekly using SAP and
approved by the project
manager
Project Size Total number of
COSMIC function points
Function points Measured after each
major milestone using
COSMİC
COMASYS SPMP | 38

Actual cost The money spent for the
project activities
TL Calculated monthly
Table 17: Metrics
CPI and SPI values will be computed based on the collected metrics. Thus, it is a critcal factor to keep
track of the progress in the project. These metrics shall be utilized in the project closeout plan to asses the
overall performance of the projects. The metrics shall show the what are the good and bad decision made in
the projects and make us obtain a lesson learnt report.
8.8. Reviews and audits
By referring 4.6.2. Internal Interfaces, a steering group meeting will be held every week to discuss
progress, problems and issues. The participants of this meeting are going to be the project stakeholders,
advisory & approval committee members and project manager. Project communication between external and
internal interfaces is going to be done via Project Manager.
There is going to be another meeting between internal team members and project manager. This meeting is
going to be progress meeting of this project and group members is going to discuss what is going on so far.
As described in 4.2. Process Improvement Plan, process meetings are done on every Friday at 9 AM in the
meeting room 1.
8.9. Verification and validation
The validation of final product is done by Approval Committee Members. They are going to try the
system functionalities and interfaces. The found bugs will be fixed before installation on customer server. The
validation is going to be done according to the contract and SRS document.
After finalizing the project, product installation will take place in METU. Main parts of the system
installation are database part and web application parts. We estimated that only a couple of hours is needed
for installation of the product. The system is going to be verified by METU program coordinator.
COMASYS SPMP | 39

9. Additional plans
There is no additional plan.
10. End Matter
10.1. Annexes
10.1. ANNEX A: Cosmic Measurement of SRS v1.0
FUR: Functional User Requirement
FP: Function Point
DM: Data Movement
OOI: Object of Interest
CFP: Cosmic Function Point
FUR#
FP# FP
D
M
DM Description OOI Data Group CFP
1 1 User Signup
E User enters information
User Generic
Info
username,
name, surname,
password,
emailAddress,
occupation, title,
gender,
address,
affiliation,
birthDate,
expertiseAreas
6
W Write user information into
DB
User Generic
Info
username,
name, surname,
password,
emailAddress,
occupation, title,
gender,
address,
affiliation,
COMASYS SPMP | 40

birthDate,
expertiseAreas
X Send activation email Activation
activationToken,
userId, activated
E
User clicks activation link in
email
Activation
Request
activation
request
W Activate user Activation
activationToken,
userId, activated
X Show notification Notification
error/success
notification
2 2 User Login
E
User enters his login
credentials Login Info
username,
password
4
R
Reads user credentials from
DB Login Info
username,
password
W Save session token Session
sessionToken,
userId
X Show error message Notification
error/success
notification
3 3 User Logout E Clicking Logout Logout Request logout request 3
W Delete session token Session
sessionToken,
userId
X Show success message Notification
error/success
notification
4 4 Show Profile
E Clicking My Profile link
Show Profile
Request
show profile
request
3
R Reads user credentials from
DB
User Generic
Info
username,
name, surname,
password,
emailAddress,
occupation, title,
gender,
address,
COMASYS SPMP | 41

affiliation,
birthDate,
expertiseAreas
X Profile information displayed
User Generic
Info
username,
name, surname,
password,
emailAddress,
occupation, title,
gender,
address,
affiliation,
birthDate,
expertiseAreas
5 5 Edit Profile
E User edits profile info
User Generic
Info
username,
name, surname,
password,
emailAddress,
occupation, title,
gender,
address,
affiliation,
birthDate,
expertiseAreas
3
W
Updates user credentials in
DB
User Generic
Info
username,
name, surname,
password,
emailAddress,
occupation, title,
gender,
address,
affiliation,
birthDate,
expertiseAreas
COMASYS SPMP | 42

error/success
notification
6 6 View Avaliable
Conferences
E
Clicking Home or Welcome
link
View Available
Conferences
Request
view available
conferences
request
3
R Read available conferences
Conference
Name
conferenceId,
name
X Display conferences
Conference
Name
conferenceId,
name
7 7 View Applied
Conferences
E
Clicking My Conferences
link
View Applied
Conferences
Request
view applied
conferences
request
3
R Applied conferences
Conference
Name
conferenceId,
name
X List of applied conferences
Conference
Name
conferenceId,
name
8 8 Register to
conferences E Selected conference
Conference
Name
conferenceId,
name
3
W
Save Registered
Conference
Applied
Conferences
Info
userId,
conferenceId
error/success
notification
9 9 Upload Abstract
E
Author enters abstract data
and selects it Abstract Info
type, title,
addressLink,
conferenceId,
authors
3
W
It writes new abstract to the
db Abstract Info
type, title,
addressLink,
conferenceId,
authors
X Shows success message Notification error/success
COMASYS SPMP | 43

notification
10 10 Upload Paper
E
Author enters paper data
and selects it Paper Info
type, title,
addressLink,
conferenceId,
authors
3
W It writes new paper to the db Paper Info
type, title,
addressLink,
conferenceId,
authors
X Shows success message Notification
error/success
notification
11, 26 11 View Abstracts List
E
User selects conference
name
Conference
Name
conferenceId,
name
3
R Read uploaded abstracts Abstract Info
type, title,
addressLink,
conferenceId,
authors
X List uploaded abstracts Abstract Info
type, title,
addressLink,
conferenceId,
authors
11, 27,
29, 30,
31, 32
12 View a Submission
Item
E Select an abstract or paper Submission ID
submissionItemI
d
3
R
Read submission address
link
Submission
Address
submissionItemI
d, addressLink
X Show it in pdf viewer PDF file PDF file
12, 25 13 View Papers List
E
User selects conference
name
Conference
Name
conferenceId,
name
3
R Read uploaded papers Paper Info type, title,
addressLink,
conferenceId,
COMASYS SPMP | 44

authors
X List uploaded papers Paper Info
type, title,
addressLink,
conferenceId,
authors
13, 14 14 View results of
submission E
User clicks abstact result
link or paper result link
See Result
Request
see result
request
3
R Read status
Submission
Status
submissionItemI
d, status
X Show status of submission
Submission
Status
submissionItemI
d, status
15 15 Create conference
E Request Create Conference
Request Create
Conference
request create
conference
4
E Conference Data Conference Info
name, acronym,
subject, location,
startDate,
endDate,
contactPersonN
ame,
contactPersonE
mail,
sessionsTable,
sponsors,
submissionEnd
Date,
submissionAcce
ptanceEndDate
W Conference Data Conference Info name, acronym,
subject, location,
startDate,
endDate,
contactPersonN
ame,
COMASYS SPMP | 45

contactPersonE
mail,
sessionsTable,
sponsors,
submissionEnd
Date,
submissionAcce
ptanceEndDate
X Confirmation/Error message Notification
error/success
notification
16 16 View Managed
Conferences
E
Request Manage
Conference
Request
Manage
Conference
request manage
conference
3
R Read Conferences
Conference
Name
conferenceId,
name
X Display Conferences
Conference
Name
conferenceId,
name
16, 28 17 View a conference
detail E
Request to view a
conference
Request View
Conference
request view
conference
3
R Read Conference Details Conference Info
name, acronym,
subject, location,
startDate,
endDate,
contactPersonN
ame,
contactPersonE
mail,
sessionsTable,
sponsors,
submissionEnd
Date,
submissionAcce
ptanceEndDate
COMASYS SPMP | 46

X Display Conference Details Conference Info
name, acronym,
subject, location,
startDate,
endDate,
contactPersonN
ame,
contactPersonE
mail,
sessionsTable,
sponsors,
submissionEnd
Date,
submissionAcce
ptanceEndDate
17 18 Update Conference
Details
E Updated Conference Data Conference Info
name, acronym,
subject, location,
startDate,
endDate,
contactPersonN
ame,
contactPersonE
mail,
sessionsTable,
sponsors,
submissionEnd
Date,
submissionAcce
ptanceEndDate
3
W Write new conference data Conference Info name, acronym,
subject, location,
startDate,
endDate,
contactPersonN
COMASYS SPMP | 47

ame,
contactPersonE
mail,
sessionsTable,
sponsors,
submissionEnd
Date,
submissionAcce
ptanceEndDate
error/success
notification
18 19 Assign Reviewers to
Conference E Request assign reviewers
Request assign
reviewers
request assign
reviewers
7
R Read Roles Roles Info
userId,
roleIdName
R Read User Info User Name
userId, name,
surname
X Display users User Name
userId, name,
surname
W Write assigned members
Committee
Members Info
uniqueId, userId,
conferenceId
X Send Mail
Notification
Email notification email
error/success
notification
19 20 Assign Papers to
Reviewers E Request assign papers
Request assign
papers
request assign
papers
9
R Read Committee Members
Committee
Members Info
uniqueId, userId,
conferenceId
R Read User name User Name
userId, name,
surname
COMASYS SPMP | 48

R Read Submission papers
Submission
Name
submissionItemI
d, type, title
R Read Paper id Paper Id
submissionItemI
d, paperId
X Display Submission papers
Submission
Name
submissionItemI
d, type, title
X
Display Committee
Members User Name
userId, name,
surname
W Write assigned papers
Paper
Reviewers Info
uniqueId, userId,
submissionItemI
d, paperId
error/success
notification
20 21 Assign Abstract to
Reviewers E Request assign abstracts
Request assign
abstracts
request assign
abstracts
9
Committee
Members Info
uniqueId, userId,
conferenceId
R Read User name User Name
userId, name,
surname
R Read Submission abstracts
Submission
Name
submissionItemI
d, type, title
R Read abstract id Abstract Id
submissionItemI
d, abstractId
X
Display Submission
abstracts
Submission
Name
submissionItemI
d, type, title
X
Display Committee
Members User Name
userId, name,
surname
W Write assigned abstracts
Abstract
Reviewers Info
uniqueId, userId,
submissionItemI
d, abstractId
X Confirmation/Error message Notification error/success
COMASYS SPMP | 49

notification
21, 22,
23, 24
22 Accept/Reject
Abstract or Paper
E
Accept or Reject
abstract/paper request
Accept or reject
abstract/paper
request
accept or reject
abstract/paper
request
2
W Write submission item status
Submission
Status
submissionItemI
d, status
27, 29,
35
23 Download
abstract/paper E Request download
Request
download
request
download
3
R Read address link
Submission
Address
submissionItemI
d, addressLink
X Download document PDF file PDF file
28 24 View assigned
conferences list
E
"My Conferences as
Reviewer" link is pressed
View Assigned
Conference
Request
view assigned
conference
request
4
Committee
Members Info
userId,
conferenceId
R Read assigned conferences
Conference
Name
conferenceId,
name
X
Display assigned
conferences
Conference
Name
conferenceId,
name
29 25 View assigned
abstracts list
E
View Assigned Abstracts link
is pressed
View assigned
abstracts
request
view assigned
abstracts
request
4
R Read abstract reviewes
Abstract
Reviewers Info
uniqueId, userId,
submissionItemI
d, abstractId
R Read submission item info
Submission
Name
submissionItemI
d, type, title
X
Display assigned abstracts
list
Submission
Name
submissionItemI
d, type, title
30 26 View assigned
papers list E
View Assigned Papers link is
pressed
View assigned
paper request
view assigned
paper request
4
COMASYS SPMP | 50

R Read paper reviewers
Paper
Reviewers Info
uniqueId, userId,
submissionItemI
d, abstractId
R Read submission item info
Submission
Name
submissionItemI
d, type, title
X Display assigned papers list
Submission
Name
submissionItemI
d, type, title
31 27 Display submitted
abstracts list by the
author E
“View abstracts” button is
clicked
Display Author
Abstracts
Request
display author
abstracts
request
4
R Read submitted items
Submitted Item
Info
userId,
submissionItemI
d
R Read submission items
Submission
Name
submissionItemI
d, type, title
X
Display all submitted
abstracts of the author
Submission
Name
submissionItemI
d, type, title
32 28 Display submitted
papers list by the
author E
“View papers” button is
clicked
Display Author
Papers Request
display author
papers request
4
R Read submitted items
Submitted Item
Info
userId,
submissionItemI
d
X Read submission items
Submission
Name
submissionItemI
d, type, title
E
Display all submitted papers
of the author
Submission
Name
submissionItemI
d, type, title
33, 34 29 Evaluate
abstract/paper
E
Selects a grade and clicks
“Grade” button Grade Info
userId,
submissionItemI
d,
abstractId/paper
Id, grade
4
COMASYS SPMP | 51

W
Write grade of
abstracts/papers Grade Info
userId,
submissionItemI
d,
abstractId/paper
Id, grade
W
Calculate overall grade
again
Submission
Overall Grade
submissionItemI
d, overallGrade
error/success
notification
36 30
View Logged Bugs E
Clicking Manage Logged
Bugs
Manage Logged
Bugs request
manage logged
bugs request
3
R Read logged bugs Logs Info
logId, date,
status, detail
X Write logs Logs Info
logId, date,
status, detail
36 31 Change problem
status E Enter new problem status Logs Info
logId, date,
status, detail
3
W Delete logged problem Logs Info
logId, date,
status, detail
error/success
notification
37 32 Enter New
Information to update
Committee Members
and System
Administrators E Clicking "Upload File" XLS file XLS file
4
W
Write new committee
members
Committee
Members Info
userId,
conferenceId
W Write new admins
System Admin
Info userId, ip, status
X Success message Notification
error/success
notification
COMASYS SPMP | 52

TOTAL
CFP
123
Table 18. Cosmic Measurement Details Matrix
10.1. ANNEX B: Review Form
COMASYS SPMP | 53

10.1. ANNEX C: GANTT CHART
Figure: Gantt Chart for Work Activity 1 and 2.
COMASYS SPMP | 54

COMASYS SPMP | 55

Software Project Management Plan

Recommended

Recommended

More Related Content

What's hot

What's hot (20)

Similar to Software Project Management Plan

Similar to Software Project Management Plan (20)

More from Seval Çapraz

More from Seval Çapraz (20)

Recently uploaded

Recently uploaded (20)

Software Project Management Plan