Development System

DIVELOPMENT SYSTEM


There are some important things in developing
Information system: Those are:
1. Problems in the past systems, such as:
A Problems
• Dishonest
• Unintentionally fault
• Ineffective operational
• Disobedience Of management rule.
b Organization Improvement
It included the information so wide,
the volume of data arrangement
in creasingly and the change of new accountant principal,
so the system become ineffective.
2. Opportunities in market so competitive.
The past information/effective time as a certain point to get the successful strategy and a good planning to get a profer chance.
3. Directives
The instruction/ directives is not based on the competition of organization.
The objectives/Purpose of information system development:
• To solve problem by respairing the oldest system, so we can get the thing which needed in organization.
• To get the oportunities by doing the change of system. It can be done by effective time in order to get a successful strategy and a good planning.
• To fill the directives by using a new system so we can compete with other organization.
The expectation of company
The expectation of company after the new system
Is formed, such as :
• Performance.
Good performance on working based on through put and responsetime.
• A good Quality of information
• An economical of production cost.
• A controller of mistake and dishonesty which happenned.
The principal of system Development:
• Management system
It is needed to full fill the management.
• System is investment.


• In developing system, we need fund to be ussed. So we must consider tho things, such as:
1. Investigation alternative.
We must study many alternatives so we
can get the benefit.
2. The best investigation : Cost-benefit analysis and Cost-effectiveness analysis.


• System need educated-man
It means that we need a person who has many experience and know how to manage company
• Stage of Work(System Development Life Cycle)
This cycle involve the labbour/ team work, good planing and goodcoordination.
• System development not be well organized but it is done together.
• Don’t be afraid to cancel the projec.
If the project do not give a good benefit to the company, we should decide to cancel it.
• System documenttation
We need to make a documentation in the prosess of system development.
System development life cycle
Waterfall Model
Contains a series of activities such as the process has been described above and presented in a separate process, such as the requirement specification, design implementation software, testing . After each step is defined, this step in the sign off and followed the development in the next step.
The steps that are important in this model is
• The analysis and specification
Services, goals and constraints resulting from consultation with users system. Then everything is made in the form that can be understood by users and staff developers.
• Design systems and software
Divide the system design process needs to be system software or hardware. The process produces an overall system architecture. Design software, including the functions of system software that may be in the form of the transformation in one or more programs that can be run.
• Implementation and unit testing
During this stage, the design software we realize as a complete program or program unit. Test units, including units that each test according to specification.
• Integration and system testing
Unit tested and integrated the program into a complete system for menyakinkan that software requirements have been met. After testing, the system was delivered to the customer.
• Operation and maintenance
This phase is long. System installed and used. Maintenance, including correction of errors not found in the previous step. Improvements to the implementation of the system and increasing service needs of the new system as found.










Iteratif Model


Step-step model Iteratif

1. Initial planning
Starting from the initial planning.

2. Planning
This stage, the stages where the plan is structured in such a way to get a system that both the good and the output

3. Requirements
Analyze user needs and the needs of the system
4. Analysis and design
In this process is conducted to analyze the process of the system will be developed and began to design the system.
5. Implementation
In this process is the system that has been created.
6. Testing
At this stage, the system will try to test, to see if in conformity with the desire.
7. Evaluation
This phase will be done from the system evaluation have been made.

Spiral model





Spiral model describes the process as a spiral which is divided into a 4 quadrant:
Processes are beriterasi according to a cycle using a prototyping approach.
• Planning
Namely the duties to plan, gather for the alternative system that will have • Risk Analysis
is to evaluate the alternatives based on the objectives and constraints. Included here to identify the risks and pastian • Engineering
That is a task that is required to build one or more representations of apikasi it. • Cusomer Evaluation.
Re-evaluate the system that was created with the customer














Approach of System Development

Classic Approach of vs approach of structure
1. Classic approach
• Steps in SDLC
• Do not involve consumer, more is emphasizing of system analyst
• Problems: difficult development, expense of costly treatment, possibility of big mistake, efficacy less well guaranted, applying internal issue
2. Approach of structure
• Consumer involve from early to determine requirement of system
Using tools-tools like data of flow diagram
Approach of rasher of vs approach of system
1. Approach of rasher
• Emphasizing at a[n activity or application
• Heedless of entirety target
2. Approach of system
• See system as one intact unity
• Emphasizing at goal achievement by all

Approach of vs bottom-up approach of top-down
1. Approach of bottom-up
- Started from level under that is operational
- Representing classic approach marking
- Recognized with term of data-analysis

2. Approach of top-down
- Started from level to the that is planning of strategy
- Representing marking approach of structure
- Recognized also with decision-analysis
Approach of vs sistem all approach of moduler
1. Approach of sistem all
- Developing system at a time and totally
- Representing classic approach marking
2. Approach of moduler
- Breaking complicated system become the parts of simple
- developed system become timely, easy to to be comprehended and looked after
Representing marking approach of structure
Approach of approach great-loop vs evolutionary
1. Approach of approach great-loop
- Developing system at a time use sophisticated technology
- High Beresiko and finish many expense
2. Approach expand approach evolutionary
- Applying sophisticated technology for certain applications
- Developed to follow requirement
- Cost effective and can keep abreast of technology






Methodologies System Development

Methodologies
- Methods, procedures, concepts of oekerjaan, postulates and orders used by an science, artistic or the other discipline.
Method
- An way of systematic to do something
Alhoitma
- Medley Procedure to solve an problem

Three Type Methodologies
Functional decomposition
- This methodologies of menekanakan at trouble-shooting of system into smaller sumsistem-subsitem so that will be more easy to to in pahami,dirancang and applied
- Example of: HIPO, Stepwise Refinement, refinement stepwise iterative, hiding information
Data-Oriented
- Emphasizing at processed data characteristic
1. Data-Flow oriented : modules according to data element type
2. Data-Strucplease methodology of meaning the explain , oriented algorithmture and method: input structure and of output
Prescriptive
- Is usually provided by factory maker of software

Appliances In System Development
- Appliances system development ;
- Hipo diagram , used by methodologies of hipo and in other methodologies
- Data of flo diagram, used by methodologies of struktured system analyse and design
- Struktured chart , used by methodologies of struktured system analyse and design
- SADT diagram , methodologies used of SADT
- Wanier / methodologies orr,digunakan of warnier / Orr
- Jakson'S diagram used by methodologies of akson system of Development
- Appliance using schema
1. Charting Activity: depicting activity, example of: Chart Gant, flowchart, etc
2. -Charting Layout: depicting tataletak
3. - Relationship charting Personal: depicting personnel [relation/link], example [of]: chart organization, chart distribution working
Techniques In System Development
- Technique management of is project of for schedule of[is project of, example [of]: CPM and of PERT

- Technique o find fact to collect and determine data / fact
1. Interview
2. Observation
- Technique o analyse expense / benefit of cost-benefit and of cost-effectiveness analysis
- Technique o run meeting.
- Technique inspection.








System analyst & programmer
• Analyst system: study of the problems and determine the needs of the system to identify solutions.
• programmers: write a program code based on the building design is created by the analyst.
• Analysts duty system bridge the knowledge gap that occurs between the user and system programmers.
Knowledge that is required
• Technology data processing, computer programming and
• Knowledge of general business
• quantitative methods: regression, linier programming, etc.
• problem-solving expertise
• Skills of communication between personnel
• Expertise foster relationships between personnel