Sanju
Sanju
)
GOVT. LOCHAN PRASAD PANDEY COLLEGE SARANGARH DIST-RAIGARH (C.G.)
[1]
SHAHEED NANDKUMAR PATEL UNIVERSITY RAIGARH (C.G.)
GAMNI SAHU
[2]
SHAHEED NANDKUMAR PATEL UNIVERSITY RAIGARH (C.G.)
DECLARATION
[3]
SHAHEED NANDKUMAR PATEL UNIVERSITY RAIGARH (C.G.)
CENTER CERTIFICATE
प्रभारी
प्राचार्य
[4]
SHAHEED NANDKUMAR PATEL UNIVERSITY RAIGARH (C.G.)
Project Guide
[5]
ACKNOWLEDGMENT
! Thank you
[6]
INDEX
[7]
6.3 UNIT TESTING
CHAPTER -7
7. SYSTEM SECURITY AND MAINTENANCE
7.1 INTRODUCTION
7.2 SECURITY AND SOFTWARE
CHAPTER - 8
8. CODING
CHAPTER - 9
9. OUTPUT SCREEN
CHAPTER -10
10. CONCLUSION
10.1 FUTURE SCOPE
10.2 USER MANUAL
10.3 CONCLUSION
10.4 FUTURE ENHACEMENT
CHAPTER - 11
11. BIBIOGRAPHY
[8]
[9]
INTRODUCTION
INTRODUCTION TO PROJECT
Bank is the place where customers feel the sense of safety for their
property. In the bank, customers deposit and withdraw their money.
Transaction of money also is a part where customer takes shelter of the bank.
Now to keep the belief and trust of customers, there is the positive need for
management of the bank, which can handle all this with comfort and ease.
Smooth and efficient management affects the satisfaction of the customers and
staff members, indirectly. And of course, it encourages management committee
in taking some needed decision for future enhancement of the bank.
[10]
1.2 PROBLEM OF EXISTING SYSTEM
[11]
[12]
SYSTEM ANALYSIS
INTRODUCTION
The model that is basically being used is this particular WATER FALL
MODEL. To begin with the viability analysis is completed. Once that part is
over the responsibility psychoanalysis and job preparation gets started. If system
is available one and adjustment and addition of new component is needed,
research of present system can be utilized as basic model.
The design start following the obligation evaluation is total and the coding
starts after the mean is full. After the indoctrination is completed, the difficult is
performed. Within this model the series:
Requirement Analysis
Project Planning
System design
Detail design
Coding
Unit testing
System integration & testing
Here the linear purchasing of these activities is critical. End of the period the
end result of one stage is suggestions of other stage. The output of each phase is
usually result of one stage is the suggestions of other stage. The output of each
phase is usually to be consistent with the entire necessity of the machine. Some
of the figure of twisting model is also integrated like following the people
worried with the job review completion of each of the period the work done.
[13]
WATER FALL MODEL was being chosen because all essential were known
beforehand and the objective of our software development is the
computerization / automation associated with an already existing manual
working system.
HARDWARE REQUIRMENTS:
Processor: Pentium 3.0 GHz or higher
RAM: 1GB or MORE
Hard Drive: 250 GB or MORE
Type: Laptop or Desktop
SOFTWARE REQUIRMENTS:
Turbo C++
Dev C++
MS Office
2.4 PROPOSED SYSTEM
Input design is an integral part of overall system design. The primary objective
tthrough the input design is as listed below:
To produce a cost-effective approach to input.
To archive optimum level of precision.
[15]
To ensure that the type is suitable and grasped by the user.
OUTPUT
[16]
FEASIBILITY REPORT
Technical Feasibility
Operational Feasibility
Economical Feasibility
Technical concern typically raised during the possibility level of the assessment
includes the next:
The system analysis is beneficial only if they can be twisted out into data
system. Which will get together the organizations in commission requirements?
[18]
Ready feasibility facet of the task. As a significant part of the scheme
conclusion. Some of the significant issues lifted are to test the operational
feasibility of a project.
A system can be developed to be correct and that will be used if install must still
be a good speculation for the business. In the affordable viability, the
development cost in creating the system is evaluate in opposition to the
unlimited advantage derived from the new system , financial benefits must
equal or go beyond the costs.
[19]
SOFTWARE REQUIREMENT SPECIFICATION
INTRODUCTION
[20]
Purpose: The main purpose for getting ready this report is to provide general
perception into the evaluation and requirements of the prevailing system or
situation and then for identifying the operating characteristics of the machine.
Scope: This File plays a vital role in the development life pattern (SDLC) and it
describes the entire requirement of the machine. It is designed for use by the
coders and will be the basic during testing period. Any changes designed to the
necessities in the future will have to proceed through formal change
endorsement process.
[22]
SYSTEM DESIGN
INTRODUCTION
5.1 NORMALIZATION
The above table is not normalizes. We will see the problems that we
face when a table is not normalized.
UPDATE ANOMALY: In the above table we have two rows for employee
Rick as he belongs to two departments of the company. If we want to update the
address of Rick then we have to update the same the same in two rows or the
data will become inconsistent. If somehow, the correct address gets update in
one department but not in other then as per the database, Rick would be having
two different addresses, which is not correct and would lead to inconsistent
data.
[24]
To overcome these anomalies, we need to normalize the data. In the next
section we will discuss about normalization.
5.2 E-R
DIAGRAM
[25]
5.3 DATA FLOW DIAGRAM
USER INFORMATION
ACCOUNT
ADMIN INFORMATION
[26]
DFD LEVEL 2 (REGISTRATION)
REGISTRATION
DISPLAY REGISTRATION
USER REGISTRATION
RECORD
DISPLAY REGISTRATION
RECORD
[27]
standard in 1997. It’s been managed by UML as an approved standard in 2005.
UML has been revised over the years and is reviewed periodically.
[28]
SYSTEM TESTING AND IMPLEMENTATION
INTRODUCTION
This phase starts after the completion of phases like Unit Testing and
Integration testing.
System testing is the testing performed on completely developed and
integrated system.
Once complete system has been built then it has to be tested against
system specifications to verify whether it delivers the required features
and quality standards.
System testing verifies the entire product, after integrating all software
and hardware components and validating/testing it according to project
requirement specifications.
System testing comprises of two types of testing: Functional testing and
Non- Functional testing.
Functional Testing: involves testing of business requirements and
product features.
Non-functional Testing: involves testing features that are not directly
related to business functionality but are essential.
[29]
Testing commences at the vertex of the spiral and specializes in each
device of the program as implemented in source code. Screening improvement
by moving outward across the spiral to integration assessment, where the focus
is on the design and the structure of the software architecture. Communicating
another start outward on the spiral we face validation evaluation where
necessities proven as part of software necessities examination are validated
towards the software that is constructed.
Unit testing
Module testing
Sub-system testing
System testing
Acceptance testing
Component testing
Integration testing
[30]
execution paths etc. White box testing uses specific knowledge of programming
code to examine output. The test is accurate only if the tester knows what the
program is supposed to do. He or she can then see if the program diverges from
its intended goal. White box testing does not account for errors caused by
omission, and all visible code must also be readable. As the knowledge of
internal coding structure is prerequisite, it becomes very easy to find out which
type of input/data can help in testing the application effectively. The other
advantage of white box testing is that it helps in optimizing the code. It helps in
removing the extra lines of code, which can bring in hidden defects.
SMOKE TESTING
REQUIREMENT TESTING
PARTITION TESTING
TEST PROCESS
CONDITIONAL TESTING
In this part of the testing each of the conditions were examined to both
true and phony aspects. And all the resulting pathways were examined.
[31]
This kind of testing selects the path of this program in line with the
location of definition and use of factors. This kind of trials was used only
once some local variable were declared. These were mostly useful in nested
claims.
LOOP TESTING
In this kind of examining all the loops are analysed to all or any the
limitations possible. The following exercise was used for these loops:
IMPLEMENTATION
This phase gives us the clears pictures of our new system and all
the points that have been carefully looked in when designing the computerized
system.
Sincere efforts were taken for the implementation of the following goals.
[32]
Maximizing the source test readability.
Minimizing the development.
[33]
SYSTEM SECUIRITY AND MAINTENANCE
INTRODUCTION
Querying the status of the person of the person firewall and turning it on.
Querying the status of the anti-malware program, turning it on and
instructing it to update itself.
Querying the status of the Internet security setting and asking the user to
change them if are not optimal.
Querying the status of the automatic maintenance tasks, which includes a
quick scan for malware, disk defragmentation, power efficiency
diagnostics?
Querying the status of Backup and restore and prompting the user to
schedule a backup if one is not in place.
Querying the status of file history; however, the user is not alerted about
it.
[34]
Querying the status of Home Group; no alerts are issued about it.
Managing problems logged by Windows Error Reporting: The user can
see their detail, send them to Microsoft if they are not automatically sent,
query a solution for them (although most of the times, there is none) or
selectively delete them.
[35]
[36]
CODING
#include<iostream>
#include<fstream>
#include<cctype>
#include<iomanip>
class account
int accountnumber;
char name[50];
int deposit;
char type;
public:
void create_account();
void show_account();
void modify_account();
void deposit_funds(int);
[37]
void draw_funds(int);
void get_report();
int get_accountnumber();
int get_funds();
char get_accounttype();
};
void account::create_account()
cin>>accountnumber;
cin.ignore();
cin.getline(name,50);
cin>>type;
type=toupper(type);
cin>>deposit;
void account::show_account()
[38]
cout<<"\nAccount Number: "<<accountnumber;
void account::modify_account()
cin.ignore();
cin.getline(name,50);
cin>>type;
type=toupper(type);
cin>>deposit;
void account::deposit_funds(int x)
deposit+=x;
void account::draw_funds(int x)
[39]
{
deposit-=x;
void account::get_report()
cout<<accountnumber<<setw(10)<<" "<<name<<setw(10)<<"
"<<type<<setw(6)<<deposit<<endl;
int account::get_accountnumber()
return accountnumber;
int account::get_funds()
return deposit;
char account::get_accounttype()
return type;
[40]
void write_account();
void display_sp(int);
void modify_account(int);
void delete_account(int);
void display_all();
int main()
char opt;
int num;
for(;;)
system("color 05");
system("cls");
cout<<"\t\t\t\t******\t******";
cout<<"\t\t\t\tNAME\tGAMNI SAHU";
cout<<"\t\t\t\tCLASS\tPGDCAA";
cout<<"\t\t\t\t*****\t*****";
cout<<"\t\t\t\t****\t****";
cout<<"\t\t\t\t***\t***";
[41]
cout<<"\t\t\t\t**\t**";
cout<<"\t\t\t\t*\t*";
cout<<"\t\
t@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@
@@@@@@@@@";
cout<<"\n\t\
t@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@
@@@@@@@@@\n";
cout<<"\n\t\tOption: ";
cin>>opt;
system("cls");
switch(opt)
case '1':
system("color 02");
write_account();
break;
[42]
case '2':
system("color 03");
deposit_withdraw(num, 1);
break;
case '3':
system("color 06");
deposit_withdraw(num, 2);
break;
case '4':
system("color 08");
display_sp(num);
break;
case '5':
system("color 9");
display_all();
break;
case '6':
system("color 10");
delete_account(num);
break;
[43]
case '7':
system("color 11");
modify_account(num);
break;
case '8':
system("color 04");
break;
cin.ignore();
cin.get();
if(opt=='8')
break;
return 0;
void write_account()
account ac;
ofstream outFile;
outFile.open("account.dat",ios::binary|ios::app);
ac.create_account();
[44]
outFile.write(reinterpret_cast<char *> (&ac), sizeof(account));
outFile.close();
void display_sp(int n)
account ac;
bool flag=false;
ifstream inFile;
inFile.open("account.dat",ios::binary);
if(!inFile)
return;
cout<<"\nBALANCE DETAILS\n";
if(ac.get_accountnumber()==n)
ac.show_account();
flag=true;
[45]
inFile.close();
if(flag==false)
void modify_account(int n)
bool found=false;
account ac;
fstream File;
File.open("account.dat",ios::binary|ios::in|ios::out);
if(!File)
return;
if(ac.get_accountnumber()==n)
ac.show_account();
ac.modify_account();
int pos=(-1)*static_cast<int>(sizeof(account));
[46]
File.seekp(pos,ios::cur);
found=true;
File.close();
if(found==false)
void delete_account(int n)
account ac;
ifstream inFile;
ofstream outFile;
inFile.open("account.dat",ios::binary);
if(!inFile)
return;
outFile.open("Temp.dat",ios::binary);
inFile.seekg(0,ios::beg);
if(ac.get_accountnumber()!=n)
inFile.close();
outFile.close();
remove("account.dat");
rename("Temp.dat","account.dat");
cout<<"\n\n\tRecord Deleted...";
void display_all()
account ac;
ifstream inFile;
inFile.open("account.dat",ios::binary);
if(!inFile)
return;
[48]
cout<<"\n\n\t\tACCOUNT HOLDER LIST\n\n";
cout<<"===================================================
=\n";
cout<<"===================================================
=\n";
ac.get_report();
inFile.close();
int amt;
bool found=false;
account ac;
fstream File;
File.open("account.dat", ios::binary|ios::in|ios::out);
if(!File)
return;
[49]
}
if(ac.get_accountnumber()==n)
ac.show_account();
if(option==1)
cin>>amt;
ac.deposit_funds(amt);
if(option==2)
cin>>amt;
int bal=ac.get_funds()-amt;
cout<<"Insufficience balance";
else
ac.draw_funds(amt);
[50]
}
int pos=(-1)*static_cast<int>(sizeof(ac));
File.seekp(pos,ios::cur);
found=true;
File.close();
if(found==false)
[51]
[52]
OUTPUT SCREENSHOOT
1. MAIN MENU
3. TO DEPOSITE FUNDS
[53]
4. TO WITHDRAW FUNDS
5. TO CHECK BALANCE
[54]
6. TO VIEW ALL A/C HOLDER
7. TO CLOSE AN A/C
8. TO MODIFY AN A/C
[55]
[56]
CONCLUSION AND SCOPE
1. Customer Login
2. Admin Login
3. Add record customer
4. Delete record
5. Modify account
6. View customer account
7. View balance
8. Withdraw / Transaction
9. Go Back
[57]
10.3 CONCLUSION
[58]
[59]
BIBLIOGRAPHY
BOOK REFERENCE
WEB REFERENCE
www.Tutorialspoint.com/ C++
www.Javapoint.com/ C++
www.w3school.in
www.youtube.com
[60]
[61]
[62]