CS445 / SE463 / ECE 451 / CS645 - Student.cs.uwaterloo.ca

More documents

Recommendations

Info

Sec;on 3: UW organiza;on 3.1 External Interfaces – GUI • naviga;on map (if GUI independent) • screen shots • purpose of each UI widget – GUI events (input or output) • Mapping between GUI inputs (and outputs) and func;onal requirements inputs (outputs) – Hardware interface events • Mapping between hardware inputs (outputs) and func;onal requirements inputs (outputs)
Sec;on 3: UW organiza;on 3.2.1 Use Cases – Include a use case diagram. – Include only the use-‐case descrip;ons and alterna;ve flows that correspond to the func;onal specifica;ons. • Updated with respect to customer feedback – Include no sequence diagrams – Input and output defini;ons must be consistent among UCs, SSDs, UIs, and all other ar;facts.
Page 1 and 2: CS445 / SE463 / ECE 451 / CS
Page 3 and 4: RS vs. SRS • In prac;ce, the
Page 5 and 6: SRSs • The IEEE Recommended P
Page 7 and 8: SRS contents - Quality a_ributes
Page 9 and 10: IEEE SRS organiza;on Table of
Page 11 and 12: ATM example: Purpose This docum
Page 13 and 14: ATM example: Scope The soSware
Page 15 and 16: ATM: Defini;on vs. Abbrevia;on
Page 17 and 18: Sec;on 1. Introduc;on 1.4 Refer
Page 19 and 20: ATM: Overview The rest of this
Page 21 and 22: Sec;on 2: Overall descrip;on 2.
Page 23 and 24: 2.1 Product perspec;ve • A de
Page 25 and 26: ATM: Product perspec;ve • User
Page 33 and 34: Sec;on 3: Specific requirements
Page 35 and 36: Sec;on 3: IEEE organiza;on 3.2
Page 40 and 41: Sec;on 3: IEEE organiza;on 3.3
Page 44 and 45: Sec;on 3: UW organiza;on 3.2.2
Page 46 and 47: Sec;on 4 (UW-‐SRS): Requirem
Page 52 and 53: Example requirements table [Joel
Page 54 and 55: Example requirements table [Alex
Page 56 and 57: Index • The index maps each

CS445 / SE463 / ECE 451 / CS645 - Student.cs.uwaterloo.ca

Create successful ePaper yourself

Delete template?

Save as template?