Minggu, 08 Maret 2009

General Observation System Developments

GENERAL OBSERVATION SYSTEM DEVELOPMENTS

 

 

 

System cleyelopment is to pile up a new system to change the old system entirely or repairing the system that already exist before. The important thinies in the information system development is:

1.      There problem that to appear in the old system.

a.       Problem in the old system causing it can’t operated like wanted one.

b.      Grow of organization that causing we must to pile up a new system.

2.      To reach up portunities in the information speed competition market or efisiency of the time is a factor of success or not the strategy  and plans that already piled up to the change.

3.      There are directives not meaning the system is developed by the command from the leader but organization competition.

 

The aims of system information development:

  1. To prevent the problems on this contecs is mean that we must do the reparation on problems that already exist on the old system to make a new system that can repairing the problems and also to fill the need of organization grow.
  2. To reach the change we must can improving the system in the system in the it’s information speed or efficiency of the time for the success of organization in strategy and the plans that already piled up.
  3. To fulfill the intruction thet gived. Can fulfill what organization needs from new system to compete with other organization.

 

The increase performance on the new system work. That meke more effevtive. The ob system can be see from the throughput and response time. Throughput is the total of job that can do in an sure time. Response time is the range of the time between first transaction with second transaction. Improvitation economy of profit and dagrease the production cost.Improving control,of control to detec and repair the mistake and not fair that will heaven and already heaven.

The principle of system development.

             Processing the system development we must know some process,such as:

  1. System for management.

After developed the information of this system will be used by management.

  1. Sytem that already developed is high capital infestement.

This system is developed by very big capital infestement

-         to minimize the lost opportunity cost.

-         Cost benefit analyse and cost effectiveness analyse.

  1. System need the people that already have the skill.

In this vector the important is human.The human not must have formal education.

  1. Work stages

System development life cycle is consist of the work and job of the work that must be do.

  1. System development not must straight.this mean stages can be not straight,but can be do together.
  2. Don’t fear to cancel the project,to decise to continue or cancel the project must evaluated carefully.
  3. System documentation,must made in the processing time since that system development is still and process,because this documentation can a pair from result of any part of system development.

System Development Life Cycle

 

Waterfall Model

Waterfall Model explanation:

1. Requirement, in process requirement this is systems analysis does need collecting process from customer and or top management either from aspect area also business strategy, towards system and or desirable application.

2. Design, in this stage us does systems analysis process, fitur that need, need from application that be made good to also the application. Beside that, here we also begin to make design plan from system, like interfaces delegation, the data structure, the architecture, and as it.

3. Implementation, implementation process has been continuation from where did we begin to implementation design that made to into program codes that be read by engine language.

4. Verification, process verification here same like testing process towards system and or application that made. This process focus in internal logic from application that made, as certain that any line coding checking. Beside that here we also have done testing process towards possibility towards errors from system that made.

5. Maintenance, process maintenance here be repair process and maintenance towards system that made. Repair process here done when application and or system that made to experience error after to customer so that must necessary repair process towards system and or caused by development towards an OS so that application must be repaired again to be update.

Iteratif Model

Iteratif model explanation:

 

Iteratif Model here same with waterfall model, here found same processes, like requirement, design, implementation, and testing (verification).

    1. Initial planning, be beginning planning process and or beginning ideas to make a system.

    2. Planning, planning here be a thinking that ripe towards system that be made.

    3. Requirement, same like in process requirement waterfall model, here systems analysis does need collecting process from customer and or management on towards system and or desirable application.

    4. Analysis and design, in this stage us does systems analysis process, fitur everything that need, need from application that be made good to also the application. Beside that, here we also begin to make design plan from system, like interfaces delegation, the data structure, the architecture, and as it.

    5. Implementation, implementation process has been continuation from where did we begin to implementation the design that made to into program codes that be read by engine language.

    6. Deployment, process deployment here purpose has been distribution process towards system that made, in our meaning distributes before hand system to society before do testing so that we know our system deficit.

    7. Testing, process testing here we have done testing towards system and or application that made. This process focus in internal logic from application that made, ascertain that any line coding checking. Beside that here we also have done testing process towards possibility towards errors from system that made.

    8. Evaluation, process evaluation here be repair process, maintenance and renewal towards system that made. Repair process here done when application and or system that made to experience error after to customer so that must necessary repair process towards system. Maintenance process and renewal be done caused by development towards an OS so that application must be repaired again to update. In renewal process here will return to do process planning, data collecting (requirement), analysis system and design, implementation, deployment, testing and return again to evaluation. if there development again, so this cycle be repeated again.

 

 

Spiral Model

 

 

 

Spiral model explanation:

 

Spiral model is divided to be 4 task areas, that is:

 

    1. Determine objectives, in this process us will determine what will be made system, either from also output from it system.

    2. Identify and resolve risk, here we do identification process, planning and analyze risks may be happen. In identification process and planning, we must define before hand resource, time precision, and other related information project with system that we shall make. While in risk analysis process here we do analysis towards risks may be happen, between management or technical.

    3. Development and test, in process development and test this is us do engineering process, construction and testing towards system that be made. In engineering process and construction, we do process coding to make a application. While in testing, we do testing process towards system or application that we have made.

    4. Plan the next iteration, here we do iteration process for plan next and or evaluation in the event of request from customer in order to change towards system or application.

 

In this spiral model, when is process revolutionary begun, system engineer team moves clockwise surround spiral begun from the kernel. Spiral rotation first track produces development from product spesification. Spiral rotation furthermore may be worn to develop a prototype, and progressively develop system version will be increase. Each track that pass planning region produces to setting in project plan.

 

