Minggu, 29 Maret 2009
FIRST OBSERVATION, ANALISYS REQUIREMENT
Difference difference ( gap) of between target of system and system condition in fact
Report detect the problem not really real
1.purpose to ideal
2. Lacking of resource and or attitude
3.System measurement less be accurate
4.System target purpose under developed
5.Different between idle system and temporary system
Problem Solving:
1.System description walks on.Detailed investigation needs to solve the problem. Detailed investigation use system description walks on company.
2.Getting ideal system consensus
3.Developing some alternative
4.Chosening best alternative
5.Investigation Purpose to indicate the real problem.
RECOMENDATION
A result from investigation is a recomendation which are the following:
1.Does not take any action if the problem does not exist
2.Perform system maintenance of the small problems
3.Increasing the ability or skills
4.Consider modifications to total system
5.Putting the problem to occur in the development plan system which immediately made
INVESTIGATION TACTICS
Tactics of investigation is needed for example:
1.Can find all problem
2.Knowing cause of problem appearance
3.Determining correct solution
Investigation tactics must be done so that all system element can accept offer of solution without bothering their activity.
Some Tactic Can Be Do:
1.Listening system user opinion
2. Don’t give an early fission
3.Comparing system user story about the same case
4.Observation about logical inconsistency problem
INVESTIGATION TECHNICS
Direct:
1.Questionnaire
2. Asking and reply
3. Observation
Indirect:
1.Procedure flow
2. Document studying
3. Sample
4.Tabular
CURRENT SYSTEM DESCRIPTION
Determining current system performance will struck a snag if firm have no one performance measurement default system. Too bad, tending firm doesn't update to document walking system. Hence, analyst fix document up to problem investigation system. Current system description covers explanation:
1.inputs
2.outputs
3.files
4.data elements
5.transaction volume and action document
6.data flow diagrams
ANALYSIS NEEDS
Intensive interaction step between system analyst and end user, which system development team showing they are skill to get respond and trust of user, so its get a good participation.
Four objective being reachable :
1.Explain complete system
2.Describe ideal information system
3.Bring the ideal information system to the current situation with consider about resources problem.
4.Give support to user confidence to a system development
Method
1.Asking and reply
2.Questionnaire
3. Observation
4.Analysis procedure
5.Document observation
Resources problem
1.Time
2.Money
3.Skill
4.Technology
5.External factor
Analysis needs document
1.Analysis brief : relation with end user, process monitoring, data collect problem
2.User needs : truly needs, report needs, training needs and new system effect.
3.System problem : explain time and cost problem, skill, technology and external factor.
4.Documents, data collect instrument, statistic consensus, physical and logical data flow, starting data element on data dictionary.
GENERATING SYSTEMS ALTERNATIVES
How to current system condition approaching with condition of system which ideal?
1.Making alternative to solve information system problem
2.That best alternative is applied one expedient
Strategy Selection
1.distributed versus centralized processing
2.Changing information decision from centralized processing's data goes to decentralized end user responsibility center
3.Integrated versus dispersed is database
4.System designer shall regard data any kind ingoing in base's data and one turns in at File
5.Surround Strategy of System Development
6.Environmentally surrounding strategy is of important in term confiscation because information system of other firm may in contrast to corporate currently.
Operational scheme Selection
Scheme selection can be agglomerated into
Input
1.Online Vs Off Line Data Entry
2.Keyed Vs Machine Readable Data Entry
3.Centralized Vs Decentralized Data Entry
Processing
1.Batch Vs Realtime record update
2.Sequential Vs Direct Access to records
3.Single Vs Multiple User update of records
Output
1.Traditional Vs Turn Around Documents
2. Structured Vs Inquiry based reports
SELECTING THE PROPER SYSTEM
The tactics compare : System compared to pursuant to expense and advantage relatively;
There is 3 way of system A told by more pre-eminent with the other system if:
1.A have the lower expense from B and advantage both of equal
2.A have the lower expense from B and A yield the advantage which is more than B
3.A and B have the expense of equal but advantage yielded by A more amount.
Some Method of Komparasi System
1.Break Even point Analyisis
2.Payback Period
3.Discounted Payback period
4.Internal Rate Of Return
Categorize The Expense
1.Hardware
2.Software
3.People
4.Suppliers
5.Teleccommunications
6.Physical Sites
Expense of information system can just be happened once and earn is also happened chronically.
1.Expense of just information system that happened once that is ontime cost and development cost that happened system development moment.
2.Expense of information system that happened continually among other things is reccuring cost and also operational cost of where this expense is happened by the moment of information system operate every day.
Factor Qualitative instructing good information system performance among other things
1.Lessening mistake storey;level
2.Lessening time to improve;repair the mistake
3.Lessening time listen carefully from workstation alternative
4.Quickening ready time of information
5.Improving system security
6.Multiply to update the active source record
7.Improving wearer satisfaction
Factor of Company Strategy
1.Consumer Satisfaction
2.Mount the sale mount the
3.Komitmen of Consumer and vendor
4.product marketing Information
PRESENTING SYSTEM STUDY
1.Conducting presentation in a word
2.Lessening technique clarification in detail
3.Presenting clearly by means of assist visual
4.If using model use the assistive appliance for example laptop so that more informative
5.Emphasizing advantage from proposal of information system with a few existing alternative according to natural by condition of company
DECISION CONTINUE OR DO NOT
1.If company set mind on to develop the system hence information department will conduct the process hereinafter that is Process The Desain System
2.If on the contrary hence System Development Life Cycle ( SDLC) will be discontinued
3.Frequently will be found by problem with the study system and and usually top management will ask conducting of reworking to study system
4.Model will explain the some part of step repeated and sometime information department will make decision to repeat the step of before explaining study system
5.With the alternative, decision to repeat a not to speak of or previous step SDLC of Go – No – Go Decision.
Referensi:Pengamatan Awal, Kebutuhan Analisis; Ngurah Agus Sanjaya ER, S.KOM, M.KOM
Sabtu, 07 Maret 2009
SYSTEM DEVELOPMENT
SYSTEM DEVELOPMENT
Answer question :
[Part-2] Information Systems Analysis and Design :
1. The purpose t of system development public :
The important.of systems development is compiling a new system to replace system old ones as a whole or improve;repair system which have there. The system old ones require to improve because, existence of problems - problems that appear in system old ones. Problems of arising out such of :
- Annoyance in growth’s system of organization
- The example of annoyance in growth’s system of organization, insincerity.and mistake which intended, its efficiency [of] operation [do] not and [do] not obey of policy of management
- Growth of organization.
- For reach the opportunitys ( opportunities)
- existence of instructions ( directives)
2. Purpose or goal of developing an information system
- to solving some problems
- reach for opportunity
- fulfilling given instruction
3. The organization’s expectations after implementing an information system
A. Performance ( performance)
Measured to use and throughput of response time. The improvement of performance in a new system make the system will be effective. Performance can be measurement from throughput and response time where throughput is amount of work of which can done certain in a moment and response time is time mean which delay between two transactions.
B. Information ( information)
The improvement of information quality which presented.
C. Economy ( economic)
Increase the benefit of vs decreasing cost.
D. Control ( operation)
The improvement of control, detecting and improve;the mistake. To detection and repairing some faults and insincerity which possible happened.
E. Efficiency ( efficiency)
The improvement of operating efficiency. Efficiency related with how to use resource without doing extravagance.
F. Services ( service)
Increase the service of system.
4. The principles of developing an information system :
o System for the management
o System is big investment
§ Investigation of all alternative ( minimizing missing cost opportunity)
§ Best investigation have to be valuable : analysis cost-benefit & analysis cost-effectiveness
o System need educated people
§ not education have to be formal
o Activity stepà System Development cycle life
o System development [do] not have to massage
o Don’t fear to cancel project
o System documentation
5. Three cycle live development of system are
a. Model of waterfall explanation :
- Requirement
- Design
- Implementation
- Verification
- Maintenance
b. Model iteratif explanation :
- Initial planning
- Planning,
- Requirement
- Analysis and design
- Implementation
- Deployment
- Testing
- Evaluation
c. Model spiral explanation :
- Determine objectives
- Identify and resolve risk
- Development and test
- Plan the next iteration
6. Approaches of developing a system
There are several approach to developing a system, that is:
Classic approach vs. structured approach :
Classic approach is approach inside of developing a system that follow stages at system life cycle without supplied with tools and techniques.
Troubleshoots which can arise from this approach, such as:
a) Difficult development.
Classic approach less give tools and techniques insides develop system and finally software development process becoming not directional and difficult to be done by programmer.
b) Treatment cost or system maintenance will be more expensive.
The expensive treatment cost at classic approach caused system documentation that developed less complete and less structured.
c) Possibility of big error.
This approach doesn't prepare to manner systems analysis to do system testing, so that system errors possibility will be bigger.
d) System achievement less well guaranteed.
Because classic approach less involve system user in system development, so system user needs are less matching with the one which desirable and as finally system that applied less success.
e) Applying internal issue.
User will be startled and unaccustomed with new system suddenly introduced.
Structured approach equipped with tools and techniques that wanted in system development, so that the end result from system which developed be got system the structure will be defined well and clear. In this approach, consumer involve from early to determine requirement of system and using tools like data of flow diagram
o Piecemeal approach vs. system approach
Piecemeal approach is system approach development that emphasized at one particular activity or certain application. This approach don't heed overall target.
System approach pays information system as integration unitary to each activity or the application. This approach also emphasized in overall goal achievement from organization, not only in that information target.
o Approach of bottom-up vs. approach of up-down
Bottom-Up Approach is begin from level under organization, that is from formulation requirements to handle transaction and climb level on with formulate information need based on transaction. Bottom-up approach is used in systems analysis steps, because of the pressure is data that be cultivated before, information that be produced will follow the data. Up-Down Approach on the contrary with bottom-up approach, this approach is begin from level up organization, that is begun with define target and organization policy. Step furthermore from this approach information need analysis. After information is determined, so process goes to transaction processing, that is determination output, input, data base, operating procedure and control. This approach be feature from structured approach. Top-down approach when used in systems analysis stage called also with term decision analysis, because that be pressure information that wanted for decision making by management beforehand, then data necessary cultivated to defined to follow information that wanted.
o Total-system approach vs. modular approach
Total-system approach to be approach develops system together according to comprehensive. This approach less synchronized for complex system, because will be difficult be developed. This approach be feature classic approaches.
Modular Approach tries to divide complex system to simple some part, so that system easier will be understood and developed. Furthermore consequence system can be developed of time that planned, easy understood by system user and easy to maintain. This approach be feature structured approaches.
o great-loop approach vs. evolutionary approach
Great-loop approach applies change comprehensive according to together use sophisticated technology. This change contains many risks, because computer technology so great-loop. This approach also too expensive, because need investment at the same moment for all technology that used and difficult to developed because too complex. Evolutionary approach apply sophisticated technology just for applications that need that moment and then be developed for periods next based on technology development. This approach causes investment not too expensive and can follow fast technology development.
7. The meaning of methodology, method and algorithm :
o What is methodology?
Method those are utilized in scholarship
o What is method?
Someway systematic to work something
o What is algorithm?
Medley procedural to solves a problems
8. The classifications of development methodology
There are three classifications of developing a system, such as:
• Functional decomposition
Functional decomposition is emphasizing system resolving becomes subsystem. Examples of this classification are HIPO, Stepwise refinement, iterative stepwise refinement and information hiding.
• Data-oriented
Data-oriented is emphasizing on processed data characteristic.
• Flow oriented data: types appropriate modules data elements
• Structure oriented data: input structure and output
• Prescriptive
Usually been provided by software maker factory.
9. Tools for developing a system :
a) Get graph form: HIPO, SADT, Jackson’s diagrams, etc.
b) Tool that utilizes to design:
§ Activity charting: figuring activity, example: chart's substituting, flowchart, etc.
§ Layout charting: figuring layout
§ Personal relationship charting: figuring person relationship, example: organization chart, working distribution chart
10. Technique In System Development
Techniques that can be used in development system, that is:
- Project management technique, that is CPM (Critical Path Method) and pert (program evaluation and review technique). This technique is used for project scheduling.
- 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
- Cost-effectiveness analysis or cost benefit analysis
- Technique to run meeting
- Technique inspection/walkthrough.
- The differences of being a system analyst and a programmer and the knowledge a system analyst should posses :
System analyst studying problems and determine system user requirements to identify resolving.
Programmer writing program code bases engineering that made by analyst
- System analyst on call bridges distinctive happening science among system user and Data processing technology, computer and mathematics
- Science carries on business in common
- Quantitative method: regression, programming linear, etc. it
- Trouble-shooting membership
- Communication membership among person
Membership builds relationship among person programmer
By :
Febri Saputra