materi

Erlangga Fausa / [email protected]

MANAGEMENT ONFORMATION SYSTEMS

Chapter 10 INFORMATION SYSTEMS DEVELOPMENT

By : Erlangga Fausa (MIS Specialist)

UNIVERSITAS ISLAM INDONESIA Yogyakarta – 2011

------------------------------------------------------------------------------------------


Where Do Systems Development Projects Come From? (Whitten)

• Problem – an undesirable situation that prevents the organization from fully achieving its purpose, goals, and/or objectives.

• Opportunity – a chance to improve the organization even in the absence of an identified problem.

• Directive - a new requirement that is imposed by management, government, or some external influence.


Information Systems & Management Changes (Issues and Challenges)

Market change(Rapid change)

Management change(Complexity & dynamics)

IS change(Handling change and

complexity with IT)

IS architecture ? (characteristics ?)

New products and services


Information Systems Architecture (Characteristics)

• Comprehensive• Integrated (cross-functional)• Flexible (change ready)• Open (compatible)• Secure• Technology trend


INFORMATION SYSTEMS STAKEHOLDERS (Whitten)

• A stakeholder is any person who has an interest in an existing or proposed information system. Stakeholders can be technical or nontechnical workers. They may also include both internal and external workers :

– System owners– System users (internal and external)– System analysts– System designers– System builders– Etc.


Systems Analyst as a Problem Solver (Whitten)

• By "Problems" that need solving, we mean:– Problems, either real or anticipated, that require

corrective action

– Opportunities to improve a situation despite the absence of complaints

– Directives to change a situation regardless of whether anyone has complained about the current situation


Systems Analyst Position ? (Whitten)


Skills Needed by The Systems Analyst (Whitten)

• Working knowledge of information technology• Computer programming experience and expertise• General business knowledge• General problem-solving skills• Good interpersonal communication skills• Good interpersonal relations skills• Flexibility and adaptability• Character and ethics


The Systems Analyst as a Facilitator (Whitten)


System Development Methodologies

• System Development Life Cycle (Structured Analysis and Design)

• Prototyping• Rapid Application Development (RAD)

and Joint Application Development (JAD)

• Object Oriented Analysis and Design• dsb


A System Life Cycle (Whitten)


System Development Process (Whitten)

System development process – a set of activities, methods, best practices, deliverables, and automated tools that stakeholders use to develop and maintain information systems and software.


Classical Problem-solving approach (Whitten)

Classical Problem-solving approach1. Study and understand the problem, its context, and

its impact.

2. Define the requirements that must be meet by any solution.

3. Identify candidate solutions that fulfill the requirements, and select the “best” solution.

4. Design and/or implement the chosen solution.

5. Observe and evaluate the solution’s impact, and refine the solution accordingly.


System Development Process Overview (Whitten)

•System initiation – the initial planning for a project to define initial business scope, goals, schedule, and budget.

•System analysis – the study of a business problem domain to recommend improvements and specify the business requirements and priorities for the solution.

•System design – the specification or construction of a technical, computer-based solution for the business requirements identified in a system analysis.

•System implementation – the construction, installation, testing, and delivery of a system into production.


System Development Life Cycle (SDLC) (Martin)

• Definition Phase :– Feasibility Analysis– Requirements Definition

• Construction Phase :– System Design– System Building– System Testing

• Implementation Phase :– Installation– Operations– Maintenance


Advantages and Disadvantages of Traditional SDLC Approach (Martin)

• Advantages :– Highly structured, systematic process– Thorough requirements definition– Clear milestones with business management sign-offs

• Disadvantages :– Does not account well for evolving requirements

during project– Time-consuming (and costly) process– Top-down commitment requires


Prototyping Life Cycle (Martin)

Step-1 : Identify basic system requirements

Step-2 : Develop initial prototype

Step-3 : Use prototype and note desired changes

Step-4 : Revise andenhance prototype

Step-5 : Evaluate as operational system

Step-6 : Make necessarymodification or abandon

Step-7 : Install, operate, and maintain


Logical vs. Physical Models (Whitten)

