Project

• Purpose

• Options– Network Design– Software (?)

• Approach {customer/boss/professor}

• Teams {prefered size is 3}

Project Phases

1. Enthusiasm

2. Disillusionment

3. Panic

4. Search for the Guilty

5. Punishment of the Innocent

6. Praise and Honors for the Non-participants

"almost a joke, but too often true!"

Project Schedules

EndStart*

* A miracle occurs

"don't let yourself plan like this"

Network Design

• An iterative, interactive process"you have to ask questions, & you'll never get it all in onemeeting with the customer"

• More than just selecting the media"remember you're designing a system -- make sure you look atsomething for all 7 layers of the OSI model"

• More than one right answer"don't be dogmatic. stay open to other soltuions than the one youfeel is technically best."

Network Design,cont

• What does the customer want to do?• What does the customer want to use?

{tentative design time}

• What are the customer's desires (biases)?

• Check for completeness...

• Check for integration...

• Implementation Plan

Time"Do them in order. Each step is important"

Functions"the 2 main reasons for a network are connectivity and resource sharing"

Electronic Mail

File Sharing • Transfer • Virtual disk/files

Resource Sharing • Printers/plotters etc • Modems • CPU • Disk

Connectivity • Remote login

Software Management

Resources"Remember to be precise!"

Systems Qty Mfg Version Software

Geography Distances Constructions Standards

Tentative Design

• Meant to bring out Key features ...

• ... and Decision points ...

with the Customer.

• Provide your “best” solution, and be ready with alternatives.– Features vs “Costs”

• CYA, or “say it with memos”

User Input

"listen.

understand that you are the expert, responsible for making sure both sides understand each other.

But there are many different solutions to any networking problem."

Completeness

Integration

"Have you covered all the functions needed?"

"Does it all work together?"

Implementation"Make sure it can be built."

Sequence of actions

(1) Identify key points in schedule

(2) Provide alternative plans for problems

• Plan • Build • Test • Turn over

Project “Hints”

• READ the lecture slides– Ask the user closed end questions– Don’t try to ask too much at one session– No preconceived scenarios

• Remember Inventory (equip., s/w, space)

• Tentative Design– Informal– High Level– Drawings are “Good Things”

More Hints

• Look in catalogs

• Report Format;– Problem statement: don;t just repeat what I said– Solution HIghlights

• Alternatives considered• Word Description (logical, physical)

• Bill of Materials– Specific Items (model, brand)– Costs aren;t very important