|
Prev: Call for Papers: The 2008 International Conference of Systems Biology and Bioengineering (ICSBB 2008)
Next: CFP: DATICS 2008 - Design, Analysis and Tools for Integrated Circuits and Systems
From: linq936 on 28 Jan 2008 00:58 Hi, I am learning UML design methodology and like to apply it in the forthcoming project. This project has a very simple GUI interface while the backend is pretty complex. I am using Use Case diagram to capture the functionalities. Since the GUI is simple, it turns out the highest level use case diagram is simple. Then I go to model the use case for each individual internal package. Basically I isolate each package as a system, the related packages as actors and try to come up all the use cases for the package. After working some packages out, I find that actually I am defining API set for each package -- if I just use "_" to replace " " in the names of the use cases, add return type and argument list, they become API for that package. I think this is all right. But I am wondering a bit if this is correct. Am I going too far too quick? Am I still on the right track? |