a본 강의에서는 C언어의 break와 continue문에 대해 알아보겠습니다. break 명령은 반복 제어문에서 빠져나오는 명령이며, continue 명령은 반복 제어문에서 현재 실행하고 있는 반복과정의 나머지를 생력하고 다음 반복을 진행하는 기능을 합니다.
- Youtube 강의동영상
https://youtu.be/MeqSNCo2g4o
- 코드는 여기에서 다운 받으세요
https://github.com/dongupak/Basic-C-Programming
Bubble sort is the simplest sorting algorithm. In this technique we follow given step to short given elements in increasing order.
http://www.tutorial4us.com/data-structure/c-bubble-sort
Unit 1 android and it's tools quiz {mad cwipedia}Ankit Dubey
The document is an Android quiz consisting of 15 multiple choice questions about Android fundamentals. It covers topics like who developed Android, the programming languages used, Android versions, and components like the kernel, IDEs, and architecture. The participant answered all questions correctly, scoring full marks. Daily quizzes on Android and other computer subjects are promised to help prepare for online exams.
This document summarizes operating system process scheduling. It discusses short, long, and medium term schedulers and the CPU-IO burst cycle. It describes preemptive scheduling and different scheduling algorithms like first-come first-served, shortest job first, priority, and round robin. It also discusses scheduling criteria for optimization and different performance evaluation methods. Finally, it provides an overview of process scheduling in Linux and Windows NT systems.
This document discusses defect management. It defines a defect as an error or bug in software. Defects can arise during various stages of development due to issues like miscommunication, unrealistic schedules, lack of experience, or poor testing. Defects are classified by severity, work product, type of error, and status. The defect life cycle and management process are also described, including techniques for preventing, discovering, resolving, and closing defects through activities like reviews, logging, analysis, and process improvements.
The document provides details about preparing a test plan, including defining the scope, approach, resources, schedule, and activities for intended test activities. It discusses analyzing the product, developing a test strategy, defining objectives and criteria, planning resources and the test environment, scheduling, and identifying test deliverables. Test plans can be master plans, level-specific plans, or type-specific plans. The document also provides guidelines for test plans, including making the plan concise and specific, using lists and tables, and updating the plan regularly. It discusses deciding the test approach, setting criteria, identifying responsibilities, and planning staff training and resource requirements.
This document discusses different types and levels of software testing, including unit testing, integration testing, and performance testing. It provides details on each type or level:
Unit testing validates individual software components and is done by developers. Integration testing combines units and tests them as a group. Performance testing ensures the software performs as expected under workload. Specific techniques like load testing, stress testing, and security testing are discussed. Stubs and drivers are also explained as tools used in integration testing.
The document provides an overview of software testing methods and concepts. It defines software testing as verifying and validating software to check for errors and ensure it meets requirements. The document discusses different testing methods like static testing (reviews, inspections) and dynamic testing (executing code with test cases). It also defines key terms like verification, validation, defects, bugs, and differences between quality assurance (planning processes) and quality control (product verification).
a본 강의에서는 C언어의 break와 continue문에 대해 알아보겠습니다. break 명령은 반복 제어문에서 빠져나오는 명령이며, continue 명령은 반복 제어문에서 현재 실행하고 있는 반복과정의 나머지를 생력하고 다음 반복을 진행하는 기능을 합니다.
- Youtube 강의동영상
https://youtu.be/MeqSNCo2g4o
- 코드는 여기에서 다운 받으세요
https://github.com/dongupak/Basic-C-Programming
Bubble sort is the simplest sorting algorithm. In this technique we follow given step to short given elements in increasing order.
http://www.tutorial4us.com/data-structure/c-bubble-sort
Unit 1 android and it's tools quiz {mad cwipedia}Ankit Dubey
The document is an Android quiz consisting of 15 multiple choice questions about Android fundamentals. It covers topics like who developed Android, the programming languages used, Android versions, and components like the kernel, IDEs, and architecture. The participant answered all questions correctly, scoring full marks. Daily quizzes on Android and other computer subjects are promised to help prepare for online exams.
This document summarizes operating system process scheduling. It discusses short, long, and medium term schedulers and the CPU-IO burst cycle. It describes preemptive scheduling and different scheduling algorithms like first-come first-served, shortest job first, priority, and round robin. It also discusses scheduling criteria for optimization and different performance evaluation methods. Finally, it provides an overview of process scheduling in Linux and Windows NT systems.
This document discusses defect management. It defines a defect as an error or bug in software. Defects can arise during various stages of development due to issues like miscommunication, unrealistic schedules, lack of experience, or poor testing. Defects are classified by severity, work product, type of error, and status. The defect life cycle and management process are also described, including techniques for preventing, discovering, resolving, and closing defects through activities like reviews, logging, analysis, and process improvements.
The document provides details about preparing a test plan, including defining the scope, approach, resources, schedule, and activities for intended test activities. It discusses analyzing the product, developing a test strategy, defining objectives and criteria, planning resources and the test environment, scheduling, and identifying test deliverables. Test plans can be master plans, level-specific plans, or type-specific plans. The document also provides guidelines for test plans, including making the plan concise and specific, using lists and tables, and updating the plan regularly. It discusses deciding the test approach, setting criteria, identifying responsibilities, and planning staff training and resource requirements.
This document discusses different types and levels of software testing, including unit testing, integration testing, and performance testing. It provides details on each type or level:
Unit testing validates individual software components and is done by developers. Integration testing combines units and tests them as a group. Performance testing ensures the software performs as expected under workload. Specific techniques like load testing, stress testing, and security testing are discussed. Stubs and drivers are also explained as tools used in integration testing.
The document provides an overview of software testing methods and concepts. It defines software testing as verifying and validating software to check for errors and ensure it meets requirements. The document discusses different testing methods like static testing (reviews, inspections) and dynamic testing (executing code with test cases). It also defines key terms like verification, validation, defects, bugs, and differences between quality assurance (planning processes) and quality control (product verification).
1) Files are the basic unit of storage in an operating system. They provide a logical view of information storage that is abstracted from physical storage devices.
2) A file has attributes like its name, size, location, and permissions. The operating system performs basic operations on files like creating, reading, writing, deleting and truncating files.
3) There are different methods for organizing files and allocating storage space, including contiguous, linked, and indexed allocation schemes as well as single-level, two-level, and tree directory structures. This allows files to be efficiently organized and accessed.
This document summarizes Chapter 5 from the textbook "Operating System Concepts - 8th Edition" by Silberschatz, Galvin and Gagne. The chapter introduces CPU scheduling algorithms which are important for multiprogrammed operating systems. It describes scheduling criteria like CPU utilization and waiting time. Specific algorithms covered include first-come first-served scheduling, shortest-job-first scheduling, priority scheduling, and round robin scheduling. Advanced scheduling techniques involving multiple queues and multiple processors are also discussed.
The document discusses threads and threading models in operating systems. It defines a thread as the basic unit of CPU utilization comprising a thread ID, program counter, and register set. It describes single-threaded and multithreaded processes, benefits of multithreading, and concurrent/parallel execution. It also covers user threads, kernel threads, threading libraries like Pthreads and Java threads, and threading issues around fork(), exec(), signals, thread pools and more. It provides examples of threading in Windows XP and Linux.
This document summarizes Chapter 3 from the textbook "Operating System Concepts - 8th Edition" by Silberschatz, Galvin and Gagne. The chapter discusses processes, including the process concept, scheduling, operations on processes, and interprocess communication. Key points include that a process is a program in execution, processes have various states like ready, running, waiting, and that the operating system uses process control blocks and queues to manage processes and allocate CPU resources using schedulers. Interprocess communication allows cooperating processes to communicate through methods like message passing and shared memory.
The document discusses different operating system structures including monolithic, layered, and microkernel structures. A monolithic structure has all operating system functions in the kernel. Layered structures divide the OS into separate layers with each layer building on the ones below. Microkernel structures move nonessential components out of the kernel into user space and the kernel primarily handles communication between user modules.
This document discusses the key concepts of operating systems. It defines an operating system as a program that acts as an intermediary between the user and computer hardware. The four main components of a computer system are hardware, application programs, the operating system, and users. It describes the evolution of operating systems from batch processing to time sharing and personal computing. Different generations of computers are also outlined, from first generation machines using vacuum tubes to fourth generation systems using integrated circuits.
This document contains multiple choice questions and answers about Android. It tests knowledge of key aspects of the Android operating system including its licensing, ownership, minimum development targets, Google's business motivations, the first Android phone released, advantages for phone manufacturers, and facts about early Android development. It also covers the Open Handset Alliance announcement year, emulator vs simulator differences, Android application packaging, and components like activities, services, and intents.
This document provides a mock test for MongoDB with 25 multiple choice questions. It includes questions about MongoDB queries, indexes, transactions, and other concepts. The test is provided to help users practice and test their MongoDB skills offline. An answer key is provided to allow users to self-grade the test.
The document provides a 25 question mock test on Android fundamentals. It includes multiple choice questions covering topics like LastKnownLocation, finding GPS status programmatically, base adapters, breakpoints, DDMS, log messages, ADB, emulator ports, APKs, debugging techniques, fixing crashes with logcat, HTTP client functionality, JSON packages, MapViews, refreshing dynamic content with Ajax, JSON elements, HTTP response codes, JSON exceptions, and finding JSON element length. The answer key is provided after the questions.
This section presents various Android mock tests that can be downloaded and solved offline. Each mock test includes questions on Android topics like ANR, AsyncTask, BroadcastReceivers, ContentProviders, SQLite, tasks and activities, device features, location services, and permissions. An answer key is provided to allow users to self-grade their performance on each mock test.
This document provides an overview of servlets, including:
1. Servlets are Java programs that extend the functionality of web servers by dynamically processing HTTP requests and responses.
2. The life cycle of a servlet involves loading, instantiating, processing requests, and destroying.
3. Common steps to create and run a simple "Hello World" servlet using Tomcat include writing Java code, compiling, configuring deployment descriptors, and making HTTP requests.
4. Servlets offer benefits over other technologies like CGI scripts by being more efficient, persistent, portable, robust, and secure.
This document discusses Java Database Connectivity (JDBC) which provides a standard interface for connecting Java applications to various databases. It describes the JDBC API and architecture, including the four types of JDBC drivers. The key points are:
1) JDBC provides a standard way for Java programs to access any SQL database. It uses JDBC drivers implemented by database vendors to translate JDBC calls into database-specific protocols.
2) The JDBC API has two layers - an application layer used by developers, and a driver layer implemented by vendors. There are four main interfaces (Driver, Connection, Statement, ResultSet) and the DriverManager class.
3) There are
This document provides an overview of networking concepts in Java. It discusses socket programming, client-server models, Internet addressing using IPv4 and IPv6, common network ports, proxy servers, and the core Java networking classes like InetAddress and URLConnection that support network communication. The document serves as an introduction to networking basics and how Java implements network functionality through its java.net package.
This document provides an overview of event handling in Java. It discusses the delegation event model where a source generates an event and sends it to one or more listeners. It describes event sources, event listeners, common event classes like ActionEvent, MouseEvent, and KeyEvent. It explains the roles of sources that generate events, listeners that receive event notifications, and event classes that represent specific types of events.