systems analysis & design methods

Systems Analysis and Design 1

Systems Analysis & Design Systems Analysis & Design MethodsMethods

Budhi BuscasEdward Savage Bradley Stockton Ridwan Syafei


“The computer is a moron.”Peter Ferdinand Drucker (November 19, 1909–November 11, 2005)

“People think computers will keep them from making mistakes. They're wrong.

With computers you make mistakes faster.” Adam Osborne (March 6, 1939 – March 18, 2003)

see an example here…

http://www.youtube.com/watch?v=zvWo-ng8pvg&mode=related&search=


OverviewOverviewPresent a hypothetical projectPresent a hypothetical project

Review applicable principles of IT Project Review applicable principles of IT Project management from class discussionsmanagement from class discussions

Discuss general principles of systems analysis Discuss general principles of systems analysis and designand design

Review “waterfall” and “iterative” approaches Review “waterfall” and “iterative” approaches to project developmentto project development

Apply these approaches to the hypothetical Apply these approaches to the hypothetical projectproject

IntroductionIntroduction


Online Advisory ModuleCreate an online, personalized advising systemSystem Functions

Track progress and classesCreate hypothetical personalized schedules based on historical semester offeringsAnalyze student progress to anticipate future class needs based on majorsProvide customized information on alternative pathwaysTrack feedback on quality of instruction and content.

GoalsImprove student graduation rateOptimize class sizeMinimize schedule conflictsReduce size of advisory staffReduce cost

Hypothetical IT ProjectHypothetical IT Project


As a manager:As a manager:How should you proceed and what are How should you proceed and what are the factors that impact on the the factors that impact on the development of this project?development of this project?



Prior Discussion in ClassPrior Discussion in ClassDeterminants of Success/Failure of IT Determinants of Success/Failure of IT ProjectsProjects

Cost of IT ProjectsCost of IT Projects

Principles of Outsourcing for IT ProjectsPrinciples of Outsourcing for IT Projects




Lecture, Lacity, MC: Management of IT-EnabledBusiness Projects, presented 2/28/07Determinants of Success/Failure Determinants of Success/Failure

of IT Projectsof IT Projects


Cost of IT Projects “Denver Airport -- Baggage Handling System”

“Expectations:$175.6 million contract with BAE Automated Systems to develop the system18 month schedule to complete, April 22 1992 to Oct 1993”

“Outcome: Cancelled after horrible test in April 1994, after spending over $2 billion”

As a manager approaching development projects - Where did this fail?

Planning phase?Design phase?Implementation phase?

What development methodology was used?


Keil, M., and Montealegre, R., "Cutting Your Losses: Extricating Your Organization When A Big Project Goes Awry," Sloan Management Review, Vol. 41, 3, 2000, pp. 55-68.



Lecture, Lacity, MC: Management of IT-EnabledBusiness Projects, presented 2/28/07

As a manager, what development methodology should you choose?

Determinants of Determinants of Success/Failure of Success/Failure of IS ProjectsIS Projects



Governance and Decision Domains

Lecture, Lacity, MC: Nature of Information Technology Within Organizations, presented 1/31/07

Management Principles Management Principles for IS Projectsfor IS Projects


How are Information Systems How are Information Systems developeddeveloped

General PrinciplesGeneral Principles

Development techniquesDevelopment techniques

Advantages and disadvantages for Advantages and disadvantages for different methodologies.different methodologies.



GeneralMethodology on Information systems development.“Waterfall Techniques” -- Each step of the process must be completed in sequence

Structured Systems Analysis and Design Methods (SSADM)

“Iterative” or “incremental” – develop systems in smaller steps with repeated iterations utilizing the information and knowledge gained from the first iteration

Rapid Application Development Methods (RAD)

Example: Hypothetical development project


Dennis A, Wixom BH, Roth RM. “Systems Analysis and Design” 3rd ed. Wiley, 2005, pp 12-13.


Information Systems Development (ISD):Information Systems Development (ISD):

Definition:Definition:

Creating “…value-adding processes that serve the needs of an organization.”

“Not just computers and computer code” (Brad Stockton –personal communication)

Lyytinen, K, Robey, D, “Learning Lyytinen, K, Robey, D, “Learning failure in information systems failure in information systems development”, development”, Information Information Systems JournalSystems Journal, Vol. 9. 2, 1999, , Vol. 9. 2, 1999, p85-101.p85-101.

