CIS 543: Methods in Information Systems Temple University, CIS Department Spring 2000

1
CIS 543 Methods in Information SystemsTemple
University, CIS DepartmentSpring 2000

• Your Host David Lefkovitz (aka The Instructor)
• Room 315 Wachman Hall
• Telephone [phone]
• E-Mail lefkovitz_at_cis.temple.edu
• Course url ww2.cis.temple.edu/cis543

2
CIS 543 Methods in Information SystemsTemple
University, CIS DepartmentSpring 2000

• A Distance Learning Course
• Textbooks and Tutorials
• Software Tools
• Course Objectives
• Approach
• Grading Basis
• Course Organization

3
CIS 543 Methods in Information SystemsTemple
University, CIS DepartmentSpring 2000

• Case Study
• Enterprise Communications and Systems
• Enterprise Information Systems
• Outline of the 5 Projects
• Project 1 Systems Analysis and Design
• Definitions
• Requirements Statement
• Partial Solution

4
CIS 543 Methods in Information SystemsTemple
University, CIS DepartmentSpring 2000

• A Distance Learning Course
• Textbooks and Tutorials
• Software Tools
• Course Objectives
• Approach
• Grading Basis
• Course Organization

5
CIS 543 Methods in Information SystemsA
Distance Learning Course

• Material available on the Web
• Course Material
• Downloads of software and starter solutions
• 6 Videoconferenced lectures at two sites instead
  of 14 at one site
• Main Campus
• Ambler
• Bring hard copy of indicated web material to
  lecture

6
CIS 543 Methods in Information SystemsA
Distance Learning Course

• Instructor-Class Interaction
• Videoconferenced Lectures (S)
• Bulletin Board (WebBoard) (A)
• E-Mail (A)
• Chat (WebBoard or NetMeeting) (S)
• Application Sharing (NetMeeting) (S)
• S Synchronous, A Asynchronous

7
CIS 543 Methods in Information SystemsA
Distance Learning Course

• Web Access
• Course Material
• URL ww2.cis.temple.edu/cis543

8
CIS 543 Methods in Information SystemsA
Distance Learning Course

• Web Access
• WebBoard
• URL interact.cis.temple.edu/Cis543 Can be
  reached by Class Interaction link in Course
  Material
• First time use Sign in as a new User. Register
  your full name and E-mail address (Follow
  instructions in Home Page)

9
Text Books and Tutorials

• WebBoard
• URL ww2.cis.temple.edu/interact
• Linked from CIS 543 Web Material
• Internal WebBoard Help
• Structured Analysis
• System Architect, A Guided Tour, KC Dittman and
  Popkin Software Systems (includes software)
• Expert Systems
• Developing Knowledge-Based Systems Using
  VP-Expert, D. Dologite, Macmillan, 1993 (includes
  software download)

10
CIS 543 Methods in Information SystemsTemple
University, CIS DepartmentSpring 2000

• A Distance Learning Course
• Textbooks and Tutorials
• Software Tools
• Course Objectives
• Approach
• Grading Basis
• Course Organization
• Case Study

11
Software Tools
12
Software Tools (Contd)
13
CIS 543 Methods in Information SystemsTemple
University, CIS DepartmentSpring 2000

• A Distance Learning Course
• Textbooks and Tutorials
• Software Tools
• Course Objectives
• Approach
• Grading Basis
• Course Organization
• Case Study

14
Course Objectives

• To develop an understanding of the roles that
  various types of Information Systems play in a
  large organization
• To learn how these systems are developed and how
  information must flow through such an
  organization as a result of using these systems.

15
Approach

• The course is based upon a Case Study of the
  information requirements of a manufacturing and
  distributing company named Peerless Electronics.

16
Approach (Contd)Case Study
17
Approach (Contd)Case Study
18
CIS 543 Methods in Information SystemsTemple
University, CIS DepartmentSpring 2000

