Title: Chapter 1 Computer Technology: Your Need to Know
1Chapter 1Computer Technology Your Need to Know
2Chapter Goals
Chapter 1
Systems Architecture
- Describe the activities of information systems
professionals. - Describe the technical knowledge of computer
hardware and systems software needed to develop
and manage information systems. - Identify additional sources of information for
continuing education in computer hardware and
systems software.
3Technology and Knowledge
Chapter 1
Systems Architecture
- Technical knowledge of computer hardware and
systems software is required to develop
information systems
4Technology and Knowledge
Chapter 1
Systems Architecture
- Every day technical devices do not require
detailed understanding of how they work to be
able to use them. - Although the design of computer systems have
become more complex, computers have become easier
to use.
5Technology and Knowledge
Chapter 1
Systems Architecture
- Since computer systems are easier to use, many
computers are used in business and the home.
6Technology and Knowledge
Chapter 1
Systems Architecture
- If computers have become so easy to use, then
why do you need to know anything about their
inner technology?
7Acquiring and Configuring Technological Devices
Chapter 1
Systems Architecture
- The knowledge required to purchase and configure
technically complex devices is greater than the
knowledge needed to use them
8Acquiring and Configuring Technological Devices
Chapter 1
Systems Architecture
- To purchase a computer, you must
- Know your hardware and software preferences.
- Know your hardware and software requirements.
- Have sufficient knowledge of the available
alternatives. - Understand related technical terms.
9Acquiring and Configuring Technological Devices
Chapter 1
Systems Architecture
- Are you (or will you be) able to meet the
challenge?
10Information System Development
Chapter 1
Systems Architecture
- The steps necessary to develop an information
system are called the System Development Life
Cycle (SDLC)
11Information System Development
Chapter 1
Systems Architecture
12Information System Development
Chapter 1
Systems Architecture
- The systems survey step examines user
information needs, ways in which those needs are
being addressed (if any), and the feasibility of
developing or acquiring an information system to
address those needs.
13Information System Development
Chapter 1
Systems Architecture
- Systems Survey step
- Determines the cost and benefits of alternative
systems. - Takes days or weeks to complete.
- Determines whether the estimated benefit of the
alternative solution justifies continuing the
SDLC.
14Information System Development
Chapter 1
Systems Architecture
- Systems Survey knowledge needed
- Knowledge of hardware and systems software is
required to assess the degree to which user needs
are currently being met, and to estimate the
resources required to address unmet needs.
15Information System Development
Chapter 1
Systems Architecture
- Typical questions asked during the Systems
Survey step for a point of sale system - How much time is required to process a sale?
- Is the existing system easy for a salesperson to
use? - Is sufficient information being gathered for
marketing purposes?
16Information System Development
Chapter 1
Systems Architecture
- Typical questions asked during the Systems
Survey step for a point of sale system (cont.) - Can the existing hardware handle peak sales
volumes (for example, holidays)? - Can the existing system be expanded easily?
- What are the current hardware operating costs?
- Are there cheaper hardware alternatives?
17Information System Development
Chapter 1
Systems Architecture
- The systems analysis step examines the user needs
and the extent to which they are being met. - Called needs analysis or requirements analysis.
18Information System Development
Chapter 1
Systems Architecture
- Systems analysis step
- Takes weeks or months to complete.
- Produces a requirements document.
- Reexamines and answers systems survey questions
in more detail.
19Information System Development
Chapter 1
Systems Architecture
- Typical outcomes
- Detailed descriptions of user interfaces and data
access speed - Detailed data-processing and storage requirements
20Information System Development
Chapter 1
Systems Architecture
- The systems design step determines the exact
configuration of all hardware and software
components.
21Information System Development
Chapter 1
Systems Architecture
- Design tasks during the systems analysis step
- Selecting computer hardware
- Selecting computer software
- Selecting application program development tools
22Information System Development
Chapter 1
Systems Architecture
- Design decisions made based on earlier
decisions - Files or database design
- Program design
- User interface design
- Design of system backup and recovery mechanisms
23Information System Development
Chapter 1
Systems Architecture
24Information System Development
Chapter 1
Systems Architecture
- Technical knowledge needed
- System requirements and the capabilities of that
hardware and operating system - Development tool selection
25Information System Development
Chapter 1
Systems Architecture
- The systems implementation step is constructed
based on the blue prints created during systems
design
26Information System Development
Chapter 1
Systems Architecture
- During the systems implementation step
- Hardware and systems software are acquired,
installed, configured and tested - Application programs and files are developed,
installed and tested - The entire system is tested
27Information System Development
Chapter 1
Systems Architecture
- Technical knowledge needed
- Knowledge of hardware and systems software
- Installation and configuration of hardware and
systems software - Knowledge of how to format storage devices, set
up security systems, install application programs
and establish accounting and auditing systems
28Information System Development
Chapter 1
Systems Architecture
- During the maintenance step, the system is
evaluated for errors that escaped undetected
during installation and testing. - Minor changes are made as maintenance changes.
29Information System Development
Chapter 1
Systems Architecture
- Technical knowledge needed
- Knowledge is needed to classify the proposed
change as minor or major - Knowledge is needed about the hardware and
software components that are affected by the
change
30Information System Development
Chapter 1
Systems Architecture
- If systems evaluation and maintenance
determines that a new system is needed, then a
new SDLC will be initiated.
31Management of Computer Resources
Chapter 1
Systems Architecture
- Knowledge is needed to manage the computer
resources within a large organization. - The manager of a collection of information
systems must contend with a great deal of
technical complexity.
32Management of Computer Resources
Chapter 1
Systems Architecture
- Attention must be paid to two important
technological issues - Compatibility
- Future trends
33Management of Computer Resources
Chapter 1
Systems Architecture
- Compatibility
- The new system must not only operate correctly by
itself, but also operates smoothly with all of
the other systems in the organization.
34Management of Computer Resources
Chapter 1
Systems Architecture
- Future Trends
- The manager must have a broad understanding of
current technology, as well as future technology
trends.
35Roles and Job Titles
Chapter 1
Systems Architecture
- A large number of people can be classified
loosely as computer professionals, and an even
larger number use computers in the workplace,
school or home.
36Roles and Job Titles
Chapter 1
Systems Architecture
- Computer Professional Groups
- Application Development Personnel
- Systems Software Personnel
- Hardware Personnel
- Systems Management Personnel
37Roles and Job Titles
Chapter 1
Systems Architecture
- Application Development Personnel
- Systems Analyst
- Systems Designer
- Application Programmer
38Roles and Job Titles
Chapter 1
Systems Architecture
- A systems analyst primarily is responsible for
conducting surveys, determining feasibility, and
defining and documenting user requirements. - A systems designer primarily is responsible for
procuring hardware and procuring or designing
applications software.
39Roles and Job Titles
Chapter 1
Systems Architecture
- An application programmer primarily is
responsible for software implementation and
testing.
40Roles and Job Titles
Chapter 1
Systems Architecture
- Systems Software Personnel
- Systems programmers are responsible for the
development of systems software such as - Operating systems
- Compilers
- Database management systems
- Network monitors.
41Roles and Job Titles
Chapter 1
Systems Architecture
- Hardware Personnel
- Hardware personnel are responsible for
hardware design, installation, and maintenance.
42Roles and Job Titles
Chapter 1
Systems Architecture
- Systems Management Personnel
- Computer operations manager
- Network administrator
- Database administrator
- Chief Information Officer
43Roles and Job Titles
Chapter 1
Systems Architecture
- A computer operations manager is responsible for
the day-to-day operation of a large
information-processing facility. - The operation can include scheduling, staffing,
security, system backups, maintenance and
upgrades.
44Roles and Job Titles
Chapter 1
Systems Architecture
- A network administrator is responsible for the
network infrastructure and the management of a
local area network.
45Roles and Job Titles
Chapter 1
Systems Architecture
- A database administrator is responsible for the
management and access to collections of data
stored in databases.
46Roles and Job Titles
Chapter 1
Systems Architecture
- A Chief Information Officer (CIO) is responsible
for the management of the personnel and computer
software and hardware.
47Roles and Job Titles
Chapter 1
Systems Architecture
- A Chief Information Officer is for the management
of the database administrator, network
administrator and computer operations manager. - This position is also responsible for the
computer, networks and software owned and
operated by an organization.
48Computer Technology Information Sources
Chapter 1
Systems Architecture
- Sources to keep you up-to-date in the field
- Periodical literature
- Technology-oriented Web sites
- Vendor and Manufacturer Web sites
- Professional Societies
49Computer Technology Information Sources
Chapter 1
Systems Architecture
- Periodical Literature
- ACM Computing Surveys
- Computerworld
- Communications of the ACM
- Computer
-
50Computer Technology Information Sources
Chapter 1
Systems Architecture
51Computer Technology Information Sources
Chapter 1
Systems Architecture
- Technology-Oriented Web Sites
- There are many Web sites that are devoted to
serving the information needs of computer
professionals.
52Computer Technology Information Sources
Chapter 1
Systems Architecture
53Computer Technology Information Sources
Chapter 1
Systems Architecture
- Vendor and Manufacturer Web Sites
- Vendor Web Pages are oriented to sales, but
they usually contain detailed information on
products either directly or as links to
manufacturer Web sites.
54Computer Technology Information Sources
Chapter 1
Systems Architecture
55Professional Societies
Chapter 1
Systems Architecture
- Association for Information Technology
Professionals (AITP) - Association for Computing Machinery (ACM)
- Institute for Electrical and Electronics
Engineers (IEEE) Computer Society
56Summary
Chapter 1
Systems Architecture
- Technical knowledge of computer hardware and
systems software is required to develop
information systems. - Technical knowledge also is required to manage
the computer resources of an organization. - Technical knowledge constantly must be updated
due to changes in hardware and software
technology.
57Summary
Chapter 1
Systems Architecture
- Information about computer hardware and software
is readily available on the World Wide Web. - An understanding of computer technology is
necessary. - Computer knowledge can be updated through reading
periodicals, using Web sites and joining
professional societies.