Trees
Home page for the trees project. (Draft).
When you write up your work, use plain ascii text - not MS word or
html. Eventually this material will be posted on the wiki, which
provides minimal but sufficient formatting tools. For a sense
of what scenarios (short stories) might look like, check out what the
cs410 class did last
year, at the KICS project
wiki.
(That page may move any day now. You should always be able to find it
somewhere in the top level cs410
wiki.
- The handout Marc Welch
intended to bring to his presentation. You will find this very helpful!
-
We've divided ourselves into four teams for these tasks. It's too much
to ask that they be completed by Tuesday 2/6, but I will expect a
progress report from each team then.
- EmergencyRequest. Write draft of scenario(s) when a citizen
phones with a tree emergency.
- ServiceRequest. Write draft of scenario(s) when a citizen
phones with a query for tree service of some kind.
- Marc's actions (I've forgotten what WikiWord we chose for
this). Write drafts of scenarios illustrating the ways in which Marc
interacts with the system. (Less carefully specified than the two
previous kinds of scenarios, so will require more feedback from Marc.)
- What's out there? Investigate existing ticket systems and bug
tracking systems to see whether we can borrow/use design ideas or code
or even whole applications.
- What's in a name? Actually, quite a bit. So everyone in the
class should come next Tuesday with at least two catchy names for the
application we're building. A good name is easy to remember, describes
what the application does, and has a cool acronym or abbreviation -
preferably one for which the domain whatever.com or whatever.net is
not in use. For some ideas, look at the project names graduate SE
students chose for their projects (you can find them at
www.cs.umb.edu/Student_Research_Projects/Student_Research_Projects.htm
and in links to cs681 from my home page).