<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"><channel><description></description><title>What Ralph Knows About Software Development</title><generator>Tumblr (3.0; @ralphpoole)</generator><link>http://ralphpoole.tumblr.com/</link><item><title>Web Design References: Navigation</title><description>&lt;a href="http://www.d.umn.edu/itss/support/Training/Online/webdesign/navigation.html"&gt;Web Design References: Navigation&lt;/a&gt;: &lt;p&gt;This site provides a great resource for Web Design.  It publishes links to content that is essential reference for people building sites.&lt;/p&gt;</description><link>http://ralphpoole.tumblr.com/post/95779411</link><guid>http://ralphpoole.tumblr.com/post/95779411</guid><pubDate>Mon, 13 Apr 2009 12:13:51 -0400</pubDate></item><item><title>	SoYouKnow </title><description>&lt;a href="http://www.soyouknow.net/"&gt;	SoYouKnow &lt;/a&gt;: &lt;p&gt;When it comes down to it, if you want to learn SharePoint development it is going to take work, you are going to get frustrated, it won’t make sense and you are going to break things.  Accept it… embrace it… back up often.  Welcome to the stress filled world of SharePoint development.&lt;/p&gt;</description><link>http://ralphpoole.tumblr.com/post/92077008</link><guid>http://ralphpoole.tumblr.com/post/92077008</guid><pubDate>Wed, 01 Apr 2009 20:25:00 -0400</pubDate></item><item><title>Enterprise Architecture, Software Architecture, Architects, and Architecting</title><description>&lt;a href="http://www.bredemeyer.com/"&gt;Enterprise Architecture, Software Architecture, Architects, and Architecting&lt;/a&gt;</description><link>http://ralphpoole.tumblr.com/post/81807276</link><guid>http://ralphpoole.tumblr.com/post/81807276</guid><pubDate>Thu, 26 Feb 2009 16:48:55 -0500</pubDate></item><item><title>SEO and Social Media Marketing: Part IV - A B2B Marketing How-to</title><description>&lt;a href="http://www.engageinpr.com/2009/02/24/seo-social-media-pr/"&gt;SEO and Social Media Marketing: Part IV - A B2B Marketing How-to&lt;/a&gt;: &lt;p&gt;These are very specific tips obviously, but they go to show the little things that you can do when writing your news releases, allowing your information to be indexed for a much longer time. Additionally you must also take into account much of the information we wrote about in Parts I, II &amp; III around hyperlinking key phrases within your news release. This is important for two reasons. First for when you put the news release up on your corporate site it is already optimized, but also when you put it out over the wire it will provide you with a SEO boost…that is if you are using the right wire.&lt;/p&gt;</description><link>http://ralphpoole.tumblr.com/post/81128395</link><guid>http://ralphpoole.tumblr.com/post/81128395</guid><pubDate>Tue, 24 Feb 2009 12:39:07 -0500</pubDate></item><item><title>Introduction to Medium-Fidelity Prototypes |</title><description>&lt;a href="http://www.inovdesigns.com/prototypes.php"&gt;Introduction to Medium-Fidelity Prototypes |&lt;/a&gt;: &lt;p&gt;Medium Fidelity Prototypes  are used to develop an information architecture.  It provides a platform to conduct meaningful user tests to evaluate complex functionality and to help determine user requirements.&lt;/p&gt;</description><link>http://ralphpoole.tumblr.com/post/81120151</link><guid>http://ralphpoole.tumblr.com/post/81120151</guid><pubDate>Tue, 24 Feb 2009 12:06:13 -0500</pubDate></item><item><title>Interface | matters: "Low-Fidelity" Prototyping With Electronic Tools</title><description>&lt;a href="http://interfacematters.com/2007/06/low-fidelity-prototyping-with.html"&gt;Interface | matters: "Low-Fidelity" Prototyping With Electronic Tools&lt;/a&gt;: &lt;p&gt;This article describes the importance of developing a low fidelity prototype of a process.  This can be done collaboratively at a white board, or it can be done electronically.&lt;/p&gt;</description><link>http://ralphpoole.tumblr.com/post/81119212</link><guid>http://ralphpoole.tumblr.com/post/81119212</guid><pubDate>Tue, 24 Feb 2009 12:02:40 -0500</pubDate></item><item><title>Agile Project Management - PM Hut</title><description>&lt;a href="http://www.pmhut.com/category/agile-project-management/"&gt;Agile Project Management - PM Hut&lt;/a&gt;: &lt;p&gt;Great blog on project management!  It looks at lean and agile approaches to software development.&lt;/p&gt;</description><link>http://ralphpoole.tumblr.com/post/78057067</link><guid>http://ralphpoole.tumblr.com/post/78057067</guid><pubDate>Fri, 13 Feb 2009 12:01:37 -0500</pubDate></item><item><title>Introducing the new Web Design from Scratch Blog for 2009</title><description>&lt;a href="http://www.webdesignfromscratch.com/blog/index.php"&gt;Introducing the new Web Design from Scratch Blog for 2009&lt;/a&gt;: &lt;p&gt;he grand goal of the blog is to help “Save the Pixel” to become a rallying cry for the movement for simplicity, not just a book title. I want the fundamental principles of “Save the Pixel” to become part of the accepted wisdom of this generation of designers.&lt;/p&gt;

