The document discusses the concepts of projects and project management. It defines a project as a sequence of connected activities that must be completed by a specific time, within budget, and according to specifications to achieve a particular goal. Project management is then defined as the principles and tools used to define, plan, execute, control, and complete a project. The document emphasizes that project management is important as it helps to organize one's approach, generate credible schedules, track progress, control the project, identify issues early, and save both time and money.

1. ITGS AKAM 2015
What is a Project
 It is a sequence of unique,
complex, and connected activities
having one goal or purpose and
that must be completed by a
specific time, within budget, and
according to specification.

2. ITGS AKAM 2015
Project Management
 Project Management is a set of
principles and tools for defining,
planning, and executing,
controlling, and completing a
project.

3. ITGS AKAM 2015
Why is this important?
 Organizes your approach
 Generate a credible schedule
 Track progress and control your
project
 Identify where to focus your efforts
 Identify problems early-before there
are crises
 Saves you TIME (and MONEY)

4. ITGS AKAM 2015
Theoretical fundamentals
In every project there should be a client,
end-user and developer
 Client: Is the person or company
requesting for the development of the
product to make work easier replacing the
old system
 End user: Is the person who uses the
information system directly or uses the
information produced by the system
 Developer: is the systems analyst who will
evaluate the existing system, design the
new one, develop it, and evaluate it

5. ITGS AKAM 2015
 Data collection techniques for content
and product design, citing of sources.
Document review
Interview
Questionnaire
Observation

6. ITGS AKAM 2015
 Role of testing and processes used
Final products can be tested using
 Normal Data e.g Age 0-130
 Invalid Data e.g Age -15
 Extreme Data e.g Age 167
 Testing usually occurs before a system is
delivered to the client after 'live data' has
been used
 If the system were to fail the testing phase,
the analyst would have to re-research, re-
analyse and re-design the system.

7. ITGS AKAM 2015
 Product development and technical documentation.
Two documentation can be produced
 User Documentation: Is written to help the user of
the new system work with the new system and how
to fix any problems.
 Technical Documentation: Is written to help other
system analyst who at a later point in time might be
hired to update the system. This may include
hardware, software, data structures, expected
inputs, data validation/verification methods, and
processing details.
 End-user training: Once a system has been
completed, the system analyst should develop a
simple training manual.

8. ITGS AKAM 2015
The product development life
cycle (PDLC)
 Investigation of existing system (s)
 Feasibility study
 Requirements specification
 Project schedule
 Product design
 Product development and technical
documentation
 Client and end-user evaluation

9. Investigation of Existing System
ITGS AKAM 2015
•There are four main ways a system analyst
can use to investigate existing systems:
•Reading existing documentation
•Interview existing users
•Questionnaires
•Watching the existing software in use

10. Feasibility Study
ITGS AKAM 2015
A feasibility study encapsulates various topics which
discuss whether or not it is possible to create the
new system.
The system analyst usually discusses if the
proposed system is economically viable, if the
technology exists to create the new system, and
time it will take to plan, design and manufacture the
new system.

11. Requirements Specification
ITGS AKAM 2015
The requirements specification is a document
produced by the system analyst which is created
after all the primary and secondary data have been
recorded and analysed.
The requirements specification specifies what the
new systems capability and limitations should be,
and is used to evaluate whether or not the new
system is deemed a success or a failure.

12. Project Schedule
ITGS AKAM 2015
As the name suggests project schedule is
the time frame, drawn up by the systems
analyst, in which he will have to complete the
new system.

13. Product design
ITGS AKAM 2015
When designing the new system, the system analyst needs to
decide on the method of input used in the new system.
• Manually: Paper forms, or directly inputting data into an on-
screen form.
• Automatically: Using a bar-code scanner or a card scanner.
After which, the system analyst needs to draw up some
prototypes of the input forms and present it to his client, which
will then accept the prototype as it is or ask the systems
analyst to make any changes the client deems necessary.
After the input form has been created, the systems analyst
then needs to create the system itself. The system should
include data validation and verification methods, and the
output methods, (on-screen or printed).

14. Product Development and
Documentation
ITGS AKAM 2015
Product is developed and two user documents
produced:
• User Documentation: User documentation is written
to help the user of the new system work with the new
system and how to fix any problems.
• Technical Documentation: Technical
documentation is written to help other system analyst
who at a later point in time might be hired to update
the system.

15. Client and end user evaluation
ITGS AKAM 2015
The end-user evaluation consists of evaluating how efficient,
how easy to use and if the system is appropriate for the
business and if it meets the standards. By
• Checking against the requirements specification to check
if the system does everything it was set out to do in the
beginning.
• Checking the users' response. Is the system easy to use?
Does it make work easier? Can any improvements be
made?
The evaluation can be made through the use of
questionnaires, interviews and by observing the users in
action. The data can then be analysed and evaluated to help
in the improvement of the system.

16. ITGS AKAM 2015
Criterion A: Initial investigation and initial
consultation with client
The key questions in this stage;
 Who is your client?
 What is the present situation?
 What are the inadequacies of the present
situation?
The above is obtained in a written record of
the interview, a sound file, a video, or an
exchange of emails supported by a
questionnaire.

17. ITGS AKAM 2015
The investigation will have the following
important independent sections
a) Interview question and responses (not
graded)
b) Interview Summary (not graded)
c) Criterion A: Initial investigation (Appro.
250 words and graded)
Criterion A is built from a) and b)

18. ITGS AKAM 2015
Interview Questions Activity
Interview questions should be open ended
 Each student to write down any two
interview questions that you have or will
use with their clients

19. ITGS AKAM 2015
Interview Summary
After the interview response have been written
the a interview summary should be written
Activity
 Use the handout provided to write down some
questions that you think were used to develop
the interview summary.

20. ITGS AKAM 2015
Compare the Questions
 What problem (s) does do you face in
your position as Head of ICT?
 Do you know of any examples of
students breaking the rules that had
serious consequences?
 How could an IT solution solve the
problem?
 Do you have any ideas ?

21. ITGS AKAM 2015
Criterion A: Initial Investigation
Read the sample initial investigation posted
Use your some of your interview responses
to draft the initial investigation in pairs.