3.2. Necesidades de orientación de los estudiantes
3.2.2. De orientación académica
The inputs to this system include:
Customer: Customer Name, Customer’s Street, Customer’s City Branch: Branch Name, Branch City, Assets.
Account: Account Number, Account Balance. All are connected by links.
Other inputs are the use of the mouse to point, drag and move over to achieve desired effects, keys on the keyboard. While input is the items fed into the system, output is the outcome of the system manipulations of the inputs.
The design process can be described as a set of iterations of trying out alternative clients.
Based on the requirements, the design will set up a set of initial clients and carry out the simulation. After obtaining the simulation results, the data will be analyzed to check for possible attack and subsequent countermeasures.. This kind of model-simulate-analysis procedure will be iterated many times until the analysis results from modeling and simulation match the requirements or the “best” result are found (Wasson, 2006).
Tables 4.1 and 4.2 specified the input and output specifications for the system.
Input Specifications:
Table 4.1
Field Name Width Data type
Customer Name 40 Text
Customer street 25 Text
Customer City 15 Text
Branch Name 15 Text
Branch City 15 Text
Branch Assets 15 Numeric
Account No 25 Numeric
Account Bal Auto Currency
Type of
Transaction
30 Text
4.6.2 Output Specifications:
Table 4.2
Field Name Width Data Type
Customer Name 40 Text
Customer street 25 Text
Customer City 15 Text
Branch Name 15 Text
Branch City 15 Text
Branch Assets 15 Numeric
Account No 25 Numeric
Account Bal Auto Currency
Type of
Transaction
30 Text
Customer Profession
20 Text
Nature of
business
25 Text
Mobile phone No 15 Numeric
e-mail 25 Text
Sex 8 Numeric
Date of birth Auto Date/Time
Closing Balance Auto Currency
No of log in attempts
3 Numeric
History
Marital Status 15 Text
4.6.3 Input Formats Input Form
Fig 4.8 Sample Input Form Fig 4.5 Sample Input
Figure 4.6a: Sample Input Form
Customer name/Title Customer street Customer city
Branch Name Branch city
Branch State
Code
Account Type Next of kin Account number
Profession Mobile number
Date Of Birth SEX
Nature of Business
Opening balance
e-Mail address
Login counter
Access PWdetails (Login ID
)
IB application formSmart card details
CLOSE OK
Savings Current
Day Month Year MARRIED:
SINGLE: Marital Status
F M
4.6.4 Output Form CUSTOMER NAMEC
FIG 4.7 SAMPLE OUTPUT FORM
Figure 4.6b: Sample Output Form 4.7 DATABASE DESIGN
A network database is considered the most ideal for this work. It consists of a collection of records connected to one another through links. A record is in many respects similar to an entity in the E-R model. Each record is a collection of fields (attributes), each of which contains only one data value. A link is an association between precisely two records. Thus, a link can be viewed as a restricted (binary) form of relationship in the sense of the E-R model.
In the relational model, the data and the relationships among data are represented by a collection of tables. The network model differs from the relational model in that data are represented by collections of records, and relationships among data are represented by links.
Customer Name Customer Street Customer City
Branch Name Branch City Account Number
Branch Code
State
Transaction History Type of Transaction
Account Type Closing Balance
Smart card details Consistency check report
Authorization PW details
SEARCH
Login ID
As an illustration, consider the inputs of customer/account in the database (fig 4.6) representing a customer-account relationship in a banking system.
There are two record types, customer and account. Customer record type is represented thus:
Type customer = record customer-name: string;
customer-street: string;
customer-city: string;
End
The account record type can be defined as:
Type account = record account-number: string;
balance: integer;
End
link
link
Figure 4.7a Network model example
The schema, subschema, and data management language are a few of the key components that make this database model unique. The schema used for this model is conceptual organization of the entire database.
Cedric Emeka Okoye A-102 400
Johnson Nonso Ebuka
A101 500
A201 900
Emmanuel Chuka Ibe A-305 350
4.7.1 Database Structure
The database structure is Network Database which can be defined as:
(1) A database that runs in a network. The DBMS was designed with client/server architecture.
(2)A database that holds addresses of other users in the network.
(3) A database organization method that allows for data relationships in a net-like form. A single data element can point to multiple data elements and can itself be pointed to by other data elements in contrast with relational database and hierarchical database. The advantages of Network Database Model include:
a) Representing a complex data relationship more effectively.
b) Improving database performance.
c) And imposing a database standard.
Network database model also provides Conceptual simplicity, data access flexibility, conformance to standards, handles more relationship types, promote database integrity, and allows for data independence. A representation of Database model using E-R diagram is as shown below in figure 4.7b.
(a) E-R Diagram.