Foundation Degree IT Project

Methodologies (for reference)

Information systems

Richard Hancock3

We are dealing with computer based information systems that can process data

Information systems in an organisation are about providing facts to its members and clients in order to help it operate effectively

A computer based information system could be considered a formal system meaning that they provide information on a regular basis and in a controlled manner An informal system can be just as valid, for example corridor discussions,

meetings, rumour etc

Examples: Payroll Sales Project planning Conferencing system Decision support Transaction processing

19/04/23

Methodology background

Richard Hancock4

Early computer applications (1960s) were implemented without the use of methodologies

Developers were technically trained, but poor communicators

User requirements were not established Developer experience and rule of thumb was used User requirements change over time, requiring

amendments to systems often resulting in unexpected outcomes

Essentially it was merely an attempt to survive the day

Costs increased and so a solution to manage this process was required

19/04/23

Methodologies

Richard Hancock5

We are dealing with information systems development methodologies NOT project development methodologies (like PRINCE2)

One definition is: “a collection of procedures, techniques, tools and

documentation aids which will help the systems developers in their efforts to implement a new information system” – Avison & Fitzgerald (1998)

Methodologies are based on a philosophical view As a result of this they all have different emphasis

Human emphasis Scientific approach Pragmatic approach Automated approach

19/04/23

Methodology objectives

Richard Hancock6

These could be: To record accurately the requirements for an

information system To provide a systematic method of development

so that progress can be effectively monitored To provide an information system within an

appropriate time limit and at an acceptable cost To produce a system which is well documented

and easy to maintain To provide an indication of any changes which

need to be made as early as possible in the development process

To provide a system that is liked by those people affected by that system

19/04/23

The traditional systems development lifecycle (SDLC)

Richard Hancock7

1. Feasibility study2. System investigation3. Systems analysis4. Systems design5. Implementation6. Testing and maintenance

Also known as the systems development lifecycle or the waterfall model

19/04/23

Feasibility study

Richard Hancock8

A miniature project in of itself! Looks at present system, requirements it is supposed

to meet, problems in meeting those requirements, new requirements and alternative solutions

Essentially it aims to determine if a proposed system is feasible based upon: Legal requirements Organisation and social issues Technical issues Economics

A recommended solution is proposed (with outline functional specification) from alternatives and presented to management for approval

19/04/23

System investigation

Richard Hancock9

Thorough investigation of the application area Functional requirements of existing and new

system Constraints Data types and volume Problems with the current system

Data gathered using: Observation Interviews Questionnaires Sampling Documentation collection

19/04/23

System analysis

Richard Hancock10

Analyse the current system Ask:

Why do problems exist? Why have certain methods been adopted Are there alternative methods

Essentially try to understand all aspects of the current system and determine why it evolved in the way that it did

Eventually indicate how things might be improved with a new system

19/04/23

System design

Richard Hancock11

Analysis leads to the design of the new system

Consideration of: Data capture, inputs and outputs Processes User manuals Security System implementation plans and testing

***

19/04/23

Implementation

Richard Hancock12

Can involve various processes and stages Equipment purchase Software development User training User documentation/manuals Integration into the environment

Could be a complete switch Or run in parallel with old system Integration via phases

Acceptance testing

19/04/23

Testing and maintenance

Richard Hancock13

Occurs when system is fully operational Changes are likely to the system and

expected Systems review to confirm it meets the

requirements originally set out

***

19/04/23

Summary

Richard Hancock14

Information systems methodologies attempt to guide the developer in developing a new information system

They are varied in their emphasis, based upon a philosophical point of view

The traditional systems development lifecycle is seen as one of the root methodologies from which many more have stemmed

***

19/04/23

Resources

Richard Hancock15

SDLC Software development methodology

***

19/04/23

Questions...

19/04/23Richard Hancock16

...are there any?

Richard Hancock17

End!

19/04/23