Information Systems DevelopmentInformation Systems Development


Issues in early system developmentIssues in early system developmentUnstructured MethodologiesUnstructured Methodologies

limited user involvement limited user involvement

inadequate description of requirements inadequate description of requirements

unstructured analysis and design unstructured analysis and design

absence of easy to use tools absence of easy to use tools

inflexible storage and data management inflexible storage and data management

Systems did not satisfy business requirementsSystems did not satisfy business requirements

lack of ownership lack of ownership

requirements may have changed or been requirements may have changed or been misunderstood misunderstood

inadequate analysis and design prior to inadequate analysis and design prior to deliverydelivery

http://www.comp.glam.ac.uk/pages/staff/tdhutchings/chapter4.html



This lead to the development of “Structured methodologies” for system development

Clarify and reduce misunderstanding of business requirements by formalizing the descriptive processStandardize best practice techniques for the analysis and design process


Representative Representative System System Development Development MethodologiesMethodologies

Structured Systems Analysis Structured Systems Analysis and Design Method (SSADM)and Design Method (SSADM)

Rapid Application Rapid Application Development (RAD)Development (RAD)

Architected Rapid Application Architected Rapid Application Development (Architected Development (Architected RAD)RAD)

Dynamic Systems Dynamic Systems Development Methodology Development Methodology (DSDM)(DSDM)

Joint Application Development Joint Application Development (JAD)(JAD)

Information Engineering (IE)Information Engineering (IE)

Rational Unified Process (RUP)Rational Unified Process (RUP)

Structured Analysis and Structured Analysis and DesignDesign

eXtreme Programming (XP)eXtreme Programming (XP)



Stages:Stages: Development Operation and maintenance

Whitten, Jeffrey L. , Bentley, Lonnie D, and Dittman, Kevin , Systems Analysis and Design Methods, 7/e, Mc Graw-Hill, 2007



“Methodology:A codified set of recommended practices, sometimes accompanied by training materials, formal educational programs, worksheets and diagramming tools.

Thick methodology:A methodology that includes a large amount of formal process paperwork and documentation

Thin methodology:A methodology that eschews formal process paperwork and documentation.”

Software Project Management:Methodologies & TechniquesSE Project 2003/2004 group E17th September 2004 http://paul.luon.net/essays/SEP-essay-final.pdf.

Wikipedia | Methodology (Software engineering)http://en.wikipedia.org/wiki/Methodology(software_engineering).

Imperial College London | The Free On-Line Dictionary ofComputinghttp://foldoc.doc.ic.ac.uk/foldoc/.



Information Systems Information Systems Development methodology:Development methodology:

A standardized sequence of A standardized sequence of Information Systems development Information Systems development processes which solve problems, give processes which solve problems, give benefits, and competitive advantages benefits, and competitive advantages to an organization.to an organization.




Sircar S, Nerur SP, Mahapatra R. “Revolution or Evolution? A Comparison of Object-Oriented and Structured Systems Development Methods” MIS Quarterly, 25, 4, 2001, pp. 457-471.


Systems Analysis and Design

Analysis: Collect, compile and document the IS requirements, create models of the system.

Design: Create specifications, design, implement and test



Dennis, Alan, Wixom, Barbara, Dennis, Alan, Wixom, Barbara, Roth, Roberta. Roth, Roberta. Systems Analysis Systems Analysis and Designand Design 3rd ed., Wiley, 3rd ed., Wiley, Hoboken, 2005.Hoboken, 2005.

Four Phases of Development



Dennis, Alan, Wixom, Barbara, Dennis, Alan, Wixom, Barbara, Roth, Roberta. Roth, Roberta. Systems Analysis Systems Analysis and Designand Design 3rd ed., Wiley, 3rd ed., Wiley, Hoboken, 2005.Hoboken, 2005.


Principles:Principles:“Justify systems as capital investments.”“Get the system users involved.”“Don’t be afraid to cancel or revise scope.”“Use a problem-solving approach.”“Establish phases and activities.”“Document throughout development.”“Establish standards.”“Manage the process and projects.”“Divide and conquer.”“Design systems for growth and change.”




Online Advisory ModuleCreate an online, personalized advising systemSystem Functions

