Information Systems

10/30/2010
Overview
• Information Systems
– Crucial to success of modern business
Information Systems organizations
– Constantly being developed to make business
more competitive
Reference: Systems Analysis and Design in a – Impact productivity and profits
Changing World, 3rd Edition • Keys to successful systems development
– Thorough systems analysis and design
– Understanding what business requires
Systems Analysis and Design in

2
a Changing World, 3rd Edition
Analyst’s Approach to Problem

Overview (continued) Solving
Research and understand the problem
• Systems analysis – what system should do Verify that the benefits of solving the problem outweigh the costs
Define the requirements for solving the problem

• Systems design – how components of
information system should be physically Develop a set of possible solutions (alternatives)
implemented Decide which solution is best, and make a recommendation
Define the details of the chosen solution

• Systems analyst – uses analysis and design
techniques to solve business problems with Implement the solution
information technology Monitor to make sure that you obtain the desired results
Systems Analysis and Design in Systems Analysis and Design in

3 4
a Changing World, 3rd Edition a Changing World, 3rd Edition
Specification of Information Systems Components of specifications
• Specification of any system before its development is crucial. • Structure: How it is organized.
• Specifications perform for information systems the same • Function: What it does.
function that blue-prints and engineering specifications
perform for physical structures. • Behavior: How it responds to
• Specifications serve as benchmarks for evaluating designs as events and stimuli.
well as their implementation.
• Specifications facilitate quality assurance via verification (are • Data: Its meaning and
we building the system right, ie., do the design and organization.
implementation meet the specifications?) and validation ( are
we building the right system, ie., does the system meet the
user needs?).

5 6
1
10/30/2010
Information Systems and Subsystems

7 8
Information Systems and Component System Boundary vs. Automation

Parts Boundary

10
Systems Analysis and Design in a Changing World, 3rd Edition 9 a Changing World, 3rd Edition
Types of Information Systems Types of Information Systems (continued)

• Transaction processing systems (TPS) • Decision support systems (DSS)
– Capture and record information about – Explore impact of available options or decisions
organization’s transactions (What-if scenarios)
• Management information systems (MIS)
• Communication support systems
– Take information captured by TPS
– Produce reports for planning and control – Facilitate communication internally and with
customers and suppliers
• Executive information systems (EIS)
– Monitoring competitive environment and strategic • Office support systems
planning – Help employees create and share documents
11 12
2
10/30/2010
Components of an Information
The Analyst’s Role in Strategic Planning
Systems Strategic Plan
• Special projects affecting executives
– Business process reengineering – radical
improvements to existing processes
• Strategic planning development process
• Information systems strategic planning
– Application architecture plan (business focus)
– Technology architecture plan (infrastructure focus)
• Enterprise resource planning (ERP) integrated
systems
13
a Changing World, 3rd Edition Systems Analysis and Design in a Changing World, 3rd Edition 14
Systems Development Life Cycle (SDLC)

Systems Development Life Cycle (SDLC)
Overview
• Systems development life cycle (SDLC) • Systems development project
– Provides overall framework for managing system – Planned undertaking with fixed beginning and end
development process – Produces desired result or product
• Two main approaches to SDLC – Can be a large job of thousands of hours of effort
– Traditional approach: structured systems or a small one month project
development and information engineering • Successful development project:
– Object-oriented approach: object technologies – Provides a detailed plan to follow
requires different approach to analysis, design, – Organized, methodical sequence of tasks and
and programming activities
• All projects use some variation of SDLC – Produces reliable, robust, and efficient system

15 16
Phases of the Systems Development

The waterfall approach to the SDLC
Lifecycle (SDLC)
• Project planning: initiate, ensure feasibility,
plan schedule, obtain approval for project
• Analysis: understand business needs and
processing requirements
• Design: define solution system based on
requirements and analysis decisions
• Implementation: construction, testing, user
training, and installation of new system
• Support: keep system running and improve
17 18
3
10/30/2010
Overlap of Systems Development

Iterations across life cycle phases
Activities

19 20
Information System Development SDLC and problem-solving

Phases • Problem definition: On receiving a request from the user for
systems development, an investigation is conducted to state
the problem to be solved.
– Deliverables: Problem statement.
• Feasibility study: The objective here is to clearly define the
scope and objectives of the systems project, and to identify
alternative solutions to the problem defined earlier.
– Deliverables: Feasibility report.
• Systems analysis phase: The present system is investigated
and its specifications documented. They should contain our
understanding of HOW the present system works and WHAT
it does.
– Deliverables: Specifications of the present system.

