<?xml version="1.0" encoding="iso-8859-1"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:content="http://purl.org/rss/1.0/modules/content/">

<channel>
<title>Practices - Web Developer Tutorials</title>
<link>http://www.devshed.com</link>
<!-- PubSubHubbub Discovery -->
<link rel="hub"  href="http://devshednet.superfeedr.com/" xmlns="http://www.w3.org/2005/Atom" />
<link rel="self" href="http://www.devshed.com/rss-feeds-18.xml" xmlns="http://www.w3.org/2005/Atom" />
<!-- End Of PubSubHubbub Discovery -->
<atom:link href="http://www.devshed.com/rss-feeds-18.xml" rel="self"/>
<description>Practices Tutorials at Dev Shed.  DevShed is a community focused on both beginner and advanced tutorials in Java, C, PHP, Python, MySQL and Ruby-on-rails...amongst others.</description>
<language>en-us</language>
<lastBuildDate>Thu, 23 May 2013 19:11:24 -0400</lastBuildDate>
<pubDate>Thu, 23 May 2013 19:11:24 -0400</pubDate>
<item><title>Calculating Development Project Costs</title>
<pubDate>Mon, 10 Sep 2012 09:01:20 -0400</pubDate>
<link>http://www.devshed.com/c/a/Practices/Calculating-Development-Project-Costs-70288/</link>
		<description><![CDATA[As a programmer or project manager, you may at some point need to calculate the man-hours or costs involved in a particular development project before going forward. This may seem like an overwhelming task, especially when you consider how often projects end up running behind schedule and over budget. To help you in this task, here are a few things you may want to keep in mind.]]></description>
		<content:encoded><![CDATA[As you might imagine, the topic of how to estimate the needs of a software project going forward comes up from time to time on Dev Shed's forums; here's a recent thread on the subject. One of our long-time members, dve83, contributed his expertise; I'm basing this article around his post. Before you go forward with planning your project, I'd suggest you look into extreme programming  practices. The idea behind this discipline of software development is to bring  the whole team together in the presence of simple practices, with enough feedback to enable the team to see where they are and to tun...]]></content:encoded>
