• Post Reply
  • Bookmark Topic Watch Topic
  • New Topic

Assignment design doubts: Use case realization with assumptions

 
rana izzat
Greenhorn
Posts: 20
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Imagine, Use case given in 'Order mgmt system' is 'Search Order Line items'. No use case is describing about creation of Order and its line items in problem.
As the part of solution, two options I made for sequence diagram design. Which option is valid and applicable for making right design decisions? or both are not valid?

Option1 :
'Search UC' sequence diagram has to show how the order is created before searching(from inventory sub system).

Option2:
Start the 'Search UC' sequence diagram with steps that only explained in the problem with additional note saying 'Order is created and assigned to customer' as pre-condition.

I think Option-1 is suitable and explaining the solution. Existing use cases can be modified with assumed steps shown.

Your suggestions are welcome.
 
Cameron Wallace McKenzie
author and cow tipper
Saloon Keeper
Posts: 4968
1
Hibernate Spring Tomcat Server
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Howdy Greenhorn!

For a search use-case, I don't see any need to demonstrate how the Orders were created. It certainly wouldn't be part of my code for searching a system.

-Cameron McKenzie
 
rana izzat
Greenhorn
Posts: 20
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator

Thanks Cameron for clarifying my doubts. Your answer is raised the other question.

For the case of 'Add line items' use-case, Do the assumed points(order creation) to be shown here or an uml note is sufficient?

"if One use case has some dependency on other use-case which is not described in problem, assumed flow/points also shold be taken into account in order to show, how the gap is resolved rather than what." I applied this rule as whole point.

Please correct me if I'm wrong.

-Rana Izzat
 
Cameron Wallace McKenzie
author and cow tipper
Saloon Keeper
Posts: 4968
1
Hibernate Spring Tomcat Server
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Welcome back, Greenhorn!

If the use case is to add line items to an existing order, it would be incorrect to create an order in that use case diagram. After all, the order is already created. I would likely document the creation of the line item and the addition of the order.

Put yourself in the programmers shoes. Someone says "you need to add ten line items to these order objects that already exist." It would confuse the life out of the programmer if they were shown a diagram for creating orders. They'd be thinking "why am I looking at these pages of documents about creating something that already exists."

Remember, the diagrams should make developing a solution easier and less confusing.

-Cameron McKenzie
 
rana izzat
Greenhorn
Posts: 20
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Thanks again Cameron and pleased from your detailed answers!!

-Rana Izzat
 
  • Post Reply
  • Bookmark Topic Watch Topic
  • New Topic