Research Topics
Research Topic Requirements Engineering
Key issues:- Problem Frames
- Requirement Engineering for Security & Safety
- Requirements Interaction Analysis
- UML-Profile & Tools
| Year | Title | Author | Journal/Proceedings | Publisher | |
|---|---|---|---|---|---|
| 2017 | A structured and systematic model-based development method for automotive systems, considering the OEM/supplier interface | Beckers, K., Côté, I., Frese, T., Hatebur, D. & Heisel, M. | Reliability Engineering & System Safety | ||
| Abstract: Abstract The released ISO 26262 standard for automotive systems requires to create a hazard analysis and risk assessment and to create safety goals, to break down these safety goals into functional safety requirements in the functional safety concept, to specify technical safety requirements in the safety requirements specification, and to perform several validation and verification activities. Experience shows that the definition of technical safety requirements and the planning and execution of validation and verification activities has to be done jointly by OEMs and suppliers. In this paper, we present a structured and model-based safety development approach for automotive systems. The different steps are based on Jackson's requirement engineering. The elements are represented by UML notation extended with stereotypes. The UML model enables a rigorous validation of several constraints. We make use of the results of previously published work to be able to focus on the OEM/supplier interface. We illustrate our method using a three-wheeled-tilting control system (3WTC) as running example and case study. | |||||
BibTeX:
@article{Beckers2016-4,
year = {2017},
title = {A structured and systematic model-based development method for automotive systems, considering the OEM/supplier interface},
author = {Beckers, Kristian and C{\^{o}}t{\'{e}}, Isabelle and Frese, Thomas and Hatebur, Denis and Heisel, Maritta},
journal = {Reliability Engineering \& System Safety},
volume = {158},
pages = {172 - 184},
note = {Special Sections : Reliability and Safety Certification of Software-Intensive Systems},
url = {http://www.sciencedirect.com/science/article/pii/S0951832016304057},
doi = {10.1016/j.ress.2016.08.018}
}
|
|||||
| 2017 | A structured hazard analysis and risk assessment method for automotive systems—A descriptive study | Beckers, K., Holling, D., Côté, I. & Hatebur, D. | Reliability Engineering & System Safety | ||
| Abstract: Abstract The 2011 release of the first version of the ISO 26262 standard for automotive systems demand the elicitation of safety goals following a rigorous method for hazard and risk analysis. Companies are struggling with the adoption of the standard due to ambiguities, documentation demands and the alignment of the standards demands to existing processes. We previously proposed a structured engineering method to deal with these problems developed in applying action research together with an OEM. In this work, we evaluate how applicable the method is for junior automotive software engineers by a descriptive study. We provided the method to 8 members of the master course Automotive Software Engineering (ASE) at the Technical University Munich. The participants have each been working in the automotive industry for 1–4 years in parallel to their studies. We investigated their application of our method to an electronic steering column lock system. The participants applied our method in a first round alone and afterwards discussed their results in groups. Our data analysis revealed that the participants could apply the method successfully and the hazard analysis and risk assessment achieved a high precision and productivity. Moreover, the precision could be improved significantly during group discussions. | |||||
BibTeX:
@article{Beckers2016-5,
year = {2017},
title = {A structured hazard analysis and risk assessment method for automotive systems—A descriptive study},
author = {Beckers, Kristian and Holling, Dominik and C{\^{o}}t{\'{e}}, Isabelle and Hatebur, Denis},
journal = {Reliability Engineering & System Safety},
volume = {158},
pages = {185 - 195},
note = {Special Sections : Reliability and Safety Certification of Software-Intensive Systems},
url = {http://www.sciencedirect.com/science/article/pii/S0951832016305002},
doi = {10.1016/j.ress.2016.09.004}
}
|
|||||
| 2017 | Facilitating Reuse of Control Software through Context Modelling based on the Six-Variable Model [BibTeX] |
Ulfat-Bunyadi, N., Meis, R. & Heisel, M. | Software Technologies | Springer | |
BibTeX:
@incollection{CCIS17,
year = {2017},
title = {Facilitating Reuse of Control Software through Context Modelling based on the Six-Variable Model},
booktitle = {Software Technologies},
author = {Ulfat-Bunyadi, Nelufar and Meis, Rene and Heisel, Maritta},
publisher = {Springer},
volume = {743},
series = {Communications in Computer and Information Science},
pages = {332-358},
url = {http://www.springer.com}
}
|
|||||
| 2017 | Aspect Frames – Describing Cross-Cutting Concerns in Aspect-Oriented Requirements Engineering | Meis, R. & Heisel, M. | Proceedings of the 22nd European Conference on Pattern Languages of Programs | ACM | |
| Abstract: Cross-cutting concerns often arise when non-functional requirements are operationalized, because non-functional requirements are themselves cross-cutting. In the field of aspect-oriented requirements engineering (AORE), functional requirements that cross-cut multiple other functional requirements are called aspects. An aspect describes in most cases a solution for a non- functional requirement and how this solution can be integrated into the realization of the functional requirements it cross-cuts. Examples for cross-cutting concerns are logging, encryption, and access control. We observed that aspects often share a basic structure, behavior, and the way of how they have to be integrated into the realization of the functional requirements they cross-cut. We propose in this paper aspect frames. An aspect frame is a kind of pattern for aspects that share a common concern, behavior, and way how they are integrated into the realization of the functional requirements |
|||||
BibTeX:
@inproceedings{EuroPLoP17,
year = {2017},
title = {Aspect Frames – Describing Cross-Cutting Concerns in Aspect-Oriented Requirements Engineering},
booktitle = {Proceedings of the 22nd European Conference on Pattern Languages of Programs},
author = {Meis, Rene and Heisel, Maritta},
publisher = {ACM},
number = {25},
series = {EuroPLoP '17},
pages = {28},
url = {https://doi.org/10.1145/3147704.3147732},
doi = {3147704.3147732}
}
|
|||||
| 2017 | Computer-Aided Identification and Validation of Intervenability Requirements | Meis, R. & Heisel, M. | Information | ||
| Abstract: Privacy as a software quality is becoming more important these days and should not be underestimated during the development of software that processes personal data. The privacy goal of intervenability, in contrast to unlinkability (including anonymity and pseudonymity), has so far received little attention in research. Intervenability aims for the empowerment of end-users by keeping their personal data and how it is processed by the software system under their control. Several surveys have pointed out that the lack of intervenability options is a central privacy concern of end-users. In this paper, we systematically assess the privacy goal of intervenability and set up a software requirements taxonomy that relates the identi�ed intervenability requirements with a taxonomy of transparency requirements. Furthermore, we provide a tool-supported method to identify intervenability requirements from the functional requirements of a software system. This tool-supported method provides the means to elicit and validate intervenability requirements in a computer-aided way. Our combined taxonomy of intervenability and transparency requirements gives a detailed view on the privacy goal of intervenability and its relation to transparency. We validated the completeness of our taxonomy by comparing it to the relevant literature that we derived based on a systematic literature review. The proposed method for the identi�cation of intervenability requirements shall support requirements engineers to elicit and document intervenability requirements in compliance with the EU General Data Protection Regulation. | |||||
BibTeX:
@article{Information2017,
year = {2017},
title = {Computer-Aided Identification and Validation of Intervenability Requirements},
author = {Meis, Rene and Heisel, Maritta},
journal = {Information},
volume = {8},
number = {30},
url = {http://www.mdpi.com/2078-2489/8/1/30},
doi = {10.3390/info8010030}
}
|
|||||
| 2017 | Deriving Safety Requirements according to ISO 26262 for complex systems: A method applied in the automotive industrie | Frese, T., Heisel, M., Hatebur, D. & Côté, I. | Innovative Produkte und Dienstleisungen in der Mobilität | ||
BibTeX:
@article{mobi2017,
year = {2017},
title = {Deriving Safety Requirements according to ISO 26262 for complex systems: A method applied in the automotive industrie},
author = {Frese, Thomas and Heisel, Maritta and Hatebur, Denis and C{\^{o}}t{\'{e}}, Isabelle},
journal = {Innovative Produkte und Dienstleisungen in der Mobilit{\"{a}}t},
volume = {Wissenschaftsforum Mobilit{\"{a}}t 8},
pages = {211-222}
}
|
|||||
| 2017 | Towards Systematic Privacy and Operability (PRIOP) Studies | Meis, R. & Heisel, M. | ICT Systems Security and Privacy Protection | Springer | |
| Abstract: The assessment of privacy properties of software systems gains more and more importance nowadays. This is, on the one hand because of increasing privacy concerns of end-users due to numerous reported privacy breaches, and on the other hand due to stricter data protection regulations, e.g., the EU General Data Protection Regulation that prescribes an assessment of the privacy implications that a project possibly has. The lack of systematic methods to assist a comprehensive and detailed privacy analysis makes it hard for analysts to address the end-users’ and legal requirements. In this paper, we adopt the principles of the hazard and operability (HAZOP) studies, which have successfully been used for safety analyses, to privacy to provide a systematic method to identify the relevant privacy threats for a software to be developed. We propose a method called privacy and operability (PRIOP) studies that allows to systematically analyze the potential privacy issues that a software to be developed might raise, based on the software’s functionality at the requirements level. | |||||
BibTeX:
@inproceedings{SEC17,
year = {2017},
title = {Towards Systematic Privacy and Operability ({PRIOP}) Studies},
booktitle = {ICT Systems Security and Privacy Protection},
author = {Meis, Rene and Heisel, Maritta},
publisher = {Springer},
volume = {502},
series = {IFIP AICT},
pages = {427--441},
url = {http://dx.doi.org/10.1007/978-3-319-58469-0_29},
doi = {10.1007/978-3-319-58469-0_29}
}
|
|||||
| 2017 | Pattern-based Representation of Privacy Enhancing Technologies as Early Aspects | Meis, R. & Heisel, M. | Trust, Privacy, and Security in Digital Business | Springer International Publishing | |
| Abstract: Several regulations and standards emphasize that privacy shall already be considered from the very beginning in software development. A crucial point during the development of a privacy-friendly software is the selection and integration of measures that implement speci c privacy requirements or mitigate threats to these. These measures are called privacy enhancing technologies (PETs). PETs have a crosscutting nature. That is, a PET needs often to be integrated into several base functionalities of the software-to-be. For example, anonymization techniques need to be integrated into functionalities that shall reveal originally identi able information in an anonymized form to others. One possibility to handle cross-cutting concerns already on the requirements level is aspect-oriented requirements engineering. In this paper, we show how PETs can be represented as early aspects and how these can be integrated into a given requirements model in problem frames notation. Furthermore, we show how PETs can be represented as patterns to help requirements engineers to identify and select appropriate PETs that address the privacy requirements they have to satisfy. We use the PET Privacy-ABCs (Attribute-Based Credentials) to illustrate our approach. |
|||||
BibTeX:
@inproceedings{TrustBus17,
year = {2017},
title = {Pattern-based Representation of Privacy Enhancing Technologies as Early Aspects},
booktitle = {Trust, Privacy, and Security in Digital Business},
author = {Meis, Rene and Heisel, Maritta},
publisher = {Springer International Publishing},
volume = {10442},
series = {LNCS},
pages = {49--65},
url = {https://doi.org/10.1007/978-3-319-64483-7_4},
doi = {10.1007/978-3-319-64483-7_4}
}
|
|||||
| 2016 | Supporting Privacy Impact Assessments using Problem-based Privacy Analysis | Meis, R. & Heisel, M. | Software Technologies - 10th International Joint Conference, ICSOFT 2015, Revised Selected Papers | Springer | |
| Abstract: Privacy-aware software development is gaining more and more importance for nearly all information systems that are developed nowadays. As a tool to force organizations and companies to consider privacy properly during the planning and the execution of their projects, some governments advise to perform privacy impact assessments (PIAs). During a PIA, a report has to be created that summarizes the consequence on privacy the project may have and how the organization or company addresses these consequences. As basis for a PIA, it has to be documented which personal data is collected, processed, stored, and shared with others in the context of the project. Obtaining this information is a difficult task that is not yet well supported by existing methods. In this paper, we present a method based on the problem-based privacy analysis (ProPAn) that helps to elicit the needed information for a PIA systematically from a given set of functional requirements. Our tool-supported method shall reduce the effort that has to be spent to elicit the information needed to conduct a PIA in a way that the information is as complete and consistent as possible. | |||||
BibTeX:
@inproceedings{CCIS16,
year = {2016},
title = {Supporting Privacy Impact Assessments using Problem-based Privacy Analysis},
booktitle = {Software Technologies - 10th International Joint Conference, {ICSOFT} 2015, Revised Selected Papers},
author = {Meis, Rene and Heisel, Maritta},
publisher = {Springer},
volume = {586},
series = {Communications in Computer and Information Science},
pages = {79--98},
url = {http://dx.doi.org/10.1007/978-3-319-30142-6_5},
doi = {10.1007/978-3-319-30142-6_5}
}
|
|||||
| 2016 | The Six-Variable Model - Context Modelling Enabling Systematic Reuse of Control Software | Ulfat-Bunyadi, N., Meis, R. & Heisel, M. | Proceedings of the 11th International Joint Conference on Software Technologies (ICSOFT 2016) | SciTePress | |
| Abstract: A control system usually consists of some control software as well as sensors and actuators to monitor and control certain quantities in the environment. The context of the control software thus consists of the sensors and actuators it uses and the environment. When starting development of the control software, its context is often not predefined or given. There are contextual decisions the developers can make (e.g. which sensors/actuators/other systems to use). By means of these decisions, the context is defined step by step. Existing approaches (like the Four-Variable Model) call for documenting the environmental quantities (monitored, controlled, input, and output variables) that are relevant after making these contextual decisions. The environmental quantities that have originally been relevant (i.e. before deciding which sensors/actuators/other systems to use) are not documented. This results in problems when the software shall later on be reused in another, slightly different setting (e.g. with additional sensors). Then, it is hard for developers to decide which environmental quantities are still relevant for the software. In this paper, we suggest an extended version of the Four-Variable Model, the Six-Variable Model, and, based on that, a context modelling method, that combines existing approaches. The benefit of our method is that the environmental quantities that are relevant before and after decision making are documented as well as the contextual decisions themselves and the options that were selectable. In this way, later reuse of the software is facilitated. | |||||
BibTeX:
@inproceedings{ICSOFT16a,
year = {2016},
title = {The Six-Variable Model - Context Modelling Enabling Systematic Reuse of Control Software},
booktitle = {Proceedings of the 11th International Joint Conference on Software Technologies {(ICSOFT} 2016)},
author = {Ulfat-Bunyadi, Nelufar and Meis, Rene and Heisel, Maritta},
publisher = {SciTePress},
pages = {15--26},
url = {http://www.scitepress.org/DigitalLibrary/Link.aspx?doi=10.5220/0005944100150026},
doi = {10.5220/0005944100150026}
}
|
|||||
| 2016 | Introducing Product Line Engineering in a Bottom-up Approach | Ulfat-Bunyadi, N., Meis, R., Mohammadi, N. G. & Heisel, M. | Proceedings of the 11th International Joint Conference on Software Technologies (ICSOFT 2016) | SciTePress | |
| Abstract: The optimal way for introducing a product line is to set up a completely new product line by developing a reuse infrastructure for the whole range of products right from the start. However, in practice, product line engineering is frequently introduced by a company after having developed a number of products separately (i.e. in single system engineering). The challenge then consists of defining the product line based on these existing products, i.e. to a certain extent these products have to be re-engineered. More precisely, two problems need to be solved: first, commonality and variability among the existing products needs to be identified to define a common set of core assets, and, second, the way in which future systems (i.e. products of the product line) will be developed based on this common set of assets needs to be defined. The method we suggest in this paper solves these two problems. Our method focuses on control systems, i.e. systems which monitor/control certain quantities in their environment. | |||||
BibTeX:
@inproceedings{ICSOFT16b,
year = {2016},
title = {Introducing Product Line Engineering in a Bottom-up Approach},
booktitle = {Proceedings of the 11th International Joint Conference on Software Technologies {(ICSOFT} 2016)},
author = {Ulfat-Bunyadi, Nelufar and Meis, Rene and Mohammadi, Nazila Gol and Heisel, Maritta},
publisher = {SciTePress},
pages = {146--153},
url = {http://www.scitepress.org/DigitalLibrary/Link.aspx?doi=10.5220/0006006001460153},
doi = {10.5220/0006006001460153}
}
|
|||||
| 2016 | Computer-Aided Identification and Validation of Privacy Requirements | Meis, R. & Heisel, M. | Information | MDPI | |
| Abstract: Privacy is a software quality that is closely related to security. The main difference is that security properties aim at the protection of assets that are crucial for the considered system, and privacy aims at the protection of personal data that are processed by the system. The identification of privacy protection needs in complex systems is a hard and error prone task. Stakeholders whose personal data are processed might be overlooked, or the sensitivity and the need of protection of the personal data might be underestimated. The later personal data and the needs to protect them are identified during the development process, the more expensive it is to fix these issues, because the needed changes of the system-to-be often affect many functionalities. In this paper, we present a systematic method to identify the privacy needs of a software system based on a set of functional requirements by extending the problem-based privacy analysis (ProPAn) method. Our method is tool-supported and automated where possible to reduce the effort that has to be spent for the privacy analysis, which is especially important when considering complex systems. The contribution of this paper is a semi-automatic method to identify the relevant privacy requirements for a software-to-be based on its functional requirements. The considered privacy requirements address all dimensions of privacy that are relevant for software development. As our method is solely based on the functional requirements of the system to be, we enable users of our method to identify the privacy protection needs that have to be addressed by the software-to-be at an early stage of the development. As initial evaluation of our method, we show its applicability on a small electronic health system scenario. | |||||
BibTeX:
@article{Information16,
year = {2016},
title = {Computer-Aided Identification and Validation of Privacy Requirements},
author = {Meis, Rene and Heisel, Maritta},
journal = {Information},
publisher = {MDPI},
volume = {7},
number = {28},
url = {http://www.mdpi.com/2078-2489/7/2/28},
doi = {10.3390/info7020028}
}
|
|||||
| 2016 | Understanding the Privacy Goal Intervenability | Meis, R. & Heisel, M. | Trust, Privacy, and Security in Digital Business | Springer | |
| Abstract: Privacy is gaining more and more attention in society and hence, gains more importance as a software quality that has to be considered during software development. A privacy goal that has not yet been deeply studied is the empowerment of end-users to have control over how their personal data is processed by information systems. This privacy goal is called intervenability. Several surveys have shown that one of end-users’ main privacy concerns is the lack of intervenability options in information systems. In this paper, we refine the privacy goal intervenability into a software requirements taxonomy and relate it to a taxonomy of transparency requirements because transparency can be regarded as a prerequisite for intervenability. The combined taxonomy of intervenability and transparency requirements shall guide requirements engineers to identify the intervenability requirements relevant for the system they consider. We validated the completeness of our taxonomy by comparing it to the relevant literature that we derived based on a systematic literature review. | |||||
BibTeX:
@inproceedings{TrustBus16,
year = {2016},
title = {Understanding the Privacy Goal Intervenability},
booktitle = {Trust, Privacy, and Security in Digital Business},
author = {Meis, Rene and Heisel, Maritta},
publisher = {Springer},
volume = {9830},
series = {LNCS},
pages = {79--94},
url = {https://link.springer.com/chapter/10.1007%2F978-3-319-44341-6_6},
doi = {10.1007/978-3-319-44341-6_6}
}
|
|||||
| 2015 | A Problem-, Quality-, and Aspect-Oriented Requirements Engineering Method | Faßbender, S., Heisel, M. & Meis, R. | Software Technologies - 9th International Joint Conference, ICSOFT 2014, Vienna, Austria, August 29-31, 2014, Revised Selected Papers | Springer | |
| Abstract: Requirements engineers not only have to cope with the requirements of various stakeholders for complex software systems, they also have to consider several software qualities (e.g., performance, maintainability, security, and privacy) that the system-to-be shall address. In such a situation, it is challenging for requirements engineers to develop a complete and coherent set of requirements for the system-to-be. Separation of concerns has shown to be one option to handle the complexity of systems. The problem frames approach address this principle by decomposing the problem of building the system-to-be into simpler subproblems. Aspect-orientation aims at separating cross-cutting functionalities into separate functionalities, called aspects. We propose a method called AORE4PF, which shows that aspect-orientation can be integrated into the problem frames approach to increase the separation of concerns and to benefit from several methods that exist on problem frames to develop a complete and coherent set of requirements. We validated our method with a small experiment in the field of crisis management. |
|||||
BibTeX:
@inproceedings{CCIS15a,
year = {2015},
title = {A Problem-, Quality-, and Aspect-Oriented Requirements Engineering Method},
booktitle = {Software Technologies - 9th International Joint Conference, {ICSOFT} 2014, Vienna, Austria, August 29-31, 2014, Revised Selected Papers},
author = {Fa{\ss}bender, Stephan and Heisel, Maritta and Meis, Rene},
publisher = {Springer},
volume = {555},
series = {Communications in Computer and Information Science},
pages = {291--310},
url = {http://dx.doi.org/10.1007/978-3-319-25579-8_17},
doi = {10.1007/978-3-319-25579-8_17}
}
|
|||||
| 2015 | Problem-Based Security Requirements Elicitation and Refinement with PresSuRE | Faßbender, S., Heisel, M. & Meis, R. | Software Technologies - 9th International Joint Conference, ICSOFT 2014, Vienna, Austria, August 29-31, 2014, Revised Selected Papers | Springer | |
| Abstract: Recently published reports on cybercrime indicate an ever-increasing number of security incidents related to IT systems. Many attacks causing the incidents abuse (in)directly one or more security defects. Fixing the security defect once fielded is costly. To avoid the defects and the subsequent need to fix them, security has to be considered thoroughly when developing software. The earliest phase to do so is the requirements engineering, in which security threats should be identified early on and treated by defining sufficient security requirements. In a previous paper, we introduced a methodology for Problem-based Security Requirements Elicitation (PresSuRE). PresSuRE provides a computer-aided security threat identification. The identification is based on the functional requirements for a system-to-be. Still, there is a need for guidance on how to derive security requirements once the threats are identified. In this work, we provide such guidance extending PresSuRE and its tool support. We illustrate and validate our approach using a smart grid scenario provided by the industrial partners of the EU project NESSoS. |
|||||
BibTeX:
@incollection{CCIS15b,
year = {2015},
title = {Problem-Based Security Requirements Elicitation and Refinement with PresSuRE},
booktitle = {Software Technologies - 9th International Joint Conference, {ICSOFT} 2014, Vienna, Austria, August 29-31, 2014, Revised Selected Papers},
author = {Fa{\ss}bender, Stephan and Heisel, Maritta and Meis, Rene},
publisher = {Springer},
volume = {555},
series = {Communications in Computer and Information Science},
pages = {311--330},
url = {http://dx.doi.org/10.1007/978-3-319-25579-8_18},
doi = {10.1007/978-3-319-25579-8_18}
}
|
|||||
| 2015 | Challenges in Rendering and Maintaining Trustworthiness for Long-Living Software Systems | Alebrahim, A., Mohammadi, N. G. & Heisel, M. | Proceedings of the 2nd Collaborative Workshop on Evolution and Maintenance of Long-Living Software Systems (EMLS), GI Software Engineering Tagung SE | CEUR-WS.org | |
| Abstract: Trustworthiness plays a key role in acceptance and adoption of software by the end-users. When maintaining long-living software systems, trustworthiness has to be addressed since trust of the end-user is volatile and can change over time. In this paper, we discuss the challenges regarding trustworthiness of long-living software systems. Trustworthiness should be considered in the whole life-cycle of a long-living system, i.e., in all development phases aiming at building trustworthiness into the core of the system at design-time and later maintaining it during run-time. But, our focus in this paper is on challenges in requirements engineering and also planning for the run-time activities, e.g., what are the needed monitor interfaces, what are the planned actions and how are the execution interfaces for performing those actions. |
|||||
BibTeX:
@inproceedings{EMLS2015,
year = {2015},
title = {Challenges in Rendering and Maintaining Trustworthiness for Long-Living Software Systems},
booktitle = {Proceedings of the 2nd Collaborative Workshop on Evolution and Maintenance of Long-Living Software Systems (EMLS), GI Software Engineering Tagung SE},
author = {Alebrahim, Azadeh and Mohammadi, Nazila Gol and Heisel, Maritta},
publisher = {CEUR-WS.org},
volume = {1337},
series = {{CEUR} Workshop Proceedings},
pages = {103--105},
url = {http://ceur-ws.org/Vol-1337/paper14.pdf}
}
|
|||||
| 2015 | Applying Performance Patterns for Requirements Analysis | Alebrahim, A. & Heisel, M. | Proceedings of the 20th European Conference on Pattern Languages of Programs (EuroPLoP) | ACM | |
| Abstract: Performance as one of the critical quality requirements for the success of a software system must be integrated into software development from the beginning to prevent performance problems. Analyzing and modeling performance demands knowledge of performance experts and analysts. In order to integrate performance analysis into software analysis and design methods, performance-specific properties known as domain knowledge have to be identified, analyzed, and documented properly. In this paper, we propose the performance analysis method PoPeRA to guide the requirements engineer in dealing with performance problems as early as possible in requirements analysis. Our structured method provides support for identifying potential performance problems using performance-specific domain knowledge attached to the requirement models. To deal with identified performance problems, we make use of performance analysis patterns to be applied to the requirement models in the requirements engineering phase. To show the application of our approach, we illustrate it with the case study CoCoME, a trading system to be deployed in supermarkets for handling sales. |
|||||
BibTeX:
@inproceedings{Europlop2015-1,
year = {2015},
title = {Applying Performance Patterns for Requirements Analysis},
booktitle = {Proceedings of the 20th European Conference on Pattern Languages of Programs (EuroPLoP)},
author = {Alebrahim, Azadeh and Heisel, Maritta},
publisher = {ACM},
url = {https://dl.acm.org/citation.cfm?id=2855357}
}
|
|||||
| 2015 | Transforming Process Models to Problem Frames | Faßbender, S. & Aysolmaz, B. | Springer | ||
| Abstract: An increase of process awareness within organizations and advances in IT systems led to a development of process-aware information systems (PAIS) in many organizations. UPROM is developed as a unified BPM methodology to conduct business process and user requirements analysis for PAIS in an integrated way. However, due to the purpose, granularity and form of UPROM artifacts, one cannot analyze the software requirements in detail with (semi-)formal methods for properties such as completeness, compliance and quality. In contrast, Problem Frames modeled using the UML4PF tool can be used for such analysis. But using the Problem Frames notation and corresponding methods alone does not cover a direct support for building a PAIS. Hence, in this work we propose to integrate UPROM and UML4PF using model transformation. We use eCompany, a project which is part of an e-government program, as running example. | |||||
BibTeX:
@inproceedings{FassbenderA2015,
year = {2015},
title = {Transforming Process Models to Problem Frames},
author = {Fa{\ss}bender, Stephan and Aysolmaz, Banu},
publisher = {Springer},
series = {LNBIB},
url = {www.springer.com}
}
|
|||||
| 2015 | Systematic Identification of Information Flows from Requirements to support Privacy Impact Assessments | Meis, R. & Heisel, M. | ICSOFT-PT 2015 - Proc. of the 10th Int. Conf. on Software Paradigm Trends | SciTePress | |
| Abstract: Several countries prescribe or advise government departments and organizations to perform a privacy impact assessment (PIA) if these prepare new projects or change existing ones that involve personal information. A PIA shall summarize what personal information is collected, processed, stored, and distributed in the context of the project. But there is only little support for undertaking a PIA and to create a PIA report, most countries only provide vague guidelines and simple templates. We present in this paper an extension of the problem-based privacy analysis (ProPAn) method that derives information needed to conduct a PIA from a requirements model in problem frame notation. We provide a formally specified method with well-defined steps and tool support to reduce the effort to be spent for eliciting the needed information and to ensure that the needed information is as complete and coherent as possible to form an adequate basis for the creation of a PIA report. |
|||||
BibTeX:
@inproceedings{ICSOFT15,
year = {2015},
title = {Systematic Identification of Information Flows from Requirements to support Privacy Impact Assessments},
booktitle = {{ICSOFT-PT} 2015 - Proc. of the 10th Int. Conf. on Software Paradigm Trends},
author = {Meis, Rene and Heisel, Maritta},
publisher = {SciTePress},
pages = {43-52},
url = {http://dx.doi.org/10.5220/0005518500430052},
doi = {10.5220/0005518500430052}
}
|
|||||
| 2015 | Performance Analysis Patterns for Requirements Analysis | Alebrahim, A. | Proceedings of Student Research Forum Papers and Posters, the 41st International Conference on Current Trends in Theory and Practice of Computer Science (SOFSEM) | CEUR-WS.org | |
| Abstract: Many problems might arise when performance requirements are not taken into account from the beginning of software development. Architectural solutions such as performance patterns represent design decisions on the architecture level that might constrain quality requirements significantly. Knowledge which is gained in the solution space, for example from performance patterns, should be reflected in the requirements engineering to obtain sound architectures and correct requirements.We propose to reuse performance architectural patterns in the requirements engineering in a systematic manner to equip requirement models with performance solution approaches early in the software development process. To this end, we propose performance analysis patterns. The performance requirement models elaborated with performance analysis patterns can easily be transformed into a particular solution at the design level. |
|||||
BibTeX:
@inproceedings{SOFSEM2015,
year = {2015},
title = {Performance Analysis Patterns for Requirements Analysis},
booktitle = {Proceedings of Student Research Forum Papers and Posters, the 41st International Conference on Current Trends in Theory and Practice of Computer Science (SOFSEM)},
author = {Alebrahim, Azadeh},
publisher = {CEUR-WS.org},
volume = {1326},
series = {CEUR Workshop Proceedings},
pages = {54--66},
url = {http://ceur-ws.org/}
}
|
|||||
| 2015 | A Taxonomy of Requirements for the Privacy Goal Transparency | Meis, R., Heisel, M. & Wirtz, R. | Trust, Privacy, and Security in Digital Business | Springer | |
| Abstract: Privacy is a growing concern during software development. Transparency--in the sense of increasing user's privacy-awareness--is a privacy goal that is not as deeply studied in the literature as the properties anonymity and unlinkability. To be compliant with legislation and standards, requirements engineers have to identify the requirements on transparency that are relevant for the software to be developed. To assist the identification process, we provide a taxonomy of transparency requirements derived from legislation and standards. This taxonomy is validated using related research which was identified using a systematic literature review. Our proposed taxonomy can be used by requirements engineers as basis to systematically identify the relevant transparency requirements leading to a more complete and coherent set of requirements. |
|||||
BibTeX:
@inproceedings{TrustBus2015,
year = {2015},
title = {A Taxonomy of Requirements for the Privacy Goal Transparency},
booktitle = {Trust, Privacy, and Security in Digital Business},
author = {Meis, Rene and Heisel, Maritta and Wirtz, Roman},
publisher = {Springer},
series = {LNCS 9264},
pages = {195-209},
url = {http://dx.doi.org/10.5220/0005518500430052},
doi = {10.5220/0005518500430052}
}
|
|||||
| 2014 | Problem-oriented Security Patterns for Requirements Engineering | Alebrahim, A. & Heisel, M. | Proceedings of the 19th European Conference on Pattern Languages of Programs (EuroPLoP) | ACM | |
BibTeX:
@inproceedings{Alebrahim-europlop2014,
year = {2014},
title = {Problem-oriented Security Patterns for Requirements Engineering},
booktitle = {Proceedings of the 19th European Conference on Pattern Languages of Programs (EuroPLoP)},
author = {Alebrahim, Azadeh and Heisel, Maritta},
publisher = {ACM},
note = {Accepted},
url = {https://dl.acm.org/citation.cfm?id=2721963}
}
|
|||||
| 2014 | A Problem-based Approach for Computer Aided Privacy Threat Identification | Beckers, K., Faßbender, S., Heisel, M. & Meis, R. | Privacy Technologies and Policy | Springer | |
| Abstract: Recently, there has been an increase of reported privacy threats hitting large software systems. These threats can originate from stakeholders that are part of the system. Thus, it is crucial for software engineers to identify these privacy threats, refine these into privacy requirements, and design solutions that mitigate the threats. In this paper, we introduce our methodology named Problem-Based Privacy Analysis (ProPAn). The ProPAn method is an approach for identifying privacy threats during the requirements To capture the environment of the system, e.g., stakeholders and other IT systems, |
|||||
BibTeX:
@inproceedings{APF2012,
year = {2014},
title = {A Problem-based Approach for Computer Aided Privacy Threat Identification},
booktitle = {Privacy Technologies and Policy},
author = {Beckers, Kristian and Fa{\ss}bender, Stephan and Heisel, Maritta and Meis, Rene},
publisher = {Springer},
volume = {8319},
series = {LNCS},
pages = {1-16},
url = {http://dx.doi.org/10.1007/978-3-642-54069-1_1},
doi = {10.1007/978-3-642-54069-1_1}
}
|
|||||
| 2014 | Towards a Computer-aided Problem-oriented Variability Requirements Engineering Method | Alebrahim, A., Faßbender, S., Filipczyk, M., Goedicke, M., Heisel, M. & Konersmann, M. | Advanced Information Systems Engineering Workshops | Springer | |
| Abstract: In theory, software product lines are planned in advance, using established engineering methods. However, there are cases where commonalities and variabilities between several systems are only discovered after they have been developed individually as single systems. In retrospect, this leads to the hindsight that these systems should have been developed as a software product line from the beginning to reduce costs and effort. To cope with the challenge of detecting variability early on, we propose the PREVISE method, covering domain and application engineering. Domain engineering is concerned with exploring the variability caused by entities in the environment of the software and the variability in functional and quality requirements. In application engineering, the configuration for a concrete product is selected, and subsequently, a requirement model for a concrete product is derived. |
|||||
BibTeX:
@incollection{ASDENCA2014,
year = {2014},
title = {Towards a Computer-aided Problem-oriented Variability Requirements Engineering Method},
booktitle = {Advanced Information Systems Engineering Workshops},
author = {Alebrahim, Azadeh and Fa{\ss}bender, Stephan and Filipczyk, Martin and Goedicke, Michael and Heisel, Maritta and Konersmann, Marco},
publisher = {Springer},
series = {LNBIP 178},
pages = {136-147},
url = {https://link.springer.com/}
}
|
|||||
| 2014 | A Meta-Pattern and Pattern Form For Context-Patterns | Beckers, K., Faßbender, S. & Heisel, M. | Proceedings of the 19th European Conference on Pattern Languages of Programs (Europlop) | ACM | |
| Abstract: In a previous EuroPlop publication we introduced a catalog of context-patterns.We described common structures and stakeholders for several different domains in our context-patterns. The common elements of the context were obtained from observations about the domain in terms of standards, domain specific-publications, and implementations. Whenever a system-to-be is already described by a context-pattern, one can use this context-pattern to elicit domain knowledge via instantiation of the context-pattern. Moreover, we analyzed the common concepts in our context-patterns and created a meta-model to describe the relations between these concepts. This meta-model was the initial step towards a pattern language for context-patterns. In this work, we show the consequent next step for the definition of a pattern language for context-patterns. |
|||||
BibTeX:
@inproceedings{BeckersFassbender2014-europlop-A,
year = {2014},
title = {A Meta-Pattern and Pattern Form For Context-Patterns},
booktitle = {Proceedings of the 19th European Conference on Pattern Languages of Programs (Europlop)},
author = {Beckers, Kristian and Fa{\ss}bender, Stephan and Heisel, Maritta},
publisher = {ACM},
series = {EuroPloP'14},
pages = {5:1--5:23},
url = {http://doi.acm.org/10.1145/2721956.2721979},
doi = {10.1145/2721956.2721979}
}
|
|||||
| 2014 | Deriving a Pattern Language Syntax for Context-Patterns | Beckers, K., Faßbender, S. & Heisel, M. | Proceedings of the 19th European Conference on Pattern Languages of Programs (Europlop) | ACM | |
| Abstract: In a previous publication we introduced a catalog of context-patterns. Each context pattern describes common structures and stakeholders for a specific domain. The common elements of the context were obtained from observations about the domain in terms of standards, domain specific-publications, and implementations. Whenever the domain of a system-to-be is already described by a context-pattern, one can use this context-pattern to elicit domain knowledge by instantiating the corresponding context-pattern. Moreover, we analyzed the common concepts in our context-patterns and created a meta-model to describe the relations between these concepts. This meta-model was the initial step towards a pattern language for context-patterns. In this work, we show the consequent next step for the definition of a pattern language syntax for context-patterns. Thus, we describe how to derive the connections between the existing context-pattern in a structured way and present the results. |
|||||
BibTeX:
@inproceedings{BeckersFassbender2014-europlop-B,
year = {2014},
title = {Deriving a Pattern Language Syntax for Context-Patterns},
booktitle = {Proceedings of the 19th European Conference on Pattern Languages of Programs (Europlop)},
author = {Beckers, Kristian and Fa{\ss}bender, Stephan and Heisel, Maritta},
publisher = {ACM},
series = {EuroPLoP '14},
pages = {2:1--2:25},
url = {http://doi.acm.org/10.1145/2721956.2721967},
doi = {10.1145/2721956.2721967}
}
|
|||||
| 2014 | A Computer Aided Process From Problems to Laws in Requirements Engineering | Faßbender, S. & Heisel, M. | Software Technologies | Springer | |
| Abstract: In today’s world many products and services are highly dependent on software and information systems. With the growing importance of IT systems, legislators worldwide decided to regulate and enforce laws for IT systems. With respect to this situation, the impact of compliance on the development of IT sys- tems becomes more and more severe. Hence, software engineers have a need for techniques to deal with compliance. But identifying relevant compliance regu- lations for IT systems is a challenging task. We proposed patterns and a struc- tured method to tackle these problems [1]. A crucial step is the transformation of requirements into a structure, which allows for the identification of laws. The transformation step was described in general in [2]. This work describes a method to structure the requirements, elicit the needed domain knowledge and transform requirements into law identification pattern instances. The manual execution of this method was reported by us to be time consuming and tedious. Hence, in this work we identify the points for (semi-)automation, and we outline a first imple- mentation for the automation. We present our results using a voting system as an example, which was obtained from the ModIWa DFG1 project and the common criteria profile for voting systems. |
|||||
BibTeX:
@inproceedings{FassbenderH13_SDT,
year = {2014},
title = {A Computer Aided Process From Problems to Laws in Requirements Engineering},
booktitle = {Software Technologies},
author = {Fa{\ss}bender, Stephan and Heisel, Maritta},
publisher = {Springer},
volume = {457},
series = {Communications in Computer and Information Science},
pages = {215-234},
url = {http://link.springer.com/chapter/10.1007%2F978-3-662-44920-2_14},
doi = {10.1007/978-3-662-44920-2_14}
}
|
|||||
| 2014 | Intertwining Relationship between Requirements, Architecture, and Domain Knowledge | Alebrahim, A. & Heisel, M. | Proceedings of the 9th International Conference on Software Engineering Advances (ICSEA) | ||
| Abstract: In requirements engineering, properties of the environment and assumptions about it, called domain knowledge, need to be captured in addition to exploring the requirements. Despite the recognition of the significance of capturing the required domain knowledge, domain knowledge might be missing, left implicit, or be captured inadequately during the software development process, causing incorrect specifications and software failure. Domain knowledge affects the elicitation and evolution of requirements, the evolution of software architectures, and related design decisions. Conversely, requirements and design decisions affect the elicitation and modification of domain knowledge. In this paper, we propose the iterative capturing and co-developing of domain knowledge with requirements and software architectures. We explicitly discuss the effects of requirements and design decisions on domain knowledge and illustrate this relationship with examples drawn from our research, where we had to go back and forth between requirements, domain knowledge, and design decisions. |
|||||
BibTeX:
@inproceedings{ICSEA2014,
year = {2014},
title = {Intertwining Relationship between Requirements, Architecture, and Domain Knowledge},
booktitle = {Proceedings of the 9th International Conference on Software Engineering Advances (ICSEA)},
author = {Alebrahim, Azadeh and Heisel, Maritta},
volume = {421},
series = {IFIP Advances in Information and Communication Technology},
pages = {150--162}
}
|
|||||
| 2014 | Aspect-oriented Requirements Engineering with Problem Frames | Faßbender, S., Heisel, M. & Meis, R. | ICSOFT-PT 2014 - Proc. of the 9th Int. Conf. on Software Paradigm Trends | SciTePress | |
| Abstract: Nowadays, the requirements of various stakeholders for a system do not only increase the complexity of the system-to-be, but also contain different cross-cutting concerns. In such a situation, requirements engineers are really challenged to master the complexity and to deliver a coherent and complete description of the system-to-be. Hence, they are in need for methods which reduce the complexity, handle functional and quality requirements, check completeness and reveal interactions, and are tool supported to lower the effort. One possible option to handle the complexity of a system-to-be is the separation of concerns. Both, aspect-oriented requirements engineering and the problem frames approach implement this principle. Therefore, we propose a combination of both, the AORE4PF (Aspect-Oriented Requirements Engineering for Problem Frames) method. AORE4PF provides guidance for classifying requirements, separating the different concerns, modeling requirements for documentation and application of completeness and interaction analyses, and weaving the reusable parts to a complete and coherent system. AORE4PF provides tool support for most activities. We exemplify our method using a smart grid case obtained from the NESSoS project. For validation, the results of a small experiment in the field of crisis management systems are presented. | |||||
BibTeX:
@inproceedings{ICSOFT14Aspects,
year = {2014},
title = {Aspect-oriented Requirements Engineering with Problem Frames},
booktitle = {{ICSOFT-PT} 2014 - Proc. of the 9th Int. Conf. on Software Paradigm Trends},
author = {Fa{\ss}bender, Stephan and Heisel, Maritta and Meis, Rene},
publisher = {SciTePress},
pages = {145-156},
url = {http://dx.doi.org/10.5220/0005001801450156},
doi = {10.5220/0005001801450156}
}
|
|||||
| 2014 | Functional Requirements Under Security PresSuRE | Faßbender, S., Heisel, M. & Meis, R. | ICSOFT-PT 2014 - Proc. of the 9th Int. Conf. on Software Paradigm Trends | SciTePress | |
| Abstract: Recently, there has been an increase of reported security incidents hitting large software systems. Such incidents can originate from different attackers exploiting vulnerabilities of different parts of a system. Hence, there is a need for enhancing security considerations in software development. It is crucial for requirements engineers to identify security threats early on, and to refine the threats into security requirements. In this paper, we introduce a methodology for Problem-based Security Requirements Elicitation (PresSuRE). PresSuRE is a method for identifying security needs during the requirements analysis of software systems using a problem frame model. Our method does not rely entirely on the requirements engineer to detect security needs, but provides a computer-aided security threat identification, and subsequently the elicitation of security requirements. The identification is based on the functional requirements for a system-to-be. We illustrate and validate our approach using a smart grid scenario provided by the industrial partners of the EU project NESSoS. |
|||||
BibTeX:
@inproceedings{ICSOFT14Pressure,
year = {2014},
title = {Functional Requirements Under Security {PresSuRE}},
booktitle = {{ICSOFT-PT} 2014 - Proc. of the 9th Int. Conf. on Software Paradigm Trends},
author = {Fa{\ss}bender, Stephan and Heisel, Maritta and Meis, Rene},
publisher = {SciTePress},
pages = {5-16},
url = {http://dx.doi.org/10.5220/0005098600050016},
doi = {10.5220/0005098600050016}
}
|
|||||
| 2014 | Problem-Based Consideration of Privacy-Relevant Domain Knowledge | Meis, R. | Privacy and Identity Management for Emerging Services and Technologies | Springer | |
| Abstract: Especially for a privacy analysis, an adequate and accurate consideration of domain knowledge is needed. Domain knowledge is often only implicitly given and mainly stored in the minds of domain experts. It is important to make this implicit knowledge explicit and to use it in the privacy analysis of a software system. To our knowledge, no privacy-aware requirements engineering approach exists yet which explicitly considers the elicitation of privacy-relevant domain knowledge. This paper presents an extension of the problem-based privacy analysis (ProPAn) method. The extension consists of three parts. First, we elicit the relevant domain knowledge based on questionnaires which are derived from the stakeholder analysis literature. Second, we present generic patterns which can be instantiated to represent the elicited knowledge. Last, we extend the definitions of ProPAn's privacy graphs to take into account the domain knowledge. |
|||||
BibTeX:
@incollection{IFIP2013,
year = {2014},
title = {{Problem-Based Consideration of Privacy-Relevant Domain Knowledge}},
booktitle = {Privacy and Identity Management for Emerging Services and Technologies},
author = {Meis, Rene},
publisher = {Springer},
volume = {421},
series = {IFIP Advances in Information and Communication Technology},
url = {http://dx.doi.org/10.1007/978-3-642-55137-6_12},
doi = {10.1007/978-3-642-55137-6_12}
}
|
|||||
| 2014 | Problem-Based Requirements Interaction Analysis | Alebrahim, A., Faßbender, S., Heisel, M. & Meis, R. | Proceedings of the International Working Conference on Requirements Engineering: Foundation for Software Quality (REFSQ) | Springer | |
| Abstract: The ability to address the diverse interests of different stakeholders in a software project in a coherent way is one fundamental software quality. These diverse and maybe conflicting interests are reflected by the requirements of each stakeholder. Thus, it is likely that aggregated requirements for a software system contain interactions. To avoid unwanted interactions and improve software quality, we propose a structured method consisting of three phases to find such interactions. For our method, we use problem diagrams, which describe requirements in a structured way. The information represented in the problem diagrams is translated into a formal Z model. Then we reduce the number of combinations of requirements, which might conflict. The reduction of requirements interaction candidates is crucial to lower the effort of the in depth interaction analysis. For validation of our method, we use a real-life example in the domain of smart grid. |
|||||
BibTeX:
@inproceedings{REFSQ2014,
year = {2014},
title = {Problem-Based Requirements Interaction Analysis},
booktitle = {Proceedings of the International Working Conference on Requirements Engineering: Foundation for Software Quality ({REFSQ})},
author = {Alebrahim, Azadeh and Fa{\ss}bender, Stephan and Heisel, Maritta and Meis, Rene},
publisher = {Springer},
series = {LNCS 8396},
pages = {200--215},
url = {http://dx.doi.org/10.1007/978-3-319-05843-6_15},
doi = {10.1007/978-3-319-05843-6_15}
}
|
|||||
| 2014 | A Catalog of Security Requirements Patterns for the Domain of Cloud Computing Systems | Beckers, K., Côté, I. & Goeke, L. | ACM | ||
| Abstract: Security and privacy concerns are essential in cloud computing scenarios, because cloud customers and end customers have to trust the cloud provider with their critical business data and even their IT infrastructure. In projects these are often addressed late in the software development life-cycle, because these are difficult to elicit in cloud scenarios, due to the large amount of stakeholders and technologies involved. We contribute a catalog of security and privacy requirement patterns that support software engineers in eliciting these requirements. As requirements patterns provide artifacts for re-using requirements. This paper shows how these requirements can be classified according to cloud security and privacy goals. Furthermore, we provide a structured method on how to elicit the right requirements for a given scenario. We mined these requirements patterns from existing security analysis of public organizations such as ENISA and the Cloud Security Alliance, from our practical experience in the cloud domain, and from our previous research in cloud security. We validate our requirements patterns in co-operation with industrial partners of the ClouDAT project. |
|||||
BibTeX:
@inproceedings{SAC2014,
year = {2014},
title = {{A Catalog of Security Requirements Patterns for the Domain of Cloud Computing Systems}},
author = {Beckers, Kristian and C{\^{o}}t{\'{e}}, Isabelle and Goeke, Ludger},
publisher = {ACM},
url = {http://dl.acm.org/}
}
|
|||||
| 2014 | A Structured Approach for Eliciting, Modeling, and Using Quality-Related Domain Knowledge | Alebrahim, A., Heisel, M. & Meis, R. | Proceedings of the 14th International Conference on Computational Science and Its Applications (ICCSA) | Springer | |
| Abstract: In requirements engineering, properties of the environment and assumptions about it, called domain knowledge, need to be captured in addition to exploring the requirements. Despite the recognition of the significance of capturing and using the required domain knowledge, it might be missing, left implicit, or be captured inadequately during the software development. This results in an incorrect specification. Moreover, the software might fail to achieve its quality objectives because of ignored required constraints and assumptions. In order to analyze software quality properly, we propose a structured approach for eliciting, modeling, and using domain knowledge. We investigate what kind of quality-related domain knowledge is required for the early phases of quality-driven software development and how such domain knowledge can be systematically elicited and explicitly modeled to be used for the analysis of quality requirements. Our method aims at improving the quality of the requirements engineering process by facilitating the capturing and using of implicit domain knowledge. |
|||||
BibTeX:
@incollection{SQ2014,
year = {2014},
title = {A Structured Approach for Eliciting, Modeling, and Using Quality-Related Domain Knowledge},
booktitle = {Proceedings of the 14th International Conference on Computational Science and Its Applications (ICCSA)},
author = {Alebrahim, Azadeh and Heisel, Maritta and Meis, Rene},
publisher = {Springer},
series = {LNCS 8583},
pages = {370--386},
url = {http://dx.doi.org/10.1007/978-3-319-09156-3_27},
doi = {10.1007/978-3-319-09156-3_27}
}
|
|||||
| 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}
}
|
|||||
| 2014 | Privacy-Aware Cloud Deployment Scenario Selection | Beckers, K., Faßbender, S., Gritzalis, S., Heisel, M., Kalloniatis, C. & Meis, R. | Trust, Privacy, and Security in Digital Business | Springer | |
| Abstract: Nowadays, IT-resources are often out-sourced to clouds to reduce administration and hardware costs of the own IT infrastructure. There are different deployment scenarios for clouds that heavily differ in the costs for deployment and maintenance, but also in the number of stakeholders involved in the cloud and the control over the data in the cloud. These additional stakeholders can introduce new privacy threats into a system. Hence, there is a trade-off between the reduction of costs and addressing privacy concerns introduced by clouds. Our contribution is a structured method that assists decision makers in selecting an appropriate cloud deployment scenario. Our method is based on the privacy requirements of the system-to-be. These are analyzed on basis of the functional requirements using the problem-based privacy threat analysis (ProPAn). The concept of clouds is integrated into the requirements model, which is used by ProPAn to automatically generate privacy threat graphs. |
|||||
BibTeX:
@inproceedings{TrustBus2014,
year = {2014},
title = {Privacy-Aware Cloud Deployment Scenario Selection},
booktitle = {Trust, Privacy, and Security in Digital Business},
author = {Beckers, Kristian and Fa{\ss}bender, Stephan and Gritzalis, Stefanos and Heisel, Maritta and Kalloniatis, Christos and Meis, Rene},
publisher = {Springer},
series = {LNCS 8647},
pages = {94-105},
url = {http://dx.doi.org/10.1007/978-3-319-09770-1_9},
doi = {10.1007/978-3-319-09770-1_9}
}
|
|||||
| 2013 | Structured Pattern-Based Security Requirements Elicitation for Clouds [BibTeX] |
Beckers, K., Côté, I., Goeke, L., Güler, S. & Heisel, M. | Proceedings of the International Conference on Availability, Reliability and Security (ARES) - 7th International Workshop on Secure Software Engineering (SecSE 2013) | IEEE Computer Society | |
BibTeX:
@inproceedings{Beckers2013-ares2,
year = {2013},
title = {Structured Pattern-Based Security Requirements Elicitation for Clouds},
booktitle = {Proceedings of the International Conference on Availability, Reliability and Security ({ARES}) - 7th International Workshop on Secure Software Engineering (SecSE 2013)},
author = {Beckers, Kristian and C{\^{o}}t{\'{e}}, Isabelle and Goeke, Ludger and G{\"{u}}ler, Selim and Heisel, Maritta},
publisher = {IEEE Computer Society},
pages = {465-474},
url = {http://www.ieee.org/}
}
|
|||||
| 2013 | Combining Goal-oriented and Problem-oriented Requirements Engineering Methods | Beckers, K., Faßbender, S., Heisel, M. & Paci, F. | Proceedings of the International Cross Domain Conference and Workshop (CD-ARES 2013) | Springer | |
| Abstract: Several requirements engineering methods exist that differ in their abstraction level and in their view on the system-to-be. Two fundamentally different classes of requirements engineering methods are goal- and problem-based methods. Goal-based methods analyze the goals of stakeholders towards the systemto- be. Problem-based methods focus on decomposing the development problem into simple sub-problems. Goal-based methods use a higher abstraction level that consider only the parts of a system that are relevant for a goal and provide the means to analyze and solve goal conflicts. Problem-based methods use a lower abstraction level that describes the entire system-to-be. A combination of these methods enables a seamless software development, which considers stakeholders’ goals and a comprehensive view on the system-to-be at the requirements level. We propose a requirements engineering method that combines the goalbased method SI* and the problem-based method Problem Frames. We propose to analyze the issues between different goals of stakeholders first using the SI* method. Our method provides the means to use the resulting SI* models as input for the problem frame method. These Problem Frame models can be refined into architectures using existing research. Thus, we provide a combined requirements engineering method that considers all stakeholder views and provides a detailed system specification. We illustrate our method using an E-Health example. |
|||||
BibTeX:
@inproceedings{Beckers2013-cdares2,
year = {2013},
title = {Combining Goal-oriented and Problem-oriented Requirements Engineering Methods},
booktitle = {Proceedings of the International Cross Domain Conference and Workshop (CD-ARES 2013)},
author = {Beckers, Kristian and Fa{\ss}bender, Stephan and Heisel, Maritta and Paci, Federica},
publisher = {Springer},
series = {LNCS 8127},
pages = {178-194},
url = {http://www.springerlink.com/}
}
|
|||||
| 2013 | A Meta-Model Approach to the Fundamentals for a Pattern Language for Context Elicitation | Beckers, K., Faßbender, S. & Heisel, M. | Proceedings of the 18th European Conference on Pattern Languages of Programs (Europlop) | ACM | |
| Abstract: It is essential for building the right software system to elicit and analyze requirements. Requirements define what right is, without them a checking if the right software was built is impossible. Writing requirements that can achieve this purpose is only possible if the domain knowledge of the system-to-be and its environment is known and considered thoroughly. We consider this as the context problem of software development. In the past, we tackled this problem by describing common structures and stakeholders for several different domains. The common elements of the context where obtained by from observations about the domain in terms of standards, domain specific publications and implementations. Whenever a system-to-be is within the context of a domain already described by a context elicitation pattern, one can use this pattern to describe the context by instantiation. But the description of the structure of a context elicitation pattern, especially in terms of its static structure, was not aligned. This inhibits relating context elicitation patterns to form a patter language. Also describing newly observed pattern is difficult for inexperienced pattern creators without any guidance. We present these patterns, show how we used them to construct our meta-model, and give an example how to describe a context elicitation pattern using the meta-model. We propose a meta model for describing context patterns. The meta model contains elements, which can be used to structure and describe domain knowledge in a generic form. These context patterns can afterwards be instantiated with the domain knowledge required for software engineering. We presented a number of context patterns for different areas of domain knowledge in the past. This work is based on these existing patterns, which we abstracted into a meta-model. We present our context patterns, show how we used them to construct our metamodel, and provide an example of how to describe a context elicitation pattern using our meta-model. We contribute this meta model as a basis for a pattern language for context elicitation. |
|||||
BibTeX:
@inproceedings{Beckers2013-europlop,
year = {2013},
title = {A Meta-Model Approach to the Fundamentals for a Pattern Language for Context Elicitation},
booktitle = {Proceedings of the 18th European Conference on Pattern Languages of Programs (Europlop)},
author = {Beckers, Kristian and Fa{\ss}bender, Stephan and Heisel, Maritta},
publisher = {ACM},
pages = {-},
note = {Accepted for Publication},
url = {http://dl.acm.org/}
}
|
|||||
| 2013 | A Meta-Model for Context-Patterns | Beckers, K., Faßbender, S. & Heisel, M. | Proceedings of the 18th European Conference on Pattern Languages of Program | ACM | |
| Abstract: It is essential for building the right software system to elicit and analyze requirements. Writing requirements that can achieve the purpose of building the right system is only possible if the domain knowledge of the system-to-be and its environment is known and considered thoroughly. We consider this as the context problem of software development. In the past, we tackled this problem by describing common structures and stakeholders for several different domains. The common elements of the context were obtained from observations about the domain in terms of standards, domain specific p u blications a n d i m plementations. But the d escription of t h e structure of a context-pattern, especially in terms of its static structure, was not aligned. This inhibits relating context-patterns to form a pattern language. It is also difficult for inexperienced pattern creators to describe newly observed patterns without any guidance. We propose a meta model for describing context-patterns. The meta model contains elements, which can be used to structure and describe domain knowledge in a generic form. These context-patterns can afterwards be instantiated with the domain knowledge required for software engineering. This work is based on already existing patterns, which we abstracted into a meta-model. We present our context-patterns, show how we used them to construct our meta-model, and provide an example of how to describe a context-pattern using our meta-model. We contribute this meta model as a basis for a pattern language for context elicitation. |
|||||
BibTeX:
@inproceedings{BeckersFassbender2013ACM-europlop,
year = {2013},
title = {A Meta-Model for Context-Patterns},
booktitle = {Proceedings of the 18th European Conference on Pattern Languages of Program},
author = {Beckers, Kristian and Fa{\ss}bender, Stephan and Heisel, Maritta},
publisher = {ACM},
series = {EuroPLoP '13},
pages = {5:1--5:15},
url = {http://doi.acm.org/10.1145/2739011.2739016},
doi = {10.1145/2739011.2739016}
}
|
|||||
| 2013 | A Framework for Combining Problem Frames and Goal Models to Support Context Analysis during Requirements Engineering | Mohammadi, N. G., Alebrahim, A., Weyer, T., Heisel, M. & Pohl, K. | Proceedings of the 5th International Cross-Domain Conference on Availability, Reliability, and Security in Information Systems and HCI (CD-ARES) | Springer | |
| Abstract: Quality requirements, like security requirements, are dicult to elicit, especially if they cross multiple domains. Understanding these domains is an important issue in the requirements engineering process for the corresponding systems. Well-known requirements engineering ap- proaches, such as goal-oriented techniques provide a good starting point in capturing security requirements in the form of soft-goals in the early stage of the software engineering process. However, such approaches are not sucient for context and problem analysis. On the other hand, the context and problem modeling approaches like e.g., problem frames, do not address the system goals. Integrating the relevant context knowledge into goal models is a promising approach to address the mutual limita- tions. In this paper, we propose a framework for combining goal models and problem frames. The framework makes it possible to document the goals of the system together with the corresponding knowledge of the system's context. Furthermore, it supports the process of re ning (soft-) goals right up to the elicitation of corresponding security requirements. To show the applicability of our approach, we illustrate its application on a real-life case study concerning Smart Grids. |
|||||
BibTeX:
@inproceedings{CDARES2013,
year = {2013},
title = {A Framework for Combining Problem Frames and Goal Models to Support Context Analysis during Requirements Engineering},
booktitle = {Proceedings of the 5th International Cross-Domain Conference on Availability, Reliability, and Security in Information Systems and HCI (CD-ARES)},
author = {Mohammadi, Nazila Gol and Alebrahim, Azadeh and Weyer, Thorsten and Heisel, Maritta and Pohl, Klaus},
publisher = {Springer},
series = {LNCS 8127},
pages = {272--288},
url = {https://link.springer.com/}
}
|
|||||
| 2013 | From Problems to Laws in Requirements Engineering Using Model-Transformation (Best Students Paper Award) | Faßbender, S. & Heisel, M. | ICSOFT 2013 - Proceedings of the 8th International Conference on Software Paradigm Trends | SciTePress | |
| Abstract: Nowadays, many legislators decided to enact different laws, which all enforce legal and natural persons to deal more carefully with IT systems. Hence, there is a need for techniques to identify and analyze laws, which are relevant for an IT system. But identifying relevant compliance regulations for an IT system and aligning it to be compliant to these regulations is a challenging task. In earlier works of ours we proposed patterns and a structured method to tackle these problems. One of the central crucial steps, while using the patterns and the method, is the transformation of requirements into a structure, allowing the identification of laws. The step is not trivial, as requirements, in most cases, focus on the technical parts of the problem, putting the knowledge about the environment of the system aside. In this work, we propose a method to structure the requirements, elicit the needed domain knowledge and transform requirements into law identification pattern instances. For this purpose, we make use of problem diagrams, problem frames, domain knowledge, and questionnaire. We present our method using a voting system as an example, which was obtained from the ModIWa DFGa project and the common criteria profile for voting systems |
|||||
BibTeX:
@inproceedings{FassbenderH13_icsoft,
year = {2013},
title = {From Problems to Laws in Requirements Engineering Using Model-Transformation (Best Students Paper Award)},
booktitle = {ICSOFT 2013 - Proceedings of the 8th International Conference on Software Paradigm Trends},
author = {Fa{\ss}bender, Stephan and Heisel, Maritta},
publisher = {SciTePress},
pages = {447-458},
url = {http://www.scitepress.org/DigitalLibrary/Link.aspx?doi=10.5220/0004490804470458},
doi = {10.5220/0004490804470458}
}
|
|||||
| 2012 | Comparing Privacy Requirements Engineering Approaches [BibTeX] |
Beckers, K. | Proceedings of the International Conference on Availability, Reliability and Security (ARES) - 6th International Workshop on Secure Software Engineering (SecSE 2012) | IEEE Computer Society | |
BibTeX:
@inproceedings{Beckers2012-ares2,
year = {2012},
title = {Comparing Privacy Requirements Engineering Approaches},
booktitle = {Proceedings of the International Conference on Availability, Reliability and Security ({ARES}) - 6th International Workshop on Secure Software Engineering (SecSE 2012)},
author = {Beckers, Kristian},
publisher = {IEEE Computer Society},
pages = {574-581},
url = {http://www.ieee.org/}
}
|
|||||
| 2012 | Using Security Requirements Engineering Approaches to Support ISO 27001 Information Security Management Systems Development and Documentation | Beckers, K., Heisel, M., Faßbender, S. & Schmidt, H. | Proceedings of the International Conference on Availability, Reliability and Security (ARES) | IEEE Computer Society | |
| Abstract: An ISO 27001 compliant information security management system is difficult to create, due to the the limited support for system development and documentation provided in the standard. We present a structured analysis of the documentation and development requirements in the ISO 27001 standard. Moreover, we investigate to what extent existing security requirements engineering approaches fulfill these requirements. We developed relations between these approaches and the ISO 27001 standard using a conceptual framework originally developed for comparing security requirements engineering methods. The relations include comparisons of important terms, techniques, and documentation artifacts. In addition, we show practical applications of our results. |
|||||
BibTeX:
@inproceedings{Beckers2012-ares4,
year = {2012},
title = {Using Security Requirements Engineering Approaches to Support ISO 27001 Information Security Management Systems Development and Documentation},
booktitle = {Proceedings of the International Conference on Availability, Reliability and Security ({ARES})},
author = {Beckers, Kristian and Heisel, Maritta and Fa{\ss}bender, Stephan and Schmidt, Holger},
publisher = {IEEE Computer Society},
pages = {243-248},
url = {http://www.ieee.org/}
}
|
|||||
| 2012 | An integrated Method for Pattern-based Elicitation of Legal Requirements applied to a Cloud Computing Example | Beckers, K., Faßbender, S. & Schmidt, H. | Proceedings of the International Conference on Availability, Reliability and Security (ARES) - 2nd International Workshop on Resilience and IT-Risk in Social Infrastructures (RISI 2012) | IEEE Computer Society | |
| Abstract: Considering legal aspects during software development is a challenging problem, due to the cross-disciplinary expertise required. The problem is even more complex for cloud computing systems, because of the international distribution, huge amounts of processed data, and a large number of stakeholders that own or process the data. Approaches exist to deal with parts of the problem, but they are isolated from each other. We present an integrated method for elicitation of legal requirements. A cloud computing online banking scenario illustrates the application of our methods. The running example deals with the problem of storing personal information in the cloud and based upon the BDSG. We describe the structure of the online banking cloud system using an existing pattern-based approach. The elicited information is further refined and processed into functional requirements for software development. Moreover, our method covers the analysis of security-relevant concepts such as assets and attackers particularly with regard to laws. The requirements artifacts then serve as inputs for existing patterns for the identification of laws relevant for the online banking cloud system. Finally, our method helps to systematically derive functional as well as security requirements that realize the previously identified laws. |
|||||
BibTeX:
@inproceedings{Beckers2012-ares5,
year = {2012},
title = {An integrated Method for Pattern-based Elicitation of Legal Requirements applied to a Cloud Computing Example},
booktitle = {Proceedings of the International Conference on Availability, Reliability and Security ({ARES}) - 2nd International Workshop on Resilience and IT-Risk in Social Infrastructures (RISI 2012)},
author = {Beckers, Kristian and Fa{\ss}bender, Stephan and Schmidt, Holger},
publisher = {IEEE Computer Society},
pages = {463-472},
url = {http://www.ieee.org/}
}
|
|||||
| 2012 | Supporting the Development and Documentation of Trustworthy ICT Systems according to Security Standard through Patterns and Security Requirements Engineering Approaches [BibTeX] |
Beckers, K. | Electronic Proc. of the 1st ESSoS Doctoral Symposium, ESSoS-DS 2012 | CEUR-WS.org | |
BibTeX:
@other{BeckersESoSDS2012,
year = {2012},
title = {{S}upporting the {D}evelopment and {D}ocumentation of {T}rustworthy {ICT} {S}ystems according to {S}ecurity {S}tandard through {P}atterns and {S}ecurity {R}equirements {E}ngineering {A}pproaches},
booktitle = {Electronic Proc. of the 1st ESSoS Doctoral Symposium, ESSoS-DS 2012},
author = {Beckers, Kristian},
publisher = {CEUR-WS.org},
volume = {834},
pages = {65-70},
url = {http://CEUR-WS.org}
}
|
|||||
| 2012 | A Pattern-Based Method for Identifying and Analyzing Laws | Beckers, K., Faßbender, S., Küster, J.-C. & Schmidt, H. | Proceedings of the International Working Conference onRequirements Engineering: Foundation for Software Quality (REFSQ) | Springer | |
| Abstract: This paper presents a novel method for identifying and analyzing laws. The method makes use of different kinds of law analysis patterns that allow legal experts and software and system developers to understand and elicit relevant laws for the given development problem. Our approach also helps to detect dependent laws. We illustrate our method using an online-banking cloud scenario. |
|||||
BibTeX:
@inproceedings{BeckersFKS12,
year = {2012},
title = {A Pattern-Based Method for Identifying and Analyzing Laws},
booktitle = {Proceedings of the International Working Conference onRequirements Engineering: Foundation for Software Quality ({REFSQ})},
author = {Beckers, Kristian and Fa{\ss}bender, Stephan and K{\"{u}}ster, Jan-Christoph and Schmidt, Holger},
publisher = {Springer},
series = {LNCS 7195},
pages = {256-262},
url = {https://link.springer.com/chapter/10.1007%2F978-3-642-28714-5_23},
doi = {10.1007/978-3-642-28714-5_23}
}
|
|||||
| 2012 | Patterns- and Security-Requirements-Engineering-based Support for Development and Documentation of Security Standard Compliant ICT Systems [BibTeX] |
Beckers, K. | DOKTORANDENSYMPOSIUM DER SOFTWARE ENGINEERING 2012 PROCEEDINGS | Brandenburg University of Technology | |
BibTeX:
@other{BeckersSE2012,
year = {2012},
title = {{P}atterns- and {S}ecurity-{R}equirements-{E}ngineering-based {S}upport for {D}evelopment and {D}ocumentation of {S}ecurity {S}tandard {C}ompliant {ICT} {S}ystems},
booktitle = {DOKTORANDENSYMPOSIUM DER SOFTWARE ENGINEERING 2012 PROCEEDINGS},
author = {Beckers, Kristian},
publisher = {Brandenburg University of Technology},
volume = {01/12},
pages = {25-30},
url = {http://www-docs.tu-cottbus.de/programmiersprachen-compilerbau/public/publikationen/2012/DS-SE-2012.pdf}
}
|
|||||
| 2012 | An Aspect-Oriented Approach to Relating Security Requirements and Access Control | Alebrahim, A., Tun, T. T., Yu, Y., Heisel, M. & Nuseibeh, B. | Proceedings of the CAiSE Forum | CEUR-WS.org | |
| Abstract: Affecting multiple parts in software systems, security requirements often tangle with functional requirements. In order to separate crosscutting concerns and increase modularity, we propose to represent security requirements as aspects that can be woven into functional requirements. Using problem frames to model the functional requirements, weaving is achieved by composing the modules representing security aspects with the requirement models. Moreover, we provide guidance on how such security aspects are structured to implement a particular access control solution. As a result, such security aspects become reusable solution patterns to refne the structure of security-related problem. | |||||
BibTeX:
@inproceedings{CAiSEForum2012,
year = {2012},
title = {An Aspect-Oriented Approach to Relating Security Requirements and Access Control},
booktitle = {Proceedings of the CAiSE Forum},
author = {Alebrahim, Azadeh and Tun, Thein Than and Yu, Yijun and Heisel, Maritta and Nuseibeh, Bashar},
publisher = {CEUR-WS.org},
volume = {855},
series = {CEUR Workshop Proceedings},
pages = {15--22},
url = {http://ceur-ws.org/}
}
|
|||||
| 2012 | Enterprise Applications: From Requirements to Design | Choppy, C., Reggio, G., Hatebur, D. & Heisel, M. | Aligning Enterprise, System, and Software Architectures | IGI Global | |
BibTeX:
@incollection{CRHH2012,
year = {2012},
title = {Enterprise Applications: From Requirements to Design},
booktitle = {Aligning Enterprise, System, and Software Architectures},
author = {Choppy, Christine and Reggio, G. and Hatebur, Denis and Heisel, Maritta},
publisher = {IGI Global},
pages = {96--117},
url = {www.igi-global.com}
}
|
|||||
| 2012 | Supporting the Development and Documentation of ISO 27001 Information Security Management Systems Through Security Requirements Engineering Approaches | Beckers, K., Faßbender, S., Heisel, M., Küster, J.-C. & Schmidt, H. | Proceedings of the International Symposium on Engineering Secure Software and Systems (ESSoS) | Springer | |
| Abstract: Assembling an information security management system according to the ISO 27001 standard is difficult, because the standard provides only sparse support for system development and documentation. We analyse the ISO 27001 standard to determine what techniques and documentation are necessary and instrumental to develop and document systems according to this standard. Based on these insights, we inspect a number of current security requirements engineering approaches to evaluate whether and to what extent these approaches support ISO 27001 system development and documentation. We re-use a conceptual framework originally developed for comparing security requirements engineering methods to relate important terms, techniques, and documentation artifacts of the security requirements engineering methods to the ISO 27001. |
|||||
BibTeX:
@inproceedings{essos2012,
year = {2012},
title = {Supporting the Development and Documentation of {ISO} 27001 Information Security Management Systems Through Security Requirements Engineering Approaches},
booktitle = {Proceedings of the International Symposium on Engineering Secure Software and Systems ({ESSoS})},
author = {Beckers, Kristian and Fa{\ss}bender, Stephan and Heisel, Maritta and K{\"{u}}ster, Jan-Christoph and Schmidt, Holger},
publisher = {Springer},
series = {LNCS 7159},
url = {https://link.springer.com/}
}
|
|||||
| 2012 | Pattern- and Component-based Development of Dependable Systems | Hatebur, D. | School: University of Duisburg-Essen | Deutscher Wissenschafts-Verlag (DWV) Baden-Baden | |
BibTeX:
@phdthesis{Hatebur2012,
year = {2012},
title = {Pattern- and Component-based Development of Dependable Systems},
author = {Hatebur, Denis},
publisher = {Deutscher Wissenschafts-Verlag (DWV) Baden-Baden},
school = {University of Duisburg-Essen},
url = {http://www.dwverlag.de/index.php?art=Pattern-+and+Component-based+Development+of+Dependable+Systems&mod=Onlineshop&view=Artikel&abid=166}
}
|
|||||
| 2012 | Designing Architectures from Problem Descriptions by Interactive Model Transformation | Alebrahim, A., Côté, I., Heisel, M., Choppy, C. & Hatebur, D. | Proceedings 27th Symposium on Applied Computing | ACM | |
| Abstract: We present a structured approach to systematically derive a software architecture from a given problem description based on problem frames and a description of the environment. Our aim is to re-use the elements of the problem descriptions in creating the architecture. The derivation is performed by transforming the problem description into an initial architecture, where each subproblem corresponds to a component. The transformation is supported by model transformation rules, formally specified as operations with pre- and postconditions. This specification serves as a blueprint for a tool supporting the architectural design. We illustrate our method by the example of a patient care system. |
|||||
BibTeX:
@inproceedings{SAC2012,
year = {2012},
title = {Designing Architectures from Problem Descriptions by Interactive Model Transformation},
booktitle = {Proceedings 27th Symposium on Applied Computing},
author = {Alebrahim, Azadeh and C{\^{o}}t{\'{e}}, Isabelle and Heisel, Maritta and Choppy, Christine and Hatebur, Denis},
publisher = {ACM},
pages = {1256--1258},
url = {http://dl.acm.org/}
}
|
|||||
| 2012 | Pattern-based Context Establishment for Service-Oriented Architectures | Beckers, K., Faßbender, S., Heisel, M. & Meis, R. | Software Service and Application Engineering | Springer | |
| Abstract: A context description of a software system and its environment is essential for any given software engineering process. Requirements define statements about the environment (according to Jackson's terminology). The context description of a Service-Oriented Architecture is difficult to provide, because of the variety of technical systems and stakeholders involved. We present two patterns for SOA systems and support their instantiation with a structured method. In addition, we show how the pattern can be used in a secure service development life-cycle. |
|||||
BibTeX:
@inproceedings{sdps2012,
year = {2012},
title = {Pattern-based Context Establishment for Service-Oriented Architectures},
booktitle = {Software Service and Application Engineering},
author = {Beckers, Kristian and Fa{\ss}bender, Stephan and Heisel, Maritta and Meis, Rene},
publisher = {Springer},
series = {LNCS 7365},
pages = {81-101},
url = {http://dx.doi.org/10.1007/978-3-642-30835-2_7},
doi = {10.1007/978-3-642-30835-2_7}
}
|
|||||
| 2012 | Deriving Quality-based Architecture Alternatives with Patterns | Konersmann, M., Alebrahim, A., Heisel, M., Goedicke, M. & Kersten, B. | Software Engineering | GI | |
| Abstract: We propose in this paper an iterative method composed of three steps to derive architecture alternatives from quality requirements using a catalogue of patterns and styles. The solution candidates are chosen by answering a set of questions which reflects the requirements. We instantiate then the solution candidates using a UMLbased enhancement of the problem frame approach. To ensure that the instantiated architectures fulfill the quality requirements, we evaluate them in the next step. A desired refinement of the software architectures is then achieved by iterating over the described steps. |
|||||
BibTeX:
@inproceedings{SE2012,
year = {2012},
title = {Deriving Quality-based Architecture Alternatives with Patterns},
booktitle = {Software Engineering},
author = {Konersmann, Marco and Alebrahim, Azadeh and Heisel, Maritta and Goedicke, Michael and Kersten, Benjamin},
publisher = {GI},
series = {LNI 198},
pages = {71--82},
url = {www.gi.de}
}
|
|||||
| 2011 | Towards Systematic Integration of Quality Requirements into Software Architecture | Alebrahim, A., Hatebur, D. & Heisel, M. | Proceedings of the 5th European Conference on Software Architecture (ECSA 2011) | Springer | |
| Abstract: We present a model- and pattern-based approach that allows software engineers to take quality requirements into account right from the beginning of the software development process. The approach comprises requirements analysis as well as the software architecture design, in which quality requirements are re ected explicitly. |
|||||
BibTeX:
@inproceedings{AHH2011a,
year = {2011},
title = {Towards Systematic Integration of Quality Requirements into Software Architecture},
booktitle = {Proceedings of the 5th European Conference on Software Architecture (ECSA 2011)},
author = {Alebrahim, Azadeh and Hatebur, Denis and Heisel, Maritta},
publisher = {Springer},
series = {LNCS 6903},
pages = {17--25},
url = {https://link.springer.com/}
}
|
|||||
| 2011 | Connecting Security Requirements Analysis and Secure Design Using Patterns and UMLsec | Schmidt, H. & Jürjens, J. | Proceedings of the International Conference on Advanced Information Systems Engineering (CAiSE) | Springer | |
| Abstract: Existing approaches only provide informal guidelines for the transition from security requirements to secure design. Carrying out this transition is highly non-trivial and error-prone, leaving the risk of introducing vulnerabilities. This paper presents a pattern-oriented approach to connect security requirements analysis and secure architectural design. Following the divide & conquer principle, a software development problem is divided into simpler subproblems based on security requirements analysis patterns. We complement each of these patterns with architectural security patterns tailored to solve classes of security subproblems.We use UMLsec together with the advanced modeling possibilities for software architectures of UML 2.3 to equip the architectural security patterns with security properties, and to allow tool-supported analysis and composition of instances of these patterns. We validate our approach using two case studies and illustrate its support for Common Criteria certifications. |
|||||
BibTeX:
@inproceedings{caise11,
year = {2011},
title = {Connecting Security Requirements Analysis and Secure Design Using Patterns and {UMLsec}},
booktitle = {Proceedings of the International Conference on Advanced Information Systems Engineering ({CAiSE})},
author = {Schmidt, Holger and J{\"{u}}rjens, Jan},
publisher = {Springer},
series = {LNCS 6741},
pages = {367--382},
url = {https://link.springer.com/}
}
|
|||||
| 2011 | Systematic Architectural Design based on Problem Patterns | Choppy, C., Hatebur, D. & Heisel, M. | Relating Software Requirements and Architectures | Springer | |
| Abstract: We present a method to derive systematically software architectures from problem descriptions. The problem descriptions are based on the artifacts that are set up when following Jackson's problem frame approach. They include a context diagram describing the overall problem situation and a set of problem diagrams that describe subproblems of the overall software development problem. The different subproblems should be instances of problem frames, which are patterns for simple software development problems. Starting from these pattern-based problem descriptions, we derive a software architecture in three steps. An initial architecture contains one component for each subproblem. In the second step, we apply different architectural and design patterns and introduce coordinator and facade components. In the final step, the components of the intermediate architecture are re-arranged to form a layered architecture, and interface and driver components are added. All artefacts are expressed as UML diagrams, using specific UML profiles. The method is tool-supported. Our tool supports developers in setting up the diagrams, and it checks different validation conditions concerning the semantic integrity and the coherence of the different diagrams. We illustrate the method by deriving an architecture for an automated teller machine. |
|||||
BibTeX:
@incollection{CHH2011a,
year = {2011},
title = {Systematic Architectural Design based on Problem Patterns},
booktitle = {Relating Software Requirements and Architectures},
author = {Choppy, Christine and Hatebur, Denis and Heisel, Maritta},
publisher = {Springer},
pages = {133--159},
url = {https://link.springer.com/}
}
|
|||||
| 2011 | A UML Profile and Tool Support for Evolutionary Requirements Engineering | Côté, I. & Heisel, M. | Proceedings of the European Conference on Software Maintenance and Reengineering | IEEE | |
| Abstract: In this paper, we present a method to perform the first steps of software evolution, namely evolutionary requirements engineering, where new requirements have to be analyzed in the context of a set of already given requirements. The basic idea is to adjust an existing requirements engineering process so that evolution is supported. In the requirements engineering process we consider, the original software development problem is decomposed into a number of subproblems that are analyzed according to the problem frame approach [1]. Evolution is performed by defining rules for each process step and each document that is generated in the respective step to incorporate the new evolution requirements into the existing requirements documents or to create, when necessary, additional documents. We show that the evolution task benefits from the chosen problem decomposition. The described software evolution method is toolsupported. Our tool UML4PF, which is based on the Eclipse Modeling Framework, supports the problem frame approach to software engineering by a specifically defined UML profile. We extend that profile so that it also covers software evolution. |
|||||
BibTeX:
@inproceedings{CoteHeisel2011,
year = {2011},
title = {A {UML} Profile and Tool Support for Evolutionary Requirements Engineering},
booktitle = {Proceedings of the European Conference on Software Maintenance and Reengineering},
author = {C{\^{o}}t{\'{e}}, Isabelle and Heisel, Maritta},
publisher = {IEEE},
pages = {161--170},
url = {https://www.ieee.org/}
}
|
|||||
| 2011 | UML4PF -- A Tool for Problem-Oriented Requirements Analysis | Côté, I., Hatebur, D., Heisel, M. & Schmidt, H. | Proceedings of the International Conference on Requirements Engineering (RE) | IEEE Computer Society | |
| Abstract: We present a tool called UML4PF. This tool supports requirements analysis according to an enhanced version of Michael Jackson’s problem frame approach. UML4PF supports software engineers in developing a coherent and complete set of requirements documents. Moreover, it supports the systematic development of an appropriate software architecture. |
|||||
BibTeX:
@inproceedings{re2011,
year = {2011},
title = {{UML4PF} -- A Tool for Problem-Oriented Requirements Analysis},
booktitle = {Proceedings of the International Conference on Requirements Engineering ({RE})},
author = {C{\^{o}}t{\'{e}}, Isabelle and Hatebur, Denis and Heisel, Maritta and Schmidt, Holger},
publisher = {IEEE Computer Society},
pages = {349--350},
url = {https://www.ieee.org}
}
|
|||||
| 2011 | A Pattern- and Component-Based Method to Develop Secure Software | Schmidt, H., Hatebur, D. & Heisel, M. | Software Engineering for Secure Systems: Academic and Industrial Perspectives | IGI Global | |
| Abstract: We present a security engineering process based on security problem frames and concretized security problem frames. Both kinds of frames constitute patterns for analyzing security problems and associated solution approaches. They are arranged in a pattern system that makes dependencies between them explicit. We describe step-by-step how the pattern system can be used to analyze a given security problem and how solution approaches can be found. Afterwards, the security problems and the solution approaches are formally modeled in detail. The formal models serve to prove that the solution approaches are correct solutions to the security problems. Furthermore, the formal models of the solution approaches constitute a formal specification of the software to be developed. Then, the specification is implemented by generic security components and generic security architectures, which constitute architectural patterns. Finally, the generic security components and the generic security architecture that composes them are refined and the result is a secure software product built from existing and/or tailor-made security components. KEYWORDS security |
|||||
BibTeX:
@incollection{SHH2011,
year = {2011},
title = {A Pattern- and Component-Based Method to Develop Secure Software},
booktitle = {Software Engineering for Secure Systems: Academic and Industrial Perspectives},
author = {Schmidt, Holger and Hatebur, Denis and Heisel, Maritta},
publisher = {IGI Global},
pages = {32--74},
url = {http://www.igi-global.com/}
}
|
|||||
| 2011 | A Pattern-Based Method for Identifying and Analyzing Laws in the Field of Cloud Computing Compliance | Beckers, K., Faßbender, S., Küster, J.-C. & Schmidt, H. | |||
| Abstract: Cloud computing o ers highly exible and scalable usage of IT resources, from which companies can bene t. Clouds are sociotechnical systems with a high number of di erent kinds of stakeholders. Moreover, they are often geographically distributed, process critical data, and support sensitive IT processes. Therefore, aligning clouds to meet compliance regulations is a challenging task. Presently, this unsolved problem prevents companies from using clouds for critical tasks. This paper presents a novel method for identifying and analyzing laws for clouds. The method makes use of di erent kinds of patterns, which help to systematically elicit relevant laws. We present law analysis patterns that allow legal experts and software and system developers to understand and elicit relevant laws for the given development problem. Our approach also helps to detect dependent laws. Our law analysis patterns make use of results generated by the application of a cloud system analysis pattern and di erent kinds of stakeholder templates that serve to understand and describe a given cloud development problem. We illustrate our method using an online banking cloud scenario. |
|||||
BibTeX:
@techreport{,
year = {2011},
title = {A Pattern-Based Method for Identifying and Analyzing Laws in the Field of Cloud Computing Compliance},
author = {Beckers, Kristian and Fa{\ss}bender, Stephan and K{\"{u}}ster, Jan-Christoph and Schmidt, Holger}
}
|
|||||
| 2010 | A Comparison of Security Requirements Engineering Methods | 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 | Hatebur, D. & Heisel, M. | Proceedings of International Conference on Formal Engineering Methods (ICFEM) | 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{HateburHeisel2010a,
year = {2010},
title = {Making Pattern- and Model-Based Software Development More Rigorous},
booktitle = {Proceedings of International Conference on Formal Engineering Methods ({ICFEM})},
author = {Hatebur, Denis and Heisel, Maritta},
publisher = {Springer},
series = {LNCS 6447},
pages = {253--269},
url = {https://link.springer.com/}
}
|
|||||
| 2010 | A UML Profile for Requirements Analysis of Dependable Software | 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{HateburHeisel2010b,
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 = {https://link.springer.com/}
}
|
|||||
| 2010 | Automated Checking of Integrity Constraints for a Model- and Pattern-Based Requirements Engineering Method (Technical Report) | Côté, I., Hatebur, D. & Heisel, M. | |||
| Abstract: We present a new UML profile serving to support a pattern- and model-based requirements engineering method based on Jackson’s problem frames. The UML profile allows us to express the different models being defined during requirements analysis using UML diagrams. In order to automatically perform semantic validations associated with the method, we provide integrity conditions, expressed as OCL constraints. These constraints concern single models as well as the coherence of different models. To provide tool support for the requirements engineering method, we have developed a tool called UML4PF. It is based on the Eclipse development environment, extended by an EMF-based UML tool, in our case, Papyrus. To demonstrate the applicability of our approach, we use the case study of a vacation rentals reservation system. |
|||||
BibTeX:
@misc{,
year = {2010},
title = {Automated Checking of Integrity Constraints for a Model- and Pattern-Based Requirements Engineering Method (Technical Report)},
author = {C{\^{o}}t{\'{e}}, Isabelle and Hatebur, Denis and Heisel, Maritta}
}
|
|||||
| 2009 | A Foundation for Requirements Analysis of Dependable Software | 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{HH09b,
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 = {https://link.springer.com/}
}
|
|||||
| 2008 | Analysis and Component-based Realization of Security Requirements | Hatebur, D., Heisel, M. & Schmidt, H. | Proceedings of the International Conference on Availability, Reliability and Security (AReS) | IEEE Computer Society | |
| Abstract: We present a process to develop secure software with an extensive pattern-based security requirements engineering phase. It supports identifying and analyzing conflicts between different security requirements. In the design phase, we proceed by selecting security software components that achieve security requirements. The process enables software developers to systematically identify, analyze, and finally realize security requirements using security software components. We illustrate our approach by a lawyer agency software example. |
|||||
BibTeX:
@inproceedings{HHS2008b,
year = {2008},
title = {Analysis and Component-based Realization of Security Requirements},
booktitle = {Proceedings of the International Conference on Availability, Reliability and Security (AReS)},
author = {Hatebur, Denis and Heisel, Maritta and Schmidt, Holger},
publisher = {IEEE Computer Society},
series = {IEEE Transactions},
pages = {195--203},
url = {https://www.ieee.org}
}
|
|||||
| 2007 | A Pattern System for Security Requirements Engineering | Hatebur, D., Heisel, M. & Schmidt, H. | Proceedings of the International Conference on Availability, Reliability and Security (AReS) | IEEE Computer Society | |
| Abstract: We present a pattern system for security requirements engineering, consisting of security problem frames and concretized security problem frames. These are special kinds of problem frames that serve to structure, characterize, analyze, and finally solve software development problems in the area of software and system security. We equip each frame with formal preconditions and postconditions. The analysis of these conditions results in a pattern system that explicitly shows the dependencies between the different frames. Moreover, we indicate related frames, which are commonly used together with the considered frame. Hence, our approach helps security engineers to avoid omissions and to cover all security requirements that are relevant for a given problem. |
|||||
BibTeX:
@inproceedings{HHS2007,
year = {2007},
title = {A Pattern System for Security Requirements Engineering},
booktitle = {Proceedings of the International Conference on Availability, Reliability and Security (AReS)},
author = {Hatebur, Denis and Heisel, Maritta and Schmidt, Holger},
publisher = {IEEE Computer Society},
series = {IEEE Transactions},
pages = {356--365},
url = {https://www.ieee.org}
}
|
|||||
| 2007 | A Security Engineering Process based on Patterns | Hatebur, D., Heisel, M. & Schmidt, H. | Proceedings of the International Workshop on Secure Systems Methodologies using Patterns (SPatterns) | IEEE Computer Society | |
| Abstract: We present a security engineering process based on security problem frames and concretized security problem frames. Both kinds of frames constitute patterns for analyzing security problems and associated solution approaches. They are arranged in a pattern system that makes dependencies between them explicit. We describe step-by-step how the pattern system can be used to analyze a given security problem and how solution approaches can be found. Further, we introduce a new frame that focuses on the privacy requirement anonymity. |
|||||
BibTeX:
@inproceedings{HHS2007a,
year = {2007},
title = {A Security Engineering Process based on Patterns},
booktitle = {Proceedings of the International Workshop on Secure Systems Methodologies using Patterns (SPatterns)},
author = {Hatebur, Denis and Heisel, Maritta and Schmidt, Holger},
publisher = {IEEE Computer Society},
url = {https://www.ieee.org}
}
|
|||||
| 2006 | Security Engineering using Problem Frames | Hatebur, D., Heisel, M. & Schmidt, H. | Proceedings of the International Conference on Emerging Trends in Information and Communication Security (ETRICS) | Springer | |
| Abstract: We present a method for security engineering, which is based on two special kinds of problem frames that serve to structure, characterize, analyze, and finally solve software development problems in the area of software and system security. Both kinds of problem frames constitute patterns for representing security problems, variants of which occur frequently in practice.We present security problem frames, which are instantiated in the initial step of our method. They explicitly distinguish security problems from their solutions. To prepare the solution of the security problems in the next step, we employ concretized security problem frames capturing known approaches to achieve security. Finally, the last step of our method results in a specification of the system to be implemented given by concrete security mechanisms and instantiated generic sequence diagrams. We illustrate our approach by the example of a secure remote display system. |
|||||
BibTeX:
@inproceedings{HHS2006a,
year = {2006},
title = {Security Engineering using Problem Frames},
booktitle = {Proceedings of the International Conference on Emerging Trends in Information and Communication Security (ETRICS)},
author = {Hatebur, Denis and Heisel, Maritta and Schmidt, Holger},
publisher = {Springer},
volume = {3995/2006},
pages = {238--253},
url = {https://link.springer.com/}
}
|
|||||
| 2005 | Composing architectures based on architectural patterns for problem frames | Choppy, C., Hatebur, D. & Heisel, M. | |||
| Abstract: to be inserted | |||||
BibTeX:
@techreport{ChoppyHateburHeisel05,
year = {2005},
title = {Composing architectures based on architectural patterns for problem frames},
author = {Choppy, Christine and Hatebur, Denis and Heisel, Maritta},
note = {\tt http://swe.uni-duisburg-essen.de/intern/comparch05.pdf}
}
|
|||||
| 2005 | A Model-Based Development Process for Embedded Systems | Heisel, M. & Hatebur, D. | Proc. Workshop on Model-Based Development of Embedded Systems | ||
| Abstract: We present a development process for embedded systems which emerged from industrial practice. This process covers hardware and software components for systems engineering, but the main focus is on embedded software components and the modeling of problems, specications, tests and architectures. Each step of the process has validation conditions associated with it that help to detect errors as early as possible. |
|||||
BibTeX:
@inproceedings{HH2005a,
year = {2005},
title = {A Model-Based Development Process for Embedded Systems},
booktitle = {Proc. Workshop on Model-Based Development of Embedded Systems},
author = {Heisel, Maritta and Hatebur, Denis},
publisher = {Technical University of Braunschweig},
number = {TUBS-SSE-2005-01},
note = {Available at {\tt http://www.sse.cs.tu-bs.de/publications/MBEES-Tagungsband.pdf}}
}
|
|||||
| 2003 | Formalisation des besoins à l`aide de schémas LSCs | Souquières, J. & Heisel, M. | Proceedings Approches Formelles dans l'Assistance au Développement de Logiciels - AFADL'2003 | ||
| Abstract: Dans notre approche pour l'expression des besoins, nous proposons d'intégrer une étape de formalisation très tôt dans le développement an d'analyser de manière détaillée les besoins des utilisateurs et de découvrir les inconsistances et les problèmes à partir des difcultés rencontrées lors de la formalisation. An d'améliorer la lisibilité et l'écriture des besoins formalis és, nous proposons d'utiliser les LSCs, Life Sequence Charts, au lieu des formules pour la formalisation des besoins décomposés sous forme de fragments. Nous proposons, en particulier, des schémas graphiques pour exprimer différents types de besoins. Ces schémas constituent un guide à la formalisation. |
|||||
BibTeX:
@inproceedings{SH2003,
year = {2003},
title = {Formalisation des besoins {\`{a}} l`aide de sch{\'{e}}mas {LSCs}},
booktitle = {Proceedings Approches Formelles dans l'Assistance au D{\'{e}}veloppement de Logiciels - AFADL'2003},
author = {Souqui{\`{e}}res, Jeanine and Heisel, Maritta},
pages = {53--63},
note = {ISBN 2-7261-1236-6}
}
|
|||||
| 2002 | Logische Modellierung von Anwendungswelten aus Benutzersicht | Heisel, M. & Krömker, H. | Workshop Proceedings "Multimediale Informations- und Kommunikationssysteme, NET.OBJECT Days 2002" | ||
| Abstract: Der Softwareentwicklung fehlt oft eine detaillierte methodische Unterstützung von technischen Softwareentwicklungsaktivitäten. Eine Autorin dieses Papiers hat das Konzept der Agenda entwickelt, das zum Ziel hat, Softwareentwicklungswissen als "methodische Essenzen" von Softwareentwicklungsaktivitäten explizit zu repräsentieren. Zur logischen Modellierung von Anwendungswelten aus Benutzersicht wird eine Agenda entwickelt, die es erlaubt diese Anwendungswelt methodisch in Konzepten der Handlungspsychologie zu erheben. | |||||
BibTeX:
@inproceedings{Heisel2002,
year = {2002},
title = {Logische Modellierung von Anwendungswelten aus Benutzersicht},
booktitle = {Workshop Proceedings "Multimediale Informations- und Kommunikationssysteme, NET.OBJECT Days 2002"},
author = {Heisel, Maritta and Kr{\"{o}}mker, Heidi},
publisher = {tranSIT GmbH, Ilmenau},
pages = {649--656},
note = {ISBN 3-9808628-1-X}
}
|
|||||
| 2000 | A heuristic algorithm to detect feature interactions in requirements | Heisel, M. & Souquières, J. | Language Constructs for Describing Features | Springer-Verlag | |
| Abstract: We present a method to systematically detect feature interactions in requirements, which are expressed as constraints on system event traces. We show its application on the lift system, incorporating new features to a simple lift, concerning the lift overfull and the executive floor with priority. This method is part of a broader approach to requirements elicitation and formal specification. |
|||||
BibTeX:
@incollection{HS2000,
year = {2000},
title = {A heuristic algorithm to detect feature interactions in requirements},
booktitle = {Language Constructs for Describing Features},
author = {Heisel, Maritta and Souqui{\`{e}}res, Jeanine},
publisher = {Springer-Verlag},
pages = {143--162},
url = {http://www.springerlink.com/}
}
|
|||||
| 2000 | Une méthode pour l'élicitation des besoins: application au système de contrôle d'accès | Souquières, J. & Heisel, M. | Proceedings Approches Formelles dans l'Assistance au Développement de Logiciels - AFADL'2000 | ||
| Abstract: Cet article présente l'utilisation d'une approche systématique pour clarifier et analyser les besoins sur l'étude de cas d'un système de contrôle d'accès. L'approche intègre une détection systématique des interactions entre les différents besoins. | |||||
BibTeX:
@inproceedings{Souqui`eres2000,
year = {2000},
title = {Une m{\'{e}}thode pour l'{\'{e}}licitation des besoins: application au syst{\`{e}}me de contr{\^{o}}le d'acc{\`{e}}s},
booktitle = {Proceedings Approches Formelles dans l'Assistance au D{\'{e}}veloppement de Logiciels - AFADL'2000},
author = {Souqui{\`{e}}res, Jeanine and Heisel, Maritta},
publisher = {LSR-IMAG, Grenoble},
pages = {36--50},
note = {http://www-lsr.imag.fr/afadl/Programme/ProgrammeAFADL2000.html}
}
|
|||||
| 2000 | A Method for Systematic Requirements Elicitation: Application to the Light Control System | Souquières, J. & Heisel, M. | |||
| Abstract: This paper demonstrates the use of a systematic approach to clarify and analyze requirements of the light control case study. The approach includes a formalization of the requirements and the analysis of interactions between them. | |||||
BibTeX:
@techreport{Souqui`eres2000a,
year = {2000},
title = {A Method for Systematic Requirements Elicitation: Application to the Light Control System},
author = {Souqui{\`{e}}res, Jeanine and Heisel, Maritta},
number = {A00-R-090}
}
|
|||||
| 2000 | Structuring the First Steps of Requirements Elicitation | Souquières, J. & Heisel, M. | |||
| Abstract: to be inserted | |||||
BibTeX:
@techreport{Souqui`eres2000b,
year = {2000},
title = {Structuring the First Steps of Requirements Elicitation},
author = {Souqui{\`{e}}res, Jeanine and Heisel, Maritta},
number = {A00-R-123}
}
|
|||||
| 1999 | A Method for Requirements Elicitation and Formal Specification | Heisel, M. & Souquières, J. | Proceedings 18th International Conference on Conceptual Modeling, ER'99 | Springer | |
| Abstract: We propose a method for the elicitation and the expression of requirements. The requirements are then transformed in a systematic way into a formal specification. The approach - which distinguishes between requirements and specifications - gives methodological support for requirements elicitation and specification development. It avoids introducing new notations but builds on known techniques. | |||||
BibTeX:
@inproceedings{Heisel1999,
year = {1999},
title = {A Method for Requirements Elicitation and Formal Specification},
booktitle = {Proceedings 18th International Conference on Conceptual Modeling, ER'99},
author = {Heisel, Maritta and Souqui{\`{e}}res, Jeanine},
publisher = {Springer},
series = {LNCS 1728},
pages = {309--324},
url = {http://www.springerlink.com/}
}
|
|||||
| 1999 | De l'élicitation des besoins à la spécification formelle | Heisel, M. & Souquières, J. | Technique et science informatiques | ||
| Abstract: ABSTRACT. This paper proposes a method for the elicitation and the expression of requirements.It is based on a detailed analysis of requirements, leading to a better understanding of the problem to be solved. The approach – which clearly distinguishes between requirements and specifications – leads to the expression of a formal specification in a natural way. It does not introduce new languages but builds on known techniques. Agendas are used to describe the method | |||||
BibTeX:
@article{Heisel1999a,
year = {1999},
title = {De l'{\'{e}}licitation des besoins {\`{a}} la sp{\'{e}}cification formelle},
author = {Heisel, Maritta and Souqui{\`{e}}res, Jeanine},
journal = {Technique et science informatiques},
volume = {18},
number = {7},
pages = {777--801}
}
|
|||||
| 1998 | A Heuristic Algorithm to Detect Feature Interactions in Requirements | Heisel, M. & Souquières, J. | Proc. 5th Feature Interaction Workshop | ||
| Abstract: We present a heuristic algorithm to systematically detect feature interactions in requirments, which are exjpressed as constraints on systems event traces. The algorithm is part of a broader methodology for requirements elicitations and formal specification. Given a new constraint and a set of already accepted constraints, it computes a set of candidate constraints that possible interact with the new one. | |||||
BibTeX:
@inproceedings{Heisel1998e,
year = {1998},
title = {A Heuristic Algorithm to Detect Feature Interactions in Requirements},
booktitle = {Proc.\ 5th Feature Interaction Workshop},
author = {Heisel, Maritta and Souqui{\`{e}}res, Jeanine},
publisher = {IOS Press Amsterdam},
pages = {165--171}
}
|
|||||
| 1998 | Detecting Feature Interactions -- A Heuristic Approach | Heisel, M. & Souquières, J. | Proc. of the first FIREworks Workshop | ||
| Abstract: We present a method to systematically detect feature interactions in requirements. The requirements are expressed as constraints on system event traces. This method part is part of a broader approach to requirements elicitation and formal specification. | |||||
BibTeX:
@inproceedings{Heisel1998f,
year = {1998},
title = {Detecting Feature Interactions -- A Heuristic Approach},
booktitle = {Proc.\ of the first {FIRE}works Workshop},
author = {Heisel, Maritta and Souqui{\`{e}}res, Jeanine},
publisher = {Univ. Magdeburg},
series = {Preprint 10/98},
pages = {30--48}
}
|
|||||
| 1998 | Methodological Support for Requirements Elicitation and Formal Specification | Heisel, M. & Souquières, J. | Proc. 9th International Workshop on Software Specification and Design | IEEE Computer Society Press | |
| Abstract: We propose a method for the elicitation and the expression of requirements. The requirements can then be transformed in a systematic way into a formal specification that is a suitable basis for design and implementation of a software system. The approach – which distinguishes between requirements and specifications – gives methodological support for requirements elicitation and specification development. It does not introduce a new language but builds on known techniques. | |||||
BibTeX:
@inproceedings{Heisel1998g,
year = {1998},
title = {Methodological Support for Requirements Elicitation and Formal Specification},
booktitle = {Proc. 9th International Workshop on Software Specification and Design},
author = {Heisel, Maritta and Souqui{\`{e}}res, Jeanine},
publisher = {IEEE Computer Society Press},
pages = {153--155},
url = {http://www.ieee.org/}
}
|
|||||
Created by JabRef on 13/03/2018.