Basic Review and Synchronization (6th week!)

1
Basic Review and Synchronization (6th week!)

• We do Requirements Elicitation and Analysis now
  in parallel
• elicitation produces a requirements spec
• analysis produces analysis models
• and revised requirements spec
• Wiegers ch 6-10 - very practical guidelines
• managers have you checked Part III in Wiegers?

2
Reading

• You were to read 2 chapters ahead last week in
  both Wiegers and Weinberg
• Read another 2 chapters ahead this week
• it will be of significant help to read carefully

3
Managers meeting Friday?

• I would like to have a meeting with managers on
  Friday, 27 October
• Formal status report
• a few slides would be helpful
• I need to know exactly where you are and your
  plans to proceed
• Suggested times?
• I can be flexible

4
Team / Self Evaluations due Monday

• Forms on my webpage
• be honest
• dont take it personally (or mean it that way)
• it is used to measure as a basis for improvement
• get it to me in confidence (can drop it off in
  main office to get to my mailbox)
• you might even edit the document and return via
  email (though it is not set up for that)

5
Common Elicitation Activities (all about
communication with users, clients, developers!)

• Identify
• actors
• scenarios
• use cases
• refined use cases
• relationships among use cases
• other functional requirements (recall Wiegers p
  136)
• you will produce use cases and SRS with some
  formal modeling
• other nonfunctional requirements

6
Common Analysis Activities (all about
correctness, completeness, consistency of
requirements!)

• Identify objects
• classify
• entity - main concepts in application domain
• boundary - system interface with actors
• control - coordinates boundary and entity objects
• Map use cases to objects, define interactions
• sequence, event trace diagrams

7
Common Analysis Activities (contd)

• Refine by formal modeling
• nontrivial behavior Statecharts, Petri Nets
• special failure analysis Fault Trees, Event
  Trees
• define attributes of objects ER, data dictionary
• define associations entity relationship diagrams
• Consolidate models eliminate redundancy
• Review, inspect, walkthrough, document

8
Your Requirements Document

• By Monday (30 Oct.)
• memo to me regarding your project and the 405
  requirements discussed in class
• I can read it again if necessary
• Start formal modeling now
• your document must contain formal models
• RSL, statecharts, DFDs, ERs, data dictionary
  (in RSL, there is a checker for it!) for
  significant parts
• best use RSL throughout