Software Requirement Engineering Through Use Case
Software Requirement Engineering through Use case
Mrs Mirza Zainab, Lecturer in IT Dept, M.H.S.S. COE, Byculla, India
Mirza_zainab@yahoo.com
ABSTRACT
By now, it is well known that shortcomings in requirements definition and management lead to excessive rework on software projects and products that fail to achieve full customer satisfaction. In systems engineering and software engineering, requirements analysis encompasses all of the tasks that go into the investigation, scoping and definition of a new or altered system. Requirements analysis is an important part of the system design process, whereby requirements engineers and business analysts, along with systems engineers or software developers, identify the needs or requirements of a client. Once the client's requirements have been identified, the system designers are then in a position to design a solution. Software requirements engineering is a communication-intensive activity, at a minimum involving analysts, developers, business stakeholders and end users. The paper describes how use cases can be used effectively to model requirement of system and how it can be used as a means of communication between analyst and end users.
KEYWORDS
Software requirement engineering, use cases, actor, include, extend
INTRODUCTION
Software development involves perhaps 50 percent computing and 50 percent communication. Unfortunately, most teams are better at the computing part, and requirements are almost entirely about communication. There are many links in the requirements communication chain, like end user, sales representative, marketing, product manager, developer, and tester. A breakdown in any of these links leads to significant problems. The inevitable outcome of requirements errors is time consuming and costly rework. Analysts report that rework can consume 30 to 40 percent of the total effort expended on a software project. Multiple studies have indicated that roughly 50 percent of the defects
Mrs Mirza Zainab, Lecturer in IT Dept, M.H.S.S. COE, Byculla, India
Mirza_zainab@yahoo.com
ABSTRACT
By now, it is well known that shortcomings in requirements definition and management lead to excessive rework on software projects and products that fail to achieve full customer satisfaction. In systems engineering and software engineering, requirements analysis encompasses all of the tasks that go into the investigation, scoping and definition of a new or altered system. Requirements analysis is an important part of the system design process, whereby requirements engineers and business analysts, along with systems engineers or software developers, identify the needs or requirements of a client. Once the client's requirements have been identified, the system designers are then in a position to design a solution. Software requirements engineering is a communication-intensive activity, at a minimum involving analysts, developers, business stakeholders and end users. The paper describes how use cases can be used effectively to model requirement of system and how it can be used as a means of communication between analyst and end users.
KEYWORDS
Software requirement engineering, use cases, actor, include, extend
INTRODUCTION
Software development involves perhaps 50 percent computing and 50 percent communication. Unfortunately, most teams are better at the computing part, and requirements are almost entirely about communication. There are many links in the requirements communication chain, like end user, sales representative, marketing, product manager, developer, and tester. A breakdown in any of these links leads to significant problems. The inevitable outcome of requirements errors is time consuming and costly rework. Analysts report that rework can consume 30 to 40 percent of the total effort expended on a software project. Multiple studies have indicated that roughly 50 percent of the defects