This is my school homework, Lecture notes of Marketing Business-to-business (B2B)

Download This is my school homework and more Lecture notes Marketing Business-to-business (B2B) in PDF only on Docsity!

Moving into Design

CORRESPONDING TO CHAPTER 7 OF “SYSTEMS ANALYSIS

AND DESIGN,” BY DENNIS, WIXOM, AND ROTH

Learning Objectives

Explain what happens during the design phase.

Describe three ways to acquire a system: custom,

packaged, and outsourced alternatives.

Understand the pros and cons of each acquisition strategy,

along with factors affecting the decision and tools used

during acquisition.

Key Ideas

In Systems Analysis we figure out…

o

What the business needs

In System Design we figure out…

o

How to build the system that fulfills those needs

All of the “logical” work from Systems Analysis is

converted to the “physical”

Key Definitions

Design phase

o

Decide how to build the system

o

Refine and specify details of system requirements that describe all

technical details for building the system

System specification

o

Final deliverable from design phase

o

Conveys exactly what system the development team will implement

during the implementation phase

Elements of

System

Specification

System Acquisition

Strategies

WHAT IS THE BEST WAY TO ACQUIRE THIS SYSTEM?

What are the pros and cons of each

acquisition strategy?

See if you can think of some before I show them on the slides

(Group activity – each group is assigned one of the next 6 slides)

Separate PPT file with pros and cons will be available on

TITANium after class

Custom Development – Pros

Get exactly what we want

New system built consistently with existing technology and

standards

Build and retain technical skills and function knowledge in-

house

Allows team flexibility and creativity

Unique solutions created for strategic advantage

Purchased Software – Pros

No need to “reinvent the wheel” for common business

needs

Tested, proven product

Cost savings

Time savings

Utilize vendors’ expertise

Some customization may be possible

Purchased Software – Cons

Rarely a perfect fit

Organizational processes must adapt to software

Reliance on vendor for maintenance and future

enhancements

Won’t develop in-house functional and technical skills

Unique needs may go unmet

May require system integration

Outsourced Development – Cons



No opportunity to build in-house expertise



Reliance on vendor



Future options limited



Security – potential loss of confidential information



Performance based on contract terms

Selecting an Acquisition

Strategy

HOW DO WE CHOOSE?

In-class Discussion

"Concepts in Action 7-D: Building a Custom System--With

Some Help“

p. 227 in 6th ed, p. 268 in 5th ed.

Read the case and answer the questions posed at the end of

this text box.

Developing Our Options



Need to collect information about resources available for

each acquisition option

o

For custom development: What tools and technologies are needed

for a custom development project?

o

For pre-packaged software: What vendors make products that

address the project needs?

o

For outsourcing: What service providers would be able to build this

application if outsourced?