ch04lect1_UD - Using UML, Patterns, and Java...

Info iconThis preview shows pages 1–7. 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
This is the end of the preview. Sign up to access the rest of the document.

Unformatted text preview: Using UML, Patterns, and Java Object-Oriented Software Engineering Chapter 4, Requirements Elicitation 2 Bernd Bruegge & Allen H. Dutoit Object-Oriented Software Engineering: Using UML, Patterns, and Java 2 Software Lifecycle Activities Application Domain Objects Subsystems class... class... class... Solution Domain Objects Source Code Test Cases ? Expressed in Terms Of Structured By Implemented By Realized By Verified By System Design Detailed Design Implemen- tation Testing class.... ? Requirements Elicitation Use Case Model Analysis 3 Bernd Bruegge & Allen H. Dutoit Object-Oriented Software Engineering: Using UML, Patterns, and Java 3 What does the Customer say? 4 Bernd Bruegge & Allen H. Dutoit Object-Oriented Software Engineering: Using UML, Patterns, and Java 4 First step in identifying the Requirements: System identification Two questions need to be answered: 1. How can we identify the purpose of a system? 2. What is inside, what is outside the system? These two questions are answered during requirements elicitation and analysis Requirements elicitation: Definition of the system in terms understood by the customer (Requirements specification) Analysis: Definition of the system in terms understood by the developer ( Technical specification, Analysis model) Requirements Process: Contains the activities Requirements Elicitation and Analysis. 5 Bernd Bruegge & Allen H. Dutoit Object-Oriented Software Engineering: Using UML, Patterns, and Java 5 Techniques to elicit Requirements Bridging the gap between end user and developer: Questionnaires: Asking the end user a list of pre-selected questions Task Analysis: Observing end users in their operational environment Scenarios: Describe the use of the system as a series of interactions between a concrete end user and the system Use cases: Abstractions that describe a class of scenarios. 6 Bernd Bruegge & Allen H. Dutoit Object-Oriented Software Engineering: Using UML, Patterns, and Java 6 Scenario-Based Design Scenarios can have many different uses during the software lifecycle Requirements Elicitation : As-is scenario, visionary scenario Client Acceptance Test: Evaluation scenario...
View Full Document

This note was uploaded on 12/22/2011 for the course CS 101 taught by Professor Dat during the Spring '11 term at Bilkent University.

Page1 / 53

ch04lect1_UD - Using UML, Patterns, and Java...

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

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