Software Engineering

Demo #2 -- Iteration 2(b) --  (date listed here)

This demo should show your accomplishments for the entire course. The structure and grading criteria for the demo are the same as for the demo #1.

1.   Product Brochure

Each team should bring to the demo a one-to-two-pages advertising leaflet providing basic descriptive information about the software product they developed. No more than two (2) pages are allowed! At the least the brochure should include the group number and members' names, project title, project webpage URL, the list of features and short description of each feature, system requirements to run the system, etc. Please keep in mind that this is a marketing brochure, not a technical document.

2.   Demo Format

You should demonstrate the functional features of your software product. Please avoid demonstrating login, user authentication, and creating new user accounts. Focus on highlighting your achievements after the first demo. Of course, you need to demonstrate the functions in context, but put emphasis on your new accomplishments (after the first demo).

The demo format is as follows:

1. Give a short verbal overview of the product -- who and what is it for
   Please avoid slide presentation in demo #2. Rather, use live demonstration to show the product functionality.
2. Highlight one, two, or three key features/functions:
   1. Briefly describe what the function does
   2. Demonstrate how the user uses it
   3. During the demonstration, highlight important aspects, such as user interface design, what is going on at the application's back-end, etc.

The most important thing for the demo is that you want to impress the audience with your technical achievement for this semester. You want to impress the audience that:

• You are addressing an important problem
• The problem presents technical challenges, which you have successfully tackled
• Your solution employes sophisticated software engineering techniques
• This product is easy to understand and operate/use
• This product is reliable and professionaly developed

3.   Demo Schedule

Final Demo Room is at D110, Engineering Building D-Wing.
Please contact the TAs by email ASAP requesting a time slot for you to give the demo. When contacting the TAs, put the request title in the subject line so that they can speed up the work.
This table shows the current demo reservation schedule.

The demo should last no more than 18 minutes. Make sure your demo is ready before it starts; as you can see, the schedule is tight and I'll not be able to wait until you get ready. See the TA before the demo if you need to install and try it.

NOTE: It is required that all group members be present for the demo and each member takes part. Demo presentations are open and anybody interested is free to attend. However, you are not required to attend other groups' demos.

4.   Grading

Make sure to email us the breakdown of individual contributions immediately after the demo.

See also the grading policy for the assigning the overall team grade vs. grades for the individual members.

The demo will be graded as follows:

Aspect	Points	Explanation
Functionality / Task complexity	15	Emphasize the key functions of your system, what are they useful for. Show that this is a non-trivial project that required a team of smart students working for a full semester.
Programming, not webpage design	15	You must convince us that programming has been central for your project development and webpage design has only been ancillary.
Software reliability	10	"Software reliability" means that your software runs without crashing and, generally, it does not display unintended behavior or bugs.
Presentation quality	10	Impress the audience that you have developed a useful, non-trivial product, that only a highly trained software engineer can do.
User Interface / Ease of use	10	"Ease-of-use of the user interface" should not be confused with a flashy interface. On the contrary, you should avoid flashy user interfaces. "Ease-of-use" means that interface is easy to understand and operate. A minimal user interface that is well organized should be sufficient.
Novelty/ Usefulness	10	Demonstrate that you have invented at least something, some part of your product, rather than plainly copying an existing idea.
Product brochure	5	Informativeness and general appearance of the product brochure.
Total points	75

NOTE: Please keep in mind that the grades are assigned competitively, i.e., the group that is perceived as the best receives 100 % and the others are scaled relatively to this.

• Course home page
• Course syllabus page