• A Distance Learning Course
• Textbooks and Tutorials
• Software Tools
• Course Objectives
• Approach
• Grading Basis
• Course Organization
• Case Study

19
Grading Basis

• Solutions to the five projects (100)
• Late projects are downgraded by one letter grade
• Class participation (Extra Credit)
• No exams

20
Course Organization
21
Course Organization (Contd)
22
Course Organization (Contd)
23
CIS 543 Methods in Information SystemsTemple
University, CIS DepartmentSpring 2000

• Case Study
• Enterprise Communications and Systems
• Enterprise Information Systems
• Outline of the 5 Projects
• Project 1 Systems Analysis and Design
• Definitions
• Requirements Statement
• Partial Solution

24
Case StudyPeerless Organization Chart
25
Enterprise Communications and Systems- Physical -

• External
• Long distance toll
• Long distance leased or owned (WAN,Cable)
• Local toll
• Local leased (MAN,Cable)
• Internal
• Local telephone
• LAN

26
Enterprise Communications and Systems-
Functional -

• External and Internal
• Voice and Voice-Mail
• E-Mail
• FAX
• Videoconference
• Hand carried mail
• Internet/Intranet
• Text, Audio, Video (TCP/IP, HTTP, IIOP)
• File transfer (FTP)
• Electronic Data Interchange (EDI)
• Electronic Funds Transfer (EFT)

27
(No Transcript)
28
Enterprise Communications and Systems-
Application Server -

• TPS, MIS
• DSS, OLAP, Data Warehousing
• Office Automation
• WP, Spreadsheet, Database management
• Graphics, Slides, Web Authoring
• Address Book, Calendar
• Asynchronous Collaboration
• E-Mail, Listserve, Bulletin Board
• Synchronous Collaboration (eg, NetMeeting)
• Chat (Textual, Audio, Video)
• AP Sharing

29
Enterprise Information Systems

• Transaction Processing System (TPS)
• Management Information System (MIS)
• Decision Support System (DSS)

30
Enterprise Information Systems

• Transaction Processing System (TPS)
• Supports the day to day operational needs of the
  enterprise.
• Maintains a corporate database via transactions.
• Database used to generate operational and
  management reports and to control various
  operational functions.

31
Enterprise Information Systems

• Management Information System (MIS)
• Generates reports from DB maintained by TPS.
• Reports satisfy predictable information needs.
• Produced periodically or on demand.
• May include a general purpose Inquiry system to
  provide information that is less predictably
  needed, but which fits patterns that conform to
  the database structure.

32
Enterprise Information Systems

• Decision Support System (DSS)
• Any information gathering and producing facility
  that aids in decision making, typically
  strategic.
• DSS is the counterpart to MIS. It provides ad hoc
  management reports that are usually not
  predictable and tend to be more logically or
  mathematically complex.

33
Enterprise Information Systems Decision
Support System (Contd)

• Many different software techniques and packages
  are required.
• Statistics, Operations Management (formerly
  Operations Research (OR))
• Linear Programming, Dynamic Programming
• Queuing Theory
• Fuzzy Logic
• Artificial Intelligence, Expert Systems (ES)

34
Enterprise Information Systems Decision
Support System (Contd)

• Data Warehousing
• The Database is often restructured and/or
  augmented with external databases. Large amounts
  of historical data are drawn from the corporate
  database and restructured for more efficient and
  flexible retrieval.
• Data Mining or OnLine Analytic Processing (OLAP)
• Various mathematical, analytic techniques are
  made available in a convenient package form.

35
Enterprise Information Systems Decision
Support System (Contd)

• Internet
• Research support from a vast manifold of public,
  but uncontrolled, data sources.

36
CIS 543 Methods in Information SystemsTemple
University, CIS DepartmentSpring 2000

• Case Study
• Enterprise Communications and Systems
• Enterprise Information Systems
• Overview of the 5 Projects
• Project 1 Systems Analysis and Design
• Definitions
• Requirements Statement
• Partial Solution

