requirements standards (use- case model) a use case is a technique used in software and systems...
TRANSCRIPT
![Page 1: Requirements standards (use- case model) A use case is a technique used in software and systems engineering to capture the functional requirements of](https://reader036.vdocuments.site/reader036/viewer/2022082506/5697bf741a28abf838c7f8de/html5/thumbnails/1.jpg)
![Page 2: Requirements standards (use- case model) A use case is a technique used in software and systems engineering to capture the functional requirements of](https://reader036.vdocuments.site/reader036/viewer/2022082506/5697bf741a28abf838c7f8de/html5/thumbnails/2.jpg)
Requirements standards (use-case model)A use case is a technique used in software and systems
engineering to capture the functional requirements of a system. Use cases describe the interaction between a primary actor—the initiator of the interaction—and the system itself, represented as a sequence of simple steps. Actors are something or someone which exist outside the system under study, and who (or which) take part in a sequence of activities in a dialogue with the system, to achieve some goal: they may be end users, other systems, or hardware devices. Each use case is a complete series of events, from the point of view of the actor.
(Wikipedia - http://en.wikipedia.org/wiki/Use_case)
![Page 3: Requirements standards (use- case model) A use case is a technique used in software and systems engineering to capture the functional requirements of](https://reader036.vdocuments.site/reader036/viewer/2022082506/5697bf741a28abf838c7f8de/html5/thumbnails/3.jpg)
Requirements standards (IEEE)<Condition> <user> <shall || should || may>
<action>
Condition: optionalUser: external or internal, usually singularSee RFC 2116 (http://www.ietf.org/rfc/rfc2119.txt)
Shall: Mandatory, “definition is an absolute requirement of the specification.”
Should: Recommended, “there may exist valid reasons in particular circumstances to ignore a particular item”
May: OptionalAction: usually singular
![Page 4: Requirements standards (use- case model) A use case is a technique used in software and systems engineering to capture the functional requirements of](https://reader036.vdocuments.site/reader036/viewer/2022082506/5697bf741a28abf838c7f8de/html5/thumbnails/4.jpg)
Standard vs. feature list vs. functional requirementStandard:
IntuitiveFeature:
Have different levelsFunctional requirement(s):
Armadillo Run shall have 15 levels.Design requirement(s):
A level class shall have an IDENTITY attributeAn IDENTITY attribute shall be an integer
![Page 5: Requirements standards (use- case model) A use case is a technique used in software and systems engineering to capture the functional requirements of](https://reader036.vdocuments.site/reader036/viewer/2022082506/5697bf741a28abf838c7f8de/html5/thumbnails/5.jpg)
Words/phrases to avoidAppropriatelyEssentiallyAbout/approximatelyA fewQuicklySlowlyAverage (adjective
not noun or verb)Realistic
Designated amount of time
Will make sure
![Page 6: Requirements standards (use- case model) A use case is a technique used in software and systems engineering to capture the functional requirements of](https://reader036.vdocuments.site/reader036/viewer/2022082506/5697bf741a28abf838c7f8de/html5/thumbnails/6.jpg)
Term Grid 1 2 3 4 5 6 7 8 9 108:05 9:00 9:55 10:50 11:45 12:40 1:35 2:30 3:25 4:20
Monday
CSSE375-01O101 Lunch
Tuesday
CSSE375-01O101 Team C Lunch
Wednesday Team A Team G
Thursday
CSSE375-01O101 Team J Team E Lunch Team L
Friday
CSSE375-01O101 Lunch
Department meeting