View-based mechanisms for structured and distributed enactment
ISAW '96 Joint proceedings of the second international software architecture workshop (ISAW-2) and international workshop on multiple perspectives in software development (Viewpoints '96) on SIGSOFT '96 workshops
About views for modeling software processes in a role-specific manner
ISAW '96 Joint proceedings of the second international software architecture workshop (ISAW-2) and international workshop on multiple perspectives in software development (Viewpoints '96) on SIGSOFT '96 workshops
Formalizing Software Engineering Standards
ISESS '97 Proceedings of the 3rd International Software Engineering Standards Symposium (ISESS '97)
Expanding the horizons of software development processes: a 3-D integrated methodology
SPW'05 Proceedings of the 2005 international conference on Unifying the Software Process Spectrum
| Hi-index | 0.00 |
The goal of software process model reuse should be to provide a comprehensive process model that guides and coordinates all roles within a project. This means that roles do not use their own process model, but all roles use a single, integrated one that represents all needed information. Views are derived to present information necessary for performing a role's tasks. Because every project is unique, reuse of software process models requires tailoring. Reusing generic, large software process models seems to be impractical, because of many interdependencies between generic parts of the model. Process engineering will only be successful when techniques are developed to formulate units of software process modules (staying relatively stable from project to project), to tailor them according to new contexts, and to integrate them into a comprehensive software process model. The hypothesis of this paper is that views are the process modules to be reused. Views are less complex and easier to maintain than a comprehensive process model.