SOFTWARE PROJECT MANAGEMENT PLAN (SPMP)

Online Secure Document Sharing and Management System Team 41

Team Members
Emre Genco YAKAR mit Caferi Elif Serim Hilmi Emre LKER

Acquirer: Dr. zlem Albayrak Consultant: Hamdi Murat YILDIRIM

Change History Table

Project Name Online Secure Document Sharing and Management System Version 1.0 Person Responsible Emre Genco YAKAR mit CAFER Elif SERM Hilmi Emre LKER Date 03.04.2011 Changes Team 41 SPMP.doc was created

ii

Signature Page

Project Advisor Hamdi Murat Yldrm

Signature

Senior Project Manager zlem Albayrak

Signature

Team Members Emre Genco Yakar mit Caferi Elif Serim Hilmi Emre lker

Signature

iii

Preface
The purpose of this document is to specify the project plan to develop the Online Secure Document Sharing and Management System (OSDSMS). The primary audience is the project advisor, Dr. Hamdi Murat Yldrm, and our senior project manager, Dr. zlem Albayrak. This document outlines a brief plan about how the project is to be shaped and also includes the milestones and deliverables. Updates of this document will serve to record the progress of the project.

Table of Contents
iv

Change History Table............................................................................................ii Signature Page..................................................................................................... iii Preface.................................................................................................................. iv Table of Contents..................................................................................................iv List of figures....................................................................................................... vii List of tables....................................................................................................... viii 1 Overview.............................................................................................................1 1.1 Project Summary...........................................................................................1 1.1.1 Purpose, Scope and Objectives...............................................................1 1.1.2 Assumptions and Constraints..................................................................1 1.1.3 Project Deliverables ...............................................................................3 1.1.4 Schedule and Budget Summary..............................................................3 1.2 Evolution of the plan.....................................................................................5 2 References.......................................................................................................... 5 3 Definitions...........................................................................................................5 4 Project Organization............................................................................................6 4.1 External Interfaces........................................................................................6 4.2 Internal Structure..........................................................................................6 4.3 Roles and Responsibilities.............................................................................6 5 Managerial process plans....................................................................................7 5.1 Startup plan................................................................................................. 7 5.1.1 Estimation plan.......................................................................................7 5.1.2 Staffing plan..........................................................................................10 5.1.3 Resource acquisition plan.....................................................................11 5.1.4 Project staff training plan......................................................................11 5.2 Work Plan....................................................................................................11 5.2.1 Work Activities......................................................................................11 5.2.2 Schedule Allocation...............................................................................26 v

5.2.3 Resource Allocation...............................................................................26 5.2.4 Budget Allocation..................................................................................26 5.3 Control Plan.................................................................................................27 5.3.1 Requirements Control Plan....................................................................27 5.3.2 Schedule Control Plan...........................................................................27 5.3.3 Budget Control Plan..............................................................................27 5.3.4 Quality Control Plan..............................................................................27 5.3.5 Reporting Plan.......................................................................................28 5.3.6 Metrics Collection Plan..........................................................................28 5.4 Risk Management Plan................................................................................28 5.5 Closeout Plan...............................................................................................29 6 Technical Process Plans.....................................................................................29 6.1 Process Model.............................................................................................29 6.2 Methods, Tools, and Techniques.................................................................30 6.3 Infrastructure Plan.......................................................................................31 6.4 Product Acceptance Plan.............................................................................32 7 Supporting Process Plans..................................................................................32 7.1 Configuration Management Plan.................................................................32 7.2 Verification and Validation Plan...................................................................32 7.3 Documentation Plan....................................................................................32 7.4 Quality Assurance Plan................................................................................32 7.5 Review and Audits.......................................................................................32 7.6 Problem Resolution Plan..............................................................................32 7.7 Subcontractor Management Plan................................................................32 7.8 Process Improvement Plan..........................................................................32 8 Additional Plans.................................................................................................32

vi

List of figures
Figure 1 - Cocomo Object Point Calculation............................................................9

vii

List of tables
Table 1 Cocomo Function Point Calculation.........................................................8 Table 2 Cocomo Function Point Calculation 2...........................................8 Table 3 - Cocomo Object Point Calculation...........................................................10 Table 4 - Staffing plan..........................................................................................11 Table 5 - Table WPS for Meeting with Customer - Initial Plan...............................13 viii

Table 6 - WPS for Meeting with Acquirer - Initial Plan...........................................14 Table 7 - WPS for Preparation of Initial Plan........................................................15 Table 8 - WPS for Revision of Initial Plan..............................................................16 Table 9 - WPS for Meeting with Customer - Requirement Analysis.......................16 Table 10 - WPS for Meeting with Acquirer - Requirement Analysis.......................17 Table 11 - WPS for Requirement Elicitation..........................................................18 Table 12 - WPS for Analysis of Requirements.......................................................18 Table 13 - WPS for Preparation of SRS.................................................................19 Table 14 - WPS for Revision of SRS.......................................................................20 Table 15 - WPS for Meeting with Customer SPMP..............................................21 Table 16 - WPS for Meeting with Acquirer SPMP................................................21 Table 17 - WPS for Managerial Process Plan.........................................................22 Table 18 - WPS for Technical Process Plan...........................................................23 Table 19 - WPS for Supporting Process Plan.........................................................23 Table 20 - WPS for Preparation of SPMP...............................................................24 Table 21 - WPS for GUI Design.............................................................................25 Table 22 - WPS for Database Design....................................................................25 Table 23 - Resource Allocation.............................................................................26 Table 24 Metrics Collection Plan.........................................................................28 Table 25 Risk Management Plan........................................................................29

