Systems and Computer Organization
| Input | - | Output | - | Process |
|
| algorithm |
Algorithm: The logical order of decision-making for solving the problem (Munir, 1988)
| Input | - | Output | - | Process |
|
| algorithm |
Algorithm: The logical order of decision-making for solving the problem (Munir, 1988)
History of Computing
- Programming paradigm
- Programming Terseruktur
- Object-oriented programming
- In the 1960s:
- simple application
- do not use a particular motode (creativity)
- Done alone (planning, analysis, design, implementation, testing)
- Program complex (many GO TO)
- The 1970s:
- Using a structured design method (Al-Constantie and Ed Yourdon)
- Structured Methods:
- Software is organized into fungis basic functions (modular)
- avoiding GOTO
- Methods exist only in software, data
- Suitable for the development of scientific applications (scientific application)
- Using the tool Data Flow Diagrams (DFD)
- Suitable for the development of scientific applications (scientific application)
- Using the tool Data Flow Diagrams (DFD)
- 1980's
- An update method structured entity concept model is a collection of data items.
- Suitable for business application development because the data is relatively stable
- Using a relational database
- Using the tool Entity Relationship Diagram (ERD)
DFD weak in organizing data
ERD weak in organizing the function
ERD weak in organizing the function
- OOP provides solutions to problems where data exist and function in synchronized object (1990)
- Data and function are united in an object
- Progress begins with the concept of abstract data types.
- Abstract data types:
- Developers create a data structure that can be accessed.
- weaknesses:
- Structured approach vs OOP:
- Structured approach
- Procedure-oriented programming
- Problems seen as a sequence of things to be done.
- Main activities: write a list of commands and then organize them into procedures / functions
In the multipurpose program, the data is placed globally (a weakness) - Structured approach does not describe the real world
- The function was developed based on the action is not the problem
- Software produced more dominated by the desire of the user programmer.
- Do not support reuse of components (modules not standard)
Main ---- Fungsi 1 -------> fungsi 3
Fungsi 1 -------> fungsi 4
Main ---- Fungsi 2 -------> fungsi 4
---- Fungsi 2 -------> fungsi 5
- Main characteristics:
- Emphasis on something that should be done
- Large programs are broken down into smaller programs (modular)
- Procedures and functions share global data
- Data move freely within the system
- Functions transform data from one form to another
- Top Down Approach
Rizka: ya, makasih deh atas referensinya, tapi pbo disini bkan masuk ke aplikasi atau bahasa java, ini khusus buat pembelajaran delphi. dan ane juga dapet dari kampus ane, tapi makasih sebelumnya.
ReplyDelete