Course Agenda for an onsite, 5-day "Parallel Turbocharge" workshop

One of our expert Parallel Agile consultants will visit your location and help you get your project off to a flying start. At the end of a week you've got a working instance of Mongo DB with a Node JS API (documented in Swagger), along with a mix of working prototypes and production-ready code along with a detailed UML model including requirements, use cases, MVC decompositions, sequence diagrams and test cases.   If you know a faster way to develop high quality software we want to know about it.

The first day of your workshop is instructor-led.   For the rest of the week your team guessed parallel.

Here's how it works:

Monday - Generate Database and API from Domain Model

On the first day of class you'll experience the power of Executable Domain Models and COGENT™ - Parallel Agile's domain driven code generator.  We'll spend a couple of hours brainstorming the domain model and then transform it to a working database (Mongo) with all database access functions code generated and wrapped in a Node JS API.   API docs are automatically generated in Swagger as well as some client-side sample code in JavaScript, Java, Swift and C#.  And then it's almost lunchtime. 

COGENT Generates MongoDB schema and database access functions, a Node JS API, and Swagger documentation instantly from your domain model

In the afternoon you'll identify User Stories, Epics, and Tasks and develop a visual model sprint plan using the Parallel Agile Add-In for Enterprise Architect.   You'll also develop a Use Case model.  Then you'll allocate the development tasks to students and begin prototyping against the new API which can be hosted on AWS or on the cloud-server of your choice.

Tuesday - Prototype

You'll come in Tuesday morning wondering whether that API that got generated yesterday really works, and energized when you start prototyping and discover that it does.  When you prototype you're free to focus on sunny-day scenarios without need for unit testing so you'll find that progress is rapid.  Stakeholders can interact with your prototypes and feed you more specific requirements.

Wednesday - Model Requirements and MVC Conceptual Designs

On Wednesday morning you'll flesh out the functional requirements model of your system along with developing a detailed set of behavior requirements in the form of a detailed use case model with each use case defined in terms of its Models, Views, and Controllers.  These behavior models will consider all of the rainy-day scenarios, corner cases, and edge cases that you got to skip when you were prototyping.  All of this modeling work is done in parallel so you'll get a lot done in a day.

On Wednesday afternoon you'll update the domain model to reflect the feedback gained from the prototyping, and re-generate the database, API, and API docs.

Thursday - Detailed Design and Coding

On Thursday you can do as much detailed design as needed using UML techniques like sequence diagrams and state machines, and when you're ready start coding against the updated API.  If you like to code unit tests, feel free to do that as well.   Because the REST API is client-language neutral, you can develop in the languages of your choice.

Friday - Acceptance Testing

If you were wondering why you modeled rainy-day scenarios on Wednesday and coded them on Thursday it's because on Friday you get to generate a set of acceptance test scripts that have been generated and give them to your QA department.  You'll follow the Design Driven Testing process and use the ICONIX/Agile DDT add-in from Sparx Systems.

So there it is - 5 days to turbocharge your project:

For more information on getting your project turbocharged, email us at