We use cookies to give you the best experience possible. By continuing we’ll assume you’re on board with our cookie policy

See Pricing

What's Your Topic?

Hire a Professional Writer Now

The input space is limited by 250 symbols

What's Your Deadline?

Choose 3 Hours or More.
Back
2/4 steps

How Many Pages?

Back
3/4 steps

Sign Up and See Pricing

"You must agree to out terms of services and privacy policy"
Back
Get Offer

MIS: MANAGING THE DIGITAL FIRM

Hire a Professional Writer Now

The input space is limited by 250 symbols

Deadline:2 days left
"You must agree to out terms of services and privacy policy"
Write my paper

Management Information Systems
MANAGING THE DIGITAL FIRM, 12TH EDITION GLOBAL EDITION

Chapter 13
BUILDING INFORMATION SYSTEMS

Don't use plagiarized sources. Get Your Custom Essay on
MIS: MANAGING THE DIGITAL FIRM
Just from $13,9/Page
Get custom paper

VIDEO CASES
Case 1: IBM: Business Process Management in a Service-Oriented Architecture and Managing Projects
Case 2: Rapid Application Development With Appcelerator
Instructional Video 1: Salesforce and Google: Developing Sales Support Systems with Online Apps

Management Information Systems
CHAPTER 13: BUILDING INFORMATION SYSTEMS

Learning Objectives

• How does building new systems produce
organizational change?
• What are the core activities in the systems
development process?
• What are the principal methodologies for modeling
and designing systems?
• What are the alternative methods for building
information systems?
• What are new approaches for system building in the
digital firm era?
2

© Pearson Education 2012

Management Information Systems
CHAPTER 13: BUILDING INFORMATION SYSTEMS

Systems as Planned Organizational Change

• Structural organizational changes enabled by IT
1. Automation
• Increases efficiency
• Replaces manual tasks
2. Rationalization of procedures
• Streamlines standard operating procedures
• Often found in programs for making continuous
quality improvements
– Total quality management (TQM)
– Six sigma
3

© Pearson Education 2012

1

6/28/2013

Management Information Systems
CHAPTER 13: BUILDING INFORMATION SYSTEMS

Systems as Planned Organizational Change

• Structural organizational changes enabled by IT
3. Business process redesign
• Analyze, simplify, and redesign business
processes
• Reorganize workflow, combine steps, eliminate
repetition
4. Paradigm shifts
• Rethink nature of business
• Define new business model
• Change nature of organization
4

© Pearson Education 2012

Management Information Systems
CHAPTER 13: BUILDING INFORMATION SYSTEMS

Systems as Planned Organizational Change
ORGANIZATIONAL
CHANGE CARRIES
RISKS AND
REWARDS
The most common forms of
organizational change are
automation and rationalization.
These relatively slow-moving
and slow-changing strategies
present modest returns but
little risk. Faster and more
comprehensive change—such
as redesign and paradigm
shifts—carries high rewards
but offers substantial chances
of failure.
FIGURE 13-1

5

© Pearson Education 2012

Management Information Systems
CHAPTER 13: BUILDING INFORMATION SYSTEMS

Systems as Planned Organizational Change

• Business process management (BPM)
– Variety of tools, methodologies to analyze, design,
optimize processes
– Used by firms to manage business process redesign

• Steps in BPM
1.Identify processes for change
2.Analyze existing processes
3.Design the new process
4.Implement the new process
5.Continuous measurement
6

© Pearson Education 2012

2

6/28/2013

Management Information Systems
CHAPTER 13: BUILDING INFORMATION SYSTEMS

Systems as Planned Organizational Change
AS-IS BUSINESS PROCESS FOR PURCHASING A BOOK FROM A PHYSICAL BOOKSTORE

FIGURE 13-2

Purchasing a book from a physical bookstore requires many steps to be performed by both the seller and the customer.

7

© Pearson Education 2012

