Fall 2003 Software Project

1
Fall 2003 Software Project

• Divide into teams of about 4-5 people per team to
  perform
• project planning
• project organization and coordination
• performing the actual software development
• monitoring and assessing the status
• reporting on the status and making necessary
  adjustments
• deliver a final project experience summary
• The deliverables requested by the instructor
• Plan
• quick plan (from everyone individually) -
  9/11/2003
• a more comprehensive team plan (from the team) -
  9/30/2003
• Organizational setup or action plan
  presentation by the team ( 10/7/2003 -
  10/9/2003 )
• process and methodologies
• people assignments and tasks to be performed
  schedule
• tools, specific methods and systems to be used
• specific goals and metrics to be used for
  monitoring

2
Fall 2003 Software Project (cont.)

• Weekly or bi-weekly monitoring status reports by
  each team (10/14 -11/20)
• 10 - 15 minutes status reports based on the
  metrics chosen for monitoring
• discussion on adjustments that was necessary
• if necessary, a chunk of class time will be set
  aside for this
• if necessary, discussion with instructor (office,
  e-mail, etc.) can be set aside for this
• A final report on the project experience by the
  team - (11/20 -11/25)backed by data from the
  project
• a written part
• oral part to be presented to class
• a quick demo of the final product

3
Final Report/Presentation - Fall 2003

• Content
• Goals
• Actual Achievements vs the Goals
• Methodology/Process used
• Suggestions for future Product/Process
  Improvements
• Summary of (weekly)Monitored Data Adjustments
  Made
• Open Issues and Non-resolved issues
• Others

4
The Software Development Part

• The Actual Problem
• A hospital is finding out that their billing to
  the in-patient customers are often challenged due
  to inaccuracy such as wrong room charge, wrong
  doctors fee, wrong dates, extra medication
  charge, even wrong medical procedure! They
  approached your team to develop something that
  can get them out of this mess and embarrassment.
• Your team is to propose and develop a software
  solution for this hospital.
• It also occurs to you, as astute business
  managers, that this may not be an uncommon
  problem among hospitals ---- may be you can sell
  this to many other hospitals if the system is
  made to be more robust (extensible).
• You have the opportunity, as a team, to decide on
  the software requirements and put it in your
  plan. As the project proceeds, you are allowed to
  request and recommend adjustments based on your
  status.
• Be realistic on what the team can develop and
  finish
• Consider the amount of time you will be spending
  in the management of the project