1. The important of develop an information system is to mean to compile an system which to replace system old ones as a whole or improve repair system which have there is.
2. Target of in developing an information system
v Existence of problemss of arising out system old ones like :
a. Solvingproblems
Solvingprogram in system old ones cause to operate disagree with which expected. This solvingprogram can in the form of :
· Insinceritys intended causing is not peaceful company estae him and truth of data become less well guaranted
· Mistakes which not be intended able to cause the truth of from data less well guaranted.
· Inefficient of operation
· Not adhere of management wisdom which have been specified.
b. Growth of organization
Growth of organization among others requirement of information which progressively wide of, data-processing volume progressively mount, change of new accountancy principle. Caused by this change cause system old ones is not effective again.
c. To reach for opportunitys
Information technology require to be used ready to increase information so that can support in course of decision making. In a state of market compete, speed of time efficiency or information very determining success or failure of strategy which have been compiled. If the competitor can exploit company it is not, hence opportunity will fall competitor hand.
d. Existence of intruksi-intruksi
Compilation of new system earn also happened caused by instructions from the top of head and or organizational from outside like government.
3. Expectation after applying a information system is:
a. Performance, make-up of to new system job so that become more effective. Performance can be measured from and throughput of response time
b. Information, make-up of to quality of presented information
c. Economy, make-up of to advantage or benefit or decreasing cost that happened
d. Control, make-up of to operation to detect and improve;repair mistake and also insincerity which and will happened
e. Efficiency, make-up of to operation efficiency. Efficiency differ from ekonomis,efisiensi can be measured from it is divided with its input
f. Services, make-up of to service given by system
4. Principle in developing a information system is :
1. Developed system is to menajemen
After system have been developed, system have to earn to support requirement needed by management .
2. System the developed is big capital invesment
Developed information system require big capital used of recent technology, hence
each every capital infestasi have to consider two matter following :
a. All existing alternative have to the investigation of
If disregarded existing alternative and have come too far unintentionally have inculcate dama to a project of certain invesment, hence investor will lose time to inculcate its fund to other invesment. Ekonom mention it with opportunity cost term. Therefore from some existing invesment alternatip have to the investigation of to determine most beneficial or best alternative
a. Investigation of best have to be valuable
Not yet of course best alternatip represent beneficial invesment. This invesment can be told to profit if valuable with the meaning result or benefit return him bigger than expense to obtaining it
3. Developed system need one who is educated
Human being represent primary factor which it is success menetukan do not asystem, good in course of its development, its applying, and also in course of its operation. System analyst have to have education to problem of which is faced it. Because later this system analyst will communicate with and management of programer, and so it is with user of system have to represent one who educated about this system
4. Step work and duties which must be done in course of development of system
Before process development of sietem done, hence have to be made beforehand job schedule showing job steps to be done, so that process system development can be done and finish successfully as according to planned budget and time
5. Process development of system do not have to massage
Done stages steps do not have to massage, but can be done by together
6. Don fear to cancel project
Decision to continue a project or canceling it is true have to evaluate by carefully and is coherent. Doubt to continue to to continue the project of which improper again because have permeated of fund into this project will only throw away useless fund
7. documentation there must be for guidance in development of system
documentation ought to be made by when process of system development of itself still in course of, because this documentation can be yielded from result of job every step in system development
5. Model of Waterfall
Requirements give service, definition, and system target determining to through consultancy with system user. Last go to design which is process scheme of system divide conditions in hardware system and software. Determining system architecture as a whole. Hereinafter Implementation which design software realized as with refer toing program unit or program entangling verification that eachevery unit have fulfilled its specification.Afterwards to verification represent program unit or integrated individual program and tested as complete system to guarantee that conditions of system have been fulfilled. After examination of system, software sent to User.Last go to maintenance, usually represent cycle phase which at longest ( although do not ought to). system of Diinstall. Maintenance include cover correction and various error which do not be found by at previous phases, repair of system unit implementation and development of service of system.
Model of Iterasi
Initial planning make planning program . Requirements collecting requirement completely later then is later;then analysed and defined by requirement which must fulfill by program to be woke up. This phase have to be done completely to be able to yield complete desain. Analysis & design in doing after requirement have been collected completely. Mendesain program Implementation translated into codes by using Ianguage of pemrograman which have been determined. direct woke up program tested by either through unit. Testing federating of program units is later then tested as a whole ( testing system) so the last with evaluation which evaluating.
Model of Spiral
Determine determine the intention of determined phase. Strategy alternative have been prepared pursuant to risks knew, and have been planned. Going to Identify risks resolve and each;every risk analysed in detail at this sector, for example making prototype to know to incompatibility of requirement. Going to Development test and , after risk evaluation, hence system development model selected, for example if risk of user dominant interface, hence making User Interface prototype. Going to Plan iteration next the of[is Project of evaluated or ditinjau-ulang and set mind on to continue to phase of loop hereinafter or do not. If continuing to next phase of plan for loop hereinafter.
6. Approach in approach a system
1. Classic approach of opponent approach of structure
Classic approach emphasize that development of system will succeed if following phase in cycle life systems. Approach of structure try to provide to analysis of system additional of techniques and appliances for the development of system beside remain to follow idea of cycle life systems
2. Approach of rasher fight against approach of system
Approach Piecemeal, selected application or activity, to be developed by regardless of its position in information system or regardless of target of[is overall of organization. Approach Systems paying attention information system as one unity integrated to the each activity or its application which emphasize at goal achievement of is overall of from organization
3. Approach under going up approach opponent to the going down
Approach Bottom-up started from formulation of requirements to handle transaction and climb level to the by formulating requirement of information pursuant to transaction. Approach Top-down started by identifying organization wisdom and target hereinafter to analyse requirement of information, hence process go down to transaction process
4. modular Approach the against fight Total-system of approach
Approach Total-system represent approach developing system at a time by totally is. Modular of approach try to solve complicated system become some part so that system will be more is easy to comprehended and developed
5. Approach of jumping movement far fight against approach expand
Loop approach Great apply change totally at a time use sophisticated technology. Approach Evolutionary cause invesment do not too costly and can keep abreast of technology which quickly, so that used technology do not quickly become worn outly
7. Methodologies is unitys of methods, procedures, work concepts, postulates and orders used by a science, artistic or the other discipline.
Algorithm is procedure sequences for this trouble-shooting.
Method is a way of systematic technique to do something
8. Explaining the three classification of development methodologies
1. Decomposition methodologies Functional
This methodologies emphasize at resolving of system into smaller subsistem-subsistem, so that will be more easy to to be comprehended, to be designed and applied. Which included in this methodologies group:
· Plus HIPO(hierarchy of input-process-output)
· Refinement(Sr Stepwise) or revinement(ISR stepwise iterative)
· Information-Hiding
2. Data of Oriented methodologies
This methodologies emphasize at characteristic of data to be processed. This methodologies is grouped into two class that is data of flow methodologies oriented data of structure methodologies oriented
3. Methodologies Presciptive
- ISDOS
Usefulness of ISDOS is to automatization process development of information system. ISDOS have two component that is PSL ( a Ianguage to note requirement of user in the form of machine-readable) and PSA ( software package which loo like with data dictionary used to check included data which is kept and which is analysed to be to be yielded as report output )
- PLEXSYS
Usefulness of PLEXSYS is to do transformasi a[n high level computer Ianguage statemen to a executable to hardware kofigurasi which wanted.
- PRIDE
Representing a[n better inwrought software for analyst / designed by structure system, data menajemenn, menajemen of is project of and documentation.
- SDM / 70
Representing a[n software contain with method corps, estimation, documentasi and guide of administration of gunba assist user to develop and take care of effective system.
- SPECTRUM
This Software have some version for is different, a kind of SPECTRUM-1 ( for the life of koncensional cycle), SPECTRUM-2 ( for the system of management of[is project of structure) and SPECTRUM-3(UNTUKON-LINE estimator interactive)
- SRES and of SREM
SRES requirement of user expressed by in RSL ( language statement requirement). Definition of RSL later then can be analysed by using REVS ( system validation and engineering requirement). Methodologies constitutoing software in mentioning SREM ( merthodologi engineering requirement software).
9. Mentioning tool for develop a graph system
a. Diagram HIPO, used as by methodologies of HIPO and the other methodologies
b. data of Flow diagram, used by in methodologies of structured design and analylis systems
c. Chat Structured, used by in methodologies of systems design and analysis
d. Diagram SADT, used by in methodologies of SADT
e. Warnier / diagram orr, used by in methodologies of Warnier / orr
f. Diagram Jakson's, used by in methodologies of Jackson development system
Appliances development of system which in form of schema
1. charting activity
a. flowchart systems
b. program of flowchart: program of logic flowchart, program computer detailed of flowchart
c. flowchart paperwork
d. database of relationship flowchart
e. flowchart process
f. chart gantt
2. charting layout
3. personal of chartin relationship
a. chart distribution working
b. chart organization
10. Explaining technique used by in develop a system
a. technique of menajemen the project of , that is CPM ( method path critical ) and PERT ( program of evaluation technique review and). This technique is used by for schedulling project
b. techniques finding fact, that is technique able to be used to collect data and find facts in activity study existing system. Between him of interview, observation, questionnaires, sampling
c. analyst technique of is expense of or benefit
d. technique to run meeting
e. inspection technique / walkthrough
11. Analyst analysis systems who one is Systems ( wearer system of requirement the determine and out arising of problem learning) occasion the to have which resolving the identify to.
Programmer of Is program code the write who one of to analyst system a by made been have which develop build device to pursuant application certain a
1. Knowledge and membership about data-processing technique of technology of computer and pemrograman of computer
Technical membership which must have is the including membership in usage of technique and appliance
Technical knowledge which must have to cover knowledge about is hardware, data communications technology, computer Ianguage, operating system, software package and utilities
2. Knowledge about business in general
Knowledge about this business cover financial accounting, cost accounting, accounting management, system operation of management, marketing, production, and other aspects.
3.Pengetahuan about quantitative method
In developing application models, system analyst using many quantitative method
4.Keahlian pemechan of problem
System analyst have to have ability to put down problems, breaking problem, analysing and later;then stringing up it become a[n system.
5.Keahlian communications between personnel
Analyst have to have membership in communicating in verbally and also in writing
6. Membership construct relation between personnel
Analyst have to have membership in constructing relation between other personnel of will make its work become effectively.
Refference:
A Ziya Aktas, Structured Analysis & Design of Informations System. (NJ: Prentice-Hall,1987),
chapter 2-4,3-16.
Chris Gano dan Trish Sarson, Structured Systems Analysis: Tools and Techniques,
(NJ: Prentice Hall, 1979), chapter 1
Pressman, Roger.S. "Software Engineering : A Practioner's Approach." 4th . McGrawHill. 1997