Professional Documents
Culture Documents
For
PHARMACY SYSTEM
(PS)
Acquirer:
Syed Amjad Ali
Prepared By:
GROUP MEMBERS: Nesrin Duman, Onur Öztürker,
Oğuz Bedir, Mert Öcal
Change History
Date Version File Name Document Format Status
30 November 1.0 Spmp_report.v1.0.doc Microsoft Word Created
2
PS Software Project Management Plan Version 1.0
Preface
3
PS Software Project Management Plan Version 1.0
Table of Contents
Change History 2
Preface 3
Table of Contents 4
List of Figures 6
List of Tables 7
1 OVERVIEW 8
1.1 Project Summary 8
1.1.1 Purpose, Scope and Objectives 8
1.1.2 Assumptions and Constraints 9
1.1.2.1 Assumptions 9
1.1.2.2 Constraints 9
1.1.3 Project Deliverables 10
1.1.4 Schedule and Budget Summary 11
1.2 Evolution of the Plan 12
2 REFERENCES 12
3 DEFINITIONS & ABBREVATIONS 13
4 PROJECT ORGANIZATION 14
4.1 External Interfaces 14
4.2 Internal Structure 15
4.3 Roles and Responsibilities 16
5 MANAGERIAL PROCESS PLANS 17
5.1 Start-up Plan 17
5.1.1 Estimation Plan 17
5.1.2 Staffing Plan 21
5.1.3 Resources Acquisition Plan 22
5.1.4 Project Staff Training Plan 22
5.2 Work Plan 22
5.2.1 Work Activities 22
5.2.2 Schedule Allocation 46
5.2.3 Resource Allocation 46
5.2.4 Budget Allocation 47
5.3 Control Plan 47
5.3.1 Requirements Control Plan 47
5.3.2 Schedule Control Plan 48
5.3.3 Budget Control Plan 48
5.3.4 Quality Control Plan 49
5.3.5 Reporting Plan 49
5.3.6 Metrics Collection Plan 50
5.4 Risk Management Plan 51
5.5 Project Closeout Plan 53
6 TECHNICAL PROCESS PLANS 54
6.1 Process Model 54
6.2 Methods, Tools and Techniques 54
4
PS Software Project Management Plan Version 1.0
5
PS Software Project Management Plan Version 1.0
List of Figures
Figure 1 External Structure 13
Figure 2 Internal Structure 16
Figure 3 Process Model 57
6
PS Software Project Management Plan Version 1.0
List of Tables
Table 1 Schedule of the Project 11
Table 2 Evolution of the Plan 12
Table 3 The Roles and Responsibilities 16
Table 4 Unadjusted Function Point Table 19
Table 5 Degree of Influences 19
Table 6 Staff Training Plan 22
Table 7 Work Activities 22
Table 8 Schedule Allocation 46
Table 9 Resource Allocation 47
Table 10 Metrics Collection Plan 50
Table 11 List of Identical Risk 51
Table 12 Probability Evolation Criteria 52
Table 13 Consequence Evalatuon Criteria 52
Table 14 Risk Management 53
Table 15 Documentation Schedule 58
7
PS Software Project Management Plan Version 1.0
1 OVERVIEW
PS Software Project Management Plan is prepared according to IEEE Std. 1058-1998,
IEEE Standard for Software Project Management Plans.
The use of the document is Hospital or Clinic users which are Doctors Nurses, and
Pharmacy Worker. The system is designed to be a platform which brings the drugs
information with the doctors and nurses together and let them share their information.
This project has two main parts. First approach is to establish the right connection
between the patient and the doctor in order to make the right diagnosis for the patient and
have the best treatment. The second approach is to provide stock control and to provide stock
information to doctors while they are making a prescription.
Within this project we are going to establish the information between Doctor, Nurse
and the Pharmacy workers. The pharmacy system on web is going to be adapted with the
Wireless Network, by using a PDA it is going to provide the communication between the
doctor and the nurse , nurse -patient -doctor and pharmacy worker.
The PS database system will collect and supply required drugs, patient and illnesses
information and PS web interface will be the source which provides a secure and interactive
platform between the users and the database.
8
PS Software Project Management Plan Version 1.0
1.1.2.1 Assumptions
The project staff is consisting of 4(four) persons and each person will work 3(three)
hours a day.
All the necessities such as server, account and PDA will be supplied by CTIS.
The system will be used by
o Doctors
o Nurse
o Pharmacy Worker
o Database Administrator
1.1.2.2 Constraints
9
PS Software Project Management Plan Version 1.0
10
PS Software Project Management Plan Version 1.0
20 December SDD
11
PS Software Project Management Plan Version 1.0
No budget will be associated with PS by the MONO members, because all needs such
as server, account for web-address or database will be supply by the CTIS.
This SPMP is evolved from the Initial Plan of the PS project that is simple version of
this document. Hence, this document is developed by the MONO Group Members with the
approval of the acquirer.
There are three scheduled versions of this plan. The following table summarizes the
scheduled versions.
30 November SPMP
2 REFERENCES
12
PS Software Project Management Plan Version 1.0
[1] IEEE STD 1058-1998, IEEE Standard for Software Project Management Plans
[2] Ian Sommerville, Software Engineering Seventh Edition, Addison-Wesley 2004
[3] Humphrey, W, Managing the Software Process, Addison-Wesley 1989
[4] Arthur M. Langer, Analysis and Design of Information System, Springer-Verlag New
York, Inc., 2001
[5] CTIS 455 Software Engineering Lecture Notes.
[6] http://www.rspa.com/spi/ Software Engineering Resource Page
[7] http://www.geocities.com/ResearchTriangle/Campus/6025/fpa/fpa.htm, Functional Size
Measurement (FSM) Page.
13
PS Software Project Management Plan Version 1.0
Acquirer: Specifies requirements for and accepts delivery of a new or modified software
product. In this project acquirers refer to our two instructors.
Senior Project: Refers to a lecture that is to be finished by the fourth year students to
graduate.
Subcontractor: Refers to the review group who make necessary corrections in the documents
in order to improve the quality of the product and documentation. In this project subcontractor
refer to our Software Engineering course instructor.
User: Refers to people in the hospital or clinic who are doctor, nurse, pharmacy worker and
database administrator.
4 PROJECT ORGANIZATION
Project Group: MONO Mert Öcal, Oğuz Bedir, Nesrin Duman, Onur Öztürker.
CTIS
Figure 1 External Interfaces
Acquirer 14
Customer
PS Software Project Management Plan Version 1.0
PS
Software
Requirements Testing Design Content Version
4.3 Roles and
Enginering Responsibilities
Engineering Management Control
15
PS Software Project Management Plan Version 1.0
Programmer, Configuration
Manager
Software Engineer: will plan, analyze and design the software project during preparing the
documentations of project.
Test Team Member: will test the system to augment the quality.
Training Coordinator: will prepare the stuff-training plan to ensure that necessary skill levels
in sufficient numbers will be available to successfully conduct the software project.
Meeting Tracer: will organize and coordinate the meetings of team members and also
meetings with customers.
Software System Engineer: will help the project team to identify, control, and track
requirements and changes to requirements at any time as the project proceeds and make the
architectural design of the project accordingly.
Project Manager: will plan (schedule, cost and budget), motivate, organize and control the
software team.
Configuration Manager: will manage different versions of the work products, control the
changes that are imposed and audit and report on the changes that are made. And also will
update the project’s web page regularly.
The cost and schedule for conducting the project (PS) as well as the methods, tools,
techniques, used to estimate project cost, schedule, resource requirements, external input and
output data associated confidence levels are presented below.
16
PS Software Project Management Plan Version 1.0
Function Point method is used for size estimation of the project. The functions of the
project are identified according to the user requirements defined during the initial meetings.
These functions are:
External inputs:
New Patient Information Add
New Patient Information Delete
New Patient Information Update
Patient Disease Identification and Therapy Information Add
Patient Disease Identification and Therapy Information Delete
Patient Disease Identification and Therapy Information Update
Drug Information Add
Drug Information Delete
Drug Information Update
Drug Stock Input-Output Information Add
Drug Stock Input-Output Information Delete
Drug Stock Input-Output Information Update
Disease Information ICP-10 Add
Disease Information ICP-10 Delete
Disease Information ICP-10 Update
External Output:
Patient Registration
Drug Registration
Stock Registration
Warning Message
External Enquiry:
Access to Patient Records
Access drugs which are given to patient before
Access to Drugs Records
Access to stock records
17
PS Software Project Management Plan Version 1.0
Function Levels
Components Low Average High Total
External Inputs 9x3 6x4 1x6 54
External Outputs 2x4 2x5 0x7 18
External Inquiries 4x3 2x4 1x6 26
Internal Logical Files 5x 7 0 x 10 0 x 15 35
External Interface Files 0x5 0x7 1 x 10 10
Total Unadjusted FP (UFP): 143
Table 4 Unadjusted Function Point Table
18
PS Software Project Management Plan Version 1.0
The table shown above lists the replies of the system to the specific questions
depending on the IFPUG documents.
Value Adjustment Factor (VAF) = (TDI x 0.01) + 0.65 = (41 x 0.01) + 0.65 = 1.06
Adjusted Function Point Count (FP) = UFP x VAF = 1.06 x 143 = 151.58
Effort Estimation
19
PS Software Project Management Plan Version 1.0
COCOMO model is used to calculate the schedule estimation for the PS. COCOMO
model calculates effort in man months.
Cost Estimation
The hourly salary of each group member is $10, therefore the estimated cost of the
Project is:
15.68 man month = 15.68 x 152 (hours in a month) = 2383,36~ 1383 man hours
Cost = Effort x $ (the hourly salary)
C = 2383 man-hours x $10/man-hours
C = $23.830
20
PS Software Project Management Plan Version 1.0
The Gantt Charts are used to depict the staffing plan by project phase; this chart is
given on Appendix A.
Each one of the group members has the same designated responsibilities which are
required to acquire resources as needed through the evolution of the project.
Since our customers are allocated in Bilkent Campus, there is no transportation cost
for the meetings.
MONO members need training. Since, all the training will be given by the team
members; there is no need to assign a budget for training.
Both hardware and software are supplied by the group members.
21
PS Software Project Management Plan Version 1.0
Work activities of PS project are given in table 10. The milestone tasks are identified
at the third column by *Milestone mark.
22
PS Software Project Management Plan Version 1.0
23
PS Software Project Management Plan Version 1.0
24
PS Software Project Management Plan Version 1.0
25
PS Software Project Management Plan Version 1.0
26
PS Software Project Management Plan Version 1.0
27
PS Software Project Management Plan Version 1.0
28
PS Software Project Management Plan Version 1.0
29
PS Software Project Management Plan Version 1.0
30
PS Software Project Management Plan Version 1.0
31
PS Software Project Management Plan Version 1.0
32
PS Software Project Management Plan Version 1.0
33
PS Software Project Management Plan Version 1.0
34
PS Software Project Management Plan Version 1.0
35
PS Software Project Management Plan Version 1.0
36
PS Software Project Management Plan Version 1.0
37
PS Software Project Management Plan Version 1.0
Skill: Communication
Tool: Notebook, IEEE document, Existing SDD
Travel: N/A
Outputs Borders of SDD
Baselines No
Predecessors 1.5.5
Successors 1.5.7
Completion Criteria SDD plan is reviewed
Implementation
Personnel Assigned Team Members
Starting Date 19 December 06
Completion Date 20 December 06
Cost (Budgeted and Actual) NA
Legacy Comments None
38
PS Software Project Management Plan Version 1.0
39
PS Software Project Management Plan Version 1.0
40
PS Software Project Management Plan Version 1.0
41
PS Software Project Management Plan Version 1.0
42
PS Software Project Management Plan Version 1.0
43
PS Software Project Management Plan Version 1.0
44
PS Software Project Management Plan Version 1.0
45
PS Software Project Management Plan Version 1.0
Group members have the general information about design techniques of .Net
language. PCs will be used for documentations of the reports that are IP, SRS, SPMP and
SDD and coding. Table 9 shows software tools to be used by project phase. Personnel
allocation for each WBS item is given in Table 8.
46
PS Software Project Management Plan Version 1.0
The lecture’s instructor predefines the schedule of the project. All of the requirements
in the SRS are written as a result of the meeting with the acquirers. Hence, the requirements
are constant and certain. However, small changes that do not affect the scope of the project
can be occurred by the request of the acquirers during the project.
The schedule and resources of the project are fixed. Therefore, all of the requirements which
are defined in the SRS are almost definite and stable. Only minor changes will be made in the
continuity of the project because major changes effects the over schedule of the project.
For minor changes, “A Change Request Form (CRF)” (Appendix B) is filled by the
acquirer for the requested minor changes and submitted to the software development team for
evaluation. After the evaluation, the acquirer’s request will be accepted or rejected. If the
request rejected, document of the objection will be send to the acquirer. If the request
accepted, necessary changes will be made in the all related plans. After the changes are made,
“Requirement Change Report (RCR)” (Appendix B) will be prepared and submitted to the
acquirer.
The project schedule is fixed. While preparing the schedule plan, MS Project tool is
used and all the milestones of the project phases are defined. The software development team
sticks the milestones. At every milestone, necessary deliverables send to the acquirer and
subcontractor and subcontractor will be check and compare the actual process and planned
process.
The schedule of the Project is under control due to the deadlines. The project team is
very strict about the team management planning. There are some specific days that the team
members come together and work on the project in every week. Sometimes, these meetings
are not enough. At these times, team members come together on weekends.
The milestones of the projects are predefined by the CTIS 455 Lecture’s Instructor, so
it is not possible to change the date of submission of any deliverables. The MONO members
cannot delay the dates. So, group members mark the milestones on their own calendars.
MONO also uses a Schedule Control Plan (SCP) (Appendix C) to measure and control
schedule progress. It is supply a vision of the current deliverable. Achievement and quality of
that deliverables will be evaluated by the consultant.
47
PS Software Project Management Plan Version 1.0
If the actual progress does not conform to the planned progress, a Schedule Control
Report (SCR) (Appendix D) will be prepared and submitted to the acquirer and subcontractor.
In this report schedule corrections will be defined.
There is no need budget control plan because there is no budget allocated for the PS
project. The cost of the project depends on achievement of the schedule and deadlines and the
effort spend by the project group. Budget Control Report (Appendix E) will be prepared for
the acquirer by the Project Manager.
Quality control plan will be applied all deliverables of the project. These deliverables
is controlled by both internal and external reviews which are defined in the WBS and
schedule allocation. Internal reviews will be made by the software development team and
external reviews will be made by the subcontractor.
After every review meeting, the software development team discusses the meeting
subjects, make the necessary reviews and update the product according to the subcontractor’s
corrections.
All of the reports which are prepared during the project phase prepared according to
the IEEE standards [1, 2, 3, and 4] and project schedule. These reports are Initial Plan,
Software Requirement Specification, Software Project Management Plan and Software
Design Document. MS Project 2003 and MS Word 2003 tools will be used for reporting.
On the other hand, the four control reports that are listed below will be used during the
project:
Change Request Form: This form is used when the acquirer wants new
requirements or any changes to the existing ones. More details can be found in
section 5.3.1.
48
PS Software Project Management Plan Version 1.0
Schedule Control Report: If there is any distortion from the actual progress, a
SCR will be prepared for the acquirer. The report is supplied by MONO
members using MS Project 2003. More details can be found in section 5.3.2.
Budget Control Report: If there is any distortion from actual cost, a BCR will
be prepared for the acquirer. The report is prepared by Project Manager using
MS Project 2003. More details can be found in section 5.3.3.
Schedule Control Plan Form: These reports are supplied by the MONO group
members after every meeting. More details can be found in section 5.3.2.
The metrics to be collected, their units, and the frequency of collection are given in
Table13.
49
PS Software Project Management Plan Version 1.0
Project risks are identified in Table 15. These risks can be monitoring during the
development of product or documentation. If these risks are occur, they will be evaluated in
team meetings. Because the project group is responsible to take correct decisions and perform
these decisions if the risks are become real.
50
PS Software Project Management Plan Version 1.0
51
PS Software Project Management Plan Version 1.0
52
PS Software Project Management Plan Version 1.0
A final report including lessons learned and analysis of project objectives achieved
will be prepared by the software development team.
The final deliverable documents that are IP, SRS, SPMP, and SDD will be submitted
to the consultant who is our Software Engineering lecture’s Instructor. The Project group will
hold an interview with project customer.
After the documents are accepted by consultant, the documents will be established in
the group’s web side. After all these process are completed at the end of the next semester
project group will make a demonstration of the product to the customer a few instructors.
Because this project is a part of fourth year students’ senior project.
The process model of the project is “Waterfall” model. All work activities of the Work
Breakdown Structure (Appendix A) includes major milestones, project deliverables of each
phase, reviews and schedules. The deliverables produced at the end of the each phase stated in
top level WBS items shall be the input for the next phase.
Product
Delivery
Figure 3 Process Model
The waterfall methodology shall be used. .Net shall be the programming development
environment and user interface environment. Ms-SQL database management system shall be
used storing and processing data. The main tools to be used for documentation shall be
53
PS Software Project Management Plan Version 1.0
Microsoft Word 2003 for documents and Microsoft Project 2003 for project planning.
Microsoft Visio 2003 shall be used for ER diagrams, design diagrams and process models.
IEEE Std. 1058-1998, IEEE Standard for Software Project Management Plans; IEEE
Std. 830-1998, IEEE Recommended Practice for Software Requirements Specifications; IEEE
Std. 1016-1998, Recommended Practice for Software Design Descriptions will be used for
standardization of the documents .
During the development project group members shall use their own hardware and
software environments. The hardware used shall be minimum 512 MB RAM. Microsoft .Net
and Ms-SQL database management system shall be installed on computers of the group
members. Photoshop and MS Visio 2003 shall be used for analysis and design. Internet
Explorer shall be minimum IE 3.0. This project will be web based, so the network
infrastructure and speed is important. The system will be hosted by a Bilkent University
server. Because of the high quality network speed and infrastructure of Bilkent University,
users can reach the system very fast. Also, the response time of the system will be high.
o The documents must deliver on predefined dates. Late submission will not be
accepted.
o Each project team must have “Project Web Site” to publish their deliverables
o The documents must be prepared according to the IEEE Standards.
o The each documents shall be updated and established after the consultant is
reviewed the documents.
o The product shall be demonstrated to the customer and instructors at the end of
the semester.
o The acceptance criterion is the customer’s and the instructors’ satisfaction with
that demonstration. However, the product which is not work correctly will not
be accepted.
54
PS Software Project Management Plan Version 1.0
All group members are responsible for verification activities. Validation is the process
of making sure that the product is being built correctly. At the completion of each milestone, a
validation analysis should be done. The validation will be performed by group member during
internal reviews to make sure that the delivered products are right. A demonstration of the
user interfaces to the acquirer will be made for validation.
All the testing activities are under the test team members’ responsibilities. There will
be two types of testing. One of them will be done after coding of each part; the other will be
done before publishing of the web site.
The configuration manager is the responsible person to publish all the deliverables via
web. All the deliverables will be prepared by group members. The demonstration of the
product and final product will be done by group members. Documentation schedule is seen at
Table 15.
55
PS Software Project Management Plan Version 1.0
DEMO Demonstration of
May 2006
Product
For quality assurance plan, review and configuration management methods will be
used. The project team will make both internal and external meetings. In internal meetings,
only team members will be in that meeting and they will make plans about their deliverables
deadlines. In external meetings, the project team will meet via customer, supervisor or
instructor to get the requirements. In these meetings team members will take notes to provide
56
PS Software Project Management Plan Version 1.0
that the deliverables are correct and meets the requirements specifications in SRS report. The
configuration manager will arrange these external meetings.
Before the delivery of each document, team members will have a meeting about the
existing document. These meetings are identified in 5.2 Work Activities section. Project
group is review the document lastly. If some corrections are necessary, these are made during
these meetings. After the document is established, the consultant examines the documents and
adds some comment to correct the fault. Then group members correct the faults and
established again with second version.
None, problems would be resolved informally between the developer, the advisor and
Subcontractor reviews the deliverables and highlights the points those need
corrections in order to improve the quality of the product and documentation.
57
PS Software Project Management Plan Version 1.0
58
PS Software Project Management Plan Version 1.0
59
PS Software Project Management Plan Version 1.0
60
PS Software Project Management Plan Version 1.0
Document Name:
Version No:
Section(s):
Identification No :
61
PS Software Project Management Plan Version 1.0
Current Condition:
Proposed Change:
Change Information
Change Control Number:
Cost Impact:
Timing Impact:
Quality Impact:
Scope Impact:
Other Impact:
Change Review Information
Signatures
Follow up
Documentation Updated:
SCHEDULE CONTROL
PLAN FORM
Document Name: Version No:
62
PS Software Project Management Plan Version 1.0
Works:
Submission Date:
Revised:
Revision Date:
Additional Information:
Task Name :
Date of Control:
Authority seeking change :
Action Officer :
Proposed change : Date proposed change :
Action(s) Taken:
63
PS Software Project Management Plan Version 1.0
Approval authority
Project Management signature :
Task Name :
Date of Control:
Authority seeking change :
Action Officer :
Proposed change : Date proposed change :
Action(s) Taken:
64
PS Software Project Management Plan Version 1.0
Approval authority
Project Management signature :
65