@202usecasemodeling@20ppt

@202usecasemodeling@20ppt - TUM Use Case Modeling 2 Prof....

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

View Full Document Right Arrow Icon
TUM Use Case Modeling Prof. Bernd Brügge Technische Universität München Lehrstuhl für Angewandte Softwaretechnik 6 May 1998
Background image of page 1

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

View Full DocumentRight Arrow Icon
Bernd Brügge Component--Based Software Engineering 2 Defining the System Boundary: What do you see?
Background image of page 2
Bernd Brügge Component--Based Software Engineering 3 System Identification v Development of a system is not just done by taking a snapshot of a scene (domain) v Definition of the system boundary u What is inside, what is outside? v How can we identify the purpose of a system? v Requirements Process: w Requirements Elicitation: Definition of the system in terms understood by the customer w Requirements Analysis: Technical specification of the system in terms understood by the developer.
Background image of page 3

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

View Full DocumentRight Arrow Icon
Bernd Brügge Component--Based Software Engineering 4 Requirements Elicitation v Very challenging activity v Requires collaboration of people with different backgrounds w User with application domain knowledge w Developer with implementation domain knowledge v Bridging the gap between user and developer: w Scenarios: Example of the use of the system in terms of a series of interactions with between the user and the system w Use cases: Abstraction that describes a class of scenarios
Background image of page 4
Bernd Brügge Component--Based Software Engineering 5 Requirements Validation v Critical step in the development process, w Usually after requirements engineering or requirements analysis. Also at delivery v Requirements validation criteria: w Correctness: u The requirements represent the client’s view. w Completeness: u All possible scenarios through the system are described, including exceptional behavior by the user or the system w Consistency: u There are functional or nonfunctional requirements that contradict each other w Realism: u Requirements can be implemented and delivered
Background image of page 5

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

View Full DocumentRight Arrow Icon
Bernd Brügge Component--Based Software Engineering 6 Requirements Validation v Traceability: w Each system function can be traced to a corresponding set of functional requirements v Tool: w RequisitPro from Rational u Stores requirements in a repository u Multi-user access u Automatically creates a requirements document from the repository u Provides traceability and change management throughout the project lifecycle u http://www.rational.com/products/reqpro/docs/datasheet.html
Background image of page 6
Bernd Brügge Component--Based Software Engineering 7 Types of Requirements Elicitation v Greenfield Engineering w Development starts from scratch, no prior system exists, the requirements are extracted from the end users and the client w Triggered by user needs v Re-engineering w Re-design and/or re-implementation of an existing system using newer technology w Triggered by technology enabler v Interface Engineering w Provide the services of an existing system in a new environment w Triggered by technology enabler or new market needs
Background image of page 7

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

View Full DocumentRight Arrow Icon
Bernd Brügge Component--Based Software Engineering 8 Actors v Actors constitute everything that is external to the system and that communicates and interacts with the system.
Background image of page 8
Image of page 9
This is the end of the preview. Sign up to access the rest of the document.

This note was uploaded on 11/20/2010 for the course CS 301 taught by Professor Berndbrügge during the Spring '98 term at TU München.

Page1 / 41

@202usecasemodeling@20ppt - TUM Use Case Modeling 2 Prof....

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

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