Use cases and scenarios have emerged as prominent analysis tools during requirements engineering activities due to both their richness and informality. In some instances, for example when a project's budget or schedule time is reduced on short notice, practitioners have been known to adopt a collection of use cases as a suitable substitute for a requirements specification. Given the challenges inherent in managing large collections of scenarios, this shortcut is cause for concern and deserves focused attention. We discuss our experiences with a goal-driven analysis of a requirements specification for an electronic commerce application for a large international company. We describe scenario management within the context of this goal-driven requirements analysis effort. In particular, we identify the specific risks incurred, focusing more on the challenges imposed due to traceability,inconsistent use of terminology, incompleteness and consistency, rather than on traditional software project management risks. We conclude by discussing the impact of the lessons learned for requirements engineering in the context of building quality systems during goal and scenario analysis.
Did you find this white paper useful?
21 out of 50 users found this white paper useful
Related white papers
On Guard: Producing Run-Time Checks From Integrity Constraints
Software applications are inevitably concerned with data integrity, whether the data is stored in a database, files, or program memory. An integrity guard is code executed before a data update...
WebEx Builds Interactive Media Platform Using Forte Developer 6
WebEx is the leader in real-time communications infrastructure for Web meetings. WebEx built a service that could handle massive concurrent connections while maintaining exceptional response times to support live video,...
3-D Look at the IBM Software Development Platform for Linux
This webcast explains how the IBM Software Development Platform supports development teams in a Linux environment. This event covers the 3-D aspect of the IBM SDP for Linux: Discovery, Development...
An Assessment Process for Software Reuse
Each organization is unique in that they have different cultures and maturity with software processes and thus each organization should have a reuse plan specifically designed for their purposes. Therefore...
Object-Oriented Project Management
Object-orientation is a way of looking at the world as "classes" of "objects" in order to model the real world more effectively than traditional structured software engineering or other methods...
Process Reengineering and the Data Flow Diagram
In a structured design environment, DFD use proceeds in the following sequence (Yourdon, 1988): (1) hierarchical chart of system processes, (2) physical DFDs of the current system (both the Whats...
A Grounded Theory Study of Successful Organizational Integrated CASE Technology Implementation
This paper describes a research project that endeavors to answer the question are there certain characteristics of an organization that will predict whether ICASE will be successful in that organization?...
