ArgoUML:
- Notation: responsible for the notation of the diagrams, could be Java or UML notation
- Guillemet: responsible for the guillemets ( “<<”, “>>” ) of the diagrams
Freemind:
- Icons: responsible for the icons that can be put on the node of the mind map
- Clouds: responsible for the clouds that can be put around the nodes
Tetris:
- Next Piece Box: responsible for showing the next piece box on the game
BerkeleyDB:
- EnvironmentLock: responsible for locking the data base
- Checksum: responsible for validating the checksum of the operations
- TruncateDB: responsible for allowing the truncate of databases
- DeleteOP: responsible for allowing the delete operation on databases
- LookAHead
- Evictor
- NIO
House Structure:
Farmville:
- Dynamically turn off any calls back to the platform
Sales Scenario:
HealthWatcher:
- Persistence Mechanism (In Memory, Database (implies Transaction Mechanism))
- Transaction Management (optional feature, requires Database)
- Distribution (optional feature)
- Complaint (different options, such as Animal, Food, and so on)
- ...
Some design rules implemented using ecesarj
have been detailed
Some design rules implemented using escala are explained
here.
--
RodrigoBonifacio - 16 Aug 2010
--
RodrigoAndrade - 12 Aug 2010

Copyright © 2008-2025 by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
Ideas, requests, problems regarding TWiki?
Send feedback