Computer Graphics Assignment: Diagrams and Code for 3D Projects (CMSI 371) - Prof. John Da, Assignments of Computer Graphics

An assignment for the computer graphics course, cmsi 371, during the spring 2008 semester. Students are required to create several diagrams, including a use case diagram, a structural diagram, and a user control diagram, for their graphics project. They are also encouraged to write initial code for the model and controller as extra credit. The diagrams should be clear, readable, and submitted in hardcopy, while the code can be committed to cvs under /projects/cmsi371/doc. The submission and evaluation of the work are based on the functionality and degree of difficulty of the committed code.

Typology: Assignments

Pre 2010

Uploaded on 08/19/2009

koofers-user-bft
koofers-user-bft 🇺🇸

10 documents

1 / 1

Toggle sidebar

This page cannot be seen from the preview

Don't miss anything!

bg1
CMSI 371
COMPUTER GRAPHICS
Spring 2008
Assignment 0313
Spring Break is the perfect time for hunkering down and working through an additional level of detail and
planning for your graphics project; this assignment hopes to give it a little structure.
Not for Submission
Read Chapters 10 and 11 in Angel for additional
information, details, and alternatives for 3D
object/scene modeling.
For Submission
Flesh out your graphics project a little bit more by
creating (and submitting) the following documents:
A use case diagram for your project
A structural diagram for the data needed by your
project (i.e., its model), including the approach
that you plan to use for the 3D or geometric in-
formation that will be displayed onscreen
A “user control” diagram that specifies how each
of your project’s use cases will be triggered (e.g.,
keypresses, mouse activities, etc.)
Note how these documents essentially define the
model and controller of your graphics project; most
of the remaining work focuses on the view, which
makes sense since this is, after all, a computer
graphics course.
You may use any tool that you find effective, in-
cluding hand-drawn sketches just make sure
that your diagrams are clear and readable. Thus,
submission for this assignment is on hardcopy.
If you do produce these diagrams electronically, by
all means commit them to CVS, under /projects/
cmsi371/doc.
For Submission (Extra Credit)
You will receive extra credit if you supplement
your design documents with enough initial code to
constitute a substantial beginning toward the im-
plementation your model and controller.
Your code must show a clear correspondence to
the plans laid out by your documents — this is no
longer a throwaway prototype, but the foundation
for your actual project. Focus on definitions and
implementations of the data structures and event
handlers specified by your use case, structural, and
user control diagrams. View-related code (i.e., the
display() function and all other directly-supporting
code) may wait.
I reserve the right to determine, based on the func-
tionality and degree of difficulty of the committed
code, whether your submission constitutes a “sub-
stantial beginning” (and thus whether you do get
the extra credit).
How to Turn it In
Commit your work to /projects/cmsi371, using
whatever directory structure you feel is needed to
expedite development.

Partial preview of the text

Download Computer Graphics Assignment: Diagrams and Code for 3D Projects (CMSI 371) - Prof. John Da and more Assignments Computer Graphics in PDF only on Docsity!

CMSI 371

C O M P U T E R G R A P H I C S

Spring 2008

Assignment 0313

Spring Break is the perfect time for hunkering down and working through an additional level of detail and planning for your graphics project; this assignment hopes to give it a little structure.

Not for Submission

Read Chapters 10 and 11 in Angel for additional information, details, and alternatives for 3D object/scene modeling.

For Submission

Flesh out your graphics project a little bit more by creating (and submitting) the following documents:

  • A use case diagram for your project
  • A structural diagram for the data needed by your project (i.e., its model), including the approach that you plan to use for the 3D or geometric in- formation that will be displayed onscreen
  • A “user control” diagram that specifies how each of your project’s use cases will be triggered (e.g., keypresses, mouse activities, etc.) Note how these documents essentially define the model and controller of your graphics project; most of the remaining work focuses on the view , which makes sense since this is, after all, a computer graphics course. You may use any tool that you find effective, in- cluding hand-drawn sketches — just make sure that your diagrams are clear and readable. Thus, submission for this assignment is on hardcopy. If you do produce these diagrams electronically, by all means commit them to CVS, under /projects/ cmsi371/doc.

For Submission (Extra Credit)

You will receive extra credit if you supplement your design documents with enough initial code to constitute a substantial beginning toward the im- plementation your model and controller. Your code must show a clear correspondence to the plans laid out by your documents — this is no longer a throwaway prototype, but the foundation for your actual project. Focus on definitions and implementations of the data structures and event handlers specified by your use case, structural, and user control diagrams. View-related code (i.e., the display() function and all other directly-supporting code) may wait. I reserve the right to determine, based on the func- tionality and degree of difficulty of the committed code, whether your submission constitutes a “sub- stantial beginning” (and thus whether you do get the extra credit).

How to Turn it In

Commit your work to /projects/cmsi371 , using whatever directory structure you feel is needed to expedite development.