Hubert Keller of the Institute für angewandte Informatik am Forschungszentrum Karlsruhe erhebt die folgenden zehn goldenen Regeln für Softwarequalität (Quelle: Computer Zeitung Nr. 22, 30 Mai 2005, S. 17):
- Saubere Analyse der Kundenanforderungen, Festlegung der Begriffswelt und Sprache des Kunden
- Erfassung der Sytem- und Architektur-relevanten Requirements
- Projektion der Systemarchitektur und –anforderungen in die Zukunft der Systemweiterentwicklung zur Absicherung der Tragfähigkeit der Architektur
- Iterative und inkrementelle Entwicklung eines Systemmodells mit klarer Konzentration auf die logische Sicht und Konsistenzprüfung
- Detaillierung des Modells (technische Realization nearby)
- implementation in Porgrammcode with tools of the Model Driven Architecture
- down process and work flow with roles and responsibilities
- Technical training of staff to be in safe procedures technically be fit
- early consideration of usability and security aspects Permanent
- review and inspection in the group as well as proof of compliance requirements, testing and configuration management
Gilding I would not follow these rules, as they show clear signs of current Forschungs-/Wissenstand terms of practices (eg the reference to Model Driven Architecture) . To the title get "golden rule", these rules should be formulated more generally. One of the rules
make clear that software quality is strongly influenced by structural measures and quality refers not only to the accuracy, but also other criteria as regards the quality of the architecture, security and usability.