21 22
SDLC and problem-solving

• Systems design phase: The specifications of the present system
are studied to determine what changes will be needed to
incorporate the user needs not met by the system presently.
The output of this phase will consist of the specifications -
WHAT the proposed system will do and HOW it will work.
– Deliverables: Specifications of the proposed system.
• Systems construction: Programming the system, and
development of user documentation for the system as well as
the programs.
– Deliverables: Programs, their documentation, and user
manuals.
• System testing & evaluation: Testing, verification and validation
of the system just built.
– Deliverables: Test and evaluation results, and the system
ready to be delivered to the user/client.

23 24
4
10/30/2010
Models Used in Analysis Models Used in Design

25 26
Some Tools Used in System Some Techniques Used in System

Development Development

27 28
Two Approaches to System Components of a Traditional Analysis Model

Development
• Traditional Approach
– Also called structured system development
– Structured analysis and design technique (SADT)
• Structured programming
– Improves computer program quality
– Allows other programmers to easily read and
modify code
– Each program module has one beginning and one
ending
– Three programming constructs (sequence,
decision, repetition)

29 30
5
10/30/2010
Traditional Approach (Structured

Physical and Logical DFDs
Systems Development)
• Logical model
– Assumes implementation in perfect technology
– Does not tell how system is implemented
• Physical model
– Describes assumptions about implementation
technology
– Developed in last stages of analysis or in early design

31 32
Structure Chart Created Using

Structured Design
• Technique developed to provide design
Structured Design Technique
guidelines
– What set of programs should be
– What program should accomplish
– How programs should be organized into a hierarchy
• Modules are shown with structure chart
• Main principle of program modules
– Loosely coupled – module is independent of other
modules
– Highly cohesive – module has one clear task

33 34
Data Flow Diagram (DFD) created

Object-Oriented Approach
using Structured Analysis Technique
• Views information system as collection of
interacting objects that work together to
accomplish tasks
– Objects - things in computer system that can
respond to messages
– No processes, programs, data entities, or files are
defined – just objects
• Object-oriented analysis (OOA)
– Defines types of objects that do work of system
– Shows how objects interact with users to complete
tasks
35 36
6
10/30/2010
Object-Oriented Approach to Systems Object-Oriented Approach (continued)

• Object-oriented design (OOD)
– Defines object types needed to communicate with
people and devices in system
– Shows how objects interact to complete tasks
– Refines each type of object for implementation
with specific language of environment
• Object-oriented programming (OOP)
– Writing statements in programming language to
define what each type of object does
• Benefits of OOA include naturalness and reuse

37 38
Relationships Among Components of a

Design Phase of SDLC
Methodology
• Design and integrate the network
• Design the application architecture
• Design the user interfaces
• Design the system interfaces
• Design and integrate the database
• Prototype for design details
• Design and integrate system controls
39 40
Design Phase Activities and Key

Components Requiring Systems Design
Questions

41 42
7
10/30/2010
Moving from Analysis to Design Design and Integrate the Network

• Design: • Network specialists establish network based on
strategic plan
– Converts functional models from analysis into models
that represent the solution • Project team typically integrates system into
– Focused on technical issues existing network
– Requires less user involvement than analysis • Technical requirements have to do with
communication via networks
• Design may use structured or OO approaches
– Database can be relational, OO or hybrid
• Technical issues handled by network specialists:
– User interface issues – Reliability, security, throughput, synchronization

43 44
Network Design Design the Application Architecture

• Integrate network needs of new system with • Specify how system activities are carried out
existing network infrastructure • Described during system analysis as logical
• Describe processing activity and network models
connectivity at each system location
• After design alternative is selected, detailed
• Describe communications protocols and computer processing is designed as physical
middleware that connects layers models such as: physical data flow diagrams,
• Ensure that network capacity is sufficient structure charts, interaction diagrams
– Data size per access type and average • Approach varies depending on development and
– Peak number of access per minute or hour deployment environments
45 46
Design and Integrate the Database Prototype for Design Details

• System analysis data model used to create • Continue to create and evaluate prototypes
physical database model during design phase
• Collection of traditional computer files, relational • Prototypes confirm design choices:
database, and/or object-oriented databases – Database
• Technical requirements, such as response times, – Network architecture
determine database performance needs – Controls
• Design work might involve: – Programming environment
– Performance tuning • Rapid application development’s (RAD) design
– Integration between new and existing databases
prototypes evolve into finished system
47 48
8
10/30/2010
Design and Integrate the System Project Management: Coordinating

