Overview of Systems Development

(1)

(2)

Overview of Systems Development



Participants



Initiating systems development



Information systems planning



Establishing objectives for systems development



Systems development and the Internet



Trends in systems development and enterprise

(3)

Participants



Stakeholders



Individu / organisasi yang merupakan penerima

manfaat dari upaya pengembangan sistem



Systems analyst



_Profesional

_yang

_{mengkhususkan}

_diri

_dalam

menganalisis dan merancang sistem bisnis



Users



_{Individu yang berinteraksi dengan sistem secara teratur}



Programmer



Individu yang bertanggung jawab untuk memodifikasi

atau mengembangkan program untuk memenuhi

(4)

Systems analyst Managers

Vendors and suppliers System stakeholders

Users _Technical

(5)

Systems Analyst

• Seorang programmer atau konsultan yang merancang

dan mengelola pengembangan aplikasi bisnis.

(6)

Alasan khas untuk Memulai

Pengembangan Sistem Proyek

Keinginan untuk membuat lebih efektif menggunakan informasi Masalah dengan sistem yang ada

Keinginan untuk memanfaatkan peluang-peluang baru

Meningkatnya persaingan

Pertumbuhan organisasi

Merger atau akuisisi

Perubahan pasar atau lingkungan eksternal

Persepsi manfaat Potensial oleh Individu mampu melakukan perubahan

Proses

(7)

Planning



Perencanaan sistem informasi

 penerjemahan tujuan strategis dan

organisasi ke dalam inisiatif pengembangan sistem



Analisis Kreatif

 Investigasi pendekatan baru untuk masalah yang ada



Analisis Kritis

 Mempertanyakan berisi dan hati-hati apakah unsur-unsur sistem yang terkait dalam cara yang paling efektif atau efisien

Strategic plan

IS planning

(8)

Langkah-langkah dalam Perencanaan IS

Strategic plan

Mengembangkan tujuan keseluruhan

Identify IS projects

Set prioritas & pilih proyek

Analisis kebutuhan sumber daya

Jadwal yang ditetapkan dan batas waktu

Mengembangkan dokumen perencanaan Sistem Informasi

(9)

Menetapkan Tujuan

Pembangunan Sistem



Performance objectives



Kualitas atau kegunaan dari output



Kualitas atau kegunaan dari format output



Kecepatan di mana output yang dihasilkan



Cost objectives



Biaya pengembangan



Biaya yang berkaitan dengan keunikan sistem aplikasi



Investasi tetap di hardware dan peralatan terkait

(10)

Systems Development

and the Internet



Aplikasi dipindahkan ke Internet



Penjualan



penempatan order



Akses informasi produk



Membangun situs Web statis



Intranet tools



NetDynamics



SilverStream



Web-Logic



Novera

(11)

Systems Development Life Cycle



Systems investigation



Masalah dan peluang diidentifikasi



Systems analysis



sistem yang ada dan proses kerja dipelajari



Systems design



Mendefinisikan bagaimana sistem informasi akan melakukan

apa yang harus dilakukan untuk memecahkan masalah



Systems implementation



Komponen sistem dirakit dan sistem baru atau diubah

ditempatkan ke dalam operasi



Systems maintenance and review



Memastikan sistem beroperasi dan dimodifikasi untuk

bersaing dengan perubahan bisnis

(12)

Systems maintenance and review

(Mengevaluasi hasil solusi) Systems implementation (Solusi tempat berlakunya)

Systems design

(Memilih dan merencanakan solusi terbaik) Systems Analysis

(13)

Biaya untuk membuat perubaha n tertentu

(14)

Prototyping



Operational prototype

 Mengakses file data real, mengedit input data, membuat perhitungan yang diperlukan dan perbandingan, dan menghasilkan output riil



Non-operational prototype

 Sebuah model yang mencakup output dan input spesifikasi dan format



Rapid application development (RAD)

 Mempekerjakan alat, teknik, dan metodologi yang dirancang untuk mempercepat pengembangan aplikasi, secara otomatis sumber generasi kode, dan memfasilitasi keterlibatan pengguna dalam kegiatan desain dan pengembangan



Joint application development (JAD)

(15)

Rapid Application Development

A programming system that enables programmers to quickly build working programs. In general, RAD systems provide a number of tools to help build graphical user interfaces that

would normally take a large development effort. Two of the most popular RAD systems for Windows are Visual Basic and Delphi.

Historically, RAD systems have tended to emphasize reducing development time, sometimes at the expense of generating efficient executable code. Nowadays, though, many RAD systems produce extremely fast code. Conversely, many

(16)

Prototyping:

The Iterative Life Cycle

Determine

User review Iteration 1

Determine

User review Iteration 2

(17)

General Model of Prototyping

Systems development initiated

Investigate and analyse problem sufficiently to develop

workable solution

Develop prototype

Put prototype into operation

Refine and modify prototype

(18)

End-User Systems

Development Life Cycle



_{End-user systems development life cycle}



_{Setiap proyek pengembangan sistem di mana upaya}

(19)

Factors Affecting Systems

Development Success



Managing change



Requires the ability to recognize existing or potential

problems and deal with them before they become a

