Information System Development: 2008 FALL EC Websites Development 1

Information System Development
2008 FALL
EC Websites Development
Conventional VS Contemporary
Conventional
Contemporary
Designed in a way to fit in the operations of a business unit. Different department will have a different system. Scope of the system is smaller. Analysis and design are simpler. Easy to maintain.
Designed in a way to fit in the operations of the whole enterprise. Processes or services oriented. Scope of the system is huge. Analysis and design are complicated ? Difficult to maintain ?
2008 FALL
Key Concepts in Systems Development
Initiating a systems development
Participants involved in a SD project Reasons for having a new system
Information systems planning

High level system requirement Feasibility analysis (Financially and technologically) Selection of system development model Objectives and schedule for SD
3
2008 FALL
Key Concepts in Systems Development
Build the system (System Development)
Detail analysis Precise system requirements (user accepted), a list of user acceptance tests System design modules, interfacing amongst modules, hardware requirements, programming language, OS Coding In-house testing unit test, system test, stress test User acceptance test
4
2008 FALL
Participants in Systems Development
2008 FALL
Participants in Systems Development
Stakeholders
Individuals who either themselves or through the organization are beneficiaries of the systems development effort. Individuals who interact with the system regularly
Professional who specializes in analyzing and designing business systems. Individual responsible for modifying or developing programs to satisfy user requirements.
6
Users
System Analyst
Programmers
2008 FALL
System Development Model
Waterfall model Spiral Model Component-based Development Prototyping Rapid Application Development Others
2008 FALL
Waterfall Model
Systems Investigation Problems and opportunities are identified
Systems Analysis Existing systems and work processes are studied

Systems Design Defines how the information system will do what it must do to solve the problem.
2008 FALL
Waterfall Model
Systems Implementation System components are assembled and the new or modified system is placed into operation.
Systems Maintenance and Review Ensures the system operates and is modified to keep up with business changes.
2008 FALL
Spiral Model
2008 FALL
10
Spiral Model
2008 FALL
11
Component-based Model
2008 FALL
12
Prototyping
Operational Prototype Accesses real data files, edits input data, makes necessary computations and comparisons, and produces real output. Nonoperational Prototype A mockup or model that includes output and input specifications and formats.
2008 FALL
13
Rapid Application Development
2008 FALL
14
Factors Affecting System Development

Resource Constraint Analysis Project Schedule and Tracking Systems Configuration Management Selected Project Management Software Packages Use of Computer-Aided Software Engineering (CASE) Tools Systems Investigation Requirements Analysis Systems Analysis
2008 FALL
15
Systems Investigation
Identify potential problems and opportunities and consider them in light of the goals of the company. It is the second round analysis. The first round analysis has been conducted during system planning.
2008 FALL
16
Feasibility Analysis
2008 FALL
17
Systems Investigation Report
A report that summarizes the results of the systems investigation and the process of feasibility analysis and recommends a course of action. The investigation is usually conducted by a system investigation team and a steering committee. Steering committee is an advisory group consisting of senior management and users from the IS department and other functional areas.
18
2008 FALL
2008 FALL
Table of Contents for a Systems EC Websites Development Investigation Report
19
Requirement Analysis
Requirements Analysis It is the third round analysis. An assessment used to determine the need of the users, the stakeholders, and the organization. Converting organizational goals into systems requirements
2008 FALL
20
Systems Analysis
External and Internal Sources of Data It is the forth and the last round analysis. The analysis must be very precise. The results will be used in system design.
2008 FALL
21
Systems Analysis
Data Collection
To understand what exactly the users needs What data/information should be processed in the system, and what sort of interface design the users expect.
Steps in Data Collection
2008 FALL
22
Systems Analysis
Techniques

Structured Interview Unstructured Interview Direct Observation Questionnaires Statistical Sampling

Steps in Data Collection
2008 FALL
23
Systems Analysis
Data Analysis
Manipulating the collected data so that it is usable for the development team members who are participating in systems analysis.
2008 FALL
24
Systems Analysis Report
Strength and weaknesses of existing system from stakeholders perspective. User/stakeholder requirements for the new system. Organizational requirements. Description of what new information systems should do to solve the problem
2008 FALL
25
Systems Analysis Report
2008 FALL
26
Remarks on System Development
2008 FALL
27
Major Problems in SD
Communication gaps between the user (nonIT) and the developer (IT)

No common language Lack of IT knowledge (non-IT) Lack of business sense (IT) Lack of mutual trust Lazy
2008 FALL
28
Solutions
User and developer should have a common ground knowledge

General and essential IT knowledge General and essential business knowledge
Patient Quality assurance process
2008 FALL
29
Technically How?
Spend more time on requirement analysis Documentation

Project schedule User manual Maintenance manual
Project plan Quality plan Analysis model Design model Testing plan
2008 FALL
30

Information System Development: 2008 FALL EC Websites Development 1

Uploaded by

Document Information

Original Description:

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Information System Development: 2008 FALL EC Websites Development 1

Uploaded by

Copyright:

Available Formats

Information System Development

Key Concepts in Systems Development

Initiating a systems development

Participants involved in a SD project Reasons for having a new system

Information systems planning

Key Concepts in Systems Development

Build the system (System Development)

Participants in Systems Development

Participants in Systems Development

System Development Model

Systems Investigation Problems and opportunities are identified

Systems Analysis Existing systems and work processes are studied

Rapid Application Development

Factors Affecting System Development

Systems Investigation Report

Table of Contents for a Systems EC Websites Development Investigation Report

Structured Interview Unstructured Interview Direct Observation Questionnaires Statistical Sampling

Systems Analysis Report

Systems Analysis Report

Remarks on System Development

User and developer should have a common ground knowledge

General and essential IT knowledge General and essential business knowledge

Patient Quality assurance process

Spend more time on requirement analysis Documentation

Project schedule User manual Maintenance manual

You might also like