Management Information Systems
CHAPTER 13: BUILDING INFORMATION SYSTEMS

Systems as Planned Organizational Change
REDESIGNED PROCESS FOR PURCHASING A BOOK ONLINE

FIGURE 13-3

Using Internet technology makes it possible to redesign the process for purchasing a book so that it requires fewer steps and consumes fewer resources.

8

© Pearson Education 2012

Management Information Systems
CHAPTER 13: BUILDING INFORMATION SYSTEMS

Systems as Planned Organizational Change

• Variety of tools for BPM, to
– Identify and document existing processes
• Identify inefficiencies

– Create models of improved processes
– Capture and enforce business rules for performing
processes
– Integrate existing systems to support process
improvements
– Verify that new processes have improved
– Measure impact of process changes on key business
performance indicators
9

© Pearson Education 2012

3

6/28/2013

Management Information Systems
CHAPTER 13: BUILDING INFORMATION SYSTEMS

Overview of Systems Development

• Systems development:
– Activities that go into producing an information
system solution to an organizational problem or
opportunity
1.Systems analysis
2.Systems design
3.Programming
4.Testing
5.Conversion
6.Production and maintenance
10

© Pearson Education 2012

Management Information Systems
CHAPTER 13: BUILDING INFORMATION SYSTEMS

Overview of Systems Development
THE SYSTEMS
DEVELOPMENT
PROCESS
Building a system can be
broken down into six core
activities.
FIGURE 13-4

11

© Pearson Education 2012

Management Information Systems
CHAPTER 13: BUILDING INFORMATION SYSTEMS

Overview of Systems Development

• Systems analysis
– Analysis of problem to be solved by new system
• Defining the problem and identifying causes
• Specifying solutions
– Systems proposal report identifies and examines alternative solutions

• Identifying information requirements

– Includes feasibility study
• Is solution feasible and good investment?
• Is required technology, skill available?
12

© Pearson Education 2012

4

6/28/2013

Management Information Systems
CHAPTER 13: BUILDING INFORMATION SYSTEMS

Overview of Systems Development

• System analysis (cont.)
– Establishing information requirements
• Who needs what information, where, when,
and how
• Define objectives of new/modified system
• Detail the functions new system must perform
– Faulty requirements analysis is leading cause of
systems failure and high systems development
cost
13

© Pearson Education 2012

Management Information Systems
CHAPTER 13: BUILDING INFORMATION SYSTEMS

Overview of Systems Development

• Systems design
– Describes system specifications that will deliver
functions identified during systems analysis
– Should address all managerial, organizational, and
technological components of system solution
– Role of end users
• User information requirements drive system building
• Users must have sufficient control over design process to ensure system reflects their business priorities and
information needs
• Insufficient user involvement in design effort is major cause of system failure
14

© Pearson Education 2012

Management Information Systems
CHAPTER 13: BUILDING INFORMATION SYSTEMS

Overview of Systems Development

• Programming:
– System specifications from design stage are
translated into software program code

• Testing



Ensures system produces right results
Unit testing: Tests each program in system separately
System testing: Test functioning of system as a whole
Acceptance testing: Makes sure system is ready to be
used in production setting
– Test plan: All preparations for series of tests
15

© Pearson Education 2012

5

6/28/2013

Management Information Systems
CHAPTER 13: BUILDING INFORMATION SYSTEMS

Overview of Systems Development

• Conversion
– Process of changing from old system to new system
– Four main strategies
1.
2.
3.
4.

Parallel strategy
Direct cutover
Pilot study
Phased approach

– Requires end-user training
– Finalization of detailed documentation showing how
system works from technical and end-user
standpoint
16

© Pearson Education 2012

Management Information Systems
CHAPTER 13: BUILDING INFORMATION SYSTEMS

Overview of Systems Development

