Fundamentals of Information Technology

Syllabus
Examinations.

There will be two papers relating to this syllabus, both of which must be passed by all
candidates.

Paper One will examine the breadth of the syllabus by means of short answer and/or
multiple choice questions. The emphasis will be one of demonstrating a recognition
of the fundamental terms and concepts which apply to the disciplinary areas within the
syllabus.

Paper Two will examine the depth of knowledge of the principles related to the
disciplinary areas. Questions will require written answers of short to medium length
and candidates will be expected to demonstrate a knowledge of the principles and
concepts concerned with the examined topics. The depth of knowledge, however, will
not be expected to be as extensive as that required for the specialist optional papers
in the respective areas.

1. Aims

On successful completion of this examination, the candidate should be able to:

• understand the need for and the importance of information in an
organisation;
• understand the need for data integrity and security and the means by which these
may be obtained;
• understand the components which comprise the information technology
infrastructure within an organisation;
• understand the processes involved in problem solving and the methods used for
developing computer-based information systems;
• understand the essential features of the hardware, software, data management
and data communications components of computer-based information systems;
• understand the ACS Code of Ethics as an example of such a code required by a
professional society.

2. Content

2.1. Information systems concepts

2.1.1 Information in an organisation

The need for and importance of information in the decision making process;
the different levels of information required in an organisation; the processes
involved in collecting, recording, processing, retrieving and presenting
data/information; the importance of accuracy and security of data and the
means by which these may be accomplished and enforced.

1
2.1.2 Development of information systems
The different approaches to the development of information systems, including
structured system design, prototyping, systems development life cycle, object
orientation; the user's role in system development; top-down vs bottom-up
design; packaged vs custom-designed systems; centralised vs distributed
systems; interactive vs batch systems.
The roles performed by system users, analysts/designers, software developers
and project managers during system development, implementation, post-
implementation review and subsequent maintenance and enhancement.
The options available for system acquisition, including in-house development,
outsourcing, facilities management.

2.1.3 Data integrity

The need for data control and accuracy; measures available at design and
operation levels; types of data validation checks used (e.g. range and
reasonableness checks, check digits); security and protection of data, including
password techniques and encryption; the implementation of backup and
recovery procedures.

2.1.4 System methodologies

Development methodologies such as structured system analysis and design,
process modelling, data modelling, object modelling; the tools and techniques
used; the objectives and comparative merits of the various approaches to
system development; the need for and type of documentation produced.

2.2. Hardware, system configuration and data communications concepts

2.2.1 Hardware
The concept of number systems and coding systems used by computers.
The functional units comprising a typical computer configuration: input/output,
fixed and removable data storage, internal storage, control and arithmetic/logic
unit. The manipulation of data, program control and execution; the CPU cycle.
The concepts relating to execution speed, data access times, storage
capacities and similar comparative aspects of hardware performance.
The alternatives available for data storage, data input and output, their
operational characteristics and relative advantages and disadvantages.

2.2.2 System configuration

The alternatives available for hardware configuration, including mainframe
architecture, stand-alone workstations, networks, client-server.

2.2.3 System software

The essential system software components of a computer configuration,
including operating systems and utilities; their typical functions including
resource management and user interface; the relative merits of different styles
of user interaction, e.g. command vs graphical.

2
2.2.4 Data communications
Fundamental data communications concepts, including the principles of data
transmission, error prevention, detection and correction, transmission media.
Network concepts such as network types, network topologies and protocols.
Hardware essentials such as multiplexers and modems.
Data communication applications.

2.3. Software

2.3.1 Application software

The generic components of an organisation's application software including
data collection, database (in its widest sense) maintenance, enquiry handling
and report generation; the generic components of business systems, sort, edit,
validate, update.
The sources of application software, including user-developed, custom-written
and off-the-shelf; their relative advantages and disadvantages.
Typical applications within an organisation, e.g. financial, inventory and
personnel management;
The role and functions of commonly available applications such as word
processors, spreadsheets, data managers, presentation and publication
managers.

