week4-1 - Requirements Engineering: What are Requirements?...

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

View Full Document Right Arrow Icon
Requirements Engineering: What are Requirements? Michael Gr¨uninger Semantic Technologies Lab University of Toronto September 27, 2010 Gr¨uninger (MIE350) Requirements Engineering September 27, 2010 1 / 25
Background image of page 1

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

View Full DocumentRight Arrow Icon
What is a Requirement? The hardest single part of building a system is deciding what to build. A requirement is a condition or capability needed by a user to solve a problem or achieve an objective. (IEEE 610) Who is the user? What problem do they need to solve? How is this related to the capabilities of a piece of software? Gr¨uninger (MIE350) Requirements Engineering September 27, 2010 2 / 25
Background image of page 2
The Role of Requirements The requirements specification reflects the mutual understanding of the problem to be solved between you and the customer. In the software lifecycle, the requirements specification (what is to be delivered) serves as the starting point for the design phase (how it is to be delivered). In agile methodologies, requirements emerge concurrently with prototypes. The delivered system will be assessed by testing its compliance with the requirements specification. Gr¨uninger (MIE350) Requirements Engineering September 27, 2010 3 / 25
Background image of page 3

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

View Full DocumentRight Arrow Icon
Requirements Engineering Process Requirements elicitation is about understanding the problem. Requirements specification is about describing the problem. Requirements validation is about agreeing upon the problem. Requirements negotiation is about fitting the problem to the situation at hand. Gr¨uninger (MIE350) Requirements Engineering September 27, 2010 4 / 25
Background image of page 4
Overview Specification Elicitation Validation Negotiation Documentation Management Gr¨uninger (MIE350) Requirements Engineering September 27, 2010 5 / 25
Background image of page 5

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

View Full DocumentRight Arrow Icon
Challenge Users cannot precisely articulate all of their requirements – we often get an incomplete and inaccurate picture of the situation. Tacit knowledge – hidden assumptions are not explicitly stated Software developers are not domain specialists, yet they must identify and employ the terminology of the users with the proper meaning. Gr¨uninger (MIE350) Requirements Engineering September 27, 2010 6 / 25
Background image of page 6
Business Requirements It is absolutely critical that the system is based on business requirements I Why are you building the system?
Background image of page 7

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

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

Page1 / 25

week4-1 - Requirements Engineering: What are Requirements?...

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