2. 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.functional requirements (Wikipedia - http://en.wikipedia.org/wiki/Use_case)

3. Requirements standards (IEEE) Condition: optional User: external or internal, usually singular See 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: Optional Action: usually singular

4. Standard vs. feature list vs. functional requirement Standard: Intuitive Feature: Have different levels Functional requirement(s): Armadillo Run shall have 15 levels. Design requirement(s): A level class shall have an IDENTITY attribute An IDENTITY attribute shall be an integer

5. Words/phrases to avoid Appropriately Essentially About/approximately A few Quickly Slowly Average (adjective not noun or verb) Realistic Designated amount of time Will make sure

6. When you can find me bowmanvc@rose-hulman.edu 877.8821