Trusted by +2 million users,
1000+ happy students everyday
Showing pages 1 to 6 of 26 pages
1
Contents1.Use Case Model Diagram (Logical Design Diagram)..................................................................42.Class Diagram (Logical Design)..................................................................................................63.Sequence Diagram (Logical Design)............................................................................................84. Program........................................................................................................................................9Critical Discussion: Introduction...................................................................................................18NationNarrow Reflection and Critical-Evaluation....................................................................18Critical self-reflection on the work................................................................................................19Software Development Life Cycle (SDLC) of this software.....................................................19Requirement Gathering..........................................................................................................19Design.....................................................................................................................................19Development..........................................................................................................................20Software Testing.....................................................................................................................20Deployment............................................................................................................................21Feedback.................................................................................................................................22Issues..............................................................................................................................................23Conclusion.....................................................................................................................................23References......................................................................................................................................242
Table of ContentS. NO.CONTENTPAGE NO.1.Use Case Model Diagram22.Class Diagram43.Sequence Diagram64.Program85.Critical Discussion:Introduction166.Critical self-reflection on the work177.Issues218.Conclusion219.References223
1.Use Case ModelDiagram (Logical Design Diagram)This diagram is employed to characterizedifferent actors / users or clients and their operations oractions or events.This use case diagram is employed to model the structure of software or a subsystem. It highlights the representation of user and their actions in which the particular user or anactor or a client is working on. It has mainly 2 components one is actor and two is use case in aspecific application It specifies theusers who are all going to use particular software withoutminding the actual implementation of a function. The actors are the real end users of the softwarewhich is depicted using an actor stereotype. The use case action is specified using oval symbol. Itis to be named with an action verb for functionality. The relationship between actor and a use casesymbol is depicted through a line which linkage the both. In this Banking Software for Nationarrow Building Society 3 main use cases where defined. They areoBank Manager,oBank Teller and Customer.The Bank Teller and the customer acts on account creation with enquiry of bank statements,deposit functionality, withdrawal action and fund transfer activitiesThe Bank manager acts on the above work flow along with adding user credentials and dealingwith approving and sanctioning of loans and allows to create account on various categoriesincluding current, saving, ISA, Business, etc.,The Bank manager use case inherits all the properties of the use case bank teller and alsointerms of customer point of view.4
Banking SystemBank Teller /Customer<<extends>>Bank ManagerBankBanking Software – Use Case Diagram5EnquiryDepositWithdrawalTransferUserCredentialsLoan Sanction
2. Class Diagram (Logical Design)This diagram is used to represent classes along with its attributes (variables) and methods(operations) also it is employed to specify relationship among base and derived classes. It is alogical building of a software programIt provides the complete structure of an object-orientedprogramming software application. It is an actual depiction of various class usages in software. Itis employed only for object-oriented constructs. The group of all the class depictions forms aclass diagram. The class representation box first part should have proper class name along withthe attribute depiction box second part should have the names of a variable and the methoddenoting box third part should have the name and return type of the function name. It isdecisively for stagnant depiction of a system. It will be sketched for the languages like c++, java,php, python, Smalltalk,etc.,It’s (class) represented with 3 main parts in a rectangular box. They are1stpart of the rectangular box is aclass name2ndpart of the rectangular box is for an attribute name3rdpart of the rectangular box is for amethod nameThe arrow line shows the relationship among various classes in an application like inheritance,aggregation, etc.,The BankAccount Class has two attributes accountno and amount and it has three functionswhich includes BankAccount(), deposit() and withdraw().The BankTeller class has various six labels four textboxes, five buttons , panel, frame attributesand it has three functions BankTeller(), testAccount, actionPerformed()The BankManager class has three functions. They are main() function, userCreden() andloanAccount()The BankManager inherits all the attributes and functionalities of its base class BankTellerwhich uses the class BankAccountfor its workingThe class NewWindowAdapter has a function of windowClosing() . It is basically derived fromthe base class WindowADapterThe class FundsInsufficientException has two attributes namely balance and withdraw _amountand two functions namely FundsInsufficientException() and toString(). It is basically derivedfrom the base class Exception6
desklib-logo
You’re reading a preview
Preview Documents

To View Complete Document

Click the button to download
Subscribe to our plans

Download This Document