There cannot be a single process of requirement elicitation that can act as a silver bullet. However authors have suggested some activities that must be done while doing requirement engineering
1. Objective Setting:
a. Identifying general goals of business
b. Outline of problem to be solved and need of problem to be solved
c. Identification of constraints including budget, schedule and interoperability
2. Background knowledge Acquisition
a. Acquiring Information regarding the organization
b. Acquiring information regarding application domain
c. Gathering knowledge about existing system that will be replaced
3. Knowledge Organization
a. Organizing large amount of knowledge acquired
b. Involves identifying system stakeholders
c. Prioritizing goals
d. Discarding unnecessary domain knowledge which do not contribute to system requirement
4. Stakeholder requirement collection
a. Involves consulting system stakeholders to discover their requirements
As a result of requirement elicitation a large amount of data is collected. In order to make the data more meaningful, it is important that the organized and structured.
Following are the ways to structure data
1. Partitioning
a. Aggregation relationship. For example in University, a degree is made up of a number of courses. Payroll of a single employee is made up of a number of earnings
2. Abstraction
a. General / Specific Relationship. For example a university offers a Degree which has a number of categories e.g. PH.D., Masters, Bachelors etc. Each category has some special characteristic
3. Projection
a. Organization of knowledge from several different perspectives, For example, information from the perspective of student, details from the perspective of faculty and information with respect to examination etc.
No comments:
Post a Comment