1 / 13

Project

Project. Purpose Options Network Design Software (?) Approach {customer/boss/professor} Teams {prefered size is 3}. Project Phases. "almost a joke, but too often true!". 1. Enthusiasm 2. Disillusionment 3. Panic 4. Search for the Guilty 5. Punishment of the Innocent

myra-buchanan
Télécharger la présentation

Project

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Project • Purpose • Options • Network Design • Software (?) • Approach {customer/boss/professor} • Teams {prefered size is 3}

  2. Project Phases "almost a joke, but too often true!" 1. Enthusiasm 2. Disillusionment 3. Panic 4. Search for the Guilty 5. Punishment of the Innocent 6. Praise and Honors for the Non-participants

  3. Project Schedules "don't let yourself plan like this" Start End * * A miracle occurs

  4. Network Design • An iterative, interactive process "you have to ask questions, & you'll never get it all in one meeting with the customer" • More than just selecting the media "remember you're designing a system -- make sure you look at something 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 you feel is technically best."

  5. Network Design,cont "Do them in order. Each step is important" Time • 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

  6. Functions "the 2 main reasons for a network are connectivity and resource sharing" Connectivity • Remote login Software Management Electronic Mail File Sharing • Transfer • Virtual disk/files Resource Sharing • Printers/plotters etc • Modems • CPU • Disk

  7. Resources "Remember to be precise!" Systems Qty Mfg Version Software Geography Distances Constructions Standards

  8. 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”

  9. 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."

  10. Completeness "Have you covered all the functions needed?" Integration "Does it all work together?"

  11. 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

  12. 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”

  13. 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

More Related