Track progress and classesCreate hypothetical personalized schedules based on historical semester offeringsAnalyze student progress to anticipate future class needs based on majorsProvide customized information on alternative pathwaysTrack feedback on quality of instruction and content.

GoalsImprove student graduation rateOptimize class sizeMinimize conflictReduce size of advisory staffReduce cost



Overview“Waterfall Techniques” -- Each step of the process must be completed in sequence

The next phase cannot begin before the previous phase is completed.Structured System Analysis and Design Methods (SSADM)

Structured System Analysis and Structured System Analysis and DesignDesign

Dennis, Alan, Wixom, Barbara, Dennis, Alan, Wixom, Barbara, Roth, Roberta. Roth, Roberta. Systems Systems Analysis and DesignAnalysis and Design 3 3rdrd ed., ed., Wiley, Hoboken, 2005. Wiley, Hoboken, 2005.


Structured System Analysis & Structured System Analysis & Design Methods (SSADM)Design Methods (SSADM)

HistoryDeveloped by the Central Computer and Telecommunications Agency (UK)

Office of Government Commerce (OGC)

support the procurement and acquisition process of public sector organizations in the UK through policy and process guidance and the negotiation of overarching service and provision frameworks

Made mandatory for new system development in 1983

Goodland M, Riha K: SSADM – an Introduction. http://www.dcs.bbk.ac.uk/~steve/1/, viewed 3/10/2007.

en.wikipedia.org/wiki/Office_of_Government_Commerce, viewed 3/10/2007.



en.wikipedia.org/wiki/Structured_Systems_Analysis_and_Design_Method, viewed 3/11/2007

Strategic Planning

SSADM

Feasibility Study

Requirements Analysis

Requirements Specification

Logical System Specification

Physical Design

Construct and Test

Full

Study

Development

Production

•Define the system•Set the scope•Develop project plan



Planning

Goal: Reduce costs and improve student graduation rates by developing an online academic advisor application for MyGateway

•$250k/year cost savings from reduced staff of Academic Advisors•$800k increased revenue from student retention due to increased visibility and management of personal academic requirements

Scope: Student activities related to managing their academic progress

Budget: •$800k/year 1 for development (10 FTE’s for 6 months)•$160k/year for maintenance (2 FTE’s for 2 months)



Tasks: Gather specific business requirements Create system design Build system Write test conditions Execute test Implement system Train students Maintain system





Strategic Planning

SSADM

Feasibility Study




Physical Design

Construct and Test

Full

Study

Development

Production

Analyze business and user requirements



Business Requirements: Single access point to manage individual degree program Personal degree requirements Progress towards earning degree Remaining requirements Class suggestions based on individual needs and class

availability Class add/drop functionality Comprehensive grade report and analysis Prospective schedule planning Class assignment Warning prompts

Out of scope: Student tuition/fee information Tuition assistance functionality Email functionality Help center functionality



Cost / Service Tradeoff?

Tuition fee/tuition functionality - $30k/year Tuition assistance functionality - $1000k/year Email functionality - $15k/year Help Center functionality - $200/year



Data Flow Modeling (DFM):Data Flow Modeling (DFM):Identify, model and document data flow Identify, model and document data flow in the business information systemin the business information system

Data transformation processes Data transformation processes Data storage Data storage External entities (things which send data External entities (things which send data into a system or receive data)into a system or receive data)Data flow pathsData flow paths

Software Project Management:Methodologies & TechniquesSE Project 2003/2004 group E17th September 2004 http://paul.luon.net/essays/SEP-essay-final.pdf, viewed 3/29/2007.

http://www.comp.glam.ac.uk/pages/staff/tdhutchings/chapter4/sld008.htm, viewed 3/29/2007.

Database

Students Faculty

Administration


http://paul.luon.net/essays/SEP-essay-final.pdf


http://www.comp.glam.ac.uk/pages/staff/tdhutchings/chapter4/sld008.htm




Logical Data Modeling (LDM): Logical Data Modeling (LDM): Identify, model and document data Identify, model and document data requirements requirements

Entity (Required business information) Entity (Required business information)

Relationships between entities.Relationships between entities.


http://www.comp.glam.ac.uk/pages/staff/tdhutchings/chapter4.html, viewed 3/29/2007.

http://www.comp.glam.ac.uk/pages/staff/tdhutchings/chapter4/sld007.htm, viewed 3/29/2007

Database

CoursesTaken

Grades

