Design Phase Schedule

Add these into the schedule for the design phase:

Name

Start Date

Duration

Resources

Predecessors

20

(0)

Design

02/17/00

19

21

(1)

Conceptual

02/17/00

19

22

(2)

Interview End

Thu

2 days

Educator,

Users

02/17/00

Product Management, End Users

Name

Start Date

Duration

Resources

Predecessors

23

Documentation of User Interviews

Fri 02/18/00

0 days

22

24

Create Use Cases

Mon 02/21/00

2 days

Product Management, Component Manager 1

23

25

Review Use Cases with End Users

Wed 02/23/00

1 day

Educator, Product Management, End Users

24

26

Complete set of Use Cases

Wed 02/23/00

0 days

25

Design cannot begin until the Vision / Scope document is complete.

The conceptual design phase is all about adding structure to the ideas from the envisionment phase. Here, we will find out from the users how they would like the system to work, and how the system can work in the most efficient way to meet business needs. When the conceptual design milestone has been reached - a complete set of finalized Use Cases - there will be a clearly defined description of the product, the functionality it will include and the manner in which the users will interact with the system.

These steps occur in a logical order, each needing to be complete before the next step can begin.

Name

Start Date

Duration

Resources

Predecessors

27

(1)

Logical

02/24/00

26

28

(2)

Design User Interface

02/24/00

29

(3)

Determine enduser requirements for the forms

02/24/00

30

Interface

Prototype

02/24/00

2 days

Educator

Name

Start Date

Duration

Resources

Predecessors

31

Review Prototype with Users

Mon 02/28/00

1 day

Educator, End Users

30

Interface prototype

Mon 02/28/00

0 days

30,31

33

User Interface designed

Mon 02/28/00

0 days

32

34

For the web component, determine links

02/24/00

1 day

Developer 3a

35 (2)

Proof of Concept Testing

02/24/00

5 days

Component Manager 2 [50%], Developer 2a [50%], Tester 2a

This stage of the design phase cannot begin until there is a complete set of finalized use cases - otherwise, there would be nothing to build upon!

The logical stage of the design phase is where a prototype of the user interface will be developed; this will allow the developers to ascertain how the users want to interact with the system. Form design will also take place, so that the user's interaction with the system is optimized and both easy and complex tasks are simple to perform.

For the web component, you must figure out conceptually what you want the look and feel of the site / application to be. If the site is large you will want to determine the design and layout of the site. Design should be decided on first and agreed on by all team members. You should also determine conceptually what your 'hot spots' will be and what they will link to.

Name

Start Date

Duration

Resources

Predecessors

36

Decide how to implement functionality

02/29/00

32

Name

Start Date

Duration

Resources Predecessors

37 (3)

Create Sequence

Tue

3 days

Component

Diagrams

02/29/00

Manager 1,

Developer 1a,

Developer 1b,

Component

Manager 2 [50%],

Developer 2a

[50%],

Developer 2b,

Component

Manager 3,

Developer 3a,

Developer 3b,

Product

Management[33% ]

38

Determine what

Fri

1 day

Component 37

components are

03/03/00

Manager 1,

required

Developer 1a,

Developer 1b,

Component

Manager 2,

Developer 2a,

Developer 2b,

Component

Manager 3,

Developer 3a,

Developer 3b,

Product

Management[33% ]

Name

Start Date

Duration

Resources

Predecessors

39

Determine service for components

Mon 03/06/00

1 day

Component Manager 1, Developer 1a, Developer 1b, Component Manager 2, Developer 2a, Developer 2b, Component Manager 3, Developer 3a, Developer 3b, Product

Management[33% ]

38

Sequence

Diagrams

Mon 03/06/00

0 days

38,39

This stage of the design phase is where the developers convert the use cases into sequence diagrams, which indicate which components the project will need, and which properties and services each component will need.

After you have defined the specific functionality in the Conceptual phase, you must decide how to implement it. The decision on how to implement functionality cannot be made until there is a complete user interface prototype - before this, the detailed functionality will not be known. This decision entails whether you will have in-house developers do the work, hire vendor development services, or you will buy a product off-the-shelf to implement the functionality.

