quiz 4

FIRST OBSERVATION AND ANALYSIS REQUIREMENT

Investigational System Concept

The problem is the gap in goal difference between the system and the actual system conditions.

Many reports on the detection problem may not be real,because of several things:

1. A goal that is too ideal, too difficult to achieve

2. Lack of resources and or attitude

3. Measurement system is less accurate

4. System that is the purpose behind Goal system that is out of date

5. The difference between the system and the system idel while

Problem solving:

1. Description of the condition of the system that runs through it in detail

2. Getting a consensus that the ideal system

3. Developed several alternative

4. select the best alternative

For the purpose of the investigation indicate that problems are actually happening

Constraints in the system of investigation

Investigations in several problems that often appear are:

1. Time

2. Cost

3. Knowledge

4. Politic

5. Intervention

Recommendations

Results of the investigation is a recommendation that contain, among others:

- Not to take any action because they are not finding a problem

- Perform system maintenance for a small problem.

- Improving the skills or the ability to use the system

- Consider modifications to the system in full

-Putting the problem to occur in the development plan system is carried out immediately

Investigation Tactics

Why we need tactics?

- Finding a problem for all

- Knowing for the emergence of problems

- for Determining the right solution

Investigative tactics need to be done by all elements of the system in order to receive offer solutions without disrupting their activities.

Some of the tactics that can be done:

- Listen to the user's system

- Don't give the early breakthrough

- Compare the stories of some of the user system the same case

- Note the logical inconsistency problem

Investigation Technique

Direct (internal):

1. The questionnaire

2. discussion

3. Observation

Indirect (external):

1. Flow of the procedure

2. Reviewing documents

3. Sample

4. Tabular

Current System Description

1. Inputs

2. Outputs

3. Files

4. Data elements

5. Transaction and document action volume

6. Data flow diagrams

Requirement Analysis

phase of intensive interaction between the systems analyst with the end user where the system shows the development team expertise to get feedback and trust so that the user get a good participation.

4 goals want to achieve:

1. Explain the complete system

2. Information system that describes the ideal

3. Bringing information system to the ideal conditions at this time with attention to resource constraints

4. Providing encouragement to the user's confidence in the system development

Method Needs Analysis

1. discussion

2. Questionnaires

3. Observation

4. Procedure Analysis

5. Observation documents

Resource constraints

1. Time

2. Money

3. Expertise

4. Technology

5. External factors

Needs Analysis Document

- Analysis direction: Relationships with end users, the observation process, problems in data collection

- The user needs: The need actual, reporting requirements, training needs and the influence of the new system

- System constraints: Explain the constraints of time and cost, expertise, technology, and

-external factors

- Documents such as data collection instruments, statistical consensus, the logical flow of

-data and phisik, data elements in the initial data dictionary.

Generating Systems Alternatives

How do I approach the condition of the system at this time with the condition of the ideal system?

- Creating an alternative to solve the problem of information system

- Best alternative is applied wisely

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 database

System designer must consider the data are entered in the data base and into 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.

Generating Systems Alternatives

Strategy Options

Options is done before the design operational

Designing Operational Options

Options can be grouped into the design

1. Input

a. Online Vs Off Line Data Entry

b. Keyed Vs Machine Readable Data Entry

c. Centralized Vs Decentralized Data Entry

2. Processing

a. Batch Vs Realtime record update

b. Sequential Vs Direct Access to records

c. Single Vs Multiple User update of records

3. Output

a. Traditional Vs Turn Around Documents

b. Structured Vs Inquiry based reports

Selecting The Proper System

Compare tactics: systems based on the comparison of costs and benefits relative; There are 3 ways the system "A" said the system is superior to the other if :

- "A" has a cost lower than "B" and their profit same.

- "A" has a cost lower than "B" and "A" result in more profits from the "B"

- "A" and "B" have the same costs but the resulting benefit "A" more.

Several Comparative Method System

1. Break Even point Analyisis

2. Payback Period

3. Discounted PayBack period

4. Internal Rate of Return

Cost category

1. Hardware

2. Software

3. People

4. Suppliers

5. Teleccommunications

6. Physical sites

Cost details

