330 likes | 489 Views
Management Information Systems, 3rd EditionEffy Oz. 2. Learning Objectives. When you finish this chapter, you will:Understand the systems development life cycle.Be able to list and explain the pros and cons of prototyping.Understand how software tools facilitate the monitoring and controlling of
E N D
1. Management Information Systems, 3rd Edition
Effy Oz 1 Chapter 15Systems Development
2. Management Information Systems, 3rd Edition
Effy Oz 2 Learning Objectives When you finish this chapter, you will:
Understand the systems development life cycle.
Be able to list and explain the pros and cons of prototyping.
Understand how software tools facilitate the monitoring and controlling of systems development.
3. Management Information Systems, 3rd Edition
Effy Oz 3 Learning Objectives Recognize the difficulties involved in systems development.
Be able to list the advantages and disadvantages of different system conversion strategies.
Understand the concept of systems integration.
4. Management Information Systems, 3rd Edition
Effy Oz 4 Why Develop an IS? Three phenomena that trigger IS development
An opportunity (proactive)
A problem (reactive)
A directive
5. Management Information Systems, 3rd Edition
Effy Oz 5 The Systems Development Life Cycle (SLDC)
6. Management Information Systems, 3rd Edition
Effy Oz 6 The Systems Development Life Cycle (SLDC) Analysis
Determines what need the system will satisfy
Investigation
Developers interview managers and perspective users to determine business needs.
Three feasibility studies performed.
7. Management Information Systems, 3rd Edition
Effy Oz 7 The Systems Development Life Cycle (SLDC)
8. Management Information Systems, 3rd Edition
Effy Oz 8 The Systems Development Life Cycle (SLDC) The Technical Feasibility Study
Ensures hardware and software exist to build the system
The Economic Feasibility Study
Benefits of the system weighed against the cost
The Operational Feasibility Study
Determines if system will be used as intended
Requirements Definition
Specific requirements of system defined
9. Management Information Systems, 3rd Edition
Effy Oz 9 The Systems Development Life Cycle (SLDC)
10. Management Information Systems, 3rd Edition
Effy Oz 10 The Systems Development Life Cycle (SLDC)
11. Management Information Systems, 3rd Edition
Effy Oz 11 The Systems Development Life Cycle (SLDC) Design
Logical Design
Translation of user requirements into detailed functions of the system
Physical Design
Construction
Systems Testing
12. Management Information Systems, 3rd Edition
Effy Oz 12 The Systems Development Life Cycle (SLDC)
13. Management Information Systems, 3rd Edition
Effy Oz 13 The Systems Development Life Cycle (SLDC)
14. Management Information Systems, 3rd Edition
Effy Oz 14 The Systems Development Life Cycle (SLDC)
15. Management Information Systems, 3rd Edition
Effy Oz 15 The Systems Development Life Cycle (SLDC)
16. Management Information Systems, 3rd Edition
Effy Oz 16 The Systems Development Life Cycle (SLDC) Implementation
Training
Conversion
Parallel Conversion
Phased Conversion
Cold Turkey Conversion
Pilot Conversion
17. Management Information Systems, 3rd Edition
Effy Oz 17 The Systems Development Life Cycle (SLDC)
18. Management Information Systems, 3rd Edition
Effy Oz 18 The Systems Development Life Cycle (SLDC) Support
19. Management Information Systems, 3rd Edition
Effy Oz 19 Prototyping Systems developed using an iterative process
Purpose is to develop a working model as quickly as possible, which can be tweaked and revised
Significantly shortens systems development backlog
Can increase risk of incompatibility and other unforeseen mishaps
20. Management Information Systems, 3rd Edition
Effy Oz 20 Prototyping
21. Management Information Systems, 3rd Edition
Effy Oz 21 Prototyping
22. Management Information Systems, 3rd Edition
Effy Oz 22 Computer-AidedSoftware Engineering Computer-Aided Software Engineering (CASE tools)
System development programs that ease and speed design and construction of new ISs
Application generators
I-CASE tools
Rapid Application Development (RAD)
23. Management Information Systems, 3rd Edition
Effy Oz 23 Project Management Project Management Tools
Project Evaluation and Review Technique (PERT)
PERT chart shows events, required activities, and relationships
Advantage: Communication of interdependencies among activities
Gantt Chart
Represents activities and start and completion times, but not the relationships among activities
Advantage: Simple and linear
24. Management Information Systems, 3rd Edition
Effy Oz 24 Project Management
25. Management Information Systems, 3rd Edition
Effy Oz 25 Project Management Project Management Goals
Complete the project on time.
Complete the project within budget.
Meet requirements.
Meet expectations.
26. Management Information Systems, 3rd Edition
Effy Oz 26 Project Management
27. Management Information Systems, 3rd Edition
Effy Oz 27 Project Management Project Management Functions
Communication Management
Schedule Management
Quality Management
Financial Management
Resource Management
28. Management Information Systems, 3rd Edition
Effy Oz 28 Systems DevelopmentLed by End Users JAD: An example of User-led Systems Development
Joint Application Development (JAD): method to be used in SDLU
Uses six-step process to take the team through planning and design
29. Management Information Systems, 3rd Edition
Effy Oz 29 Systems DevelopmentLed by End Users
30. Management Information Systems, 3rd Edition
Effy Oz 30 Systems DevelopmentLed by End Users JAD Critical Success Factors
All participants must be committed to JAD process.
Customers and IS people must agree on project’s scope.
Sponsor must be supportive and involved.
Team members must be empowered decision makers.
Business objectives must be clearly defined.
Business process must be understood.
Team members must be able to meet two or more days per week.
Members must be committed to the team.
31. Management Information Systems, 3rd Edition
Effy Oz 31 Systems Integration Takes a look at the information needs of an entire organization (or a major division)
Analysts integrate existing systems so that:
Data can flow more easily among business units.
Users can access different types of data via a single interface.
32. Management Information Systems, 3rd Edition
Effy Oz 32 Ethical and Societal IssuesShould IS Professionals Be Certified? Malfunctioning ISs
Faulty systems may wreak havoc, causing financial damage or even death
Should IS professionals be certified based on the high investment and risk involved in their work?
33. Management Information Systems, 3rd Edition
Effy Oz 33 Ethical and Societal IssuesShould IS Professionals Be Certified? Certification Pros
Protect potential employers
Protect clients of consultants
Fewer software-related failures
Certification Cons
Difficult to measure software competence
May create a “closed shop:” decreased competition, decreased incentive to improve skills