Controls the Project
• Final design activity to ensure system has • Coordinating Project Teams
adequate safeguards (system controls) to – Project schedule - coordinating ongoing work
protect organizational assets
• The Project Team at RMO
• Controls are needed for all other design
– As project team grows – structure may change
activities
– User interface – limit access to authorized users • Coordinating Information
– System interface – protect from other systems – CASE tools and central repository
– Application architecture – record transactions – Team communication and information
– Database – protect from software/hardware coordination
failure – Track open items and unresolved issues
– Network design – protect
49 communications Systems Analysis and Design in
50
Deployment Environment Implementation Phase of SDLC

• Deployment environment definition bridges • Construct software components
analysis and design
– Hardware • Verify and test
– System software
– Networking
• Convert data
• Common deployment environments in which
system will operate
• Train users and document the system
• Related design patterns and architectures for
application software
51 • Install the system
52
Implementation Alternatives Construction and Test Plan

• Development order
• Testing order
• Data used to test modules, module groups,
methods, classes, programs, and subsystems
• Acceptance criteria
• Relevant personnel assignments (construction
and testing)
53 54
9
10/30/2010
Correspondence Between SDLC

Testing Phases and Various Types of
• Process of examining a product to determine
Testing
if any defects exist
• Testing levels are related to specific SDLC

phases
• Testing activities spread throughout SDLC
• Most of testing takes place following software

construction and definition of defect
standards
55 56
SDLC Phases and Testing Activities

Installation
Performed Within Each Phase
• After development and testing, system must
be put into operation
• Important planning considerations
– Costs of operating both systems in parallel
– Detecting and correcting errors in new system
– Potentially disrupting the company and IS
operations
– Training personnel and customers with new
procedures
57 58
Direct Installation and Cutover Parallel Installation and Operation

59 60
10
10/30/2010
Phased Installation with Direct

System Documentation
Cutover and Parallel Operation
• Descriptions of system functions, architecture,
and construction details
• Used by maintenance personnel and future
developers
• Generated as a byproduct of development
– Includes source code
– Includes analysis and design models
• Failure to maintain system documentation
compromises value of a system
61 62
Lifecycle Phases and System

Documentation Generated in Each Training and User Support
Phase • Without training, user error rates will be high
• Training considerations
– Frequency and duration of system use
– Need to understand system’s business context
– Existing computer skills and proficiency
– Number of users

63 64
Maintenance and System

Implementing a Change
Enhancement
• Modification of software after delivery to • Planning for a change includes:
correct faults, improve performance, or adapt
– Identify parts of system to change or addition
the product to a changed environment
– Tracking modification requests and changes – Secure personnel to implement change
– Implementing changes – Schedule design and implementation activities
– Monitoring system performance – Develop test criteria and testing plan for changed
system
– Upgrading hardware/software
• System documentation is reviewed to
– Updating documentation
65
66
determine scope of change
11
10/30/2010
Upgrading Computing
Support Phase of SDLC
Infrastructure
• Infrastructure requires periodic updates • Maintain system
– Software maintenance releases – Small patches, repairs, and updates
• Enhance system
– Software version upgrades
– Small upgrades or enhancements to expand
– Declining system performance system capabilities
– Larger enhancements may require separate
• Infrastructure includes computer hardware, development project
system software, networks, DBMSs
• Support users
– Technical, complex, and risky – Help desk and/or support team
– Outages can impact entire
67
system a Changing World, 3rd Edition
68
Life Cycles with Different Names

for Phases

69
12

Information Systems

Caricato da

Informazioni sul documento

Titolo originale

Copyright

Formati disponibili

Condividi questo documento

Condividi o incorpora il documento

Opzioni di condivisione

Hai trovato utile questo documento?

Questo contenuto è inappropriato?

Copyright:

Formati disponibili

Information Systems

Caricato da

Copyright:

Formati disponibili

10/30/2010

Systems Analysis and Design in

Analyst’s Approach to Problem

Define the requirements for solving the problem

Define the details of the chosen solution

Systems Analysis and Design in Systems Analysis and Design in

Specification of Information Systems Components of specifications

Systems Analysis and Design in Systems Analysis and Design in