Requirements Engineering

Im Rahmen des Requirements Engineerings widmen wir uns folgenden Schwerpunkten:

  • Problem Frames
  • Requirement Engineering for Security & Safety
  • Requirements Interaction Analysis
  • UML-Profile & Tools
Veröffentlichungen
YearTitleAuthorJournal/ProceedingsPublisher
2014 Optimizing functional and quality requirements according to stakeholders’ goals

[BibTeX]

Alebrahim, A., Choppy, C., Faßbender, S. & Heisel, M. System Quality and Software Architecture (SQSA)    
BibTeX: 
@incollection{SQSA2014},
  year = {2014},
  title = {Optimizing functional and quality requirements according to stakeholders’ goals},
  booktitle = {System Quality and Software Architecture (SQSA)},
  author = {Alebrahim, Azadeh and Choppy, Christine and Fa{\ss}bender, Stephan and Heisel, Maritta},
  publisher = {Elsevier},
  pages = {75-120},
  doi = {http://dx.doi.org/10.1016/B978-0-12-417009-4.00004-1}
}
2014 Problem-Based Requirements Interaction Analysis

[BibTeX]

Alebrahim, A., Faßbender, S., Heisel, M. & Meis, R. Requirements Engineering: Foundation for Software Quality (REFSQ)   Springer International Publishing  
BibTeX: 
@inproceedings{REFSQ2014},
  year = {2014},
  title = {Problem-Based Requirements Interaction Analysis},
  booktitle = {Requirements Engineering: Foundation for Software Quality (REFSQ)},
  author = {Alebrahim, Azadeh and Faßbender, Stephan and Heisel, Maritta and Meis, Rene},
  publisher = {Springer International Publishing},
  volume = {LNCS 8396},
  pages = {200-215},
  url = {http://www.springerlink.com/}
}
2010 A Comparison of Security Requirements Engineering Methods

[Abstract] [BibTeX]

