o CONCEPT OF INVESTIGATION SYSTEM
There are some point about Investigation System Concept, which the following:
1. Discrepancy between the objective of system and the real condition of system
2. Problem detection report is not real, because:
the objective is too ideal
lack of attitude and resources
system measuring is not accurate
the objective of system which have to be left behind
difference between the idle system and the temporary system
3. The Problem solving
investigation to the system which is running
getting the ideal system consensus
choose the best alternative
4. The objective of investigation have to show the problem which in fact is happened
o CONSTRAINTS ON INVENTIGATION SYSTEM :
When we doing the investigation, there are several constraints that are appear, such as:
1. Time
2. Cost
3. Knowledge
4. Politic
5. Involved
o RECOMMENDATION
The investigation results are a recommendation that include these following:
1. Never take any action if there is no problem was found
2. System maintenance some small problems
3. Increase ability or user ability
4. Totally consider to system modification
5. Put problem into the development system plan
o TACTICS OF INVESTIGATION
1. Listen the suggestion from system agent
2. Don't give the resolving early to problem
3. Compare stories.
4. Look for reluctant responses.
5. Avoid politics.
o INVESTIGATION TECHNIQUE
Directly:
1. The questionnaire
2. Monitoring
3. Observations
Not directly:
1. Flow of procedure
2. Reviewing documents
3. Sample
4. Tabular
o SYSTEM DESCRIPTION AT THE MOMENT
1. Input
2. Output
3. File
4. Data element
5. Transaction volume and action document
6. Data flow diagram
o ANALYSIS REQUIREMENT
Intensive interactions step between systems analyze and end user
where the team development system show their skill to get respons and user trust until achieve good participation.
There are 4 goal wishes to achieve:
1. Explain the system completely
2. Describe the ideal information system
3. Bring the ideal information system at moment with observe the resource constraint
4. Give push to user conviction into development system
Method:
1. Question and Answer
2. Questioner
3. Observation
4. Current procedure
5. Document monitoring
6. Resource problem
7. Time
8. Cost
9. Skill
10. Technology
11. External factor
o Document analysis requirement
1. Analysis guide: relationship with the end user, process monitoring, problems in data gathering.
2. User requirement: real needs, report needs, exercise needs, and new system influence.
3. System problem: explain time and cost constraint, skill, technology and external factor.
4. Document such as data gathering instrument, statistic consensus, data flow according to physic and logical, first data element in data dictionary.
o GENERATING SYSTEMS ALTERNATIVES
1. create alternative to solve the information system problem
2. Applying best alternative wisely.
o OPTIONS STRATEGIES
1. Distributed versus centralized processing
Changes in information decision-making from the centralized data processing to the decentralized end user responsibility center
2. Integrated versus dispersed database
System designer must consider the data which are entered in the database and into the file
3. 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.
o TACTIC OPTION
Operational planning selection
Planner selection is able categorize into:
1. Input
•Online Vs Off Line Data Entry
•Keyed Vs Machine Readable Data Entry
•Centralized Vs Decentralized Data Entry
2. Processing
•Batch Vs Real-time record update
•Sequential Vs Direct Access to records
•Single Vs Multiple User update of records
3. Output
•Traditional Vs Turn Around Documents
•Structured Vs Inquiry based reports
o SELECTING THE PROPER SYSTEM
1. Comparing tactics: System comparison based on the costs and benefits relatively; There are 3 ways a system is superior to the other, if:
- A's cost is lower than B and both are the same benefits.
- A's cost is lower than B and A yield more advantage than B.
- A and B have the same but the A's cost advantage more than B.
2. Some methods of comparison system
- Break Even point Analyisis
- Payback Period
- Discounted PayBack period
- Internal Rate of Return
3. Category Cost
- Hardware
- Software
- People
- Suppliers
- Teleccommunications
- Physical sites
4. Fee Details
Comparing the cost of information systems through the life of the system, analysis is calculating the cost changes for the future and there are 3 models of cost of information system, namely Linear, and exponentially Step Function.
5. Cost of information system can occur only once and can also occur continously.
- The cost of information systems that occur only once is ontime cost and development cost that occur during the development of the system.
- The cost of information systems that occur on a continual basis are reccuring cost and operational cost where the cost of this is happened when the information system operates every day.
o INFORMATION SYSTEM FACTORS
Qualitative factors that lead the performance of a good information system are:
Reduce errors
1. Reduce the time to fix errors
2. Reducing the response time from the alternative workstation
3. Accelerating the provision of information
4. Increase the security system
5. Have active update source record
6. Increase user satisfaction
o CORPORATE STRATEGY FACTORS
1. Customer satisfaction
2. Level sales increased
3. Commitment of consumers and vendors
4. Information of marketing products
o PRESENTING LEARNING OF SYSTEM
1. Conduct a brief presentation
2. Reduce technical explanation in detail
3. Presenting clearly with visual aids
4. If using a model using a tool such as a laptop so that more informative
5. Emphasize the benefits of the proposed information system with some alternative that is appropriate conditions experienced by the company.
o CONTINUING THE DECISION OR NOT
1. If the company decided to develop the system, the information department will do next, namely the System Design Process.
2. If the other way then the System Development Life Cycle (SDLC) will be terminated.
3. Often a problem will be found with the study system and then usually top management will ask for the re-employment the study system.
4. 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.
5. With the alternative, the decision to repeat a previous stage SDLC or not is called Go-No-Go Decision.
Sunday, March 29, 2009
Friday, March 13, 2009
third quiz
The Importance of System Development
Problem – an undesirable situation that prevents the organization from fully achieving its purpose, goals, and/or objectives
Opportunities
Increase the equipping of information until the information can used to make a decision. The opportunities are like: market opportunity, costumer services.
Directive - a new requirement that is imposed by management, government, or some
external influence.
The Purpose of Developing an Information System
After developing new system, expected improvement in new system. This improvement relate to PIECES, that is:
• Performance, improvement of new system performance so that more efficient. Performance can be measured from throughput and response time. Throughput is the amount of work which can be done certain in a moment. Response Time is average time which delays among two work added with response time to answer the work.
• Information, improvement of quality of presented information.
• Economic, improvement of advantage or benefit.
• Control, improvement of controlling for detecting and repairing some mistake and also insincerity.
• Efficiency, improvement of operating efficiency.
• Service, improvement of service given by system.
The principles of developing an information system
1. System is developing for management
2. System is the great investment
3. System need educated person
4. System development life cycle
5. System development process is must not in series
6. Don’t be afraid to canceled the project
7. System Documentation
System development life cycle• life cycle model waterfall a method system the working gradually, in every stage can not return previous step. The step composition is requirements, design, implementation, verification, maintenance. With waterfall method, if step be verification we can’t previous to step design.
• life cycle with method itratif, by using this method our first does with initial planning, then requirement, analysis and design, then implementation, deployment, besides deployment we also do testing, then continued with evaluation. if there deficit or error in system, we can do new planning. this be difference between method waterfall with itratif. itratif can do change if there error in system.
• from life cycle spiral model, first step at does in spiral method concept of requirement that present in stage development, then concept of operation this present in stage plan, stage requirement plan that present in stage determine, risk analysis this present in stage identfy and resolve risk, get a temporary result then that is continued with stage venfication and validation, then development plan, risk analysis, produce a prototype 2, then at continue with venfication and validation, then at continue with test plan, continued again with risk analysis and produce oprational prototype, continued with detailed design, code, integration, test, implementation, and last is done release from system made.
approaches of developing a system
• will approach classic opponent will approach structured will approach this will emphasized that system development success when follow stage at system life cycle.
- pendekatan classic approach in system development that follow stages at system life cycle without supplied with tools and techniques memadai.
- pendekatan structured approach this that begun from beginning year 1970 called with approach structured. approach structured equiped with tools and techniques that wanted in system development so that end result from system that developed be got system so that end result from system the structure will be be defined well and clear.
• approach pieces opponent approaches system.
approach pieces be to approach system development that emphasized at one particular activity or certain application. approach system that pay attention information system as one integration unitary to each activity or the application.
• approach system comprehensive opponent approaches
approach sistem-menyeluruh be to approach menyang system together according to comprehensive. will approach this less synchronized for system complex because difficult to be developed. this be to approach classic approach modulate try broken complex system become some part or simple module, so that system easier will be understood and developed.
• approach opponent far jump approaches to bloom.
approach to jump -jauh apply change according to together use sophisticated technology. this change is many contains risk, because computer technology so fast bloom and to year coming be worn out. approach this too expensive, because need investment at the same moment. approach to bloom to apply sophisticated technology just for applications that need at that moment and then be developed for periods next will follow the need as according to existing technology development
meaning of methodology, method and algorithm
• methodology is unitary from methods, procedures, job concepts, rules that used by a science, art, or discipline the other
• method is a steps to in methodology
• algorithm is sequence procedure to break problem.
three classifications of development methodology
• functional decomposition methodologies
this methodology constitute in solution from system into sub system smaller. belong into group methodologies this:
- HIPO (hierarchy plus-process-output)
- Stepwise refinement (SR) or iterative stepwise refinement(ISR)
- Information-hiding
• Data oriented methodologies
- Data flow methodologies
this methodology is in general is based in solution from system intoes modules based on from type element data and module logic behaviour in system
- Data structure oriented methodologies
this methodology emphasizeds structure from input and output at system. mask in this methodology: jsd (jakson's systems development) and w/o(warnier/orr)
tools for developing a system
• system development tool:
HIPO diagram, used in metodelogi HIPO
Data flow diagram, used in system analysis and design S
Structured chart, used at method wanier/orr
Jakson's diagram, used at methodology jakson's system development
Techniques used in developing a system
techniques that can be used :
• technique management project, that is CPM(critical part method) and PERT (program evaluation and review technique). This technique used in project scheduling.
• Fact finding techniques, that is technique that can be used to gather fact and find data in activity study existing activity.
• technique analysis cost/benefit (cost-effectiveness analisys or cost-benefit analysis)
• technique to run meeting
• technique inspection/walkthrough
system analyst and a programmer
• system analysis one who analysis system (study that problems and determine system user needs) identify solution that have occasion
• a programming one who write program codes into computer system. where is code at write by virtue of analysis from a system analysis.
mention what are the knowledge a system analyst should posses
• knowledge and skill about technique processing data
• knowledge about business in general
• knowledge about quantitative method
• trouble-shooting skill
• skill in communicate with staff
• skill in build connection with staff
Problem – an undesirable situation that prevents the organization from fully achieving its purpose, goals, and/or objectives
Opportunities
Increase the equipping of information until the information can used to make a decision. The opportunities are like: market opportunity, costumer services.
Directive - a new requirement that is imposed by management, government, or some
external influence.
The Purpose of Developing an Information System
After developing new system, expected improvement in new system. This improvement relate to PIECES, that is:
• Performance, improvement of new system performance so that more efficient. Performance can be measured from throughput and response time. Throughput is the amount of work which can be done certain in a moment. Response Time is average time which delays among two work added with response time to answer the work.
• Information, improvement of quality of presented information.
• Economic, improvement of advantage or benefit.
• Control, improvement of controlling for detecting and repairing some mistake and also insincerity.
• Efficiency, improvement of operating efficiency.
• Service, improvement of service given by system.
The principles of developing an information system
1. System is developing for management
2. System is the great investment
3. System need educated person
4. System development life cycle
5. System development process is must not in series
6. Don’t be afraid to canceled the project
7. System Documentation
System development life cycle• life cycle model waterfall a method system the working gradually, in every stage can not return previous step. The step composition is requirements, design, implementation, verification, maintenance. With waterfall method, if step be verification we can’t previous to step design.
• life cycle with method itratif, by using this method our first does with initial planning, then requirement, analysis and design, then implementation, deployment, besides deployment we also do testing, then continued with evaluation. if there deficit or error in system, we can do new planning. this be difference between method waterfall with itratif. itratif can do change if there error in system.
• from life cycle spiral model, first step at does in spiral method concept of requirement that present in stage development, then concept of operation this present in stage plan, stage requirement plan that present in stage determine, risk analysis this present in stage identfy and resolve risk, get a temporary result then that is continued with stage venfication and validation, then development plan, risk analysis, produce a prototype 2, then at continue with venfication and validation, then at continue with test plan, continued again with risk analysis and produce oprational prototype, continued with detailed design, code, integration, test, implementation, and last is done release from system made.
approaches of developing a system
• will approach classic opponent will approach structured will approach this will emphasized that system development success when follow stage at system life cycle.
- pendekatan classic approach in system development that follow stages at system life cycle without supplied with tools and techniques memadai.
- pendekatan structured approach this that begun from beginning year 1970 called with approach structured. approach structured equiped with tools and techniques that wanted in system development so that end result from system that developed be got system so that end result from system the structure will be be defined well and clear.
• approach pieces opponent approaches system.
approach pieces be to approach system development that emphasized at one particular activity or certain application. approach system that pay attention information system as one integration unitary to each activity or the application.
• approach system comprehensive opponent approaches
approach sistem-menyeluruh be to approach menyang system together according to comprehensive. will approach this less synchronized for system complex because difficult to be developed. this be to approach classic approach modulate try broken complex system become some part or simple module, so that system easier will be understood and developed.
• approach opponent far jump approaches to bloom.
approach to jump -jauh apply change according to together use sophisticated technology. this change is many contains risk, because computer technology so fast bloom and to year coming be worn out. approach this too expensive, because need investment at the same moment. approach to bloom to apply sophisticated technology just for applications that need at that moment and then be developed for periods next will follow the need as according to existing technology development
meaning of methodology, method and algorithm
• methodology is unitary from methods, procedures, job concepts, rules that used by a science, art, or discipline the other
• method is a steps to in methodology
• algorithm is sequence procedure to break problem.
three classifications of development methodology
• functional decomposition methodologies
this methodology constitute in solution from system into sub system smaller. belong into group methodologies this:
- HIPO (hierarchy plus-process-output)
- Stepwise refinement (SR) or iterative stepwise refinement(ISR)
- Information-hiding
• Data oriented methodologies
- Data flow methodologies
this methodology is in general is based in solution from system intoes modules based on from type element data and module logic behaviour in system
- Data structure oriented methodologies
this methodology emphasizeds structure from input and output at system. mask in this methodology: jsd (jakson's systems development) and w/o(warnier/orr)
tools for developing a system
• system development tool:
HIPO diagram, used in metodelogi HIPO
Data flow diagram, used in system analysis and design S
Structured chart, used at method wanier/orr
Jakson's diagram, used at methodology jakson's system development
Techniques used in developing a system
techniques that can be used :
• technique management project, that is CPM(critical part method) and PERT (program evaluation and review technique). This technique used in project scheduling.
• Fact finding techniques, that is technique that can be used to gather fact and find data in activity study existing activity.
• technique analysis cost/benefit (cost-effectiveness analisys or cost-benefit analysis)
• technique to run meeting
• technique inspection/walkthrough
system analyst and a programmer
• system analysis one who analysis system (study that problems and determine system user needs) identify solution that have occasion
• a programming one who write program codes into computer system. where is code at write by virtue of analysis from a system analysis.
mention what are the knowledge a system analyst should posses
• knowledge and skill about technique processing data
• knowledge about business in general
• knowledge about quantitative method
• trouble-shooting skill
• skill in communicate with staff
• skill in build connection with staff
Subscribe to:
Posts (Atom)