ellington 0.0.4 → 0.0.5

data/README.md

@@ -7,21 +7,20 @@ The song was written about [New York City's A train](http://en.wikipedia.org/wik
 #### Ellington is an architecture for modeling complex business processes.
 
 Ellington is a collection of simple concepts designed to bring discipline, organization, and modularity to a project.
-([View the slides from the intro talk.](https://speakerdeck.com/hopsoft/ellington-intro))
 
 The nomenclature is taken from [New York's subway system](http://en.wikipedia.org/wiki/New_York_City_Subway).
-We've found that using cohesive physical metaphors helps people reason more clearly about the complexities of software.
+We've found that using consistent and cohesive physical metaphors helps people reason more clearly about the complexities of software.
 *The subway analogy isn't perfect but gets pretty close.*
 
-### Important
+### Goals
 
-The Ellington architecture should only be applied **after** a good understanding of the problem domain has been established.
-*We recommend [spiking a solution](http://en.wikipedia.org/wiki/Software_prototyping) to learn your project's requirements and then coming back to Ellington.*
+- Provide a consistent nomenclature thats simple enough to be shared by engineering and the business team.
+- Establish constraints which ensure complex projects are easy to manage, develop, and maintain.
 
-## Goals
+## Start Here
 
-- Provide a nomenclature simple enough to be shared by engineering and the business team.
-- Establish constraints to ensure that complex projects are easy to manage, develop, and maintain.
+* Skim the intro [slides on Speaker Deck](https://speakerdeck.com/hopsoft/ellington-intro).
+* Review one of the [example apps](https://github.com/hopsoft/ellington/tree/master/examples/social_media).
 
 ## Lexicon
 
@@ -34,3 +33,6 @@ The Ellington architecture should only be applied **after** a good understanding
 
 ![Ellington Diagram](https://raw.github.com/hopsoft/ellington/master/doc/primary-terms.png)
 
+**Note:** *We recommend Ellington for projects where a good understanding of the problem domain has been established.
+You might want to [spike a solution](http://en.wikipedia.org/wiki/Software_prototyping) to learn your project's requirements before using Ellington.*
+

data/lib/ellington/version.rb

@@ -1,3 +1,3 @@
 module Ellington
-  VERSION = "0.0.4"
+  VERSION = "0.0.5"
 end

metadata

@@ -1,7 +1,7 @@
 --- !ruby/object:Gem::Specification
 name: ellington
 version: !ruby/object:Gem::Version
-  version: 0.0.4
+  version: 0.0.5
   prerelease: 
 platform: ruby
 authors:
@@ -43,6 +43,22 @@ dependencies:
     - - ~>
       - !ruby/object:Gem::Version
         version: 0.0.7
+- !ruby/object:Gem::Dependency
+  name: ruby-graphviz
+  requirement: !ruby/object:Gem::Requirement
+    none: false
+    requirements:
+    - - ~>
+      - !ruby/object:Gem::Version
+        version: 1.0.8
+  type: :runtime
+  prerelease: false
+  version_requirements: !ruby/object:Gem::Requirement
+    none: false
+    requirements:
+    - - ~>
+      - !ruby/object:Gem::Version
+        version: 1.0.8
 description: ! "\n    A micro framework to ensure your projects are easy to manage,
   develop, & maintain.\n  "
 email:
@@ -118,7 +134,7 @@ required_rubygems_version: !ruby/object:Gem::Requirement
       version: '0'
 requirements: []
 rubyforge_project: 
-rubygems_version: 1.8.25
+rubygems_version: 1.8.23
 signing_key: 
 specification_version: 3
 summary: A micro framework to ensure your projects are easy to manage, develop, &
@@ -141,3 +157,4 @@ test_files:
 - test/ticket_test.rb
 - test/transition_info_test.rb
 - test/unique_type_array_test.rb
+has_rdoc: