Software Engineering

1.) What does the term requirement mean? Explain the process of determining the requirement for a software system.
 ‘Requirements’ suggests that there is someone out there doing the ‘requiring’ – a specific customer who knows what she wants. In some projects, requirements are understood to be the list of features (or functions, properties, constraints, etc.) Demanded by the customer. In practice, there is rarely a single customer, but rather a diverse set of people who will be affected in one way or another by the system. These people may have varied and conflicting goals. Their goals may not be explicit, or may be hard to articulate. They may not know what they want or what is possible. Under these circumstances, asking them what they ‘require’ is not likely to be fruitful. 2.) Describe the various steps of requirement engineering? Is it essential to follow these steps?

 Requirements engineering is an important aspect of any software project, and is a general term used to encompass all the activities related to requirements. The four specific steps in software requirements engineering are:
• Requirements elicitation is the practice of obtaining the requirements of a system from users, customers and other stakeholders.
• Requirements analysis encompasses those tasks that go into determining the needs or conditions to meet for a new or altered product, taking account of the possibly conflicting requirements of the various stakeholders, such as beneficiaries or users.
• Requirements specification is the direct result of a requirement analysis and can refer to Software Requirements Specification and Hardware Requirements Specification.
• Requirements validation
Although they seem to be separate tasks, these four processes cannot be strictly separated and performed sequentially. Some of the requirements are