Fall 2006 Lillevik 480f06- l10 1 University of Portland School of Engineering CS-EE 480 Senior Design Lecture 10 Webs Scheduling MS Project (Optional)
Fall 2006
Lillevik 480f06-l10 1University of Portland School of Engineering
CS-EE 480
Senior DesignLecture 10
Webs
Scheduling
MS Project (Optional)
Fall 2006
Lillevik 480f06-l10 2University of Portland School of Engineering
CS-EE 480
Frontpage overview
• WYGIWYS application similar to word processor
• Supports theme paradigm– All the hard work is done for you– Do not spend time customizing
• Publishes only changed files• Three views: Page, Folders, Navigation
Fall 2006
Lillevik 480f06-l10 3University of Portland School of Engineering
CS-EE 480
Frontpage hints
• Maintain local (C: or P:) copy not on server
• Use theme called UP engr
• Don’t work at HTML level
• Use publish web feature, NOT ftp
• Navigation view allows adding new page
• Insert hyperlink to reference docs
• Preview locally with browser to test
Fall 2006
Lillevik 480f06-l10 4University of Portland School of Engineering
CS-EE 480
Page view
Current Page
Place name here
Change date for revisions
Fall 2006
Lillevik 480f06-l10 5University of Portland School of Engineering
CS-EE 480
Navigation view
Use this view to add or move a page
View Navigation
Fall 2006
Lillevik 480f06-l10 6University of Portland School of Engineering
CS-EE 480
Folders viewPut .doc files here
Put meeting minutes here
Put .ppt files here
Put .mpp files here
Save data in various folders
Put data files here
Fall 2006
Lillevik 480f06-l10 7University of Portland School of Engineering
CS-EE 480
Inserting a hyperlink
Insert Hyperlink
Fall 2006
Lillevik 480f06-l10 8University of Portland School of Engineering
CS-EE 480
Documents page
Place hyperlinks to documents
Fall 2006
Lillevik 480f06-l10 9University of Portland School of Engineering
CS-EE 480
Meetings page
Place hyperlinks to meeting minutes
Fall 2006
Lillevik 480f06-l10 10University of Portland School of Engineering
CS-EE 480
Presentations page
Place hyperlinks to PowerPoint files
Fall 2006
Lillevik 480f06-l10 11University of Portland School of Engineering
CS-EE 480
Schedule page
Place hyperlinks to schedule and milestone files
Fall 2006
Lillevik 480f06-l10 12University of Portland School of Engineering
CS-EE 480
Design page
Place hyperlinks to data files
Fall 2006
Lillevik 480f06-l10 13University of Portland School of Engineering
CS-EE 480
• Do not use ftp, use File Publish Site
• Map a drive T:\\lewis\teachingwebsite$
• Remote locationFile System
T:\\SRDesign\AY07\projectName
• Click: Local to remote
Publishing
Fall 2006
Lillevik 480f06-l10 14University of Portland School of Engineering
CS-EE 480
Publishing your web
NOTE: UP password must be used
Fall 2006
Lillevik 480f06-l10 16University of Portland School of Engineering
CS-EE 480
Off-campus
• Must run VPN client
• Not required on campus
Fall 2006
Lillevik 480f06-l10 17University of Portland School of Engineering
CS-EE 480
Starter webs
Project web sites created
See Reference page in class web site
Fall 2006
Lillevik 480f06-l10 18University of Portland School of Engineering
CS-EE 480
How to create a schedule
• Start with major tasks, then break into smaller tasks
• Identify the dependencies
• Assign ownership
• Enter into MS Project
Fall 2006
Lillevik 480f06-l10 19University of Portland School of Engineering
CS-EE 480
Classic tasks
• Design: create a solution of several units
• Simulate: see if model works
• Build, code, fab: make it real
• Unit testing: stimulate unit and observe result
• Debug: fix something
• Integration: put the pieces together
• System testing: test the entire project
Fall 2006
Lillevik 480f06-l10 20University of Portland School of Engineering
CS-EE 480
Unit development
A single unit often requires iterative steps
OK?
Done
Debug
Design Model SimulateStart
no
yes
TestBuild
Fall 2006
Lillevik 480f06-l10 21University of Portland School of Engineering
CS-EE 480
Integration & sys test
Prototype results from integrating the units
Unit
Unit
Unit
IntegrateSystem
TestOK? Proto
Debug
yes
no
Fall 2006
Lillevik 480f06-l10 22University of Portland School of Engineering
CS-EE 480
Scheduling terminology
• PERT: program evaluation and review technique
• CPM: critical path method
• Task: activity
• Milestone: point in time that measures progress
• Critical path: sequence of tasks that can not be delayed or project will be delayed
• Slack time: time a task can be delayed without changing the critical path
Fall 2006
Lillevik 480f06-l10 23University of Portland School of Engineering
CS-EE 480
Optional Lecture Material
Fall 2006
Lillevik 480f06-l10 24University of Portland School of Engineering
CS-EE 480
Using MS project
Tool for creating and tracking a schedule
1. Create a new, blank project
2. Create tasks, milestones
3. Insert dependencies
4. View or print summary
5. Update with new information
Fall 2006
Lillevik 480f06-l10 25University of Portland School of Engineering
CS-EE 480
Scheduling hints
• Adjust the level of detail– Avoid too much, too little– Suggestion: 1w < task < 2w
• Tasks– Don’t enter fixed dates !!! (except end)
– Use ASAP priorities, don’t mix with ALAP– Exercise conservatism, not optimism
Fall 2006
Lillevik 480f06-l10 26University of Portland School of Engineering
CS-EE 480
Scheduling hints, continued.
• Exploit parallelism
• Resource management– Don’t over commit– Avoid idle time
• Consult experts
• Baseline to other projects
Fall 2006
Lillevik 480f06-l10 27University of Portland School of Engineering
CS-EE 480
Using MS project
Tool for creating and tracking a schedule
1. Create a new, blank project
2. Create tasks, milestones
3. Insert dependencies
4. View or print summary
5. Update with new information
6. Save project often, back it up
Fall 2006
Lillevik 480f06-l10 28University of Portland School of Engineering
CS-EE 480
Creating new project
file new blank project
Fall 2006
Lillevik 480f06-l10 29University of Portland School of Engineering
CS-EE 480
Saving your filefile save as
Fall 2006
Lillevik 480f06-l10 30University of Portland School of Engineering
CS-EE 480
Schedule views
• Gantt chart– Text and bar graphics– Less cumbersome, suggested view to use
• Pert chart– Also called network diagram– Flowchart format, boxes & arrows– Easily overwhelms the screen
Fall 2006
Lillevik 480f06-l10 31University of Portland School of Engineering
CS-EE 480
Adjust time scaleformat time scale
Middle to months
Bottom to weeks
Fall 2006
Lillevik 480f06-l10 32University of Portland School of Engineering
CS-EE 480
Insert a task
insert new task
project task information
Fill in the blanks for
the various
tabs
Milestone is a task with zero duration
Fall 2006
Lillevik 480f06-l10 33University of Portland School of Engineering
CS-EE 480
Properties of a task
• Title: unique, descriptive name• Owner: who is doing the work• Duration: how long will it take• Type: as soon as, as late as• Dependencies: predecessor tasks• Successors: follow-on tasks• Cost: $$• Priority: H, M, L
Fall 2006
Lillevik 480f06-l10 34University of Portland School of Engineering
CS-EE 480
Task properties
Use ASAP only !!
Fall 2006
Lillevik 480f06-l10 35University of Portland School of Engineering
CS-EE 480
Resource list
tools assign resources
project task information
Fall 2006
Lillevik 480f06-l10 36University of Portland School of Engineering
CS-EE 480
Simple project: no dependencies
Fall 2006
Lillevik 480f06-l10 37University of Portland School of Engineering
CS-EE 480
Adding dependencies
project task information
Fall 2006
Lillevik 480f06-l10 38University of Portland School of Engineering
CS-EE 480
Dependencies added
Project Gantt chart
Fall 2006
Lillevik 480f06-l10 39University of Portland School of Engineering
CS-EE 480
Network (Pert) view
View helpful but offers too much detail
Fall 2006
Lillevik 480f06-l10 40University of Portland School of Engineering
CS-EE 480
Tracking Gantt view
Critical path shown in RED
Fall 2006
Lillevik 480f06-l10 41University of Portland School of Engineering
CS-EE 480
Generating reports
view reports project summary