Academic Plan

CourseDescriptions

CourseSchedules










Entity/Event Modeling (EM):Entity/Event Modeling (EM): Identify, model and document Identify, model and document the sequence of business events the sequence of business events

Entity Life History (ELH)Entity Life History (ELH)


http://www.comp.glam.ac.uk/pages/staff/tdhutchings/chapter4/sld007.htm, viewed 3/29/2007.

Student Course Requirements and Desired Electives

Prerequisites

Courses taken

Course Schedules

Student Academic Plan

Database





Strategic Planning

SSADM

Feasibility Study




Physical Design

Construct and Test

Full

Study

Development

Production

Models:Data FlowLogical DataEntity/Event

RequirementsSpecification

Functions

Data Formats

InputsOutputs





Strategic Planning

SSADM

Feasibility Study




Physical Design

Construct and Test

Full

Study

Development

Production

Functions: Create logical class sequences Analysis of student progress

Data Formats

Inputs: Class Prerequisites Graduation Requirements Past and Projected Schedules

Outputs: Suggested pathways Warnings about unstable paths Schedule plans





Strategic Planning

SSADM

Feasibility Study




Physical Design

Construct and Test

Full

Study

Development

Production

RequirementsSpecification

Functions

Data Formats

InputsOutputs

Logical SystemSpecification

Detailed Narratives

Technical Specifications





http://en.wikipedia.org/wiki/Softwar_design viewed 4/1/2007.

Strategic Planning

SSADM

Feasibility Study




Physical Design

Construct and Test

Full

Study

Development

Production

… a process of problem-solving and planning for a software solution…


http://en.wikipedia.org/wiki/Softwar_design

http://en.wikipedia.org/wiki/Softwar_design


My Academic Advisor:

Added functionality


My Gateway

Personal AcademicAdvisor Page

User clicks Advisor Link

Degree Req Page

Degree Progress Page

User clicks ‘DegreeProgress’

Add/Drop Page

GPA Analysis Page

CourseSuggestion

Page

User clicks‘Add/Drop’

User clicks ‘GPA Analysis’

User clicks ‘DegreeRequirements’

User clicks ‘DegreeRequirements’


Course SuggestionPage

User clicks ‘Course Suggestion’ Page

Description & ‘Add’ button

Degree Progress Page

User clicks ‘DegreeProgress’

Add/Drop Page

GPA Analysis Page

AcademicAdvisor Page

User clicks‘Add/Drop’

User clicks ‘GPA Analysis’

User clicksAdvisor Link

User clicks on specific course



Strategic Planning

SSADM

Feasibility Study




Physical Design

Construct and Test

Full

Study

Development

Production



Software testing is the process used to help identify the correctness, completeness, security, and quality of the developed computer software.

Test Levels: Unit Testing – programmers test individual modules Integration Testing – tests interfaces and interaction between

modules Functional Testing – tests the product System Testing – tests integrated system Acceptance Testing – can be conducted by the client



Acceptance Testing – Allows the end-user to decide whether to accept the product.

Examples: Does the website provide a single point of access for

students to manage their degree program? Does the website accurately include information from

other UMSL applications (ie – GPA, course availability, etc) Does the website provide accurate course suggestions

based on the individual degree requirements and progress?



Software Release – the distribution of the software product

Can be done in phases:Alpha – stage when new features are being addedBeta – system is actively being debuggedStable – important bugs have been removed



AdvantagesOpen StandardMany companies offer CASE (Computer Aided Software Engineering) tools, training and supportUse for

Any size projectDevelop new projectsMaintain existing projects

Software Project Management:Methodologies & TechniquesSE Project 2003/2004 group E17th September 2004 http://paul.luon.net/essays/SEP-essay-final.pdf, , viewed 3/29/2007.



AdvantagesSequential approach dividing the project into modules, stages, steps, and tasks, allows straight forward project managementCan use experienced and inexperienced development staff that is tolerant of staff turnoverFacilitate communication between participantsEnhance initial understanding of design requirements and minimizing drift from these requirements






DisadvantagesDisadvantagesAssumes the requirements established at Assumes the requirements established at the beginning of the project will not changethe beginning of the project will not changeSequential approach can be very time Sequential approach can be very time consuming and inefficient creating delay.consuming and inefficient creating delay.There may be a longer development time There may be a longer development time and reduced flexibility is more likely to and reduced flexibility is more likely to create create ““failed successesfailed successes”” -- Successful -- Successful project that fails to meet its goals.project that fails to meet its goals.