ix

1 Overview
1.1 Project Summary
1.1.1 Purpose, Scope and Objectives

The purpose of Software Project Management Plan (SPMP) is to describe what processes and plans are and will be done while preparing the documents such as Initial Plan and SRS, establishing the software and after installation of the program. Online secure document sharing and management system lets us store, organize, view, and modify files with just an Internet connection. The software application that will organize the documents, members, basic information, changes, decisions, data backup, document search, document collaboration, securely share documents and activities of an association. During the project development, different types of software programs are going to be used in order to satisfy all the customer needs. The purpose of this project is to develop an online and secure document sharing and management system which allows secure and efficient document distribution and sharing between all users. It provides storage, sharing and security capabilities such as message privacy, integrity and authenticity with the help of cryptographic algorithms and related protocols. Only authorized users can access specific documents and produce digital signatures for them and also can share with other users. In this project we are planning to have file upload-download, encryption, decryption, creating digital signature and certificate such as x509 in a single web site. It will be a web-based project which enables user to share documents with each other. It will be an in-line system which means that each operation will be done in server-side. Nobody will be able to deny what he/she sends or receives by the help of digital signature. The site will do key management with the use of protocols and algorithms. It will also keep the log records. There will be two user types; admin and members. Admin will give members some rights to access specific documents. Admin will be able to add, remove the documents and members can only share and access specific documents.

1.1.2

Assumptions and Constraints

1.1.2.1 Assumptions

Online Secure Document Sharing and Management System is going to be developed in light of the specifications which are described by the following organization- standards for the application cryptographic algorithms and protocols
X.509 ISO/IEC 9594-8 The Directory: Public-key and attribute certificate

frameworks

ETSI TS 102 176-1 V2.0.0 Electronic Signatures and Infrastructures (ESI);

1

Algorithms and Parameters for Secure Electronic Signatures; Part 1: Hash functions and asymmetric algorithms IEEE P1363 (2000): "Standard Specifications for Public-Key Cryptography". ANSI X9.62, Public Key Cryptography for the Financial Services Industry, The Elliptic Curve Digital Signature Algorithm (ECDSA), 2005. The project staff will be experienced with standard X.800 security architect and RFC 2828 in order to understand security notations , During project the recommendations of NESSIE and CRYPTREC will be considered for cryptographic techniques and issues such as confidentiality, data integrity, and authentication. There are four team members dealing with the project The customers changeable requirements will be integrated into the project During the development of this project Bouncy Castle Crypto APIs will be used All project members is enrolled CTIS496 Data Security Computing Course
1.1.2.2 Constraints 1.1.2.2.1 Resource Constraints

MySQL, is a free relational database management system runs as a server providing multi-user access to number of databases. MS Visio and MS Project 2007 will be used for necessary document for our project. Microsoft .NET platform and underlined technologies will be used during development of the project. Socket (Network) Programming will be used.

1.1.2.2.2 Environmental Constraints

Online Secure Document Sharing and Management System works on a system which consists o Pentium4 1.5 GHZ processor or better o 1 GB RAM o 512 kbps Internet Connection or better. o Windows Installer version 3.1 or later. o IE 6.0, Google Chrome, Mozilla Firefox, Safari or better. Deliverables should only be submitted in exact dates. The usage rights of deliverables belong to CTIS department. Hosting, Domain and Server costs will be paid annually.

1.1.2.2.3 Delivery Constraints

1.1.2.2.4 Budgetary Constraints

1.1.3 Project Deliverables

Initial Plan SRS SPMP SRS after quality control SDD Prototype: SCOPE Prototype: DEMO

25.02.2011 20.03.2011 03.04.2011 07.04.2011 23.04.2011 30.04.2011 11.05.2011

1.1.4

Schedule and Budget Summary

1.2 Evolution of the plan

Project planning is a continuous process. The team members should review their plan when:

making progress reports; new risks are identified; problems occur.

Regarding problems, team members may arrange a meeting with advisor. They may figure it out by themselves.

References
Team-41 Initial Plan IEEE Std 1058-1998

Definitions
SPMP: Software Project Management Plan SRS: Software Requirements Specification SDD: Software Design Description COCOMO: Constructive Cost Model N/A: Not Available
5

 IE: Internet Explorer MS: Microsoft

OSDSMS: Online Secure Document Sharing and Management System

Project Organization

4.1 External Interfaces

The external interfaces for this project are the members of CTIS459 Team41 and our advisor Hamdi Murat Yldrm.

4.2 Internal Structure

The development team consists of mit Caferi, Hilmi Emre lker, Elif Serim and Emre Genco Yakar.

4.3 Roles and Responsibilities

Name Elif Serim

Contact Information
serim@ug.bilkent.edu.tr

Roles
Project Manager Software Developer Database Designer

mit Caferi

caferi@ug.bilkent.edu.tr

Software Developer GUI Designer Tester

Hilmi Emre lker

h_ulker@ug.bilkent.edu.tr

