Академический Документы
Профессиональный Документы
Культура Документы
Suarez-Brown
Chapter 1
The Systems Development Environment
1.1
Learning Objectives
Define information systems analysis
and design Discuss the modern approach to systems analysis and design Describe the organizational roles involved in information systems development
1.2
Learning Objectives
Describe four types of information systems:
Transaction Processing Systems (TPS) Management Information Systems (MIS) Decision Support Systems (DSS) Expert Systems (ES)
Learning Objectives
Discuss alternatives to the systems
development life cycle Discuss the role of computer-aided software engineering (CASE) tools in systems development
1.4
Introduction
Information Systems Analysis and Design
Complex process whereby computer-based information systems are developed and maintained Driven from an organizational prospective
Process of creating, producing, and supporting the
Understanding of organizations objectives, Structure, Processes, Knowledge of how to exploit information technology for advantage
1.5
Introduction
Application Software
Result of systems analysis and design Designed to support specific organizational functions or processes
Inventory management, payroll, or market analysis
Introduction
Information System
Set of interrelated components that collect (or retrieve), process, store, and distribute information to support decision making, coordination and control in an organization Hardware Software Documentation Training Materials Job Roles associated with overall system Controls People
Information System
INPUT
PROCESS
OUTPUT
FEEDBACK STORAGE
Introduction
Software engineering processes have been developed to assist in analysis and design Developed work methods to become a disciplined process
Methodologies
Comprehensive, multi-step approaches to systems
development Consistent with general management style Incorporate several development techniques
Techniques
Processes that are followed to ensure that work is well
1.6
Introduction
Tools
Computer programs to assist in application of techniques
Tools and techniques must be consistent with an organizations systems development methodology The organizational role most responsible for the analysis and design of information systems Study the problems and needs of an organization in order to determine how people, methods, and information technology can best be combined to bring about improvement in the organization
Systems Analyst
Introduction
Information Systems Analysis and Design
Began in the 1950s A method used by companies to create and maintain systems that perform basic business functions Main goal is to improve employee efficiency by applying software solutions to key business tasks A structured approach must be used in order to ensure success
1.7
Introduction
Systems Analyst performs analysis and design based upon:
Understanding of organizations objectives, structure and processes Knowledge of how to exploit information technology for advantage
1.8
Methodologies
A sequence of step-by-step approaches that help
Techniques
Processes that the analyst follows to ensure thorough,
Tools
Computer programs that aid in applying techniques
1.11
Information
Derived from data Organized in a manner that humans can
1.15
understand
Understanding the source and use of data is key to good system design Various techniques are used to describe data and the relationship amongst data Groups of data that move and flow through the system
Data Flows
1.16
Include description of sources and destination for each data flow Describe steps that transform data and events that trigger the steps
Processing Logic
1.17
1.19
Depicts ideal organization of data, independent of where and how data are used Data model describes kinds of data and business relationships among the data Business rules depict how organization captures and processes the data
1.20
Focuses on the data the system needs to operate Data redundancy controlled; data files designed for whole enterprise
Traditional Approach
Database Approach
Key Differences
Shared collection of logically related data Organized to facilitate capture, storage and retrieval by multiple users Centrally managed Designed around subjects
Customers Suppliers
Application Independence
1.23
IS Manager Programmers Users Other specialists Diversity of backgrounds Tolerance of diversity Clear and complete communication Trust Mutual Respect Reward structure that promotes shared responsibility
1.24
May have a direct role in systems development if the project is small Typically involved in allocating resources to and overseeing system development projects. Key individuals in the systems development process
Systems Analyst
Analytical
Understanding of organizations, functions, identify
opportunities and problems, analyze and solve problems Problem solving skills System thinking
Ability to see organizations and information systems as systems View important relationships among IS, organization they exist in, and the environment in which the organizations exist
Technical
Understanding of potential and limitations of technology Guide the systems design and development Work with Programming languages, Operating Systems
1.26
Management
Ability to manage projects, resources, risk and change
Interpersonal
Effective written and oral communication skills Work with end-users, other analysts and programmers Major role as a liaison among users
Convert specifications into instructions that the computer understands Write documentation and testing programs Structured Programming
All computing instructions represented through three
structures:
Sequence, repetition, and selection Code generators, Computer-Aided Software Engineering (CASE)
Business Managers
1.28
Have power to fund projects and allocate resources Set general requirements and constraints for projects
Database Administrator
Involved in design, development and maintenance of
databases
communications
Internal Auditors
Ensure that required controls are built into the system Keeping track of changes in the systems design
1.29
GROUPS SERVED
SENIOR MANAGERS
MANAGEMENT LEVEL
MIDDLE MANAGERS
KNOWLEDGE LEVEL
OPERATIONAL LEVEL
SALES & MARKETING MANUFACTURING FINANCE ACCOUNTING
OPERATIONAL MANAGERS
HUMAN RESOURCES
Automate and support handling of data about elementary organizational business activities (transactions) Systems answer routine questions and track the flow and processing of transactions through the organization i.e. systems to record bank deposits, customer order processing, employee timekeeping, scheduling Goal:
Improve transaction processing (speed) Use fewer people Improve efficiency and accuracy Integration
1.32
Converts raw data from transaction processing system into meaningful form Provide managers with reports or with on-line access to the organization Provide Periodic reports or summaries of data Often required data from several TPS i.e. relocation control systems
Quarterly or Bi-Annual Reports Aggregate and Summarize data Understand relationships between data to ultimately be summarized
MIS
MIS
REPORTS
Total amount of particular item used this quarter Compare total annual sales figures for specific products to planned targets
1.35
comparative sales figures between one period and the next, projected revenue figures based on product sales assumptions
Knowledge representation describes the way an expert would approach the problem
Interactive dialogue: ES asks questions, user supplies
answers, answers used to determine which rules apply and then ES provides a recommendation based on rules
Help senior management tackle and address strategic issues and long-term trends, both in the firm and external environment Where will employment levels be in ten years?, etc. What is the five year operating plan?
Orderly set of activities conducted and planning for each development project Standard process followed in an organization Consists of:
Project Identification and selection Project Initiation and planning Analysis Design Implementation Maintenance
1.37
in another phase Iterative: phases are repeated as required until acceptable Spiral: constantly cycle through phases at different levels of detail Circular: end of useful life of one system leads to the beginning of another project
Project Identification and Selection Project Initiation and Planning Analysis Design Implementation Maintenance
1.38
Phases are not necessarily sequential Each phase has a specific outcome and deliverable Individual companies use customized life cycles
1.39
schedule
Helps organization to determine whether or not resources should be dedicated to a project. Two Activities
Develop system to solve problem
Formal preliminary investigation of the problem at hand Presentation of reasons why system should or should not
Study of current procedures and information systems used to perform organizational tasks
Determine requirements Determine what users want from proposed system Study current system Structure requirements and eliminate redundancies Generate alternative designs to match requirements Compare alternatives and determine which best meets
the requirements within limits (cost, labor, technical levels) Recommend best alternative
1.41
Devoted to designing the new or enhanced system Convert description or solution into logical and then physical systems specifications Logical Design
Concentrates on business aspects of the system its
Physical Design
Technical specifications Design various parts of system to perform the physical
1.42
operations necessary to facilitate data capture, processing, and information output Determine physical details necessary to build final system Final product: physical system specifications ready to be turned over to programmers and other systems builders for construction
Turn systems specifications into working system that is tested and then put into use Coding, testing and installation
Programming User Training Documentation (produced throughout the life cycle) Hardware and software installation
Maintenance
perform functions System changed to reflect changing conditions System obsolescence (change over time)
Highly linked set of phases whose products feed the activities in subsequent phases
Must be carefully planned and managed
Traditional SDLC
Several Criticisms
go forward (milestones) difficult to go back Changing business conditions Enormous time and effort; very expensive to make changes once developed
Does not match users needs Requires extensive maintenance Increases development costs Maintenance costs account for 40% to 70% of system development costs
Tools:
Data Flow Diagrams Transform Analysis
Improve the analysis and design phases Reduce maintenance time and effort Easier to go back to earlier phases in life cycle when necessary (for when requirements change) Emphasis on partitioning/dividing problem into smaller, more manageable units Clear distinction between physical and logical design
Groups of objects share structural and behavioral characteristics (person, customer) Identifying objects, defining their structure and behavior, and defining their relationship
Primary tasks:
Delay producing system design until after user requirements are clear Prototyping serves as the working description of needs Gaining user acceptance Sacrificing computer efficiency for gains in human efficiency in rapidly building and rebuilding working systems Building a scaled-down functional version of the system Advantages:
Users are involved in design Provides feedback Captures requirements in concrete form
1.48
Approaches to Development
Joint Application Design (JAD)
New process for collecting information system requirements and reviewing system designs
Users, Managers and Analysts work together for several days System requirements are reviewed Structured meetings
1.49
Facilitate creation of a central repository for system descriptions and specifications Automate repository for easier updating and for consistency Diagramming tools for data flow diagrams and other graphical aids, etc.
1.50
Summary
Information systems analysis and design
information system
Data-Oriented
Focus is on the ideal organization of data rather than
Summary
Four types of information systems
Transaction Processing (TPS) Management Information Systems (MIS) Decision Support (DSS) Expert Systems (ES)
1.52
Summary
Systems Development Life Cycle (SDLC)
Project Identification and Selection Project Initiation and Planning Analysis Design Implementation Maintenance
1.53
Summary
Alternatives to Systems Development Life Cycle
Prototyping Rapid Application Development (RAD) Joint Application Design (JAD)