Leture-w1-3

Leture-w1-3 - SE 210: Software Specification and Design I...

Info iconThis preview shows pages 1–8. Sign up to view the full content.

View Full Document Right Arrow Icon

Info iconThis preview has intentionally blurred sections. Sign up to view the full version.

View Full DocumentRight Arrow Icon

Info iconThis preview has intentionally blurred sections. Sign up to view the full version.

View Full DocumentRight Arrow Icon

Info iconThis preview has intentionally blurred sections. Sign up to view the full version.

View Full DocumentRight Arrow Icon

Info iconThis preview has intentionally blurred sections. Sign up to view the full version.

View Full DocumentRight Arrow Icon
This is the end of the preview. Sign up to access the rest of the document.

Unformatted text preview: SE 210: Software Specification and Design I Fall 2008 Lecture 3 on Fri., Sept. 26, 2008 2 Last Lecture Software development process model: Waterfall model Spiral model Iterative approach Kind reminder Choosing a project Composing a team Due next Monday!!! 3 How Do We Know a System Meets its Intended Purpose? Requirements Specification System Problem Verification Validation 4 A Requirement R1: Reverse thrust should be enabled only when the aircraft is moving on the runway, and disabled at all other times. To detect moving on the runway, we need to find a way of connecting this to phenomena that the machine can detect. 5 Reverse Thrust for Aircraft 6 A Specification and Domain Assumptions S1: reverse thrust should be enabled if and only if wheel pulses are on. Domain Assumptions: D1: wheel pulses are on if and only if wheels are turning. D2: wheels are turning if and only if aircraft in moving on the runway. 7 Verification and Validation How to verify the control software? Write test cases that check whether it meets its specification. How to validate the control software? i.e., is the reverse thrust enabled only when the aircraft is moving on the runway? No way! We need to check the requirement and domain assumptions adequately capture what happens in reality. How can we be sure about the domain assumptions? So an important part of requirements management is to assess the risk of each such circumstance. 8...
View Full Document

Page1 / 22

Leture-w1-3 - SE 210: Software Specification and Design I...

This preview shows document pages 1 - 8. Sign up to view the full document.

View Full Document Right Arrow Icon
Ask a homework question - tutors are online