Software Developer GUI Designer Database Designer

Emre Genco Yakar

genco@ug.bilkent.edu.tr

Software Developer Tester Database Designer

Project Manager: Project manager is responsible for planning and organizing project development process. Software Developer: Software developer is responsible for implementation. Database Designer: Database designer is responsible for design the database tables, their relationships and connections. GUI Designer: GUI designer is responsible for design a user friendly graphical user interfaces depend on customer needs. Tester: Tester is responsible for testing defects and reports them.

Managerial process plans

5.1 Startup plan

5.1.1 Estimation plan COCOMO Function Point Calculation Information Item User Information Inputs Elements Name, Surname, Username, Password, E-Mail, Address, Phone, Birth date. Username, Password Document Name Doc Id, Doc Name, Doc Size, Doc for OS, Doc for Branch Total 8

Authentication Inputs Document Engine Inputs Documents Information Inputs

2 1 5

Document Category Inputs Document Inputs Survey System Inputs Mail System Inputs Design Page Layout Inputs Manage Survey Inputs Manage News Inputs

Category ID, Category Name, Category Priority Document ID, Document begin date, Document end date Vote e-mail addresses, Message. subject,

3 3 1 2 3 5 1 7

Size, Font, Design template Survey Question and 4 options News text field

CSS Files Registration Query Login Query Search Product Query Edit Document Info Query Manage Doc. Category Query Manage User Query General Management Query User/Dealer Query Management

Main.css, admin.css, style.css

3 1 1 1 1 1 1 6 1 3

Configuration Query

Table 1 Cocomo Function Point Calculation

Items External Inputs (EI)

Simple

Average Comple x 40x3=120 5x4=20 0x6=0

Total 140 0 74 25 0

External Outputs (EO) 0x4=0 0x5=0 0x7=0 External Inquiries (EQ) 18x3=54 5x4=20 0x6=0 External Interface Files (EIF) 5x5=25 0x7=0 0x10=0 Internal Logical Files (ILF) 0x7=28 0x10=0 0x15=0 Total Unadjusted Function Point (UFP) = 239 Table 2 Cocomo Function Point Calculation 2

Unadjusted function point (UFP) = 239 The project size is measured as 239 function points. 124 function points is PHP. 115 function points is Java. LOC = UFP * LFAC (Java is predefined as 30) LOC= (115*30) + (124*15) =3450+1860=5310 KLOC = LOC / 1000 =5310/ 1000 8

= 5.310 Effort Applied = 2.4 * 7.17 1.05 = 13.8535313 Person Months Average Staffing = 13.8535313 / 4 = 3.5 months = 3.46338283 FSP (Full-Time Software Personnel) Product Design Effort = 0.16 * 3.46338283 = 0.554141253 FSP Product Design Schedule = 0.19 * 3.46338283 = 0.658042738 FSP

COCOMO Object Point Calculation

Figure 1 - Cocomo Object Point Calculation

Screens / Reports Document Sharing E-mail sending Admin Panel

Simple screen* 1 12 5 17

Medium screen*2 10 3 12

Difficult screen*3 21 7 15

Reports 0

Total 107

4(simple) 32 6(simple) 94 Object Point = 233

Table 3 - Cocomo Object Point Calculation

We will not make 3GL component. NOP = OP*((100-15)/100) NOP = 233*((100-15)/100)19 NOP = 198.05 Effort= NOP/PROD Our team members experience is nominal so divide NOP to 13, Effort=198.05/13 Effort =15.2346154 Person Month Average Staffing=15.2346154 / 4 (team members) Average Staffing =3.80865385 FSP

5.1.2 Staffing plan Based on initial estimates, the project will require the human resources shown in the table below. Human Type Resource Work(Hours) 500 Working Period 18.02.201127.07.2011 Software Engineer 500 18.02.201127.07.2011 Requirements Design Implementation 10-40 TL Project Phase All Affordable Rate 30-60 TL Hourly

Project Manager

10

Testing Installation Software Developer/Tester 500 18.02.201127.07.2011 Requirements Design Implementation Testing Installation Software Developer/Tester 500 18.02.201 1-27.07.2011 Requirements Design Implementation Testing Installation 10-40 TL 10-40 TL

Table 4 - Staffing plan

5.1.3 Resource acquisition plan

TBD
5.1.4 Project staff training plan

TBD

5.2 Work Plan

5.2.1 Work Activities

Major work activities are as shown in the table below: 0.0. Online Secure Document Sharing and Management System 1.0. Project Management 1.1. Initial 1.1.1. 1.1.2. 1.1.3. 1.1.4. 1.2. SPMP 1.2.1. 1.2.2. 1.2.3. 1.2.4. 1.2.5. Plan Meeting with Customer Meeting with Acquirer Preparation of Initial Plan Revision of Initial Plan Meeting with Customer Meeting with Acquirer Managerial Process Plan Technical Process Plan Supporting Process Plan
11

2.0. 3.0.

4.0.

5.0.

5.4.

