INTRODUCTION TO

1
SYSTEMS ANALYSIS DESIGN

• INTRODUCTION TO
• INFORMATION SYSTEMS
• Shelly Cashman Rosenblatt

2
Chapter 1
Introduction to Information Systems
3
Objectives

• Describe an information system and explain its
  components and characteristics
• Explain how different levels of a business
  organization use and handle information
• Describe the phases and objectives of the systems
  development life cycle

4
Objectives

• Explain the use of software tools in the
  development of information systems
• List the major functions performed by the
  information systems department
• Discuss a systems analysts responsibilities,
  skills, and opportunities

5
Objectives

• Identify six common business information systems
  and describe their primary features

6
Introduction

• Why do businesses depend on computers more than
  ever?
• Global competition
• Intense pressure for quality
• Information technology can mean the difference
  between survival and failure

7
Introduction

• What is required for successful business
  information systems?
• The right hardware and software
• A team of talented, motivated people who use
  information technology to achieve business goals

8
Introduction

• IBM summed it up this way
• Knowledge Management
• Calls for a New Way of Thinking

9
Introduction

• IBM study cited 4 basic rules for success in the
  new marketplace
• The customer always is right
• Skilled employees create happy customers
• The organization and its information systems must
  reflect customer expectations not the other way
  around
• Information technology will be the essential
  factor in determining success

10
Systems and Procedures

• Procedures specify how the work must be done

11
Systems and Procedures

• Procedures specify how the work must be done
• A system is a group of related procedures for a
  specific business function

12
Systems and Procedures

• Procedures specify how the work must be done
• A system is a group of related procedures for a
  specific business function
• Data is basic facts that are the system's raw
  material

13
Systems and Procedures

• Procedures specify how work must be done
• A system is a group of related procedures for a
  specific business function
• Data is basic facts that are the system's raw
  material
• Processing transforms input into accurate,
  meaningful business information

14
Information System Components

• Hardware
• Software
• Data
• Procedures
• People

15
Information System Components

• Hardware is the physical layer of the information
  system

16
Information System Components

• Software
• System software controls the hardware and
  software environment and includes the operating
  system
• Application software consists of programs that
  that process data to produce information

17
Information System Components

• Data stored in files and databases is a vital
  component of every system

18
Information System Components

• Procedures define the tasks that must be
  performed by users, managers, and IS staff

19
Information System Components

• People who use the system are called users, or
  end users, and include employees, customers,
  vendors, or others who interact with the system

20
Business Information Systems

• Companies are classified based on their main
  activities
• Production-oriented (industrial ) companies that
  manufacture sell goods
• Service companies that mainly offer information,
  services, or sell goods made by others
• Combined industrial service companies

21
Business Information Systems

• Characteristics of business information systems
• 4 main characteristics affect a business
  information systems complexity
• Relationships with other systems
• Boundaries
• Specialized business needs
• Size of the company

22
Types of Information Systems

• Operational systems
• Management information systems
• Decision support systems
• Executive information systems
• Expert systems
• Office systems

23
Types of Information Systems

• Operational systems process data generated by
  day-to-day business transactions

24
Types of Information Systems

• Management information systems generate timely
  and accurate information for top, middle, and
  lower managers

25
Types of Information Systems

• Decision support systems help managers make
  business decisions by analyzing data and
  providing a what-if model

26
Types of Information Systems

• Executive information systems support information
  requirements of top-level managers who make
  unstructured decisions

27
Types of Information Systems

• Expert systems simulate human reasoning and
  decision-making using a knowledge base and
  inference rules
• Office systems are used by knowledge workers

28
Types of Information Systems

• Elements include
• Local and wide area networking
• Electronic mail, voice mail, and fax
• Video conferencing, word processing, automated
  calendars, electronic filing
• Database management, spreadsheets, desktop
  publishing, presentation graphics
• Company intranets, and Internet access throughout
  the company

29
Organizational Levels

• Four organizational levels
• Operational personnel
• Lower management
• Middle management
• Top management

30
Organizational Levels

• Four organizational levels
• Operational personnel
• Lower management
• Middle management
• Top management
• Responsibilities, decision-making styles, and
  information system requirements

31
Organizational Levels

• Four organizational levels
• Operational personnel
• Lower management
• Middle management
• Top management
• Responsibilities, decision-making styles, and
  information system requirements
• Empowerment of operational personnel

32
Systems Development Life Cycle

• Systems planning
• Systems analysis
• Systems design
• Systems implementation
• Systems operation and support

33
Systems Development Life Cycle

