Pengenalan Organisasi dan Arsitektur Komputer
•Download as PPTX, PDF•
3 likes•2,478 views
Dokumen tersebut merupakan daftar referensi dua buah buku tentang organisasi dan arsitektur komputer. Dua buku tersebut adalah Computer Organization and Architecture karya William Stalling edisi ke-10 tahun 2015 dan Organisasi dan Arsitektur Komputer karya Maman Abdurohman revisi ke-4 tahun 2017.
Report
Share
Report
Share
Recommended
Software Testing Documentation
The document discusses the importance of documentation in software testing. It notes that documentation is needed to record test implementation and results, and helps direct testing and reuse tests. There are different types of test documentation, including test plans, specifications, and analysis reports. Effective documentation provides benefits like training, communication, maintenance, and historical reference. Test documentation should be maintained throughout the software development life cycle.
Software Productivity Measurement
1) The document discusses various metrics for measuring software productivity, quality, and testing at different stages of the software development process. It covers metrics for requirements, design, source code, testing, maintenance, and processes.
2) Key metrics discussed include defects per KLOC, function points, defect removal efficiency, and size-oriented vs function-oriented metrics. Metrics for object-oriented design, user interfaces, and project management are also summarized.
3) Collecting measures and developing metrics at each stage of development allows indicators to be obtained and improvements to be made to both the product and process. A variety of productivity, quality, and testing metrics can provide meaningful insights.
Debugging (Part 2)
The document discusses various debugging techniques. It describes the brute force method, which involves taking memory dumps and adding print statements to locate bugs. This generates a large amount of data but requires little thought. The cause elimination method deduces or induces potential causes and tests hypotheses to eliminate them one by one. Other methods include trial and error, backtracking code to find failures, and forward tracking to see when results first became wrong. Principles for locating errors include thinking carefully and getting a fresh perspective. Principles for repairing errors are to fix the underlying cause, check for new errors, and re-evaluate the design when making changes.
Debugging
The document discusses debugging processes and techniques. It defines debugging as the process of finding, correcting and removing bugs from programs. There are three main types of errors: syntactic, semantic, and logic errors. The debugging process involves reproducing the problem reliably, finding the source of the error, fixing just that one error, testing the fix, and optionally looking for more errors. Key debugging techniques include inserting print statements, using a debugger, explaining the code to someone else, and fixing only one error at a time. The overall goal of debugging is to methodically match symptoms to causes to locate and correct errors in code.
Software Testing Strategy (Part 2)
This document discusses various types of software testing strategies including integration testing, continuous integration testing, and system testing. It provides details on techniques like top-down integration, bottom-up integration, smoke testing, regression testing, interface testing, and acceptance and installation testing. The objectives are to learn about integration testing, continuous integration testing, and system testing. Key aspects of different strategies like top-down vs bottom-up integration and categories of system test cases are compared. Determining when to stop testing is noted as one of the most difficult questions.
Software Testing Strategy
The document provides an overview of software testing strategies. It discusses that the main objective of software testing is to systematically find errors without taking much time. It emphasizes the importance of choosing the best testing strategy. It then covers various software testing strategies including unit testing, integration testing, validation testing, and system testing. Unit testing involves testing individual software components in isolation while integration testing focuses on testing the interaction between integrated components. The document contrasts the incremental and "big bang" approaches to integration testing and argues that the incremental approach is more effective.
Object Oriented Testing
The document discusses object-oriented testing strategies. It explains that in object-oriented testing, the component being tested is a class-object rather than a function. Unit testing focuses on testing each class's operations and attributes. Integration testing focuses on testing groups of collaborating classes. Validation testing is based on use case scenarios from the object-oriented analysis model. The document provides details on techniques for unit testing, integration testing, and validation testing of object-oriented systems.
Testing Technique (Part 2)
The document discusses various software testing techniques, including blackbox and whitebox testing. Blackbox testing focuses on functional requirements without seeing the internal structure and includes equivalence class testing, limit testing, robustness testing, and requirements testing. Whitebox testing uses internal program structure to derive test cases and focuses on all logical paths and decisions. It includes basis path testing and control structure testing such as conditional and loop testing. The document provides examples of applying these techniques.
Recommended
Software Testing Documentation
The document discusses the importance of documentation in software testing. It notes that documentation is needed to record test implementation and results, and helps direct testing and reuse tests. There are different types of test documentation, including test plans, specifications, and analysis reports. Effective documentation provides benefits like training, communication, maintenance, and historical reference. Test documentation should be maintained throughout the software development life cycle.
Software Productivity Measurement
1) The document discusses various metrics for measuring software productivity, quality, and testing at different stages of the software development process. It covers metrics for requirements, design, source code, testing, maintenance, and processes.
2) Key metrics discussed include defects per KLOC, function points, defect removal efficiency, and size-oriented vs function-oriented metrics. Metrics for object-oriented design, user interfaces, and project management are also summarized.
3) Collecting measures and developing metrics at each stage of development allows indicators to be obtained and improvements to be made to both the product and process. A variety of productivity, quality, and testing metrics can provide meaningful insights.
Debugging (Part 2)
The document discusses various debugging techniques. It describes the brute force method, which involves taking memory dumps and adding print statements to locate bugs. This generates a large amount of data but requires little thought. The cause elimination method deduces or induces potential causes and tests hypotheses to eliminate them one by one. Other methods include trial and error, backtracking code to find failures, and forward tracking to see when results first became wrong. Principles for locating errors include thinking carefully and getting a fresh perspective. Principles for repairing errors are to fix the underlying cause, check for new errors, and re-evaluate the design when making changes.
Debugging
The document discusses debugging processes and techniques. It defines debugging as the process of finding, correcting and removing bugs from programs. There are three main types of errors: syntactic, semantic, and logic errors. The debugging process involves reproducing the problem reliably, finding the source of the error, fixing just that one error, testing the fix, and optionally looking for more errors. Key debugging techniques include inserting print statements, using a debugger, explaining the code to someone else, and fixing only one error at a time. The overall goal of debugging is to methodically match symptoms to causes to locate and correct errors in code.
Software Testing Strategy (Part 2)
This document discusses various types of software testing strategies including integration testing, continuous integration testing, and system testing. It provides details on techniques like top-down integration, bottom-up integration, smoke testing, regression testing, interface testing, and acceptance and installation testing. The objectives are to learn about integration testing, continuous integration testing, and system testing. Key aspects of different strategies like top-down vs bottom-up integration and categories of system test cases are compared. Determining when to stop testing is noted as one of the most difficult questions.
Software Testing Strategy
The document provides an overview of software testing strategies. It discusses that the main objective of software testing is to systematically find errors without taking much time. It emphasizes the importance of choosing the best testing strategy. It then covers various software testing strategies including unit testing, integration testing, validation testing, and system testing. Unit testing involves testing individual software components in isolation while integration testing focuses on testing the interaction between integrated components. The document contrasts the incremental and "big bang" approaches to integration testing and argues that the incremental approach is more effective.
Object Oriented Testing
The document discusses object-oriented testing strategies. It explains that in object-oriented testing, the component being tested is a class-object rather than a function. Unit testing focuses on testing each class's operations and attributes. Integration testing focuses on testing groups of collaborating classes. Validation testing is based on use case scenarios from the object-oriented analysis model. The document provides details on techniques for unit testing, integration testing, and validation testing of object-oriented systems.
Testing Technique (Part 2)
The document discusses various software testing techniques, including blackbox and whitebox testing. Blackbox testing focuses on functional requirements without seeing the internal structure and includes equivalence class testing, limit testing, robustness testing, and requirements testing. Whitebox testing uses internal program structure to derive test cases and focuses on all logical paths and decisions. It includes basis path testing and control structure testing such as conditional and loop testing. The document provides examples of applying these techniques.
Testing Technique
This document discusses various software testing techniques classified into static, dynamic, and exhaustive categories. Static techniques like verification and static analysis do not require executing the program. Dynamic techniques execute the program and are divided into structure-oriented techniques like control flow testing and function-oriented techniques like function coverage and use case testing. Exhaustive techniques aim to cover all possible test cases. The document provides examples and explanations of different testing methods.
Testing Plan
The document discusses software testing concepts including:
1. It defines key terms related to software defects such as errors, defects, failures, and faults.
2. It outlines the different phases of software testing from component/unit testing to acceptance testing and discusses principles of good testability.
3. It provides guidance on writing test plans and cases, including reviewing requirements, identifying test suites, and transforming use cases into test cases.
Methodology Selection Strategy
This document discusses methodology selection strategy for systems analysis and design. It explains that there is no single framework appropriate for every software project, and the methodology needs to be adapted to the specific team and product. It outlines important factors to consider like clarity of requirements, technology familiarity, system complexity, schedule constraints. The methodology should guide the team's process but allow flexibility. The success of the methodology is measured by timely delivery of quality product increments that satisfy stakeholders.
Software Testing - Software Quality (Part 2)
The document discusses software quality and testing. It defines software reliability as the probability of failure-free operation of a computer program in a given environment and time. Testing aims to find errors in programs to improve reliability, rather than show a program works correctly. The document outlines ISO quality standards for software development including ISO 9001, which provides a framework for quality processes and procedures. Organizations must comply with ISO 9001 requirements to achieve quality certification.
Software Testing - Software Quality
The document discusses software quality assurance and testing. It defines software quality as having two aspects - quality of design which includes requirements and specifications, and quality of conformance which focuses on implementation. Software Quality Assurance (SQA) includes quality management, effective engineering processes, formal techniques, testing strategies, documentation control, and measurement/reporting. SQA aims to ensure requirements quality, design quality, code quality, and effective quality control. Non-functional attributes like reliability, usability, and performance largely determine a software's subjective quality from a user's perspective.
Computer Evolution and Performance
ajeng.savitri@teknokrat.ac.id
https://teknokrat.ac.id/en/
https://spada.teknokrat.ac.id/
Software Testing - Introduction
The document describes an introduction to software testing presentation. It discusses the software development life cycle (SDLC) which includes planning, analysis, design, implementation, and maintenance phases. It then explains different software development methodologies like structured design, rapid application development, and agile development. Finally, it provides definitions and goals of software testing, and presents a model of the software testing process.
Sequence Diagram
Dokumen ini membahas tentang analisis dan desain sistem untuk sistem ATM. Terdapat penjelasan mengenai diagram urutan dan diagram kelas yang menggambarkan interaksi antar objek dalam sistem ATM untuk beberapa kasus penggunaan seperti mengecek saldo, mentransfer uang, dan mengambil uang. Dokumen ini juga menampilkan contoh desain antarmuka pengguna untuk sistem ATM menggunakan perangkat lunak Netbeans.
Activity Diagram
Dokumen ini membahas tentang pemodelan proses bisnis dengan diagram aktivitas dan menggunakan sistem ATM sebagai contoh studi kasus. Diagram aktivitas digunakan untuk memvisualisasikan aliran kerja dalam suatu proses bisnis yang melibatkan beberapa departemen. Contoh aktivitas yang dimodelkan meliputi memasukkan PIN, mengecek saldo, mentransfer uang, mengambil uang, dan logout.
Use Case Diagram
The document discusses use case diagrams for systems analysis and design. It provides examples of use case diagrams for an appointment system and an ATM system. Key elements of use case diagrams are described, including actors, use cases, relationships like generalization, include and extend, and the system boundary. The ATM system example demonstrates how a use case diagram can model the interactions between an actor (user) and the various functions of an ATM machine like checking balance, transferring money, withdrawing money and logging out.
Requirement Gathering
Systems analysis and design techniques are discussed, including requirement gathering and business process analysis. Requirement gathering involves document analysis, interviews, questionnaires, and observation to understand user needs. Functional requirements define system functions while non-functional requirements address system qualities. Business process analysis assesses current processes and can involve automation, improvement, or reengineering. Barriers to effective requirement gathering include users finding additional needs after seeing a system ("yes but" syndrome), incomplete discovery of all needs ("undiscovered ruins" syndrome), and communication gaps between users and developers.
Business Value
The document discusses a feasibility analysis for a proposed CD Selections Internet Order System project.
The technical feasibility is determined to be medium risk overall, as the application and technology are somewhat unfamiliar but compatible with existing systems. The economic feasibility analysis shows a 229% return on investment over 3 years with a break-even point of 1.7 years. The organizational feasibility is low risk as the project aligns with goals of increasing sales and becoming more Internet-savvy.
Agile Development
The document discusses different agile development methodologies including Extreme Programming (XP), Scrum, Lean Development, and Dynamic Systems Development Model (DSDM). It provides details on the key aspects of XP and Scrum. XP focuses on communication, simplicity, feedback, and courage. Scrum uses self-organized teams, sprints to develop functionality in iterations with feedback from customers. While XP deals with programming and Scrum with project organization, Lean Development focuses on principles for the entire development organization. Factors like requirements clarity, technology familiarity, complexity, reliability, schedules, and schedule visibility should be considered when selecting a methodology.
Structured Design
This document discusses systems analysis and design methodologies. It covers structured design methodologies like the waterfall method and parallel development. It also discusses rapid application development, agile development approaches like extreme programming and scrum, and compares their activities and artifacts. The structured design approaches like waterfall involve completing each phase before beginning the next, while agile methods are more adaptive. Waterfall has long timelines but minimizes changes, while parallel development addresses the time gap by breaking a project into parallel subprojects.
Introduction to SDLC
The document discusses the systems development life cycle (SDLC) which includes four main phases: planning, analysis, design, and implementation.
In the planning phase, the business need for the system is identified and feasibility is analyzed. The analysis phase involves gathering requirements by determining who will use the system, what it will do, and when it will be used.
The design phase includes program, user interface, and data design to determine how the system will work. Finally, in the implementation phase the system is constructed, tested, installed, and put into operation. Key deliverables and processes are discussed for each phase of the SDLC.
Systems Analyst and Its Roles (2)
The document discusses the role of systems analysts and what they do. It begins by explaining that information systems have become essential for businesses to compete. Systems analysts play a special role in developing these systems by facilitating the analysis, design, and implementation of technology solutions to business problems.
The document then defines systems analysts as professionals who understand both business and technology. They study business problems and needs to determine how information systems and applications can solve issues and improve the business. Systems analysts are responsible for capturing and flowing business data to and from computer systems.
Finally, the document outlines the typical tasks and responsibilities of systems analysts. They follow a systematic approach called the systems development life cycle which includes planning, analysis, design, implementation, and
Systems Analyst and Its Roles
The document discusses the roles of various analysts involved in systems analysis and design. It describes the roles of business analysts, system analysts, infrastructure analysts, change management analysts, and project managers. It explains that business analysts focus on business issues and value, system analysts focus on improving business processes through information systems, and infrastructure analysts focus on system interfaces and standards. Change management analysts coordinate user training and adoption while project managers are responsible for schedules, budgets, and benefits delivery.
Algoritma Branch and Bound
ajeng.savitri@teknokrat.ac.id
https://teknokrat.ac.id/en/
https://spada.teknokrat.ac.id/
Algoritma Backtracking
Backtracking adalah algoritma berbasis DFS untuk mencari solusi persoalan secara lebih efisien daripada metode brute-force. Backtracking mencari solusi dengan mengevaluasi kemungkinan solusi secara sistematis dan membuang solusi yang tidak memenuhi kriteria. Backtracking sering digunakan untuk masalah games dan AI.
Algoritma Traversal dalam Graf
Dokumen ini membahas algoritma traversal graf, yaitu algoritma untuk mengunjungi simpul-simpul dalam graf secara sistematis. Ada dua algoritma traversal graf yang dijelaskan, yaitu Pencarian Melebar (BFS) dan Pencarian Mendalam (DFS). BFS akan mengunjungi semua simpul yang bertetangga dengan simpul awal terlebih dahulu sebelum ke simpul selanjutnya. Sedangkan DFS akan mengunjungi salah satu simpul tetang
More Related Content
More from Ajeng Savitri
Testing Technique
This document discusses various software testing techniques classified into static, dynamic, and exhaustive categories. Static techniques like verification and static analysis do not require executing the program. Dynamic techniques execute the program and are divided into structure-oriented techniques like control flow testing and function-oriented techniques like function coverage and use case testing. Exhaustive techniques aim to cover all possible test cases. The document provides examples and explanations of different testing methods.
Testing Plan
The document discusses software testing concepts including:
1. It defines key terms related to software defects such as errors, defects, failures, and faults.
2. It outlines the different phases of software testing from component/unit testing to acceptance testing and discusses principles of good testability.
3. It provides guidance on writing test plans and cases, including reviewing requirements, identifying test suites, and transforming use cases into test cases.
Methodology Selection Strategy
This document discusses methodology selection strategy for systems analysis and design. It explains that there is no single framework appropriate for every software project, and the methodology needs to be adapted to the specific team and product. It outlines important factors to consider like clarity of requirements, technology familiarity, system complexity, schedule constraints. The methodology should guide the team's process but allow flexibility. The success of the methodology is measured by timely delivery of quality product increments that satisfy stakeholders.
Software Testing - Software Quality (Part 2)
The document discusses software quality and testing. It defines software reliability as the probability of failure-free operation of a computer program in a given environment and time. Testing aims to find errors in programs to improve reliability, rather than show a program works correctly. The document outlines ISO quality standards for software development including ISO 9001, which provides a framework for quality processes and procedures. Organizations must comply with ISO 9001 requirements to achieve quality certification.
Software Testing - Software Quality
The document discusses software quality assurance and testing. It defines software quality as having two aspects - quality of design which includes requirements and specifications, and quality of conformance which focuses on implementation. Software Quality Assurance (SQA) includes quality management, effective engineering processes, formal techniques, testing strategies, documentation control, and measurement/reporting. SQA aims to ensure requirements quality, design quality, code quality, and effective quality control. Non-functional attributes like reliability, usability, and performance largely determine a software's subjective quality from a user's perspective.
Computer Evolution and Performance
ajeng.savitri@teknokrat.ac.id
https://teknokrat.ac.id/en/
https://spada.teknokrat.ac.id/
Software Testing - Introduction
The document describes an introduction to software testing presentation. It discusses the software development life cycle (SDLC) which includes planning, analysis, design, implementation, and maintenance phases. It then explains different software development methodologies like structured design, rapid application development, and agile development. Finally, it provides definitions and goals of software testing, and presents a model of the software testing process.
Sequence Diagram
Dokumen ini membahas tentang analisis dan desain sistem untuk sistem ATM. Terdapat penjelasan mengenai diagram urutan dan diagram kelas yang menggambarkan interaksi antar objek dalam sistem ATM untuk beberapa kasus penggunaan seperti mengecek saldo, mentransfer uang, dan mengambil uang. Dokumen ini juga menampilkan contoh desain antarmuka pengguna untuk sistem ATM menggunakan perangkat lunak Netbeans.
Activity Diagram
Dokumen ini membahas tentang pemodelan proses bisnis dengan diagram aktivitas dan menggunakan sistem ATM sebagai contoh studi kasus. Diagram aktivitas digunakan untuk memvisualisasikan aliran kerja dalam suatu proses bisnis yang melibatkan beberapa departemen. Contoh aktivitas yang dimodelkan meliputi memasukkan PIN, mengecek saldo, mentransfer uang, mengambil uang, dan logout.
Use Case Diagram
The document discusses use case diagrams for systems analysis and design. It provides examples of use case diagrams for an appointment system and an ATM system. Key elements of use case diagrams are described, including actors, use cases, relationships like generalization, include and extend, and the system boundary. The ATM system example demonstrates how a use case diagram can model the interactions between an actor (user) and the various functions of an ATM machine like checking balance, transferring money, withdrawing money and logging out.
Requirement Gathering
Systems analysis and design techniques are discussed, including requirement gathering and business process analysis. Requirement gathering involves document analysis, interviews, questionnaires, and observation to understand user needs. Functional requirements define system functions while non-functional requirements address system qualities. Business process analysis assesses current processes and can involve automation, improvement, or reengineering. Barriers to effective requirement gathering include users finding additional needs after seeing a system ("yes but" syndrome), incomplete discovery of all needs ("undiscovered ruins" syndrome), and communication gaps between users and developers.
Business Value
The document discusses a feasibility analysis for a proposed CD Selections Internet Order System project.
The technical feasibility is determined to be medium risk overall, as the application and technology are somewhat unfamiliar but compatible with existing systems. The economic feasibility analysis shows a 229% return on investment over 3 years with a break-even point of 1.7 years. The organizational feasibility is low risk as the project aligns with goals of increasing sales and becoming more Internet-savvy.
Agile Development
The document discusses different agile development methodologies including Extreme Programming (XP), Scrum, Lean Development, and Dynamic Systems Development Model (DSDM). It provides details on the key aspects of XP and Scrum. XP focuses on communication, simplicity, feedback, and courage. Scrum uses self-organized teams, sprints to develop functionality in iterations with feedback from customers. While XP deals with programming and Scrum with project organization, Lean Development focuses on principles for the entire development organization. Factors like requirements clarity, technology familiarity, complexity, reliability, schedules, and schedule visibility should be considered when selecting a methodology.
Structured Design
This document discusses systems analysis and design methodologies. It covers structured design methodologies like the waterfall method and parallel development. It also discusses rapid application development, agile development approaches like extreme programming and scrum, and compares their activities and artifacts. The structured design approaches like waterfall involve completing each phase before beginning the next, while agile methods are more adaptive. Waterfall has long timelines but minimizes changes, while parallel development addresses the time gap by breaking a project into parallel subprojects.
Introduction to SDLC
The document discusses the systems development life cycle (SDLC) which includes four main phases: planning, analysis, design, and implementation.
In the planning phase, the business need for the system is identified and feasibility is analyzed. The analysis phase involves gathering requirements by determining who will use the system, what it will do, and when it will be used.
The design phase includes program, user interface, and data design to determine how the system will work. Finally, in the implementation phase the system is constructed, tested, installed, and put into operation. Key deliverables and processes are discussed for each phase of the SDLC.
Systems Analyst and Its Roles (2)
The document discusses the role of systems analysts and what they do. It begins by explaining that information systems have become essential for businesses to compete. Systems analysts play a special role in developing these systems by facilitating the analysis, design, and implementation of technology solutions to business problems.
The document then defines systems analysts as professionals who understand both business and technology. They study business problems and needs to determine how information systems and applications can solve issues and improve the business. Systems analysts are responsible for capturing and flowing business data to and from computer systems.
Finally, the document outlines the typical tasks and responsibilities of systems analysts. They follow a systematic approach called the systems development life cycle which includes planning, analysis, design, implementation, and
Systems Analyst and Its Roles
The document discusses the roles of various analysts involved in systems analysis and design. It describes the roles of business analysts, system analysts, infrastructure analysts, change management analysts, and project managers. It explains that business analysts focus on business issues and value, system analysts focus on improving business processes through information systems, and infrastructure analysts focus on system interfaces and standards. Change management analysts coordinate user training and adoption while project managers are responsible for schedules, budgets, and benefits delivery.
Algoritma Branch and Bound
ajeng.savitri@teknokrat.ac.id
https://teknokrat.ac.id/en/
https://spada.teknokrat.ac.id/
Algoritma Backtracking
Backtracking adalah algoritma berbasis DFS untuk mencari solusi persoalan secara lebih efisien daripada metode brute-force. Backtracking mencari solusi dengan mengevaluasi kemungkinan solusi secara sistematis dan membuang solusi yang tidak memenuhi kriteria. Backtracking sering digunakan untuk masalah games dan AI.
Algoritma Traversal dalam Graf
Dokumen ini membahas algoritma traversal graf, yaitu algoritma untuk mengunjungi simpul-simpul dalam graf secara sistematis. Ada dua algoritma traversal graf yang dijelaskan, yaitu Pencarian Melebar (BFS) dan Pencarian Mendalam (DFS). BFS akan mengunjungi semua simpul yang bertetangga dengan simpul awal terlebih dahulu sebelum ke simpul selanjutnya. Sedangkan DFS akan mengunjungi salah satu simpul tetang
More from Ajeng Savitri (20)
Pengenalan Organisasi dan Arsitektur Komputer
- 20. Refference Stalling, William, Computer Organization and Architecture, 10th Edition, Pearson, 2015 Abdurohman, Maman, Organisasi dan Arsitektur Komputer revisi ke-4, Penerbit Informatika, 2017