37
Overview of the 5 Projects
38
Project 1 Systems Analysis and Design

• The Systems and Software Development department
  would perform this task. The clients are Sales
  and Production. An integrated TPS is to be
  developed for these clients. The functions to be
  performed by the system are Order Entry,
  Invoicing, Purchase Orders, Payment Receipt,
  Inventory Control, Production Planning, and
  Receivables tracking.
• The methodolgy to be used is Structured Analysis
  the software tool is System Architect.

39
Project 2 Product Planning Report

• The DSS Analysis department would produce this
  report for the Product Planning and Marketing
  department. It will be a web authored report
  based upon web searching that will (1) determine
  who is the competition and (2) find new personal
  applications for GPS and other information
  oriented products employing microelectronics.
• The software tools to be used are any web browser
  and a web authoring tool.

40
Project 3 Cash Flow Model

• The DSS Systems Development department would
  produce this software model for the Finance
  department, who will use the model to perform
  their own analyses of projected cash flow. One
  purpose would be to approach financial
  institutions or investors for capitalization of
  expansion or a new venture.
• The software tool to be used is Excel with
  financial and logical functions.

41
Project 4 Credit Analysis by an Expert
System

• The DSS Systems Development department would
  produce this expert system application for the
  Credit department, who will use it to determine
  whether and how much credit to extend to new or
  existing customers.
• The software tools to be used are an Expert
  System shell called VP Expert and Access, FoxPro,
  Paradox or DBase.

42
Project 5 Production Quality Control Report

• The DSS Analysis department would produce this
  report for the Production department. It will
  employ an operations management tool called
  factor analysis to determine which factors in the
  production process are most responsible for
  defects.
• The software tool to be used is Excel with
  statistical functions.

43
Strategy for Working on Projects

• The projects are fairly independent, so the best
  strategy is to work on several at a time,
  starting with the first. In this way, you can
  work on another project while waiting for a
  response to a critical question.
• An asynchronous WebBoard response may take a day
  or two, and the next videoconferenced lecture may
  be a week or two off.

44
(No Transcript)
45
CIS 543 Course Web Map

• Home Page
• Syllabus
• Term Case Study
• Peerless Organization Chart
• Course Organization
• Project 1 Systems Analysis
• Requirements
• Description of Analysis
• Project 2 Product Planning
• Project 3 Cash Flow Model
• Model Application
• Project 4 Credit Analysis ES
• Project 5 Quality Control

46
CIS 543 Methods in Information SystemsTemple
University, CIS DepartmentSpring 2000

• Case Study
• Enterprise Communications and Systems
• Enterprise Information Systems
• Overview of the 5 Projects
• Project 1 Systems Analysis and Design
• Definitions
• Requirements Statement
• Partial Solution

47
Definitions

• Enterprise
• An Enterprise is a corporate entity that has a
  defined purpose and objective along with a set of
  functions intended to achieve the objective.

48
Definitions

• Business Unit
• A Business Unit is a subunit of an enterprise.
  It is primarily defined by a subset of the
  enterprise functions, although business units may
  have functions in common. Business units are
  often categorized with respect to their position
  in the corporate hierarchy, as division,
  department, branch, group, etc.

49
Definitions

• System
• People
• Hardware or Equipment
• Procedures for carrying out designated functions
  of the people or hardware. When the hardware is a
  computer, we call the Procedures a program or
  software.
• Reference information utilized by the people or
  hardware in the conduct of their functions. When
  the hardware is a computer, we call the Reference
  information a database.

50
Definitions

• Systems Analysis
• Analysis is sometimes called Requirements
  Specification or Specification.
• It is an expression of what functions the system
  is to perform and how various components of the
  system are related to each other.

51
Definitions

• Systems Analysis (Contd)
• The objective of this expression is to be
  complete, unambiguous, consistent and as concise
  as possible. In this regard, natural language may
  be a disadvantage
