aspose file tools*
The moose likes Agile and Other Processes and the fly likes all u need are use case, sequence, class & collaboration Big Moose Saloon
  Search | Java FAQ | Recent Topics | Flagged Topics | Hot Topics | Zero Replies
Register / Login


Win a copy of The Java EE 7 Tutorial Volume 1 or Volume 2 this week in the Java EE forum
or jQuery UI in Action in the JavaScript forum!
JavaRanch » Java Forums » Engineering » Agile and Other Processes
Bookmark "all u need are use case, sequence, class & collaboration" Watch "all u need are use case, sequence, class & collaboration" New topic
Author

all u need are use case, sequence, class & collaboration

Kishore Dandu
Ranch Hand

Joined: Jul 10, 2001
Posts: 1934
I feel all we need is use case diagrams, sequence diagrams, class diagrams and collaboration diagrams to go at a deliverable.
We can always go onto delivery related UML diagrams at the end of the cycle.
What you experts think??
Kishore.


Kishore
SCJP, blog
Lasse Koskela
author
Sheriff

Joined: Jan 23, 2002
Posts: 11962
    
    5
I'm not following you. Could you rephrase a bit?


Author of Test Driven (2007) and Effective Unit Testing (2013) [Blog] [HowToAskQuestionsOnJavaRanch]
Ilja Preuss
author
Sheriff

Joined: Jul 11, 2001
Posts: 14112
Originally posted by Kishore Dandu:
I feel all we need is use case diagrams, sequence diagrams, class diagrams and collaboration diagrams to go at a deliverable.

If you want to say that you need to produce all these before starting to code, I would say you might need much less.


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
Kishore Dandu
Ranch Hand

Joined: Jul 10, 2001
Posts: 1934
What I mean is those are all the diagrams/discussions about main parts of the system to realize a production worthy system.
(assuming u have very good coders handy, if not it does not matter which way you go).
Kishore.
Tonny Tssagovic
Ranch Hand

Joined: Dec 30, 2003
Posts: 226
How about non-functional requirements? like performance, and the illities like maintability .. how about other info like delivery date, and the technologies/methods/standards that must be follwed..where are u gonna put them, so one could "test" your system up against them?
Stan James
(instanceof Sidekick)
Ranch Hand

Joined: Jan 29, 2003
Posts: 8791
I like to think a lot about packaging, too. And we are forced to diagram deployment - how many servers in how many sites, what kind of state synchronization or data replication, etc.
You might enjoy Scott Ambler's Agilemodeling.com. He talks a lot about building only the models you really need, how to know what they are, good reasons for documentation and bad reasons. It all sounds related to your original questions.


A good question is never answered. It is not a bolt to be tightened into place but a seed to be planted and to bear more seed toward the hope of greening the landscape of the idea. John Ciardi
Kishore Dandu
Ranch Hand

Joined: Jul 10, 2001
Posts: 1934
I see not much enthusiasm for deployment related diagrams. What many high profile clients do is, hire a full time/consultant who is good at figuring out merits of partitioning, clustering and network management and go that route than wasting time of so called deployment diagrams.
I am not sure if there is a big practise to look into any performance related diagrams. But, I would consider them to be more looked upon when the actual implementation is 80% completed.
Kishore.
Ilja Preuss
author
Sheriff

Joined: Jul 11, 2001
Posts: 14112
Originally posted by Tonny Tssagovic:
How about non-functional requirements? like performance, and the illities like maintability

Those need to be addressed, certainly. But do they need to be formally documented?
.. how about other info like delivery date,

A release plan, regularly updated, is important, I'd think. I very much like the XP approach for this.
the technologies/methods/standards that must be follwed

I don't think those need to be documented, but lived (and adopted) by the team. Your mileage may vary...
 
With a little knowledge, a cast iron skillet is non-stick and lasts a lifetime.
 
subject: all u need are use case, sequence, class & collaboration