Reference Larman Figure 10.3 in the text book (Larman, C. (2004). Applying UML a

Question

Reference Larman Figure 10.3 in the text book (Larman, C. (2004). Applying UML and Parttens: An Introduction to Object Oriented Analysis and Design and Iterative Development)

Imagine that you are a Software Designer on the NexGen POS project for a major retail store, and your team is following the UP as presented by Larman. A new Senior Developer named Joe joins the team, and makes several changes to the Process Sale SSD (System Sequence Diagrams).

1) Joe removes the "Loop" interaction frame from the scenario, saying it only makes the SSD confusing.

2) Joe expands the SSD to include the cases when makePayment happens via cash and when makePayment happens using credit or debit card.

3) Joe renames the endSale operation to be more specific. It is now called "pressEndSaleButton". He claims it's more clear and therefore better.

4) Joe changes enterItem to scanItem, saying that we know it's a scanner so using the vague word "enter" is not a good idea.

5) Joe writes Operation Contracts for each incoming Operation, with a pre- and post-condition for each. His Operation Contracts are each more than a page long. They are detailed narratives describing the state of the system before and after the operation.

6) Joe states that once his new version of the SSD and Operation Contracts are complete, the Use Cases themselves are no longer important and can be thrown away.

Write a draft email to Joe in MS Word explaining the potential issues and risks involved with each of his changes. Write your thoughts in complete, thorough sentences, and number each response to match the six numbered changes he made.

: Cashier System makeNewSale loop [more items ] 1. Customer arrives at a POS checkout with goods and/or services to purchasee 2. Cashier starts a new sale 3. Cashier enters item identifier 4. System records sale line item and presents item description, price, and running total Cashier repeats steps 3-4 until indicates done 5. System presents total with taxes calculated 6. Cashier tells Customer the total, and asks for payment. 7. Customer pays and System handles payment enterltem(itemID, quantit K description, total endSale --total with taxes makePayment(amount change due,receipt

Explanation / Answer

1. Removing the loop is not correct because it is required to identify which part of the process will be an activity to be performed on multiple items and multiple times.

Development perspective: It will clearly define which part is to be handled for multiple iterations

Business perspective: It defines the activity to be performed by Cashier

2. Separating payment options will confuse the user, however payment through cash is a sub section of entire payment process, it should be considered as payment only in SSD

3. pressEndSaleButton name is too much technical, to keep it user friendly and easily understandable keep it endSale.

Moreover, endSale defines the end of sale process, like an event it says sale ends, however with press sale button process is not understood just the event is clear.

4. Though, here Joe is partially right but, enter Item performs multiple activities and it covers the scenarios where in some time user has to make a manual entry, when may be scanner is not working.

Related Questions

Navigate

• Browse (All)
• Browse R
• Subjects

---

---

Integrity-first tutoring: explanations and feedback only — we do not complete graded work. Learn more.