• Production and maintenance
– System reviewed to determine if revisions needed
– May include post-implementation audit document
– Maintenance
• Changes in hardware, software, documentation, or
procedures to a production system to correct errors,
meet new requirements, or improve processing
efficiency
– 20% debugging, emergency work
– 20% changes to hardware, software, data, reporting
– 60% of work: User enhancements, improving documentation, recoding for greater processing efficiency
17

© Pearson Education 2012

Management Information Systems
CHAPTER 13: BUILDING INFORMATION SYSTEMS

Overview of Systems Development
SUMMARY OF SYSTEMS DEVELOPMENT ACTIVITIES
CORE ACTIVITY

Identify problem(s)
Specify solutions
Establish information requirements

Systems design

Create design specifications

Programming

Translate design specifications into
code

Testing

Unit test
Systems test
Acceptance test

Conversion

Plan conversion
Prepare documentation
Train users and technical staff

Production and
maintenance

18

DESCRIPTION

Systems analysis

Operate the system
Evaluate the system
Modify the system

© Pearson Education 2012

6

6/28/2013

Management Information Systems
CHAPTER 13: BUILDING INFORMATION SYSTEMS

Overview of Systems Development

• Most prominent methodologies for modeling and
designing systems:
1. Structured methodologies
2. Object-oriented development

• Structured methodologies
– Structured: Techniques are step-by-step, progressive
– Process-oriented: Focusing on modeling processes
or actions that manipulate data
– Separate data from processes
19

© Pearson Education 2012

Management Information Systems
CHAPTER 13: BUILDING INFORMATION SYSTEMS

Overview of Systems Development

• Data flow diagram:
– Primary tool for representing system’s component
processes and flow of data between them
– Offers logical graphic model of information flow
– High-level and lower-level diagrams can be used to break processes down into successive layers of detail
• Data dictionary: Defines contents of data flows and data stores • Process specifications: Describe transformation occurring within lowest level of data flow diagrams
• Structure chart: Top-down chart, showing each level of design, relationship to other levels, and place in overall design structure 20

© Pearson Education 2012

Management Information Systems
CHAPTER 13: BUILDING INFORMATION SYSTEMS

Overview of Systems Development
DATA FLOW DIAGRAM FOR MAIL-IN UNIVERSITY REGISTRATION SYSTEM

FIGURE 13-6

21

The system has three processes: Verify availability (1.0), Enroll student (2.0), and Confirm registration (3.0). The name and content of each of the data flows appear adjacent to each arrow. There is one external entity in this system: the student. There are two data stores: the student master file and the course file.

© Pearson Education 2012

7

6/28/2013

Management Information Systems
CHAPTER 13: BUILDING INFORMATION SYSTEMS

Overview of Systems Development
HIGH-LEVEL STRUCTURE CHART FOR A PAYROLL SYSTEM

This structure chart shows the highest or most abstract level of design for a payroll system, providing an overview of the entire system.

FIGURE 13-7

22

© Pearson Education 2012

Management Information Systems
CHAPTER 13: BUILDING INFORMATION SYSTEMS

Overview of Systems Development

• Object-oriented development
– Object is basic unit of systems analysis and design
• Object:
– Combines data and the processes that operate on those data – Data encapsulated in object can be accessed and modified only by operations, or methods, associated with that object

– Object-oriented modeling based on concepts of class
and inheritance
• Objects belong to a certain class and have features of that class
• May inherit structures and behaviors of a more general,
ancestor class
23

© Pearson Education 2012

Management Information Systems
CHAPTER 13: BUILDING INFORMATION SYSTEMS

Overview of Systems Development
CLASS AND
INHERITANCE
This figure illustrates how
classes inherit the common
features of their superclass.
FIGURE 13-8

24

© Pearson Education 2012

8

6/28/2013

Management Information Systems
CHAPTER 13: BUILDING INFORMATION SYSTEMS

Overview of Systems Development

• Object-oriented development
– More iterative and incremental than traditional
structured development
• Systems analysis: Interactions between system and users
analyzed to identify objects
• Design phase: Describes how objects will behave and
interact; grouped into classes, subclasses and hierarchies
• Implementation: Some classes may be reused from existing library of classes, others created or inherited