Approach System Development

 

Found several approach to develop system, that is:

 

    1. Classical approach vs structured approach (looked at from methodology that used).

    2. Piecemeal approach vs system approach (looked at from target that be achieved).

    3. Bottom-Up approach vs Top-Down approach (looked at from manner determines need from system).

    4. Total-system approach vs modular approach (looked at from manner develop it).

    5. Great loop approach vs evolutionary approach (looked at from technology that used).

System Development Approach

           

            Classical Approach vs Structured Approach

-         Classical approach is opponent of structured approach. Classical approach methodology is system development by following the stages in this life cycle system.

-         Classical approach is also known as traditional approach. This is an approach in system development that following stages of the life cycle without use the remarkable equipments and techniques.

Problems in classical approach is :

1.      Softwere developing is more dificull because the shortage of equipment and techniques in developing the system and result of the softwere developing procces is become not objective and dificul to do.

2.      Carity cost of the system will more expensive.

3.      The mistake opportunity is high.

4.      System success ratio is small.

5.      Trouble ratio is big in approach system.

 

Structured Approach

            Because many problems in classical approach, the need of better system develop is start to feel needed. But until now, still many people not know that only follow the life cycle will not make information system develop will success. Structured system develop concept is not a new concapt. The ansambling company technique and sircuit model of electronic equipment are two example of this concept that used in the many industries.

 

Great-loop approach vs evolutionary approach

-         Great-loop approach :

a. Developing the system together using good technology.

b.   High risk and spend a lot cost.

 

-         Evolutionary approach  :

a.       Use the great technology for some application.

b.      Developed for follow the need.

c.       Small cost and can follow technology development.

 

System develop methodology

            In system develop, methodology is needed, they are unites of method, procedures, concept of job, regulations, ponstulats, that used in a science, arts or other disciplines.

            Method is a systematic technique to finish anything. By following method and procedures that methodology give, system develop is hoped will be able to finished and successful. Procedures stages of problems answer known as alogarithme.

 

Three type of methodology develop are :

1.      Functional decomposition : Decide system become subsystem. For example : HIPO, stepwise refinement, iterative stepwise refinement, information hiding.

2.      Data-oriented : Seeing on data characteristic that proccesed.

-         Data-flow oriented : modules with data element type.

-         Data-strucplease explain the meaning of methodology, method and algorithmture oriented : Input and Output structures.

3.   Prescriptive : Usually prepared by softwere maker company, and that ones    

                  in this methodology category are ISDOS, PLEYSYS, PRIDE and SDM/70  

Tool In System Development

 

Tools that used in a methodology usually shaped a picture or diagram or graph. Graph formed system development tools, that is:

 

    ? HIPO diagram

    ? Data flow diagram

    ? Structured chart

    ? SADT diagram

    ? Warnier/Orr

 

Beside graph formed tools, found several graph formed tools has general likes Chart. Chart can classified as follows:

 

    1. Chart to describe activity (activity charting).

    ? System flowchart

    ? Program flowchart that can be in the form of:

    ? Program logic flowchart

    ? Detailed computer program flowchart

    ? Paperwork flowchart or form flowchart

    ? Database relationship flowchart

    ? Process flowchart

    ? Gantt chart

    2. Layout charting

    3. Staff relatioanship charting

    ? Working distribution chart

    ? Organization chart

 

 

Technique In System Development

 

Techniques that can be used in development system, that is:

 

    1. Project management technique, that is CPM (Critical Path Method) and pert (program evaluation and review technique). This technique is used for project scheduling.

    2. Fact finding techniques, that is technique that can be used to gather data and find facts in study existing system, that is:

    ? Interview

    ? Observation

    ? Questionnaire

    ? Sample collecting

    3. Cost-effectiveness analysis or cost benefit analysis

    4. Technique to run meeting

    5. Technique inspection/walkthrough.

 

 

Analysis System And Programmer

 

Analysis system is one who analyze system to study and identify that problems and determine user needs system. Programmer is one who write program code to a certain application based on has planned to get up that made by system analyst.

Function and or task from a analyst system that is as mediator or liaison between system user with programmer. Analyst system must realize right second knowledge differ about the computer technology to can communicate with programmer and knowledge about application that be developed so that can communicate with system user.

 

Knowledge And Skill That Need System Analyst

 

Found several vast eruditions and skill that must has by a system analyst, that is:

 

    1. Knowledge and skill about data processing technique, computer technology and computer programming.

    ? Technical skill that must has belong skill in tool use and technique for application software development with skill in use computer.

    ? Technical knowledge that must has cover erudition about hardware, data communication technology, computer languages, os, utilities, and another.

    2. Knowledge about business in general.

    This knowledge be wanted so that system analyst can communicate with system user.

    3. Knowledge about quantitative method.

    System analyst use many quantitative methods in build application models, like dynamic programming, regresion, network, decision tree, trend, simulation and other as it.

    4. Trouble-shooting skill.

    System analyst must has ability to put complex troubleshoots that is faced by business, divide problem into parts, analyze it and then must can return composed to be a system can overcome troubleshoots.

    5. Communication skill delivers staff.

    System analyst must has ability to hold communication either through tongue or article. This skill is need in interview, presentation, meeting and report maker.

    6. Skill builds connection delivers staff.

    Human is factor critical insides system and human character one with another differ, so that need a skill to build connection delivers staff.