1.2.6. Preparation of SPMP 1.2.7. Revision of SPMP Configuration Management 2.1. Version Control Risk Management 3.1. Identification of Risk Factors 3.2. Analysis of Risk Factors 3.3. Prioritization of Risk Factors 3.4. Monitor of Risk Factors Requirement Analysis 4.1. Meeting with Customer 4.2. Meeting with Acquirer 4.3. Requirement Elicitation 4.4. Analysis of Requirements 4.5. Preparation of SRS 4.6. Revision of SRS Design 5.1. Meeting with Customer 5.2. Meeting with Acquirer 5.3. GUI Design Data Design 5.4.1. Data Structure Design 5.4.2. Database Design 5.5. Object Design 5.6. Preparation of SDD 5.7. Revision of SDD

6.0. Presentation 6.1. Implementation of Prototype 6.2. Preparation of Presentation 7.0. Training 7.1. Database Management System Training 7.2. ASP.NET and C# Training 8.0. Implementation 8.1. Development of DB 8.2. Coding 9.0. Testing 9.1. Unit / Integration Testing 9.2. System Testing 9.3. Acceptance Testing 10.0. Quality Assurance 10.1. Verification 10.2. Validation

12

WORK PACKAGE SPECIFICATION Work Activity/Task Number Work Activity/Task Name Work Activity/Task Description Estimated Duration Resources Needed Personnel Skills Emre Genco YAKAR,Hilmi Emre lker,mit Caferi,Elif Serim Prepared questions for understanding the requirements of project more effectively. MS Word Computer 1.1.1 Meeting with Customer Meeting with the customer for defining the Requirements of project. 4 hours

Software Hardware

Product(s) to be generated when N/A completed: Predecessor Work Activity/Tasks Successor Work Activity/Tasks Risks N/A 1.1.2. Meeting with Acquirer Customer may not be available at the meeting time because of unpredictable reasons. Completion Criteria When the customer meeting times. approves the

Table 5 - Table WPS for Meeting with Customer - Initial Plan

WORK PACKAGE SPECIFICATION Work Activity/Task Number Work Activity/Task Name Work Activity/Task Description 1.1.2. Meeting with Acquirer Meeting with the acquirer for defining the requirements of initial plan 13

documents. Estimated Duration Resources Needed 1 hour

Personnel Skills

Emre Genco YAKAR,Hilmi Emre lker,mit Caferi,Elif Serim Prepared questions for understanding the requirements of project more effectively. MS Word Computer

Software Hardware

Product(s) to be generated when N/A completed: Predecessor Work Activity/Tasks Successor Work Activity/Tasks Risks N/A 1.1.3. Preparation of Initial Plan Acquirer may not be available at the meeting time because of unpredictable reasons. Completion Criteria When the acquirer meeting times. approves the

Table 6 - WPS for Meeting with Acquirer - Initial Plan

WORK PACKAGE SPECIFICATION Work Activity/Task Number Work Activity/Task Name Work Activity/Task Description Estimated Duration Resources Needed Personnel Skills Emre Genco YAKAR,Hilmi Emre lker,mit Caferi,Elif Serim Knowledge for using needed software. 14 1.1.3. Preparation of Initial Plan Meeting with the customer for defining the requirements of project. 4 days

Software

MS Word, MS Project, MS Visio

Hardware

Computers for each team members

Product(s) to be generated when Initial plan document completed: Predecessor Work Activity/Tasks 1.1.1. Meeting with Customer 1.1.2. Meeting with Acquirer Successor Work Activity/Tasks Risks Completion Criteria 1.1.4. Revision of Initial Plan N/A

The document must be completed according to the template given by acquirer.. Table 7 - WPS for Preparation of Initial Plan
WORK PACKAGE SPECIFICATION

Work Activity/Task Number Work Activity/Task Name Work Activity/Task Description

1.1.4 Revision of Initial Plan Revision of document according to some criteria like consistency, traceability, format etc. 1 day

Estimated Duration Resources Needed Personnel Skills Software Hardware

Emre Genco YAKAR,Hilmi Emre lker,mit Caferi,Elif Serim Knowledge for using needed software. MS Word, MS Project, MS Visio Computer

Product(s) to be generated when N/A completed: Predecessor Work Activity/Tasks Successor Work Activity/Tasks Risks 1.1.3. Preparation of Initial Plan 4.0. Requirement Analysis

Soft-copy of the Initial Plan can not

15

sent to acquirer because of Moodle or internet problems.

Completion Criteria

The document must be submitted to acquirer. Table 8 - WPS for Revision of Initial Plan
WORK PACKAGE SPECIFICATION

Work Activity/Task Number Work Activity/Task Name Work Activity/Task Description

4.1 Meeting with Customer Meeting with the customer for defining the requirements of project in more detail. 4 hours

Estimated Duration Resources Needed

Personnel Skills

Emre Genco YAKAR,Hilmi Emre lker,mit Caferi,Elif Serim Prepared questions for understanding the requirements of project more effectively. MS Word, MS Project, MS Visio Computer

Software Hardware

Product(s) to be generated when N/A completed: Predecessor Work Activity/Tasks Successor Work Activity/Tasks Risks N/A 4.2. Meeting with Acquirer Customer may not be available at the meeting time because of unpredictable reasons. When the customer meeting times. approves the

Completion Criteria

Table 9 - WPS for Meeting with Customer - Requirement Analysis

WORK PACKAGE SPECIFICATION Work Activity/Task Number 4.2 16

Work Activity/Task Name Work Activity/Task Description Estimated Duration Resources Needed Personnel Skills