• Graphical methods combined with minimal use of
  natural language are ideal. A methodology used
  for this purpose is Structured Analysis, which
  uses a tool called the Dataflow diagram.

52
Definitions

• Systems Design
• Design is an expression of how the system is to
  be implemented or constructed.
• Systems design starts by allocating the various
  System or Business Unit functions to one or a
  combination of the four system components
  people, hardware, procedures, and reference
  information.
• The process is then iterated. Each allocated
  component is then further specified and designed.

53
Definitions

• System Development Lifecycle
• Requirements Statement
• Specification
• Design
• Implementation (construction)
• Integration and Test
• Startup
• Operation
• Maintenance

54
Definitions

• System Development Lifecycle (Contd)
• Both the system and its components are subject
  to this multistage development lifecycle
• Each stage produces its own specific documents
  and artifacts. There is normally feedback from
  one stage to one or more of its predecessors for
  the purpose of clarification, completion or
  correction of mistakes uncovered in the successor
  stage.

55
CIS 543 Methods in Information SystemsTemple
University, CIS DepartmentSpring 2000

• Case Study
• Enterprise Communications and Systems
• Enterprise Information Systems
• Overview of the 5 Projects
• Project 1 Systems Analysis and Design
• Definitions
• Requirements Statement
• Partial Solution

56
Sales Department

• Customer Service
• Order entry
• Billing and Payments
• Send invoices to customer
• Receive and post payments
• Send checks and deposit slip to bank
• Credit
• Process customer credit requests
• Collections
• Send collection notices to customers, based upon
  Aged AR Report

57
Production Department

• Purchasing
• Send purchase orders to vendors, based upon Bill
  of Materials Report that results from Order
  Entry. Send BOM to Assembly.
• Warehouse
• Receive Vendor Shipment.
• Assembly
• Assemble products and ship to customer.

58
DSS Department

• Systems Development
• Develop Cash Flow Model for Finance Department
• Develop Credit Analysis ES for Credit Department
• Analysis
• Perform Quality Control analysis for Production
  department.
• Perform New Product analysis for Product Planning
  and Mktg department.

59
Finance Department

• Prepare a Capital Requirements Portfolio(1)
  Financial Reports (Income and Balance
  Sheet)(2) Aged Accounts Receivable Report(3)
  Cash Flow Projection
• Seek new capital for new products using the
  Capital Requirements Portfolio
• Deposit acquired loans or investment

60
CIS 543 Methods in Information SystemsTemple
University, CIS DepartmentSpring 2000

• Case Study
• Enterprise Communications and Systems
• Enterprise Information Systems
• Overview of the 5 Projects
• Project 1 Systems Analysis and Design
• Definitions
• Requirements Statement
• Partial Solution

61
Project 1 Submission

• Transfer SA diagrams to individual web pages
• Create a diagrammatic or textual index linked to
  the web page diagrams.
• Publish to your Web Server and send url.
• Detailed instructions on how to do this are in
  the Web Notes

62
Project 2 Product Planning ReportPurpose

• To find new consumer microelectronic products to
  produce
• To determine the competition
• Method of Research and Presentation
• Web Search and Web Document Authoring

63
Project 2 Product Planning ReportSoftware
Requirement

• Web browser (Netscape, Explorer)
• Search engine
• Web Authoring tool
• Front Page
• Netscape Composer
• Word
• Others
• Web Site (Server)

64
Project 2 Product Planning ReportConstruction
and Content

• Extracted descriptions and graphics
• Linked descriptions and graphics
• For Competitors
• Products
• Company location and description
• Financial data
• Media articles and company press releases
• Own comments and recommendations

65
Project 2 Product Planning ReportSubmission

• E-mail the url to the Instructor

66
Project 2 Product Planning ReportDocument
Organization

• Title and Table of Contents with links to
  sections in the report
• Introduction
• Proposed products
• Competition
• Conclusions and Recommendations