Abstract
Software Architecture plays major role in s successful software. It is one of the key artifacts of modern software development. This paper demonstrates the use of Architecture Requirements Engineering Error and Accuracy ¬ The Analysis Method (AREA¬TEAM) to evaluate an online banking system. This research paper presents the detailed case study of the system and the overall evaluation process that has employed AREA-TEAM. Eventually this paper discusses the results and elaborates the key benefits of the employed method.
Access this chapter
Tax calculation will be finalised at checkout
Purchases are for personal use only
Preview
Unable to display preview. Download preview PDF.
Similar content being viewed by others
References
Aman, M.A., Sulayman, M., et al.: Architecture Requirements Engineering Accuracy & Error – The Analysis Method. In: Accepted and Published in the first International Conference on Quality of service architectures in Net. Object Days, Erfurt Germany (2005)
Aman, M.A., Sulayman, M., et al.: Architecture Requirements Engineering Accuracy & Error – The Analysis Method, Islamabad Stock Exchange Case Study. In: Accepted and Published in IASTEAD, SE 2007, Austria (2007)
Bass, L., Clements, P., Kazman, R.: Software Architecture in Practice, 2nd edn. AddisonWesley, Boston (2003)
IEEE Computer Society, Software Engineering Standards Committee, Institute of Electrical and Electronics Engineers, IEEESA Standards Board, and IEEE Xplore. IEEE Recommended Practice for Architectural Description of Software Intensive Systems. Institute of Electrical and Electronic Engineers, New York (2000)
Clements, P., Bachmann, F., Bass, L., Garlan, D., Ivers, J., Little, R., Nord, R., Stafford, J.: Documenting Software Architectures: Views and Beyond. Addison Wesley, Boston (2003)
Pressman, R.: Software Engineering A Practitioner’s Approach, 5th edn., Mc Grawhill, International Edition, pp. 256–266 (2004)
Asada, T., et al.: The Quantified Design Space. In: Shaw, M., Garlan, D. (eds.) Software Architecture, pp. 116–127. Prentice Hall, Englewood Cliffs (1996)
Thayer, R.H., Dorfman, M.: Software Requirements Engineering, 2nd edn. IEEE Computer Society Press, Los Alamitos (1997)
Sommerville, I., Sawyer, P.: Requirements Engineering, Wiley, 1997 [10]. In: Bass, L., Clements, P., Kazman, R. (eds.) What is Software Architecture? in Software Architecture in Practice, p. 125. Pearson Education, London (2003)
Dennis, J.B.: Modularity. In: Bauer, F.L. (ed.) Software Engineering. LNCS, vol. 30, pp. 128–182. Springer, Heidelberg (1975)
Wirth, N.: Program Development by Stepwise Refinement. CACM 14(4), 221–227 (1971)
Dijkstra, D.O.E., Hoare, C.: Structured Programming. Academic Press, London (1972)
Bass, L., Klein, M., Moreno, G.: Applicability of General Scenarios to the Architecture Trade off Analysis Method, TECHNICAL REPORT, CMU/SEI2001TR014, ESETR2001-014
Author information
Authors and Affiliations
Editor information
Editors and Affiliations
Rights and permissions
Copyright information
© 2009 Springer-Verlag Berlin Heidelberg
About this paper
Cite this paper
Sulayman, M., Riaz, M., Naqvi, H., Aman, M.A. (2009). Using Area-Team to Evaluate the Software Architecture for an Online Banking System: A Case Study. In: Ślęzak, D., Kim, Th., Kiumi, A., Jiang, T., Verner, J., Abrahão, S. (eds) Advances in Software Engineering. ASEA 2009. Communications in Computer and Information Science, vol 59. Springer, Berlin, Heidelberg. https://doi.org/10.1007/978-3-642-10619-4_14
Download citation
DOI: https://doi.org/10.1007/978-3-642-10619-4_14
Publisher Name: Springer, Berlin, Heidelberg
Print ISBN: 978-3-642-10618-7
Online ISBN: 978-3-642-10619-4
eBook Packages: Computer ScienceComputer Science (R0)