<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>Learn Software Development &#187; State</title>
	<atom:link href="http://learnsoftwareprocesses.com/category/state/feed/" rel="self" type="application/rss+xml" />
	<link>http://learnsoftwareprocesses.com</link>
	<description>All about the processes involved in software development</description>
	<lastBuildDate>Sun, 20 May 2012 19:17:40 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
			<item>
		<title>Overview Of Process</title>
		<link>http://learnsoftwareprocesses.com/2009/08/26/overview-of-process/</link>
		<comments>http://learnsoftwareprocesses.com/2009/08/26/overview-of-process/#comments</comments>
		<pubDate>Wed, 26 Aug 2009 09:59:05 +0000</pubDate>
		<dc:creator>ashish</dc:creator>
				<category><![CDATA[PCB]]></category>
		<category><![CDATA[Process]]></category>
		<category><![CDATA[Process Control Block]]></category>
		<category><![CDATA[Stages]]></category>
		<category><![CDATA[State]]></category>

		<guid isPermaLink="false">http://learnsoftwareprocesses.com/?p=317</guid>
		<description><![CDATA[<p>A process is an activity which takes place over time and which has a precise aim regarding the result to be achieved. The concept of a process is hierarchical which means that a process may consist of a partially ordered set of sub-processes. A process is rather abstract. It describes the essentials of the purpose, [...]]]></description>
			<content:encoded><![CDATA[<p>A process is an activity which takes place over time and which has a precise aim regarding the result to be achieved. The concept of a process is hierarchical which means that a process may consist of a partially ordered set of sub-processes. A process is rather abstract. It describes the essentials of the purpose, structure, rationale, roles and timing, leaving plenty of implementation freedom. The power of a process is its abstraction, which enables its application in a wide range of applications, by tailoring its implementation to the specific application. A process can be tailored and elaborated in one or more procedures, which describe cookbook-like what need to be done when and by whom.<br />
The process has been given many definitions for instance :<br />
* A program in Execution.<br />
* An asynchronous activity.<br />
* The &#8216;animated sprit&#8217; of a procedure in execution.<br />
* The entity to which processors are assigned.<br />
* The &#8216;dispatchable&#8217; unit.<br />
In Process model, all software on the computer is organized into a number of sequential processes. A process includes PC, registers, and variables. Conceptually, each process has its own virtual CPU. In reality, the CPU switches back and forth among processes.<br />
A process goes through a series of discrete process states :<br />
* New State: The process being created.<br />
* Running State: A process is said to be running if it has the CPU, that is, process actually using the CPU at that particular instant.<br />
* Blocked (or waiting) State: A process is said to be blocked if it is waiting for some event to happen such that as an I/O completion before it can proceed. Note that a process is unable to run until some external event happens.<br />
* Ready State: A process is said to be ready if it use a CPU if one were available. A ready state process is runable but temporarily stopped running to let another process run.<br />
* Terminated state: The process has finished execution.</p>
<p>A process in an operating system is represented by a data structure known as a process control block (PCB) or process descriptor. The PCB contains important information about the specific process including :<br />
* The current state of the process i.e., whether it is ready, running, waiting, or whatever.<br />
* Unique identification of the process in order to track &#8220;which is which&#8221; information.  * A pointer to parent process.<br />
* Similarly, a pointer to child process (if it exists).<br />
* The priority of process (a part of CPU scheduling information).<br />
* Pointers to locate memory of processes.<br />
* A register save area.<br />
* The processor it is running on.</p>
<div class="addthis_toolbox addthis_default_style " addthis:url='http://learnsoftwareprocesses.com/2009/08/26/overview-of-process/' addthis:title='Overview Of Process '  ><a class="addthis_button_facebook_like" fb:like:layout="button_count"></a><a class="addthis_button_tweet"></a><a class="addthis_button_google_plusone" g:plusone:size="medium"></a><a class="addthis_counter addthis_pill_style"></a></div>]]></content:encoded>
			<wfw:commentRss>http://learnsoftwareprocesses.com/2009/08/26/overview-of-process/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
		<item>
		<title>Database System Concepts &#8211; Data Model, Schemas and Database state</title>
		<link>http://learnsoftwareprocesses.com/2009/08/04/database-system-concepts-data-model-schemas-and-database-state/</link>
		<comments>http://learnsoftwareprocesses.com/2009/08/04/database-system-concepts-data-model-schemas-and-database-state/#comments</comments>
		<pubDate>Tue, 04 Aug 2009 03:05:29 +0000</pubDate>
		<dc:creator>ashish</dc:creator>
				<category><![CDATA[Data]]></category>
		<category><![CDATA[Data Model]]></category>
		<category><![CDATA[Databases]]></category>
		<category><![CDATA[Instance]]></category>
		<category><![CDATA[Model]]></category>
		<category><![CDATA[Schemas]]></category>
		<category><![CDATA[State]]></category>
		<category><![CDATA[Types]]></category>
		<category><![CDATA[Categories]]></category>
		<category><![CDATA[Conceptual data model]]></category>
		<category><![CDATA[Database state]]></category>
		<category><![CDATA[physical data model]]></category>
		<category><![CDATA[representational data model]]></category>

		<guid isPermaLink="false">http://learnsoftwareprocesses.com/?p=279</guid>
		<description><![CDATA[<p>A data model is a collection of concepts that can be used to describe the structure of a database. By structure of the database we mean the data types, relationships, and constraints that should hold on the data. Most data models also include a set of basic operations for specifying retrievals and updates on database.</p> [...]]]></description>
			<content:encoded><![CDATA[<p>A data model is a collection of concepts that can be used to describe the structure of a database. By structure of the database we mean the data types, relationships, and constraints that should hold on the data. Most data models also include a set of basic operations for specifying retrievals and updates on database.</p>
<p>Categories of Data Models:<br />
- High level or Conceptual data models : These models provide concepts that are close to the way many users perceive data. They use concepts such as entities, attributes, and relationships. An entity represents a real-world object or concept such as an employee or a project. An attribute represents property of interest that describes an entity such as employee&#8217;s salary or name. A relationship represents an interaction among the entities.<br />
- Representational data models : These models provides concept that may be understood by end users but that are not too far removed from the way data is organized within the computer. They are used most frequently in traditional commercial DBMSs and they include the widely used relational model as well as the network and hierarchical models. These models represent data by using record structures and hence are sometimes called record-based data models.<br />
- Low level or Physical data models : These models provide concepts that describe the details of how the data is stored in the computer by representing information such as record formats, record orderings, and access paths. An access path is a structure that makes the search for particular database records efficient.</p>
<p>Schemas:<br />
The description of a database in any data model is called the database schema which is specified during the database design and is not expected to change frequently. A displayed is called a schema diagram.</p>
<p><a onblur="try {parent.deselectBloggerImageGracefully();} catch(e) {}" href="http://2.bp.blogspot.com/_Ft_K4jmqJjk/SnaBHIGtBxI/AAAAAAAAANc/4y5ZxiTAHMQ/s1600-h/schema+diagram.gif"><img style="display:block; margin:0px auto 10px; text-align:center;cursor:pointer; cursor:hand;width: 377px; height: 212px;" src="http://2.bp.blogspot.com/_Ft_K4jmqJjk/SnaBHIGtBxI/AAAAAAAAANc/4y5ZxiTAHMQ/s400/schema+diagram.gif" border="0" alt="Schema Diagram" id="BLOGGER_PHOTO_ID_5365617965493192466" /></a><br />
A schema diagram displays only some aspects of a schema, such as names of record types and data items, and some types of constraints.</p>
<p>Database State or Iinstance: The actual data in a database changes every time data is inserted, deleted, or modified. The data in the database at a particular moment in time is called a database state or a snapshot. It is also called the current set of occurrences or instances in the database.</p>
<p>Distinguish between Database State and Database Schema:<br />
When a new database is defined, we specify its database schema only to the DBMS. At this point, the corresponding database state is empty state. The initial state of the database is got when the database is first populated or loaded with the initial data. From then on, every time an update operation is applied to the database, we get another database state.</p>
<div class="addthis_toolbox addthis_default_style " addthis:url='http://learnsoftwareprocesses.com/2009/08/04/database-system-concepts-data-model-schemas-and-database-state/' addthis:title='Database System Concepts &#8211; Data Model, Schemas and Database state '  ><a class="addthis_button_facebook_like" fb:like:layout="button_count"></a><a class="addthis_button_tweet"></a><a class="addthis_button_google_plusone" g:plusone:size="medium"></a><a class="addthis_counter addthis_pill_style"></a></div>]]></content:encoded>
			<wfw:commentRss>http://learnsoftwareprocesses.com/2009/08/04/database-system-concepts-data-model-schemas-and-database-state/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>

