Necessary System Development

1. What is the importance of developing an information system?

System development can be meaning arrange a new system to replace old system as a whole or repair system which already there is.

Old system requires repair or replacement because:

• there is problems
• not all right in the organization growth system
• to reach a opportunities
• there is directives

2. What is the purpose or goal of developing an information system?

Destination of system development:

• Solving problems
• reach a opportunities
• fulfill given instruction

3. What are the organization’s expectations after implementing an information system?

With already expanding of new system, hence expected will happened increase on new system. This increase related is:

• Performance

Can be measured from throughput and response time

Throughput is amount from work can do by certain moment. Response time is average time delay in two transactions or work added with time of response to responds to that work.

• Information

Increase to quality of presented information.

• Economy

Increase to benefits or advantages or decreasing cost that happened.

• Control

Increase to control for detecting and repair mistake and also fraudulent will happen.

• Efficiency

Increase to operation efficiency.

• Services

Increase to service given by system.

4. What are the principles of developing an information system?

Principle system development

• System for Management
• developed system is big infestation

All infestation must be consideration:

• 1. 1. all alternative in must be investigated
     2. the best investigation must valuable
• developed system needed educated human
• phase of work and task must do system development
• developed system process not must partaking
• don’t fear to canceled project
• documentation must be guidance in system development

5. Please explain at least three system development life cycle models!

Model Waterfall has a 5 statement:

a. 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.

b. Design: in this stage us does systems analysis process, future 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.

c. 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.

d. 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.

e. 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.

Model Iteratif have a 8 statement:

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

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

b. Planning: planning here be a thinking that ripe towards system that be made.

c. 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.

d. Analysis and design: in this stage us does systems analysis process, future 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.

e. 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.

f. 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.

g. 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.

h. 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.

Model Spiral:

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 specification. 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.

6. Please explain approaches of developing a system!

• classic approach opponent structure approach
  1. classic approach
     1. Steps in SDLC.
     2. not involve consumer, more emphasizing system analyst
     3. Problems: difficult development, expense costly treatment, possibility big mistake, success less, problem of applying
  2. structure approach
     1. Consumer involved from early determining requirement of system
     2. Using tools-tools like data of flow diagram

• approach of rasher opponent approach system
  1. approach of rasher
     1. Emphasizing at application or activity
     2. Heedless of entirety target
  2. approach system
     1. See system as one intact unity
     2. Emphasizing at goal achievement as a whole

• approach bottom-up approach opponent to the up-down approach
  1. approach bottom-up
     1. start from level bottom is operational
     2. is a classic approach marking
     3. recognized with term of data-analysis

• 1. up-down approach
     1. start from up level is planning of strategy
     2. is a marking approach of structure
     3. recognized also with decision-analysis

• approach system totally opponent approach modular
  1. approach system totally
     1. Developing system at a time and totally
     2. is a marking classic approach
  2. approach modular
     1. Breaking complicated system become the parts of simple
     2. developed system become timely, easy to comprehended and looked after
     3. is a marking approach modular

• great-loop approach opponent evolutionary approach
  1. great-loop approach

• 1. 1. Developing system at a time use sophisticated technology
     2. high risk and finished many expense

• 1. evolutionary approach
     1. Applying sophisticated technology for certain applications
     2. Developed to follow requirement.
     3. Cost effective and can keep abreast of technology

7. Please explain the meaning of methodology, method and algorithm!

• What that methodology?

Methods which is used in science

• What that method?

Way of systematic to do something

• What that algorithm?

Procedure to solve problem

8. Please explain the three classifications of development methodology

• Functional decomposition

a. Emphasizing resolving of system become subsystem.

b. example: HIPO, Stepwise refinement, iterative stepwise refinement, information hiding

• Data-oriented

Emphasizing at data characteristic which is processed

• Prescriptive

Usually provided by factory maker of software

9. Please mention tools for developing a system!

• In form of graph: HIPO, SADT, Jackson’s Diagram, and others.
• Appliance using schema:

a. Activity charting: depicting activity, example: Chart Gant, flowchart, etc

b. Layout charting: depicting to arrange situation

c. Personal relationship charting: depicting personnel relation example: chart organization, chart distribution working

10. Please explain techniques used in developing a system

• Management technique of project of? for schedule project , example : CPM and PERT
• Technique find fact? to collect and determine data / fact
• Technique cost analysis / benefit? and cost-benefit of cost-effectiveness analysis
• Technique run meeting
• Inspection technique

11. Please explain the differences of being a system analyst and a programmer and also mention what are the knowledge a system analyst should posses

• System analyst: studying problems and determine requirement of user of system to identify resolving
• Programmer : writing program code pursuant to designing made by analyst
• System analyst undertake to link difference of knowledge that happened user of and system of programmer

Needed knowledge:

· Data-processing technology and computer of programming

· Knowledge of business in general.

· Quantitative method: regress, linear programming, etc

· Trouble-shooting expert

· Communications expert between personnel

· expert construct relation between personnel