Meeting with Acquirer Meeting with the acquirer for defining the requirements of SRS documents. 1 hour

Emre Genco YAKAR,Hilmi Emre lker,mit Caferi,Elif Serim Prepared questions for understanding the requirements of SRS more effectively MS Word Computer for each team members

Software Hardware

Product(s) to be generated when N/A completed: Predecessor Work Activity/Tasks Successor Work Activity/Tasks Risks 4.1. Meeting with Customer 4.3. Requirement Elicitation Acquirer may not be available at the meeting time because of unpredictable reasons When the acquirer meeting times approves the

Completion Criteria

Table 10 - WPS for Meeting with Acquirer - Requirement Analysis

WORK PACKAGE SPECIFICATION Work Activity/Task Number Work Activity/Task Name Work Activity/Task Description Estimated Duration Resources Needed Personnel Skills Software Emre Genco YAKAR,Hilmi Emre lker,mit Caferi,Elif Serim Prepared requirements of the system MS Word 17 4.3 Requirement Elicitation Obtaining the requirements of system with all team members. 3 days the

Hardware

1 Computer

Product(s) to be generated when Obtained requirements of the system completed: Predecessor Work Activity/Tasks Successor Work Activity/Tasks Risks Completion Criteria 4.2. Meeting with Acquirer 4.4. Analysis of Requirements N/A When the all team members are agreed with the requirements of the system.

Table 11 - WPS for Requirement Elicitation

WORK PACKAGE SPECIFICATION Work Activity/Task Number Work Activity/Task Name Work Activity/Task Description Estimated Duration Resources Needed Personnel Skills Emre Genco YAKAR,Hilmi Emre lker,mit Caferi,Elif Serim Prepared set of requirements of the system by each team members separately. MS Word 1 Computer 4.4 Analysis of Requirements Detailed understanding of system and customer needs 3 days

Software Hardware

Product(s) to be generated when Requirements of the system completed: Predecessor Work Activity/Tasks Successor Work Activity/Tasks Risks Completion Criteria 4.3. Requirement Elicitation 4.5. Preparation of SRS N/A When the all team members customer are agreed with requirements of the system. and the

Table 12 - WPS for Analysis of Requirements

18

WORK PACKAGE SPECIFICATION Work Activity/Task Number Work Activity/Task Name Work Activity/Task Description 4.5 Preparation of SRS Preparing the SRS documents which include functional, non functional requirements, constraints and UML diagrams. 10 days

Estimated Duration Resources Needed Personnel Skills Software Hardware

Emre Genco YAKAR,Hilmi Emre lker,mit Caferi,Elif Serim Knowledge of using needed software. MS Word, MS Visio, GUI Design Tool, Configuration Management Tool Computers for each team members

Product(s) to be generated when SRS document completed: Predecessor Work Activity/Tasks Successor Work Activity/Tasks Risks Completion Criteria 4.4. Analysis of Requirements 4.6. Revision of SRS N/A The document must be completed according to the template given by acquirer.

Table 13 - WPS for Preparation of SRS

WORK PACKAGE SPECIFICATION Work Activity/Task Number Work Activity/Task Name Work Activity/Task Description 4.6 Revision of SRS Revision of SRS according to some criteria like consistency, traceability, format etc. 4 days

Estimated Duration Resources Needed Personnel

Emre Genco YAKAR,Hilmi Emre lker,mit 19

Caferi,Elif Serim Skills Software Hardware Knowledge of using needed software and checklist MS Word, MS Visio, GUI Design Tool, Tortoise SVN, Printing services Computers for each team members

Product(s) to be generated when Improved SRS document according to completed: checklist Predecessor Work Activity/Tasks Successor Work Activity/Tasks Risks Completion Criteria 4.5. Preparation of SRS 1.2. SPMP Soft-copy of the SRS cannot send to acquirer because of Moodle or internet problems The document must be submitted to acquirer and customer.

Table 14 - WPS for Revision of SRS

WORK PACKAGE SPECIFICATION Work Activity/Task Number Work Activity/Task Name Work Activity/Task Description Estimated Duration Resources Needed Personnel Skills Software Hardware Emre Genco YAKAR,Hilmi Emre lker,mit Caferi,Elif Serim Prepared questions which are related with SPMP MS Word Computer 1.2.1. Meeting with Customer Meeting with the customer for SPMP 1 hour

Product(s) to be generated when N/A completed: Predecessor Work Activity/Tasks Successor Work Activity/Tasks Risks 4.6. Revision of SRS 1.2.2. Meeting with Acquirer Customer may not be available at the meeting time because of unpredictable reasons. 20

Completion Criteria

When the customer approves the meeting times.

Table 15 - WPS for Meeting with Customer SPMP

WORK PACKAGE SPECIFICATION Work Activity/Task Number Work Activity/Task Name Work Activity/Task Description Estimated Duration Resources Needed Personnel Skills Emre Genco YAKAR,Hilmi Emre lker,mit Caferi,Elif Serim Prepared questions for understanding the requirements of document more effectively. MS Word Computer 1.2.2 Meeting with Acquirer Meeting with the acquirer for defining the requirements of SPMP document. 1 hour

Software Hardware

Product(s) to be generated when N/A completed: Predecessor Work Activity/Tasks Successor Work Activity/Tasks Risks Completion Criteria 1.2.1. Meeting with Customer 1.2.3. Managerial Process Plan Acquirer may not be available at the meeting time because of unpredictable reasons. When the acquirer approves the meeting times.