&lt;p&gt;My more immediate goal is to publish a stream of information that reflects and reports on current best practice in web design, in a way that’s accessible to the whole community - whether you’re an interested bystander, a budding designer, or a seasoned professional. I want the Web Design from Scratch blog to be just your cup of tea, something fresh and fun that you look forward to each week.&lt;/p&gt;</description><link>http://ralphpoole.tumblr.com/post/71049026</link><guid>http://ralphpoole.tumblr.com/post/71049026</guid><pubDate>Fri, 16 Jan 2009 22:18:47 -0500</pubDate></item><item><title>Movable Type Developer's Toolbox | Developer's Toolbox | Smashing Magazine</title><description>&lt;a href="http://www.smashingmagazine.com/2008/12/08/movable-type-developers-toolbox/"&gt;Movable Type Developer's Toolbox | Developer's Toolbox | Smashing Magazine&lt;/a&gt;: &lt;p&gt;I’ve linked to this website before.  I am just astounded at how good their stuff is; lots of interesting, usable information that I can apply right away.  And even though Movable Type gives me fits, I eat this stuff up!&lt;/p&gt;</description><link>http://ralphpoole.tumblr.com/post/71040397</link><guid>http://ralphpoole.tumblr.com/post/71040397</guid><pubDate>Fri, 16 Jan 2009 21:23:47 -0500</pubDate></item><item><title>HTML Reference</title><description>&lt;a href="http://reference.sitepoint.com/html"&gt;HTML Reference&lt;/a&gt;: &lt;p&gt;Confused about when to use HTML and when to use XHTML? Want to know what the syntax differences are between the two? Do doctypes and DTDs leave you all discombobulated? Or perhaps you’d simply like to understand the basic structure of a web page?&lt;/p&gt;</description><link>http://ralphpoole.tumblr.com/post/68342838</link><guid>http://ralphpoole.tumblr.com/post/68342838</guid><pubDate>Sun, 04 Jan 2009 15:42:48 -0500</pubDate></item><item><title>15 Useful Project Management Tools | Developer's Toolbox | Smashing Magazine</title><description>&lt;a href="http://www.smashingmagazine.com/2008/11/13/15-useful-project-management-tools/"&gt;15 Useful Project Management Tools | Developer's Toolbox | Smashing Magazine&lt;/a&gt;: &lt;p&gt;There is a huge variety of project management applications out there. Most are general purpose apps, not aimed at any one industry. But there is a growing number of project management apps aimed specifically at one industry or another. Applications geared to creative types are becoming more readily available, and some of the offerings are really quite good.&lt;/p&gt;</description><link>http://ralphpoole.tumblr.com/post/59613512</link><guid>http://ralphpoole.tumblr.com/post/59613512</guid><pubDate>Fri, 14 Nov 2008 00:23:06 -0500</pubDate></item><item><title>Template: Information Architecture Plan (eGovernment Resource Centre)</title><description>&lt;a href="http://www.egov.vic.gov.au/index.php?env=-innews/detail:m2552-1-1-8-s-0:n-1503-1-0--"&gt;Template: Information Architecture Plan (eGovernment Resource Centre)&lt;/a&gt;: &lt;p&gt;Helpful decomposition of IA deliverables&lt;/p&gt;</description><link>http://ralphpoole.tumblr.com/post/58252628</link><guid>http://ralphpoole.tumblr.com/post/58252628</guid><pubDate>Thu, 06 Nov 2008 00:16:14 -0500</pubDate></item><item><title>Usability and Information Architecture</title><description>&lt;a href="http://www.sitepoint.com/subcat/usability"&gt;Usability and Information Architecture&lt;/a&gt;: &lt;p&gt;Design and Layout : Usability and Information Architecture.  From Boxes and Arrows a list of Usability articles&lt;/p&gt;</description><link>http://ralphpoole.tumblr.com/post/58247270</link><guid>http://ralphpoole.tumblr.com/post/58247270</guid><pubDate>Wed, 05 Nov 2008 23:30:11 -0500</pubDate></item><item><title>Boxes and Arrows: Defining Information Architecture Deliverables [Usability and Information Architecture]</title><description>&lt;a href="http://www.sitepoint.com/article/architecture-deliverables/"&gt;Boxes and Arrows: Defining Information Architecture Deliverables [Usability and Information Architecture]&lt;/a&gt;: &lt;p&gt;This article is a bit old now but it is still a really good description of the deliverables required when doing an information architecture.&lt;/p&gt;</description><link>http://ralphpoole.tumblr.com/post/58247035</link><guid>http://ralphpoole.tumblr.com/post/58247035</guid><pubDate>Wed, 05 Nov 2008 23:27:33 -0500</pubDate></item><item><title>Define ITIL for the IT layman | The IT Skeptic</title><description>&lt;a href="http://www.itskeptic.org/node/460"&gt;Define ITIL for the IT layman | The IT Skeptic&lt;/a&gt;: &lt;p&gt;You don’t need ITIL to run a static environment where nothing goes wrong and nothing changes and nothing grows. ITIL has nothing to do with technology, nor can it be implemented with technology. ITIL is about how an organisation and the people within it respond to planned and unexpected variations in the environment, from outages to changes to growth. ITIL defines human behaviour.&lt;/p&gt;

