INDEX
1. Introduction
2. System Analysis
a. Existing System
b. proposed System
3. Feasibility Report
a. Technical Feasibility
b. Operational Feasibility
c. Economical Feasibility
4. System Requirement Specification Document
a. Overview
b. Modules Description
c. Process Flow
d. SDLC Methodology
5. System Design
a. DFD
b. E-R diagram
c. UML
d. Data Dictionary
6. Technology Description
7. Coding
8. Testing & Debugging Techniques
9. Output Screens
10. Reports
11. Future Enhancements
12. Conclusion
INTRODUCTION
Looking for an online comprehensive solution to manage internet
banking. This will be accessible to all customers who have a valid user id and password. This system provides the following facilities………
• Balance enquiry
• Funds transfer to another account in the same bank
• Request for cheque book/change of address/stop payment of cheques.
• Viewing monthly and annual statements
In India, a number of banks have either gone for Internet Banking or are on the verge of going for it. Internet Banking System I am talking about is
different from what was possible up to now - off line information or few limited services. I am talking about the type that enables the customer to transact business on line in real time.
The Internet Banking System provides the facilities like Balance Enquiry , Funds transfer to another account in the same bank, Request for cheque book /change of address/stop payment of cheques and Viewing
monthly and annual statements. The Internet Banking System has developed a new security infrastructure for conducting commerce on the Internet. The initiative, called BankID, aims to become a national ID infrastructure
supporting services such as authentication and digital signatures for the entire authentication population.
Many researchers expect rapid growth in customers using online banking products and services. The Internet Banking System allows customer contact through increased geographical reach and lower cost delivery channels.
Customers can reach a given institution from literally anywhere in the world. Management must understand the risks associated with The Internet Banking
System before they make a decision to develop a particular class of business. Management should have the skills to effectively evaluate internet banking technologies and products. Use the Internet Banking System, the choice is yours. Make it wisely.
System Analysis
Purpose of the System:
This system provides an online solution to the customer by providing facilities such as balance enquiry, funds transfer to another account in the same bank etc.
Existing System:
Existing system is a manual system it will not provide the online system
Existing system does not provide the separate login for the user
(customer).
Existing system does not provide the online transaction facility.
This system does not give the update account information for the
customer
Proposed System:
The development of this new system contains the following activities, which try to develop on-line application by keeping the entire process in the view of data base integration approach.
Customer must have a valid user ID and password to login to the
system
If a wrong password is given thrice in the session, that account
will be locked and the customer will not be able to use it. When an invalid password is entered a warning is given to the user than the count going to get locked.
After the valid user logs in he is shown the list of accounts he has
with the bank.
On selecting the desired account he is taken to a page which
shows the present balance in that particular account number. User can view his monthly as well as annual statements. He can also take print out of the same.
If the transaction is successful a notification should appear to the
customer, in case it is unsuccessful, a proper message should be given to the customer as to why it failed.
TECHNICAL FEASIBILITY:
Evaluating the technical feasibility is the trickiest part of a feasibility study. This is because, at this point in time, not too many detailed design of the system, making it difficult to access issues like performance, costs on (on account of the kind of technology to be deployed) etc. A number of issues have to be considered while doing a technical
analysis.
i) Understand the different technologies involved in the proposed system:
Before commencing the project, we have to be very clear about what are the technologies that are to be required for the development of the new system.
ii) Find out whether the organization currently possesses the required technologies:
o Is the required technology available with the organization? o If so is the capacity sufficient?
For instance –“Will the current printer be able to handle the new reports and forms required for the new system?”
Operational Feasibility:
Proposed project is beneficial only if it can be turned into information systems that will meet the organizations operating requirements. Simply stated, this test of feasibility asks if the system will work when it is developed and installed. Are there major barriers to Implementation? Here are questions that will help test the operational feasibility of a project:Is there sufficient support for the project from management from users? If the current system is well liked and used to the extent that persons will not be able to see reasons for change, there may be resistance.
Are the current business methods acceptable to the user? If they are not, Users may welcome a change that will bring about a more operational and useful systems.
Have the user been involved in the planning and development of the project? Early involvement reduces the chances of resistance to the system and in general and increases the likelihood of successful project.
Since the proposed system was to help reduce the hardships encountered. In the existing manual system, the new system was considered to be operational feasible.
Economic Feasibility:
Economic feasibility attempts 2 weigh the costs of developing and implementing a new system, against the benefits that would accrue from having the new system in place. This feasibility study gives the top management the economic justification for the new system.
A simple economic analysis which gives the actual comparison of costs and benefits are much more meaningful in this case. In addition, this proves to be a useful point of reference to compare actual costs as the project progresses. There could be various types of intangible benefits on account of automation. These could include increased customer satisfaction, improvement in product quality better decision making timeliness of information, expediting activities, improved accuracy of operations, better documentation and record keeping, faster retrieval of information, better employee morale.
System Requirement Specification
Looking for an online comprehensive solution to manage internet banking. This will be accessible to all customers who have a valid user id and password. This system provides the following facilities………
• Balance enquiry
• Funds transfer to another account in the same bank
• Request for cheque book/change of address/stop payment of cheques.
No of Modules:
The system after careful analysis has been identified to be presented with the following modules:
The Modules involved are 1. Administrator. 2. Customer. 3. Transaction.
4. Security and authentication. 5. Reports
Description for Modules: Administrator:
Administrator can add the customers (users) and provides some username and password for the customer. Administrator can accept the
cheque book requests, view all the transactions and provide loans information and branch details.
Customer:
User can make a funds transfer to another account in the same bank. User is provided with a transaction password which is different from the login password. User applies the cheque book requests; view all the loan information, sub branch details.
User can transfer funds from his account to any other account with this bank. If the transaction is successful a notification should appear to the customer, in case it is unsuccessful, and a proper message should be given to the customer why it failed.
Security and
authentication:-1. User registration
2. Login as a user or administrator 3. Change password
4. Forgot password
Reports:-In this module the different actors can generate the different types of reports according to their access.
The Model 2 architecture for designing JSP pages is in reality, Model View Controller (MVC) applied to web applications. Hence the two terms can be used interchangeably in the web world. MVC originated in SmallTalk and has since made its way into Java community. Model 2 architecure and its derivatives are the cornerstones for all serious and industrial strength web applications designed in the real world. Hence it is essential for you
understand this paradigm thoroughly.
The main difference between Model 1 and Model 2 is that in Model 2, a controller handles the user request instead of another JSP. The controller is implemented as a Servlet. The following steps are executed when the user submits the request.
1. The Controller Servlet handles the user’s request. (This means the hyperlink in the JSP should point to the controller servlet).
2. The Controller Servlet then instantiates appropriate JavaBeans
based on the request parameters (and optionally also based on session attributes).
3. The Controller Servlet then by itself or through a controller helper communicates with the middle tier or directly to the database to fetch the required data.
4. The Controller sets the resultant JavaBeans (either same or a new one) in one of the following contexts – request, session or application. 5. The controller then dispatches the request to the next view based on the request URL.
6. The View uses the resultant JavaBeans from Step 4 to display data. Note that there is no presentation logic in the JSP. The sole function of the JSP in Model 2 architecture is to display the data from the
JavaBeans set in the request, session or application scopes. 7.
8.
This document play a vital role in the development of life cycle (SDLC) as it describes the complete requirement of the system. It means for use by developers and will be the basic during testing phase. Any changes made to the requirements in the future will have to go through formal change approval process.
SPIRAL MODEL was defined by Barry Boehm in his 1988 article, “A spiral Model of Software Development and Enhancement. This model was not the first model to discuss iterative development, but it was the first model to explain why the iteration models.
As originally envisioned, the iterations were typically 6 months to 2 years long. Each phase starts with a design goal and ends with a client reviewing the progress thus far. Analysis and engineering efforts are applied at each phase of the project, with an eye toward the end goal of the project.
The steps for Spiral Model can be generalized as follows:
• The new system requirements are defined in as much details as possible. This usually involves interviewing a number of users representing all the external or internal users and other aspects of the existing system.
• A preliminary design is created for the new system.
• A first prototype of the new system is constructed from the preliminary design. This is usually a scaled-down system, and represents an approximation of the characteristics of the final product.
• A second prototype is evolved by a fourfold procedure:
1. Evaluating the first prototype in terms of its strengths, weakness, and risks.
4. Constructing and testing the second prototype.
• At the customer option, the entire project can be aborted if the risk is deemed too great. Risk factors might involved development cost overruns, operating-cost miscalculation, or any other factor that could, in the customer’s judgment, result in a less-than-satisfactory final product.
• The existing prototype is evaluated in the same manner as was the
previous prototype, and if necessary, another prototype is developed from it according to the fourfold procedure outlined above.
• The preceding steps are iterated until the customer is satisfied that the refined prototype represents the final product desired.
• The final system is constructed, based on the refined prototype.
• The final system is thoroughly evaluated and tested. Routine maintenance is carried on a continuing basis to prevent large scale failures and to minimize down time.
Fig 1.0-Spiral Model
ADVANTAGES:
• Estimates(i.e. budget, schedule etc .) become more relistic as work
• It is more able to cope with the changes that are software development generally entails.
• Software engineers can get their hands in and start woring on the
SOFTWARE REQUIREMENT AND
HARDWARE REQUIREMENT
Software Requirements :
Operating System : Windows XP/2003 or Linux
User Interface : HTML, CSS
Client-side Scripting : JavaScript
Programming Language : Java
Web Applications : JDBC, Servlets, JSP
IDE/Workbench : My Eclipse 6.0
Database : Oracle 10g
Server Deployment : Tomcat 5.x
Frame Work : Struts 1.x
Hardware Requirements:
Processor : Pentium IV
Hard Disk : 40GB
System Design
DATA FLOW DIAGRAMS:
A graphical tool used to describe and analyze the moment of data through a system manual or automated including the process, stores of data, and delays in the system. Data Flow Diagrams are the central tool and the basis from which other components are developed. The transformation of data from input to output, through processes, may be described logically and independently of the physical components associated with the system. The DFD is also know as a data flow graph or a bubble chart.
DFDs are the model of the proposed system. They clearly should show the requirements on which the new system should be built. Later during design activity this is taken as the basis for drawing the system’s structure charts. The Basic Notation used to create a DFD’s are as follows:
Dataflow: Data move in a specific direction from an origin to a destination.
3. Source: External sources or destination of data, which may be People,
programs, organizations or other entities.
Data Store: Here data are stored or referenced by a process in the System.
Data Input Stages Data Input Stages
UI Screens
Reports
Data Input Stages
CONTEXT LEVEL DATA FLOW DIAGRAM
Data Output Stages
Data Output Stages
Data Output Stages
InternetBanking Administrator Eployee Cutomer D a ta B a se Branches Services Login Transactions Cheques Balance
Data Input Stages Data Input Stages
UI Screens
Reports
Data Input Stages
CONTEXT LEVEL DATA FLOW DIAGRAM
System Process
Data Output Stages
Data Output Stages
Data Output Stages
InternetBanking Administrator Eployee Cutomer D a ta B a se Branches Services Login Transactions Cheques Balance AUTHENTICATION DFD:
GUI Interface Username,Password Authentication Server
Authentication Server Authentication GUI Interface
NO
Level 2 Data Flow Diagram for Users Authentication
Data Input Stages
UI Screens
Reports
CONTEXT LEVEL DATA FLOW DIAGRAM
System Process
Data Output Stages
Data Output Stages
Data Output Stages
InternetBanking Administrator D a ta B a se Employee Branches Services Accounttypes FundTransfer CheqBookReq
Admin UI displaying set Of Operations Login General Information ViewAccount Types View ChequeIssue s View CustomerTra nsactions View Services ViewBranche s Add Employee View Requests LEVEL-2: Administrator:
GUI Interface InputStage Employee OutputStage Data Base Data Base InputStage Employee OutputStage GUI Interface
GUI Interface InputStage Services OutputStage Data Base Data Base InputStage Services OutputStage GUI Interface
GUI Interface InputStage AccountTtypes OutputStage Data Base 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 InputStage CheqBookReq OutputStage GUI Interface
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
Option3 AddBranches
GUI Interface AddBranchesFile
AddBranchesFile DataStore GUI Interface
Input Output
Input Output
GUI Interface ViewBranchesOption4 ViewBranchesFile
ViewBranchesFile DataStore GIU Interface
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
Option7 ViewFundTransfer
GUI Interface ViewFundTransferFile
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: Administrator: Open form() ---4.1.1.0 Enter FirstName ---4.1.1.1 Enter MidName ---4.1.1.2 LastName ---4.1.1.3
Bar Reg Date ---4.1.1.4 Select Qualification ---4.1.1.5 Enter Photograph ---4.1.1.6 Address ---4.1.1.7 PhoneNumber ---4.1.1.8 Emailid ---4.1.1.9 Enter Pin no 4.1.1.10
Level 4 Data Flow Diagram for Add Employee Details
Open form() ---4.1.2.0 Enter AccTypeName ---4.1.2.1 EnterAbbreviation 4.1.2.2 Enter Description ---4.1.2.3 EnterMinOpenBal 4.1.2.4 EnteMaxOpenBal 4.1.2.5 Enterintrest ---4.1.2.6 EnterMinBal ---4.1.2.7
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 D a ta B a se 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 Input CusTransaction Output Data Base Data Base Input CusTransaction Output GUI Interface
LEVEL-3: Employee:
Option1 AddCustomers
GUI Interface AddCustomerFile
AddCustomerFile DataStore GIU Interface
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
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
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 ViewMoneyTransaction
GUI Interface ViewMoneyTransactionFile
ViewMoneyTransactionFile DataStore GIU Interface
Input Input Output Output LEVEL-4: Employee: Open form () ---4.1.4.0 Enter CaseTypeName ---4.1.4.1
Enter Case Type Abbreviation ---4.1.4.2 Enter Case TypeDescription ---4.1.4.3 Enter Sdate ---4.1.4.4 Enter ChequeDate ---4.1.4.5 Enter ChequeNo ---4.1.4.6 Select CustomerId ---4.1.4.7
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 D a ta B a se 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 D a ta B a se Banks LoginDetails Balance Cheques StopPayment CusTransactio n
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 Input StopPayement Output Data Base Data Base Input StopPayment Output GUI Interface
GUI Interface Input CusTransaction Output Data Base Data Base Input CusTransaction Output GUI Interface
LEVEL-3: Customer:
Option1 ViewBankBranches
GUI Interface ViewBranchesFile
ViewBranchesFile DataStore GUI Interface
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
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
Option8 ViewCheqIssueDet
GUI Interface ViewCheqIssueDetFile
ViewCheqIssueDetFile DataStore GUI Interface
Input Output Input Output LEVEL-4: Customer: Open form() ---4.1.2.0 Enter LawTypeName ---4.1.2.1 Enter Abbreviation ---4.1.2.2 Enter Description ---4.1.2.3 Open form() ---4.1.3.0 Enter AccountNo ---4.1.3.1 Enter RequestTime ---4.1.3.2 Enter RequestDate ---4.1.3.3 Section CutomerId ---4.1.3.4 Enter ChequbookPosted Bit ---4.1.3.5 Enter Previous BookStatus ---4.1.2.3.6
UML Diagrams
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.
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.
System use case Diagram:
System A dm inistrat or Em ploy ee Custom erAdministrator Use case Diagram:
A dm inistrator Em ploy ees Branches Serv ices A ccount Ty pesFund Tra nsfer
Cust om er Login
Cheq Book Req
St op Pa y m ent
A dd Em ploy ee
View Em ploy ee
A dd Branches
View Bra nches
A dd Serv ices
View Serv ices
A dd A ccount Ty pes
View A ccount Ty pes
View Fund t ra nsfers
View Login Det ails
View Reques ts
Employee Use case Diagram:
Em ploy ee custom ers Bank s Fund Transfer ChequesStop Pay m ent
Cus transaction
Add Cust om ers
View Custom ers
v iew Branches
v iew A ccount ty pes
View Services
View Fund Transfer
v iew Cheq Req
View chq cancel
add Cheq issue
View Chq Issue
Add Stop Pay m ent
View Stop Pay
Customer Use Case Diagram:
Custom er Bank s Login Balance Cheques Transaction Stop Pay m entView Branches
View Serv ices
View Account Ty pes
View Login Details
A dd Bal Enquiry
View Bal Enq
Add Cheq book req
v iew Cheq Req
View Stop Pay m ents
A dd M oney Transac
Administrator Sequence Diagram:
Administrator Authentication Employees Branches Services Account Types Fund Transfer CustomerLogin CheqBookReq StopPayment
Success( Failed() if fail Add Employee() View Add View Add View Add Account View Account View Fund View Login
View Cheque Book
Employee Sequence Diagram:
Fund Transfer
Employee Authentication Customers Banks Cheques Stop Payment Cus Transaction Login() Fail() if fails if success Add View View View View View Fund View Cheque View Cheque Add Cheque Issue() View ChequeIssue()
Add Stop
View Stop
Customer Sequence Diagram:
Cheques
Customer Authntication Banks Login Balance StopPayment Transaction Login() Failed() Check( if Failes if Success View View View Account View Login Add Balance View Balance Add ChequeBook ViewChequeBook ViewStop AddMoney ViewMoney
Admin Collaboration Diagram:
Administ rator Authenti cation Employe es Branche s Services Account Types Fund Transfer Customer Login CheqBook Req Stop Payment 1: Success() 2: 3: Failed() 4: Add Employee() 5: View Employee() 6: Add Branches() 7: View branches() 8: Add Services() 9: View Services()10: Add Account Types() 11: View Account Types()
12: View FundTransfer() 13:
14: View Login Details()
15: View Cheque Book Requests()
Employee Collaboration Diagram:
Cus Transaction Employe e Authenti cation Custome rs Banks Fund Transfer Cheques Stop Payment 1: Login() 2: 3: Fail() 4: Add Customers() 5: View Customers() 6: View Branches() 7: View Accounts() 8: View Services()9: View Fund Transfers()
10: View Cheque Request() 11: View Cheque Cancel()
12: Add Cheque Issue() 13: View ChequeIssue()
14: Add Stop Payment() 15: View StopPayment()
Customer Collaboration Diagram:
Login Custome r Authntic ation Banks Balance Cheques Stop Payment Transact ion 1: Login() 2: Check() 3: Failed() 4: View Branches() 5: View Services() 6: View AccountTypes() 7: View LoginDetails()8: Add Balance Enquiry() 9: View Balance Enquiry()
10: Add ChequeBook Request() 11: ViewChequeBookRequest()
12: ViewStopPayments()
13: AddMoneyTransaction() 14: ViewMoneyTransaction()
Activity Diagrams
Employee Activity Diagram:
Employee Authentication Check Authentication Enter UserName,Password if Success if fail CheckHome Customer Banks FundTransfer Cheques StopPay Logout
AddCustomer ViewCustomer
ViewBranches ViewAccTypes AddCheqissue
AddStopPay ViewFundTransfer CusTransac ViewCusTransac ViewChqIssue ViewService ViewChqReq ViewStopPay
Customer Activity Diagram:
Customer Authentication Check Authentication Enter UserName,Password if Success if fail CheckHome Banks Login Balance Cheques StopPay Logout
ViewBranches ViewServices ViewLoginDet
AddCheqReq ViewStopPay AddBalEnquiry Transaction ViewBalEnq ViewChqReq ViewAccountTypes ViewBalEnquiry
UserMaster: DATA DICTIONARY: LoginDetails:
loginProfile:
ACCOUNTTYPEMASTER:
AccountTypeMaster:
BankBranchMaster:
BranchAccountTypes:
BankserviceMaster:
BranchServiceMaster
FieldName DataType Constraint
USERID NUMBER PRIMARY KEY
USERNAME VARCHAR2(20) PASSWORD VARCHAR2(20) FIRSTNAME VACHAR2(20) MIDDLENAME VARCHAR2(20) LASTNAME VARCHAR2(20) DOB DATE DOR DATE
DOE DATE ADDRESS VARCHAR2(20) PHONE VARCHAR2(20) EMAIL VARCHAR2(50) PHOTO BLOB BankBranchMaster:
FieldName DataType Constraint
BRANCHID NUMBER PRIMARY KEY
BRANCHADDRESS VARCHAR2(20)
BRANCHPHONENOONE VARCHAR2(20)
BRANCHPHONENOTWO VARCHR2(20)
BRANCHPHONENOTHREE VARCHAR2(20)
BRANCHEMAILID VARCHAR2(20)
BRANCHINCHGID NUMBER FOREIGN KEY
BANKSERVICESMASTER
FieldName DataType Constraint
SERVICEID NUMBER PRIMARY KEY
SERVICENAME VARCHAR2(20)
SERVICEACTIVESTATE VARCHAR2(20)
SERVICEDESC VARCHAR2(20)
BRANCHSERVICEMASTER
FieldName DataType Constraint
BRANCHID NUMBER FOREIGN KEY
SERVICEID NUMBER FOREIGN KEY
EMPLOYEESMASTER
FieldName DataType Constraint
EMPLOYEEID NUMBER PRIMARY KEY
NAME VARCHAR2(20)
PHONE VARCHAR2(20)
MAIL VARCHR2(20)
PHOTO BLOB
BRANCHID NUMBER FOREIGN KEY
ACCOUNTTYPEMASTER
FieldName DataType Constraint
ACCOUNTTYPEID NUMBER PRIMARY KEY
TYPENAME VARCHAR2(20) ABBREVATION VARCHR2(20) MINOPENBALANCE NUMBER(10,2) MAXOPENBALANCE NUMBER(10,2) INTRESTAPPLICABLEBIT NUMBER DESCRIPTION VARCHAR2(20) MINBALANCETOBEMAINTAINED NUMBER(10,2) CHECKBOOKFACILITYBIT NUMBER BANKTYPEBIT NUMBER BALACNCETYPEBIT NUMBER
SQL QUERIES FOR DATA BASE : TABLE : ACCOUNTTYPEMASTER
CREATE TABLE ACCOUNTTYPEMASTER
(
ACCOUNTTYPEID NUMBER,
TYPENAME VARCHAR2(20 BYTE),
ABBREVATION VARCHAR2(20 BYTE),
MINOPENBALANCE NUMBER(10,2),
MAXOPENBALANCE NUMBER(10,2),
INTRESTAPPLICABLEBIT VARCHAR2(20 BYTE),
DESCRIPTION VARCHAR2(20 BYTE),
MINBALANCETOBEMAINTAINED NUMBER(10,2),
CHECKBOOKFACILITYBIT VARCHAR2(20 BYTE),
BANKTYPEBIT VARCHAR2(20 BYTE),
BALACNCETYPEBIT VARCHAR2(20 BYTE) )
TABLESPACE USERS PCTUSED 0 PCTFREE 10 INITRANS 1 MAXTRANS 255 STORAGE ( INITIAL 64K MINEXTENTS 1 MAXEXTENTS 2147483645 PCTINCREASE 0 BUFFER_POOL DEFAULT ) LOGGING NOCOMPRESS NOCACHE NOPARALLEL MONITORING;
ALTER TABLE ACCOUNTTYPEMASTER ADD (
PRIMARY KEY (ACCOUNTTYPEID) USING INDEX TABLESPACE USERS PCTFREE 10 INITRANS 2 MAXTRANS 255 STORAGE ( INITIAL 64K MINEXTENTS 1 MAXEXTENTS 2147483645 PCTINCREASE 0 ));
BALANCEENQUIRYMASTER :
CREATE TABLE BALANCEENQUIRYMASTER
(
ENQUIRYID NUMBER,
ENQUIRYDATE DATE,
LOGINID VARCHAR2(20 BYTE),
FROMDATE DATE, TODATE DATE, ACCOUNTNO NUMBER, AMOUNT NUMBER ) TABLESPACE USERS PCTUSED 0 PCTFREE 10 INITRANS 1 MAXTRANS 255 STORAGE ( INITIAL 64K
BUFFER_POOL DEFAULT ) LOGGING NOCOMPRESS NOCACHE NOPARALLEL MONITORING;
ALTER TABLE BALANCEENQUIRYMASTER ADD (
PRIMARY KEY (ENQUIRYID) USING INDEX TABLESPACE USERS PCTFREE 10 INITRANS 2 MAXTRANS 255 STORAGE ( INITIAL 64K MINEXTENTS 1 MAXEXTENTS 2147483645 PCTINCREASE 0 ));
ALTER TABLE BALANCEENQUIRYMASTER ADD (
CONSTRAINT BALANCEENQUIRYMASTER_R01
FOREIGN KEY (ACCOUNTNO)
REFERENCES BANKACCOUNTS (ACCOUNTNO));
CREATE TABLE BANKACCOUNTS
(
LOGINID VARCHAR2(20 BYTE),
ACCOUNTNO NUMBER,
ACCOUNTINITIALBALANCE NUMBER,
ACCOUNTACTIVEBALANCE NUMBER,
ACCOUNTOPENINGDATE DATE,
BRANCHADDRESS VARCHAR2(20 BYTE) ) TABLESPACE USERS PCTUSED 0 PCTFREE 10 INITRANS 1 MAXTRANS 255 STORAGE ( INITIAL 64K MINEXTENTS 1 MAXEXTENTS 2147483645 PCTINCREASE 0 BUFFER_POOL DEFAULT ) LOGGING NOCOMPRESS
NOCACHE NOPARALLEL MONITORING;
CREATE UNIQUE INDEX BANKACCOUNTS_PK ON BANKACCOUNTS
(ACCOUNTNO) LOGGING TABLESPACE USERS PCTFREE 10 INITRANS 2 MAXTRANS 255 STORAGE ( INITIAL 64K MINEXTENTS 1 MAXEXTENTS 2147483645 PCTINCREASE 0 BUFFER_POOL DEFAULT ) NOPARALLEL;
BANKACCOUNTS:
ALTER TABLE BANKACCOUNTS ADD (
CONSTRAINT BANKACCOUNTS_PK PRIMARY KEY (ACCOUNTNO) USING INDEX TABLESPACE USERS PCTFREE 10 INITRANS 2 MAXTRANS 255 STORAGE ( INITIAL 64K MINEXTENTS 1 MAXEXTENTS 2147483645 PCTINCREASE 0 ));
ALTER TABLE BANKACCOUNTS ADD (
CONSTRAINT BANKACCOUNTS_R01
FOREIGN KEY (LOGINID)
REFERENCES LOGINDETAILS (LOGINNAME));
BANKACCOUNTTYPES:
CREATE TABLE BANKACCOUNTTYPES
(
BRANCHID NUMBER,
ACCOUNTYPEID NUMBER
)
MAXTRANS 255 STORAGE ( INITIAL 64K MINEXTENTS 1 MAXEXTENTS 2147483645 PCTINCREASE 0 BUFFER_POOL DEFAULT ) LOGGING NOCOMPRESS NOCACHE NOPARALLEL MONITORING;
ALTER TABLE BANKACCOUNTTYPES ADD (
CONSTRAINT BANKACCOUNTTYPES_R01
FOREIGN KEY (ACCOUNTYPEID)
REFERENCES ACCOUNTTYPEMASTER (ACCOUNTTYPEID));
BANKBRANCHMASTER:
CREATE TABLE BANKBRANCHMASTER
(
BRANCHID NUMBER,
BRANCHADDRESS VARCHAR2(20 BYTE),
BRANCHPHONENO1 VARCHAR2(20 BYTE),
BRANCHPHONENO2 VARCHAR2(20 BYTE),
BRANCHPHONENO3 VARCHAR2(20 BYTE),
EMAIL VARCHAR2(20 BYTE) ) TABLESPACE USERS PCTUSED 0 PCTFREE 10 INITRANS 1 MAXTRANS 255 STORAGE ( INITIAL 64K MINEXTENTS 1 MAXEXTENTS 2147483645 PCTINCREASE 0 BUFFER_POOL DEFAULT ) LOGGING NOCOMPRESS NOCACHE NOPARALLEL MONITORING;
ALTER TABLE BANKBRANCHMASTER ADD (
PRIMARY KEY (BRANCHID)
USING INDEX
TABLESPACE USERS
INITRANS 2 MAXTRANS 255 STORAGE ( INITIAL 64K MINEXTENTS 1 MAXEXTENTS 2147483645 PCTINCREASE 0 )); BANKSERVICESMASTER:
CREATE TABLE BANKSERVICESMASTER
(
SERVICEID NUMBER,
SERVICENAME VARCHAR2(20 BYTE),
SERVICEACTIVESTATE VARCHAR2(20 BYTE),
SERVICEDESC VARCHAR2(20 BYTE) ) TABLESPACE USERS PCTUSED 0 PCTFREE 10 INITRANS 1 MAXTRANS 255 STORAGE ( INITIAL 64K MINEXTENTS 1 MAXEXTENTS 2147483645 PCTINCREASE 0 BUFFER_POOL DEFAULT ) LOGGING NOCOMPRESS NOCACHE NOPARALLEL MONITORING;
ALTER TABLE BANKSERVICESMASTER ADD (
PRIMARY KEY (SERVICEID) USING INDEX TABLESPACE USERS PCTFREE 10 INITRANS 2 MAXTRANS 255 STORAGE ( INITIAL 64K MINEXTENTS 1 MAXEXTENTS 2147483645 PCTINCREASE 0 ));
BRANCHEMPLOYEE:
CREATE TABLE BRANCHEMPLOYEE
(
LOGINNAME VARCHAR2(20 BYTE),
BRANCHADDRESS VARCHAR2(20 BYTE) ) TABLESPACE USERS PCTUSED 0 PCTFREE 10 INITRANS 1 MAXTRANS 255 STORAGE ( INITIAL 64K MINEXTENTS 1 MAXEXTENTS 2147483645 PCTINCREASE 0 BUFFER_POOL DEFAULT ) LOGGING NOCOMPRESS NOCACHE NOPARALLEL MONITORING;
ALTER TABLE BRANCHEMPLOYEE ADD (
CONSTRAINT BRANCHEMPLOYEE_R01
FOREIGN KEY (LOGINNAME)
BRANCHSERVICEMASTER:
CREATE TABLE BRANCHSERVICEMASTER
( BRANCHID NUMBER, SERVICEID NUMBER ) TABLESPACE USERS PCTUSED 0 PCTFREE 10 INITRANS 1 MAXTRANS 255 STORAGE ( INITIAL 64K MINEXTENTS 1 MAXEXTENTS 2147483645 PCTINCREASE 0 BUFFER_POOL DEFAULT ) LOGGING NOCOMPRESS NOCACHE NOPARALLEL MONITORING;
ALTER TABLE BRANCHSERVICEMASTER ADD (
CONSTRAINT BRANCHSERVICEMASTER_R01
FOREIGN KEY (SERVICEID)
REFERENCES BANKSERVICESMASTER (SERVICEID));
CHEQUEBOOKREQUESTMASTER :
CREATE TABLE CHEQUEBOOKREQUESTMASTER
(
REQUESTID NUMBER,
REQUESTDATE DATE,
LOGINID VARCHAR2(20 BYTE),
ACCOUNTNO NUMBER,
CHEQUEBOOKTEST VARCHAR2(20 BYTE),
PREVIOUSCHEQUEBOOKSTATUS VARCHAR2(20 BYTE),
STATUS VARCHAR2(20 BYTE) )
MAXTRANS 255 STORAGE ( INITIAL 64K MINEXTENTS 1 MAXEXTENTS 2147483645 PCTINCREASE 0 BUFFER_POOL DEFAULT ) LOGGING NOCOMPRESS NOCACHE NOPARALLEL MONITORING;
ALTER TABLE CHEQUEBOOKREQUESTMASTER ADD (
CONSTRAINT CHEQUEBOOKREQUESTMASTER_R01
FOREIGN KEY (ACCOUNTNO)
REFERENCES BANKACCOUNTS (ACCOUNTNO));
CHEQUEISUEMASTER:
CREATE TABLE CHEQUEISUEMASTER
( CHEQUEISSUEID NUMBER, REQUESTID NUMBER, ISUEDATE DATE, FROMNUMBER NUMBER, TONUMBER NUMBER, ACCOUNTNO NUMBER,
EMPLOYEENAME VARCHAR2(20 BYTE),
NOOFCHEQUES NUMBER ) TABLESPACE USERS PCTUSED 0 PCTFREE 10 INITRANS 1 MAXTRANS 255 STORAGE ( INITIAL 64K MINEXTENTS 1 MAXEXTENTS 2147483645 PCTINCREASE 0 BUFFER_POOL DEFAULT ) LOGGING NOCOMPRESS NOCACHE NOPARALLEL MONITORING;
ALTER TABLE CHEQUEISUEMASTER ADD (
(CHEQUEISSUEID) USING INDEX TABLESPACE USERS PCTFREE 10 INITRANS 2 MAXTRANS 255 STORAGE ( INITIAL 64K MINEXTENTS 1 MAXEXTENTS 2147483645 PCTINCREASE 0 ));
ALTER TABLE CHEQUEISUEMASTER ADD (
CONSTRAINT CHEQUEISUEMASTER_R01
FOREIGN KEY (ACCOUNTNO)
REFERENCES BANKACCOUNTS (ACCOUNTNO));
CUSTOMERTRANSACTIONMASTER:
CREATE TABLE CUSTOMERTRANSACTIONMASTER
(
TRANSACTIONID NUMBER,
EMPLOYEENAME VARCHAR2(20 BYTE),
TRANSACTIONDATE DATE,
TRANSACTIONTYPE VARCHAR2(20 BYTE),
AMOUNT NUMBER,
ACCOUNTNO NUMBER,
BRANCHNAME VARCHAR2(20 BYTE) ) TABLESPACE USERS PCTUSED 0 PCTFREE 10 INITRANS 1 MAXTRANS 255 STORAGE ( INITIAL 64K MINEXTENTS 1 MAXEXTENTS 2147483645 PCTINCREASE 0 BUFFER_POOL DEFAULT ) LOGGING NOCOMPRESS NOCACHE NOPARALLEL MONITORING;
CREATE UNIQUE INDEX CUSTOMERTRANSACTIONMASTER_PK ON CUSTOMERTRANSACTIONMASTER
(TRANSACTIONID) LOGGING
TABLESPACE USERS PCTFREE 10
STORAGE ( INITIAL 64K MINEXTENTS 1 MAXEXTENTS 2147483645 PCTINCREASE 0 BUFFER_POOL DEFAULT ) NOPARALLEL;
ALTER TABLE CUSTOMERTRANSACTIONMASTER ADD (
CONSTRAINT CUSTOMERTRANSACTIONMASTER_PK PRIMARY KEY (TRANSACTIONID) USING INDEX TABLESPACE USERS PCTFREE 10 INITRANS 2 MAXTRANS 255 STORAGE ( INITIAL 64K MINEXTENTS 1 MAXEXTENTS 2147483645 PCTINCREASE 0 ));
ALTER TABLE CUSTOMERTRANSACTIONMASTER ADD (
CONSTRAINT CUSTOMERTRANSACTIONMASTER_R01
FOREIGN KEY (ACCOUNTNO)
REFERENCES BANKACCOUNTS (ACCOUNTNO));
FUNDSTRANSFER:
CREATE TABLE FUNDSTRANSFER
(
FUNDSTRANSFERID NUMBER,
FUNDSTRANSFERDATE DATE,
FROMACCOUNTNO VARCHAR2(20 BYTE),
TOACCOUNTNO VARCHAR2(20 BYTE),
AMOUNT NUMBER,
LOGINID VARCHAR2(20 BYTE) ) TABLESPACE USERS PCTUSED 0 PCTFREE 10 INITRANS 1 MAXTRANS 255 STORAGE ( INITIAL 64K MINEXTENTS 1 MAXEXTENTS 2147483645 PCTINCREASE 0 BUFFER_POOL DEFAULT
) LOGGING NOCOMPRESS NOCACHE NOPARALLEL MONITORING;
ALTER TABLE FUNDSTRANSFER ADD (
PRIMARY KEY (FUNDSTRANSFERID) USING INDEX TABLESPACE USERS PCTFREE 10 INITRANS 2 MAXTRANS 255 STORAGE ( INITIAL 64K MINEXTENTS 1 MAXEXTENTS 2147483645 PCTINCREASE 0 ));
ALTER TABLE FUNDSTRANSFER ADD (
CONSTRAINT FUNDSTRANSFER_R01
FOREIGN KEY (LOGINID)
REFERENCES LOGINDETAILS (LOGINNAME));
LOGINAUDIT:
CREATE TABLE LOGINAUDIT
(
LOGINID VARCHAR2(20 BYTE),
LOGINDATE DATE,
LOGINDESC VARCHAR2(200 BYTE) ) TABLESPACE USERS PCTUSED 0 PCTFREE 10 INITRANS 1 MAXTRANS 255 STORAGE ( INITIAL 64K MINEXTENTS 1 MAXEXTENTS 2147483645 PCTINCREASE 0 BUFFER_POOL DEFAULT ) LOGGING NOCOMPRESS NOCACHE NOPARALLEL MONITORING;
FOREIGN KEY (LOGINID)
REFERENCES LOGINDETAILS (LOGINNAME)
ON DELETE CASCADE);
LOGINDETAILS:
CREATE TABLE LOGINDETAILS
(
LOGINNAME VARCHAR2(20 BYTE),
PASSWORD VARCHAR2(20 BYTE),
FIRSTNAME VARCHAR2(20 BYTE),
LASTNAME VARCHAR2(20 BYTE),
LOGINTYPE VARCHAR2(20 BYTE),
LOGINSTATUS VARCHAR2(20 BYTE),
REGDATE DATE,
SQUESTIONID NUMBER,
SANSWER VARCHAR2(20 BYTE),
FIRSTLOGIN NUMBER, PASSMODIFIEDDATE DATE ) TABLESPACE USERS PCTUSED 0 PCTFREE 10 INITRANS 1 MAXTRANS 255 STORAGE ( INITIAL 64K MINEXTENTS 1 MAXEXTENTS 2147483645 PCTINCREASE 0 BUFFER_POOL DEFAULT ) LOGGING NOCOMPRESS NOCACHE NOPARALLEL MONITORING;
ALTER TABLE LOGINDETAILS ADD (
PRIMARY KEY (LOGINNAME) USING INDEX TABLESPACE USERS PCTFREE 10 INITRANS 2 MAXTRANS 255 STORAGE ( INITIAL 64K MINEXTENTS 1 MAXEXTENTS 2147483645 PCTINCREASE 0
));
ALTER TABLE LOGINDETAILS ADD (
UNIQUE (PASSWORD) USING INDEX TABLESPACE USERS PCTFREE 10 INITRANS 2 MAXTRANS 255 STORAGE ( INITIAL 64K MINEXTENTS 1 MAXEXTENTS 2147483645 PCTINCREASE 0 )); LOGINPROFILE:
CREATE TABLE LOGINPROFILE
(
LOGINID VARCHAR2(20 BYTE),
BIRTHDATE DATE,
HNO VARCHAR2(20 BYTE),
STREET VARCHAR2(20 BYTE),
CITY VARCHAR2(20 BYTE),
STATE VARCHAR2(20 BYTE),
COUNTRY VARCHAR2(20 BYTE),
PINCODE VARCHAR2(20 BYTE),
CONTACTNO VARCHAR2(20 BYTE),
EMAIL VARCHAR2(200 BYTE),
LOCALE VARCHAR2(20 BYTE),
PROFILEMODIFIEDDATE DATE ) TABLESPACE USERS PCTUSED 0 PCTFREE 10 INITRANS 1 MAXTRANS 255 STORAGE ( INITIAL 64K MINEXTENTS 1 MAXEXTENTS 2147483645 PCTINCREASE 0 BUFFER_POOL DEFAULT ) LOGGING NOCOMPRESS NOCACHE NOPARALLEL MONITORING;
ON DELETE CASCADE);
QUESTIONBASE : CREATE TABLE QUESTIONBASE
(
QUESTIONID NUMBER,
QUESTIONDETAIL VARCHAR2(20 BYTE) ) TABLESPACE USERS PCTUSED 0 PCTFREE 10 INITRANS 1 MAXTRANS 255 STORAGE ( INITIAL 64K MINEXTENTS 1 MAXEXTENTS 2147483645 PCTINCREASE 0 BUFFER_POOL DEFAULT ) LOGGING NOCOMPRESS NOCACHE NOPARALLEL MONITORING;
ALTER TABLE QUESTIONBASE ADD (
PRIMARY KEY (QUESTIONID) USING INDEX TABLESPACE USERS PCTFREE 10 INITRANS 2 MAXTRANS 255 STORAGE ( INITIAL 64K MINEXTENTS 1 MAXEXTENTS 2147483645 PCTINCREASE 0 )); STOPPAYMENTMASTER :
CREATE TABLE STOPPAYMENTMASTER
(
STOPPAYMENTTYPEID NUMBER,
STOPPAYDATE DATE,
LOGINID VARCHAR2(20 BYTE),
CHEQUENO NUMBER,
AMOUNT NUMBER(10,2),
CHEQUEDATE DATE,
REASONFORSTOPPING VARCHAR2(20 BYTE),
STATUS VARCHAR2(20 BYTE) ) TABLESPACE USERS PCTUSED 0 PCTFREE 10 INITRANS 1 MAXTRANS 255 STORAGE ( INITIAL 64K MINEXTENTS 1 MAXEXTENTS 2147483645 PCTINCREASE 0 BUFFER_POOL DEFAULT ) LOGGING NOCOMPRESS NOCACHE NOPARALLEL MONITORING;
ALTER TABLE STOPPAYMENTMASTER ADD (
PRIMARY KEY (STOPPAYMENTTYPEID) USING INDEX TABLESPACE USERS PCTFREE 10 INITRANS 2 MAXTRANS 255 STORAGE ( INITIAL 64K MINEXTENTS 1 MAXEXTENTS 2147483645 PCTINCREASE 0 ));
Sql quries used in our projects:
checkPassword---select * from logindetails where password=? and loginname=?
checkFirstLogin---select firstlogin from logindetails where loginname=?
loginCheck---select logintype from logindetails where password=? and loginname=? and loginstatus='unlock'
---update logindetails set firstlogin='0' where loginname=?
---select loginname,logintype from logindetails where loginname=?
---update logindetails set firstlogin="+ count + " where loginname=?
loginaudit---insert into loginaudit values(?,?,?) changePassword---UPDATE logindetails SET
password=?,passmodifieddate=? WHERE loginname=? and password=?
changeQuestion---select (max(questionid))+1 from questionbase
UPDATE logindetails SET squestionid=?,sanswer=? WHERE loginname=? and password=?
UPDATE logindetails SET
squestionid=?,sanswer=? WHERE loginname=? and password=? recoverPasswordByExistQuestion---SELECT password FROM
logindetails WHERE loginname=? and squestionid=? and sanswer=? registration---select questionid from questionbase where questiondetail='"+ownsecretquest+"'"
select (max(questionid))+1 from questionbase
INSERT INTO questionbase VALUES(?,?) insert into LOGINDETAILS values(?,?,?,?,?,?,?,?,?,?,?) insert into LOGINPROFILE
values(?,?,?,?,?,?,?,?,?,?,?,?)
getProfile---select
ld.firstname,ld.lastname,lp.birthdate,lp.city,lp.state,lp.country from logindetails ld,loginprofile lp where ld.loginname=lp.loginid and ld.loginname='"+loginname+"'"
modifyProfile---UPDATE loginprofile SET
birthdate=?,hno=?,street=?,city=?,state=?,country=?,pincode=?,cont actno=?,email=?,profilemodifieddate=? WHERE loginid=?");
UPDATE logindetails SET firstname=?,lastname=? WHERE loginname=?;
changeAccountStatus---UPDATE logindetails SET loginstatus=? WHERE loginname=?
getProfile---select
ld.loginname,ld.firstname,ld.lastname,lp.birthdate,lp.city,lp.state,lp.co untry from logindetails ld,loginprofile lp where
Technology Description
HTML
An initialize of Hypertext Markup Language, is the predominant markup language for web pages. It provides a means to describe the structure of text-based information in a document — by denoting certain text as headings, paragraphs, lists, and so on — and to supplement that text with interactive forms, embedded images, and other objects. HTML is written in the form of labels (known as tags), surrounded by angle brackets. HTML can also describe, to some degree, the appearance and semantics of a document, and can include embedded scripting language code which can affect the behavior of web browsers and other HTML processors.
HTML is also often used to refer to content of the MIME type text/html or even more broadly as a generic term for HTML whether in its XML-descended form (such as XHTML 1.0 and later) or its form descended directly from SGML
Hyper Text Markup Language
Hypertext Markup Language (HTML), the languages of the World Wide Web (WWW), allows users to produces Web pages that include text, graphics and pointer to other Web pages (Hyperlinks).
HTML is not a programming language but it is an application of ISO Standard 8879, SGML (Standard Generalized Markup Language), but specialized to hypertext and adapted to the Web. The idea behind Hypertext is that instead of reading text in rigid linear structure, we can easily jump from one point to another point. We can navigate through the information based on our interest and preference. A markup language is simply a series of elements, each delimited with special characters that define how text or other items enclosed within the elements should be displayed. Hyperlinks are underlined or emphasized works that load to other documents or some portions of the same document.
HTML can be used to display any type of document on the host computer, which can be geographically at a different location. It is a versatile language and can be used on any platform or desktop.
HTML provides tags (special codes) to make the document look attractive. HTML tags are not case-sensitive. Using graphics, fonts, different sizes, color, etc., can enhance the presentation of the document. Anything that is not a tag is part of the document itself.
<! -- --> specifies comments
<A>………. </A> Creates hypertext links <B>………. </B> Formats text as bold
<BIG>………. </BIG> Formats text in large font.
<BODY>…</BODY> All tags and text in the HTML document <CENTER>...</CENTER> Creates text
<DD>…</DD> Definition of a term <DL>...</DL> Creates definition list
<FONT>…</FONT> Formats text with a particular font <FORM>...</FORM> Encloses a fill-out form
<FRAME>...</FRAME> Defines a particular frame in a set of frames
<H#>…</H#> Creates headings of different levels( 1 – 6 ) <HEAD>...</HEAD> Information about a document
<HR>...</HR> Creates a horizontal rule
<HTML>…</HTML> Contains all other HTML tags <META>...</META> Meta-information about a document
<SCRIPT>…</SCRIPT> Contains client-side or server-side script <TABLE>…</TABLE> Creates a table
<TD>…</TD> Indicates table data in a table <TR>…</TR> Designates a table row
<TH>…</TH> Creates a heading in a table
Attributes:
The attributes of an element are name-value pairs, separated by "=", and written within the start label of an element, after the element's name. The value should be enclosed in single or double quotes, although values consisting of certain characters can be left unquoted in HTML (but not XHTML).Leaving attribute values unquoted is considered unsafe.
Most elements take any of several common attributes: id, class, style and title. Most also take language-related attributes: Lang and Dir.
The id attribute provides a document-wide unique identifier for an element. This can be used by style sheets to provide presentational properties, by browsers to focus attention on the specific element or by scripts to alter the contents or presentation of an element. The class attribute provides a way of classifying similar elements for presentation purposes. For example, an HTML document (or a set of documents) may use the designation class="notation" to indicate that all elements with this class value are all subordinate to the main text of the document (or documents). Such notation classes of elements might be gathered together and presented as footnotes on a page, rather than appearing in the place where they appear in the source HTML.
An author may use the style non-attribute codes presentational properties to a particular element. It is considered better practice to use an element’s son- id page and select the element with a style sheet, though sometimes this can be too cumbersome for a simple ad hoc application of styled properties. The title is used to attach sub textual explanation to an element. In most browsers this title attribute is displayed as what is often referred to as a tooltip. The generic inline span element can be used to demonstrate these various non-attributes.
The preceding displays as HTML (pointing the cursor at the abbreviation should display the title text in most browsers).
Advantages:
A HTML document is small and hence easy to send over the net. It is small because it does not include formatted information.
HTML is platform independent. HTML tags are not case-sensitive.
JavaScript
JavaScript is a script-based programming language that was developed by Netscape Communication Corporation. JavaScript was originally called Live Script and renamed as JavaScript to indicate its relationship with Java. JavaScript supports the development of both client and server components of Web-based applications. On the client side, it can be used to write programs that are executed by a Web browser within the context of a Web page. On the server side, it can be used to write Web server programs that can process information submitted by a Web browser and then update the browser’s display accordingly
Even though JavaScript supports both client and server Web programming, we prefer JavaScript at Client side programming since most of the browsers supports it. JavaScript is almost as easy to learn as HTML, and JavaScript
statements can be included in HTML documents by enclosing the statements between a pair of scripting tags
<SCRIPTS>.. </SCRIPT>. <SCRIPT LANGUAGE = “JavaScript”>
JavaScript statements </SCRIPT>
Here are a few things we can do with JavaScript:
Validate the contents of a form and make calculations.
Add scrolling or changing messages to the Browser’s status line.
Animate images or rotate images that change when we move the mouse over them.
Detect the browser in use and display different content for different browsers.
Detect installed plug-ins and notify the user if a plug-in is required.
We can do much more with JavaScript, including creating entire application.
JavaScript Vs Java:
JavaScript and Java are entirely different languages. A few of the most glaring differences are:
Java applets are generally displayed in a box within the web document; JavaScript can affect any part of the Web
While JavaScript is best suited to simple applications and adding interactive features to Web pages; Java can be used for incredibly complex applications.
There are many other differences but the important thing to remember is that JavaScript and Java are separate languages. They are both useful for different things; in fact they can be used together to combine their advantages.
Advantages
JavaScript can be used for Sever-side and Client-side scripting.
It is more flexible than VBScript.
JavaScript is the default scripting languages at Client-side since all the browsers supports it.
XML
What Is XML?
XML: A markup language for organizing information in text files. XML stands for extensible Markup Language.
XML File: A text file that contains information organized in a structure that meets XML standards.
XML can also be viewed as a meta-language for defining more specific markup languages, because it only specifies the structural rules of unspecified tags that are used to organize information. One can easily extend XML to define a