Table 16 - WPS for Meeting with Acquirer SPMP

WORK PACKAGE SPECIFICATION Work Activity/Task Number Work Activity/Task Name Work Activity/Task Description 1.2.3 Managerial Process Plan Preparing managerial process plan by determining project start up plan, work plan and control plan. 4 days

Estimated Duration Resources Needed

21

Personnel Skills

Emre Genco YAKAR,Hilmi Emre lker,mit Caferi,Elif Serim Knowledge about analysis, budget needed software. function point calculation and

Software Hardware

MS Word, MS Project , Tortoise SVN 2 Computers

Product(s) to be generated when Managerial Process Plan document completed: Predecessor Work Activity/Tasks Successor Work Activity/Tasks Risks Completion Criteria 1.2.1. Meeting with Customer 1.2.3. Managerial Process Plan N/A When the managerial process plan part of the template document is completed at 70%.

Table 17 - WPS for Managerial Process Plan

WORK PACKAGE SPECIFICATION Work Activity/Task Number Work Activity/Task Name Work Activity/Task Description 1.2.4 Technical Process Plan Preparing technical process plan by determining process model, methods, tools, techniques and acceptance plan. 1 days

Estimated Duration Resources Needed Personnel Skills

Emre Genco YAKAR,Hilmi Emre lker,mit Caferi,Elif Serim Knowledge about methodologies and environment. MS Word, Tortoise SVN 2 Computers development development

Software Hardware

Product(s) to be generated when Technical Process Plan document completed: Predecessor Work Activity/Tasks Successor Work Activity/Tasks 1.2.3. Managerial Process Plan 1.2.5. Supporting Process Plan 22

Risks Completion Criteria

N/A When the technical process plan part of the template document is completed at 70%.

Table 18 - WPS for Technical Process Plan

WORK PACKAGE SPECIFICATION Work Activity/Task Number Work Activity/Task Name Work Activity/Task Description 1.2.5 Supporting Process Plan Preparing supporting process plan by determining configuration management, validation and verification, documentation and problem resolution plan etc. 2 days

Estimated Duration Resources Needed Personnel Skills

Emre Genco YAKAR,Hilmi Emre lker,mit Caferi,Elif Serim Knowledge about validation and management.. MS Word, Tortoise SVN 2 Computers the verification, configuration

Software Hardware

Product(s) to be generated when Supporting Process Plan document completed: Predecessor Work Activity/Tasks Successor Work Activity/Tasks Risks Completion Criteria 1.2.4. Technical Process Plan 1.2.6. Preparation of SPMP N/A When the supporting process plan part of the template document is completed at 70%.

Table 19 - WPS for Supporting Process Plan

WORK PACKAGE SPECIFICATION Work Activity/Task Number 1.2.6 23

Work Activity/Task Name Work Activity/Task Description

Preparation of SPMP Merging 70% completed managerial process plan, technical process plan and supporting process plan. Then preparing the uncompleted parts and making some changes if necessary. 3 days

Estimated Duration Resources Needed Personnel Skills Software Hardware

Emre Genco YAKAR,Hilmi Emre lker,mit Caferi,Elif Serim Knowledge about the needed software. MS Word, MS Project, Tortoise SVN Computers for each team members

Product(s) to be generated when SPMP document completed: Predecessor Work Activity/Tasks Successor Work Activity/Tasks Risks Completion Criteria 1.2.5. Supporting Process Plan 1.2.7 Revision of SPMP N/A The document must be completed according to the template given by acquirer.

Table 20 - WPS for Preparation of SPMP

WORK PACKAGE SPECIFICATION Work Activity/Task Number Work Activity/Task Name Work Activity/Task Description Estimated Duration Resources Needed Personnel Skills Software Emre Genco YAKAR,Hilmi Emre lker,mit Caferi,Elif Serim Knowledge about using design tool and GUI principles GUI Design Tool, Tortoise SVN 24 5.3 GUI Design Preparing GUI screens according to requirements and GUI principles. 3 days

Hardware

2 Computers

Product(s) to be generated when GUI screens completed: Predecessor Work Activity/Tasks Successor Work Activity/Tasks Risks Completion Criteria 5.2. Meeting with Acquirer 5.4. Data Design Requirement with high importance order can be changed by customer. Before starting the data structure design part, GUI screens must be completed

Table 21 - WPS for GUI Design

WORK PACKAGE SPECIFICATION Work Activity/Task Number Work Activity/Task Name Work Activity/Task Description Estimated Duration Resources Needed Personnel Skills Emre Genco YAKAR,Hilmi Emre lker,mit Caferi,Elif Serim Knowledge about DB tables, relations, normalization and using needed software MS Word, Tortoise SVN
Computers for each team members

5.4.2 Database Design Determining the DB relations between them. 3 days tables and

Software Hardware

Product(s) to be generated when Database design document completed: Predecessor Work Activity/Tasks Successor Work Activity/Tasks Risks Completion Criteria 5.4.1. Data Structure Design 5.5. Object Design Requirement with high importance order can be changed by customer. Before starting the object design, database design part must be completed.

Table 22 - WPS for Database Design

25

5.2.2

Schedule Allocation