For example, functionality important to the users may be the ability to give feedback directly from the website to the content owners. This can be done by implementing a link that sends email to the content owners, or by creating a page that puts the feedback into a database. Creating a hotlink to email needs very little development, but there must be a scheme set up to maintain whom that mail goes to. Creating the direct-feedback page takes more development, but you have greater control over how the feedback is formulated and can be reported on. These types of tradeoffs need to be considered when designing functionality. In this stage you need to perform some cost benefit analysis as to whether it is more beneficial to develop the function in-house, hire vendor development services or buy the product in the form of an off-the-shelf product.

Name

Start Date

Duration Resources Predecessors

41 (1)

Physical

Tue

40

03/07/00

42 (2)

Design

Tue

Components for

03/07/00

the project

43 (3)

Create Activity

Tue

1 day Component

Diagrams

03/07/00

Manager 1[50%],

Developer

1a[50%],

Developer

1b[50%],

Component

Manager 2[50%],

Developer

2a[50%],

Developer

2b[50%],

Developer

3a[50%],

Developer

3b[50%],

Component

Manager 3[50%]

44

Create Class

Tue

1 day Component

Diagrams

03/07/00

Manager 1[50%],

Developer

1a[50%],

Developer

1b[50%],

Component

Manager 2[50%],

Developer

2a[50%],

Developer

2b[50%],

Component

Manager 3[50%],

Developer

3a[50%],

Developer

3b[50%]

Name

Start Date

Duration

Resources

Predecessors

Consolidated Design Document

03/07/00

0 days

Component Manager 1, Developer 1a, Developer 1b, Component Manager 2, Developer 2a, Developer 2b, Component Manager 3, Developer 3a, Developer 3b

43,44

The physical stage of the design phase is where the actual properties and services of each component are defined: this means that there is a concrete design for each component, and also for the way in which the component will interact. The physical design stage of the design phase cannot begin until all sequence diagrams are completed. The logical stage was still very general; the physical stage translates the earlier designs into the programming language of the project, in our case Visual Basic.

In this step of the physical stage, the activity and class diagrams are created - these relate directly to the Visual Basic programming language and will show exactly how each component should work in Visual Basic. The milestone for this step is the completed consolidated design document - it is essential that the design for Visual Basic be agreed upon, as this is what will be developed in the next phase. However, this milestone is dependent on the class and activity diagrams being completed.

Name

Start Date

Duration

Resources

Predecessors

46 (2)

Design Server Setup

03/07/00

40

47 (3)

Determine estimated disk space utilization

03/07/00

1 day

Logistics[33%]

48

Determine estimated traffic

03/07/00

1 day

Logistics[33%]

49

Design access permission

03/07/00

1 day

Logistics[33%]

50

Design testing / staging area scheme

Wed 03/08/00

3 days

47,48,49

Name

Start Date

Duration

Resources

Predecessors

51

Communicate with server operations

Mon 03/13/00

2 days

50

52

Server site live

03/14/00

0 days

51

There are many things to consider when designing the setup of the server, not least the fact that all sequence diagrams must be complete. First of all, you must determine how much data you will have so that you know how much space it will take up on the server - this is quite important, as vast amounts of data may cause vast increases in total project cost.

You will also want to ensure that, after developing the site, people will be able to view it. You need to determine how much estimated traffic there will be: for example, how many people will visit your site and how often will they visit it? For middle tier components, how many users will try to access the server simultaneously? This will help you figure out what server (hardware and software) configuration you should use.

Security is also an issue when developing a site: who has access to what information on the intranet? Access to information will be based on the roles that were created in the Use Cases.

Since you do not want to make content changes to your application while users are working on it, you need to define how changes will be made and how those changes will be propagated to the server components. You must also communicate all server requirements to the personnel responsible for server operations so that they can prepare and set up the production server. Only after this is complete can server site go live.

Name

Start Date

Duration

Resources

Predecessors

Support

Infrastructure

Mon 03/13/00

54 (3)

Determine network impact

Mon 03/13/00

2 days

50

55

Determine what changes need to be made

Wed 03/15/00

3 days

Logistics

54

56

Communicate with support staff

Mon 03/20/00

1 day

Logistics

55

Name

