DEVELOPING AN INFORMATION SYSTEM
1) What is the importance of developing an information system?
System development can be interpreted to arrange a new system to replace the previous system as a whole or repair the existing system. The previous system need to be repaired because of a few things, which is:
a. Problem.
The problem in this system can be in the form of deceits that causes not wealth treasure the safe companies and truth from data is less well guaranted, errors not intentional that causes data truth not well guaranted, the operation not efficient, and not bidding the management policy that applied.
b. Organization Growth.
Organization growth here that is information need more vaster, data processing volume more increase, bew accountancy principle change. Caused by this change, so old ones system not effective again, so that must there development towards system.
2) What is the purpose or goal of developing an information system?
Purpose or goal of developing an information system
- to solving some problems
- reach for opportunity
- fulfilling given instruction
3) What are the organization’s expectations after implementing an information system?
There are the expectations of organization after executing the information system
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.
Information ( information) : The improvement of information quality which presented.
Economy ( economic) : Increase the benefit of vs decreasing cost.
Control ( operation) : The improvement of control, detecting and improve;the mistake. To detection and repairing some faults and insincerity which possible happened.
Efficiency ( efficiency) : The improvement of operating efficiency. Efficiency related with how to use resource without doing extravagance.
Services ( service) : Increase the service of system.
System development principles:
1. System that developed management.
2. System that developed big capital investment.
3. System that developed to need one who educated.
4. Work stage and duties that must be done in course of system development (System Development Life Cycle).
5. System development process must not massage.
6. Don't be afraid cancel project.
7. Documentation existence for guide in system development.
Waterfall Model
Requirement : in process requirement this is systems analysis does need collecting process from customer and or top management either from aspect area also business strategy, towards system and or desirable application.
Design : in this stage us does systems analysis process, fitur that need, need from application that be made good to also the application. Beside that, here we also begin to make design plan from system, like interfaces delegation, the data structure, the architecture, and as it.
Implementation : implementation process has been continuation from where did we begin to implementation design that made to into program codes that be read by engine language.
Verification : process verification here same like testing process towards system and or application that made. This process focus in internal logic from application that made, as certain that any line coding checking. Beside that here we also have done testing process towards possibility towards errors from system that made.
Maintenance : process maintenance here be repair process and maintenance towards system that made. Repair process here done when application and or system that made to experience error after to customer so that must necessary repair process towards system and or caused by development towards an OS so that application must be repaired again to be update.
b. Iteratif Model
Initial planning : Be beginning planning process and or beginning ideas to make a system.
Planning : Planning here be a thinking that ripe towards system that be made.
Requirement : Same like in process requirement waterfall model, here systems analysis does need collecting process from customer and or management on towards system and or desirable application.
Analysis and design : In this stage us does systems analysis process, fitur everything that need, need from application that be made good to also the application. Beside that, here we also begin to make design plan from system, like interfaces delegation, the data structure, the architecture, and as it.
Implementation : Implementation process has been continuation from where did we begin to implementation the design that made to into program codes that be read by engine language.
Deployment : Process deployment here purpose has been distribution process towards system that made, in our meaning distributes before hand system to society before do testing so that we know our system deficit.
Testing : Process testing here we have done testing towards system and or application that made. This process focus in internal logic from application that made, ascertain that any line coding checking. Beside that here we also have done testing process towards possibility towards errors from system that made.
Evaluation : Process evaluation here be repair process, maintenance and renewal towards system that made. Repair process here done when application and or system that made to experience error after to customer so that must necessary repair process towards system. Maintenance process and renewal be done caused by development towards an OS so that application must be repaired again to update. In renewal process here will return to do process planning, data collecting (requirement), analysis system and design, implementation, deployment, testing and return again to evaluation. if there development again, so this cycle be repeated again.
Spiral Model
Spiral model explanation:
1. Determine objectives
in this process us will determine what will be made system, either from also output from it system.
2. Identify and resolve risk
here we do identification process, planning and analyze risks may be happen. In identification process and planning, we must define before hand resource, time precision, and other related information project with system that we shall make. While in risk analysis process here we do analysis towards risks may be happen, between management or technical.
3. Development and test
in process development and test this is us do engineering process, construction and testing towards system that be made. In engineering process and construction, we do process coding to make a application. While in testing, we do testing process towards system or application that we have made.
4. Plan the next iteration
here we do iteration process for plan next and or evaluation in the event of request from customer in order to change towards system or application.
3) Please explain approaches of developing a system
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
· 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.
· 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.
· 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.
· 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.
4) Please explain the meaning of methodology, method and algorithm
Methodologies is the methods which is used in science
Method [is] a way of systematic to do something
Algorithm [is] procedure sequence to solve a problem
5) Please explain the three classifications of development methodology
System Development Methodology
Methodology is methods unitary, procedures, job concepts, rules and postulates that used by a science, art or discipline the other. Method is a manner, systematic technique to does a certain. System development methodology means methods, procedures, job concepts, rules and postulates that be used to will develop information system. Algorithm is sequence procedure to break a problem.
Classification based on existing methodology can classified to be three, that is:
1. Functional decomposition methodologies.
This methodology emphasizeds in solution from system into subsystems smaller, so that easier to be understood, designed and applied. Belong this methodology, that is:
HIPO (Hierarchy plus Input-Proccess-Output)
Stepwise Refinement (SR) or Iterative Stepwise Refinement (ISR)
Information-hidding
2. Data-oriented methodologies.
This methodology will emphasized in characteristics from data that be processed. This methodology can be grouped to into two class, that is:
a. Data-flow oriented methodologies.
This methodology is based in solution from system intoes modules based on data element type and module logic behaviour insides system. Belong in this methodology, that is:
SADT (Structured Analysis and Design Techniques)
Composite design
Structured System Analysis and Design (SSAD)
b. Data structure oriented methodologies.
This methodology emphasizeds structure from input and output at system. Belong this methodology, that is:
JSD (Jakson's System Development)
W/O (Winner/Orr)
3. Prescriptive methodologies.
This methodology is usually is provided by software maker factory. Belong in this methodology, that is:
- ISDOS (Information System Design and Optimization System)
- PLEXSYS
- PRIDE
- SDM/70
6) Please mention tools for developing a system
Tools for developing a system
• Get graph form: HIPO, SADT, Jackson’s diagrams, etc.
• 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
7) Please explain techniques used in developing a system
There are the technique - used technique in developing a system
A. Management technique of project for schedule of project , example : cpm and of pert
B. Technique find fact to collect and determine data / fact 1. Interview 2. Observation
C. Technique analyse expense / benefit of cost-benefit and cost-effectiveness analysis
D. Technique to do the meeting
11) Please explain the differences of being a system analyst and a programmer and also mention what are the knowledge a system analyst should posses
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
No comments:
Post a Comment