Hotspots: Admin Pages | Turn-in Site |
Current Links: Cases Final Project Summer 2007
BwL ECoDE Cases
ECoDE is a tool designed to help Squeakers with the design process. You can write scenarios, CRC cards, assign method names to each responsibility in that CRC card, and then ultimately generate code for your program.
The first screen, "Analysis Mode". I'm not sure what the Goals part on the left is for. Here you can type in a scenario:
Scenarios are little stories to write on how a user would use your program. They usually start from the moment the user opens the program to when she closes it. There is just general usage and feature description in these, no dirty details on how we nerds will actually code the thing. Make them funny to keep yourself entertained. Using these in ECoDE was relatively straightforward and easy. Just make sure to press alt-S to save your paragraph! There's no warning if the window is closed and the text is not saved.
We can then enter in CRC cards:
CRC (class-responsibility-collaborator) cards are useful to make after you write scenarios. Here you get a bit more detailed (but not too detailed), by coming up with some general classes, what they should do (responsibilities) and what other classes they work with (collaborators).
After the Analysis mode, there's the Design mode:
Where we can assign method names to each scenario in a CRC card:
The last mode is program mode, where we can actually generate code. Because we started the code before using ECoDE, I didn't use this mode.
Observations of good features
- This system is a good idea for those just beginning a project. It'll allow you to share scenario and CRC card information in a Squeak environment.
- The code generation is a big help too for those starting from scratch.
- The system overall is stable.
Issues for Improvement
- What's the use for the "Goals" section? I couldn't figure it out.
- The CRC cards are nice, but they have alot of shortcomings. They should allow for long responsibility descriptions. "Just keep them short" is not a valid solution. Furthermore, there should be more than one collaborator allowed for a given responsibility. Some responsibilities just require them. If we make things too simplistic and nuclear, then things become overly confusing. Confusion doesn't lead to good design.
- The CRC cards are unprintable in their current state. Maybe the ability to export them out as a gif, much like how the Connectors UML diagramming program works. I think if the responsibility and collaborator sections were larger this would work well. Also, there's no necessity for the whole bottom section of the CRC card window.
This is a good system to use if you're starting from scratch, particulary for the code generation. There's nothing to compel you to keep on using it afterwards however. The analysis mode functionality, particularly the scenarios and CRC cards, can be done much easier with much less headache with Microsoft Word.
Return to our main Cases page: Bears with Lightsabers
Links to this Page
- Cases last edited on 30 July 2011 at 2:33 am by r59h132.res.gatech.edu
- Bears with Lightsabers last edited on 7 December 2003 at 1:59 am by ga-cmng-cuda1-c6a-a-78.atlaga.adelphia.net