Actions § Requirements are Services, NOT trigger spots. § Primary vs. Secondary Actors § The reader will learn something, i.e., Understand better the system
a description of a software system to be developed. It lays out functional and non-functional requirements. § Establishes the basis for an agreement between customers and contractors or suppliers on what the software product is to do as well as what it is not expected to do. § Permits an assessment of requirements before design can begin and reduces later redesign.
830-1998, IEEE Recommended Practice for Software Requirements Specifications Standard 830, last revised in 1998. § IEEE Standard ISO/IEC/IEEE 29148:2011, with an update in 2018. § Like many IEEE standards for software engineering, they includes guidance and recommended approaches for specifying software requirements. It's not a complete tutorial on requirements development, but it does contain some useful information. § The IEEE standard provides several suggestions of how to organize functional requirements. There is no single organizational approach that's best. § Tailor and customize templates to best suit the nature and scale of your projects.
template from IEEE § Review the SRS for the Monopoly Game. Can you identify opportunities for improvement (errors)? http://agile.csc.ncsu.edu/SEMaterials/UseCaseRequirements.pdf § Review the SRS for the Pac-Man Game. Can you identify opportunities for improvement (errors)? (No, it is not a 100% good solution – be aware!) § Review the SRS for Gephi. Can you identify opportunities for improvement ? https://gephi.org/users/gephi_srs_document.pdf Nothing to submit yet
<use cases diagram> 7. <use cases list> 8. for-each use case { a. Id number b. Name – the goal as a short active verb phrase. c. Goal – a longer statement of the goal in context if needed d. Preconditions – what we expect is already the state of the world e. Post-conditions (also called success condition) - the state of the world upon successful completion f. failed condition (exception sequence) – the state of the world if goal abandoned. g. Description, base sequence or flows – it can be a paragraph or a diagram (use activity diagrams and state diagrams in this place) h. Actors – a role name or description for user or other systems }
[email protected] Fall 2021 Copyright. These slides can only be used as study material for the class CSE563 at ASU. They cannot be distributed or used for another purpose.
javiergs
niftycorp
kwakeuijin
shibuyamizuho
makihiro
warrenm
nrslib
tera_ny
fuyan777
datanalyticslabo
kimura_m_29
memory1994
garrettdimon
marcelosomers
eileencodes
csswizardry
brad_frost
maltzj
lara
carmenintech
bcantrill
sachag