““The assumption of a stable and coherent The assumption of a stable and coherent strategic context within which an SSADM strategic context within which an SSADM project would take place was shown to be project would take place was shown to be invalid in practice.invalid in practice.””“…“…good quality, firm, detailed requirements good quality, firm, detailed requirements are very hard to obtain.are very hard to obtain.””

Software Project Management:Methodologies & TechniquesSE Project 2003/2004 group E17th September 2004 http://paul.luon.net/essays/SEP-essay-final.pdf , viewed 3/29/2007.

Middleton, P. “Barriers to the efficient and effective use of information technology”, The International Journal of Public Sector Management. Vol.13, 1, 2000, pp. 85-100.

Middleton, P. “Software Quality by Administration”, Software Quality Journal, Vol. 7, 261-275, 1998.





Rapid Application Rapid Application Development (RAD) MethodsDevelopment (RAD) Methods

Overview“Iterative” or “incremental” – develop systems in smaller steps with repeated iterations utilizing the information and knowledge gained from the first iteration

Rapid Application Development Methods (RAD)


What is RAD?“A systems development philosophy that can be effective in controlling waste and inefficiencies that are so common with system development projects.”“iterative development,… construction of prototypes, and the use of Computer-aided Software Engineering (CASE) Tools.”

The Goal:High quality systemsRapid DevelopmentReduced cost

Compton TR, Minimizing waste Compton TR, Minimizing waste with RAD, with RAD, Strategic FinanceStrategic Finance; Vol., ; Vol., 83, 12, 2002; pg. 50-3.83, 12, 2002; pg. 50-3.

Rapid Application Rapid Application Development (RAD) methodsDevelopment (RAD) methods


Developed in the 1980s to address some of the shortcomings of SSADM and other structured methodologies

Very high level of user involvement fosters commitment and ownership; Rapid response to changing requirements; Multi-disciplinary approach combining users, analysts and technical specialists.

Incremental development of large projects“a software product is designed and built in a succession of incremental iterations.”Modularity allows application to many types of software projects





RAD:Define user requirementsIterations

Build a system prototypeDevelop and test

Deploy

Compton TR, Minimizing waste Compton TR, Minimizing waste with RAD, with RAD, Strategic FinanceStrategic Finance; Vol., ; Vol., 83, 12, 2002; pg. 50-3.83, 12, 2002; pg. 50-3.



PrioritizationAssign priority to quality criteria and functions

Time-Boxingsplitting the project up in a number of separate time periods - each with a separate deadline and budget

EfficiencyTesting with each iterationProblems corrected earlierAvoid waiting for the completion of one phase before beginning anotherIntegration and implementation part of development processHandles requirement “creep” more effectivelyMany standard packages available

Rational Unified Process (IBM)

Knöll, Heinz-Dieter, Kuhl Roland, Kuhl Lukas, and Moreton Robert, Optimising Business Performance with Standard Software Systems: How to Reorganise Workflows by Chance of Implementing New ERP-Systems, Springer, Wiesbaden, 2001.


http://en.wikipedia.org/wiki/Time_boxing viewed 4/7/2007.


Components


Joint application development (JAD)Small group of users and designers with decision making authority – skilled in design and business

Clean roomsJAD remote from the business and free from interruption

Incremental prototypingDevelopers create working model to show users.Developers and users agree on changes and enhancementsRepeated until the user is satisfied

Highly interactive, low complexity projects

Beynon-Davies P, Carne C, Beynon-Davies P, Carne C, Mackay H, Tudhope D., “Rapid Mackay H, Tudhope D., “Rapid application development (RAD): application development (RAD): an empirical review, an empirical review, European European Journal of Information SystemsJournal of Information Systems, , Vol. 8, 3, 1999; pp. 211-222.Vol. 8, 3, 1999; pp. 211-222.


Components


TypesIntensive

Developers and users enter a “clean room” for a specified “time box” to deliver a product.Weeks

PhasedDelivery of incremental prototypes with successive refinements (iterations)Months