Fabian, B., Gürses, S., Heisel, M., Santen, T. & Schmidt, H. Requirements Engineering -- Special Issue on Security Requirements Engineering    
Abstract: This paper presents a conceptual framework for security engineering, with a strong focus on security requirements elicitation and analysis. This conceptual framework establishes a clear-cut vocabulary and makes explicit the interrelations between the different concepts and notions used in security engineering. Further, we apply our conceptual framework to compare and evaluate current security requirements engineering approaches, such as the Common Criteria, Secure Tropos, SREP, MSRA, as well as methods based on UML and problem frames. We review these methods and assess them according to different criteria, such as the general approach and scope of the method, its validation, and quality assurance capabilities. Finally, we discuss how these methods are related to the conceptual framework and to one another.
BibTeX: 
@article{FGH+2010},
  year = {2010},
  title = {A Comparison of Security Requirements Engineering Methods},
  author = {Fabian, Benjamin and G{\"u}rses, Seda and Heisel, Maritta and Santen, Thomas and Schmidt, Holger},
  journal = {Requirements Engineering -- Special Issue on Security Requirements Engineering},
  volume = {15},
  number = {1},
  pages = {7--40}
}
2010 Making Pattern- and Model-Based Software Development More Rigorous

[Abstract] [BibTeX] [pdf]

Hatebur, D. & Heisel, M. Proceedings of 12th International Conference on Formal Engineering Methods, ICFEM 2010, Shanghai, China   Springer  
Abstract: Pattern-based and model-based software development approaches have a high potential to improve the quality of software. Patterns allow engineers to re-use established and proven development knowledge. Developing software by constructing a sequence of models provides engineers with various possibilities for validation, because the different development models are not independent of each other and hence can be checked for coherence. We present a UML profile equipped with numerous OCL constraints that supports a pattern- and model-based software development process. The basis of the UML profile is a representation of problem frames, which are patterns supporting requirements analysis. OCL constraints provide a formal underpinning of the development process and allow one to perform semantic checks every time a new model is set up. Our approach is supported by a tool, called UML4PF. The tool is based on the Eclipse development environment, extended by an EMF-based UML tool, in our case, Papyrus. In this paper, we specifically focus on ensuring that problem frames are instantiated correctly. We illustrate our approach by the case study of an automatic teller machine.
BibTeX: 
@inproceedings{ICFEM10},
  year = {2010},
  title = {Making Pattern- and Model-Based Software Development More Rigorous},
  booktitle = {Proceedings of 12th International Conference on Formal Engineering Methods, ICFEM 2010, Shanghai, China},
  author = {Denis Hatebur and Maritta Heisel},
  publisher = {Springer},
  series = {LNCS 6447},
  pages = {253-269},
  url = {http://www.springerlink.com/}
}
2010 A UML Profile for Requirements Analysis of Dependable Software

[Abstract] [BibTeX] [pdf]

Hatebur, D. & Heisel, M. Proceedings of the International Conference on Computer Safety, Reliability and Security (SAFECOMP)   Springer  
Abstract: At Safecomp 2009, we presented a foundation for requirements analysis of dependable software. We defined a set of patterns for expressing and analyzing dependability requirements, such as confidentiality, integrity, availability, and reliability. The patterns take into account random faults as well as certain attacks and therefore support a combined safety and security engineering. In this paper, we demonstrate how the application of our patterns can be tool supported. We present a UML profile allowing us to express the different dependability requirements using UML diagrams. Integrity conditions are expressed using OCL. We provide tool support based on the Eclipse development environment, extended with an EMF-based UML tool, e.g., Papyrus UML. We illustrate how to use the profile to model dependability requirements of a cooperative adaptive cruise control system.
BibTeX: 
@inproceedings{Safecomp10},
  year = {2010},
  title = {A {UML} Profile for Requirements Analysis of Dependable Software},
  booktitle = {Proceedings of the International Conference on Computer Safety, Reliability and Security (SAFECOMP)},
  author = {Hatebur, Denis and Heisel, Maritta},
  publisher = {Springer},
  series = {LNCS 6351},
  pages = {317-331},
  url = {http://www.springerlink.com/}
}
2010 UML4PF – A Tool for Problem-Oriented Requirements Analysis

[BibTeX] [pdf]

Heisel, M., S. H. I. C.    
BibTeX: 
@techreport{UML4PF},
  year = {2010},
  title = {UML4PF – A Tool for Problem-Oriented Requirements Analysis},
  author = {Heisel, M., Schmidt, H., Isabelle C\^ot\'e}
}
2009 A Foundation for Requirements Analysis of Dependable Software

[Abstract] [BibTeX] [pdf]

Hatebur, D. & Heisel, M. Proceedings of the International Conference on Computer Safety, Reliability and Security (SAFECOMP)   Springer  
Abstract: We present patterns for expressing dependability requirements, such as confidentiality, integrity, availability, and reliability. The paper considers random faults as well as certain attacks and therefore supports a combined safety and security engineering. The patterns - attached to functional requirements - are part of a pattern system that can be used to identify missing requirements. The approach is illustrated on a cooperative adaptive cruise control system.
BibTeX: 
@inproceedings{HateburHeisel2009},
  year = {2009},
  title = {A Foundation for Requirements Analysis of Dependable Software},
  booktitle = {Proceedings of the International Conference on Computer Safety, Reliability and Security (SAFECOMP)},
  author = {Hatebur, Denis and Heisel, Maritta},
  publisher = {Springer},
  series = {LNCS 5775},
  pages = {311--325},
  url = {http://www.springerlink.com/}
}
2008 A Systematic Account of Problem Frames

[Abstract] [BibTeX] [pdf]

Côté, I., Hatebur, D., Heisel, M., Schmidt, H. & Wentzlaff, I. Proceedings of the European Conference on Pattern Languages of Programs (EuroPLoP)   Universitätsverlag Konstanz  
Abstract: We give an enumeration of possible problem frames, based on domain characteristics, and comment on the usefulness of the obtained frames. In particular, we investigate problem domains and their characteristics in detail. This leads to finegrained criteria for describing problem domains. As a result, we identify a new type of problem domain and come up with integrity conditions for problem frames. Taking a complete enumeration of possible problem frames (with at most three problem domains) as a basis, we find 8 new problem frames, 7 of which we consider as useful in practical software development.
BibTeX: 
@inproceedings{europlop07},
  year = {2008},
  title = {A Systematic Account of Problem Frames},
  booktitle = {Proceedings of the European Conference on Pattern Languages of Programs (EuroPLoP)},
  author = {C\^ot\'e, Isabelle and Hatebur, Denis and Heisel, Maritta and Schmidt, Holger and Wentzlaff, Ina},
  publisher = {Universit{\"a}tsverlag Konstanz},
  pages = {749-767},
  url = {http://www.uvk.de/},
  doi = {http://www.uvk.de/}
}