Requirements engineering (RE) is about identifying and evolving needs or problems to specifications for systems and solutions that target those initial needs. As we move from a perceived need to a structured specification and, finally, to a solution, we can identify several risks that characterize RE as a discipline ý namely, overlooking a crucial requirement, inadequately representing or understanding the customer, considering only functional requirements, not verifying requirements, attempting to perfect requirements before beginning construction, representing requirements in the form of designs, and jumping too fast to a solution before understanding the problem domain. These risks are most effectively addressed during collection, analysis, and specification by categorizing requirements (that is, grouping requirements, permitting a higher-level understanding of relationships and dependencies, and consistently applying a specification template); organizing requirements (using automated tools to assist in understanding and tracing requirements from inception to allocation to delivery and applying strict change management); and prioritizing requirements (determining the order of consideration based on criticality of need and level of associated risk, implementing in increments following the priorities, and de-scoping those requirements with the lowest priority).

RE integrates these techniques by providing processes, methods, and tools throughout the product's life cycle, from the problem analysis stage to the system implementation and maintenance stages. Although RE varies greatly depending on the domain involved, similarities in its structure follow certain steps: elicitation, analysis, specification, verification, and management.

The articles in this bundle provide concrete usage scenarios of RE concepts in industry, with how-to tips, case studies, and examples of how you can best use RE. In "Requirements Engineering: The State of the Practice," for example, Colin Neill and Phillip Laplante summarize the deployment and use of current RE practices in industry. They show what is working and what doesn't deliver to expectations. "Requirements Engineering in Automotive Development: Experiences and Challenges," from Matthias Weber and Joachim Weisbrod is a practical industry paper describing the overall RE process, challenges, and experiences as it's used by a major car manufacturer. "ERP Requirements Engineering Practice: Lessons Learned," by Maya. Daneva provides a practical case study on how RE is practiced in IT systems development with COTS solutions that are adapted for practical usage. This paper also offers insight in RE for IT systems. Laura Lehtola with her coauthors emphasize that RE is closely linked to the business success of products. Their article shows how RE is more effectively lined up with business decision making. Finally, "Understanding the Product Life Cycle: Four Key Requirements Engineering Techniques" is a classic article that shows how RE is embedded and integrated into the product life cycle. It provides useful industry examples of how to improve RE processes end-to-end.

These articles on RE provide a look at practical experiences in applying RE to projects and product development with a focus on how to make it happen in your own environment. I selected them based on their practical insights and added value from real-world industrial applications of RE processes, methods, and tools.

Christof Ebert is managing director at Vector Consulting Services, where he helps clients worldwide improve technical product development. He led the introduction of real-time Linux and other FOSS to Alcatel products. Ebert has a PhD in electrical engineering from the University of Stuttgart. He's authored several books and many articles on software development and FOSS. He is a senior member of the IEEE.