Beynon-Davies P, Carne C, Beynon-Davies P, Carne C, Mackay H, Tudhope D., “Rapid Mackay H, Tudhope D., “Rapid application development (RAD): application development (RAD): an empirical review, an empirical review, European European Journal of Information SystemsJournal of Information Systems, , Vol. 8, 3, 1999; pp. 211-222.Vol. 8, 3, 1999; pp. 211-222.



Iteration 11) Individual degree requirements2) Individual degree progress3) GPA & analysis4) Course suggestions5) Add/Drop functionality

Difference from SSADM?Difference from SSADM?•Sequential development (Iterations)Sequential development (Iterations)•PrioritizationPrioritization•User InvolvementUser Involvement•Addresses changes throughout projectAddresses changes throughout project

Iteration 21) Improve iteration 1 functions2) Track progress and classes3) Create hypothetical

personalized schedules based on historical semester offerings

4) Analyze student progress to anticipate future class needs based on majors

Iteration 31) Improve iteration 2 functions2) Provide customized information

on alternative pathways3) Track feedback on quality of

instruction and content.



Rapid Development – Greater efficiencySense of customer ownership

Better meets user expectationsKnowledgeable user

Understands and participates in development process

Effective communicationFlexibility for changing requirementsEarlier review and testing of the productEarlier error detection

Reduced cost?

Hentzen, Whil, and Nowak, Patty. Hentzen, Whil, and Nowak, Patty. The Software Developer’s GuideThe Software Developer’s Guide 3rd ed., Hentzenwerke, Whitefish 3rd ed., Hentzenwerke, Whitefish Bay, 2002. Bay, 2002.

AdvantagesAdvantages



May try and hurry the project too much “Haste makes waste.”

Requires the availability of experienced usersPotentially steep learning curve for programmers inexperienced with RAD tools

e.g. RUPCommercial product, no open or free standardComplex methodology, not appropriate for small projectsParticipants have to learn to work with it

Need to make a significant investment of time, money, and training

Loosely documentedOnly useful for interactive projects

with a defined user group requiring specific user interface functionality;not computationally complex with requirements which are fairly simple (less detailed) and specific.

Kendall, Kenneth E. and Kendall, Julie E, Systems Analysis and Design, Prentice Hall, Upper Saddle River, 2002.



Robinson R., “Put the rapid into Robinson R., “Put the rapid into RAD” RAD” Datamation,Datamation, 42, 4, 1996, 42, 4, 1996, pg. 80.pg. 80.

DisadvantagesDisadvantages



Successful Systems Analysis and Successful Systems Analysis and Design:Design:

Managerial involvementManagerial involvementUser involvementUser involvementDeveloper involvementDeveloper involvementStandardized, robust Standardized, robust methodologymethodologyTimely developmentTimely developmentMechanisms to adapt to Mechanisms to adapt to changing requirementschanging requirements

SummarySummary



Outlined two distinct approachesOutlined two distinct approachesWaterfall -- SSADMWaterfall -- SSADM

Iterative -- RADIterative -- RAD

In reality, many approaches have In reality, many approaches have been developed which merge been developed which merge advantages of each approachadvantages of each approach

SummarySummary



Waterfall Methods -- SSADMWaterfall Methods -- SSADMComplex ProjectsComplex ProjectsBroad ApplicationBroad ApplicationRelatively stable requirementsRelatively stable requirementsRelatively non-interactiveRelatively non-interactive

Iterative – RADIterative – RADSmaller projectsSmaller projectsFocused applicationFocused applicationDynamic requirementsDynamic requirementsHighly interactiveHighly interactiveCustomer ownershipCustomer ownership

SummarySummary


Successful Systems Analysis and Design:Successful Systems Analysis and Design:

Whatever approach is chosen:Whatever approach is chosen:

“… “… people rather than methodology are people rather than methodology are the key factor in raising productivity.”the key factor in raising productivity.”

““User communication: the emphasis User communication: the emphasis needs to be shifted from diagramming needs to be shifted from diagramming techniques and CASE tools to the techniques and CASE tools to the sociology of projects…much larger and sociology of projects…much larger and cheaper gains could be made from cheaper gains could be made from tackling the "soft" organizational rather tackling the "soft" organizational rather than the "hard" technical issues within IS than the "hard" technical issues within IS development.”development.”

SummarySummaryMiddleton, P. “Barriers to the efficient and effective use of information technology”, The International Journal of Public Sector Management. Vol.13, 1, 2000, pp. 85-100.


QUESTIONSQUESTIONS


