CS 2401 - AY2019-T3_ Week 3 Discussion Question.pdf -...

This preview shows page 1 - 3 out of 44 pages.

01.04.2019 CS 2401 - AY2019-T3: Week 3 Discussion Question 1/44 Home My courses CS 2401 - AY2019-T3 14 February - 20 February Discussion Forum Unit 3 Week 3 Discussion Question Discussion Forum Unit 3 Week 3 Discussion Question Subscribed HOME CONTACT US RESOURCES LINKS FACULTY MY COURSES MENU     1 CS 2401 Software Engineering 1 - Term 3, 2018-2019 Search forums Week 3 Discussion Question by Jim Casale (Instructor) - Wednesday, 30 January 2019, 7:45 AM What is the di±erence between a scenario and a use case? When do you use each construct? Explain with the help of 1-2 suitable examples. 25 words Permalink | Reply Re: Week 3 Discussion Question by Natacia Mariott - Friday, 15 February 2019, 4:51 PM Hi class, I look forward to hearing your thoughts on use cases after having completed our textbook readings and reviewing our programming assignment for the unit! And thank you all kindly for your meaningful feedback in our previous discussion forum - it was awesome and incredibly helpful, truly. What is the di±erence between a scenario and a use case? When do you use each construct? Explain with the help of 1-2 suitable examples.
01.04.2019 CS 2401 - AY2019-T3: Week 3 Discussion Question 2/44 In re²ecting on our reading material, it seems to me that use cases are quite similar to scenarios, but for discussion sake I understand I am looking to highlight the di±erence! I guess a scenario would be di±erent than a use case in the sense that it is a broader de³nition of a potential happenings, and it's not always something we expect to happen or want to happen, while a use case is a pretty well-de³ned and speci³c instance of an expected happening. A use case also has a speci³c objective: achieving the business goal (Marsic, 2012), while a scenario could describe an instance without de³nitive goals or particular business meaning. One suitable example of when we might use a scenario might be when considering "worst-case" (Marsic, 2012). That scenario isn't de³nitely going to happen (and hopefully won't), but it can be useful to think about, plan for, and thereby avoid, should it happen. An example of worst-case scenario might be that there is a system failure. Well this isn't a use case, because it's not something any of the actors would intend to do, or try to do. But it is a scenario that might happen, and therefor it would be a good idea to consider and plan for it, in the event that it does. A second suitable example, and this time I'll focus on use cases, would be an action we intend to happen within the system, but would not detail the "how" or go into any of the black-box workings of the system. The use case "withdraw cash" in our ATM example does just that. Identi³es the action to enter dialog of the system, but goes not deeper into the workings of the ATM system to de³ne how that's going to happen (Marsic, 2012).

  • Left Quote Icon

    Student Picture

  • Left Quote Icon

    Student Picture

  • Left Quote Icon

    Student Picture