Books: Pragmatic Unit Testing in Java, Agile Java, Modern C++ Programming with TDD, Essential Java Style, Agile in a Flash. Contributor, Clean Code.
Originally posted by Tonny Tssagovic:
I beleive that drawing the GUI (menus) and arrows showing the flow of the different steps will make much more sense then writing a lot of verbose Use cases. What do you think?
An other question is (assuming I have to write use cases) how many of them should there be? Shall I have a use case to view Tenis results and an other to view Football results and yet an other for Formula 1 or just one "view today's sports results" use case, and then where is the football/tenis going to be in the use case diagram?
Now I have been told) (a long time ago) that use cases show the interaction beetween the actor and the system in question, Kind of user input and system response table. In this case, I have a use case with the user (actor) choosing to viw some info from his mobile (system). This is quite simple and the real big thing actually happens in the server side, and there are many components (just simple servlets +EJBs or simple objects) on the server side. Should I write a use case for these "sub-systems" (components) or they just appear in the sequence diagrams?
In this case some other component might be actors using other systems part, and one has to describe the requirements provided by this later component hmm it seems I have a headache
Please help :roll:
The soul is dyed the color of its thoughts. Think only on those things that are in line with your principles and can bear the light of day. The content of your character is your choice. Day by day, what you do is who you become. Your integrity is your destiny - it is the light that guides your way. - Heraclitus
Originally posted by Tonny Tssagovic:
Well What I want from my use cases is to please my teacher(ok maybe not).
I would like to send these use cases to a team on a far-away country for outsourcing, and really don't want to loose too much time on communication overhead.. I have once used more time to explain to a guy via chatting/e-mails what to do then I would probably have used to do it myself (and much better solution and performing code of course).
I also want my use case diagram to look cool, for a school report.
Books: Pragmatic Unit Testing in Java, Agile Java, Modern C++ Programming with TDD, Essential Java Style, Agile in a Flash. Contributor, Clean Code.
Originally posted by Tonny Tssagovic:
Thanks for your replies Jeff and Ilja
Well What I want from my use cases is to please my teacher(ok maybe not).
I would like to send these use cases to a team on a far-away country for outsourcing, and really don't want to loose too much time on communication overhead.. I have once used more time to explain to a guy via chatting/e-mails what to do then I would probably have used to do it myself (and much better solution and performing code of course).
The soul is dyed the color of its thoughts. Think only on those things that are in line with your principles and can bear the light of day. The content of your character is your choice. Day by day, what you do is who you become. Your integrity is your destiny - it is the light that guides your way. - Heraclitus
With a little knowledge, a cast iron skillet is non-stick and lasts a lifetime. |