Requirements analysis for customizable software: a goals-skills-preferences framework

Hui, Bowen; Liaskos, Sotirios; Mylopoulos, John

doi:10.1109/icre.2003.1232743

Cited by 62 publications

(58 citation statements)

References 5 publications

Supporting

Mentioning

Contrasting

Unclassified

Order By: Relevance

“…VBRE, in contrast, does provide specific advice based on a sound theory [48]. Emotional requirements could augment modelling of social influences in i* [63], and VBRE could be applied to the goals, skills preferences approach [64] and RE modelling of socio-technical systems. Considering emotions and motivation may help in modelling agents and their relationships, since trust and responsibility are already part of the i* family of models [11,63].…”

Section: Discussion Of Resultsmentioning

confidence: 99%

“…The framework advances previous elicitation techniques by providing explicit taxonomies of values and motivations to guide discovery of socio-political issues. It could extend the goals-skills preference trade-offs [64] by providing a sound taxonomy of personal characteristics and motivations. While our approach so far has been inspection based, a possible extension could be to use elements of the taxonomy in modelling soft-goal analysis in the i* framework [11] and augmenting the semantics of i* agent properties and relationships.…”

Section: Future Directions and Conclusionmentioning

confidence: 99%

See 1 more Smart Citation

Value-based requirements engineering: method and experience

Thew

Sutcliffe

2017

Requirements Eng

View full text Add to dashboard Cite

'Socio-political' issues, such as emotions, values and people's feelings, are often cited as problems in the RE process. A method is described for analysing such issues. The method consists of a taxonomy of stakeholders' values, motivations and emotions (VME), with process guidance for eliciting and analysing these issues for the RE process and design implications. Values are personal attitudes or long-term beliefs which may influence stakeholder functional and non-functional requirements. Motivations are psychological constructs related to personality traits which may be viewed as stakeholders' long-term goals in RE. Emotions are cues to stakeholders' reactions arising from value/motivation conflicts. The method is supported by a website which illustrates the taxonomy with explanations and scenarios describing problems arising from value conflicts, and from poor understanding of stakeholder values. Two method validation studies were undertaken: first, an evaluation of the website and method by novices and RE experts; and second, case study applications of RE value analysis in real-world industrial practice. The method was used by all practitioners, although in different ways, some used it to create an agenda of issues for analysis while others employed the VMEs to interpret stakeholders' views and manage stakeholder negotiations. The validation studies provide evidence for the acceptability of the method for industrial practitioners, illustrating how valuerelated problems are identified and analysed effectively by the method. The utility of analysing VMEs is compared to other 'socio-political issues'-oriented methods in RE and methods which focus on monetized values in product requirements.

show abstract

Section: Discussion Of Resultsmentioning

confidence: 99%

Section: Future Directions and Conclusionmentioning

confidence: 99%

Value-based requirements engineering: method and experience

Thew

Sutcliffe

2017

Requirements Eng

View full text Add to dashboard Cite

show abstract

“…In [4], goal models were used in the context of "personal software" (e.g., an email system) specifically to capture alternative ways of achieving user goals as a basis for creating highly customizable systems that can be fine-tuned for each particular user. The GoalsSkills-Preferences approach for ranking alternatives is also presented in [4]. The approach takes into consideration the user's preferences (the desired quality attributes) as well as the user's physical and mental skills to find the best option for achieving the user's goals.…”

Section: Goal Model-based Customization and Configurationmentioning

confidence: 99%

“…However, once the goal model is developed, the alternatives can be enumerated and analyzed automatically. For example, [4] shows that even naïve algorithms can work reasonably well on a goal model with 750 nodes and 10 6 alternatives.…”

Section: The Approachmentioning

confidence: 99%

Requirements-driven design of autonomic application software

Lapouchnian

Liaskos

et al. 2006

Proceedings of the 2006 Conference of the Center for Advanced Studies on Collaborative Research - CASCON '06

View full text Add to dashboard Cite

Autonomic computing systems reduce software maintenance costs and management complexity by taking on the responsibility for their configuration, optimization, healing, and protection. These tasks are accomplished by switching at runtime to a different system behaviour -the one that is more efficient, more secure, more stable, etc. -while still fulfilling the main purpose of the system. Thus, identifying the objectives of the system, analyzing alternative ways of how these objectives can be met, and designing a system that supports all or some of these alternative behaviours is a promising way to develop autonomic systems. This paper proposes the use of requirements goal models as a foundation for such software development process and demonstrates this on an example.

show abstract

“…The reason is that requirements are not uniform and differ according to different factors. Hui et al [10] describe how requirements can be customized to fit the actual skills of users. Liaskos et al [11,12] discuss customizing the requirements to users' preferences expressed over non-functional and optional requirements.…”

Section: Introductionmentioning

confidence: 99%

Requirements-driven deployment

2012

View full text Add to dashboard Cite

Deployment is a main development phase which configures a software to be ready for use in a certain environment. The ultimate goal of deployment is to enable users to achieve their requirements while using the deployed software. However, requirements are not uniform and differ between deployment environments. In one environment, certain requirements could be useless or redundant, thereby making some software functionalities superfluous. In another environment, instead, some requirements could be impossible to achieve and, thus, additional functionalities would be required. We advocate that ensuring fitness between requirements and the system environment is a basic and critical step to achieve a comprehensive deployment process. We propose a tool-supported modelling and analysis approach to tailor a requirements model to each environment in which the system is to be deployed. We study the case of contextual goal model, which is a requirements model that captures the relationship between the variability of requirements (goal variability space) and the varying states of a deployment environment (context variability space). Our analysis relies on sampling a deployment environment to discover its context variability space and use it to identify loci in the contextual goal model where a modification has to take place. Finally, we apply our approach in practice and report on the obtained results.

show abstract

Requirements analysis for customizable software: a goals-skills-preferences framework

Cited by 62 publications

References 5 publications

Value-based requirements engineering: method and experience

Value-based requirements engineering: method and experience

Requirements-driven design of autonomic application software

Requirements-driven deployment

Contact Info

Product

Resources

About