Peer reviewed and scholarly journalsPeer reviewed and scholarly journals Harris AL, Lang M, Oates B, Siau K. “Systems Analysis & Design: An Essential Part Harris AL, Lang M, Oates B, Siau K. “Systems Analysis & Design: An Essential Part

of IS Education” of IS Education” Journal of Information Systems Education,Journal of Information Systems Education, Vol. 17, 3, 2006; pp. Vol. 17, 3, 2006; pp. 241-9. 241-9.

Cullen S, Seddon P, Willcocks L. “Managing Outsourcing: The Lifecycle Imperative” Cullen S, Seddon P, Willcocks L. “Managing Outsourcing: The Lifecycle Imperative” MIS Quarterly ExecutiveMIS Quarterly Executive, Vol. 4, 1, 2005; pp 229-246., Vol. 4, 1, 2005; pp 229-246.

Keil, M, and Montealegre, R. "Cutting Your Losses: Extricating Your Organization Keil, M, and Montealegre, R. "Cutting Your Losses: Extricating Your Organization When A Big Project Goes Awry," When A Big Project Goes Awry," Sloan Management ReviewSloan Management Review, Vol. 41, 3, 2000, pp. , Vol. 41, 3, 2000, pp. 55-68.55-68.

Feeny D, Willcocks, L, “Core IS Capabilities for exploiting Information Technology, Feeny D, Willcocks, L, “Core IS Capabilities for exploiting Information Technology, Sloan Management ReviewSloan Management Review, Vol. 39, 3, 1998, pp. 9-21. , Vol. 39, 3, 1998, pp. 9-21.

Sircar S, Nerur SP, Mahapatra R. “Revolution or Evolution? A Comparison of Sircar S, Nerur SP, Mahapatra R. “Revolution or Evolution? A Comparison of Object-Oriented and Structured Systems Development Methods” Object-Oriented and Structured Systems Development Methods” MIS Quarterly MIS Quarterly ExecutiveExecutive, Vol. 25, 4, 2001, pp. 457-471., Vol. 25, 4, 2001, pp. 457-471.

Beynon-Davies P, Carne C, Mackay H, Tudhope D., “Rapid application Beynon-Davies P, Carne C, Mackay H, Tudhope D., “Rapid application development (RAD): an empirical review, development (RAD): an empirical review, European Journal of Information European Journal of Information SystemsSystems, Vol. 8, 3, 1999; pp. 211-222., Vol. 8, 3, 1999; pp. 211-222.

Compton TR, “Minimizing waste with RAD”, Compton TR, “Minimizing waste with RAD”, Strategic FinanceStrategic Finance; Vol., 83, 12, 2002; ; Vol., 83, 12, 2002; pg. 50-3.pg. 50-3.

Lyytinen, K, Robey, D, “Learning failure in information systems development”, Lyytinen, K, Robey, D, “Learning failure in information systems development”, Information Systems JournalInformation Systems Journal, Vol. 9. 2, 1999, p85-101., Vol. 9. 2, 1999, p85-101.

Middleton, P. “Barriers to the efficient and effective use of information Middleton, P. “Barriers to the efficient and effective use of information technology”, technology”, The International Journal of Public Sector Management.The International Journal of Public Sector Management. Vol.13, 1, Vol.13, 1, 2000, pp. 85-100.2000, pp. 85-100.

Middleton, P. “Software Quality by Administration”, Middleton, P. “Software Quality by Administration”, Software Quality Journal,Software Quality Journal, Vol. Vol. 7, 261-275, 1998.7, 261-275, 1998.

BibliographyBibliography


Non-Peer reviewedNon-Peer reviewed en.wikipedia.org/wiki/Structured_Systems_Analysis_and_Design_Method, viewed 3/11/2007.en.wikipedia.org/wiki/Structured_Systems_Analysis_and_Design_Method, viewed 3/11/2007. Goodland M, Riha K: SSADM – an Introduction. http://www.dcs.bbk.ac.uk/~steve/1/, viewed Goodland M, Riha K: SSADM – an Introduction. http://www.dcs.bbk.ac.uk/~steve/1/, viewed

