The Community for Technology Leaders
RSS Icon
Subscribe
Issue No.06 - Nov.-Dec. (2011 vol.28)
pp: 78-85
Daniel Menascé , George Mason University
Hassan Gomaa , George Mason University
Sam Malek , George Mason University
João Sousa , George Mason University
ABSTRACT
Making architectural decisions manually in the presence of quality-of-service trade-offs can be complicated. The SASSY (Self-architecting Software Systems) framework automatically generates candidate software architectures and selects the one that best serves stakeholder-defined, scenario-based quality-of-service (QoS) goals. This lets domain experts concentrate on functional and QoS requirements. SASSY reduces the effort of composing service-oriented systems by automatically generating the QoS–optimized architecture and rapidly reconfiguring it at runtime. Self-architecting occurs during initial system deployment and at runtime, thus making systems self-adaptive, self-healing, self-managing, and self-optimizing.
INDEX TERMS
software architectures, QoS, quality of service, service-oriented systems, software engineering
CITATION
Daniel Menascé, Hassan Gomaa, Sam Malek, João Sousa, "SASSY: A Framework for Self-Architecting Service-Oriented Systems", IEEE Software, vol.28, no. 6, pp. 78-85, Nov.-Dec. 2011, doi:10.1109/MS.2011.22
REFERENCES
1. J. Kramer and J. Magee, "Self-Managed Systems: An Architectural Challenge," Proc. Future of Software Eng. (FOSE 07), IEEE CS Press, 2007, pp. 259–268.
2. M.C. Huebscher and J.A. McCann, "A Survey of Autonomic Computing—Degrees, Models, and Applications," ACM Computing Surveys, vol. 40, no. 3, 2008, pp. 1–28.
3. M.P. Papazoglou et al., "Service-Oriented Computing: State of the Art and Research Challenges," Computer, vol. 40, no. 11, 2007, pp. 38–45.
4. P. Clements, R. Kazman, and M. Klein, Evaluating Software Architectures: Methods and Case Studies, Addison-Wesley, 2001.
5. S. Weerawarana et al., Web Services Platform Architecture: SOAP, WSDL, WS-Policy, WS-Addressing, WS-BPEL, WS-Reliable Messaging, and More, Prentice Hall, 2005.
6. J.O. Kephart and D.M. Chess, "The Vision of Autonomic Computing," Computer, vol. 36, no. 1, 2003, pp. 41–50.
7. N. Esfahani et al., "A Modeling Language for Activity-Oriented Composition of Service-Oriented Software Systems," Proc. 12th Int'l Conf. Model Driven Eng. Languages and Systems, Springer, 2009, pp. 591–605.
8. E.M. Dashofy, A. van der Hoek, and R.N. Taylor, "A Highly-Extensible, XML-Based Architecture Description Language," Proc. Working IEEE/IFIP Conf. Software Architectures, IEEE CS Press, 2001, pp. 103–112.
9. J. Magee and J. Kramer, Concurrency: State Models and Java Programs, 2nd ed., John Wiley & Sons, 2006.
10. D.A. Menascé et al., "QoS Architectural Patterns for Self-Architecting Software Systems," Proc. 7th Int'l Conf Autonomic Computing and Communications (ICAC 10), ACM Press, 2010, pp. 195–204.
11. D.A. Menascé et al., "A Framework for Utility-Based Service Oriented Design in Sassy," Proc. 1st Joint WOSP/SIPEW Int'l Conf. Performance Eng. (WOSP/SIPEW 10), ACM Press, 2010, pp. 27–36.
12. H. Gomaa et al., "Software Adaptation Patterns for Service-Oriented Architectures," Proc. ACM Symp. Applied Computing (SAC 10), ACM Press, 2010, pp. 462–469.
13. G. Edwards, S. Malek, and N. Medvidovic, "Scenario-Driven Dynamic Analysis of Distributed Architecture," Proc. 10th Int'l Conf. Fundamental Approaches to Software Eng., Springer, 2007, pp. 125–139.
17 ms
(Ver 2.0)

Marketing Automation Platform Marketing Automation Tool