Lecture 3 - History of ISD and Current practice and problems Flashcards
What do information systems consist of?
Data, People, hardware, software and telecommunications
IS and competetive forces - mention the five forces
Bargaining power of suppliers, bargaining power of buyers, threat of substitute products, potential threat of new entrants.
What is the four essential difficulties in ISD?
Complexity, conformity (overensstemmelse), changeability, invisibility.
(Avison et Fitzgerald, 2006)
Describe the pre-methodology era.
(1950+)
No explicit ISD-method existed.
Developers lacked communication skills.
(Avison et Fitzgerald, 2006)
Describe the early methodolgy era.
1960+
Development of SDLC (software development life cycle)
Waterfall Model
No iterations and no looking back
Describe the methodolgy era.
1970+
Evolution of SDLC led to Merise, SSADM, Yourdon Systems Method.
New approaches/methologies based on different paradigms: strategy, participation, prototyping (incremental), data analysis, etc.
(Avison et Fitzgerald, 2006)
Describe the post-methodology era
2000+
Also called reflecting era.
Methodologies were used in a reflected way, and critique raised againts using methods: productivity, complexity, etc.
(Avison et Fitzgerald, 2006)
Describe the contingency approach.
Is where a structure is presented but stages, phases, tools, techniques, and so on, are expected to be used or not (or used and adapted), depending on the situation => the choices are context dependent (project size, importantsness etc.)
(Avison et Fitzgerald, 2006)
What are some of the main risks when following the Waterfall approach?
Fordi testfasen først ligger til sidst vil mange fejl og mangler først blive opdaget her, hvilket ofte ikke kan løse med mindre justeringer, men vil kræve en omlægning af både systemkrav design ovs., hvilket kan være meget tids- og omkostningskrævende for et projekt.
(Royce 1979)
What are the five steps that Royce (1979) recommends when making system development to minimize the risks of failing? (Looks somehow like a modified waterfall model, that includes small iterations - see article for illustrations)
Step 1: Program design comes first
Step 2: Document the design
Step 3: Do it twice
Step 4: Plan, control, and monitor testing.
Step 5: Involve the customer (has to be committed to the process before the final delivery)
(Royce 1979)
What is the main difference between the Waterfall Model and the Spiral Model?
The Spiral Model is more risk-driven of nature, where the Waterfall Model is more document-driven (Documents are used as a completion criteria for early requirements) (Document driven causes the stages to be in the wrong order.)
(Boehm 1987)
What is the primary advantage of the Spiral Model?
The model has many options consisting of good features of existing software process models (Boehm 1987)
What are the main difficulties of the Spiral Model?
The primary challenges involve matching to contract software, relying on risk-assessment expertise and the need for further elaboration of the spiral model steps. (Boehm 1987)
Why are software process models important?
They provide guidance on the order (phases, increments, prototypes, validation tasks, etc.) in which a project should carry out its major tasks. (Boehm 1987)
Give an example of the risk resolution in the different rounds? (Spiral Model)
a. Surveys
b. Analysis
c. Structured interviews with software developers and managers
d. Benchmarking
e. Analysis of a prototype
(Boehm, 1987)