Comparing the cost of information systems through the life of the system, analysts projected the cost changes for the future and there are 3 models cost information system, namely Linear, and exponentially Step Function.

Information system cost happen in one time and be able happen continuous.

- Cost information system that occur only once the cost ontime and development costs that occur during the development of the system.

- Cost information system that occur continuously among reccuring cost and operational cost where the cost of this is the case when the operating system information every day.

The Information System Factor

Qualitative factors that lead the performance information system that both of them:

1. Reduce errors

2. Reducing the time to fix errors

3. Reduce the response time from the workstation alternative

4. Accelerate the time of providing information

5. Improve security systems

6. Propagate update records on the source

7. Increasing user satisfaction

Company Strategy Factor

1. Customer satisfaction

2. Sales increased

3. Consumer and vendor commitment

4. Information marketing products

Representation Learning System

1. Make short presentations

2. Reduce the detail description techniques

3. represented clearly with visual tools

4. If using a model using a tool such as a laptop so that more informative

5. Emphasize the benefits of the proposed system with some alternative information that is

appropriate conditions experienced by the company.

Decision to continue or No

- If the company decided to develop the information system, the department will do next, namely the System Design Process.

- If then the System Development Life Cycle (SDLC) will be terminated.

- Often the problem will be found with the system and the study and top management will usually ask for the re-employment system to study.

- Model will describe some of the stages of the repeated and sometimes the information will make a decision before the repeat stage system of study.

- With the alternative, the decision to repeat a previous stage SDLC or not called Go - No-Go Decision.

Importance of developing an information system

Importance of developing an information system

problems

By using the information system of the problems that usually can be completed with the old manual way with the information system problem is resolved more quickly. For example in the mini market, there is a cashier who has to record transactions a day with the usual manual may be slow but the results, using the information system can be done more quickly.

Irregularity in the growth of System Organization

In an organization there are certain data that must be processed, when organisai is growing data that diolahpun needed so that the larger a system is good, if not use the information system so that both orgnisasi growth will be hampered

opportunities

System information also assists in achieving opportunities. And also make it easier to seize opportunities.

directives

Informs the system can more quickly provide instruction, for example, the confusion are a company looking for a document, then the system with the information we provide live instruction to the system to search for it.

Destination development system

Development means the system can arrange a new system to replace the old system as a whole or improve the existing system. The old system need to be replaced or repaired is because some things, are as follows:

• The existence of the problems that arise in the old system. The problems that arise can be:

a. Irregularity

Irregularity in the old system caused the old system can’t operate in accordance with that expected. This irregularity may be operating inefficiently.

b. The growth of the organization

Growth of the organization must be the establishment of a new system. The growth of these organizations is the information needs of the area, the volume of data increases, changes in the new accounting principles.

• To seize opportunities

Organization began to feel that information technology should be used to improve the provision of information so that it can support in the decision making process that will be done by management. In the competitive market, speed or efficiency of the information isn’t to determine the success or strtegi plan and that plan has been developed to reach the opportunities that exist. If competitors can utilize, while the company can ‘t take advantage of this technology, the kesempatankesempatan will fall ketangan competitors.

• The instructions

Preparation of the new system can also occur because of instructions from the top leadership or from outside organizations, such as government regulations.

Expected on the new system

Has been developed with the new system, the expected increase will occur, the increase in the new system.

• Performance

Improvement of the performance of the new system which will be most effective. Performance can be measured from the throughput and response time.

• Information

Improving the quality of information presented.

• Economy

Improvement of the benefits or the benefits or a decrease in the cost-reduction.

• Control

Detect and fix errors that occur and will occur.

• Efficiency

Improvement of operational efficiency.

• Services

Improvement of the services provided by the system.

The principle of the development system

When you do the system development process, several principles must not be forgotten. These principles are as following:

• System developed for the management

After the system finished developed, which will then use information from this system is the management, so that the system must be able to support the needs that are required by management.

• The system developed is a large capital investment

System that you will develop the funds that weren’t a little. So every investment capital should consider the following 2:

a. Investigate all alternatives (minimize cost of lost opportunity)

b. Investigation must be best value: cost-benefit analysis & cost-effectivenes analysis

