Class Meeting: More Teams; Software Process Models
Admin
mention class notes over at Student Stores
make to make a meatball if you want it there
make sure your producer has a "mailto" link next to his/her name on
your team page... this will make it easier for me to contact the producer
Class disk space... here is the location:
/afs/unc/project/courses/comp145/s00
Put your project Web home in the shared space... use the naming
convention "web/index.html" for the page name... use symbolic links
to get to them; for example:
cd ~/public_html
ln -s /afs/unc/project/courses/comp145/s00/bball/web/index.html
./dlearn.html
I will install symbolic links in my area for reference in the Class homepage.
Contracts, first draft, due on-line today. I will
look it over and get comments to the team for revisions.
Schedules due next time... make sure they are linked to your
project web page.
Remeber I wanted 3 items: Work-breakdown structure,
PERT chart, Gantt chart. If you have used software to generate these,
make a note on your schedule page(s) of the name of the package(s).
no one organization is best for all projects (like no one process
is best)
decentralized control is best when detailed and extensive
communication among engineers is necessary for achieving a good solution
Centralized control is best when time for development is short
and the problem is well understood
A good organization tried to limit the amount of communication
to what is necessary for acomplishing the project goals -- no more,
no less. "Need to know" organization
A good organization may well depend on factors other than speed of
development:
lower life-cycle costs
reduced personnel turnover
repeatability of the process
development of junior engineers into senior
widespread dissemination of specialized information and
expertise among engineers