0% found this document useful (0 votes)
45 views29 pages

ch12 - Building Information Systems and Managing Projects

Uploaded by

jmexact
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
45 views29 pages

ch12 - Building Information Systems and Managing Projects

Uploaded by

jmexact
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 29

Management Information

Systems
Chapter 12 Building Information Systems and Managing Projects

Business School

Kyung Jin CHA


[email protected]
Learning Objectives

12.1 What are the core problem-solving steps for developing


new information systems?
12.2 What are the alternative methods for building information
systems?
12.3 What are the principal methodologies for modeling and
designing systems?
12.4 How should information systems projects be selected and
managed?

2
Core Problem-Solving Steps for Developing New
Information Systems
• New information systems are built as solutions to problems
• Four steps to building an information system
• Define and understand the problem
• Develop alternative solutions
• Choose a solution
• Implement the solution
• The first three steps are called systems analysis
Figure 12.1 Developing an Information System
Solution
Defining and Understanding the Problem
• Different people may have different ideas about the nature of
the problem and its severity
• What caused the problem?
• Why does it persist?
• Why hasn’t it been solved?
• What are the objectives of a solution?
• Information requirements
• Identifies who needs what information, when, where, and
how
• Requirements analysis
Developing Alternative Solutions

• Paths to a solution determined by systems analysis.


• Some solutions do not require an information system.
• Some solutions require modification of existing systems.
• Some solutions require new systems.
Evaluating and Choosing Solutions

• Feasibility study:
• Is solution feasible from financial, technical, and
organizational standpoint?
• Systems proposal report
• Describes, for each alternative solution
• Costs and benefits
• Advantages and disadvantages
Implementing the Solution

• Systems design
• Completing implementation
• Hardware selection and acquisition
• Software development and programming
• Testing
• Training and documentation
• Conversion
• Production and maintenance
• Managing the change
Figure 12.2 A Sample Test Plan for the Girl
Scout Digital Cookie System
Traditional Systems Development Lifecycle

• SLDC: Oldest method for building information systems


• Phased approach with formal stages
• Waterfall approach
• Formal division of labor
• Used for building large, complex systems
• Time consuming and expensive to use
Figure 12.3 The Traditional Systems
Development Life Cycle
Prototyping

• Preliminary model built rapidly and inexpensively


• Four-step process
• Identify the user’s basic requirements
• Develop an initial prototype
• Use the prototype
• Revise and enhance the prototype
• Especially useful in designing a user interface
Figure 12.4 The Prototyping Process
End-User Development

• End users create simple information systems with little or no


assistance from specialists
• Completed more rapidly than systems developed with
conventional tools
• Often leads to higher level of user involvement and satisfaction
with systems
• Cannot handle large numbers of transactions
• Organizational risks
Application Software Packages, software
Services, and Outsourcing
• Request for Proposal (RFP)
• Application software packages and cloud software packages
– Generalized systems for universal functions with standard
processes
– Customization features
• Outsourcing
• Domestic outsourcing
• Offshore outsourcing
Figure 12.5 Total Cost of Offshore Outsourcing
Mobile Application Development

• Mobile websites, web apps


• Native apps
• Different requirements for mobile devices than for PCs
• Reduced size of screens
• Touch screens
• Saving resources: bandwidth, memory, processing, data
entry
• Responsive web design
Rapid Application Development

• Need for agility, scalability, and fast-cycle techniques


• Rapid application development (RAD)
• Creating workable systems in a very short period of time
• Joint application design (JAD)
• End users and information systems specialists working
together on design
• Agile development
• DevOps
Figure 12.6 Data Flow Diagram for Mail-in
University Registration System
Object-Oriented Development
• Uses the object as the basic unit of systems analysis and design
• Class
• Inheritance
• More iterative and incremental than traditional structured
development
• Component-based development
• Groups of objects assembled into software components
• Used to create e-commerce applications
• Web services, cloud-based development
Figure 12.8 Class and Inheritance
Computer-Aided Software Engineering (CASE)

• Provides software tools to automate the previously described


methodologies
• Reduces repetitive work in systems development
• CASE tools facilitate
• Clear documentation
• Coordination of team development efforts
• Modest productivity benefits if tools are used correctly
Project Management Objectives
• Project management
• Application of knowledge, skills, tools, and techniques to
achieve targets within specified budget and time
constraints
• Five major variables:
• Scope
• Time
• Cost
• Quality
• Risk
Selecting Projects

• Determining project costs and benefits


• Tangible benefits
• Intangible benefits
• Capital budgeting methods
• Information systems plan
• Portfolio analysis
• Scoring model
Figure 12.9 A System Portfolio
Managing Project Risk and System-Related
Change
• Implementation and change management
• Implementation
• User-designer communications gap
• Controlling risk factors
• Formal planning and tools
• Gantt chart, PERT chart
• Project management software
• Overcoming user resistance
• Ergonomics
• Organizational impact analysis
Figure 12.10 A Gannt Chart (1 of 3)
A:
Figure 12.10 A Gannt Chart (3 of 3)
C:
Figure 12.11 A PERT Chart

You might also like