Software Architecture in Banking
CSSE 377 – Software Architecture & Design II
Software Architecture in Banking
A Comparative Paper on the Effectiveness of Different Software Architectures Within an Financial Banking System
JD Hill Andrew Robby Kruth Joe Salisbury Sam Varga 11/9/2010
Introduction
Software architecture design is an important aspect of our daily lives whether we know it or not. There are so many different systems that we interact with on a daily basis that we do not recognize are closely tied to software architecture decisions. These systems handle things from stoplights, electricity, televisions, communications, and many other things. Another example of a software system involved with our life is a system that powers banks and financial networks across the globe. When implementing such a system, there are several things that need to be considered. The design of any software system needs to be thought out and have certain aspects considered from the beginning. By choosing specific quality attributes to be designed into the architecture, there is a greater chance that the system will be successful. Specifically for a bank system, there will be several important attributes to focus on. First, the performance of the system needs to be high quality. Bank workers, people at ATMs, and bank administrators will all be interacting with other systems and so the new system will need to perform fast enough to allow everyone to complete the necessary tasks. Also, the reliability and security of the system are two of the most important thing to focus on. The system needs to be reliable such that it does not crash and has a very high uptime. The security is important because banks hold a large amount of private information. If this private information became available to people who should not have access, the company which made the system could face a lot of legal issues due to the breach of privacy. A bank system needs to make sure that people who are authorized to get in the system
Software Architecture in Banking
A Comparative Paper on the Effectiveness of Different Software Architectures Within an Financial Banking System
JD Hill Andrew Robby Kruth Joe Salisbury Sam Varga 11/9/2010
Introduction
Software architecture design is an important aspect of our daily lives whether we know it or not. There are so many different systems that we interact with on a daily basis that we do not recognize are closely tied to software architecture decisions. These systems handle things from stoplights, electricity, televisions, communications, and many other things. Another example of a software system involved with our life is a system that powers banks and financial networks across the globe. When implementing such a system, there are several things that need to be considered. The design of any software system needs to be thought out and have certain aspects considered from the beginning. By choosing specific quality attributes to be designed into the architecture, there is a greater chance that the system will be successful. Specifically for a bank system, there will be several important attributes to focus on. First, the performance of the system needs to be high quality. Bank workers, people at ATMs, and bank administrators will all be interacting with other systems and so the new system will need to perform fast enough to allow everyone to complete the necessary tasks. Also, the reliability and security of the system are two of the most important thing to focus on. The system needs to be reliable such that it does not crash and has a very high uptime. The security is important because banks hold a large amount of private information. If this private information became available to people who should not have access, the company which made the system could face a lot of legal issues due to the breach of privacy. A bank system needs to make sure that people who are authorized to get in the system
Bibliography: "Base One - Database-centric Grid and Cluster Computing." Base One - .NET Database Programming Tools. Web. 05 Nov. 2010. . Daniel D. Corkill. Collaborating Software: Blackboard and Multi-Agent Systems & the Future. In Proceedings of the International Lisp Conference, New York, New York, October 2003. Dué, Richard T. "Client/Server Feasibility." Information Systems Management 11.3 (1994): 79-82. Academic Search Premiere. Web. 05 Nov. 2010. Gallaugher, John, and Suresh Ramanathan. "Choosing a Client/Server Architecture." Information Systems Management 13.2 (1996): 7-13. Academic Search Premiere. Web. 05 Nov. 2010. "Introduction to 3-Tier Architecture." DotNetSlackers: ASP.NET News and Articles For Lazy Developers. Web. 05 Nov. 2010. . Michalarias, I., A. Omelchenko, and H. Lenz. "FCLOS: A Client–server Architecture for Mobile OLAP." Data & Knowledge Engineering 68.2 (2009): 192-220. Academic Search Premiere. Web. 05 Nov. 2010. "Owen Taylor on 'Space Based Architecture ' - TheServerSide.com." TheServerSide.com: Your Java Community Discussing Server Side Development. Web. 05 Nov. 2010. . "Space-Based Architectural Thinking." CQRS, DDD, and NServiceBus Video. Web. 05 Nov. 2010. . "Space-Based Programming - O 'Reilly Media." ONJava.com: The Independent Source for Enterprise Java -- Java Development, Open and Emerging Enterp. Web. 05 Nov. 2010. . Tyree, J., and A. Akerman. "Architecture Decisions: Demystifying Architecture." IEEE Software 22.2 (2005): 19-27. Academic Search Premiere. Web. 05 Nov. 2010. Wikipedia, the Free Encyclopedia. Web. 05 Nov. 2010. . (Used multiple articles as base line for some information gathering and to seek out other sources)