CS182 -- Lab 6: Graphical User Interface Programming



->Courses
->CS182
-->Objectives
-->Homework
-->Quiz 1
-->Lab 1
-->Lab 2
-->Lab 3
-->Lab 4
-->Lab 5
->Lab 6
-->Project
->Electronic Submission
->Old Exams
->C++ Examples
->MSVC Info
->Software
->Tentative Schedule
->Support Forum
->Course Policies

[Courses]
[Rich][Home][Rich]
[Author]

Winter Quarter 2002-2003

Overview

The purpose of this lab is to provide exposure to Graphical User Interface (GUI) programming.

Procedures

Create the GUI application discussed in class by following the step by step instructions. Then develop your own GUI application. This may involve making modifications to the current application or creating an entirely new application. Some of you may choose to create a GUI version of a previous lab assignment. If you have any questions on what is appropriate, please ask your instructor.

Program Demonstration (beginning of week 8 lab)

You will be required to demonstrate your program at the beginning of the week 8 lab session. Programs that are not ready to be demonstrated at the beginning of the lab session will be considered late.

Lab report (due 11:00pm, the day prior to week 8 lab)

The lab report for this week should be rather brief in order to give you more time to explore GUI programming. The report should consist of an image of the GUI and four paragraphs containing:

  • What you did.
  • Why you chose to do what you did.
  • What you learned.
  • What you would have done differently if you had to do it again. Also, please include any suggestions you may have on how to improve this lab in the future.
  • At least one screen shot from your GUI application (save as 182msoeloginL6.png where msoelogin is your msoe login).
  • An activity log indicating how much time you spent on each phase of the assignment. You should use the format found in the template XML file and report the time in the following categories:
    • Design
    • Coding
    • Debug (before you think it's working)
    • Test (after you think it's working)
    • Writing Report
    • Other
  • Documented source code for your program. (Include all .cpp and .h files that you modified.)

As with any report you submit, correct spelling and grammar are required. In addition, your report should be submitted electronically following the Electronic submission guidelines. (You may wish to consult the sample report before submitting your report.) Be sure to keep copies of all your files, in case something gets lost. It may be wise to keep a diskette backup as well.

Your grade will depend on quality of design, clarity of code and documentation, as well as whether your program produces the correct results. If you have any questions, consult your instructor.

© 2002 Dr. Christopher C. Taylor Office: CC-27C Phone: 277-7339 Last Updated: Mon Jan 27 06:09:21 2003
I am responsible for all content posted on these pages; MSOE is welcome to share these opinions but may not want to.