Welcome!  Team AYB is a CS 4500 group at the University of Utah.  We're currently in the process of deciding on projects and constructing bids.  Go to the Documents section to see our bid information and other documents as we post them.

• Brochure Information

Current Test Script Failures

NONE!  Those test scripts helped us to find some important bugs.  Let's focus on writing more test scripts to catch more bugs.

Other observations: Most of the remaining work to be done is Jon's; Let's support him any way we can in finishing his work!

Please make sure that you run the automated test scripts after you change code, so that you don't unwittingly add bugs!

Top Ten Risks

1. Separation of tasks exposes us to failure if one team member is somehow unable to complete his part (e.g. spontaneous combustion...).
       - Valid; some team members have gone on vacation, impeding the project's progress.
2. Time constraints might prevent us from being able to implement all of our features.
       - Valid; We have had to drop the PocketPC support, and may need to drop the Reporting features.
3. We're using JasperReports and don't know how well it will work with our database.
4. The GUI programmers aren't yet familiar with JFC/Swing.
       - No longer a significant risk.
       - Solution: Jon learned JFC/Swing, and GUI responsibility was shifted to him.
5. Because each component will be written separately and then integrated, there is a risk that the parts won't work well together when the time comes.
       - Not a significant risk; It's worked well so far.
6. None of us has used Java to program a PocketPC before, and we don't know what issues might come up because of that.
       - Resolved; We weren't able to find a good JRE for the PocketPC that uses JFC/Swing.
       - Solution: We have decided to drop PocketPC support, and stick with the desktop version.
7. Only one of us has a PocketPC, and it's not the chief GUI programmer, so we are relying on our ability to find a working emulator.
       - Resolved; We weren't able to find an emulator, or even a good JRE for the PocketPC that uses JFC/Swing.
       - Solution: We have decided to drop PocketPC support, and stick with the desktop version.
8. We're using Ingres for our database software, and we don't know how well that will work with our server software.
       - Not a risk; works like a charm.
9. If we overestimated the time we'll need for features, we might finish before deadline and be compelled to add functionality with what time we have left. (Danger=potential for added bugs)
       - Not a risk; We've encountered quite the opposite.
10. The idea of putting the logic for retrieving data from the database into the class library may present unexpected issues.
        - Not a risk; This has proven to be a good choice.

Team Members

• James Jensen
  • Email: j a m e s j @ c s . u t a h . e d u
  • Personal Log: http://ayb2005-james.blogspot.com/
  • Responsibilities:
    • Team Leader
    • Webmaster
    • Documentation & Reporting
• Greg Nelson
• Email: g r o u r k @ g m a i l . c o m
• Personal Log: http://ayb2005-greg.blogspot.com/
• Responsibilities:
  • Client-to-host Architecture
• Jon Richardson
  • Email: p o p a t r @ y a h o o . c o m
  • Personal Log: http://ayb2005-jon.blogspot.com/
  • Responsibilities:
    • Testing, Coding, and Code Review
• Peter Kingston
  • Email: k i n g s t o n . p e t e r @ g m a i l . c o m
  • Personal Log: http://ayb2005-peter.blogspot.com/
  • Responsibilities:
    • Database Interface
    • Software Design Leader

Meeting Time

We are scheduled to meet with Professor Henderson in his office (MEB 3450) at 3:05 each Friday.  Don't be late!

Project Log

Project Log:    http://ayb2005.blogspot.com.