The temporal logic of reactive and concurrent systems
The temporal logic of reactive and concurrent systems
Formal refinement patterns for goal-driven requirements elaboration
SIGSOFT '96 Proceedings of the 4th ACM SIGSOFT symposium on Foundations of software engineering
A formal approach for designing CORBA based applications
Proceedings of the 22nd international conference on Software engineering
Agent-based tactics for goal-oriented requirements elaboration
Proceedings of the 24th International Conference on Software Engineering
Deriving operational software specifications from system goals
Proceedings of the 10th ACM SIGSOFT symposium on Foundations of software engineering
A design for evidence - based soft research
REBSE '05 Proceedings of the 2005 workshop on Realising evidence-based software engineering
Software architects in practice: handling requirements
CASCON '06 Proceedings of the 2006 conference of the Center for Advanced Studies on Collaborative research
Integrating visual goal models into the Rational Unified Process
Journal of Visual Languages and Computing
Using FDAF to bridge the gap between enterprise and software architectures for security
Science of Computer Programming
Deriving event-based transition systems from goal-oriented requirements models
Automated Software Engineering
On the symbiosis of aspect-oriented requirements and architectural descriptions
Proceedings of the 10th international conference on Early aspects: current challenges and future directions
COMPASS: composition-centric mapping of aspectual requirements to architecture
Transactions on aspect-oriented software development IV
ICSE'05 Proceedings of the 2005 international conference on Software Engineering Education in the Modern Age
Hi-index | 0.00 |
The most dificult step in the design process of a system is clearly the transition from the requirements to the architecture. Requirements obtained from the various stakeholders must be transformed into an architecture that can be understood by developers. The power plant system we use in this study was derived from [1,2]. We first created a goal-oriented requirements specification from the information available using the KAOS requirement specification language [3,4,5]. Since the description was not complete we often had to make do with inadequate data.