– Because objects are reusable, object-oriented
development can potentially reduce time and cost of
development
25

© Pearson Education 2012

Management Information Systems
CHAPTER 13: BUILDING INFORMATION SYSTEMS

Overview of Systems Development

• Computer-aided software engineering (CASE)
– Software tools to automate development and reduce
repetitive work, including




Graphics facilities for producing charts and diagrams
Screen and report generators, reporting facilities
Analysis and checking tools
Data dictionaries
Code and documentation generators

– Support iterative design by automating revisions and
changes and providing prototyping facilities
– Require organizational discipline to be used effectively 26

© Pearson Education 2012

Management Information Systems
CHAPTER 13: BUILDING INFORMATION SYSTEMS

Alternative Systems Building Approaches

• Alternative Systems-Building Methods
– Traditional systems life-cycle
– Prototyping
– End-user development
– Application software packages
– Outsourcing

27

© Pearson Education 2012

9

6/28/2013

Management Information Systems
CHAPTER 13: BUILDING INFORMATION SYSTEMS

Alternative Systems Building Approaches

• Traditional systems lifecycle:
– Oldest method for building information systems
– Phased approach divides development into formal
stages
• Follows “waterfall” approach: Tasks in one stage finish before another stage begins

– Maintains formal division of labor between end users
and information systems specialists
– Emphasizes formal specifications and paperwork
– Still used for building large complex systems
– Can be costly, time-consuming, and inflexible
28

© Pearson Education 2012

Management Information Systems
CHAPTER 13: BUILDING INFORMATION SYSTEMS

Alternative Systems Building Approaches

• Prototyping
– Building experimental system rapidly and
inexpensively for end users to evaluate
– Prototype: Working but preliminary version of
information system
• Approved prototype serves as template for final system

– Steps in prototyping
1.
2.
3.

Identify user requirements
Develop initial prototype
Use prototype

4.

Revise and enhance prototype

29

© Pearson Education 2012

Management Information Systems
CHAPTER 13: BUILDING INFORMATION SYSTEMS

Alternative Systems Building Approaches
THE PROTOTYPING
PROCESS
The process of developing a prototype
can be broken down into four steps.
Because a prototype can be developed
quickly and inexpensively, systems
builders can go through several
iterations, repeating steps 3 and 4, to
refine and enhance the prototype before
arriving at the final operational one.
FIGURE 13-9

30

© Pearson Education 2012

10

6/28/2013

Management Information Systems
CHAPTER 13: BUILDING INFORMATION SYSTEMS

Alternative Systems Building Approaches

• Advantages of prototyping
– Useful if some uncertainty in requirements or design
solutions
– Often used for end-user interface design
– More likely to fulfill end-user requirements

• Disadvantages
– May gloss over essential steps
– May not accommodate large quantities of data or
large number of users
• May not undergo full testing or documentation
31

© Pearson Education 2012

Management Information Systems
CHAPTER 13: BUILDING INFORMATION SYSTEMS

Alternative Systems Building Approaches

• End-user development:
– Uses fourth-generation languages to allow end-users
to develop systems with little or no help from
technical specialists
– Fourth generation languages: Less procedural than
conventional programming languages






PC software tools
Query languages
Report generators
Graphics languages
Application generators
Application software packages
Very high-level programming languages

32

© Pearson Education 2012

Management Information Systems
CHAPTER 13: BUILDING INFORMATION SYSTEMS

Alternative Systems Building Approaches

• End-user development (cont.):
– Advantages:
• More rapid completion of projects
• High-level of user involvement and satisfaction

– Disadvantages:
• Not designed for processing-intensive applications
• Inadequate management and control, testing,
documentation
• Loss of control over data

– Managing end-user development
• Require cost-justification of end-user system projects
• Establish hardware, software, and quality standards
33

© Pearson Education 2012

