The New Internet Banking System for the High Street Bank - Report Example

HIGH STREENT BANK ONLINE BANKING SYSTEM SYSTEM REPORT BY-------- TO-------- TABLE OF CONTENTS Section 3 Introduction 3 Section 2 3 2- System Requirements 3 2.1 Functional Requirements 4 2.2 Non Functional Requirements 5 Section 3 6 Categories of prototype to be developed 6 3.1 Functional Prototype for the “New Customer and Account” 6 3.2 The classes of users to be involved in development 7 Section 4 8 Class Diagram 8 Use Case Diagram 10 Section 6 12 Discuss System security 12 Section 7 13 Conclusion 13 References 13 Section 1 1- Introduction This report presents a detailed analysis of development of the new Internet banking system for the High street bank. The bank has decided to upgrade their banking style with the help of new technology. This up-gradation will enhance the bank’s capability to manage and handle more customers who want new or innovative style of the banking. Initially the High street bank has settled up few goals for the internet banking and it is decided that bank will provide following services to their online customers: Transaction details Customer details Account details Requests for Internet banking This implementation will require updating of the pervious bank network and online website. Now this network will incorporate more efficient data management and security parameters. In the below sections it will be outlined that how the system will respond against any external input. These sections are aimed to present the basic system requirement and logical/physical design. Section 2 2- System Requirements This section will present the detailed analysis of the system requirement regarding the better system development and implementation. These requirements can be user driven or system driven. These requirements should be driven in an effective way to develop a better system design that will lead to more successful banking system implementation. 2.1 Functional Requirements Here I will elaborate how the system needs to work and respond to any user request. The following given functional requirements will present the main system features regarding its functionality. Simple interface: The system should have a simple interface that can be easily accessed. The interface should not contain any complex features and data that can make the user feel distracting. This will also need to consider about the color schema of the website pages and links. We have to choose colors those are simple and provide a feel of lightness. The font is also a main consideration of this interface. We have to choose the font that is easy in reading and working. Adoptability: The system should be adoptable both inside and out side the bank. Means that the bank employees should feel more ease; while working with this new system and customers should not face problems regarding the usage of the bank website. If the system produces a feeling of overhead then it will be difficult for the user and bank employees to use the system in a more effective way. Usability: The system should be usable in the scenario of its working and ease of online transaction. This new system needs to provide its user a more relaxing and satisfaction feeling for the online banking. Efficiency: The system should be efficient in its working and banking tasks. Security: Nowadays we are facing biggest hazard form the online money frauds. A number of people would be uncertain from the online transaction. In our system we need to make sure that there is no security hole in the system working and online cash transaction. By this way public will feel easiness in carrying out online transaction and our business will gain more customers loyalty. For this purpose we will provide that facility that all data should be encrypted. 2.2 Non Functional Requirements This section will provide a deep insight into the system non-functional requirements. Here it emphasizes that we can address each aspect of system non-functional requirements area. Hardware requirements: Pentium 4 [workstation for each bank employee] Network Equipment Servers Switches LAN structure Software requirements: Windows XP Oracle database Visual Basic and Access CASE tools Section 3 Categories of prototype to be developed 3.1 Functional Prototype for the “New Customer and Account” In this prototype the system will provide the facility to the customer regarding the opening of a new account. This prototype is able to provide complete functionary regarding the user account creation. Figure 1- Basic User Interface 3.2 The classes of users to be involved in development This section will present a list of the users that will be involved in the development of this online baking system. Technical Users Here we will involve the different team of the application developers: Analysts This team will be involved to gain main requirements and system needs System Designers System designers will develop the system logical and physical design Coders This class of users will code the system in the Oracle and visual basic Testers Team of tester will check the system for the potential errors and faults Quality Assurance The quality assurance team aimed to check the system for the better system working and fault free working. Technical Staff They will be involved in the up-gradation of the physical network of the company Non-Technical Users This category of the users will be involved for the gaining of the basic requirements and system features. For instance we will involve the following people for this system development: Customer Operatives IT operatives Bank manager Employees for the new system handling Network management staff Any class of common persons who is interested in the online banking (will give there comments regarding system design and working) Section 4 Class Diagram In this section I will present the class diagram of the High street bank online banking system: Class Diagram Section 5 Use Case Diagram In this section I will present the use case diagram of the High street bank online banking system: Use case diagram Error: Reference source not found Sn Account Renewal Information Error: Reference source not found Figure 2- Use case Diagram Section 6 Discuss System security Security risk: The information security risk can be acknowledged as the intensity of affect on organization processes (encompassing operational tasks, illustrations, or status), organization possessions, or individuals resultant from the course of action of a business information arrangement that proffer the possible influence of a hazard and the probability of that intimidation occurring. Investment risk: business hazards linked by the probable incapability to attain wide-ranging program aims inside divergent price, timetable, and technological limitations. As I have earlier talked about the security of the online banking system in the functional requirements. The security of the online banking system is one the critical aspect of the new age banking systems. Here we have to implement the state of the art technology and techniques for the better system security and privacy of the user information and online case dealing. The main problems are the online hacking and money frauds. The hackers can access the network to give a serious danger to our system working and cash reserves. For this purpose the bank’s officials has decided to implement the encryption of the bank information before its transmission on the World Wide Web. The encryption of the bank and user account information will provide us a better way of security and privacy. In this technique we will settle a predefined or system generated encryption code that will be used to encrypt the data. Nowadays this technique is really feasible and effective for the online baking and other areas where we want to implement the system security. To implement the complete system security we need to implement a network firewall that will facilitate against potential hackers and virus attacks. Section 7 Conclusion In this report I have presented the deep insight into the development of the new online banking system of the High street bank. I have presented a complete overview of the system requirements and design. This report is a useful document for the overall system analysis and design. I have developed the use case diagrams and class diagrams that are really effective for while system development. I hope this report will provide a valuable insight into the system design. References 1. Allen, R.J., 1997. A Formal Approach to Software Architecture, PhD thesis thesis, Software Engineering Institute, Carnegie Mellon University 2. Bass, L., Clements, P. and Kazman, R., 2003. Software Architecture in Practice, 2nd Edition. Addison Wesley, Reading, MA, USA. 3. Connley, Warren, Adrian Rad, and Stephen Botzum. 2004. Integrated Risk Management within NASA Programs/Projects’, In Space Systems Engineering and Risk Management, Manhattan Beach. 4. Hofmeister, C., Nord, R.L. and Soni., D.(1999), Describing software architecture with UML. in Proceedings of the TC2 1st Working IFIP Conference on Software Architecture (WICSA1), (San Antonio, TX, USA, 1999), pp. 145-159. 5. Kenneth. C. Laudon. 1999. Management Information Systems, (Fifth Edition), New Jersey, Prentice-Hall. 6. Martin, Paula K. and Bruce C. Chadbourne. 2004. The Professional Guide to Risk Assessment: The MTA Step-by-Step Method. Cincinnati, OH: Martin Training Association. 7. Selic, B. 1999. UML-RT: A profile for modelling complex real-time architectures. ObjecTime Limited. 8. Sommerville, Ian. 2004. Software Engineering (7th Edition). Addison Wesley. 2004. Read More