Preface

Begin difficult things while they are easy,

do great things when they are small.
The difficult things of the world must have once been easy;
The great things must have once been small ...
A thousand mile journey begins with one step
Laozi, ancient Chinese philosopher
Leading technology
With technology in general, and with computers in particular, you have two options you can
either be a passive recipient of what they have to offer, or you can proactively look to control
them.
All of your life computers and technology will try to tell you what to do (Press Enter to
continue, Are you sure you want to delete this file?). Through a study of IPT you have a chance
to take back control, to tell the technology what to do. By gaining an understanding of how the
various devices work, by building skills in using information systems, by developing
proficiency in problem solving and communication, and through appreciating how computers
affect society, you can reverse this trend. Instead of being directed by, you can learn to lead the
technology.
What is IPT?
Information Processing and Technology (IPT) is an investigation into what makes technology
so significant in our world how it works, how it operates, how we control and direct it, and
how it affects us.
IPT is a unique subject there are few like it. It involves a blend of computer science,
analysing, programming, investigation, problem solving, research, making, thinking, writing,
data manipulation, and an exploration of the practice and philosophy of computing. By
studying IPT you will not only learn more about how computers operate and affect us, but you
will develop valuable skills in thinking, problem solving, collaboration, and communication.
The title IPT is made up of three terms, information, or meaningful facts, processing, the ways
these are developed and handled, and technology, the tools for doing this.
Kevin Savage 2011 Single user licence issued to Mitchell Ingall
Leading Technology 2

The study of IPT is divided into six principal topics:
algorithms step by step problem solving
human-computer interaction (HCI) what makes technology useable
relational information systems how data can be managed and used
social and ethical issues (SEI) ways technology influences our world
software programming how to instruct the computer, and
structured query language (SQL) means for manipulating data.
In addition the study of IPT can also involve two other topics, Intelligent Systems, human-like
computing, and Computer Systems, how the technology operates.
In practice these topics overlap. For example the writing of a computer game may involve
image manipulation, an understanding of the HCI aspects of the player interface, and an
awareness of the possible social effects of using the game.
Our method of working in IPT involves the three aspects or dimensions:
Knowledge and Application learning about technology, and carrying out practical
activities
Analysis and Synthesis examining and determining what is involved, and building or
developing solutions
Evaluation and Communication making supported judgements, and clearly
conveying understandings.
Throughout these dimensions we work, both individually and collaboratively, to solve
problems using the design-develop-evaluate (DDE) model.
The DDE cycle
You may often be put in the position where you are faced with having a sizeable task to
complete. Some people are good at doing this, while others are not.
In IPT we use the design-develop-evaluate cycle to solve problems. Design is planning and
preparation, develop is putting the plan into action, and evaluate is looking back to check how
effective we have been.
We will look at each of the three parts of DDE in turn.
Design
If I had eight hours to chop down a tree, I would spend six hours sharpening
the axe.
Abraham Lincoln, US president
It has been found in the information technology (IT) industry that the more time spent on the
design stages, the less time there has to be spent on the development, testing and possible re-
design of the solution. It is very expensive to alter a solution that is in place if there are
fundamental design flaws, errors that may not show up until the solution and has been
operating for some time.
Design consists of three stages, understand, specify and plan.
Kevin Savage 2011 Single user licence issued to Mitchell Ingall
Preface 3

Firstly you must make sure you understand the problem you are about to tackle. Read the
information given, if necessary carry out some research, discuss issues, make notes, perhaps re-
write the task in your own words. The important point is to make sure you are very clear on
what is required. It is pointless to spend hours producing an elegant solution to a problem if it
has little to do with what was actually required.
The second stage is to form a clear idea of what you have to do to solve this problem. To
achieve this, carefully analyse whatever information is available, and then work out a
specification of how the problem can be solved. Get an idea of what you want to do, and then
determine how you will put it together. The specification can be done on paper, or with
sketches, or as just a mental picture. If you do not have any idea of where you are going, you
will have no idea of how to get there!

The DDE cycle
The final stage of design is to make a plan. The plan will vary with the project undertaken. It
may involve:
identification of tasks to be done, prioritisation and, if in a group, task allocation
a proposed timeline of activities
determination of possible sources or search methods
an outline of ways to proceed and decisions on emphasis
determinations on layout and style, perhaps including sketches or screen designs
preparation of materials to be used.
Depending on the size of the project the plan can be very simple (a sketch and a few notes) to
very complex (proposed timelines, allocated responsibilities, performance parameters, etc.).
Whatever form the plan takes however it is a vital part of the design step.
Without a plan you run the risk of not completing the task the way it should be done, You can
become sidetracked, lose focus, run out of time, get distracted, or become confused. The more
complex the task, the more vital the plan becomes and the more detailed it must be.
The written parts of your planning will form part of the documentation of the task.
Kevin Savage 2011 Single user licence issued to Mitchell Ingall
Leading Technology 4