Start Date

Duration

Resources

Predecessors

Requirements

Documented

Mon 03/20/00

0 days

56

58 (2)

Completed Design Document

Mon 03/20/00

0 days

45,52,57

Ideally, a lab should be set up to simulate the production network (bandwidth and traffic). Since this is not always feasible, your best guess on impact to the network is important so that different potential solutions to problems can be identified. If your system's speed, reliability or response time will be compromised because of network issues, you must determine what steps need to be taken to address those issues.

Keep your support personnel abreast of any issues you think relevant (network, server or content related) so that they can prepare to staff accordingly. This is important because you want your support staff and intranet site to go live simultaneously. The deliverable for the design phase is a completed design document - dependent on there being a completed consolidated design document, a live server site and full documentation of support requirements - detailing exactly what the system is to include and how this should be developed.

The schedule for the design phase will look as follows:

Microsoft Project - DNA

fei File Edit View Insert Format lools Project Window Help ffjxj

Arial

O

Task Name

Duration

Start

Finish

Predecessors

Resource Names

20

B Design

23 days

Thu OZriTlOO

Mon 03120/00

19

21

B Conceptual

5 days

Thu OZriTlOO

Wed 02123/00

19

22

Interview End Users

2 days

Thu 02/17/00

Fri 02/18/00

Educator .Product Mans

23

Documentation of User Interviews

0 days

Fri 02/18/00

Fri 02/18/00

22

24

Create Use Cases

2 days

Mon 02/21 /DO

Tue 02/22/00

23

Product Management ,C

25

Review Use Cases with End Users

1 day

Wed 02/23/00

Wed 02/23/00

24

Educator .Product Mane

26

Complete set of Use Cases

0 days

Wed 02/23/00

Wed 02/23/00

25

27

B Logical

H days

Thu 02/24100

Mon 03I0G/00

2G

28

B Design User Interface

3 days

Thu 02/24100

Mon 02121/00

29

B Determine end-user requirements

3 days

Thu 02/24100

Mon 02121/00

30

Creaite User Interface Prototype

2 days

Thu 02/24/00

Fri 02/25/00

Educator

31

Review Prototype with Users

1 day

Mon 02/28/00

Mon 02/28/00

30

Educator .End Users

32

Completed User Interface prototype

0 days

Mon 02/28/00

Mon 02/28/00

30,31

33

User Interface designed

0 days

Mon 02/28/00

Mon 02/28/00

32

34

For the web component, determine links

1 day

Thu 02/24/00

Thu 02/24/00

Developer 3a

35

Proof of Concept Testing

5 days

Thu 02/24/00

Wed 03/01 fflO

Component Manager 2[

36

B Decide how to implement functionality

5 days

Tue 02129100

Mon 03I0G/00

32

37

Create Sequence Diagrams

3 days

Tue 02/29/00

Thu 03/02/00

Component Manager 1

38

Determine what components are require

1 day

Fri 03/03/00

Fri 03/03/00

37

Component Manager 1

39

Determine service for components

1 day

Mon 03/06/00

Mon 03/06/00

38

Component Manager 1

40

Completed Sequence Diagrams

0 days

Mon 03/06/00

Mon 03/06/00

38,39

41

B Physical

10 days

Tue 03/07100

Mon 03120/00

40

42

B Design Components for the project

1 day

Tue 03/07100

Tue 03107/00

43

Create Activity Diagrams

1 day

Tue 03/07/00

Tue 03/07/00

Component Manager 1[

44

Create Class Diagrams

1 day

Tue 03/07/00

Tue 03/07/00

Component Manager 1[

45

Create Consolidated Design Document

0 days

Tue 03/07/00

Tue 03/07/00

43,44

Component Manager 1

46

B Design 5erver Setup

G days

Tue 03/07100

Tue 03M4/00

40

Ready

The Gantt chart will look as follows:

Was this article helpful?

0 0
Project Management Made Easy

Project Management Made Easy

What you need to know about… Project Management Made Easy! Project management consists of more than just a large building project and can encompass small projects as well. No matter what the size of your project, you need to have some sort of project management. How you manage your project has everything to do with its outcome.

Get My Free Ebook


Post a comment