gimcada@gmail.com
for ATIB BUSINESS AND COMPUTER COLLEGE
Data Security
Adding Records
Records are added to a file when additional data is required to make it current. If
a school admits a new student, for example, the admissions department would
need to add a record containing the data for the new student to the school’s
student file the process required to add this record to the file includes the
following steps: 1. An admission counselor in the admission department starts
a student maintenance program that gives him or her access to the database.
The admission counselor then clicks the New Record button, which begin a
process of adding a record to the student file. 2. The admissions counselor
assigns a student ID to the new student. This number serves as the primary key
for the student record.
3. The counselor enters data to fill in the fields in the student record. (For
purposes of this example, the data entered is kept to a minimum)
4. Once the admissions counselor verifies the data on the screen, he or she
clicks the New Record button to add the new student record to the student file.
The program that manages the disk determines where to write the record on the
disk. In some cases, the new record is written between existing records in the
file. In other cases, it writes the new record to the end of the file.
Changing Records
Generally, you change a record in a file for two primary reasons: (1) to
correct inaccurate data or (2) to update older data with newer data.
As an example of the first type of change, assume that an
administrative assistant entered a new student’s name as Anita Jonson instead
of Anita Johnson. When the student receives her schedule for classes, she
notices the error, contacts the registration department, and requests that the
department correct the spelling of her name.
To do, an administrative assistant in the registration department retrieves the
record and changes the last name field from Jonson to Johnson. The change
thus corrects the inaccurate data and replaces it with accurate data.
A more common reason to change a record is to update older data with
newer data. Suppose, for example, that Anita Johnson moves from 423 Western
Avenue to 45 Francis Boulevard. The process required to change the address
and update Anita Johnson record includes the following steps:
1 The registration administrative assistant starts the student
maintenance program
2 The registration administrative assistant enters Anita Johnson’s
Student ID of 998-69-2286 to display Anita Johnson record on the screen. If the
assistant did not have the Student ID available, he or she could enter the
student’s last name, which would retrieve all students with the same last name.
3 The program displays data about Anita Johnson. By reviewing this
data on the screen, the assistant can confirm that the correct Student ID was
entered
4 the administrative assistant enters the new street address of 45
Francis Boulevard.
5 Once the administrative assistant verifies the data on the screen,
she clicks the save button to change the record in the Student file. The program
changes the record on the disk.
Deleting Records
When a record no longer is needed, it deleted from a file. In this example, a
student name Brandon Cloak has requested a transfer to another school. The
process required to delete a record from a file includes the following steps:
1 The registration administrative assistance starts the Student
Maintenance program.
2 The assistance enters Brandon Cloak’s Student ID of 997-23-1928
to the display his record on the screen.
3 The program displays Brandon Cloaks name and personal data on
the screen.
4 Once the assistant verifies that this is the record to be deleted, he
or she clicks the Delete Record button to delete the record from the
Student file. The actual processing that occurs to delete a record
from the file depends on the application. Sometime, the record is
removed from the file immediately. Other times, as in this example,
the record is not removed from the file. Instead, the record is
flagged, or marked, in some manner so the program will not
process it again. In this case, an asterisks (*) is placed at the
beginning of the record.
Although the record still physically is stored on the disk, it effectively is deleted
because the program will not retrieve it for processing again. Flagged records
commonly are used in applications where inactive data must be maintained for
some period. A bank for example might flag closed account and remove them
after one year. Periodically, you should run a utility program that removes flagged
records and reorganize current records. Deleting unneeded records reduces the
size of file and creates additional storage space.
Data validation
Validation is the process of comparing the data to a set of rules or values to
determine if the data is accurate. Many programs perform a validity check that
analyzes entered data to help ensure that the data is current and accurate. For
instance, when an assistant adds or changes data in a record, the database
management system performs a validity test to check the entered data.
A range check is an example of a validity check. For example, if you were
entering high school grade point averages, you would expect values in the range
of 0.0 to 4.0. A value of -10 or 85 clearly is outside of the valid range. If the
entered data does not pass a validity check, the computer usually display an
error message and asks you to re-enter the data. Validity check, also called
validation rules, minimize data entry errors and thus enhance the integrity of the
data before the data is stored.
Various types of validity checks include alphabetic checks, numeric checks,
completeness check, range checks, consistency checks and check digit.
ALPHABETIC/NUMERIC CHECKS
An alphabetic check ensures that only alphabetic data is entered into an
alphabetic field and a numeric check ensures that only numeric data is entered
into a numeric field. For example, data in a city field should contain only
alphabetic characters and data in a HS GPA (grade point average) field should
contain only numbers.
COMPLETENESS CHECK
A completeness check verifies that all required data is present. In many
application programs, you can not leave the last name field blank. A
completeness check on this field ensures data exists in it.
RANGE CHECK
A range check determines whether a number is within a specified range. When
data in the HS GPA field must be between 0.0 and 4.0, any number outside this
range is invalid.
CONSISTENCY CHECK
A consistency check test the data entered in two or more field to determine
whether a known relationship between the fields is reasonable. For example, a
High School Graduation Date can not occur before a Birthdate.
CHECK DIGIT
A check digit verifies the accuracy of a primary key. Bank account numbers,
credit card number, an identification number often include a check digit. A check
digit is a number(s) or character(s) that appended to or inserted into a primary
key value.
The value of a check digit is determined by applying a formula to the numbers in
the primary key. For example, if the primary key is 4359, you could do the
following:
(1)Multiply every other digit beginning with rightmost digit by two and then add
together the product and the even digit (4+6+5+1+8=24); (2) subtract the result
from the next highest number ending in zero to generate the check digit (30-
24=6). The primary key then would be 43596 (the primary key value, 4359, with
the check digit, 6, appended).
When the data entry clack enters the primary key, 43596, the program applies
the formula to the fist four digit of the primary key to test if its check digit is valid.
If the computed check digit is the same as the entered check digit (6, in this
case), the program assumes the entered primary key is valid. If the program
compute any other number as the check digit, it displays an error message.
Data dictionary
A data dictionary stores data about each file in the database and each
field within those files. For each file, a data dictionary stores data including the
file name, description, and the files relationship to other file, For each field, a data
dictionary stores data including the field name, field size, description, type of data
(e.g., text, numeric, or date/time), default value, validation rule, and the field
relationship to other field,.
A DBMS uses the data dictionary to perform validation check and maintain
the integrity of the data. When you enter data, the data dictionary verifies that the
entered data matches the field data type. The HS graduation data field, for
example, must contain a number. A data dictionary also allows you to specify a
default value for certain field. A default value is a value that the DBMS
automatically display in a field. Fr example, if most student that attend a school
live in Indiana. Then the DBMS could display a default value minimize the
possibility of errors, because commonly used data items are entered for you.
Usually, you can override a default value if it does not apply for a certain record.
For example, you can change the value, IN, to MI if you need to add a student
that lives in Michigan.
.A multimedia databases that store images, audio clips, and video clips. A
geographic information system (GIS) database, for example, stores map (Figure
10-25); a voice mail system stores audio messages; and a television broadcast
database stores audio and video clips.
Feasibility Assessment
Feasibility is a measure of hoe suitable the development of a system
will be to the organization. A project determined feasible at one point
might become infeasible at a later point in life cycle, thus systems
analysts reassess feasibility frequently during the SDLC.
System analysts use four criteria to test feasibility of a project:
operational feasibility, schedule feasibility, technical feasibility, and
economic feasibility. Operational feasibility measures how well the
proposed information system will work in the organization. In other
words, operational feasibility addresses these questions; will the user
like the new system? Will they use it? Will it meet their requirements?
Will it cause any changes to their environment?
Schedule feasibility measures whether the established deadlines for
the project are reasonable. If a deadline is not reasonable, a new
schedule might be developed. If a deadline is mandatory and can not
be extended, then the scope of the project might be reduced so the
mandatory deadline can be met.
Technical feasibility measures whether the organization has or can
obtain the hardware, software, networks and people needed to
deliver and then support the proposed information system. For most
system projects, the technology exists; the challenge is obtaining
fund to pay for such resources, which is address in economic
feasibility.
Economic feasibility, also called cost/benefit feasibility, measures
whether the lifetime benefits of the proposed information system will
exceed its lifetime costs. Many financial techniques, such as return
on investment and payback analysis, are used to perform this
cost/benefit analysis. Often, the system analyst is unfamiliar with
these financial techniques so he or she requests the assistance of a
financial analyst to access economic feasibility.
Documentation
During the entire system development life cycle, project team
members produce much documentation. Documentation is the
compilation and summarization of data and information; it includes
reports, diagrams, programs, or any other deliverable generated
during the SDLC. The entire collection of documentation for a single
project is stored in a project notebook. The project notebook might
be a single one, such as a large three ring binder, or it may be more
sophisticated such as automated project notebook that can be
created and stored using a computerized analysis and design
software package, a project dictionary or repository.
Well-written, thorough documentation makes easier for everyone
involved to understand all aspect of the life cycle, from economic
decisions to system features to security considerations.
Documentation should be an ongoing part of the system development
life cycle. Too often, documentation is put off because project team
members consider it an unimportant or unproductive part of the
system development. In this case, documentation is pushed to the
end of life cycle or not done at all. Without complete and accurate
documentation, users and information system personnel may not
know how to use, operate or support the system. Having quality
documentation also makes it easier to modify the system to meet
changing information requirements.
Data Information Gathering Techniques
Throughout the SDLC, the project team gathers data and information.
System developers need accurate and timely data and information for
many reasons, such as to keep a project on schedule, to access
feasibility, and to ensure the system is meeting requirements. Analyst
and other system developer use several techniques during the
system development life cycle to gather data and information:
reviewing system documentation, observing, sending questionnaires,
interviewing, conducting JAD sessions, and researching.
Reviewing current system documentation
By reviewing system documentation such as a company’s
organization chart, memos, and meeting minutes, you learn the
history of a project and aspect of the business such as its operation,
weaknesses, and strengths.
Observing, Observing an employee or machine can help you
understand exactly how a system functions or task is performed.
Sending questionnaires, To obtain data and information from a
large number of people, you could send questionnaires
Interview, the interview is the most important data and information
gathering techniques because it enables you to clarify responses and
probe from user face to face. An interview can be unstructured or
structured. An unstructured interview relies on the interviewee (the
user) to direct the conversation based on general subject. In a
structured interview, the interviewer (the system analyst) directs the
conversation by following a specific set of topics and asking
predefined questions. Structured interviews tend to be more
successful for the system analyst.
Conducting JAD sessions, As an alternative to the one-on-one
interview, some companies use joint-application design sessions. A
joint-application design (JAD) session is a lengthy, structured,
group work session where all involved in the SDLC, including users
and information system personnel; discuss an aspect of the project.
The goal of the JAD session is to obtain group agreement on an
issue, such as problems associated with an existing system or
information requirements of a new system.
Researching, Computer magazines, trade journals, reference books,
and the world wide web are excellence sources of information. These
resources can provide you information such as the latest hardware,
software, and networking products; and explanations of new
processes and procedures.
WHAT INTIATES THE SYSTEM DEVELOPMENT LIFE CYCLE?
A user may request a new or modified information for variety of
reasons, some external and some internal. An external reason would
be that management or some other governing body mandate that you
make a change to a system. For example, a nation wide bank might
require all offices to use the same e-mail software. Competition is
another external reason for system development. For example, once
one bank offers internet access to account information, others will
have to allow suit, or run the risk of losing customers.
One internal reason for changing an information system is to improve
or enhance it. For example, if a school wants to provide students with
the ability to register for classes via the telephone, the school would
have to modify the registration system to include this enhancement.
The most obvious internal reason for changing an information system
is to correct a problem. For example, the stock-on-hand listed on a
report may not match the actual stock-on-hand in the storehouse.
The initial request for a new or modified information system may be
communicated verbally or written as a memo or E-mail message but
eventually should be written on a standard form. This form called a
request for system service or project request becomes the first
item of documentation in the project notebook. It is important that this
request be completed so that all requests are organized in a similar
format for the first phase of the system development life cycle:
planning.
APPLICATION LAYER
• Is the OSI layer that is closest to the
user; it provides network services to
the user’s applications.
– File transfer
– Electronic mail
– Terminal access
– Word processing
– Intended communication partners
PRESENTATION
Ensures that the information that the
application layer of one system sends
out is readable by the application layer
of another system.
– Format of data
– Data structure
– Data conversion
– Data compression
– Data encryption
SESSION
• Establishes, manages, and terminates
sessions between two communicating
hosts.
– Sessions
– Dialog
– Conversations
– Data exchange
TRANSPORT
• Provides reliable, transparent transfer
of data over networks.
– Segments, data stream, datagram
– Connection oriented and
connectionless
– End-to-end flow control
– Error detection and recovery
– Segmentation & reassembly
NETWORK
• Provides connectivity and path
selection between two host
systems that may be located on
geographically separated
networks.
– Packets
– Virtual circuits
– Route, routing table, routing
protocol
– Logical address
– Fragmentation
DATA LINK
PHYSICAL
• Transmission of an unstructured
bit stream over a physical link
between end systems.
– Electrical, mechanical,
procedural and functional
specifications
– Physical data rate
– Distances
– Physical connector
INFORMATION
SYSTEMS AND
TECHNOLOGY
Topics discussed would include:
Information Systems
Internet and E-Business
IT Trends
What is Information Technology?
Information Technology is the hardware, software and telecommunications used interchangeably.
These technologies provide the means to transmit, store and retrieve data, voice and video to
anyplace in the world in real time. Information Systems is the collection of hardware, software,
data, people and procedures that are designed to generate information that supports the day-to-
day, operations. Information Systems are generally classified into the following categories:
Transaction Processing
Systems (TPS)
TPS is an information system that capture and process data generated during the dayto-
day transactions of an organization. Example: Deposits, payments, orders or reservations.
Decision Support Systems (DSS)
DSS is an information system designed to help the
user reach a decision when a decision making situation arises. DSS uses data from internal /
External sources.
Management Information
Systems (MIS) is an information system that generates accurate, timely and organized
information so that managers can make decisions, solve problems, supervise activities and track
progress. However, employees are wired into the systems and technology is pushed downwards
and becomes widely accessible.
E-Business
The Internet provided a link to the customer and company by means of E-Business.
E-Business provides customers with worldwide and continuous access to the
global markets.
Common Benefits of E-Business
Speedy Communications
Reduced business cost (travel, marketing, location)
24 Hour access
Major advantages of EBusiness to an organization
Reach new markets
Receive electronic orders
Provide after-sales service
Order and pay for business supplies
Monitor competitors activities
Undertake market research
Network with allied businesses
Components of E-Business
To effectively and efficiently manage an EBusiness,
organizations introduced the following systems:
Enterprise Resource Planning (ERP)
Customer Relationship Management (CRM)
Knowledge Management (KM)
Enterprise Resource Planning (ERP)
Enterprise Resource Planning is a major factor in EBusiness.
Enterprise Resource Planning (ERP) Systems provide strategic planning capabilities, even to the
smallest of organizations. It is a comprehensive tool for integrating
accounting, strategic planning, sales order management, quality control, manufacturing,
logistics and warehousing.
Enterprise Resource Planning (ERP) Enterprise resource planning as a term, derives from
material resource planning. ERP are management information systems that integrate and
automate many of the business practices associated with the operations or production aspects of
a company.
Enterprise Resource Planning (ERP)
These typically include manufacturing, logistics, distribution, inventory, shipping,
invoicing and accounting. ERP software can aid in the control of
many business activities, like sales, deliveries, billing, production, inventory
management, and Human Resource Management.
Advantages of ERP
The benefits from enterprise resource planning
are claimed to include:
lower inventory carrying costs
lower ordering costs
lower production costs
Disadvantages of ERP
The limitations and pitfalls of the enterprise resource planning are claimed to be:
Systems can be very expensive to install and
maintain
Difficult to use
A problem in one department or at one of the
partners will affect all the other participants
They are often called back office systems indicating that customers and
the general public are not directly involved. This is contrasted with front
office systems like Customer Relationship Management (CRM)
systems that deal directly with the customer.
KM Issues
Getting Employees on Board – companies ignore the people and cultural issues
KM Requires Ongoing Maintenance - at any given time changes occur, as do the skills of
Employees
Dealing with a Data Deluge – information overload
Management Implications of IT
As the technological environment grows, managers are now provided with greater
returns. These include, a better connection with employees, the environment, and each
other.
Implications of IT
Increased Efficiency
Empowered Employees
Information Overload
Enhanced Collaboration
Increased Productivity
New information technology offers significant promise for speeding up the work
process, cutting costs and increasing efficiency. Increased Productivity
An example of this is at IBM they helped reduce the number of call centre employees
and saved $750 million in one year alone! Companies just like IBM are slashing costs
and wiring deeper discounts from suppliers. Sweeping away administrative paperwork
and automating mundane tasks is yet another advantage of new technology.
Empowered Employees
Lower-level employees are increasingly challenged with more information and are
expected to make decisions previously made by supervisors. Nurses, janitors, truck
drivers, utility repair workers, and warehouse staffers all need easy access to information
that would better enable them to complete their tasks to the best of their abilities.
Empowered Employees
These changes support the objectives of knowledge management by enabling decisions to be
made by the employees that are in the best position to do so and in the end see the results of
their work. An example is that of the U.S. Army, they began to use new information technology
that relays information about battle fields conditions, the latest intelligence on the enemy down to
the troops. Armed with better data and trained to see patterns in the barrage of
information, lieutenants in the field will be able to decipher better how to launch their attacks.
Information Overload One problem associated with the advances of technology, the company can
become a quagmire of information, which means that it can find itself in an extremely dangerous
situation and will find great difficulty in finding their way out of that situation. Employees
can become vastly overwhelmed with information and are likely not able to sort the
valuable from the useless. More than ever, the ability to produce data and information is
outstripping employees' ability to process it. One British psychologist claims that
this may cause a mental disorder in employees known as Fatigue Syndrome. Thankfully,
managers have been able to alleviate the problem by ensuring that suppliers of information
technology and CIO work hand in hand with employees to identify the kinds of data and
information they really need . Secondly, top executives set limits by focusing on the organisation
key strategies and on the critical questions that must be answered. Enhanced Collaboration
Information technology undoubtedly has brought about collaboration within the work
environment, customers, suppliers and partners. In businesses, one of the most
effective uses of information technology for collaboration has been in the area of
product development such as division of labour.
IT Trends
As the world evolved and is faced with new challenges and the endless data, man saw
the need to transform his environment to meet his ever demanding workforce.
Many inventions were created to assist man in this fast paced world. Some of which would
be discussed here. Some of the modern trends are as follows:
Wireless Internet
VoIP – Voice Over Internet Protocol
Blogs and Wikis
Weblog
According to Andy Warhol’s prediction that, in the future, everyone will be famous
for 15 minutes. Weblogs also known as Blogs, has enabled an individual to publish a daily
commentary or idea electronically. Some view blogs as an electronic version of word-of-mouth
Weblogs (or Blogs) Blogs enabled communication at all levels, where in times past an individual
could not air their opinions on a Website unless it was spam. In more recent times, management
has embraced to the ideas of blogs as it provides marketing information and is opening lines of
communication to the corporate world.
Blogs and Wiki’s Unlike blogs, wiki allows the user’s not just a forum to air their views but visitors
also can edit the website or add content. Wiki basically is a web-enabled, integrated
system based on the principle that any user can obtain full read/write access to all or most
pages in the Wiki. Wiki For example, to create a hyperlink to another page within a Wiki, the user
need only type the page name as a compound without spaces (eg. WelcomeToWiki).
This system is widely gaining users within large and complex organization, but some
are available to the public.