Analyzing by the Gannt chart, schedule allocation can be reviewed.

5.2.3

Resource Allocation

Needed Skill: Knowledge about the using of software programs by the team members are enough.

Work Activity
Initial Plan Requirement Analysis SPMP Design Presentation Implementation Testing Final Product and Documentation

Needed Resources
Computers, MS Word, MS Visio, MS Project, soft copy Computers, MS Word, MS Visio, GUI Design Tool, Printing Services Computers , Ms Word, MS Project, Printing Services MS Word, MS Visio, GUI Design Tool, Printing Services MS Visual Studio 2010, SQL server 2008, MS Power point MS Visual Studio 2010, SQL server 2008 MS Word, JIRA, MS Visual Studio 2010, SQL server 2008 Source code, DB, Documents

Table 23 - Resource Allocation

5.2.4

Budget Allocation

Although final product delivers to CTIS Department, this project is educational project for team members at Bilkent University CTIS department. Therefore there is no allocated budget for Project.

26

5.3 Control Plan

5.3.1 Requirements Control Plan

All of the requirements have been specified in the Software Requirements Specification. When changes are to be made in the requirements after the SRS has been released, the changes shall be brought to the attention of the Team 41 and discussed. Any changes that are to be made will be with the prior approval of the Team 41 and only if feasible and permissible within the constraints of the project mentioned in section 1.1.2. Once the changes have been made to the SRS document, an updated version of the SRS shall be released. All changes in requirements will be reflected to the SRS and SDD. The page in which the changes are done will be written on the change history table description part.

5.3.2

Schedule Control Plan

Schedule of the project was prepared by Gantt chart. By analyzing milestones of the project from Gantt chart, all team members will fulfill their responsibilities. If there is a minor delay at the milestones of the project, each team member will work extra hours to reach the determined milestones. If there is a major delay at the milestones of the project, meeting with the team members will be done. At this meeting, some precautions will be taken and if necessary, Gantt chart will be updated according to deliver time of the final product at the determined date by the CTIS department.If the work scheduled in section 1.1.4 is gets behind, Team 41 is ready to spend extra time on the project to make up for the lost time and deliver the final project on time.

5.3.3

Budget Control Plan

The cost of work completed, measured in team member man hours, will be compared to the budgeted cost to determine whether the actual cost remains consistent with the planned cost. Examination of the actual cost will occur after the implementation of each iteration.

5.3.4 Quality Control Plan

This subsection will describe the mechanisms to be used for measuring and controlling quality of work processes and products. Audits Audits of work processes will not be conducted on a schedule. However, they may be requested by one of the following: Elif SERM (Team 41 Project Manager) Hamdi Murat YILDIRIM (Consultant) Reviews
27

Regularly scheduled reviews of work products will take place. Defect/issue tracking After testing, verification and validation; bugs, defects and faults founded at the source code and requirements of the project will be kept in the change request tool - JIRA. By analyzing the change requests from JIRA, which defect should solve will be determined firstly. After solving the defects of the product, this information is kept in JIRA also. By the way, coordination between the team members will be obtained. Also, at the some phases of the project, customer can post change requests to team members over JIRA. By conducting risk management, project will be realized on determined time and scope.

5.3.5

Reporting Plan

Each of preliminary versions of all the documents and updates and status reports will be sent and discussed with the advisor and upon approval the approved document will be circulated to the other members of Team 41. At the major deliverables date, deliverables will be delivered to the acquirer and customer. For acquirer, deliverables will be uploaded to the Moodle.
5.3.6 Metrics Collection Plan

Metric Name
Project Size Effort Development Time Cost Defects and bugs Duration

Metric Unit
COCOMO Man - months Months TL Error Hours/ days/ months

Table 24 Metrics Collection Plan

5.4 Risk Management Plan

This section will observe the project risks that may arise in the future, and also specify the techniques used to manage these project risks.

Risk

Probability

Effect Serious Serious

Strategy Share the team members work among the project team. Conform to the plan of project to deliver the requirements in exact dates. 28

Failure of one team member High in 459 courses Passing deadlines Low

Server breakdown

High

Serious

Keep waiting a second server to keep the system work. Block all the incoming attacks to the system. Do search about the problem that occurred in the system via the Internet. Always be in contact with the customer in order to review the system according to the requirements. Get a SSL Certificate to make the system reliable. Make provision against hacking techniques such as SQL injection.

Lack of information during High development of the software Change of the Requirements Low

Tolerable

Serious

Stolen of information

the

user Moderate

Serious

Table 25 Risk Management Plan

5.5 Closeout Plan

This section describes the nature of the activities that will be used to close out the project when it is completed. Upon termination of the entire project for any reason, whether due to the objectives being met or some other reason, there is a number of closure activities that will be performed before the project is considered closed. These activities are captured in the following: Communicate decision, identify remaining work, deliver released software, get customer approvals, release or reassign team and return or release vendor or customer materials.

Technical Process Plans

6.1 Process Model

The software process model can be defined as a simplified description of a software process, presented from a particular perspective. Each stage of the software process is identified and a model is then employed to represent the inherent activities associated within that stage. There are several software process models which demonstrate the different approaches to software development. Each process model follows a particular life cycle in order to ensure success in process of software development. One such approach used in Software Development is "The Waterfall Model" which is going to be used in this project. In this model, the whole process of software development is divided into separate process phases. These are: Requirement Specifications phase, Software Design, Implementation and Testing & Maintenance. The output of the Requirement Specifications phase is the projects SRS which is delivered at 20.03.2011. The projects SDD will be delivered at 23.04.2011, which is one of the outputs of
29

