how to develop use cases for a project !

Question

1.00/5 (1 vote)

See more:

how to develop use cases for a project !
take a simple application,
kindly explain us.

this is will help us a lot.
and how to estimate a .net appliation.
is there any tools.

Posted 14-May-12 2:32am

jameschowdary

Add a Solution

2 solutions

Add a Solution

Add your solution here

Treat my content as plain text, not as HTML

Preview 0

…

Existing Members

Sign in to your account

...or Join us

Download, Vote, Comment, Publish.

Your Email
Password
Forgot your password?

Your Email
This email is in use. Do you need your password?
Optional Password

I have read and agree to the Terms of Service and Privacy Policy
Please subscribe me to the CodeProject newsletters

When answering a question please:

Read the question carefully.
Understand that English isn't everyone's first language so be lenient of bad spelling and grammar.
If a question is poorly phrased then either ask for clarification, ignore it, or edit the question and fix the problem. Insults are not welcome.
Don't tell someone to read the manual. Chances are they have and don't get it. Provide an answer or move on to the next question.

Let's work to help developers, not make them feel stupid.

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)

Prasad_Kulkarni · Answer 1 · 2012-05-14T02:39:00

Solution 1

Tips and guidelines for producing use cases:
A CP Article:Producing Use Cases[^]
Writing Effective Use Case[^]

Here you will get some good examples:
Writing effective Use Case and User Story Examples[^]
Use Case Templates[^]
UML 2 Use Case Diagrams[^]
Use Case Tutorial[^]

Posted 14-May-12 2:39am

Prasad_Kulkarni

Pete O'Hanlon · Answer 2 · 2012-05-14T02:41:00

You can't explain how to develop real use cases in the space of a single forum answer. There's just far too much to cover, and anything that we put in here would be too brief for you to get a real understanding. You might want to read this[^] article to give you some idea.

The second part of your question relates to project estimation, and this is based on many many factors, but really needs experience to tackle. How you estimate depends how you are going to run the project, e.g. is it Agile, how many stages you are splitting it up into, what counts as a phase? When it comes to estimation, I find that Project and Excel are my best tools.