Communications of the ACM - Special issue on analysis and modeling in software development
Planning and replanning with truth maintenance
Planning and replanning with truth maintenance
Common KADS Library for Expertise Modelling
Common KADS Library for Expertise Modelling
IEEE Standard for Developing Software Life Cycle Processes
IEEE Standard for Developing Software Life Cycle Processes
A Classification of CASE Technology
Computer
Software Process Model Evolution in the SPADE Environment
IEEE Transactions on Software Engineering
Techniques for Process Model Evolution in EPOS
IEEE Transactions on Software Engineering
Integrating software process models and design rationales
KBSE '96 Proceedings of The 11th Knowledge-Based Software Engineering Conference
Project coordination in design processes
WET-ICE '96 Proceedings of the 5th International Workshops on Enabling Technologies: Infrastructure for Collaborative Enterprises (WET ICE'96)
Project coordination in design processes
WET-ICE '96 Proceedings of the 5th International Workshops on Enabling Technologies: Infrastructure for Collaborative Enterprises (WET ICE'96)
Component-based software development for integrated construction management software applications
Artificial Intelligence for Engineering Design, Analysis and Manufacturing
An integrated agent-oriented approach to real-time operational design coordination
Artificial Intelligence for Engineering Design, Analysis and Manufacturing
Requirements Engineering for Distributed Development Using Software Agents
ER '08 Proceedings of the ER 2008 Workshops (CMLSA, ECDM, FP-UML, M2AS, RIGiM, SeCoGIS, WISM) on Advances in Conceptual Modeling: Challenges and Opportunities
| Hi-index | 0.00 |
In conventional approaches to support planning of software development processes, the project plan has to be completely specified ahead of the process enactment. These approaches ignore two main characteristics of software development processes. Firstly, many planning decisions can only be made on base of knowledge resulting from the development process itself. Therefore the project planner must be able to extend and adapt the plan during enactment on basis of the current project data. Secondly, plan changes have to be taken into account. Considering these observations, the planner can be supported effectively, only if planning and enactment steps are alternated. In this contribution we identify the main requirements on a "dynamic" planning of software development processes and present methods and techniques which meet them.