1. CSE3308 - Software Engineering: Analysis and Design, 2001Lecture 13.1 Software Engineering: Analysis and Design - CSE3308 Exam Revision 1998 Practice Exam CSE3308/DMS/2001/32

2. CSE3308 - Software Engineering: Analysis and Design, 2001Lecture 13.2 Question 1(a) - Use Cases First Step - fill in the basic details Use Case:Buy Items with EFTPOS Actors:Customer (initiator), Cashier Purpose:Capture a sale and its EFTPOS payment Overview: A Customer arrives at a checkout with items to purchase. The Cashier records the purchase items. The Cashier inputs the details for the EFTPOS transaction. The Customer enters their PIN number. On completion, the Customer leaves with the items. Type:primary and essential

3. CSE3308 - Software Engineering: Analysis and Design, 2001Lecture 13.3 Q 1(a) 1. This use case begins when a Customer arrives at the register with items to purchase. 2. The cashier records the identifier from each item. If more than one of the same item, the Cashier can enter the quantity as well. 4. Cashier indicates completion of item entry. 6. Cashier tells the Customer the total. 3. Determines the item price and adds the item information to the running sales transaction. The description and price of the item are presented. TYPICAL COURSE OF EVENTS ACTOR ACTION SYSTEM RESPONSE 5. Calculates and presents the sale total.

4. CSE3308 - Software Engineering: Analysis and Design, 2001Lecture 13.4 Q 1(a) 7. The Customer indicates an EFTPOS payment will be made. 8. Cashier asks Customer for account type and cash out amount 9. Cashier enters amount of payment, type of account and cash out amount 11. Customer enters PIN Number. 13. Cashier issues receipt and required cash ACTOR ACTION SYSTEM RESPONSE 10. System asks Customer for PIN Number 12. System checks PIN Number and account balance

5. CSE3308 - Software Engineering: Analysis and Design, 2001Lecture 13.5 Q 1(a) ACTOR ACTION SYSTEM RESPONSE 14. Customer takes goods u Alternative Courses u Line 2: Invalid identifier entered. Indicate error u Line 7: Cash payment made (see Lecture 4A) u Line 13: Invalid PIN Number, PIN number must be re-entered u Line 13: Insufficient Funds: use alternative payment method

6. CSE3308 - Software Engineering: Analysis and Design, 2001Lecture 13.6 Q 1(a) Line 10: System checks credit balance and prints out credit card receipt Line 11: Customer signs credit card receipt

7. CSE3308 - Software Engineering: Analysis and Design, 2001Lecture 13.7 Q 1 (b) Purchase Goods Customer Cashier

8. CSE3308 - Software Engineering: Analysis and Design, 2001Lecture 13.8 Q 1(c) u Primary - represent major common processes u Secondary - represent minor or rare processes u Optional - processes that may not be implemented in the system depending upon resources

9. CSE3308 - Software Engineering: Analysis and Design, 2001Lecture 13.9 Question 2 (a) - Class Diagram Possible Classes u Supermarket u Section u Stock Line u Product Type vFrozen vPerishable vMedium-term vLong-term u Shelf vRefrigerated vChilled vStandard u Cashier u Cashier Station u EFTPOS Transaction u Scanner u Keyboard u Scales u Display Panel u EFTPOS Terminal

10. CSE3308 - Software Engineering: Analysis and Design, 2001Lecture 13.10 Q2 (a) - Possible Class Diagram

11. CSE3308 - Software Engineering: Analysis and Design, 2001Lecture 13.11 Q 2b Involved Classes Cashier Cashier Station EFTPOS Transaction Scanner Keyboard Scales Display Panel Product Type

12. CSE3308 - Software Engineering: Analysis and Design, 2001Lecture 13.12 Collaboration Diagram

13. CSE3308 - Software Engineering: Analysis and Design, 2001Lecture 13.13 Q 3(a) Structured Stuff Crazy Al’s Cars Taxation Department Car Seller Salesperson Purchaser Management Mechanic Sales report Purchases report Tax payable Transfer Info Service cost Repair details Sale details Car details Purchaser details

14. CSE3308 - Software Engineering: Analysis and Design, 2001Lecture 13.14 Q3b Search For Car Produce Tax Report Produce Mgmt Reports Transfer Car to Mechanic Sell Car Purchase Car Car Seller CAR Mechanic PURCHASER Transfer info Service cost, repair details Car details problems Repair costs Car details Purchaser details Tax Department Management Car details Sales and purchase report Sales and Purchase details Tax details Taxation report Purchaser details Sale details Note: this diagram should also include the “Salesperson” terminator

15. CSE3308 - Software Engineering: Analysis and Design, 2001Lecture 13.15 Q 3c Structured English Search for an appropriate car for a customer GET customer-requirements LOOP not (at end of CAR or car-found) SEARCH CAR for match DISPLAY CAR details IF car satisfactory SET car-found = True ENDIF ENDLOOP

16. CSE3308 - Software Engineering: Analysis and Design, 2001Lecture 13.16 Question 4(a) and (b) u Three most likely risks vIncreased size of the project relative to what the company has done before »use incremental development, break down into useable chunks, don’t try to build the whole system at once, monitor project progress on a continuing basis, hire new staff who have worked on this size project, define software process vUncertainty of requirements by the customer »use prototyping to help refine requirements, ensure contract has some flexibility at early stages on cost vThe inexperience of staff in analysis and design methods »bring in experienced consultants/mentors, ensure good training for all relevant staff, have formal and informal technical reviews

17. CSE3308 - Software Engineering: Analysis and Design, 2001Lecture 13.17 Q 4(a) and (b) vProject management issues, e.g. communications between the various parts of the project team »establish a formal communications method, have social activities involving all team members, provide meeting places (e.g. tea room where different parts can mix) vInability of manager to take hands-off approach »pick people that you can trust

18. CSE3308 - Software Engineering: Analysis and Design, 2001Lecture 13.18 Q 4(c) u To get benefits from quality standards vmust use sound management techniques vmust aim at improving the process vemployees must actively participate vintegrate the quality standard documentation with the already existing documentation u Quality standards are of greatest value to those organisations which don’t already have formal development processes u They don’t replace individual skills and abilities u They can only be as good as the work practices which they document

19. CSE3308 - Software Engineering: Analysis and Design, 2001Lecture 13.19 Q4 (d) u Business Systems Planning vgiven the uncertainty of the customer’s requirements u Project Management and Planning vespecially project estimation and control tools u Development Support vespecially quality assurance tools, based on the need to move to AS3563 u Analysis and Design vgiven that there will be a much larger team and the need to maintain communication across a large group u Prototyping vgiven the need for handling uncertain requirements

20. CSE3308 - Software Engineering: Analysis and Design, 2001Lecture 13.20 Q 4(e) u Management commitment u Alignment with organisation culture and work practices u Training u Involving users u Selecting appropriate tools u Having realistic expectations - often a drop in productivity in the first year u Matching the tool’s methodology with the organisation’s methodology u Getting help

21. CSE3308 - Software Engineering: Analysis and Design, 2001Lecture 13.21 Q 5 u Set an agenda and maintain it u Insist on advance preparation u Develop a checklist for each work product u Allocate resources and time u Conduct meaningful training u Review earlier reviews