Develop
Once the design has been worked out, the solution to the task can now be developed. Again
there are stages within this step, draft, refine, and test.
Firstly a draft or rough implementation of the solution can be made. This can then be checked
to see if it meets the specification decided in the design stage. If the draft solution does not
meet requirements, either it will need to be improved, or the design may need to be revised.
When the draft does fulfil task requirements it can be refined in detail, content and layout.
While this step often takes the most time, if the previous phases have been done effectively this
should not be difficult.
Finally the solution should be tested to ensure it works correctly, is user friendly, and user
proof. Again it may be necessary to cycle back to an earlier part of the process to correct flaws.
Records of drafts, refinements, testing, and so on will form part of the documentation of the
project. You can also include evidence or examples of the solution in action.
Evaluate
The evaluation is an important part of completing any task. Its purpose is to use evidence to
make judgements as to the value of what you have done. With effective evaluation you can
learn from the experience and use this to make a better attempt at the next similar project you
undertake. Evaluation should not be simplistic, but be well thought out.
Evaluation takes two forms, ongoing during the task, and a formal evaluation conducted at the
end of the process.
Ongoing evaluation
Evaluation should not be an afterthought but should occur throughout as you face decisions or
make judgements.
During the design and the development phases you will often find you have more than one
possible way of doing something. At times like this you will have to make an evaluation of the
choices you face at each stage. The decisions you make will affect the outcome and involve
making effective judgements.
Part of planning, especially in larger tasks, might also include the determination of criteria by
which you will judge its success or failure. These criteria should be specified early, before the
project is implemented. (If not, it is tempting to accept lower standards as you encounter
difficulties later.) Some of the criteria you might consider could include, reliability, user-
friendliness, efficiency, practicality, effectiveness, relative value, functionality, and so on.
At each stage of the project you should also be making judgements of how the product is
progressing, the effectiveness of decisions you take, and of how you have performed. These
judgements should be recorded so that they can be compiled as part of the final evaluation of
the task upon completion.
Formal evaluation
While evaluation continues throughout your task, when the solution has been developed and
tested it is a good idea to make a final evaluation to look back at what you have achieved.
Kevin Savage 2011 Single user licence issued to Mitchell Ingall
Preface 5

An assessment can be made that includes things like, if the finished project achieved your aims
and objectives, if it met all of the specifications laid out, how effective your decision making
was, and how successfully you worked on each phase of the process of development. The
formal evaluation should look at both the product you have made and the process by which you
made it.
The product is the solution you have come up with. To do this you might ask yourself these
questions:
validation does the final product do what it was supposed to; is it useful?
verification does it agree with your initial design specification?
quality is the product as good as it could be; were there any errors or faults?
consistency is the quality the same throughout?
rating how good is the product; is it easy to use; does it engage the user?
The process is the way you have arrived at the solution. You might ask the following questions:
did you complete all required aspects of the task?
did you stay on task, and did you finish on time?
have you worked efficiently?
what would you do differently if you were to start again?
If you worked as part of a group or team:
how well did the members cooperate?
how well were tasks shared?
was there one particular leader, or was leadership shared?
was there good communication between team members?
was the task affected by the personalities involved?
As well as an evaluation by yourself it is sometimes a good idea to get evaluation from
someone who was not involved in the task. An outsider who looks at what you have done is
less likely to be biased, and can make objective judgements of what has been developed. This
outside assessment can be by your peers.
Both ongoing and formal evaluation will form part of the task documentation.
Documentation
Documentation is the recording of all phases of the designdevelopevaluate cycle. It can
include planning documentation, details of research, sample output, written records, sketches,
log books, screen designs, bibliographies, print outs, planning charts, algorithms, outlines, or
any other record made of what has been done. It will also include the formal evaluation.
Documentation is integral to the application of DDE. Through it the product developed and
process followed can be communicated to anyone who needs to be aware of either.
Kevin Savage 2011 Single user licence issued to Mitchell Ingall
Leading Technology 6

Task development cycles
For major tasks or projects in IPT the DDE cycle is extended into one of the following cycles.
Software Development Cycle
Design
problem identification
solution specification
select and apply appropriate design methods
Develop
design implementation
Evaluate
testing
evaluation of product and process
Documentation
Information System Development Cycle
Design
identification
conceptualisation
formalisation
Develop
implementation
Evaluate
testing
evaluation
Documentation and specification documentation.
Information Literacy Cycle
Design
identify the topic
determine information to find or collect
identify potential sources
Develop
collect relevant information; organise
material to present and prepare draft
Evaluate
reflect on, make judgements or draw
conclusions about information presented
Documentation
Kevin Savage 2011 Single user licence issued to Mitchell Ingall
Preface 7

Conclusion
IPT is valuable subject to apply yourself to. There is much that will not come easily, but then
nothing that is worthwhile ever does. You may find this course demanding and strange at first,
but if you apply yourself by working carefully and conscientiously through the text and
activities in this book you will give yourself every chance of doing well.
I hope that by the time you have finished this book you will appreciate some of the skills
needed to develop the applications, games, web pages, and the information systems we all use.
You may not end up an expert in the processing of technology, but you will have a sound basis
for developing your knowledge of this fascinating and useful area.
Good luck and I hope you enjoy IPT, and that you can learn to lead the technology and not just
be led by it.
Kevin Savage
Toowoomba
30-09-10


Welcome
to IPT
Kevin Savage 2011 Single user licence issued to Mitchell Ingall