&lt;p&gt;Every organisation needs the processes ITIL describes. Every organisation already has them. ITIL is just one way of defining a standard approach to performing them. You may not need ITIL but every IT shop needs to be doing what ITIL describes, one way or another.&lt;/p&gt;</description><link>http://ralphpoole.tumblr.com/post/55889995</link><guid>http://ralphpoole.tumblr.com/post/55889995</guid><pubDate>Wed, 22 Oct 2008 23:02:00 -0400</pubDate></item><item><title>Wapedia - Wiki: Microsoft Operations Framework</title><description>&lt;a href="http://wapedia.mobi/en/Microsoft_Operations_Framework#4."&gt;Wapedia - Wiki: Microsoft Operations Framework&lt;/a&gt;: &lt;p&gt;Microsoft Operations Framework (MOF) 4.0 is a series of guides aimed at helping information technology (IT) professionals establish and implement reliable, cost-effective services.  It describes a set of service management frameworks for the entire software development life cycle.&lt;/p&gt;</description><link>http://ralphpoole.tumblr.com/post/55672267</link><guid>http://ralphpoole.tumblr.com/post/55672267</guid><pubDate>Tue, 21 Oct 2008 17:25:00 -0400</pubDate></item><item><title>	Stack Overflow</title><description>&lt;a href="http://stackoverflow.com/"&gt;	Stack Overflow&lt;/a&gt;: &lt;p&gt;This is a website that provides lots of great questions and answers about software development.&lt;/p&gt;</description><link>http://ralphpoole.tumblr.com/post/55326446</link><guid>http://ralphpoole.tumblr.com/post/55326446</guid><pubDate>Sun, 19 Oct 2008 15:52:00 -0400</pubDate></item><item><title>Wire Frame Your Site [Design Practice]</title><description>&lt;a href="http://www.stumbleupon.com/toolbar/#topic=Graphic Design&amp;url=http%253A%252F%252Fwww.sitepoint.com%252Farticle%252Fwire-frame-your-site"&gt;Wire Frame Your Site [Design Practice]&lt;/a&gt;: &lt;p&gt;Implementing a few simple steps in carefully planning your site, before you create any graphics, can eliminate a lot of headaches. One method that I find very useful is the creation of a wire frame or “white site” model. I’ll outline the benefits and process of wire framing in this article.&lt;/p&gt;</description><link>http://ralphpoole.tumblr.com/post/55235662</link><guid>http://ralphpoole.tumblr.com/post/55235662</guid><pubDate>Sat, 18 Oct 2008 23:48:45 -0400</pubDate></item><item><title>Writing Software Requirements Specifications | A Technical Communication Community</title><description>&lt;a href="http://www.techwr-l.com/techwhirl/magazine/writing/softwarerequirementspecs.html"&gt;Writing Software Requirements Specifications | A Technical Communication Community&lt;/a&gt;: &lt;p&gt;For technical writers who haven’t had the experience of designing software requirements specifications (SRSs, also known as software functional specifications or system specifications) templates or even writing SRSs, they might assume that being given the opportunity to do so is either a reward or punishment for something they did (or failed to do) on a previous project. Actually, SRSs are ideal projects for technical writers to be involved with because they lay out the foundation for the development of a new product and for the types of user documentation and media that will be required later in the project development life cycle. It also doesn’t hurt that you’d be playing a visible role in contributing to the success of the project.&lt;/p&gt;