11

6/28/2013

Management Information Systems
CHAPTER 13: BUILDING INFORMATION SYSTEMS

Alternative Systems Building Approaches

• Application software packages
– Save time and money
– Many offer customization features:
• Software can be modified to meet unique requirements without destroying integrity of package software

– Evaluation criteria for systems analysis include:
• Functions provided by the package, flexibility, user friendliness, hardware and software resources, database requirements,
installation and maintenance efforts, documentation, vendor
quality, and cost

– Request for Proposal (RFP)
• Detailed list of questions submitted to packaged-software vendors • Used to evaluate alternative software packages
34

© Pearson Education 2012

Management Information Systems
CHAPTER 13: BUILDING INFORMATION SYSTEMS

Alternative Systems Building Approaches

• Outsourcing
– Several types
• Cloud and SaaS providers
– Subscribing companies use software and computer hardware provided by vendors

• External vendors
– Hired to design, create software
– Domestic outsourcing
» Driven by firms need for additional skills, resources,
assets
– Offshore outsourcing
» Driven by cost-savings
35

© Pearson Education 2012

Management Information Systems
CHAPTER 13: BUILDING INFORMATION SYSTEMS

Alternative Systems Building Approaches

• Outsourcing (cont.)
– Advantages
• Allows organization flexibility in IT needs
– Disadvantages
• Hidden costs, e.g.
– Identifying and selecting vendor
– Transitioning to vendor

• Opening up proprietary business processes to
third party
36

© Pearson Education 2012

12

6/28/2013

Management Information Systems
CHAPTER 13: BUILDING INFORMATION SYSTEMS

Application Development for the Digital Firm

• Rapid application development (RAD)
– Process of creating workable systems in a very short
period of time
– Utilizes techniques such as:
• Visual programming and other tools for building
graphical user interfaces
• Iterative prototyping of key system elements
• Automation of program code generation
• Close teamwork among end users and information
systems specialists
37

© Pearson Education 2012

Management Information Systems
CHAPTER 13: BUILDING INFORMATION SYSTEMS

Application Development for the Digital Firm

• Joint application design (JAD)
– Used to accelerate generation of information
requirements and to develop initial systems
design
– Brings end users and information systems
specialists together in interactive session to
discuss system’s design
– Can significantly speed up design phase and
involve users at intense level

38

© Pearson Education 2012

Management Information Systems
CHAPTER 13: BUILDING INFORMATION SYSTEMS

Application Development for the Digital Firm

• Agile development
– Focuses on rapid delivery of working software by
breaking large project into several small sub-projects
– Subprojects
• Treated as separate, complete projects
• Completed in short periods of time using iteration and
continuous feedback

– Emphasizes face-to-face communication over written
documents, allowing collaboration and faster
decision making
39

© Pearson Education 2012

13

6/28/2013

Management Information Systems
CHAPTER 13: BUILDING INFORMATION SYSTEMS

Application Development for the Digital Firm

• Component-based development
– Groups of objects that provide software for common
functions (e.g., online ordering) and can be combined to
create large-scale business applications
– Web services
• Reusable software components that use XML and open Internet standards (platform independent)
• Enable applications to communicate with no custom
programming required to share data and services
• Can engage other Web services for more complex transactions • Using platform and device-independent standards can result in significant cost-savings and opportunities for collaboration with other companies

40

© Pearson Education 2012

14

Cite this MIS: MANAGING THE DIGITAL FIRM

MIS: MANAGING THE DIGITAL FIRM. (2016, May 05). Retrieved from https://graduateway.com/mis-managing-the-digital-firm/

Show less
  • Use multiple resourses when assembling your essay
  • Get help form professional writers when not sure you can do it yourself
  • Use Plagiarism Checker to double check your essay
  • Do not copy and paste free to download essays
Get plagiarism free essay

Search for essay samples now

Haven't found the Essay You Want?

Get my paper now

For Only $13.90/page