DATA FLOW DIAGRAMS
AUTHENTICATION DFD:
GUI Interface Username,Password Authentication Server
Authentication Server Authentication GUI Interface
NO
Level 2 Data Flow Diagram for Users Authentication
ADMIN:
Data Input Stages
UI Screens
Reports CONTEXT LEVEL DATA FLOW DIAGRAM
System Process
Data Output Stages
Data Output Stages
Data Output Stages
InternetBanking Administrator
Data Base
Employee
Branches
Services
Accounttypes
FundTransfer
CheqBookReq
Level1 Data Flow Diagram for Admin:
Admin UI displaying
GUI Interface InputStage Employee OutputStage Data Base
Data Base InputStage Employee OutputStage GUI Interface
GUI Interface InputStage Branches OutputStage Data Base
GUI Interface InputStage Services OutputStage Data Base
Data Base InputStage Services OutputStage GUI Interface
GUI Interface AccountTtype
s Data Base
InputStage OutputStage
Data Base InputStage AccountTypes OutputStage GUI Interface
GUI Interface InputStage FundTransfer OutputStage Data Base
Data Base InputStage FundTransfer OutputStage GUI Interface
GUI Interface InputStage CheqBookreq OutputStage Data Base
Data Base CheqBookRe
q GUI Interface
InputStage OutputStage
LEVEL-3:
ADMINISTRATOR:
Option1 AddEmployee
GUI Interface AddEmployeeFile
AddEmployeeFile DataStore GUI Interface
Input Output
In[ut Output
GUI Interface ViewEmployeeOption2 ViewEmployeeFile
ViewEmployeeFile DataStore GIU Interface
Input Output
Input Output
Option3 AddBranches
GUI Interface AddBranchesFile
AddBranchesFile DataStore GUI Interface
Input Output
Input Output
GUI Interface ViewBranchesOption4 ViewBranchesFile
ViewBranchesFile DataStore GIU Interface
Input Output
Input Output
Option5 AddServices
GUI Interface AddServicesfile
AddServicesFile DataStore GUI Interface
Input Output
Input Output
GUI Interface ViewServicesOption6 ViewServicesFile
ViewServicesFile DataStore GIU Interface
Input Output
Input Output
Option7 ViewFundTransfer
GUI Interface ViewFundTransferF
ile
ViewFundTransferF
ile DataStore GUI Interface
Input Output
Input Output
GUI Interface ViewLoginDetailsOption8 ViewLogindetailsFile
ViewLoginDetailsFil
e DataStore GIU Interface
Input Output
Input Output
Option 9 ViewCheqBookreq
GUI Interface ViewChqbookReqFile
ViewChqBookReqFile DataStore GUI Interface
Input Output
Input Output
GUIInterface Option 10
ViewStopPayments ViewStopPaymentFile
ViewStopPaymentFile DataStore GIUInterface
Input Output
Input Output
LEVEL-4:
Level 4 Data Flow Diagram for Add Employee Details
Open form()
Level 4 Data Flow Diagram for Add Acc Types Details
Employee:
UI Screens
Reports Data Input Stages
CONTEXT LEVEL DATA FLOW DIAGRAM
System Process
Data Output Stages
Data Output Stages
Data Output Stages
InternetBanking Eployee
Data Base
Customer
Banks
FundTransfe r
Cheques
StopPayment
CusTransactio n
Level1 Data Flow Diagram for Employee:
Employee
UI displaying set Of Operations Login
General Information
ViewAccount Types
View ChequeIssue
s
View CustomerTra
nsactions View Services Registration
ViewBranche s
LEVEL-2:
EMPLOYEE:
GUI Interface Input Customer Output Data Base
Data Base Input Customer Output GUI Interface
GUI Interface Input Banks Output Data Base
Data Base Input Banks Output GUI Interface
GUI Interface Input FundTransfer Output Data Base
Data Base Input FundTransfer Output GUI Interface
GUI Interface Input Cheques Output Data Base
Data Base Input Cheques Output GUI Interface
GUI Interface Input StopPay Output Data Base
Data Base Input StopPay Output GUI Interface
GUI Interface CusTransactio
n Data Base
Input Output
Data Base CusTransactio
n GUI Interface
Input Output
LEVEL-3:
Employee:
Option1 AddCustomers
GUI Interface AddCustomerFile
AddCustomerFile DataStore GIU Interface
Input Output
Input Output
Option2 ViewCustomerFile
GUI Interface ViewCustomerFile
ViewCustomerFile DataStore GIU Interface
Input Output
Input Output
Option3 ViewBranches
GUI Interface ViewBranchesFile
ViewBranchesFile DataStore GIU Interface
Input Output
Input Output
Option4 ViewAccountTypes
GUI Interface ViewAccountTypesFile
ViewAccounttypesFile DataStore GIU Interface
Input
Input Output
Output
Option5 ViewStopPayments
GUI Interface ViewStopPaymentsFile
ViewStopPaymentsFile DataStore GIU Interface
Input Output
Input Output
Option6 AddBalanceEnquiry
GUI Interface AddBalanceEnquiryFile
AddBalanceEnquiryFile DataStore GIU Interface
Input Output
Input Output
Option7 ViewBalanceEnquiryFile
GUI Interface ViewBalanceEnquiryFile
ViewBalanceenquiryFile DataStore GIU Interface
Input Output
Input Output
Option8 AddChequeBookReq
GUI Interface AddCheqBookReqFile
AddCheqBookReqFile DataStore GUI Interface
Input Output
Input Output
GUI Interface ViewCheqBookReqOption9 ViewCheqBookreqFile
ViewCheqBookReqFile DataStore GIU Interface
Input Output
Input Output
GUI Interface AddMoneyTransactionFile
AddMoneyTransactionFile DataStore GIU Interface
Input Output
Input Output
Option10 AddMoneytransaction
Option11
Level 4 Data Flow Diagram for Stop Payment Master Details
LEVEL-0:
Customer:
UI Screens
Reports Data Input Stages
CONTEXT LEVEL DATA FLOW DIAGRAM
System Process
Data Output Stages
Data Output Stages
Data Output Stages
InternetBanking Customer
Data Base
Banks
LoginDetails
Balance
Cheques
StopPayment
CusTransactio n
UI Screens
Reports Data Input Stages
CONTEXT LEVEL DATA FLOW DIAGRAM
System Process
Data Output Stages
Data Output Stages
Data Output Stages
InternetBanking Customer
Data Base
Banks
LoginDetails
Balance
Cheques
StopPayment
CusTransactio n
Level1Data Flow Diagram For Customer:
Customer UI displaying set Of Operations Login
General Information
ViewAccount Types
Add Money Transactions
View MoneyTransa
ctions View Services Registration
ViewBranche s
LEVEL-2:
Customer:
GUI Interface Input Banks Output Data Base
Data Base Input Banks Output GUI Interface
GUI Interface Input LoginDetails Output Data Base
Data Base Input LoginDetails Outptu GUI Interface
GUI Interface Input Cheques Output Data Base
Data Base Input Cheques Output GUI Interface
GUI Interface Input Balance Output Data Base
Data Base Input Balance Output GUI Interface
GUI Interface StopPayemen
t Data Base
Input Output
Data Base Input StopPayment Output GUI Interface
GUI Interface CusTransactio
n Data Base
Input Output
Data Base CusTransactio
n GUI Interface
Input Output
LEVEL-3:
Customer:
Option1 ViewBankBranches
GUI Interface ViewBranchesFile
ViewBranchesFile DataStore GUI Interface
Input Output
Input Output
Option2 ViewAccountType
GUI Interface ViewAccountTypeFile
ViewAccountTypeFile DataStore GUI Interface
Input
Input Output
Outptu
Option3 ViewLoginDetails
GUI Interface ViewLoginDetailsform
ViewLogindetailsForm DataStore GUI Interface
Input Output
Input Output
Option4 AddMOneyTransaction
GUI Interface AddMoneyTransactionFile
AddMoneyTransactionFile DataStore GUI Interface
Input Output
Input Output
Option5 ViewMoneyTransaction
GUI Interface ViewMoneyTransactionFile
ViewMoneyTransactionFile DataStore GUI Interface
Input Output
Input Output
Option6 AddChequeBookRequest
Master
GUI Interface AddChequeBookReqdetFile
AddCheqBookreqDetFile DataStore GUI Interface
Input Output
Input Output
Option7 ViewChequeBookReque
stMaster
GUI Interface ViewChequeBookReqdetFile
ViewCheqBookreqDetFile DataStore GUI Interface
Input Output
Input Output
Option8
Level 4 Data Flow Diagram for Add Cheque Book Request Details
E-R Diagram
UML Diagrams
(Unified Modeling Language)
The Unified Modeling Language allows the software engineer to express an analysis model using the modeling notation that is governed by a set of syntactic semantic and pragmatic rules.
A UML system is represented using five different views that describe the system from distinctly different perspective. Each view is defined by a set of diagram, which is as follows.
User Model View:
i. This view represents the system from the users perspective.
ii. The analysis representation describes a usage scenario from the end-users perspective.
Structural model view:
i. In this model the data and functionality are arrived from inside the system.
ii. This model view models the static structures.
Behavioral Model View:
It represents the dynamic of behavioral as parts of the system, depicting the interactions of collection between various structural elements described in the user model and structural model view.
Implementation Model View:
In this the structural and behavioral as parts of the system are represented as they are to be built.
Environmental Model View:
In this the structural and behavioral aspects of the environment in which the system is to be implemented are represented.
UML is specifically constructed through two different domains they are:
i. UML Analysis modeling, this focuses on the user model and structural model views of the system.
ii. UML design modeling, which focuses on the behavioral modeling, implementation modeling and environmental model views.
Use case Diagrams represent the functionality of the system from a user’s point of view. Use cases are used during requirements elicitation and analysis to represent the functionality of the system. Use cases focus on the behavior of the system from external point of view.
Actors are external entities that interact with the system. Examples of actors include users like administrator, bank customer …etc., or another system like central database.