Representing and using non-functional requirements: a process-oriented approach
Representing and using non-functional requirements: a process-oriented approach
Requirements analysis and system design: developing information systems with UML
Requirements analysis and system design: developing information systems with UML
Software engineering (6th ed.)
Software engineering (6th ed.)
Representing and Using Nonfunctional Requirements: A Process-Oriented Approach
IEEE Transactions on Software Engineering - Special issue on knowledge representation and reasoning in software development
AI Models for Business Process Reengineering
IEEE Expert: Intelligent Systems and Their Applications
Viewpoints for Requirements Elicitation: A Practical Approach
ICRE '98 Proceedings of the 3rd International Conference on Requirements Engineering: Putting Requirements Engineering to Practice
Goal-Oriented Requirements Engineering: A Guided Tour
RE '01 Proceedings of the Fifth IEEE International Symposium on Requirements Engineering
Co-Evolution of Complementary Formal and Informal Requirements
IWPSE '04 Proceedings of the Principles of Software Evolution, 7th International Workshop
| Hi-index | 0.00 |
Software development processes requires a thorough understanding of stakeholder objectives and requirements. Product-centrism is an insufficient stance from which to achieve greater efficiencies and reduce re-engineering. Stakeholder requirement elicitation is thus worthy of formalization. A suite of tools, notably the i* model, provides a framework for early-phase requirements capture. These tools currently are at best only semi-automated and essentially consist of a notational glossary and sets of mark-up symbols. Increasing formalization may lead to greater automation of the process in the future, but currently there is a degree of flexibility that presents pitfalls for the unwary practitioner. A notion of contextual consistency would enhance the applicability such toolkits. Requirements generated from stakeholder objectives may suffer scoping errors, complicated by the complexity of practical examples. Hierarchical situations of contextual confusion are explored. A formalisation is offered of the constraints that circumscribe the set of valid decompositions.