Draft:IFIP Working Group 2.9
![]() | Draft article not currently submitted for review.
This is a draft Articles for creation (AfC) submission. It is not currently pending review. While there are no deadlines, abandoned drafts may be deleted after six months. To edit the draft click on the "Edit" tab at the top of the window. To be accepted, a draft should:
It is strongly discouraged to write about yourself, your business or employer. If you do so, you must declare it. Where to get help
How to improve a draft
You can also browse Wikipedia:Featured articles and Wikipedia:Good articles to find examples of Wikipedia's best writing on topics similar to your proposed article. Improving your odds of a speedy review To improve your odds of a faster review, tag your draft with relevant WikiProject tags using the button below. This will let reviewers know a new draft has been submitted in their area of interest. For instance, if you wrote about a female astronomer, you would want to add the Biography, Astronomy, and Women scientists tags. Editor resources
Last edited by Wiki.breaux (talk | contribs) 24 days ago. (Update) |
IFIP Working Group 2.9 on Requirements Engineering is a working group within TC-2 (Software: Theory and Practice), which in turn is a technical committee of International Federation for Information Processing.
History
IFIP WG 2.9 was established in 1993.
Purpose
The purpose of IFIP WG 2.9 is to develop a better understanding of:
- The elicitation, specification, analysis and management of the requirements for large and complex software intensive systems;
- The interpretation and documentation of those requirements in such a way as to permit the developer to construct a system which will satisfy them.
Requirements engineering has received significant attention in software development design education[1][2].
Scope
The Scope of IFIP WG 2.9 includes all aspects of requirements engineering. Some examples of areas of special interest are:
- Formal representation schemes and requirements modelling;
- Descriptions of the requirements engineering process;
- Tools and environments to support requirements engineering;
- Requirements engineering methods;
- Requirements analysis and validation;
- Requirements elicitation, acquisition and formalisation;
- Methods and tools for verification of an implementation’s compliance with requirements;
- Reuse and adaptation of requirements;
- Domain modelling and analysis;
- Requirements engineering for distributed, safety-critical, composite, real-time and embedded systems.
Organization
- Andrea Zisman, Chair, Open University, UK
- Travis Breaux, Vice Chair, Carnegie Mellon University, USA
- Liliana Pasquale, Secretary, University College Dublin, Ireland
Members
- Dalal Alrajeh, Imperial College, UK
- Jo Atlee, University of Waterloo, Canada
- Amel Bennaceur, Open University, UK
- Lionel Briande, University of Ottawa, Canada
- Marsha Chechik, University of Toronto, Canada
- Betty HC Cheng, Michigan State University, USA
- Jane Cleland-Huang, University of Notre Dame, USA
- Krzysztof Czarnecki, University of Waterloo, Canada
- Daniela Damien, University of Victoria, BC, Canada
- Vincenzo Gervasi, University of Pisa, Italy
- Matts Heimdahl, University of Minnesota, USA
- Julio Cesar Leite, Federal University of Bahia, Brazil
- Robyn Lutz, Iowa State University, USA
- Bashar Nuseibeh, Open University, UK
- Klaus Pohl, University of Duisburg-Essen, Germany
- Sebastian Uchitel, Imperial College, UK
- Michael Whalen, Amazon, USA
- John Whittle, CSIRO, Australia
Emertius
- Annie Antón, USA
- Dan Berry, Canada
- Stephen Fickas, USA
- Carlo Ghezzi, Italy
- Sol Greenspan, USA
- Robert Hall, USA
- Jeff Kramer, UK
- Axel van Lamsweerde, Belgium
- John_Mylopoulos, Canada
- William Robinson, USA
- Kevin Ryan, Ireland