Project Description

seasoningalluringData Management

Nov 29, 2012 (4 years and 9 months ago)

240 views

Web Project


Version:
1.0

Project Description


Date: 200
5
-
11
-
15





Page
1



























Web Project

Project Description


Version
1.0



Doc. No.:



Web Project


Version:
1.0

Project Description


Date: 200
5
-
11
-
15





Page
2



Revision History


Date

Version

Description

Author

200
5
-
1
1
-
1
5

1.0

Initial Draft

Khurram Shahzad, Shoaib
Ahmed
, Abdullah Anjum














Web Project


Version:
1.0

Project Description


Date: 200
5
-
11
-
15





Page
3



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

5

2.

Organization

5

2.1

Project management

5

2.2

Project group

5

2.3

Steering group

5

2.4

Customer

5

2.5

Others

5

3.

Assumptions and constraints

5

3.1

Technological

5

3.2

Environmental

5

3.3

Interpersonal

5

3.4

Work distribution

5

3.5

Casual relationships

6

3.6

Time

6

4.

Deliverables

6

4.1.1

Remarks

6

5.

Inputs

6

5.1.1

Remarks

6

6.

Project risks

7

7.

Communication

7

8.

Configuration management

7

9.

Project plan

7

9.1

Time schedule

7

9.1.1

Remarks

8

9.2

Activity plan

8

9.3

Financial Plan

8

9.3.1

Remarks

8


Web Project


Version:
1.0

Project Description


Date: 200
5
-
11
-
15





Page
4



1.

Introduction

Web Project is the projec
t 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,
Zagreb, C
roatia. The aim of
the course is to provide a distrib
uted environment to develop software.


1.1

Purpose of this document

The basic purpose of this document is to describe our project as well as the plan for
carrying out this project
. In this document we have included the responsibilities
assigned to each member
of the group and we have also mentioned the deliverables.


1.2

Intended Audience

The Audience that is going to use this document includes customer, project
supervisor, group leader and group members.

1.3

Scope

The project is aimed to provide a central place for or
ganizing, 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 an
d project members
working far apart all around the world.


1.4

Definitions and acronyms


1.4.1

Definitions


Keyword

Definitions











1.4.2

Acronyms and abbreviations


Acronym or

abbreviation

Definitions




















Web Project


Version:
1.0

Project Description


Date: 200
5
-
11
-
15





Page
5



1.5

References

Requirement Definit
ion document

2.

Organization


2.1

Project management

Khurram Shahzad is assigned the role of Project Manager and he will be responsible
for the management of the project.


2.2

Project group

Name

Initials

Responsibility (roles)

Khurram Shahzad

Mr.

Analysis, Coding
,
a
nd Management

Ahsan Jawed

Mr.

Analysis, Coding and Documentation

Imran Afzal

Mr.

Documentation and Designing

Shoaib Ahmed

Mr.

Documentation and Designing

Abdulla Anjum

Mr.

CVS and
Testing



2.3

Steering group

Ivica Crnkovic (MDH)

Rikard Land (MDH)

Mario Z
agar (FER)

Igor Cavrak (FER)


2.4

Customer

Igor Cavrak (FER)

2.5

Others


3.

Assumptions and constraints


3.1

Technological

We will use java as
server side

technology. JSP will be used for developing user
interface. We will use the MVC model (struts) in our project
. Postg
reSQL will be
used as a back end.


3.2

Environmental

We will use tomcat as the application server and apache as web server on windows
platform.


3.3

Interpersonal


3.4

Work distribution

Khurram Shahzad will be doing analysis, coding

and management.

Analysis, coding a
nd documentation is assigned to Ahsan Jawed

Imran Afzal and Shoaib Ahmed will be involved in designing and documentation

Web Project


Version:
1.0

Project Description


Date: 200
5
-
11
-
15





Page
6



Abdull
ah

Anjum will
be involved in

testing

and CVS.


3.5

Casual relationships


3.6

Time

We have decided that all the group
members have

to work

between 1:00 PM to 4:00
PM in the first three days of the week. On Friday we will work from 3:00 PM to
7
:00
PM
.

4.

Deliverables


To

Output

Planned
week

Promised
week

Late +/
-

Delivered
week

Rem

Customer

Project Plan

3


3




Customer

Project Design

4

4




Customer

Revised Design

5

5




Customer

Project Status

7

7




Customer

Final Delivery

10

10





4.1.1

Remarks


Remark
Id

Description












5.

Inputs


From

Required item

Planned
week

Promised
week

Late +/
-

Delivered
week

Rem

Igor

Project Proposal

2

2


























Comment:

Required week

= week when it is required by the project;
Promised week
indicates
when the
From

expects to deliver;
Late +

indicates a discrepancy between
Required
week
and
Promised week; Received week

is week when it wa
s actually received;
Rem
is a remark index number.


5.1.1

Remarks


Remark
Id

Description

Web Project


Version:
1.0

Project Description


Date: 200
5
-
11
-
15





Page
7














6.

Project risks


Possibility

Risk

Preventive action

40%

Technology
unfamiliarity

Extra Training Hours

20%

Man Power

Dedication

20%

Technical
Resources

Good
Planning

20%

Incomplete
requirements

Try to define all the possible requirements



7.

Communication

We will use English as the communication medium, but as all the group members
belongs to Pakistan so there is strong possibility that we might use URDU as we
ll.


8.

Configuration management

Khurram Shahzad will be
responsible for

the configuration management.


9.

Project plan


9.1

Time schedule


Comment:

Finished week: Plan
= original plan;
Actual
= week when it was actually available;
Forecast Week

indicates the estimated finished week;
Forecast +/
-

indicates changes
in the estimation compared to the previous project report;
Metr

is the difference
betwee
n Plan and Actual, that is if Plan is w604 and Actual is w606, then Metr will be
-
2. To be filled in when the milestone is reported as completed;
Rem

is a remark index
number.


Id

Milestone

Description

Responsible
Dept./Initials

Finished week

Metr
.

Rem
.

Plan

Forecast

Actual

Wee
k

+/
-

1

Pro
ject Description & Plan


17
-
11
-
05






2

Requirement Definition


1
7
-
11
-
05






3

Project Design


24
-
11
-
05






4

Revised Project Plan


01
-
12
-
05






5

Project Status Presentation


15
-
12
-
05






6

Final Presentation & delivery


19
-
01
-
06






Web Project


Version:
1.0

Project Description


Date: 200
5
-
11
-
15





Page
8



9.1.1

Remarks


Remark
Id

Description











9.2

Activity plan


Activity

w45

w46

w
47

w48

w49

w50

w51

w52

w1

w2

w3

Project preparations





















Requirements analysis & definition





















Project Plan





















Project Design





















Project Coding





















Project Testing





















Project Documentation





















Project Management























9.3

Financial Plan


Activity

Volume
(days
)

Cost

Rem.

Project Preparations

7

1
0,000

SEK


Requirement analysis & Definition

21

1
0,000

SEK


Project Plan

21

1
0,000

SEK


Project Design

21

2
0,000

SEK


Project Coding

42

5
0,000

SEK


Project Testing

21

1
0,000

SEK


Project Documentation

63

3
0,000

SEK


Project Management

70

50
,000

SEK




Planned effort (man
-
Hours
)

Man
-
Hour

cost

Planned project cost (100%)

1200

100

19
0,000

SEK



9.3.1

Remarks


Remark
Id

Description







Web Project


Version:
1.0

Project Description


Date: 200
5
-
11
-
15





Page
9