Why require to develop sisten information?

system development can mean to compile a system in the new system to replace the system old ones as a whole or improve;repair the system which there have. system old ones require to be improve;repaired or change by the way because of several things, that is as follows:

Ø Existence of Problems ( problems)

Ø wrong in the Organizational Growth System

Ø To Reach for the opportunity ( opportunities)

Ø Existence of instruction ( directives)

system development Target

v Solving problems

v Reach for the opportunity

v Fulfilling given instruction

What expected at new system?

· Performance ( performance)

- Measured to use the throughput and response time

· Information ( information)

- Make-Up of information quality

· Economy ( economic)

- Make-Up of benefit of vs decreasing cost

· Control ( operation)

- Detecting and improve;repairing mistake

· Efficiency ( efficiency)

- Efficient of operational

· Services ( service)

- Make-Up of system service

system development Principle.

· System for the management of

System in the big investment

- Investigation of all alternative ( minimizing missing opportunity cost)

- Best investigation have to be valuable : cost-benefit analysis & cost-effectivenes analysis

· System need the educated people

- no education have to be formal

· Step work the ? System Development life cycle

· System development because have to massage

· Don'T fear to cancel the project

· System documentation

System development life cycle

Model Waterfall

Phase model the Waterfall

• Analyse and requirement definition
• Desain of System and software
• implementation And unit testing
• integration And testing system

• Operate for and maintenance Insuffiency from model waterfall [is] difficulty to accommodate the change after process walk.

Problems Model the Waterfall

• Inflexible in project division to in different storey;level
• Difficult to merespon of requirement change consumer
• So that model this compatible only if requirement have been understood better.

Model Iteratif

Model Spiral

Sector Model The Spiral

v Objective Setting

- special Objective for the phase of identified the

v estimating And risk reduction

- Risk appraised active to lessening risk.

v development And Validasi

- Model the development for the system of selected which is in the form of model generic

v Planning

- the Project of next direview phase and from spiral planned.

system development Approach.

· Classic approach of vs of structure approach

· approach of Rasher of vs of system approach

· approach of under vs to climb of approach on and

· approach of Sistem of approach moduler

· Approach of jumping movement far vs approach expand

system development Approach.

v Classic approach of structure approach

- Classic approach

· Step in SDLC

· not involve the consumer, more emphasizing to system analyst

· Problems: difficult development, costly treatment expense, big mistake possibility, efficacy less be well guaranted, internal issue applying

- Structure approach

· Consumer involved from early to determine the system requirement

· Using tools-tools is like document of flow diagram

v approach of Rasher of vs of system approach

- Rasher approach

· Emphasizing at application or activity

· Heedless of the target

- System approach

· See system as one intact union

· Emphasizing at goal achievement as a whole

v approach of under and to climb vs of approach on and to come

- approach under and to climb( bottom-up)

· Started from level is under that is operational

· Representing approach marking classical

· Recognized with the term document and analysis

- approach under and to climb ( top-down)

· Started from level for that is strategy planning

· Representing marking of structure approach

· Recognized also by decision-analysis

v approach of Sistem and to spread vs of approach moduler

- approach Sistem and to spread

· Developing system at a time and totally

· Representing classic approach marking

- approach Moduler

· Breaking complicated system become the parts of simple

· System developed become on schedule, easy to to be comprehended and looked after

v Representing marking of structure approach

- approach of to the jump and far away vs approach expand the

· approach to the jump and far away ( great-loop approach)

· Developing system at a time use the sophisticated technology

· High resolution and finish a lot of expense

- Approach expand the ( evolutionary approach)

· Applying sophisticated technology for the application of certain

· Developed to follow the requirement

· Cost effective and can keep abreast of technology

system development Methodologies.

What that methodologies?

- Method used in science

What the meaning method ?

- way of systematic to do something

What that algorithm?

- Procedure medley to solve problem

Klasifikasi of development Methodologies.

v Functional Decomposition

- Emphasizing system resolving become the sub system

- Follow the example of the: HIPO, Stepwise Refinement, iterative stepwise refinement, information hiding

v Data-Oriented

- Emphasizing at processed document characteristic

· document and flow Oriented: module of according to document element type

· document and structure Oriented: structure of input and output

v Prescriptive

- of usually provided by factory of software maker

Appliance in system development.

· In form of graph: HIPO, SADT, Jackson’S Diagram, and others

· Appliance using schema:

- Activity Charting: depicting activity, follow the example of the: Gant Chart, flowchart, dll

- Layout Charting: depicting

- Personal Relationship charting: depicting personnel [relation/link], follow the example of the: organization chart, working distribution chart

system development Technique.

· technique of project Management ? for the schedule of project, follow the example of the: CPM And PERT

· Technique find the fact ? to collect and determine the document / fact

- Interview the

- Observation

· Technique analyse the expense / benefit ? cost-benefit and cost-effectiveness analysis

· Technique run the meeting

· Inspection technique

System Analyst & Programming.

· System analyst: learning problem and determine the requirement of system wearer to identify the resolving

· Programming: writing code program pursuant to designing to develop;build which is made by a analyst

· System analyst undertake to link the knowledge difference that happened among/between wearer of system and progmming

needed knowledge.

· document processing Technology, computer and programming

· Business knowledge in general

· Quantitative method: regresi, linear is programming

· Trouble-Shooting m

· Communications usher the personnel

- construct the relation/link usher personnel

reference ;

jerry fitzgerald,ardra.f .fitzgerald,warren D.stallings,jr.fudermentals of sytems Analisis