<?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>The discovery blog &#187; Liam Sheerin</title>
	<atom:link href="http://blogs.semantico.com/discovery-blog/author/liam-sheerin/feed/" rel="self" type="application/rss+xml" />
	<link>http://blogs.semantico.com/discovery-blog</link>
	<description>Semantico looks at online publishing</description>
	<lastBuildDate>Thu, 02 Sep 2010 10:22:31 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.2</generator>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<image>
			<title>The discovery blog</title>
			<url>http://blogs.semantico.com/discovery-blog/wp-content/uploads/2008/11/logo64.png</url>
			<link>http://blogs.semantico.com/discovery-blog</link>
			<width>64</width>
			<height>64</height>
			<description>Semantico looks at online publishing</description>
		</image>		<item>
		<title>Semantico creates Dictionarium app for iPhone and iPad</title>
		<link>http://blogs.semantico.com/discovery-blog/2010/09/semantico-creates-dictionarium-app-for-iphone-and-ipad/</link>
		<comments>http://blogs.semantico.com/discovery-blog/2010/09/semantico-creates-dictionarium-app-for-iphone-and-ipad/#comments</comments>
		<pubDate>Wed, 01 Sep 2010 11:48:21 +0000</pubDate>
		<dc:creator>Liam Sheerin</dc:creator>
				<category><![CDATA[Mobile]]></category>
		<category><![CDATA[Technology]]></category>

		<guid isPermaLink="false">http://blogs.semantico.com/discovery-blog/?p=1793</guid>
		<description><![CDATA[Semantico&#8217;s Dictionarium app is available for download from the app store now (short link at http://bit.ly/dictionarium)
We&#8217;re really pleased with how quickly we managed to get this live in the app store. The app was approved on first submission &#8211; a testament to our internal QA.
Creating a dictionary has given us the perfect opportunity to refine [...]]]></description>
			<content:encoded><![CDATA[<div id="attachment_1808" class="wp-caption alignright" style="width: 210px"><a href="http://blogs.semantico.com/discovery-blog/wp-content/uploads/2010/09/Dictionarium-screenshot-small.png"><img class="size-full wp-image-1808  " style="border: 1px solid black;" title="Dictionarium screenshot" src="http://blogs.semantico.com/discovery-blog/wp-content/uploads/2010/09/Dictionarium-screenshot-small.png" alt="Screenshot from Semantico's Dictionarium app" width="200" height="289" /></a><p class="wp-caption-text">Screenshot from Semantico&#39;s Dictionarium app</p></div>
<p>Semantico&#8217;s Dictionarium app is available for <a href="http://bit.ly/dictionarium">download from the app store now</a> (short link at <a href="http://bit.ly/dictionarium">http://bit.ly/dictionarium</a>)</p>
<p>We&#8217;re really pleased with how quickly we managed to get this live in the app store. The app was approved on first submission &#8211; a testament to our internal QA.</p>
<p>Creating a dictionary has given us the perfect opportunity to refine a number of important concepts we use when developing mobile apps.</p>
<p>Throughout the design process we&#8217;ve taken care to optimise the display for both the iPhone and the new iPad devices. Delivering an app for both devices is not only essential for publishers, who don&#8217;t want to develop the same content twice, but also for end users who don&#8217;t want the complication of downloading different apps in order to access the same content.<br />
<span id="more-1793"></span><br />
We&#8217;ve built the app to take us through some of the core concepts that publishers will need when taking their content to mobile devices, whatever the subject matter. The essential functionality of Dictionarium is that of a search engine with an integrated e-content reader. Text with hyperlinks allows the user to navigate through the the content and jump from one concept to another.</p>
<p>Semantico&#8217;s bespoke publishing platforms deal with large amounts of complex information: putting together the dictionary has allowed us to create and deliver an app with a large data set behind it of 107,757 headwords and 123,742 definitions.</p>
<p>Data compression and application speed optimisations are essential to create a great end user experience and an app that publishers can be proud of. By compressing the database we&#8217;ve halved the size of the app from 105MB to 51MB.</p>
<p>The Dictionary is designed so that the main way users find the information they need is through search. Search functionality is important for all online publications. Users expect to be able to find the information they want through keyword searching at the very least, and there&#8217;s been no problem with implementing this in the iPhone / iPad environment.</p>
<p>After a successful project it&#8217;s pleasing to have had 2,000 downloads in the first week of the app going live. Take a look at the work we&#8217;ve done – and make it 3,000! <a href="http://bit.ly/dictionarium">http://bit.ly/dictionarium</a></p>
]]></content:encoded>
			<wfw:commentRss>http://blogs.semantico.com/discovery-blog/2010/09/semantico-creates-dictionarium-app-for-iphone-and-ipad/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Search Engine Optimisation for Online Publishing</title>
		<link>http://blogs.semantico.com/discovery-blog/2009/11/search-engine-optimisation-for-online-publishing/</link>
		<comments>http://blogs.semantico.com/discovery-blog/2009/11/search-engine-optimisation-for-online-publishing/#comments</comments>
		<pubDate>Mon, 09 Nov 2009 16:27:04 +0000</pubDate>
		<dc:creator>Liam Sheerin</dc:creator>
				<category><![CDATA[Information Architecture]]></category>
		<category><![CDATA[Online Publishing Market]]></category>
		<category><![CDATA[Search]]></category>

		<guid isPermaLink="false">http://blogs.semantico.com/discovery-blog/?p=733</guid>
		<description><![CDATA[Search Engine Optimisation is a crucial part of any web strategy. Optimisation techniques involve helping search engines to accurately read and index the information on your site and deliver it to potential users through search results. The best techniques do this while with no impact on the user&#8217;s experience of the site. Here&#8217;s a review [...]]]></description>
			<content:encoded><![CDATA[<p>Search Engine Optimisation is a crucial part of any web strategy. Optimisation techniques involve helping search engines to accurately read and index the information on your site and deliver it to potential users through search results. The best techniques do this while with no impact on the user&#8217;s experience of the site. Here&#8217;s a review of the first steps on any SEO journey.<br />
<span id="more-733"></span></p>
<h2>1. Site Copy</h2>
<p>Copy has a direct impact on search engine optimisation as it provides the crawlers with meaningful semantic information about the site. The book content of any publishing site will contain excellent copy  but marketing and home page material should be carefully considered as this is often where crawlers, users and off-site links find themselves first. The number of keywords per site should be limited to three or four and these should be added to the content in such a way that the content remains natural and readable.</p>
<p>Particular attention should be paid to drafting text for hyperlinks. This is because the words that point to a particular page are heavily weighted by Google when determining keywords for that particular page. Never use phrases like &#8220;Click <em>here</em> for our contact form&#8221; (for example); instead use words that describe the page you&#8217;re linking to by thinking of what a user would search for if they were looking for that page. In our example this might be &#8220;Contact us now using our <em>contact form</em>&#8220;.</p>
<h2>2. Incoming Links</h2>
<p>Google rates a pages relevance using an algorithm called PageRank which is calculated based on the number and relevancy of links pointing to the site. The concept is that each link represents a vote of confidence for your site. But the votes are not equal, links from pages with a high PageRank are worth more. The PageRank of any site is shown on the <a title="Google Toolbar" href="http://toolbar.google.com">Google Toolbar</a>, which you can download from Google. Wikipedia have a good explanation of the <a title="Wikipedia article on the PageRank algorithm" href="http://en.wikipedia.org/wiki/PageRank" target="_blank">PageRank alogorithm</a>.</p>
<h2>3. Google Webmaster tools</h2>
<p><a title="Google Webmaster Tools" href="http://www.google.co.uk/webmasters/" target="_blank">Google Webmaster Tools</a> offers a comprehensive selection of tools for configuring a site for improved search results on Google. The main offering is the ability to submit an XML sitemap that improves the crawl across the site making it easier to control what pages are being indexed. The use of XML sitemaps will improve discoverability of the content for any site. In addition to this, is the ability to see when crawls have taken place and when they are next scheduled. This is of particular importance on each content update to ensure that the most recent updates have been picked up. Google Webmaster Tools also provides:</p>
<ul>
<li>A top search queries feature, where information about user search queries that have returned pages from your site are shown.</li>
<li>An interface for quickly finding all links to a site, allowing incoming links to be tracked.</li>
<li>Keywords and their frequency within the site.</li>
<li>Internal links.</li>
</ul>
<h2>4. Google Analytics</h2>
<p><a title="Google Analytics" href="http://www.google.com/analytics/" target="_blank">Google Analytics</a> offers further integration with Google search as the script that enables the tracking of the site provides constant activity feedback back to Google. Google Analytics should be used to determine where users are coming from and where users are landing. This information in itself will not help search ranking and discoverability, but it will provide metrics with which to measure the progress of any search engine optimisation activity. There are other analytics packages, such as <a title="Yahoo! Web Analytics" href="http://web.analytics.yahoo.com/">Yahoo! Web Analytics</a> (which provides real-time statistics), but Google Analytics has been recommended as it is the leading search provider and integrates well with other Google tools.</p>
<h2>4. URL structure</h2>
<p>Have a look at many complex publishing sites and you might notice that there are no PageRanks on many of the deeper linked pages within the sites. This is most likely due to Google&#8217;s crawlers not reading complex page URLs as these pages are often less meaningfully marked up and are the result of a a query.  For more details you can read <a title="Google article on meaningful URL markup" href="http://www.google.com/support/webmasters/bin/answer.py?hl=en&amp;answer=76329" target="_blank">Google&#8217;s explanation of this behaviour</a>.</p>
<p>Many sites can benefit from an overhaul of the URL structure to provide more meaningful and less complex URL structure. Care needs to be be taken in making sure that the original links are still operable and their appearance in search engine results will diminish over time.</p>
<h2>5. Error pages</h2>
<p>If the user requests an unknown page, return a friendly error message and use the correct <a title="Link to W3's article on HTTP status code" href="http://www.w3.org/Protocols/rfc2616/rfc2616-sec10.html">HTTP status code</a>. This might sound obvious, but it&#8217;s a surprisingly common mistake on publisher platforms. If you don&#8217;t return the correct error code (for example &#8220;404 Not Found&#8221;) then Google will cache dead or bad links on your site, leading to less than optimal search experience for your users. Similarly, link resolution services such as <a title="CrossRef" href="http://www.crossref.org/">CrossRef</a> can only quality check your DOI metadata if the HTTP codes are used correctly.</p>
<h2>Conclusion</h2>
<p>In conclusion, a little attention to the copy and structure of your site can pay dividends in terms of search engine rankings and discoverabilty.</p>
]]></content:encoded>
			<wfw:commentRss>http://blogs.semantico.com/discovery-blog/2009/11/search-engine-optimisation-for-online-publishing/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
		<item>
		<title>Software Estimation and the Cone of Uncertainty</title>
		<link>http://blogs.semantico.com/discovery-blog/2009/06/software-estimation/</link>
		<comments>http://blogs.semantico.com/discovery-blog/2009/06/software-estimation/#comments</comments>
		<pubDate>Mon, 29 Jun 2009 09:19:53 +0000</pubDate>
		<dc:creator>Liam Sheerin</dc:creator>
				<category><![CDATA[Project Management]]></category>
		<category><![CDATA[Technology]]></category>

		<guid isPermaLink="false">http://blogs.semantico.com/discovery-blog/?p=350</guid>
		<description><![CDATA[Accurate estimation for software projects is the cornerstone of good project management. Learn how task duration and confidence levels are fundamentally connected in managing project risks.]]></description>
			<content:encoded><![CDATA[<p>It is notoriously difficult to estimate how long something will take to do. Take, for example, travel. A car journey to London from Brighton should be easy to estimate based on the distance divided by a reasonable average speed. But what is a reasonable average speed? Traffic should also be considered if the estimate is to be accurate and, for the same reason, roadworks. There are other considerations that would affect the estimate but what is obvious from this small set is that it is not possible to guarantee an estimate&#8217;s accuracy at this stage.</p>
<p>If we take the example further, and look at how such an estimate would change over the duration of the journey, we can see that the only time the estimate can be guaranteed as 100% accurate is once the journey is complete – when the estimate is an actual.</p>
<p>The situation is no different in software development and the accuracy of the estimation of software tasks also increases over time. This change in accuracy over time often referred to as the &#8216;Cone of Uncertainty&#8217;.</p>
<div id="attachment_352" class="wp-caption aligncenter" style="width: 388px"><a href="http://blogs.semantico.com/discovery-blog/wp-content/uploads/2009/06/Cone.png"><img class="size-full wp-image-352" title="Cone of Uncertainty" src="http://blogs.semantico.com/discovery-blog/wp-content/uploads/2009/06/Cone.png" alt="Cone of Uncertainty" width="378" height="341" /></a><p class="wp-caption-text">Cone of Uncertainty</p></div>
<p>The  Cone of Uncertainty shows how an estimate will start with a high degree of uncertainty – either over-estimated or under-estimated –  which then improves over time as more is known about the task(s). The diagram shows several common stages within a project and shows how accuracy will be increased as the project progresses.</p>
<p>If, therefore, it is not possible to guarantee the accuracy of an estimate, then another approach is required.</p>
<p><span id="more-350"></span></p>
<p>It is reasonable to assume that an estimate for completion of a single task could be bounded by a range of best and worst possible cases. If such a range is further defined as having a most likely completion point, an estimation profile for the task can be demonstrated.</p>
<h2>Program Evaluation and Review Technique</h2>
<p>The Program Evaluation and Review Technique (PERT) for software estimations requires developers to provide a range of estimates for a task. PERT requests a best (<code>B</code>), likely (<code>L</code>) and worst (<code>W</code>) case for each task with which one can plot a probability curve for the task. The probability curve plots the probability of completion against the completion time.</p>
<div id="attachment_357" class="wp-caption aligncenter" style="width: 388px"><a href="http://blogs.semantico.com/discovery-blog/wp-content/uploads/2009/06/singletask.png"><img class="size-full wp-image-357" title="Task Profile" src="http://blogs.semantico.com/discovery-blog/wp-content/uploads/2009/06/singletask.png" alt="Task profile" width="378" height="198" /></a><p class="wp-caption-text">Task Profile</p></div>
<p>From the ranged estimate an expected case (<code>E</code>) can be calculated that has a probability of 50%. As can be seen in the graph there are a number of ways of calculating the expected case, based on a weighted average of the best, likely and worst estimates for the task. The weights selected for the expected case should ideally be based on historical data from previous actuals and estimates. In the absence of such historic data, the <code>E=(B+4L+W)/6</code> equation is the prudent choice.</p>
<p>Another benefit of the ranged estimation approach is that it highlights tasks that have a high risk. These can be seen as tasks with the largest range. Where such tasks are identified action can be taken to further understand their nature and therefore provide a more accurate estimation. This can be done through:</p>
<ul>
<li>research and analysis</li>
<li>prototyping</li>
<li>additional requirements workshops</li>
</ul>
<h2>Combining multiple tasks</h2>
<div id="attachment_358" class="wp-caption aligncenter" style="width: 388px"><a href="http://blogs.semantico.com/discovery-blog/wp-content/uploads/2009/06/multipletasks.png"><img class="size-full wp-image-358" title="Multiple Task Profiles" src="http://blogs.semantico.com/discovery-blog/wp-content/uploads/2009/06/multipletasks.png" alt="Multiple Task Profiles" width="378" height="198" /></a><p class="wp-caption-text">Multiple Task Profiles</p></div>
<p>As multiple tasks are estimated a number of task probability profiles will be created. The tasks can be combined to produce an overall project profile that describes the full project.</p>
<div id="attachment_359" class="wp-caption aligncenter" style="width: 388px"><a href="http://blogs.semantico.com/discovery-blog/wp-content/uploads/2009/06/AllTasksProfile.png"><img class="size-full wp-image-359" title="Combining Multiple Tasks" src="http://blogs.semantico.com/discovery-blog/wp-content/uploads/2009/06/AllTasksProfile.png" alt="Combining Multiple Tasks" width="378" height="198" /></a><p class="wp-caption-text">Combining Multiple Tasks</p></div>
<p>Understanding the project profile is useful but the practicalities of project scheduling and costing dictate that a single figure is produced.  As has been demonstrated, completely accurate single estimates are not possible. However, with the application of some basic statistical methods, it is possible to produce estimates at known probability or <em>confidence</em> levels.</p>
<p>The importance of selecting the right confidence level can be seen in the chart below which shows how the confidence level and break-even point for a project define whether the project is likely to be profitable or loss-making.</p>
<div id="attachment_360" class="wp-caption aligncenter" style="width: 388px"><a href="http://blogs.semantico.com/discovery-blog/wp-content/uploads/2009/06/OverallProject.png"><img class="size-full wp-image-360" title="Project Break-even" src="http://blogs.semantico.com/discovery-blog/wp-content/uploads/2009/06/OverallProject.png" alt="Project break-even" width="378" height="198" /></a><p class="wp-caption-text">Project Break-even</p></div>
<h2>Understand that estimates have two dimensions</h2>
<p>Effective delivery of projects on time and on budget requires the application of a clear risk management approach throughout the whole project life cycle. The key learning from this approach is that any project estimate is meaningless without an accompanying confidence level. Applying this principle allows the management of both dimensions in project estimation, which in turn improves the identification and mitigation of risks throughout the project life cycle.</p>
]]></content:encoded>
			<wfw:commentRss>http://blogs.semantico.com/discovery-blog/2009/06/software-estimation/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>
