Modeling and analysis of performance aspects for software architecture: A uml-based approach

International Journal of Software Engineering and Knowledge Engineering

Volumn 16, Issue 3, 2006, Pages 347-378

  Dai, Lirong ^a   Cooper, Kendra ^b   Eric Wong, W ^b  

^a SEATTLE UNIVERSITY   (United States)

^b The University of Texas at Dallas   (United States)

Author keywords

Aspect oriented software development; Formal methods; Rapide architectural description language; Software architecture; Unified modeling language

Indexed keywords

ALGORITHMS; COMPUTER ARCHITECTURE; MATHEMATICAL MODELS; NUMERICAL ANALYSIS; REAL TIME SYSTEMS;

ASPECT-ORIENTED SOFTWARE DEVELOPMENT; FORMAL METHODS; RAPIDE ARCHITECTURAL DESCRIPTION LANGUAGE; SOFTWARE ARCHITECTURE; UNIFIED MODELING LANGUAGE;

SOFTWARE ENGINEERING;

EID: 33745784833     PISSN: 02181940     EISSN: None     Source Type: Journal    
DOI: 10.1142/S0218194006002835     Document Type: Article

References (41)

1. R. J. Allen, A formal approach to software architecture, PhD Thesis, Carnegie Mellon University, CMU Technical Report CMU-CS-97-144, 1997.
2. S. Balsamo, M. Marzolla, and A. D. Marco, Experimenting different software architectures performance techniques: A case study, in Proc. Fourth Int. Workshop on Software and Performance, San Francisco, CA, January 2004, pp. 115-119.
3. L. Bass, P. Clements, and R. Kazman, Software Architecture in Practice, Addison-Wesley, 2003.
4. P. Bertrand, R. Darimont, E. Delor, P. Massonet, and A. van Lamsweerde, GRAIL/KAOS: An environment for goal drivent requirements engineering, in Proc. 20th IEEE-ACM Int. Conf. on Software Engineering, Kyoto, Japan, April 1998.
5. P. Bresciani and A. Perini, Tropos: An agent-oriented software development methodology, Autonomous Agents and Multi-Agent Systems 8(3) (2004) 203-236.
6. K. W. Brodlie, L. A. Carpenter, R. A. Earnshaw, J. R. Gallop, R. J. Hubbard, A. M. Mumford, C. D. Osland, and P. Quarendon (eds.), Scientific Visualization, Techniques and Applications, Springer-Verlag, 1992.
7. B. Cheng, S. Honrad, L. Campbell, and R. Wassermann, Using security patterns to model and analyze security requirements, in Proc. Second IEEE Workshop on Requirements for High Assurance Systems, Monterey Bay, CA, September 2003, pp. 13-22.
8. L. Chung, B. A. Nixon, E. Yu, and J. Mylopoulos, Non-Functional Requirements in Software Engineering, Kluwer Academic Publishing, 2000.
9. T. Clark and A. Evans, Foundations of the unified modeling language, in Proc. Second Northern Formal Methods Workshop, Ilkley, UK, September 1997.
10. S. Clark and R. Walker, Generic aspect-oriented design with theme/UML, in Aspect-Oriented Software Development, eds. R. Filman, T. Elrad, S. Clarke, and M. Aksit, Addison-Wesley Professional, 2004, pp. 425-459.
11. K. Cooper, L. Dai, and Y. Deng, Performance modeling and analysis of software architecture: An aspect-oriented UML based approach, Journal of Science of Computer Programming 57(1) (2005) 89-108.
12. A. Dardenne, A. van Lamsweerde, and S. Fickas, Goal-directed requirements acquisition, Science of Computer Programming 20(1-2) (1993) 3-50.
13. R. Filman, T. Elrad, S. Clarke, and M. Aksit, Aspect-Oriented Software Development, Addison-Wesley Professional, 2004.
14. P. Giorgini, J. Mylopoulos, and R. Sebastiani, Goal-oriented requirements analysis and reasoning in the Tropos methodology, Engineering Applications of Artificial Intelligence 18(2) (2005) 159-171.
15. S. Göbel, C. Pohl, S. Röttger, and S. Zschaler, The COMQUAD component model: Enabling dynamic selection of implementations by weaving non-functional aspects, in Proc. Third Int. Conf. on Aspect-Oriented Software Development, Lancaster, UK, March 2004, pp. 74-82.
16. A. H. M. ter Hofstede and H. A. Proper, How to formalize it? Formalization principles for information system development methods, Information and Software Technology 40(10) (1998) 519-540.
17. G. Holzmann, The SPIN Model Checker: Primer and Reference Manual, Addison-Wesley Professional, 2003.
18. R. Jain, The Art of Computer Systems Performance Analysis: Techniques for Experimental Design, Measurement, Simulation, and Modeling, Wiley-Interscience, April 1991.
19. D. Jani, D. Vanderveken, and D. Perry, Deriving Architecture Specifications from KAOS Specifications: A Research Case Study, Lecture Notes in Computer Science, Vol. 3527, 2005, pp. 185-202.
20. J. Jürjens, Sound methods and effective tools for model-based security engineering with UML, in Proc. 27th Int. Conf. on Software Engineering, St. Louis, MI, May 2005, pp. 322-331.
21. R. Kazman, M. Klein, M. Barbacci, T. Longstaff, H. Lipson, and J. Carriere, The architecture tradeoff analysis method, in Proc. Fourth IEEE Int. Conf. on Engineering of Complex Computer Systems, Monterey, CA, August 1998, pp. 68-78.
22. S. Keller, L. Kahn, and R. Panara, Specifying software quality requirements with metrics, in Tutorial: System and Software Requirements Engineering, Los Alamitos, CA, 1990, pp. 145-163.
23. R. Laddad, AspectJ in Action: Practical Aspect-Oriented Programming, Manning Publications, July 2003.
24. K. Lano, J. Bicarregui, and A. Evans, Structured axiomatic semantics for UML models, in Proc. Rigorous Object-Oriented Methods, York, UK, January 2000.
25. J. P. López-Grao, J. Merseguer, and J. Campos, From UML activity diagrams to stochastic Petri nets: Application to software performance engineering, in Proc. Fourth Int. Workshop on Software and Performance., Redwood City, CA, January 2004, pp. 25-36.
26. D. C. Luckham, J. J. Kenney, L. M. Augustin, J. Vera, D. Bryan, and W. Mann, Specification and analysis of system architecture using Rapide, IEEE Transactions on Software Engineering 21(4) (1995) 336-354.
27. N. Medvidovic, D. S. Rosenblum, D. F. Redmiles, and J. E. Robbins, Modeling software architectures in the unified modeling language, ACM Transactions on Software Engineering and Methodology 11(1) (2002) 2-57.
28. B. Meyer, Introduction to the Theory of Programming Languages, Prentice Hall, July 1990.
29. P. V. Mockapetris, Domain Names - Implementation and Specification, IETF STD0013, 1987.
30. R. T. Monroe, Capturing software architecture design expertise with Armani, Technical Report CMU-CS-98-163, School of Computer Science, Carnegie Mellon University, Pittsburgh, Pennsylvania, 1998.
31. I. Ober, An ASM semantics for UML derived from the meta-model and incorporating actions, in Proc. Tenth Int. Workshop on Abstract State Machines, Taormina, Italy, March 2003, pp. 356-372.
32. Object Management Group, UML Profile for Schedulability, Performance, and Time Specification, OMG Documents ptc/2003-03-02, 2003.
33. J. Rumbaugh, I. Jacobson, and G. Booch, The Unified Modeling Language Reference Manual, Addison-Wesley, 2004.
34. M. Shaw and D. Garlan, Software Architecture: Perspectives in an Emerging Discipline, Prentice Hall, 1996.
35. H. A. Simon, The Sciences of the Artificial, MIT Press, 1996.
36. Software Design Group, the Alloy Analyzer, archived at http://alloy.mit.edu, 2002-2005.
37. J. M. Spivey, Understanding Z: A Specification Language and its Formal Semantics, Cambridge University Press, 1988.
38. A. Van Lamsweerde, Goal-oriented requirements engineering: A guided tour, in Proc. Int. Joint Conf. on Requirements Engineering, Toronto, IEEE, August 2001, pp. 249-263.
39. J. Warmer and A. Kleppe, The Object Constraint Language: Precise Modeling with UML, Addison-Wesley, 1998.
40. B. Win, W. Joosen, and F. Piessens, Developing secure applications through aspect-oriented programming, in Aspect-Oriented Software Development, eds. R. Filman, T. Elrad, S. Clarke, and M. Aksit, Addison-Wesley Professional, 2004, pp. 633-651.
41. E. Yu, Agent orientation as a modelling paradigm, Wirtschaftsinformatik 43(2) (2001) 123-132.