Software processes are software too
ICSE '87 Proceedings of the 9th international conference on Software Engineering
State of the art in testing components
QSIC '03 Proceedings of the Third International Conference on Quality Software
On the Effectiveness of the Test-First Approach to Programming
IEEE Transactions on Software Engineering
View Graphs for Analysis and Testing of Programs at Different Abstraction Levels
HASE '05 Proceedings of the Ninth IEEE International Symposium on High-Assurance Systems Engineering
Building up and Exploiting Architectural Knowledge
WICSA '05 Proceedings of the 5th Working IEEE/IFIP Conference on Software Architecture
Software is a directed multigraph
ECSA'11 Proceedings of the 5th European conference on Software architecture
On architecture warehouses and software intelligence
FGIT'12 Proceedings of the 4th international conference on Future Generation Information Technology
On quick comprehension and assessment of software
Proceedings of the 14th International Conference on Computer Systems and Technologies
One Graph to Rule Them All Software Measurement and Management
Fundamenta Informaticae - Concurrency, Specification and Programming
| Hi-index | 0.00 |
For a software-intensive system, software quality measures how well the software is designed and how well the software conforms to that design, whereas architecture of a software system is typically defined as the fundamental organization of the system embodied in its components, their relationships to each other and the environment, and the principles governing the system's design and evolution. Obviously, as long as there were no software systems, governing their architecture was no problem at all; when there were only small systems, governing their architecture became a mild problem; and now we have gigantic software systems, and governing their architecture has become an equally gigantic problem (to paraphrase Edsger Dijkstra). In this paper we propose a unified approach to the problem of governing (or managing) the knowledge about architecture of software systems and demonstrate by example its impact on a certain software project. First we postulate that only the holistic approach that supports continuous integration and verification for all system architectural artifacts is one worth taking. Next we demonstrate by example how a concrete large software project being developed in an agile approach is being perceived using the model in question