Draft:IFIP Working Group 2.9
Submission declined on 2 June 2025 by KylieTastic (talk).
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
|  |
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
[edit]Established in 1993, the IFIP WG 2.9 membership draws from academic and industry researchers who have made significant contributions to the field. In 1993, Kevin Ryan (Emeritus) was among the first to recognize the future potential of natural language processing to reduce the manual effort of documenting and analyzing requirements.[1] and Axel van Lamsweerde (Emeritus), in collaboration with Anne Dardenne and Stephen Fickas (Emeritus), introduced a method for modeling early requirements, called goals.[2]
Several members of the IFIP WG 2.9 have received a Most Influental Paper Award, which is a retrospective award recoginizing the 10-year impact of research on the fields of software and requirements engineering, including: Sol Greenspan and John Mylopolous (1994)[3], Jeff Kramer and Bashar Nuseibeh (2003)[4], Stephen Fickas (2005)[5], Annie Antón (2006)[6]
Each year, the IFIP WG 2.9 meets to engage the membership and invited guests in the discussion of unpublished research. New members are inducted by vote of the membership after they have attended three meetings as guests. After attending five meetings as members, members may self-elect to enter Emerit status.
Purpose
[edit]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.[7][8]
Scope
[edit]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
[edit]- Andrea Zisman, Chair, Open University, UK
- Travis Breaux, Vice Chair, Carnegie Mellon University, USA
- Liliana Pasquale, Secretary, University College Dublin, Ireland
Members
[edit]- 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
[edit]- 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
References
[edit]- ^ K. Ryan, (1993). "The role of natural language in requirements engineering," Proceedings of the IEEE International Symposium on Requirements Engineering, San Diego, CA, USA, 1993, pp. 240-242, https://doi.org/10.1109/ISRE.1993.324852
- ^ Dardenne, A., van Lamsweerde, A., Fickas, S. (1993). Goal-directed requirements acquisition. Science of Computer Programming 20(1–2): 3-50. https://doi.org/10.1016/0167-6423(93)90021-G
- ^ S. J. Greenspan, J. Mylopoulos, and A. Borgida. (1982). "Capturing more world knowledge in the requirements specification." 6th International Conference on Software Engineering (ICSE '82), pp. 225–234.
- ^ B. Nuseibeh, J. Kramer and A. Finkelstein, (1993). "Expressing the relationships between multiple views in requirements specification," Proceedings of 1993 15th International Conference on Software Engineering, Baltimore, pp. 187-196, https://doi.org/10.1109/ICSE.1993.346045.
- ^ S. Fickas and M. S. Feather, (1995). "Requirements monitoring in dynamic environments," Proceedings of 1995 IEEE International Symposium on Requirements Engineering (RE'95), pp. 140-147, https://doi.org/10.1109/ISRE.1995.512555.
- ^ A. I. Anton, (1996) "Goal-based requirements analysis," Proceedings of the Second International Conference on Requirements Engineering, Colorado Springs, pp. 136-144, https://doi.org/10.1109/ICRE.1996.491438.
- ^ van Lamsweerde, A. (2009). Requirements Engineering: From System Goals to UML Models to Software Specifications. United States: Wiley.
- ^ Wiegers, K., Beatty, J. (2013). Software Requirements. United States: Pearson Education.
- in-depth (not just passing mentions about the subject)
- reliable
- secondary
- independent of the subject
Make sure you add references that meet these criteria before resubmitting. Learn about mistakes to avoid when addressing this issue. If no additional references exist, the subject is not suitable for Wikipedia.