Software engineering article types: An analysis of the literature
Journal of Systems and Software
Agile architecture methodology: long term strategy interleaved with short term tactics
Companion to the 23rd ACM SIGPLAN conference on Object-oriented programming systems languages and applications
Applying empirical software engineering to software architecture: challenges and lessons learned
Empirical Software Engineering
Decision-making techniques for software architecture design: A comparative survey
ACM Computing Surveys (CSUR)
Interoperability among UML tools: an industrial case study
Proceedings of the 2012 ACM SIGSOFT symposium on Industry Day
| Hi-index | 0.00 |
The architecture of a software-intensive system is largely irrelevant to its end users. Far more important to these stakeholders is the system's behavior, exhibited by raw, working source code. As long as a system provides the right answers at the right time with all the right other "-ilities" (maintainability, dependability, changeability, and so on), end userscouldn't care less about what's behind the curtain making things work. To stakeholders other than end users, however, a system's architecture is intensely interesting. Moreover, software architecture has had a hand in better project management, greater use of iterative development, and leverage from the Web's infrastructure.