Your SlideShare is downloading. ×
Information Systems Analysis and Design
Upcoming SlideShare
Loading in...5
×

Thanks for flagging this SlideShare!

Oops! An error has occurred.

×
Saving this for later? Get the SlideShare app to save on your phone or tablet. Read anywhere, anytime – even offline.
Text the download link to your phone
Standard text messaging rates apply

Information Systems Analysis and Design

2,599

Published on

0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total Views
2,599
On Slideshare
0
From Embeds
0
Number of Embeds
0
Actions
Shares
0
Downloads
80
Comments
0
Likes
0
Embeds 0
No embeds

Report content
Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
No notes for slide

Transcript

  • 1. Information Systems Analysis and Design
  • 2. Chapter Contents
    • Section A: Information Systems
    • Section B: Systems Analysis
    • Section C: System Design
    • Section D: Implementation and Maintenance
  • 3. Section A: Information Systems
    • Information Systems in Organizations
    • Transaction Processing Systems
    • Management Information Systems
    • Decision Support Systems
    • Expert Systems and Neural Networks
  • 4. Information Systems in Organizations
    • An information system collects, stores, and processes data to provide useful, accurate, and timely information
    • An organization is a group of people working together to accomplish a goal
      • Business
      • Nonprofit organization
      • Mission
        • Mission statement
  • 5. Information Systems in Organizations
    • Organizational charts depict the hierarchy of employees in an organization
  • 6. Information Systems in Organizations
    • Information systems can:
      • Automate routine tasks
      • Solve problems
        • Structured problem
        • Semi-structured problem
        • Unstructured problem
      • Collect and store internal or external information
  • 7. Transaction Processing Systems
    • Provides a way to collect, process, store, display, modify, or cancel transactions
      • Point-of-sale systems
      • General accounting systems
      • Payroll systems
      • Order-entry / invoice systems
    • Batch processing vs. online processing
      • OLTP system
    • Detail reports
  • 8. Transaction Processing Systems
    • A transaction processing system (TPS) is characterized by
    • its ability to:
    • Collect, display, and modify transactions
    • Store transactions
    • List transactions
    • CLICK TO START
  • 9. Management Information Systems
    • A management information
    • system is characterized by its ability to:
    • Produce routine and on-demand reports
    • Provide useful information for managerial activities
    • Increase managerial efficiency
    • Provide information used for structured, routine decisions
    • CLICK TO START
  • 10. Management Information Systems
  • 11. Decision Support Systems
    • Helps people make decisions by directly manipulating data, analyzing data from external sources, generating statistical projections, and creating data models of various scenarios
      • Executive information system
    • DSSs design decision models and make decision queries
  • 12. Decision Support Systems CLICK TO START
  • 13. Expert Systems and Neural Networks
    • Expert systems are designed to analyze data and produce a recommendation, diagnosis, or decision based on a set of facts and rules
      • Knowledge base
        • Inference engine
        • Knowledge engineering
      • Expert system shell
      • Fuzzy logic
    • A neural network uses computer circuitry to simulate the way a brain might process information, learn, and remember
  • 14. Expert Systems and Neural Networks
    • An expert system is characterized by its ability to:
    • Replicate the reasoning of a human expert
    • Work with internal or external data
    • Produce a recommendation or decision
    • CLICK TO START
  • 15. Section B: Systems Analysis
    • System Development Life Cycle
    • Planning Phase
    • Project Justification
    • Analysis Phase
    • System Requirements
  • 16. System Development Life Cycle
    • Waterfall SDLC
  • 17. System Development Life Cycle
    • Modified waterfall SDLC
    • Iterative SDLC
  • 18. Planning Phase
    • Create a Project Development Plan
    • Project management software
    • Joint application design (JAD)
  • 19. Project Justification
    • Usually emerges from a serious problem with the current system
    Michael Porter’s Five Forces model illustrates the factors that affect competition among business rivals. CLICK TO START
  • 20. Project Justification
    • An organization must be able to:
      • Make improvements
      • Change the industry
      • Create new products
    • The PIECES framework helps classify problems in an information system
  • 21. Project Justification
    • Development methodologies
      • Structured methodology
      • Information engineering methodology
      • Object-oriented methodology
      • Rapid application development
  • 22. Analysis Phase
    • Produce a list of requirements for a new or revised information system
    • Analysis phase activities
      • Study the current system
      • Determine system requirements
      • Write requirements report
  • 23. Analysis Phase
  • 24. System Requirements
    • Criteria for successfully solving problems identified in an information system
      • Success factors
    • A CASE tool can:
      • Document system requirements
      • Diagram current and proposed information systems
      • Schedule development tasks
      • Develop computer programs
  • 25. System Requirements CASE tools help project team members manage all the details of system documentation. In this example, the project team is defining fields for the Inventory object depicted on the diagram. CLICK TO START
  • 26. System Requirements
    • A System Requirements Report describes the objects for an information system
  • 27. Section C: System Design
    • Design Phase
    • Evaluation and Selection
    • Application Specifications
  • 28. Design Phase
    • The project team must figure out how the new system will fulfill the requirements in the specified in the System Requirements Report
  • 29. Design Phase
    • Consider the following when evaluating hardware alternatives
      • Level of automation and computerization
      • Processing methodology
        • Centralized processing
        • Distributed processing
      • Network technology
  • 30. Design Phase
    • Software alternatives
      • Programming language
      • Application development tool
      • Commercial software
      • Turnkey system
  • 31. Evaluation and Selection
    • Decision support worksheet
  • 32. Evaluation and Selection
    • A request for proposal (RFP) describes the information system problem and the requirements for the solution
  • 33. Evaluation and Selection
    • A request for quotation (RFQ) is a request for a formal price quotation on a list of hardware and software
  • 34. Application Specifications
    • Describe the way the information system’s software should interact with users, store data, process data, and format reports
    • Feature creep refers to the failure to constrain change
    • Changes should be managed formally, including written change requests
  • 35. Section D: Implementation and Maintenance
    • Implementation Phase
    • Development and Testing
    • Documentation and Training
    • Conversion and Cutover
    • Maintenance Phase
  • 36. Implementation Phase
    • Project team supervises the tasks necessary to construct the new information system
  • 37. Development and Testing
    • Software customization is the process of modifying a commercial application to reflect an organization’s needs
    • Application testing is performed in three ways:
      • Unit testing
      • Integration testing
        • Test area
      • System testing
  • 38. Development and Testing
  • 39. Documentation and Training
    • System documentation
      • Describes a system’s features, hardware architecture, and programming
    • User documentation
      • Describes how to interact with the system to accomplish specific tasks
      • Procedure handbook
        • Contains step-by-step instructions for performing specific tasks
  • 40. Conversion and Cutover
    • System conversion
      • Deactivating an old information system and activating a new one
      • Several conversion strategies:
        • Direct conversion
        • Parallel conversion
        • Phased conversion
        • Pilot conversion
    • Acceptance testing is designed to verify that the new information system works as required
  • 41. Maintenance Phase
    • Involves day-to-day operation of the system, making modifications to improve performance, and correcting problems
    • Security is a top priority as well as an ongoing activity
  • 42. Maintenance Phase
    • The system operator is responsible for operating the computer on a day-to-day basis
    • The systems programmer installs new versus of the operating system and modifies settings to maximize performance
    • The help desk is staffed by technical support specialists who are familiar with the information system and record problems and solutions
  • 43. Maintenance Phase
    • Maintenance phase costs

×