RE 2012 – Author Index |
Contents -
Abstracts -
Authors
Online Calendar - iCal File |
Alexandrova, Assia |
RE '12-DOCTORAL: "Business Requirements Analysis ..."
Business Requirements Analysis and Development for Legacy System Replacement Projects in Government Organizations
Assia Alexandrova (Open University, UK) e-Government innovation is commonly hindered by legacy systems in public sector agencies. Legacy systems not only present technical constraints, but they also embed outdated and inefficient business processes. A critical manifestation of this issue occurs during the requirements phase of e-government projects, where requirements tend to mimic the features of old systems that must be modernized or replaced. The problem is not easy to identify and qualify, unless a critical stance to requirements analysis is taken, and unless requirements are examined in the context of processes that are creative, exploratory and collaborative. We propose a solution to legacy reproduction issues in the development of a game-based tool that through competition enables the analysis and transformation of business requirements by applying risk and opportunity criteria. @InProceedings{RE12p337, author = {Assia Alexandrova}, title = {Business Requirements Analysis and Development for Legacy System Replacement Projects in Government Organizations}, booktitle = {Proc.\ RE}, publisher = {IEEE}, pages = {337--340}, doi = {}, year = {2012}, } |
|
Hoffmann, Axel |
RE '12-DOCTORAL: "A Pattern-Based Approach for ..."
A Pattern-Based Approach for Analysing Requirements in Socio-technical Systems Engineering
Axel Hoffmann (University of Kassel, Germany) Requirements analysis for socio-technical systems faces the challenge of multidisciplinary requirements that need to be collected from, understood by and agreed upon by various stakeholders. In some cases, requirements analysts or involved stakeholders do not fully understand the requirements that other disciplines impose, and thus fail to deliver a requirements specification that can be used in interdisciplinary development teams. In requirements engineering, requirement patterns are used to recognize important and recurring issues, thus reducing the effort of compiling a list of software requirements. The objective of the proposed dissertation project is to develop a similar pattern based approach that helps in analysing requirements from different disciplines and making them comprehensible for all stakeholders who need to agree to a requirement specification as the deliverable of requirements engineering. Due to the importance of legal aspects for, and users’ trust in, socio-technical systems, requirement patterns will be developed for these two aspects. For the legal requirement patterns, legal requirements that are stable concerning changes due to their origin in fundamental, higher-ranked laws will be collected, and requirement patterns will be derived from them. For the requirement patterns for trust support, antecedents that build trust will be collected, and requirement patterns that demand functionality to support these antecedents will be developed. The obtained patterns are then used to compile a requirement list that serves as input for requirements negotiation with the various stakeholders. @InProceedings{RE12p341, author = {Axel Hoffmann}, title = {A Pattern-Based Approach for Analysing Requirements in Socio-technical Systems Engineering}, booktitle = {Proc.\ RE}, publisher = {IEEE}, pages = {341--344}, doi = {}, year = {2012}, } |
|
Knauss, Alessia |
RE '12-DOCTORAL: "On the Usage of Context for ..."
On the Usage of Context for Requirements Elicitation: End-User Involvement in IT Ecosystems
Alessia Knauss (University of Victoria, Canada) Today’s systems are faced with the need of constant evolution to remain competitive, especially when looking at IT Ecosystems and their growing number of subsystems. As a prerequisite for these to stay competitive, system providers need a clear understanding of their stakeholder’s needs. As systems tend to be increasingly complex nowadays, support an increasingly number of stakeholders, have a shorter release cycles to evolve and need to adapt to the environment and the users, some of the standard requirements elicitation techniques tend not to be suitable any more. Especially when adaptivity is necessary, system providers need to understand the context, in which the systems are used, but also the context of users for the adaptation. In this paper I concentrate on the largest stakeholder group, namely the end-users for requirements elicitation. Evaluation criteria include i) support of context, ii) scalability to large numbers of end-users, and iii) scalability to large numbers of end-user’s needs and problems that lead to new requirements. My literature review suggests that this important field is currently underrepresented in Requirements Engineering research. This research proposes to develop a framework that explains the different context types and their role for requirements elicitation. The framework is then used to investigate existing requirements elicitation techniques and their potential for considering context. It is also used to show how emerging techniques can further support requirements elicitation with context. @InProceedings{RE12p345, author = {Alessia Knauss}, title = {On the Usage of Context for Requirements Elicitation: End-User Involvement in IT Ecosystems}, booktitle = {Proc.\ RE}, publisher = {IEEE}, pages = {345--348}, doi = {}, year = {2012}, } |
|
Riegel, Norman |
RE '12-DOCTORAL: "Model-Based Prioritization ..."
Model-Based Prioritization in Business-Process-Driven Software Development
Norman Riegel (Fraunhofer IESE, Germany) Requirements engineers in business-process-driven software development are faced with the challenge of letting stakeholders determine which requirements are actually relevant for early business success and should be considered first or even at all during the elicitation and analysis activities. In the area of requirements engineering (RE) and release planning, prioritization is an established strategy for achieving this goal. Available prioritization approaches, however, do not consider all idiosyncrasies of business-process-driven software development. This lack of appropriate prioritization leads to effort often being spent on (RE) activities of minor importance. To support the requirements engineer in overcoming this problem, the idea of applying different models during prioritization is introduced, which shall bring it to a more reliable basis. Through this notion it is expected to reduce unnecessary (RE) activities by focusing on the most important requirements. @InProceedings{RE12p349, author = {Norman Riegel}, title = {Model-Based Prioritization in Business-Process-Driven Software Development}, booktitle = {Proc.\ RE}, publisher = {IEEE}, pages = {349--352}, doi = {}, year = {2012}, } |
|
Todoran, Irina |
RE '12-DOCTORAL: "StakeCloud: Stakeholder Requirements ..."
StakeCloud: Stakeholder Requirements Communication and Resource Identification in the Cloud
Irina Todoran (University of Zurich, Switzerland) With the recent emergence of cloud computing, the number of cloud service providers is constantly increasing and consumers’ needs are becoming more sophisticated. This situation leads to an evident need for methods which enable providers to correctly elicit requirements coming from very heterogeneous consumers. Moreover, consumers demand ways to find the cloud services which best meet their needs. We propose to address the issues identified by creating the StakeCloud community platform, capable of working as a cloud resources marketplace. It will allow users to input their resource needs and provide them with matching cloud services. Additionally, in case these are not met, they can be communicated as new requirements to cloud providers. Such a contribution will improve the requirements communication and resource identification in cloud systems, bridging the gap between consumers and providers. @InProceedings{RE12p353, author = {Irina Todoran}, title = {StakeCloud: Stakeholder Requirements Communication and Resource Identification in the Cloud}, booktitle = {Proc.\ RE}, publisher = {IEEE}, pages = {353--356}, doi = {}, year = {2012}, } |
5 authors
proc time: 0.27