awebfactory - web application factory pattern

[This needs to be re-written in the light of cloud app architecture]

awebfactory builds upon an agile, test-driven, architecturally centered and iterative and incremental approach to web application development based primarily on both the Drupal Content Management and Ruby on Rails frameworks, focusing on client participation.

In terms of web application deliverables, awebfactory is turning increasingly towards a mentoring services methodology: commitment to project through empowerment.

We help you to create a best practices rooted workspace in which to house a cooperative web application process for every client and project, based upon our soon-to-be released (in Drupal distribution profile format) "Process Flow and Tracker" web application.

[Just thinking aloud here, that's what a blog is for, isn't it?]

I like use cases because they are great for modeling scope.

Once you have a use case, with its basic flow and alternative flows, then you can discover the most important paths through the basic and alternative flows, and clearly mark out the key scenarios.

Each one of these key scenarios corresponds to a single test case. So each use case has one or more key scenarios and the same number of test cases.

These test cases are what the customer and the developers must write together based on a user story which is going to be implemented.

I am quoting in full a post of mine at groups.drupal.org

Work performed in accordance with a Guideline by a Role in the context of a Project.

The pattern may be instantiated to yield a process tailored to the project