A Programaçao Orientada a Objeto
Por: Eric Alves • 13/5/2016 • Artigo • 834 Palavras (4 Páginas) • 281 Visualizações
[pic 1]
TOWER HAMLETS COLLEGE
BTEC HNC IN COMPUTING & SYSTEMS DEVELOPMENT
Banking Application for firm ICC-digitals
Eric Alves
Student ID No: 1117690
Unit 19: Object Oriented Programing
Lecturer André Beckley
Final Submission Date 08/01/2015
[pic 2]
ABSTRACT
Object oriented programming methodology is heavily used in the industry to develop complex systems with proven success. The OOP principles are based on solid research in the field of software engineering and system development.
This assignment will enable you to develop an understanding of the principles of object oriented programming as an underpinning technological concept in the field of programming, data management and systems development. You will be able to apply object oriented paradigm in system development and test the robustness an accuracy of the system with reflections on the processes and outcomes.
TABLE OF CONTENTS:
1.0 – INTRODUCTION 2
TASK 1
2.0 – Object Oriented Programming Key Concepts 3
TASK 2
3.0 -
TASK 3
TASK 4
Appendices
Appendix 1 – OOP Poster
Appendix 2
1.0 – INTRODUCTION:
The purpose of this report is to discuss the principles, characteristics and features of object oriented programming using graphical and practical implementation of a banking application which will be operated by the bank cashiers.
Will be identified objects, data and file structure to implement the design making use of diagrams.
An implementation of the design will be provided to demonstrate how the system works and also will be provided solutions to problems that may occur.
Also the design will be analysed and tested to ensure that system runs without error or bugs ensuring that a good solution is provided.
TASK 1
2.0 – Object Oriented Programming Key Concepts
Please refer to appendix 1.
TASK 2
USE CASE DIAGRAM 1 – General Bank Application
[pic 3][pic 4][pic 5][pic 6][pic 7][pic 8][pic 9][pic 10][pic 11][pic 12][pic 13][pic 14][pic 15][pic 16][pic 17][pic 18][pic 19][pic 20][pic 21][pic 22][pic 23][pic 24][pic 25][pic 26][pic 27]
USE CASE DIAGRAM 2 – Action Required: Deposit Money[pic 28]
[pic 29][pic 30][pic 31]
[pic 32]
[pic 33]
[pic 34][pic 35]
[pic 36]
[pic 37][pic 38][pic 39]
[pic 40][pic 41]
[pic 42][pic 43][pic 44][pic 45][pic 46]
[pic 47]
[pic 48][pic 49]
[pic 50]
[pic 51][pic 52][pic 53][pic 54][pic 55]
[pic 56]
[pic 57]
Narrative:
Validate card
Customer inserts card
Card is validated, if card is invalid it will be rejected
Validate Customer
Customer inserts PIN
PIN is validated, if pin is invalid will be required to be confirmed
Deposit Type:
Customer specify if it is a Cash or Cheque Deposit
Specify Amount
Customer specify amount.
Money Insertion
Customer insert money,
Count Money, if amount specified and money inserted do not match deposit will be rejected and money returned.
Eject Card
Provide Receipt
USE CASE DIAGRAM 3 – Action Required: Withdraw Money[pic 58][pic 59][pic 60][pic 61][pic 62][pic 63][pic 64][pic 65][pic 66][pic 67][pic 68][pic 69][pic 70][pic 71][pic 72][pic 73][pic 74][pic 75][pic 76][pic 77][pic 78][pic 79]
[pic 80][pic 81][pic 82][pic 83][pic 84][pic 85][pic 86][pic 87]
Narrative:
Validate card
Customer inserts card
Card is validated, if card is invalid it will be rejected
Validate Customer
Customer inserts PIN
PIN is validated, if pin is invalid will be required to be confirmed
Specify Amount
Customer requests amount
System checks balance, if not enough funds will be displayed the following message: You have insufficient funds to complete the transaction
Issue Money
Determine availability
Count money
Eject card
Provide money
Provide Receipt
FLOW CHART DIAGRAM 1: Action Required: Deposit Money
[pic 88]
FLOW CHART DIAGRAM 2: Action Required: Withdraw Money
[pic 89]
CLASS DIAGRAM[pic 90][pic 91][pic 92][pic 93][pic 94][pic 95][pic 96]
[pic 97]
[pic 98]
[pic 99]
Test Number | Test Description | Test Date/Action | Test Result | Re-Test Y/N | |||
Normal | Erroneous | Extreme | |||||
Black Box Testing | 1 | Depositing Money in Current Account | 20 | #£!!!! | |||
White Box Testing | |||||||
- Bank Account is a class that provides variables and methods that can be inherited by all the different accounts types which each one are classified as subclasses.
- Polymorphism can be presented in all the 5 types of bank accounts, each one behaves and provide transactions that can be unique or common to other account types.
- Current and Business Accounts present specific variables and methods that can provide a wider range of transactions and possibilities than Savings, ISA and Child Accounts.
- Savings account can do most of transactions but presents some limitations, such as no credit card, loans and or overdraft are not applicable and some of the methods are not available, however it can provide interest.
- ISA and Child Accounts are accounts which an agreement is made that money cannot be withdrawn before the end of terms and conditions of the agreement. They are very basic accounts and do not provide overdraft, credit cards, loans, however they can also provide interest as savings accounts.
- In order to develop the system it was adopted Adaptive Planning in which the requirements were added during the development process.
References
https://youtu.be/OkC7HKtiZC0
...