Digging In (Later Monday)

Back in my office, I start looking at more details for the two major use cases:

  • Timing an Activity

  • Getting a Tally of the Data

I expand them a bit on two other sheets of paper and build a sequence diagram on my whiteboard.

I'm also starting to get an idea of how I'll design the code in the applet, using three classes. I draw a sketch of what the timer will look like on the screen:

Figure 4.7. Sketch of Product Interface.

graphics/04fig07.gif

And as I go, I think of more and more questions and issues: Is the activities list predefined and static? (Probably not.) Can each developer create a new list, or only access an existing list? Gary is unavailable, and I can only get hold of his voice mail, so I write down my questions for tomorrow.

By evening, I've built an applet that looks like this on the screen:

Figure 4.8. Screen Shot of Completed Product Interface.

graphics/04fig08.gif

I've also succeeded in writing some data for an activity on a text file, with all the testing I could think of (in true XP style). Not too bad for a single day of work.



The Rational Unified Process Made Easy(c) A Practitioner's Guide to Rational Unified Process
Programming Microsoft Visual C++
ISBN: N/A
EAN: 2147483647
Year: 2005
Pages: 173

flylib.com © 2008-2017.
If you may any questions please contact us: flylib@qtcs.net