Sunday, 29 July 2012

Requirement Elicitation of credit card fraud detection


A Requirement is a feature that the system must have or a constraint that it must satisfy to be accepted by the clients. Requirements Engineering aims at defining the requirements of the system under construction. It includes two main activities namely Requirements Elicitation and Analysis.        
            Requirements Elicitation focuses on describing the purpose of the system. The Client, the Developer, and the Users identify a problem area and define a system that addresses the problem. Such a definition is called Requirements Specification. This specification is structured and formalized during analysis to produce an Analysis Model.
Requirements Elicitation and Analysis focuses only on the user’s view of the system. Requirements Elicitation includes the following activities:

Identifying Actors:
Ø      During this activity, developers identify the different types of users and the future system will support.

Identifying Scenarios:
Ø      During this activity, developers observe users and develop a set of detailed scenarios for typical functionality provided by the future system. 
Ø      Developers use these scenarios to communicate with the users and depends their understanding.

Identifying Use Cases:
Ø      Once developers and users agree on a set of scenarios, developers derive from the scenarios a set of use cases that completely represent the future system.
Refining Use Cases:
Ø      During this activity, developers ensure that the requirements specification is complete by detailing each use case and describing the behavior of the system in the presence of errors and exceptional conditions.

Identifying relationships among use cases:
Ø      During this activity, developers identify dependencies among use cases and also consolidate the use case model by factoring out common functionality.

Identifying Non-functional requirements:
Ø      During this activity, developers, users and clients agree on aspects like performance of system, documentation, resources, security and its quality.

No comments:

Post a Comment