Logical model - a pictorial representation that depicts what a system is or does.

Physical model - a technical pictorial representation that depicts what a system is or does and how the system is implemented


Rapid Application Development Strategy (Whitten)

• Rapid application development (RAD) – a system development strategy that emphasizes speed of development through extensive user involvement in the rapid, iterative, and incremental construction of series of functioning prototypes of a system that eventually evolves into the final system.

– Prototype – a small-scale, representative, or working model of the users’ requirements or a proposed design for an information system.

– Time box – the imposition of a non-extendable period of time, usually 60-90 days, by which the first (or next) version of a system must be delivered into operation.


Rapid Application Development (RAD) [Newer approach] - Martin

Requirements Planning

User Design

Construction

Cutover


RAD Process (Whitten)


RAD Advantages and Disadvantages (Martin)

• Advantages :– Dramatic Savings in development time– Focuses on essential system requirements– Ability to rapidly change system design at user

request

• Disadvantages :– Quality may be sacrifices for speed– Time-consuming commitments for key user personnel– Possible shortcuts on internal standards and module

reusability


Process Design (Modeling) Data Fow Diagram (DFD) – Example (Whitten)


Database Design (Modeling) Entity-Relationship Diagram (ERD) – Example (Whitten)


Input Design & Prototyping (Whitten)

Data capture – the identification and acquisition of new data (at its source).

Source documents – forms used to record business transactions in terms of data that describe those transactions.

Data entry – the process of translating the source data or document (above) into a computer readable format.


Output Design & Prototyping – (Whitten)

a. Internal output – an output intendedfor system owners and system userswithin an organization. Detailed report – an internal

output that presents information withlittle or no filteringExample: A listing of all customers

Summary report – an internaloutput that categorizes informationfor managersDo not have to wade through details.Increasingly presented in graphical formats using charts Example: A count of customers by region

b. External outputs – an output thatleaves the organization organization.Intended for customers, suppliers,partners, or regulatory agencies


User Interface Design (Whitten)

Graphical User Interface (GUI) ;

-Windows and frames -Menu-driven interfaces-Pull-down and cascading

menus-Tear-off and pop-up menus-Toolbar and iconic menus-Hypertext and hyperlink menus

-Instruction-driven interfaces-Language-based syntax-Mnemonic syntax-Natural language syntax

- Question-answer dialogue


Computer-Assisted Software Engineering (CASE) – (Whitten)

Computer-aided systems engineering (CASE) –automated software tools that support the drawing and analysis of system models and associated specifications. Some CASE tools also provide prototyping and code generation capabilities.

– CASE repository – system developers’ database where developers can store system models, detailed descriptions and specifications, and other products of system development. Synonyms: dictionary and encyclopedia.

– Forward engineering – CASE tool capability that can generate initial software or database code directly from system.

– Reverse engineering – CASE tool capability that can generate initial system models from software or database code.


Using a CASE Tool for System Development (Whitten)


Organization’s Needs vs Systems’s Performance (Martin)

Performance of the system

Needs of the organization

Time

Perf

orm

ance

Req

uire

men

ts

Widening gap


BEHAVIORAL ASPECTS OF MIS (Organization Behavior, Murdick, Robert G)


BEHAVIORAL ASPECTS OF MIS (Organization transformation / change management, Murdick, Robert G)

Two key factors :• Social organization with its norms, roles,

relationships and communications networks

• The psycological needs of the individuals for esteem, self-actualization, and freedom from represive control.



Common reasons result in resistance of the MIS:• Threat to status• Threat to ego• Economic threat• Job complexity• Isolation• Superior-subordinate relationships changed• Job ambiguity and loss of control• Time rigidity• Interpersonal relationship changed



Organizational systems :

•Required structure•Required behavior

Anticipated emergenceorganization :

•Structure•Activities•Attitudes•Norms



Procedure for effecting change without resistance :

• Create a climate for change• Develop effective agents of change• Modify the required organizational system in the

light of anticipated emergent behavior


T H A N K Y O U ..

materi

Documents

rapid application

system development

systems analyst

system development

behavioral

driven interfaces

system analysis

internal output