What steps need to take after UC

[sc_kew]

What further steps / documentation I need to take when the Use case description have been completed? How do I know the programmer is fully understand the functionality of the system as the Use Case is only explain to them what the system should do BUT not how the system should do?

Please advise me!

Yours,

SCK

[thomaskilian]

Hi,
this is really a long story.I would recommend http://www.usecasemodeling.com/. To put it very short: relate all requirements to the use cases.  Write down the flow of events (basic and alternates). Create use case realizations for all use cases. Model your classes with sequence diagrams to fill them with life. If there is time use prototypes to gain feedback from your programmers to the users.

The ICONIX CD purchased at Sparx shows in brief how you can step from use cases to code without worrying too much about all the zillion possibilities of UML. This can help you the short way. However, I recommend reading the book anyway.

[angel-o-sphere]

Besides the suggestions of thomaskilian you can start writing scenarios.

That means you cut out the main flow or alternate flows from the UCs descriptions and fill them with sample data.

They should be equivalent to sequence diagrams. Later they are used as test cases.

Depending on the coding environment (how skilled the developers are) this should be enough. However: making sequence diagrams leads you towards a first class model. Which can be generated.

How do you make sure your UCs are the one you want? Thats a far more interesting question than: how do you make sure the coders do you understand?

You have to go to scenarios or sequence diagrams ... because you will realize flaws and complicated flows while crafting them and you likely will want to rework the UCs.

If you use Sequence Diagrams the reworking will lead to an evolving class model ... so a skelleton of the application is allready crafted during analysis. If you give the UCs imediatly to the coders they will spend a lot of time to get the vocabulary and the requirements. But if they allready have worked in a similar project with the same vocabulary they likely won't *need* more.

angel'o'sphere