First Observation and Analysis Requirement

System Investigation Concepts

The problem is the gap in goal difference between the system and the actual system conditions. Investigation used to find out the cause of the failure of a system before an action. with the investigation, an analyst will understand the problem and the flow system further. Investigation aims to stabilize or show the actual problem occurred while analysts as a way to understand the system in depth.

Many reports in the detection problem may not actually be real or can not be solved. This may be because:

• Goals that are too difficult or the ideal so that might not be reached.
• The system can not be developed because of lack of resources, attitudes, or both.
• Measurement system that is not accurate.
• Statement of purpose of the system that is behind (statement of goals is dated).
• The gap between the ideal system and the system at this time is temporary (the gap between the ideal and the current system is temporary and will decrease given patience).

In problem solving, should provide an explanation of:

• Explanation of the condition system that runs through the investigation in detail.
• Getting a consensus that the ideal system.
• Developed several alternatives to reduce the difference (gap) between the ideal system with which the system is running.
• Selecting the best alternative and sell it to management.

Constraints in the system of investigation

In conducting investigations, there are several barriers or obstacles that will occur, among other issues:

• Time. The problems that often arise in the completion stages of investigation is the lack of resources resulted in the only part of the investigation can be conducted. Time is also related to the cost problem is required.
• Cost. The cost is usually related to the duration of the investigation. So that management will give the limits of cost.
• Knowledge. Knowledge of the analyst influence the results of the investigation.
• Politics. Some parties may distribute certain issues that can hamper the investigation.
• Intervention. There are parties who try to intervene or control activities in the investigation, which can disrupt or cause a disruption.

Recommendations

Results of the investigation is a recommendation, which is one of them is as follows:

• Does not take any action because it found no problems.
• Perform system maintenance for problems that small.
• Improving the skills or the ability to run or use the information system.
• Consider modifications to the system in total, so the need to replace it with the thought that the new system.
• Place going into the development plan system which is done immediately.

Investigation tactics

• listen, do not lecture.
• Do not provide solutions to the initial problem
• Comparing the story
• Look for reluctant responses
• Probe for logical inconsistencies
• Observe your effect
• Require hard work, giving rise to boredom
• Avoid problems politics

Investigation Techniques

Investigation techniques included:

1. Direct (internal) Probes
   • Questionnaire
   • Interview
   • Observation

To find out directly what is happening in the environment. Internal probes is a source of disruptive, the differences arise because of attitude. Internal probes used as a richer and the justifier of the facts that truer group of facts. There are three techniques to investigate directly, ie with:

2. Indirect (external) Probes
   • Flow of the procedure (procedure flow)
     Undertake the operational procedures of the facilities (vehicles) for new employees understand their work and experience to handle employee problems.
   • Learn the document (document review)
     Is to find and gather important documents (critical document).
   • Sample (sampling)
   • Tabular (Tabular tools)
     Tabular is a check list (checklists) to find the conflict (discrepancies) in the transaction flow.

Indirect (indirect (external) probes) Activities that can be done quickly and not visible from the operational personnel, so that the outside can see or something that is hidden from the user community. This activity will dominate at the beginning of the SDLC activities, to further deepen internal probe. Some of the things that are associated with this technique include:

Current System Description

Description of the system include a clear explanation at this time:

• Inputs
• Outputs
• Files
• Data elements
• Transaction and document action volume
• Data flow diagrams

Requirement Analysis

In doing this step will be achieved 4 goals, namely:

• Describe the system at this time in full.
• Describes the ideal information system.
• Bringing information system to the ideal conditions at this time with attention to resource constraints.
• Provide encouragement to the confidence of this team into the development system.

Requirement analysis phase is the intensive interaction between the systems analyst with the community system (end-user), where the system shows the development team to gain expertise and confidence in the responses, so get a good participation.

Method Analysis Requirement

• Interviews
• Questionnaires
• Observation
• Procedure Analysis
• Document Survey
• Sampling

Resource constraints

• Time
• Money
• Expertise
• Technology
• External factors

Analysis Requirement Document

1. Referral (conduct) analysis.
   • Relationships with end users.
   • Analyze the records, forms and reports.
   • Observation process.
   • Analyzing the methods used.
   • Problems in data collection.
2. User Requirement
   • What are the actual needs.
   • Reporting needs (type and frequency).
   • Training needs.
   • The influence of the new system.
3. Constraint system
   • Explain the constraints of time, cost, expertise, technology, and external factors.
   • Realistic system.
4. Documentation
   • Instrument data collection (needs questionnaire, interview).
   • Consensus statistics.
   • The flow of data in logical and physical.
   • Initial element in the data dictionary.

Generating Systems Alternatives

How is the performance gap closed?

• Creating an alternative to solve the problem of information system.
• Alternatives are defined in the best wise (most expedient).

Options Strategies

• Distributed versus centralized processing

Changes in decision-making information from the centralized data processing to the end user Decentralized responsibility center.

• Integrated versus dispersed databases (a database system spread)

System designer must consider the data are entered in the database and enter the File.

• Surround strategy of system development

About important environmental strategy in the case of company takeovers because the information system of other companies may vary with the company at this time.

Options Tactics

Management decide now or later, the opponent modification, and configuration SDLC. This selection is done before the selection operation.

Now or later

• Technology

Is a breakthrough technology requires consideration for several years to come.

• Cash flow

