<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>State-Machine on Lucas Pardue - Bits &amp;&amp; Pieces</title>
    <link>https://lucaspardue.com/categories/state-machine/</link>
    <description>Recent content in State-Machine on Lucas Pardue - Bits &amp;&amp; Pieces</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Tue, 22 Apr 2014 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://lucaspardue.com/categories/state-machine/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>UML: Modelling User Interfaces Part 1 - Hierarchy and Navigation</title>
      <link>https://lucaspardue.com/2014/04/22/uml-modelling-user-interfaces-part-1-hierarchy-and-navigation/</link>
      <pubDate>Tue, 22 Apr 2014 00:00:00 +0000</pubDate>
      <guid>https://lucaspardue.com/2014/04/22/uml-modelling-user-interfaces-part-1-hierarchy-and-navigation/</guid>
      <description>&lt;p&gt;This is the first post in a series that looks at the modelling of User Interface&#xA;(UI) related software using UML.&lt;/p&gt;&#xA;&lt;p&gt;The main purpose of the post is to explore how we effectively model the&#xA;navigation of a tree-like hierarchy, especially when considering the premise &amp;ldquo;In&#xA;a tree structure there is one and only one path from any point to any other&#xA;point&amp;rdquo;.&lt;/p&gt;&#xA;&lt;p&gt;The tl;dr is that UML does not necessarily have the ability to represent UI&#xA;concepts of hierarchy and navigation effectively.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
