CS-321 Lab 3: Introduction To the Graphics Shell

This is a 1-week lab. Please refer to http://people.msoe.edu/~cs321/lab3.shtml [no longer online] for the lab details.

UML Class and Sequence Diagrams

Before writing your code for this week, model your existing work and develop your design using a UML editing tool. Specifically, use** Visio (Windows) or Dia (Windows or Linux***) to prepare a UML class diagram and a UML sequence diagram.

Your model must contain enough detail to support a non-trivial example of using your classes. For example...

• Writing a file with multiple shapes of two types (could be initiated by a function in your class derived from Shell; not required this week)
• Clicking the mouse to create and draw a new point
• Drawing an image (diagramming this requires a partial model of QPainter)

Feel free to propose another example for diagramming to the instructor.

Save your graphics (1 class diagram and 1 sequence diagram) in PNG format at a reasonable resolution for on-screen viewing and reference them so that they appear in your XML report (File|Save As in Visio, File|Export in Dia). In your report, give the user an overview of the diagrams with additional information not obvious from the diagrams -- do not simply re-tell the user what the UML diagrams already convey.

**If you prefer, you may instead use Rose, a much more powerful tool that you have access to while on campus (the Department has 100 licenses managed by a license server). Rose has a shallower learning curve (meaning that it takes longer to gain proficiency), but is also much more powerful. Rose has a Web Export feature that, among other things, generates PNG versions of all diagrams.

***If dia is not available (dia& from command prompt), execute `up2date dia` as root to install it on your Linux setup.

Other Requirements

These requirements are in addition to those listed on the common lab page linked to above.

• Override the Erase function from Shell so that the user may erase the image by pressing the Erase button. This should cause the image object to become empty and the drawing shown on the screen to become blank.

Note: It is not necessary to handle loading and saving, but these features will be required in future labs, so you might want to get a start on them.

Demonstration (during week 5 lab)

You will need to demonstrate your project to the instructor during the week 5 lab meeting. The demonstration will count for 25% of your project grade.

Lab report (due 4 P.M., the day prior to week 5 lab)

Your lab report need not be self-contained. This means that it is not necessary to restate the entire specification in your report.

• Prepare your report in the XML format described in the Electronic Submission Guidelines.
• Include...
  • a brief overview of the assignment;
  • details of any problems you encountered;
  • suggestions for how the lab could be improved;
  • things you could not figure out how to do;
  • a list of extra features that you implemented, if any;
  • a tally of the number of Non-commented new Lines Of Code (NLOC) written for this lab assignment. Follow the requirements for this item from lab 2.
  • A summary of your activity log indicating how much time you spent on the assignment. Follow the requirements for this item from lab 2.
  • Documented source code—See lab 2 for information on gensrc, which helps format your code for your XML report.
    • If a file has not changed since the last assignment, note this in your report and do not include the unchanged file.
• Follow the report submission requirements.
• Email this file to the instructor (durant@msoe.edu) with a subject and message body indicating that this is your CS-321 Lab 3 submission.

If you have any questions, consult the instructor.