<P>The world is becoming ever more dependent on software intensive systems. They are central to our economy, to our society, to the services we depend upon and, increasingly to the very survival of the global ecosystem. Despite many failures, some of them very well publicized, the engineering of such systems has improved consistently over the past few decades. However many challenges remain. Every computer–based system involves relating the myriad, informal facets of the real world to the intricate and formal specifics of a software system. Understanding potentials or details of software systems is not expected of stakeholders, who have their own specialized concerns. Similarly, the eager and technologically capable developers are not expected to understand the nuances of the many domains where software applies. Requirements Engineering (RE) is the essential capability that can bridge the two perspectives. The RE activity is multi–disciplinary. When defining the requirements of major systems we must bring to bear expertise from a wide range of specialisms such as Human–Computer Interaction, Systems Modeling, and Security. The RE research field builds the effective bridges between these and other sub–disciplines of the Computer Science and Information Systems fields. The many computer–based system needs of business and society are often contradictory, inadequately defined, and rapidly changing. RE helps stakeholders communicate, helping to reconcile their conflicts, clarify their goals, and reflect their priorities. If our society is to seek a better future we will need all of the models, methods, and tools that RE can provide.</P> <P>The IEEE International Requirements Engineering Conference provides the premier international forum for researchers, educators, industrial practitioners and students to present and discuss the most recent innovations, trends, experiences and concerns in the field of requirements engineering.<BR></P> <P><B>Keywords:</B> </P> <P>requirements elicitation, analysis, documentation, validation and verification; requirements specification languages, methods, processes and tools; requirements management, traceability, viewpoints, prioritization and negotiation; modeling of requirements (formal and informal), goals and domains; prototyping, simulation and animation; evolution of requirements over time, product families and variability; relating requirements to business goals, products, architecture and testing; social, cultural, global, personal and cognitive factors in requirements engineering; domain–specific problems, experiences and solutions. </P>
Abbrevation
RE
Link
City
Atlanta, GA
Country
United States
Deadline Paper
Start Date
End Date
Abstract