USECASE is an implementation independent notation. How will the designer give the implementation details of a particular USECASE to the programmer?

• This might be help full
  
  Use Case Name --> a name given to particular use case
  
  Actor --> user of the user case
  Description --> brief description of the module
  Preconditions --> specify the conditions for the module to work fine
  Post conditions --> post conditions if necessary, such as saving data of logging out of application
  Normal Course of event --> accessing and applying the module applications including all steps
  
  Alternative Course --> alternate way of accessing module application and further steps
  
  Access Point --> link or button available
  Assumption --> only if necessary
  
  
  a standard use case report consists of all these points
• 11 years agoHelpfull: Yes(1) No(0)