serious threat to the success of a new or modified

system



Use of project management tools



Schedule



Milestone



Deadline



Critical path



Program Evaluation Review Technique (PERT)

(20)

(21)

Selected Project Management

Software Packages

Software

Vendor

BeachBox ’98

NetSQL Partners

Job Order

Management Software Inc.

OpenPlan

Welcom

Project

Microsoft

Project Scheduler

Scitor Corp.

(22)

Use of Computer-Aided Software

Engineering (CASE) Tools



CASE tools automate tasks required in a system

development effort and enforces adherence to the SDLC



Upper CASE tools



Tools that focus on activities associated with the early stages of

systems development



Lower CASE tools



Tools that focus on the later implementation stage of systems

development



Integrated-CASE (I-CASE) tools



Tools that provide links between upper- and lower-CASE packages,

allowing lower-CASE packages to generate program code from

(23)

CASE

Short for Computer Aided Software Engineering, a category of software that provides a development environment for programming teams. CASE systems offer tools to automate, manage and simplify the development process. These can include tools for:

• Summarizing initial requirements

• Developing flow diagrams

• Scheduling development tasks

• Preparing documentation

• Controlling software versions

• Developing program code

Various companies offer CASE software capable of supporting some or all of these activities. While many CASE systems provide special support for object-oriented

(24)

ISO 9000



_{An international standard used by IS departments to}

(25)

Systems Investigation



Identify potential problems and opportunities and consider

them in light of the goals of the company



The investigation team



Managers and stakeholders



IS personnel



Task



Undertake feasibility analysis



Establish system development goals



Select system development methodology

(26)

Feasibility Analysis



Technical feasibility



Can the hardware, software, and other system components be

acquired or developed to solve the problem?



Operational feasibility



Can the project be put into action or operation?



Schedule feasibility



Can the project be completed in a reasonable amount of time?



Economic feasibility



Does the project make financial sense?



Net present value

(27)

The 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



Steering committee

(28)

Systems Analysis



_{Typical table of contents from a systems investigations}

report:

Table of Contents 1. Executive summary

2. Review of goals and objectives

3. System problems and opportunities 4. Project feasibility

(29)

Sources of Data

Internal Sources

• Users, stakeholders, managers

• Organization charts

• Forms and documents

• Procedure manuals and policies

• Financial reports

• IS manuals

• Other measures of business processes

External Sources

• Customers

• Suppliers

• Stockholders

• Government agencies

• Competitors

• Outside groups

• Journals, etc.

(30)

Data Collection



Structured Interview



Unstructured Interview



Direct Observation



Questionnaires



Statistical Sampling

Identify data sources

Data collection

(31)

Data Analysis



Data analysis



Manipulating collected data so that it is usable for the development

team members participating in systems analysis



Data modeling



A commonly accepted approach to modeling organizational objects

and associations that employ both text and graphics



E.g, ER (entity relationship) diagrams



Activity modeling



A method to describe related objects, associations, and activities



Data flow diagram

(32)

ER Example

Play

Member Game of Golf

MID

Name Address Date

paid Date Time Score

1 

(33)

Data Flow Diagram



_{Schematic description of business processes}



_{Premise: for every activity there is some communication,}

transference, for flow that can be described as a data

element

(34)

Entity symbol Data-flow line Process

symbol Data-flow line Data store

Member

Assign Tee time

Check

Member card

Scores Tee time

Reservation request

Course access

Member ID

Score card

Handicap

Available times

Group information

Member tee time

Date

Score card

(35)

Application Flowchart



Charts that show relationships among

applications or systems

Order processing application

Inventory control application

Invoicing application

(36)

Grid Charts



A table that shows relationships among the

various aspects of a systems development effort

Database

Accounts receivable database

Order processing applications

Inventory control application

(37)

Requirements Analysis



An assessment used to determine user,

stakeholder, and organizational needs

Goals and mission of the organization

Systems requirements Strategy

(38)

Screen Layout Charts



May be tailored for…



_{Frequent users who require little descriptive}

information, or



_{Infrequent users who require more descriptive}

(39)

ITEM NO. QTY UNIT PRICE DOLLARS DISCOUNTS

XXXXXXX XXXX XX XXXXX XXXXXX XX XX XX

ORDER ENTRY

ORDER NO.

CUSTOMER NO.

SALES

PERSON REGION COMMISSION

NET

DOLLARS

XXXXX XXXXX XXXXX XXX XXX XXXXX

(40)

Which online option would you like to perform?

(Please enter an ‘X’ to make a selection)

_DATA ENTRY Enter transaction and report

requests for later processing

_RETRIEVALS Review online information from the database: bill of materials,

where-used, routing, item data

(41)

The Systems Analysis Report



_{Strength and weaknesses of existing system from a}

stakeholder’s perspective



_{User/stakeholder requirements for the new system}



_{Organizational requirements}



Description of what new information systems should

(42)

Typical Table of Contents for a

Report on an Existing System

Johnson & Flores, Inc. Systems Analysis Report

TABLE OF CONTENTS

Background Information Problem or Need Statement Data Collection

Data and Requirements Analysis Recommendations

(43)