Guiding Goal Modeling Using Scenarios
IEEE Transactions on Software Engineering
The unified software development process
The unified software development process
Software Development
Goal-Oriented Requirements Engineering: A Guided Tour
RE '01 Proceedings of the Fifth IEEE International Symposium on Requirements Engineering
The rational unified process made easy: a practitioner's guide to the RUP
The rational unified process made easy: a practitioner's guide to the RUP
The Rational Unified Process: An Introduction
The Rational Unified Process: An Introduction
Tropos: An Agent-Oriented Software Development Methodology
Autonomous Agents and Multi-Agent Systems
Developing Intelligent Agent Systems: A Practical Guide
Developing Intelligent Agent Systems: A Practical Guide
Use case and actor driven requirements engineering: an evaluation of modifications to prometheus
CEEMAS'05 Proceedings of the 4th international Central and Eastern European conference on Multi-Agent Systems and Applications
Prioritisation mechanisms to support incremental development of agent systems
International Journal of Agent-Oriented Software Engineering
Prometheus and INGENIAS Agent Methodologies: A Complementary Approach
Agent-Oriented Software Engineering IX
Use case and actor driven requirements engineering: an evaluation of modifications to prometheus
CEEMAS'05 Proceedings of the 4th international Central and Eastern European conference on Multi-Agent Systems and Applications
| Hi-index | 0.00 |
This paper presents a mechanism for dividing an agent oriented application into the three IEEE defined scoping levels of essential, conditional and optional. This mechanism is applied after the initial system specification, and is then used to direct incremental development with three separate releases. The scoping described can be applied at any stage of a project, in order to guide consistent scoping back if such is needed. The three levels of scoping that are used are consistent with the approach used in many companies. The approach to scoping requires that scenarios are prioritised manually on a five point scale. All other aspects are then prioritised automatically, based on this information. The approach used allows a developer to indicate what size partitions - based on number of scenarios - are required for each scoping level. The mechanisms are applied to the Prometheus development methodology and are integrated into the Prometheus Design Tool (PDT).