Requirements engineering: a roadmap
Proceedings of the Conference on The Future of Software Engineering
OOPSLA '02 OOPSLA 2002 Practitioners Reports
Towards a Semiotic Communications Quality Model
Proceedings of the IFIP TC8 / WG8.1 Working Conference on Organizational Semiotics: Evolving a Science of Information Systems
Agile Modeling: Effective Practices for eXtreme Programming and the Unified Process
Agile Modeling: Effective Practices for eXtreme Programming and the Unified Process
Towards a documentation maturity model
Proceedings of the 21st annual international conference on Documentation
Real work, necessary friction, optional chaos
Communications of the ACM - Wireless sensor networks
Third Intenational Workshop on Quality in Modeling
Models in Software Engineering
Towards an integrated quality assessment and improvement approach for UML models
SDL'09 Proceedings of the 14th international SDL conference on Design for motes and mobiles
Collaborative prioritization of architectural concerns
Journal of Systems and Software
| Hi-index | 0.00 |
Model-centric software processes, such as RUP, involve a rich set of artefacts (e.g., requirements specifications, design models, code) used for many activities (e.g., cost estimation, construction, communication, maintenance, archiving) by engineers in many roles (e.g., analysts, designers, developers, testers, managers). This diversity makes organisation and implementation of infrastructure for artefacts (such as document repositories, web portals, editors, indexes) a challenge: without analysis of involved tasks, and validation of the infrastructure's implementation, some tasks may not be properly supported. This paper presents a quality model for design documentation (i.e., for artefacts on the abstraction level between requirements specifications and code) intended to be used for requirements engineering of such. Twenty two qualities, most of which concern nonfunctional requirements on the design documentation are identified. The model is based on qualitative analysis of interviews with engineers and managers in a large software development organisation with 8 years experience of implementing RUP.