Some Technical Stats About LetMeGo.com

Hi!

The details of LetMeGo.com, its business model, and its Merrcury Engine are a secret we are not sharing just yet, but today I am sharing some stats of our project with you. I am not sure if they are useful or not, but they are definitely cool.

Use cases documented

  • 128 use cases so far (15 white level use cases)
  • 160 use cases (total) estimated for beta

User interfaces documented

  • 707 interfaces so far
  • 1000 estimated for beta

Test cases recorded (most of them recorded via Selenium)

  • 42 test cases so far
  • 600 test cases estimated for beta

Unit tests coded

  • 194 “passes” so far
  • 480 “passes” estimated for beta

Man hours invested in documenting, designing, and coding the Merrcury Engine:

  • 12,000 hours so far
  • 21,000 hours estimated for beta

Just for fun, I created the graph below. It is a visualization of the requirements of the Merrcury Engine. It renders the pages and links in our wiki where we document the use cases and user interfaces. Each node is a use case or user interface. Each orange line is a link to a use case, while each black line is a link to a user interface. The version of the graph that we are publishing here is small, on purpose, so that you can’t read the names of the use cases or the user interfaces. The original size of the graph is around 25k x 20k pixels. It was rendered using the radial method of Graphviz.


Alexander Torrenegra

P.S. In case you are wondering, we use Rrápido as our developing methodology.

About the Author

Alexander is LetMeGo's co-founder and jefe. Here is his LetMeGo profile. You can follow him on Twitter @torrenegra.

1 Comment

  1. Alberto Domínguez

    My speechless reaction about the Level Of Effort is evident. I cannot wait to see the Mercury Engine in action.

Leave a Reply




XHTML: You can use these tags: <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <embed> <i> <object> <p> <q cite=""> <script> <strike> <strong>