Software Design, Implementation phase. Also Prototype of the project and a demonstration of it will be executed at 11.05.2011. All these phases are cascaded to each other so that second phase is started as and when defined set of goals are achieved for first phase. All the methods and processes undertaken in Waterfall Model are more visible.

6.2 Methods, Tools, and Techniques

Development Methodology: The Waterfall Development Methodology is going to be used in this project which has following advantages: It is a linear model and simple to be implemented. The amount of resources required to implement this model is minimal. Documentation is produced at every stage of the waterfall model development. This makes the understanding of the product designing procedure simpler. Programming Languages: C# programming language is going to used during software development. It is a multiparadigm programming language encompassing imperative, declarative, functional, generic, object-oriented (class-based), and component-oriented programming disciplines. It was developed by Microsoft within the .NET initiative and later approved as a standard by Ecma. It is simple, modern, general-purpose, object-oriented programming language. Tools and Techniques: Microsoft Visual Studio will be used during development process of our web application which is an integrated development environment (IDE) from Microsoft. It can be used to develop console and graphical user interface applications along with Windows Forms applications, web sites, web applications, and web services in both native code together with managed code for all platforms supported by Microsoft Windows, Windows Mobile, Windows CE, .NET Framework. MySQL is going to be used in the project which is free a relational database management system that runs as a server providing multi-user access to a number of databases. MySQL is written in C and C++ and works on works on many different system platforms, including AIX, BSDi, FreeBSD, HP-UX, eComStation, i5/OS, IRIX, Linux, Mac OS X, Microsoft Windows etc. Microsoft. NET platform will be used during development of the project. The .NET Framework is a software framework for Microsoft Windows operating systems. It includes a large library, and it supports several programming languages which allow language interoperability). The .NET library is available to all the programming languages that .NET supports. IBM Rational Software Architect will be used for drawing necessary UML diagrams for our project. RSA is a comprehensive modeling and development environment that uses the Unified Modeling Language (UML) for designing architecture for C++ and Java 2 Enterprise Edition (J2EE) applications and web services. Microsoft Word will be used for deliverable documents for our project.

30

Techniques, Standards OSDSMS is going to be developed in light of the specifications which are described by the following organization- standards for the application cryptographic algorithms and protocols
X.509 ISO/IEC 9594-8 The Directory: Public-key and attribute certificate

frameworks ETSI TS 102 176-1 V2.0.0 Electronic Signatures and Infrastructures (ESI); Algorithms and Parameters for Secure Electronic Signatures; Part 1: Hash functions and asymmetric algorithms IEEE P1363 (2000): "Standard Specifications for Public-Key Cryptography". ANSI X9.62, Public Key Cryptography for the Financial Services Industry, The Elliptic Curve Digital Signature Algorithm (ECDSA), 2005. The project staff will be experienced with standard X.800 security architect and RFC 2828 in order to understand security notations. The recommendations of NESSIE and CRYPTREC will be considered for cryptographic techniques and issues such as confidentiality, data integrity, and authentication. Bouncy Castle Crypto APIs will be used during the development of this project.

6.3 Infrastructure Plan

OSDSMS project infrastructure includes software and hardware infrastructures. Software Infrastructure OSDSMS be developed with C# programming language and Socket (Network) Programming will be used during development. MySql version 5.1.3 will be used as database in OSDSMS. Microsoft Visual Studio will be used as an integrated development environment (IDE) from Microsoft. Graphical User Interface will be created on Microsoft Visual Studio by the help of Adobe Photoshop and Fireworks. Hardware Infrastructure There will be two servers on OSDSMS. First one will be web server and the second one will be for database server. Both of these servers will be on PCs with Windows OS. One PC will be used for Repository. SVN will be set up to this PC and all team will have accounts to reach the repository. The minimum requirements of the PCs are: Windows Xp(x86) with Service Pack 3 Pentium4 1.5 GHZ processor or better
31

3GB of available hard disk space. 1 GB Ram Net framework 3.5 Sp 1. 512 kbps Internet Connection or better.

6.4 Product Acceptance Plan

This section specifies the plan for acquirer acceptance of the deliverable work products generated during the OSDSMS project. The deliverables which are stated in the section 1.1.3 are consists of documentation and the software products. All the documentation will be reviewed by both PM and rest of the project team. All deliverables will be reviewed and approved by the consultant of the project H.Hamdi Yldrm and acquirer Dr.zlem Albayrak. After testing at the end of development process, the software will be presented to the Hamdi Yildirim and Dr.zlem Albayrak for acceptance process.

7 Supporting Process Plans

7.1 Configuration Management Plan
TBD.

7.2 Verification and Validation Plan

TBD.

7.3 Documentation Plan

TBD.

7.4 Quality Assurance Plan

TBD.

7.5 Review and Audits

TBD.

7.6 Problem Resolution Plan

TBD.

7.7 Subcontractor Management Plan

TBD.

7.8 Process Improvement Plan

TBD.

Additional Plans
N/A

32