Eliminating receive livelock in an interrupt-driven kernel
ACM Transactions on Computer Systems (TOCS)
Software architecture in practice
Software architecture in practice
Software performance antipatterns
Proceedings of the 2nd international workshop on Software and performance
Characteristics of scalability and their impact on performance
Proceedings of the 2nd international workshop on Software and performance
The Operational Analysis of Queueing Network Models
ACM Computing Surveys (CSUR)
Architecture-Centric Software Project Management: A Practical Guide
Architecture-Centric Software Project Management: A Practical Guide
Theory, Volume 1, Queueing Systems
Theory, Volume 1, Queueing Systems
Risk Themes Discovered through Architecture Evaluations
WICSA '07 Proceedings of the Sixth Working IEEE/IFIP Conference on Software Architecture
Model-Based scalability estimation in inception-phase software architecture
MoDELS'05 Proceedings of the 8th international conference on Model Driven Engineering Languages and Systems
Leadership and management in software architecture
ICSE '09 COMPANION Proceedings of the 2009 31st International Conference on Software Engineering: Companion Volume
| Hi-index | 0.00 |
System performance and scalability issues often have their roots in architectural and design choices that are made early in the software life cycle. Because he must communicate with developers, designers, product managers, business stake holders, application domain experts, testers, and requirements engineers, the software architect is uniquely placed to play a leadership role in linking performance requirements to business and engineering needs. Ideally, the architectural, technology, and design choices that are made should take performance requirements and artifacts into account. This means that the architect should be equipped with at least a rudimentary understanding of performance engineering concepts. Ideally, an architect should be directly involved in performance concerns. Failing that, he should overtly give a mandate to and remain in close contact with a performance engineer to do this instead, because close architectural involvement with performance concerns is key to the success of the project.