Chapter+7 - Modeling System Requirements with Use Cases...

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: Modeling System Requirements with Use Cases Chapter 7 Introduction to Use-Case Modeling One of the primary challenges is the ability to elicit the correct and necessary System Requirements from the Stakeholders and specify them in a manner understandable to them so those requirements can be verified and validated. The hardest single part of building a software system is deciding precisely what to build. No other part of the conceptual work is as difficult as establishing the detailed technical requirements, including all the interfaces to people, to machines, and to other software systems. No other work so cripples the resulting system if done wrong. No other part is more difficult to rectify later. Fred Brooks User-Centered Development and Use-Case Modeling User-Centered Development – Process of Systems Development based on understanding the needs of the Stakeholders and the reasons why the system should be developed. Use-Case Modeling – Process of modeling a system’s functions in terms of business events, who initiated the events, and how the system responds to those events. – Use-Case Modeling has roots in Object-Oriented modeling. – Gaining popularity in non-object development environments because of its usefulness in communicating with users. – Compliments traditional modeling tools. Benefits of Use-Case Modeling • Provides tool for capturing functional requirements. • Assists in decomposing system into manageable pieces. • Provides means of communicating with users/stakeholders concerning system functionality in language they understand. • Provides means of identifying, assigning, tracking, controlling, and management system development activities. • Provides aid in estimating project scope, effort, and schedule. Benefits of Use-Case Modeling (continued) • Aids in defining test plans and test cases. • Provides baseline for user documentation. • Provides tool for requirements traceability. • Provides starting point for identification of data objects or entities. • Provides specifications for designing user and system interfaces. • Provides means of defining database access requirements. • Provides framework for driving the system development project. System Concepts for Use-Case Modeling Use Case – Behaviorally related sequence of steps (scenario), both automated and manual, for the purpose of completing a single business task....
View Full Document

This note was uploaded on 04/17/2008 for the course M&IS 24060 taught by Professor G.dehondt during the Spring '08 term at Kent State.

Page1 / 37

Chapter+7 - Modeling System Requirements with Use Cases...

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