&lt;p&gt;This article will describe what an SRS is and why it’s important, discuss how and why technical writers should be involved with them, and discuss the critical elements for writing an SRS. Although this article does not attempt to address all aspects of developing SRSs, it aims to help you determine the scope for such a project, to provide some guidelines for writing SRSs, and to provide additional resources. Hopefully with this information, you’ll not be asking, “Why me?” but proclaiming “Why not me?”&lt;/p&gt;</description><link>http://ralphpoole.tumblr.com/post/54862918</link><guid>http://ralphpoole.tumblr.com/post/54862918</guid><pubDate>Thu, 16 Oct 2008 11:16:20 -0400</pubDate></item><item><title>ArsDigita Systems Journal: &#13;
Requirements Gathering for Application Design</title><description>&lt;a href="http://www.eveandersson.com/arsdigita/asj/requirements/"&gt;ArsDigita Systems Journal: &#13;
Requirements Gathering for Application Design&lt;/a&gt;: &lt;p&gt;Motivation&lt;/p&gt;

&lt;p&gt;A solution delivery team and a client agree to develop a software application. Together they agree on scope, specifications, timeline, and price. The delivery team begins coding against the specifications and at the initial milestone date meets with the client to review functionality. The client’s reaction upon seeing the functionality - “This is not what we were expecting!”&lt;br/&gt;
Even with a seemingly well-defined set of functional requirements, web service developers and customers often have different interpretations for how requirements translate into applications. But regardless of why or how these differences surface, the customer expects the development team to be accountable and to meet predefined project timelines and budgets. The outcome is solutions that are delivered late and result in significant incremental costs to the delivery team (e.g. additional development resources are needed, developers are overworked, morale suffers, other projects are neglected). Often the original project timeline is compromised and customers are generally unhappy.&lt;/p&gt;

&lt;p&gt;With dot.com type clients, these risks are real but manageable. With larger, more established clients (e.g., Fortune 500), these risks can result in very public and damaging failures. As web service companies continue to grow and extend their customer bases, success will be largely predicated on how quickly and comprehensively they can get to know their customers and understand their needs.&lt;/p&gt;</description><link>http://ralphpoole.tumblr.com/post/54738981</link><guid>http://ralphpoole.tumblr.com/post/54738981</guid><pubDate>Wed, 15 Oct 2008 17:23:22 -0400</pubDate></item></channel></rss>