3/10/2007.3/10/2007. en.wikipedia.org/wiki/Office_of_Government_Commerce, viewed 3/10/2007.en.wikipedia.org/wiki/Office_of_Government_Commerce, viewed 3/10/2007. en.wikipedia.org/wiki/Waterfall_model, viewed 3/11/2007en.wikipedia.org/wiki/Waterfall_model, viewed 3/11/2007 Software Project Management: Methodologies & Techniques SE Project 2003/2004 group E 17th Software Project Management: Methodologies & Techniques SE Project 2003/2004 group E 17th

September 2004 http://paul.luon.net/essays/SEP-essay-final.pdf, viewed 4/1/2007.September 2004 http://paul.luon.net/essays/SEP-essay-final.pdf, viewed 4/1/2007. Wikipedia | Methodology (Software engineering) Wikipedia | Methodology (Software engineering)

http://en.wikipedia.org/wiki/Methodology_(software_engineering) , viewed 4/1/2007.http://en.wikipedia.org/wiki/Methodology_(software_engineering) , viewed 4/1/2007. Imperial College London | The Free On-Line Dictionary of Computing Imperial College London | The Free On-Line Dictionary of Computing

http://foldoc.doc.ic.ac.uk/foldoc/ , viewed 4/1/2007.http://foldoc.doc.ic.ac.uk/foldoc/ , viewed 4/1/2007. http://www.comp.glam.ac.uk/pages/staff/tdhutchings/chapter4.html viewed 4/1/2007.http://www.comp.glam.ac.uk/pages/staff/tdhutchings/chapter4.html viewed 4/1/2007. http://en.wikipedia.org/wiki/Time_boxing viewed 4/7/2007.http://en.wikipedia.org/wiki/Time_boxing viewed 4/7/2007. www.cbe.wwu.edu/misclasses/MIS320_Spring06_Bajwa/Chap006.ppt , viewed April 03, 2007www.cbe.wwu.edu/misclasses/MIS320_Spring06_Bajwa/Chap006.ppt , viewed April 03, 2007 http://www.comp.glam.ac.uk/pages/staff/tdhutchings/chapter4.html viewed 4/7/07.http://www.comp.glam.ac.uk/pages/staff/tdhutchings/chapter4.html viewed 4/7/07. http://en.wikipedia.org/wiki/Methodology(software_engineering), viewed 4/3/07.http://en.wikipedia.org/wiki/Methodology(software_engineering), viewed 4/3/07. Dennis, Alan, Wixom, Barbara, Roth, Roberta. Dennis, Alan, Wixom, Barbara, Roth, Roberta. Systems Analysis and DesignSystems Analysis and Design 3 3rdrd ed., Wiley, ed., Wiley,

Hoboken, 2005. Hoboken, 2005. Hentzen, Whil, and Nowak, Patty. Hentzen, Whil, and Nowak, Patty. The Software Developer’s GuideThe Software Developer’s Guide 3rd ed., Hentzenwerke, 3rd ed., Hentzenwerke,

Whitefish Bay, 2002.Whitefish Bay, 2002. Kendall, Kenneth and Kendall, Julie, Kendall, Kenneth and Kendall, Julie, Systems Analysis and DesignSystems Analysis and Design, Prentice Hall, Upper Saddle , Prentice Hall, Upper Saddle

River, 2002.River, 2002. Knöll, Heinz-Dieter, Kuhl Roland, Kuhl Lukas, and Moreton Robert, Knöll, Heinz-Dieter, Kuhl Roland, Kuhl Lukas, and Moreton Robert, Optimising Business Optimising Business

Performance with Standard Software Systems: How to Reorganise Workflows by Chance of Performance with Standard Software Systems: How to Reorganise Workflows by Chance of Implementing New ERP-SystemsImplementing New ERP-Systems, Springer, Wiesbaden, 2001., Springer, Wiesbaden, 2001.

Robinson R., “Put the rapid into RAD” Robinson R., “Put the rapid into RAD” Datamation,Datamation, 42, 4, 1996, pg. 80. 42, 4, 1996, pg. 80. Whitten, Jeffrey and Bentley, Lonnie, Whitten, Jeffrey and Bentley, Lonnie, Systems Analysis and Design MethodsSystems Analysis and Design Methods, 7, 7thth ed., McGraw-Hill, ed., McGraw-Hill,

New York, 2007.New York, 2007.

BibliographyBibliography

systems analysis & design methods

Documents

designsystems analysis

projectssystems analysis

projectsystems analysis

example heresystems

design phase

project management

management principles

development projects