i-faktor testimony bureau full document
DESCRIPTION
Try to use itTRANSCRIPT
I-FaKTOR Testimony Bureau (IFTB)
Synopsis:
The project deals with the I-Factor followed for an IT firm and also with the profit and
process management followed for a firm. The Software companies will be in need of the
hardware resources from the different client and the problem faced by the company is
they will be unable to get the complete requirements of the hardware as due to finance to
solve this, the company focus on the banking sector. The company directly will be having
the direct investment on the banking sector and with the help of bank the company will
be getting the hardware resources from the client. As part of the manual it is very difficult
to manage the process of the bank to provide the facilities to all the company having
account with them. Based on the criteria followed in the banking sector,
they will be providing the opportunities to the firm to get the hardware requirements to
them.
As by making to a web-based process the firm will be getting the complete record
from the bank and also the criteria for getting the help from the bank. The back order
process for the requirements also will be handled by the banking sector and the
information will be providing to the client. The default mailing procedure will be
followed in which the mail will be applied within the intranet of the web –application.
The application also maintains the client details of the company and also the banking
sector details up to date. The on-line processing of ordering the resource requirements to
the bank and the file transfer within the web server will be followed based on the
authentication provided to the user.
The web application will be implementing the latest web technology features of
AJAX in which the speed of the web-pages in the internet will be faster as compared
with the previous web features followed.
‘
The web-application contains the following modules:
Bank Criteria module
Transaction module
Patron module
File Transfer module
Quality Check module
Mail module
Secure module
Admin module
Report module
Module Description:
Bank Criteria module
The bank will be following different type of criteria based on the transaction and also the
standards and investment procedures. The system should provide the automatic
remainder to the clients and the updates of the bank also should be intimated to the client
based on the reporting structure.
Transaction module
The bank will maintain the credit and debit payment of the firm and also the client
records. Based on the initial criteria of the bank the transaction structure will be followed
and it will maintain in a centralized server.
Patron module
The complete details of the client of the firm will be updated sequentially in the server
and the official details of the client in terms of the bank transaction will also be updated
and maintained. The patron may be having more than one bank account with different
type of bank based on the banking sector proficiencies.
File Transfer module
The firm maintains the set of files for the banking transaction and file sharing will be
provided to the authorized users of the firm and also the bank will be sharing some
files to the client based on the work procedure and the flow of the criteria followed in
the banking domain.
Quality Check module
The firm maintains a set of quality procedures to be checked for the file transfer
within the client or in bank. Quality manger will be having a normal quality check
with the file working on it and based on the quality check the file will be transferred.
Mail Module
The intranet mailing concept will be followed in the application. The mail can be sent
from the part of the client and also to the bank and to the firm. Only the main can be
sent with in the organization people who had given the rights.
Secure Module
The Bank follows a set of security features and provides some authorization to the
firm sharing of the resources both to the client and also to the customers. The
advanced security features will be implemented in the security.
Admin module
The administrator of the application will be providing the authentication and
authorization to the users and the total control of the web-application will be maintained
by the admin.
Report ModuleThe company requires different type of reports like bank transaction, client report,
company report etc., the different part of reports will be used to track the record.
SYSTEM STUDY:
Existing System
The existing system is being done manually. Each process is entered by manual
means. The process involved in creating a particular report consumes such time, since
searching through the manual record involves more manual activity which is a time
consuming process. The process can be prone to resulting in errors and in duplication of
data. Apart from tedious process, there is a chance for missing data and reports.
Limitations of Existing System:
Existing system is a window based Application.
The time involved in retrieving any information takes long.
File transfer is very difficult in window based application.
Lots of papers has be maintained
Time delay
Wastage of human resources
Record maintenance is difficult
Proposed System:
This project helps to maintain the details of the clients, banks and transaction
details in full fledged security. Unauthorized persons cannot access the data. The
transactions are kept online, so that there is fast completion of the transaction process
available.
The current system is developed by web based application.
No need for manual work.
The retrieval time is quick and fast.
File Transfer is very easy.
DATA FLOW DIAGRAM
A data flow diagram is graphical tool used to describe and analyze movement of
the data through a system. These are the central tool and the basis form which the other
components are developed. The transformation of the data from the input to output,
through processed, may be described logically and independently of physical components
associated with the system. These are known as the logical dataflow diagram. The
physical data flow diagram show actual implements and movement of the data between
people, departments and workstation, a full description of system actually consists of set
of data flow diagrams. Using two familiar notations Yourdon, Gane and Sarson notation
develops the data flow diagrams. Each component in DFD is labeled with a descriptive
name. Process is further identified with number that will be used for identification
purpose. The development of DTD’s is done in several levels. Each process in lower
level diagram can be broken down into a more detailed DFD in the next level. Top-level
diagram is often called context diagram. It consist a single process bit, which plays vital
role studying the current system. The process at the first level DFD.
The idea behind the explosion of a process into more process is that
understanding at one level of details is exploded into greater detailed at the next level.
This is done until further explosion is necessary and an adequate amount of detail is
described for analyst to understand the process.
Larry Constantine first developed the DFD as a way of expressing system
requirements in a graphical form, this lead to the modular design.
A DFD is also known as a “Bubble Chart” has the purpose of clarifying system
requirements and identifying major transformation the will become program in system
design. So it is the starting point of the design to lowest level of details. A DFD consists
of series of bubbles joined by data flows in the system.
DFD SYMBOLS
In the DFD, there are four Symbols
1. A square define a source or destination system data
2. An arrow identified data flow. It is the pipeline through which the
information flow
3. A circle or a bubble represents a process that transforms
4. Incoming data flow into outgoing data flows
5. An open rectangle is a data store, data at rest or a temporary of data
Process that transformation data flow
Source or Destination of data
CONSTRUCTING A DFD
Several rules of thumb are used in drawing DFD’s
Process should be named and numbered for an easy reference. Each name
should be representative of the process.
The direction of flow is top to bottom and from left to right. Data
traditionally flow from source to the destination although they may flow
back to the source. One way to indicate this is to draw long flow line back
to the source. An alternative way is to repeat the source symbol as a
destination. Since it is used more than once in the DFD it is marked with a
short diagonal.
When a process is exploded into lower level details, they are numbered.
The names of data stores and destinations are written in capital letters.
Process and dataflow names have the first letter of each work capitalized.
A DFD typically shows the minimum contents of data store. Each data store
should contain all the data elements that flow in and out.
Questionnaires should contain all the data elements that flow in and out. Missing
interface redundancies and like is than accounted for often through interviews.
FEATURES OF DFD’S
1. The DFD shows flow of data, not of control loops and decision are
controlled consideration do not appear on a DFD.
2. The DFD does not indicate the time factor involved in any process
whether the data flows take place daily, weekly, monthly or yearly.
3. The sequence of events is not brought out on the DFD.
TYPES OF DATA FLOW DIAGRAMS
1. Current Physical
2. Current Logical
3. New Logical
4. New Physical
CURRENT PHYSICAL:
In current physical DFD processes label include the name of people or
their positions or the names of computer system that might provide some of the overall
system processing label includes an identification of the technology used to process the
data. Similarly data flows and data stores are often labels with the names of the actual
physical media on which data are stored such as file folders, computer files, business
from or computer tapes.
CURRENT LOGICAL
The physical aspects at the system are removed as mush as possible so that the
current system is reduced to its essence to the data and the processors that transforms
them regardless of actual physical form.
NEW LOGICAL
This is exactly like a current logical model if the user were completely happy with
he user were completely happy with functionality of the current system but had problems
with how it was implemented typically through the new logical model will differ from
current logical model while having additional functions, absolute function removal and
inefficient flows recognized.
NEW PHYSICAL
The new physical represents only the physical implementation of the new system.
RULES GOVERNING THE DFD’S PROCESS
1. No process can have only outputs
2. No process can have only inputs. If an object has only inputs
than it must be a sink.
3. A process has a verb phrase label.
DATA STORE
1. Data cannot move directly from one data store to another data store, a
process must move data.
2. Data con not move directly from an outside source to a data store, a
process, which receives, must move data from the source and place the
data into data store.
3. A data store has a noun phrase label.
SOURCE OR SINK
The origin or destination of data
1. Data cannot move direly form a source to sink it must be moved by
process
2. A source and or sink has a noun phrase land
DATA FLOW
1. A data flow has only one destination of flow between symbols. It may
flow in both directions between a process and a data store to show a read
before an update. The later is usually indicated however by two separate
arrows since these happen at different type.
2. A join in DFD means that exactly the same data comes from any of two or
more different processes data store or sink to a common location.
3. A data flow cannot go directly back to the same process it leads. There
must be at least one other process that handles the data flow produce some
other data flow returns the original data into the beginning process
4. A data flow to a data store means updates ( delete or change)
5. A data flow from a data store means retrieve or use.
A data flow has a noun phrase label more than one data flow noun phrase can appear on a
single arrow as long as all of the flows on the same arrow move together as one package.
Level 1
Admin Authentication Company Input
Send I/p to bank
Check Input
Allocate input to company
Report
Resource Transfer
Company Details
Company Details
Bank Details
View
User Login Details
LEVEL 2:ADMIN MODULE
Admin Check Authentication
Client
Company
Bank
Transaction
User DetailsClient Details
Company Details
Bank Details
Transaction Details
Fetch
Store
Reports
Valid
Invalidd
Username, password
Store
Store
Store
View
Store
Store
Store
BANK MODULE:
File Transfer
FetchUsername, password
Invalidd
Valid
Store
Store
Store
Bank Director
Check Authentication
Client
Transaction
File Transfer
Loan
Store
Loan DetailsFile Transfer Details
Transaction DetailsClient DetailsBank DetailsReports
Loan Details
File Transfer Details
Bank Details
Transaction Details
Client Details
View
Reports
No
Yes
Yes Virus
No
If file length Not equals
If file length equals
File Transfer
File Transfer
File Exists
Virus File
DAP
Error Page
File Not Found
Virus File
File Transfer Completed
I-FaKTOR Testimony Bureau:
Inbox Compose
DB
Received Messages
Screen Shots:
