Skip to content

Understanding Your Domain

Mehmet Özkaya edited this page Apr 1, 2019 · 9 revisions

Its really important to understand what you will develop and its crucial that defining your use cases.

Requirements and Modelling

  • Identify User Stories
  • Identify the Nouns in the user stories
  • Identify the Verbs in the user stories
  • Put together object interaction diagram
  • Put together object responsibilities diagram
  • Put together class digram UML showing only interesting interactions

So here are made up user stories:

  • As a customer I want to be able to put products that I want to purchase in to the shopping cart so that I can check out quickly later on
  • As a customer I want to see the total cost all for all of the items that are in my cart so that I see if I can afford to buy everything
  • As a customer I want to see the total cost of each item in the shopping cart so that I can re-check the price for items
  • As a customer I want to see the total cost for all of the items in the shopping cart with total tax
  • As a customer I want to be able to specify the address of where all of the products are going to be sent to
  • As a customer I want to be able to add a note to the delivery address so that I can provide special instructions to the postman

Now I am going extract nouns and verbs from the stories above. I am looking for the nouns that will become my main objects and not the attributes.

Nouns:

  • Customer
  • Item
  • Order
  • Shopping Cart
  • Address

Verbs:

  • Put products in to the shopping cart
  • See total cost for all of the items
  • See total cost for each item
  • See total tax for my country
  • Specify delivery address
  • Specify delivery note for delivery address
  • Specify invoice address
  • Receive invoice for the order

Reference

Clone this wiki locally