This is all about our classes in information and system design from week 3..continue from Week 1 post..
Before we start to build and develop an information system, we need to know the reasons need to be done so that the development of a system. Here are some reasons for the development of a system :
1. There is a problem that needs to be completed. This is often experienced by many organizations. For example in a telecommunications company will require a great system for dealing with information communication notes clients. The problem would be very difficult if not using the information system
2. Irregularity in the growth of the organization. This is also experienced by many organizations. For example, an organization implement a system akutansi. Of course this requires information systems to handle the changes.
3. To reach opportunities. In the organization is often required information is obtained only with implementing information systems in organizations. This valuable information that can later be used to gain opportunities in the organization.
4. Having the instructions. Sometimes the way the organization will meet the demands of the instructions the relevant authorities. For example of the new government set a minimum wage, the system required the development of existing information.
Of reasons, it can be the goal of the development system is as follows:
1. Solving problems.
2. Reach the opportunity
3. Intruction meet the given
Now let we discuss about is expected from developin system.
Measured using the throughput and response time
Improving the quality of information
Increasing the benefits vs. cost reduction
Detect and fix errors
Improvement of the system
What are the principles of developing an information system?
There are seven priciples of developing an information system :
1. System for management
2. System is a large investment
– Investigate all alternatives (minimize cost of lost opportunity)
– Investigation must be best value: cost-benefit analysis & cost-effectivenes analysis
3. Systems require educated people
There must be formal education
4. Stages of labor -> System development life cycle
5. Development of the system does not need to order
6. Do not be afraid to cancel the project
7. Documentation system
System Development Live Cycle (SDLC)
1. Requirement: At this stage we determine the needs of the system. Identify the problem, detect potential problems and to complete the goal of making system. This stage is very important because at this stage we menetukan way of making system.
2. Design: In this step, we created a design system based on the analysis of the needs we have done in the previous stage.
3. Implementation: At this stage, we try to implement the system we have pata design stage before.
4. Verification: At this stage we do verification of the system we have implemented. If all are not running and there is a design error in the system that we implemented.
5. Maintenance: This stage will continue to be used throughout the system. Because at this stage is done so that treatment can continue to run the system in accordance with the expected
Model here is almost the same as the waterfall model, only after the system been use, there will be trials of the system. Evaluation of testing done to know the weaknesses in the system, if there is an error, then the system will reset in the analysis.
This method is almost the same as the method iteratif, only in this method continues to be improvements for the development system. This is done by creating a prototype-prototype before the final version are released.
Ok , now after discuss System Development Live Cycle ..there are five approach of developing a system :
1. The classical approach vs structured approach
– Classical approach
Stages in the SDLC
Did not include users, system analysts put more emphasis
Problems: the development of hard, expensive treatment, the possibility of error, success is less assured, the problems in the implementation of
– Structured approach
Users involved from the beginning to determine the needs of the system
Using tools-tools such as data flow diagrams
2. The piece approaches vs the system approach
– The piece approach
Emphasizing on an application or event
Does not override the overall target
– System Approach
View the system as a whole is unity
Emphasis on achieving the overall target
3. Bottom-Up approach vs. top-down approach
– Bottom-Up approach (bottom-up)
Starting from the bottom level of the operational
Is a discrete approach to classical
Known by the term data-analysis
– Top-down approach (top-down)
Starting from the top-level strategy planning
Is a discrete approach to structured
Also known with the decision-analysis
4. The system-comprehensive approach vs. modular approach
– Comprehensive approach
Develop a system simultaneously and comprehensively
Is a discrete approach to classical
– Modular approach
Split the system into the complex parts of a simple
System to be developed on time, easy to understand and kept
Is a discrete approach to structured
5.The great-loop approach approach vs. evolutionary approach
– Great-loop approach
Develop a system simultaneously using the advanced technology
High-risk and spend a lot of cost
– evolutionary approach
Applying advanced technology for application-specific applications
Developed for the needs
Cost effective and can follow the development of technology
That’s so important to us to understand about step for develop a system. There are some points to note :
What is the methodology?
Methodology are methods used in science
What is the method?
Method is a systematic way to grind
What is the algorithm?
Algorithm are sequence procedures to solve a problem
Three classifications of development methodology :
1. Functional decomposition
– Emphasize breaking system subsystem
– Example: HIPO, Stepwise refinement, iterative stepwise refinement, information hiding
– Emphasizes the characteristics of the data processed
– Data-flow oriented: modules according to the type of data elements
– Data-oriented structure: the structure of input and output
Usually provided by the manufacturer of the software
Tools for developing a system :
1. Shaped graph: HIPO, SADT, Jackson’s diagram, and other
Tools that use the chart:
– Charting activity: describes the activities, for example: Gant chart, flowchart, etc.
– Layout charting: describes the layout
– Charting a personal relationship: describes the relationship of personnel, for example: organization charts, work distribution chart
Techniques used in developing a system :
– Techniques for project management -> scheduling project, for example: CPM and pert
– Techniques to gather facts and determine the data / facts
– Technical analysis of cost / benefit -> cost-benefit and cost-Effectiveness analysis
– Techniques to run a meeting
– Technical inspection
The differences of being a system analyst and a 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
System analyst duty bridge the knowledge gap that occurs between the user and system programmers
The knowledge a system analyst should posses :
– Technology, data processing, computer programming and business knowledge in general
– Quantitative methods: regression, linier programming, dsbnya
– Problem-solving skills
– Communication skills among the personnel
– Expertise builds relationships between the personnel