[bashirnmt]

Dear,

How can we provide guidance to the systems analyst working on a project about how he should check that the use case diagram is correct or not? What are the key points of checking a case diagram? What is he required to do next or what shall be done next?

Thanks

This post has been edited by bashirnmt: 06 August 2011 - 06:58 AM

[Martyr2]

How can he check if a use case diagram is correct? Ask him to tell you the process of steps using the diagram. If he can correctly go through an entire case telling you each step and in the correct order, then the case diagram is correct.

Remember the diagram is to visually explain the processes in a system. For instance, I hand you a use case about an ATM machine. Then I tell you how would a person go through the process of making a withdrawl. Using only the diagram, you should be able to tell me step by step, in order, how someone would interact with the system.

If you can tell me all the steps in the correct order using only the diagram, then it is correct.

That or they should be able to tell you which systems talk to which systems without a sense of time (which would have been done in a sequence diagram). Same example with the ATM, he should be able to tell you that if you put in an envelope for a deposit, the money tray should contact the deposit subsystem which talks to the account class and invokes a deposit method which then updates the screen and ends the transaction.

These diagrams describe processes and the way you know it is correct is to step through those processes and see if anything is missing or a misunderstanding arises.

This post has been edited by Martyr2: 06 August 2011 - 10:27 AM