• Systems planning
• Preliminary investigation report
• Systems analysis
• System requirements document
• Systems design
• System design specification
• Systems implementation
• Complete functioning information system
• Systems operation and support
• Operational information system

34
Systems Development Life Cycle

• Systems planning
• Purpose identify problems nature/scope
• Systems request begins the process describes
  desired changes/improvements
• Systems planning includes preliminary
  investigation or feasibility study
• End product preliminary investigation report

35
Systems Development Life Cycle

• Systems analysis
• Purpose is to learn exactly how the current
  system operates
• Fact-finding or requirements determination is
  used to define all functions of the current system

36
Systems Development Life Cycle

• Options
• Develop a system in-house
• Purchase a commercial package
• Modify an existing system
• Stop development
• The end product for this phase is the systems
  requirements document

37
Systems Development Life Cycle

• Systems design
• Purpose is to satisfy all documented requirements
• Identify all outputs, inputs, files, manual
  procedures, application programs
• Avoid misunderstanding through manager and user
  involvement
• End product is system design specification

38
Systems Development Life Cycle

• Systems implementation
• Construct/deliver information system
• Prepares functioning, documented system
• Write, test, document application programs
• User and manager approval obtained
• File conversion occurs
• Users, managers, IS staff trained to operate and
  support the system
• Post-implementation evaluation performed

39
Systems Development Life Cycle

• Systems operation and support
• New system supports business operations
• Maintenance changes correct errors or meet
  requirements
• Enhancements increase system capability
• After several years of operation, systems
  experience need for extensive changes
• Systems development life cycle ends with system
  replacement

40
Systems Development Life Cycle

• General considerations
• Complete the phases in sequence
• Focus on end products
• Estimate required resources

41
Systems Development Life Cycle

• Automated tools for systems development
• Software tools
• Prototypes
• Computer-aided software engineering (CASE)

42
TRADEOFF

• Is it better to have more or fewer phases in the
  SDLC?
• More phases can result in more checkpoints, end
  products, and work
• Fewer phases can result in less cost and faster
  development time
• Success really depends on the skills and
  motivation of the development team

43
A KEY QUESTION

• Should Mommas, a small chain of 12 bed and
  breakfast inns, adopt the SDLC process of Global
  Hotels, a large multinational hotel company?

44
Information Systems Department

• Operations group responsible for centralized
  computers and processing
• Technical support group installs and supports
  systems software and serves in an advisory and
  support capacity to other groups in the IS
  department

45
Information Systems Department

• Applications group analyzes, designs, programs,
  tests, installs, and maintains the companys
  information systems
• Information center (IC) provides users with
  technical resources, information, and support

46
The Systems Analyst Position

• Responsibilities
• Required skills and background
• Career opportunities

47
TRADEOFF

• As a systems analyst, is working at a small or
  large company better for you?
• Points to consider
• Professional growth and experience
• Corporate culture
• Variety in assignments
• Amount of responsibility
• Salary, location, and companys prospects

48
A KEY QUESTION

• Which job offer should Lisa Jameson choose?
• Pembroke Boats
• Small boat-building firm
• Located in small town
• Lisa would create a new IS department

49
A KEY QUESTION

• Albemarle Express
• Nationwide trucking company headquartered in
  Detroit
• Higher salary
• Lisa would start as programmer/analyst
• Opportunity to become systems analyst
• Acquisition rumors

50
SOFTWEAR, LIMITED

• Background and history
• Company organization chart
• IS department structure

51
SOFTWEAR, LIMITED

• Background and history
• Manufactures and sells casual and recreational
  clothing
• Formed in 1991
• 250 million total 1997 sales
• Total of 450 employees
• California Texas manufacturing plants
• 125 people work at SWLs headquarters in Raleigh,
  N.C.
• SWL maintains a Web site

52
SOFTWEAR, LIMITED

• Company organization chart
• President, Robert Lansing four direct reports
• Vice President Operations, David Josephs
• Vice President Marketing, Amy Neal
• Vice President Finance, Michael Jeremy
• Vice President Human Resources, Tina Pham

53
SOFTWEAR, LIMITED

• Company organization chart
• President, Robert Lansing four direct reports
• Vice President Operations, David Josephs
• Vice President Marketing, Amy Neal
• Vice President Finance, Michael Jeremy
• Director of Information Systems, Ann Hon, reports
  to the Vice President Finance, Michael Jeremy
• Vice President Human Resources, Tina Pham

54
SOFTWEAR, LIMITED

• IS department structure
• Director of Information Systems, Ann Hon, has
  three direct reports
• Manager Applications, Jane Rossman
• Manager Tech Support, Kerry Krauss
• Manager Operations, Gene Talkington