Professional Documents
Culture Documents
Preliminary
Investigation
Implementation
Determination of
Requirements
System Testing
Developm ent of
System
Design of System
So, here we followed the different stages of system development life cycle to
develop Billing Software efficiently.
After carrying out these interviews, I drew conclusion about the Top
Managements requirements and whether users are in support of the new
system.
This activity is consisting of three parts:-
The tools that we were requiring were all available to us they are:-
Hardware Requirements
Server Machine:
Minimum p-3, 256 MB RAM, 20 GB Hard Disk
Client Machine:
Minimum p-3, 128 MB RAM, 8 GB Hard Disk
Printer:
132 columns High
language support
Speed
Dot
Matrix
Printer
with
local
Software Requirements
Windows OS: Version 2000 and above; Source: Microsoft for Server
Windows OS: Version 2000 or XP; Source: Microsoft for Client
Visual Basic: Version 6.0 and above; Source: Microsoft
MS-Access:
This software also possesses behavioral feasibility. Its because the users of
the system are computer professionals and know the advantages of computer
system. Moreover, this application is going to enhance their skills and
reduce their workloads.
8
SYSTEM DESIGN
10
User Interface
Communication Interface
The various documents that are maintained by the RR section that have been
used to analyze the user interfaces that will interact with the billing software.
The billing software consists of many modules and these modules consist of
various sub modules, which provides the user with various facilities.
The software may either be installed on a client server based setup with a
Local Area Network (using the Ethernet Interface, one to one connection and
TCP/IP) or on a standalone machine whereby client and server components
resides on the same machine.
12
Account No
User
Account
Details
Bank
System
Transaction
Flow chart
13
ACC. NO.
ADDRESS
.
NAME
BALANCE.
START
BANK
TRANSACTION
DEBIT
h
a
s
CUSTOMER
Don
e by
CREDI
T
14
START
CUSTOMER
ha
s
ha
s
FIXED
DEPOSITE
ACCOUNT
AMOUNT
ID. NO.
DURATION
BALANCE
15
ACC. ID.
Transaction Process
TRANSACTION
CUSTOMER
CURRENT
BALANCE
DEBIT
CREDI
T
UPDATE
BALANCE
UPDATE
BALANCE
BALANCE
16
Unit Testing:
It is testing of individual module. Before initiating unit
testing, it must be ensured that the code is peer previewed.
Integration Testing:
Integration testing is performed after all the software units are combined
together. The objective here is to test the software interfaces. Project team
conducts the integration testing. Before entering integration testing, it may
be ensured that code review and unit testing have been performed on the
individual software modules.
I conducted the unit testing for finding errors and the results of the unit
testing are recorded and action initiated for rectification of the
errors/defects.
VALIDATION
Almost every field in the database which is sensitive i.e. responsible for
some important changes are validated. Basically we validated the field as
such is numeric and the length in case of the primary keys and also used the
Data base to complete most of the details once entered at the data entry time,
So that while performing the transaction at faster rate also the user is not
going to face any problems or can make any sort of blunders in the fine,
status, book that can be issued, and other important fields.
Mostly the validation is carried out in the lost focus, click, change and other
similar events where the entered value is compared with the one stored in the
database and if there is duplication to occur or no match with the database
then the entry is to be removed and user is prompt to reenter it.
18
19
part