Guidelines for project demonstration

What to demonstrate?

• Before beginning the demonstration, you must load the test data into your database or file(s).
• At the beginning of the demonstration, you must show that the data from the file(s) or database is available. You can demonstrate this by showing/viewing the data. You may be asked, at the beginning of the demo, to show a particular data from the test cases.
• The following (minimal set of) functionalities must be demonstrated - these are the most important functionalities for this application, and are derived from the problem description given at the beginning of the term. Please note that you will be asked to demonstrate any subset of the following requirements in random order.
  • Administrators must be able to add/modify/delete a new user (in all different types).
  • Borrowers must be able to search and check out an item
  • Borrowers must be able to pay the fines
  • Borrowers must be able to place on hold for an item
  • The system must be able to generate the return dates and billing information
  • Librarians must be able to add and delete an item
• At the closing of the system, all current information must be written back to the file(s) or database. You may be storing all the information as soon as a change is made, but you must demonstrate at the end that the information is written back onto the secondary storage for later use.
• You may have several additional functionalities. You can also demonstrate them after you show all the basic features of the application as described above.

For you to remember:

• You must bring in your requirements document for the demonstration. If you do not have your requirements document for the demo, you will lose some marks. This is because the requirements document is the contract between the customer and the developer and as a developer you are now demonstrating what the customer agreed earlier.
• All the team members must be present for the demonstration.
• You are responsible for bringing in all the tools that are necessary for your demo (may be your laptop, database, any additional software that you are using). If you wish, you can check with me before the demo schedule whether it can be demonstrated on my machine.
• You can invite others to watch your demo, if you wish.
• The maximum time for the demo is 15 minutes. This includes set-up time and question session.
• You must submit the following at the time of demonstration
  • Well-commented source code - print only the code that you (as a team) wrote; do not print any code that you used such as the database code or any part of the GUI that you did not write.
  • User manual - it should be brief and must be written for a novice user (in simple terms) explaining how to use the system.
  • Meeting logs - indicate what each person contributed to the code. This is important.
  • Signature page - This is important too.