• System that educated people need to be developed

People involved in the development and use of this system should be the people who educated about the problems that exist and to solutions that may be made. Educated here should not mean a formal, but it can be done in the exercise work.

• Stages and work tasks that must be made in the process of system development

System development process generally involves several stages and involves the work of personnel in some form of team for it. Experience shows, without the planning and coordination work that well, then the system development process will not be successful with satisfactory.

• The development of the system doesn’t have to order

The steps that must be done doesn’t need to order, but it can be done together. For example, in the development of the system, design the output stage should be done before the design file. This does not mean that all output must be designed before they can make a new design file. But can be done simultaneously, the output during the design process is still conducted, the results of the output that has been completed can be used to design files.

• Don’t be afraid to cancel the project

For the cases a, where a project had to be stopped or canceled because it is not feasible anymore, it should be done with the firm.

• Documentation system

This documentation should be made at the time of the process of developing the system itself is still in the process. Because of this documentation can be produced from the work of each step in the development system. Documentation created and collected during the process of system development can be used for communication between the system analyst with the system and can be used to encourage the involvement of the system.

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

System development approach

• A structured approach versus classical approach (seen from the methodology used)
• Piecemeal approach versus system approach (seen from the target to be achieved)
• The bottom-up approach versus top-down approach (seen from how to determine the needs of the system)
• Total-system approach versus modular approach (seen from the way the developing)
• Great loop- approach versus evolutionary approach approach (seen from the technology that will be used)

A structured approach versus classical opponent approach

Classical approach

• Stages in SDLC-stage
• Not to include users, system analysts put more emphasis
• The problem: the development of hard, expensive treatment, the possibility of error, success is less assured, the problems in the implementation of

Structured approach

• User involvement from the beginning to determine the needs of the system
• Using tools-tools such as data flow diagrams

Piecemeal approach versus system approach

Piecemeal approach

• Emphasizing on an application or event
• Don’t override the overall target

System approach

• Viewing the system as a whole is unity
• Emphasizing the achievement of overall objectives

Bottom-up approach versus top-down approach

Bottom-up approach

• Starting from the bottom level of the operational
• It is the characteristics of classical
• Known by the term data-analysis

Top-down approach

• Starting from the top-level strategy planning
• It is the characteristics of structured
• Also known to the decision-analysis

Total-system approach versus modular approach

Total-system approach

• Develop a system simultaneously and comprehensively
• It is the characteristics of classical approach

Modular approach

• break a complex system into parts of a simple
• System to be developed on time, easy to understand and kept
• It is the characteristics of structured

Great loop- approach versus evolutionary approach approach

great-loop approach approach

• Develop a system simultaneously using the advanced technology
• At risk and spend a lot of high cost

evolutionary approach approach

• Applying advanced technology for application-specific applications
• Developed for the needs
• Save the cost and can follow the development of technology

methodology, method and algorithm

• Methodology

Is methods used in science

• method

A systematic way to grind

• algorithm

Sort-order the procedure to solve a problem

Classification of development methodology

• Functional decomposition

– Emphasizing the breakthrough system subsystem

– Example : HIPO, Stepwise refinement, iterative stepwise refinement, information hiding

• Data-oriented

– Emphasizing on the characteristics of the data processed

• Data-flow oriented: modules according to the type of data elements

• Data-structure oriented: structure of the input and output

• Prescriptive

– Usually provided by the manufacturer of the software

Tool for developing a system

• shaped graph: HIPO, SADT, Jackson’s diagram, etc.

• Tools that use the chart:

ü Activity charting : describes the activity, for example: Gant chart, flowchart, etc.

ü Layout charting: Describes the layout

ü Personal relationship charting: describes the relationship of personnel, for example: organization charts, work distribution chart

Techniques used in the development a system

• Technical project management

Technique that is used to penjadualan project, for example : CPM dan PERT

• Fack finding technique

to collect data and determine and find the facts

– interview

– Observation

• cost-benefit or cost-effectiveness analysis

• Technical meetings run

• walkthrough

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

References

http://en.wikipedia.org/wiki/Waterfall_model

http://en.wikipedia.org/wiki/Spiral_model