2.3.2 Software development

The process of software development, including problem definition, design of a
solution, program development, testing procedures and the need for
documentation.
Approaches to software design:
The structured methodology; sequence, selection and iteration.
The tools and techniques available for software design, e.g. pseudocode,
flowcharts, structure diagrams.
The object oriented methodology; classes, objects, encapsulation, inheritance,
polymorphism, reuse.
The variety of programming languages/products available, including procedural
languages, non-procedural or declarative languages, visual programming
languages and object-oriented languages. Their characteristics and relative
advantages/disadvantages.
The translation process: the concept of an assembler, compiler, interpreter, link
editor. The meaning of source program and object programs; compiler
generated diagnostics, compilation and syntax errors; run-time errors.
Program statement types: input, output, assignment statements, arithmetic and
logical operations, control statements.
Structure charts and pseudocode: ability to use structured charts to design
simple programs from a statement of requirements; ability to specify logic in
pseudocode of a simple specification written in narrative or structure chart
format.
Program testing and maintenance: testing vs debugging; test data; code
reviews; structured walkthroughs; interactive debugging; reasons for

3
 maintenance.
Documentation: relationship to the software development life-cycle; technical
and user documentation; internal and external documentation.
The factors affecting software quality, e.g. conformance to specifications, zero
defects, reusability, efficiency of operation, documentation and user support.
Productivity and measurement: CASE tools and application generators;
programmer productivity; development and maintenance considerations;
program efficiency and standards; reusability; software metrics.

2.3.3 Professional responsibility and ethics.

The Australian Computer Society Code of Ethics.
Ownership of software and software piracy.

2.4. Data Management

The fundamental principles relating to the storage and retrieval of data within a
computer-based system, including data structures, data types or classes, the
concept of single and compound keys; generic operations such as creation,
amendment, updating, sorting, extraction or selection, reporting and
presentation.
The elements of file design, including record and field structures, indexes and
generated storage addresses, direct vs sequential/serial access.
Master file management: serial and direct file updating.
The concepts of a database; the different database models and
implementations; the characteristics of these models and their relative
advantages/disadvantages.
The elements of relational database design, including tables, keys; the need for
data normalisation; the role of SQL-like languages in data retrieval and
manipulation.

3. Notes
Candidates will not be expected to be familiar with any particular programming
language, but will be expected to be able to develop simple algorithms in
pseudocode, and discuss the outcomes of procedures expressed in
pseudocode. Candidates will be expected to use the pseudocode format
described in the Appendix to the syllabus for Programming and Software
Technology.

4. Texts

Capron, H.L., (1999). Computers - Tool for an Information Age. 6th edn. Prentice-Hall.

5.References

Alter, S., Information Systems – A Management Perspective, Addison-Wesley.

Date, C. J., An introduction to database systems, Addison-Wesley.
Goldschlager, L. and Lister, A., Computer science: a modern introduction, Prentice-

4
Hall.
Halsal, F., Data communications, computer networks and OSI, Addison-Wesley.
Hawryszkiewycz, I. T., Introduction to systems analysis and design, Prentice-Hall.
Henderson-Sellers, B., A book of object-oriented knowledge, Prentice-Hall.
Juliff, P., Program Design, Prentice-Hall.
Kroenke, D. M., Database processing: Fundamentals, design, implementation,
MacMillan
Pressman R. S., Software engineering: A practitioner's approach, Mcgraw-Hill.
Stallings, W., Business data communications, MacMillan.
Stallings, W., Computer organisation and architecture, MacMillan.
Whitten, J.L., Bentley, L.D. and Barlow, V.M. Systems analysis and design methods,
Irwin.

Australian Computer Society Code of Ethics.

Information Technology industry and professional journals and publications, such as:

Australian Computer Journal

Information Age
IEEE Computer Society publications
Communications of the ACM
Computer World