Topics for Exam 2 in Com S 362

This test covers topics from homeworks 2, 3, and problems 1-5 from
homework 4.

REMINDERS

This test is open book and notes.  However, it is to be done
individually and you are not to exchange or share materials with other
students during the test.  So if you have materials on your team
project you wish to refer to during the test, please make copies.

If you need more space, use the back of a page.  Note when you do that
on the front.

This test is timed.  We will not grade your test if you try to take
more than the time allowed.  Therefore, before you begin, please take
a moment to look over the entire test so that you can budget your
time.

For diagrams and programs, clarity is important; if your diagrams or
programs are sloppy and hard to read, you will lose points.
Correct syntax also makes some difference.


READINGS

Principally, chapters 1-9 of Craig Larman's "Applying UML and
Patterns: An Introduction to Object-Oriented Analysis and Design and
the Unified Process", Second Edition. Prentice Hall PTR, Upper Saddle
River, NJ, 2001. Also read chapters 1-3 and 5 of Martin Fowler
with Kendall Scott's book UML Distilled (Addison-Wesley Longman, Inc.,
Reading, MA, 2000).  Finally, as an example look at the web page for
the StickSync project:

  http://www.cs.iastate.edu/~cclifton/courses/sticksync/vision.shtml

If you have more time, see the syllabus for further readings.


TOPICS

Topics marked + below are more important than topics marked - below.
Topics marked with a ++ will almost certainly be on the test.
In general, things that are more like the homework will be more important.

* Overview
     + Explain iterative development and its advantages and disadvantages
     - Explain the phases of a typical development,
       how long each phase is (relative to the others),
       and what is involved in each
     + Explain what kinds of systems object-oriented techniques should
       be used for, and which ones they should not be used for.

* Inception phase
     - Explain the goals of the inception phase.
     + Be able to write a vision and business case. [HW2, HW3]
     - Be able to write a glossary. [HW2, HW3]
     ++ Be able to write clear use cases in an essential, UI-free, style,
         in brief, casual, and fully-dressed formats. [HW3, HW4]
     + Be able to apply the elementary business process guidelines. [HW4]
     + Be able to find and write non-functional requirements 
       in a supplementary specification. [HW3]
     + Be able to identify risks in a system. [HW3]

* Elaboration Phase
     + Be able to draw a system sequence diagram for a scenario of a use case.
       [HW4]