Professional Documents
Culture Documents
Version 1.0
Doc. No.: 1
Web Project Version: 1.0
Final Project Report Date: 2006-10-01
Revision History
Page 2
Web Project Version: 1.0
Final Project Report Date: 2006-10-01
Table of Contents
1. Introduction 4
1.1 Purpose of this document 4
1.2 Intended Audience 4
1.3 Scope 4
1.4 Definitions and acronyms 4
1.4.1 Definitions 4
1.4.2 Acronyms and abbreviations 4
1.5 References 4
3. Organization 4
3.1 Project Manager 4
3.2 Project Group 4
3.3 Steering Group 5
3.4 Customer 5
3.5 Others 5
4. Milestones 5
4.1 Remarks 5
5. Project Results 5
5.1 Requirements 5
5.1.1 Requirement Compliance Matrix 5
5.1.2 Requirements Compliance Summary 6
5.1.3 Remarks 6
5.2 Work Products and Deliverables 6
5.2.1 Remarks 6
6. Project Experiences 6
6.1 Positive Experiences 6
6.2 Improvement Possibilities 7
7. Financials 7
7.1 Project Cost Summary 7
7.2 Work per Member 7
8. Metrics 7
8.1 Milestone Metrics 7
8.2 Effort Metrics 7
Page 3
Web Project Version: 1.0
Final Project Report Date: 2006-10-01
1. Introduction
Web Project is the project undertaken as a mandatory requirement for the course “Distributed
Software Development” that is being conducted mutually by Malardalen University in Vasteras,
Sweden and University of Zagreb. The aim of the course is to provide a distributed environment
to develop software. In this course we have to develop the Distributed Software in two teams.
But in our project we are not distributed because we are working on the same side. But we hope
that we will make this Project on time.
1.3 Scope
The project is aimed to provide a central place for organizing, planning and tracking projects that
are developed in a distributed environment. It therefore is a web application that should be
compatible with majority of browsers to provide user friendly Interface for project administrator,
project leaders and project members working far apart all around the world.
1.4.1 Definitions
Keyword Definitions
Distributed Process in which the software is being developed by
software different teams working at least 30 m apart physically.
Development
Acronym or
Definitions
abbreviation
Page 4
Web Project Version: 1.0
Final Project Report Date: 2006-10-01
1.5 References
“Web Project” Final Project document.
3. Organization
Name Responsibility
Khuram Shehzad Project manager, Analysis, Implementation, Designing,
DB Design
Ahsan Jawed Implementation, Documentation, Analysis, DB Design
Imran Afzal Implementation, Documentation, Designing, Analysis
Shoaib Ahmad Implementation, Analysis, Documentation, Analysis
Abdullah Anjum Integration, Testing, Analysis
3.4 Customer
Igor Cavrak
Page 5
Web Project Version: 1.0
Final Project Report Date: 2006-10-01
3.5 Others
4. Milestones
Finished week M
Milestone Responsible Re
4.1Id Forecast Act et
Description Dept./Initials Plan m
Week +/- ual r
M-001 Project Description & 17-11- 0 0 17-11- Y G
Plan 05 05 oo
d
M-002 Requirement Definition 17-11- 0 0 17-11- Y G
05 05 oo
d
M-004 Project Design 24-11- 0 0 24-11- Y G
05 05 oo
d
M-005 Revised Project Plan 01-12- 0 0 01-12- Y G
05 05 oo
d
M-006 Project Status 15-12- 0 0 15-12- Y G
Presentation 05 05 oo
d
M-007 Final Presentation & 19-01- 0 0 19-01- Y Ex
delivery 06 06 cel
le
nt
Remarks
Rema
Description
rk Id
R-001 It was good experience to give a Presentation in Distributed Environment.
5. Project Results
5.1 Requirements
Page 6
Web Project Version: 1.0
Final Project Report Date: 2006-10-01
Requirement
Id completed Rem
Description
Web-1 System Administration Requirements Yes
Web -1.1 Administrator should login to do any specific Yes
task.
Web -1.2 Administrator should be able to adjust system Yes
parameters.
Web -1.3 Administrator should be able to add/ modify/ Yes
enable/ disable/ delete system users.
Web -1.4 Administrator should be able to add/ modify/ Yes
archive/ delete projects.
Web -1.5 Administrate project leaders for existing projects. Yes
Web -1.6 Comments to different members. Yes
Web -2 Project leader Requirements. Yes
Web -2.1 Project leader should be able to define baseline Yes
plan.
Web -2.2 Project leader should be able to manage project Yes
group.
Web -2.3 Project leader should be able to monitor individual Yes
work.
Web -2.4 Project leader should be able to define milestones, Yes
activities, resources & financial plans etc…
Web -2.5 Project leader should be able to freeze work done Yes
report at the end of the week after finalizing the
week plan.
Web -3 Project member should be able to submit week Yes
report.
Web -4 E-mail Alerts & Logging Yes
Web -5 Look & Feel and Language Yes
Web -6 Gand Chart Yes
Web -7 Log File Yes
5.1.3 Remarks
Remark Id Description
Deliv R
Planned Promised
To Output Late +/- ered e
week week
week m
Igore Project W46 W46
Cavrak Description No W46
& Plan
Igore Requireme
Cavrak nt W47 W47 No W47
Definition
Igore Project W49 W49 No
Cavrak Design W49
Igore Revised
Cavrak Project W52 W52 No W52
Plan
Igore Project
Cavrak Status W01 W01 No W01
Presentatio
n
Igore Final
Cavrak Presentatio W03 W03 No W03
n &
delivery
5.2.1 Remarks
Remark
Description
Id
Page 8
Web Project Version: 1.0
Final Project Report Date: 2006-10-01
6. Project Experiences
7. Financials
Planned
250.000 SEK
Cost
Actual Cost 260.000 SEK
Page 9
Web Project Version: 1.0
Final Project Report Date: 2006-10-01
Member W45 W46 W47 W48 W49 W50 W51 W52 W01 W02 W03 Total
Khuram 20 24 20 22 25 35 30 30 36 34 46 322
Shahzad
Ahsan Jawed 15 19 18 19 22 25 28 26 30 29 32 263
Imran Afzal 13 15 16 20 19 20 24 22 23 24 30 226
Shoiab 14 16 15 15 20 24 22 20 20 22 28 214
Ahmad
Abdullah 15 13 15 16 20 15 22 19 22 25 30 212
Anjum
Total 77 87 84 92 106 117 126 117 131 134 166 1237
8. Metrics
Completed as planned
Total Timeliness
or earlier
18 19 Achieved
Page 10
Web Project Version: 1.0
Final Project Report Date: 2006-10-01
Effort estimation
accuracy (%)
(100*(1 - abs(Actual – 98.14%
Planned)/Actual))
Page 11