Requirements engineering in the year 00: a research perspective

Lamsweerde, Axel van

doi:10.1109/icse.2000.870392

Cited by 186 publications

(250 citation statements)

References 69 publications

Supporting

Mentioning

225

Contrasting

Unclassified

Order By: Relevance

“…It also makes it more rational in that the designer can point to an explicit evaluation of these alternatives in terms of stakeholder criteria to justify his choice. An authoritative account of Goal-Oriented Requirements Engineering (GORE) can be found in [16].…”

Section: Goal-oriented Requirements Engineeringmentioning

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

Section: Goal-oriented Requirements Engineeringmentioning

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

show abstract

“…Agent-oriented approaches to development should not force any change in an applications requirements. Therefore, the techniques used in requirements engineering for agent-based systems will be the same as those elsewhere [3,12] (see Tropos [1] for an agent-oriented software engineering methodology based on requirements engineering). A common requirements engineering technique is to describe the requirements in terms of functional goals it is intended to achieve and priorities and restrictions which, jointly, we call preferences.…”

Section: Requirements To Designmentioning

confidence: 99%

Towards a Methodology for Coordination Mechanism Selection in Open Systems

Miles

Joy

Lück

2003

Engineering Societies in the Agents World III

View full text Add to dashboard Cite

“…Though there are alternatives to sharing a common language, if that may be made possible without impairment of other aspects of the development process, it cannot but be accepted as a desirable property of a method. Indeed, the need of an interface between the different project stakeholders is self-evident [29]. That does not necessarily imply that all of them need communicate using formal speci®cations, but these may provide precision when and where that is desirable.…”

Section: Introductionmentioning

confidence: 99%

Bases for the development of LAST: a formal method for business software requirements specification

Almendros-Jiménez

González-Jiménez

2002

Information and Software Technology

View full text Add to dashboard Cite

This paper proposes a possible approach to IS requirements speci®cation. It relies on the application of standard (i.e. conventional) discrete mathematics, more precisely, it uses a fairly limited number of concepts from the ®elds of linear algebra and set theory (hence its name, LAST). The use of LAST for data de®nition and query±answer are discussed in some detail, given the data-rich quality of Business IS and the fact that a solid data-model is therefore essential to their speci®cation. The proposed approach implies integration with other semiformal speci®cation methods, two of the possibilities being integration with UML±OCL and with the Entity Relationship Model, which are discussed in this paper. Finally, mapping of LAST speci®cations to the Relational Model is also addressed; this possibility having an interest both, for (partial) implementation and for model simulation. q

show abstract

Requirements engineering in the year 00: a research perspective

Cited by 186 publications

References 69 publications

Requirements-driven design of autonomic application software

Requirements-driven design of autonomic application software

Towards a Methodology for Coordination Mechanism Selection in Open Systems

Bases for the development of LAST: a formal method for business software requirements specification

Contact Info

Product

Resources

About