Now or later
a. Technology.
Is a breakthrough technology requires consideration for several years to come.
b. Cash flow.
The condition of cash flow the company will need to be considered in the development or replacement of the system.

• Resources expertise

In the development of the system need to consider recruitment of experts involved in the perancangannya and in pemakaiannya later.

• Politics

Many information system currently proposed by someone in the company. For one or more reasons, the information systems department may choose, or slow the development of a replacement system.

Speed versus Charge

Alternative information systems will be the first time a quantitative comparison of the cost. Therefore have difficulties to adjust the speed of the increase in the form of cost savings.

Eight Options on the Design Operational

Design choices are grouped into input, processing, and output. Each group can have the following options:

• Input

1. On-line versus off-line data entry.

Off-line data entry does not have the ability both to validate the transaction immediately. Therefore, the on-line data entry still used in the recommended system configuration information.

2. Keyed versus machine-readable data entry.

Machine-readable data entry can increase speed, reduce the income data errors, and save costs for workers (save human costs). However require a large investment in equipment and maintenance.

3. Centralized versus Decentralized data entry.

Decentralized entry is faster but the error level high because many users who enter data. Machine-readable entry requires decentralization that provides income benefits in the process of capturing the speed of data source (point of sale).

• Processing

1. Batch versus real-time update record.

Batch processing the update rekord long, suitable for centralized data entry. Real time processing equipment costs and speed the process up.

2. Sequential versus direct access to records.

Sequential access is associated with batch processing. Direct access to the related real-time processing.

3. Single versus multiple-user updates of records.

Design a system for multiple-user more complex (complex) in security access and update the record simultaneously. Kekomplekkan (complexity) occurs when the speed is important and the application process with real-time.

• Output

1. Traditional versus turnaround documents.

Traditional document is a document that pendataannya to how the system is done through the keyboard (key input). Turnaround documents to the collection system is done through a machine document

2. Structured versus inquiry-based reports.

Structured report is created in a standard format and provided on a regular basis, while the inquiry-based reports are based on the request in accordance with the format of this request. Seringkalli-base inquiry report found in the environment where real-time data must be accessed quickly.

Comparison Tactics

There are three ways a system (A) can be more superior than the other system (B).

1. Have a cost lower than B and both systems have the same advantage.
2. Have a lower cost than B, and A will also have the advantage that more than that of B.
3. A and B cost the same, but A has more advantages.

Method for Comparison System

There are 4 methods used to compare two or more
information system, namely:

• Break-even analysis (BEP)
• Payback period
• Discounted payback period
• Internal rate of return (IRR)

Cost categories

Basically the costs are divided into categories:

• Hardware: Mainframe, minicomputers, microcomputers, peripherals and equipment.
• Software: systems, utilities, and application software.
• People: analysts, programmers, operators, data entry personnel, and so forth.
• Supplies: paper, tapes, disks, and so forth.
• Telecommunications: modem, local area network cabling, multiplexors, front-end processors, and so forth.
• Physical site: air conditioning, Humidity control, security, and so forth.

Costs of Nature

Shows the changes in the cost of the future compare with the cost information system through the life of the system. To accomplish this, there are three models operating cost information system, namely:

• Linear.
• Exponential.
• Step function.

When Costs Occur

Cost information system can occur once or continuously. On-time costs, development costs are related to the development of the system, and recurring costs, operational costs are associated with the operating system information every day. The difference between one-time (development) and recurring (operational costs) are often from the material (matter).

The Information System Factor

Some of the factors that lead qualitative performance information system that both:

• Reduce the error level (increased accuracy).
• Reducing the time to fix the error.
• Reduce the response time of interactive workstations.
• Accelerate the provision of the report (information).
• Improving the security system.
• Propagate update the source record is active.
• Increasing user satisfaction. Several factors can be measured, but not in money.

The Company’s Strategy

There are factors the company strategy is as follows:

1. Customer satisfaction (customer satisfaction).
2. Increase sales (increased sales).
3. Consumer and vendor commitment (customer and vendor commitments).
4. Information product marketing.

Here are some guidelines for presenting the study system successfully:

1. Make short presentations to avoid exceeding the given time.
2. Reducing the technical explanation of detail may be minimal. Better describe the technique in detail in the specific questions are asked than not.
3. Presented clearly, so that does not use berantarkan visual equipment.
4. If using a model (prototyping), take bring portable workstation (laptop). Demonstration is more direct, informative and interesting than inactive visual aids.
5. Emphasize the benefits of the proposed information system in accordance with several alternative conditions experienced by the company. Do not limit the other system information. Use komparasi financial values such as ROI (return on investment).

Go / No-go decision

Top management must decide to continue (go) to develop a new information system or slow or does not approve the development of the system (no-go). If top-level management decisions, decided to mengembangkankan systems, information systems departments have begun the design process (designing) the next stage. If top management does not approve the proposed new information system, the systems development life cycle (SDLC) is stopped. Rarely decision as that.
Often, top management to find a problem with the system study. The problem is not serious enough cause termination of project, but they re-work (rework system study). This decision is the basis for the waterwall models of systems analysis. Model explains some of the stages of the repeated. Sometimes, the department of information systems decision making phases repeat (repeat stages) before the (present) system study. With the alternative, the decision SDLC phases of a repeat or not previously called with the go / no-go decision. If the top management to approve the proposed development of a new information system, the next stage in the SDLC is system design.

reference :
Martin, Merle P., Analysis And Design of Business Information Systems,
Macmillan Publishing Company, New York, 1991.