<category>Practices</category>
<guid isPermaLink="true">http://www.devshed.com/c/a/Practices/Calculating-Development-Project-Costs-70288/</guid>
</item>
<item><title>More Techniques for Finding Things</title>
<pubDate>Thu, 17 Jul 2008 10:00:47 -0400</pubDate>
<link>http://www.devshed.com/c/a/Practices/More-Techniques-for-Finding-Things/</link>
		<description><![CDATA[In this second part of a two-part series that provides an overview of search techniques for the developer, you'll learn more about the challenges and trade-offs of various approaches. It is excerpted from chapter four of Beautiful Code: Leading Programmers Explain How They Think, written by Andy Oram and Greg Wilson (O'Reilly, 2007; ISBN: 0596510047). Copyright © 2007 O'Reilly Media, Inc. All rights reserved. Used with permission from the publisher. Available from booksellers or direct from O'Reilly Media.]]></description>
		<content:encoded><![CDATA[Problem: Who Fetched What, When?   Running a couple of quick scripts over the logfile data reveals that there are 12,600,064 instances of an article fetch coming from 2,345,571 different hosts. Suppose we are interested in who was fetching what, and when? An auditor, a police officer, or a marketing professional might be interested.  So, here's the problem: given a hostname, report what articles were fetched from that host, and when. The result is a list; if the list is empty, no articles were fetched.  We've already seen that a language's built-in hash or equivalent data structure gives the p...]]></content:encoded>
<category>Practices</category>
<guid isPermaLink="true">http://www.devshed.com/c/a/Practices/More-Techniques-for-Finding-Things/</guid>
</item>
<item><title>Finding Things</title>
<pubDate>Thu, 10 Jul 2008 10:30:49 -0400</pubDate>
<link>http://www.devshed.com/c/a/Practices/Finding-Things/</link>
		<description><![CDATA[Search, whether it's searching the web or the contents of your computer, presents the developer with a major challenge. This article, the first of two parts, provides an overview of several search techniques, and the trade-offs that go with them. It is excerpted from chapter four of Beautiful Code: Leading Programmers Explain How They Think, written by Andy Oram and Greg Wilson (O'Reilly, 2007; ISBN: 0596510047). Copyright © 2007 O'Reilly Media, Inc. All rights reserved. Used with permission from the publisher. Available from booksellers or direct from O'Reilly Media.]]></description>
		<content:encoded><![CDATA[COMPUTERS CAN COMPUTE, BUT THAT'S NOT WHAT PEOPLE USE THEM FOR, MOSTLY. Mostly, computers store and retrieve information. Retrieve implies find, and in the time since the advent of the Web, search has become a dominant application for people using computers.  As data volumes continue to grow-both absolutely, and relative to the number of people or computers or anything, really-search becomes an increasingly large part of the life of the programmer as well. A few applications lack the need to locate the right morsel in some information store, but very few.  The subject of search is one of the l...]]></content:encoded>
<category>Practices</category>
<guid isPermaLink="true">http://www.devshed.com/c/a/Practices/Finding-Things/</guid>
</item>
<item><title>Finishing the System`s Outlines</title>
<pubDate>Thu, 22 May 2008 10:00:47 -0400</pubDate>
<link>http://www.devshed.com/c/a/Practices/Finishing-the-Systems-Outlines/</link>
		<description><![CDATA[This second part of a two-part article completes our coverage of how to talk to a client so that you are both on the same page when designing a system and understanding what it will be required to do. It is excerpted from Prefactoring, written by Ken Pugh (O'Reilly; ISBN: 596008740). Copyright © 2007 O'Reilly Media, Inc. All rights reserved. Used with permission from the publisher. Available from booksellers or direct from O'Reilly Media.]]></description>
		<content:encoded><![CDATA[Clumping When Sam described his customers in detail, he mentioned that he needed to keep track of each customer's home address, including street, city, state, and Zip Code, as well as credit card billing address, including street, city, state, and Zip Code.  I asked him,  quot;Do both of those addresses contain the same information? quot;  He replied affirmatively.  I said,  quot;Then let's just describe the combination as an Address. That way, you don't have to keep mentioning all the parts unless there is something different about them. quot;   quot;OK, quot; he answered.  We clumped the dat...]]></content:encoded>
<category>Practices</category>
<guid isPermaLink="true">http://www.devshed.com/c/a/Practices/Finishing-the-Systems-Outlines/</guid>
</item>
<item><title>The System in So Many Words</title>
<pubDate>Thu, 15 May 2008 10:00:47 -0400</pubDate>
<link>http://www.devshed.com/c/a/Practices/The-System-in-So-Many-Words/</link>
		<description><![CDATA[This article will show you how to talk to a client so that you are both on the same page when designing a system and understanding what it will be required to do. It is excerpted from Prefactoring,   Written by Ken Pugh (O'Reilly;  ISBN: 596008740). Copyright © 2007 O'Reilly Media, Inc. All rights reserved. Used with permission from the publisher. Available from booksellers or direct from O'Reilly Media.]]></description>
		<content:encoded><![CDATA[WE MEET SAM, THE CLIENT, FOR WHOM WE ARE DEVELOPING A SYSTEM. Tim, a co-developer, and I interact with Sam to get an overall view of what he wants the system to do through use cases and prototypes. We work together to determine a common vocabulary to describe the system's requirements. Meet Sam  Systems are not developed in a vacuum. They are created to meet an organization's needs. The client for whom a system is developed is the source of the requirements for the system and is the final decider of whether a system meets those requirements. Sam, the client, represents a composite of clients f...]]></content:encoded>
<category>Practices</category>
<guid isPermaLink="true">http://www.devshed.com/c/a/Practices/The-System-in-So-Many-Words/</guid>
</item>
<item><title>Basic Data Types and Calculations</title>
<pubDate>Thu, 08 Sep 2005 10:00:01 -0400</pubDate>
<link>http://www.devshed.com/c/a/Practices/Basic-Data-Types-and-Calculations/</link>
		<description><![CDATA[This article looks at some of the basic data types that are built into C++. If you're learning how to use C++, you will want to keep reading, since you'll be using these data types in all of your programs. It is taken from chapter two of the book Beginning ANSI C++: The Complete Language, by Ivor Horton (Apress, 2004; ISBN: 1590592271).]]></description>
		<content:encoded><![CDATA[ IN THIS CHAPTER, you'll look at some of the basic data types that are built into C++ and that you're likely to use in all your programs. You'll also investigate how to carry out simple numerical computations. All of C++'s object-oriented capability is founded on the basic data types built into the language, because all the data types that you'll create are ultimately defined in terms of the basic types. It's therefore important to get a good grasp of using them. By the end of the chapter, you'll be able to write a simple C++ pro gram of the traditional form: input - process - output.  In this...]]></content:encoded>
<category>Practices</category>
<guid isPermaLink="true">http://www.devshed.com/c/a/Practices/Basic-Data-Types-and-Calculations/</guid>
</item>
<item><title>What`s the Address? Pointers</title>
<pubDate>Thu, 01 Sep 2005 10:00:00 -0400</pubDate>
<link>http://www.devshed.com/c/a/Practices/Whats-the-Address-Pointers/</link>
		<description><![CDATA[The name  pointer  describes the job of the item; a pointer  points  to another variable or constant. Some tasks in C++ are easier to do with pointers; others would be utterly impossible without pointers. This article discusses how to create and work with pointers in C++. It is taken from chapter 11 of the book C++ Demystified, written by Jeff Kent (McGraw-Hill/Osborne, 2004; ISBN: 0072253703).]]></description>
		<content:encoded><![CDATA[ What's the Address? Pointers  My parents told me when I was a child that it was not polite to point. However, each semester I teach my computer programming students how to point. No, I am not trying to promote rude behavior. Rather, I am teaching my students about pointers, which  point  to another variable or constant.  You yourself may have acted as a pointer in the past. Have you ever been asked where someone lives? If that house was nearby, you may have pointed it out.  The pointer performs a similar function. A pointer points to another variable or constant. Of course, the pointer does n...]]></content:encoded>
<category>Practices</category>
<guid isPermaLink="true">http://www.devshed.com/c/a/Practices/Whats-the-Address-Pointers/</guid>
</item>
<item><title>Design with ArgoUML</title>
<pubDate>Thu, 25 Aug 2005 10:00:00 -0400</pubDate>
<link>http://www.devshed.com/c/a/Practices/Design-with-ArgoUML/</link>
		<description><![CDATA[This article provides an overview of the practical application of object-oriented analysis and design (OOAD) design concepts and the Unified Modeling Language (UML). It is taken from chapter two of the book Enterprise Java Development on a Budget, written by Brian Sam-Bodden and Christopher M. Judd (Apress, 2004; ISBN: 1590591259)]]></description>
		<content:encoded><![CDATA[ Luck is the residue of design.  JAVA HAS FOUND a niche in the server side of contemporary distributed computing, in which the most prevalent service model is the browser-based application or web application. The rise of the Internet as a global network for business has given enterprise computing its greatest weapon and also its greatest challenge. More power and possibilities mean more challenges and complexity. Software engineers have realized that without a solid architecture and some semblance of a process that emphasizes analysis and design, a project's failure is all but imminent. Keepin...]]></content:encoded>
<category>Practices</category>
<guid isPermaLink="true">http://www.devshed.com/c/a/Practices/Design-with-ArgoUML/</guid>
</item>
<item><title>Pragmatic Guidelines: Diagrams That Work</title>
<pubDate>Thu, 11 Aug 2005 10:00:01 -0400</pubDate>
<link>http://www.devshed.com/c/a/Practices/Pragmatic-Guidelines-Diagrams-That-Work/</link>
		<description><![CDATA[Unified Modeling Language is about communication. But in order for communication to work, it must be useful. How do you make sure that you don't sweat over a set of UML diagrams only to discover that no one else can understand them? Fortunately, there are guidelines, discussed in this article, to help prevent this catastrophe. This article is excerpted from chapter three of the book UML Applied: A .NET Perspective, written by Martin L. Shoemaker (Apress, 2004; ISBN: 1590590872).]]></description>
		<content:encoded><![CDATA[IN THE LAST CHAPTER, we spent a long time working through the process of Five-Step UML, and looking at all of the new UML notation which that entailed. But in this chapter, we're going to take a quick break from learning all the formal rules and all the step-by-step instructions on how to use UML as part of a modeling process. Instead, I'm going to present a set of pragmatic guidelines that will help you stay on the right track during your development work. By this point, you may already be tired of hearing me say that UML is about communication. But that's easy to say, and much harder to do. ...]]></content:encoded>
<category>Practices</category>
<guid isPermaLink="true">http://www.devshed.com/c/a/Practices/Pragmatic-Guidelines-Diagrams-That-Work/</guid>
</item>
<item><title>Five-Step UML: OOAD for Short Attention Spans - Design, Repeat</title>
<pubDate>Thu, 04 Aug 2005 10:00:01 -0400</pubDate>
<link>http://www.devshed.com/c/a/Practices/FiveStep-UML-OOAD-for-Short-Attention-Spans-Design-Repeat/</link>
		<description><![CDATA[This article continues our introduction  to the concepts of Five-Step UML, working from beginning to end. It introduces UML notation and goes into great detail. This article covers the final two steps of a five-step process. It is  from chapter 2 of UML Applied A .NET Perspective, written by Martin L. Shoemaker (Apress, 2004; ISBN: 1590590872).]]></description>
		<content:encoded><![CDATA[ Step 4: Design Show the relations among the elements with Component Diagrams. Add other diagrams where they shed light on the components.  In this step, you'll assign the interfaces and user interfaces discovered in Step 3 to components, and then show the relationships between components and interfaces in Component Diagrams. You'll try to identify existing components and interfaces that can be reused, along with new components that will support the new interfaces. UML Notation  A Component Diagram is a way of depicting the executables and other components that form the logical architecture of...]]></content:encoded>
<category>Practices</category>
<guid isPermaLink="true">http://www.devshed.com/c/a/Practices/FiveStep-UML-OOAD-for-Short-Attention-Spans-Design-Repeat/</guid>
</item>
<item><title>Five-Step UML: OOAD for Short Attention Spans - Define, Refine, Assign</title>
<pubDate>Thu, 28 Jul 2005 10:00:00 -0400</pubDate>
<link>http://www.devshed.com/c/a/Practices/FiveStep-UML-OOAD-for-Short-Attention-Spans-Define-Refine-Assign/</link>
		<description><![CDATA[This article introduces the concepts of Five-Step UML, working from beginning to end. It introduces UML notation and goes into great detail. This article covers the first three of five steps. It is  from chapter 2 of UML Applied A .NET Perspective, written by Martin L. Shoemaker (Apress, 2004; ISBN: 1590590872).]]></description>
		<content:encoded><![CDATA[ IN THIS CHAPTER, I'll introduce you to Five-Step UML. We'll work through the whole process from beginning to end, and along the way, I'll be introducing all the UML notation that you'll need to understand the relevant diagrams. I'll also show you how the whole thing works from the point of view of .NET development. By way of examples, I'll be using lots of diagrams from the Kennel Management System case study, which was introduced at the end of the last chapter. I'm not going to show you everything in exhaustive detail at this stage, however, because we'll be examining that case study more sl...]]></content:encoded>
<category>Practices</category>
<guid isPermaLink="true">http://www.devshed.com/c/a/Practices/FiveStep-UML-OOAD-for-Short-Attention-Spans-Define-Refine-Assign/</guid>
</item>
<item><title>Introducing UML: Object-Oriented Analysis and Design</title>
<pubDate>Thu, 21 Jul 2005 10:00:01 -0400</pubDate>
<link>http://www.devshed.com/c/a/Practices/Introducing-UMLObjectOriented-Analysis-and-Design/</link>
		<description><![CDATA[The purpose of UML, or Unified Modeling Language, is communication; to be specific, it is to provide a comprehensive notation for communicating the requirements, architecture, implementation, deployment, and states of a system. This article will offer an overview of Object Oriented Analysis and Design, focusing in on the three most important concepts it encompasses: objects, analysis, and design. It is excerpted from the book UML Applied: A .Net Perspective, by Martin Shoemaker (Apress, 2004; ISBN: 1590590872).]]></description>
		<content:encoded><![CDATA[  TIP For those who are impatient . . . If you already understand objects, you don't need convincing that UML is a great thing, and you just want to start learning the UML notation right away, skip ahead to Chapter 2.    IN UML, the L is for language, one of the definitions of which is  any means of communicating,  according to the Merriam-Webster Dictionary. That is the single overriding purpose of UML, or the Unified Modeling Language: to provide a comprehensive notation for communicating the requirements, architecture, implementation, deployment, and states of a system.  UML communicates th...]]></content:encoded>
<category>Practices</category>
<guid isPermaLink="true">http://www.devshed.com/c/a/Practices/Introducing-UMLObjectOriented-Analysis-and-Design/</guid>
</item>
<item><title>Class and Object Diagrams</title>
<pubDate>Thu, 14 Jul 2005 10:00:01 -0400</pubDate>
<link>http://www.devshed.com/c/a/Practices/Class-and-Object-Diagrams/</link>
		<description><![CDATA[This article will teach you about UML structural diagrams, used to help you keep track of the structure of your models. It was excerpted from chapter three of Fast Track UML 2.0, written by Kendall Scott (Apress, 2004; ISBN: 1590593200).]]></description>
		<content:encoded><![CDATA[THIS CHAPTER FOCUSES ON THE UML STRUCTURAL diagrams that you use to capture the fundamental structure of your models at the class and object levels. Class Diagrams A class diagram focuses on a set of classes (see Chapter 1) and the structural relationships among them (see Chapter 2). It may also show interfaces (see the section  Interfaces, Ports, and Connectors  in Chapter 1).  The UML allows you to draw class diagrams that have varying levels of detail. One useful way to classify these diagrams involves three stages of a typical software development project: requirements, analysis, and desig...]]></content:encoded>
<category>Practices</category>
<guid isPermaLink="true">http://www.devshed.com/c/a/Practices/Class-and-Object-Diagrams/</guid>
</item>
<item><title>Class Relationships</title>
<pubDate>Thu, 16 Jun 2005 10:00:00 -0400</pubDate>
<link>http://www.devshed.com/c/a/Practices/Class-Relationships/</link>
		<description><![CDATA[With the UML, it is the relationships between classes that provide structure to what you are creating. This article explains how to use the UML to illustrate various kinds of class relationships. It is taken from chapter two of Fast Track UML 2.0 written by Kendall Scott (Apress, 2004; ISBN: 1590593200).]]></description>
		<content:encoded><![CDATA[Class Relationships  Classes, by themselves, aren't particularly useful. It's the relationships among classes that provide the foundation for the structure of a new system. The following sections explore how you use the UML to illustrate various kinds of class relationships. Associations An association is a simple structural connection between classes.  You might think of an association as representing a  peer  relationship. (You look at other kinds of relationships that involve  parents  and  children,  and  parts  and  the whole,  later in the chapter.) Instances of classes involved in an as...]]></content:encoded>
<category>Practices</category>
<guid isPermaLink="true">http://www.devshed.com/c/a/Practices/Class-Relationships/</guid>
</item>
<item><title>Classes</title>
<pubDate>Wed, 27 Apr 2005 10:00:00 -0400</pubDate>
<link>http://www.devshed.com/c/a/Practices/Classes/</link>
		<description><![CDATA[In this article you will learn about the Unified Modeling Language (UML) by examining basic modeling of things and concepts in the real world. It is excerpted from the book Fast Track UML 2.0, written by Kendall Scott (Apress, 2004; ISBN: 1590593200)]]></description>
		<content:encoded><![CDATA[ LET'S BEGIN OUR LOOK AT THE DETAILS of the Unified Modeling Language (UML) by exploring how we do basic modeling of things and concepts in the real world. Classes and Objects A class is a collection of things or concepts that have the same characteristics. Each of these things or concepts is called an object.  An object that belongs to a particular class is often referred to as an instance of that class. You can think of a class as being an abstraction and an object as being the concrete manifestation of that abstraction.  The class is the most fundamental construct within the UML. Reasons wh...]]></content:encoded>
<category>Practices</category>
<guid isPermaLink="true">http://www.devshed.com/c/a/Practices/Classes/</guid>
</item>
</channel>
</rss>
