8/6/2007
1
If ti S t
I
n
f
orma
ti
on
S
ys
t
ems
Engineering
Development approaches –
an overview
It’s all about cooking!
Following a method is analogous to a recipe
book!
• A development method is like a recipe,
g
ivin
g
g
uidelines
ggg
• You can follow the recipe and produce a
meal just like a top chef
– Alternatively, you can follow the recipe and
produce something inedible (even by the
dog)!
Where we’ve got to….
• Development techniques have changed
rapidly over the last 15 years
• The approach to systems development still
continues to evolve as we utilise new
technology and software development
approaches
– Development approaches for web-based
projects are poor
– Many systems developed using system
building tools
There is some agreement
• All software developers agree that in the end the
important issue is not so much about which
methodology you use, as having some kind of
framework within which to structure your project.
• Today’s developers have a much more realistic
view: you need to adapt your recipe to the
ingredients you have and to the preferences of
the consumers
Also agreement on what a
methodology is all about..
As we said in the previous lecture:
• Should provide a framework for evaluating
the problem the project is intended to
addres
s
• Should provide a roadmap for the project
ensuring that no important stages are left
out and everything is proceeding to plan
• Provides tools and techniques that enable
us to represent (model) different aspects
of the system
What development methods are
out there? (1)
• From Avison & Fitzgerald (2006)
– 1st publication of book in 1988 described area of I.S.
development methodologies as ‘a jungle’
– 3rd edition not much had changed still ‘a methodology
jl’
j
ung
l
e
’
.
• Estimated in 1995 that over 1,000 brand name
methodologies existed
• Many of these were the same but differentiated for marketing
purposes
