Welcome

About

Welcome to the RealSMA Specification System.

As you probably have noticed, this is a web app built on the RealSMA framework. It's for the framework, on the framework to test the framework. (Talk about the chicken and the egg). Naturally there will be lots of stuff that do not work but hey, at least you can get some data in and out. All the configuration is done via XML files (for now). Take a look under the installed directory if you are interested. If not, just jump directly into a project on the right.

The purpose of this system is to capture requirements for RealSMA solutions. Yes, it might even be used by other non-RealSMA projects. So, if you want that then better let me know.

Here are some of the concepts used in defining requirements for RealSMA applications:

  • Project - Something that consumes time, money and makes hair gray.
  • Module - Just to group some stuff for contextual navigation (Feature sets)
  • Feature Set - Theme or set of features / stories
  • Story - Describes a feature.

Interesting links to look at:

  • RealSMA Specification System - My initial kick off on the requirements for the RS Spec system.
  • Domain Events and Commands - The domain events and commands used by this (running) system.
  • Site Map - No, this is not a realy site map. Sorry.. It's just the list of all the resources in the application.
  • Projects - Web Application - Web Application - The list of projects
  • Projects - REST (Hypermedia) interface - The application to be consumed by REST clients (thus your browser too ;)
  • Projector - All changes in the application are written in the event log. The events are then projected to read side (tables). The projecter manages the projections of events from the domain model. For the moment it drops and recreates tables from the event store.

Known issues:

Here are some known issues that will be addressed. Yes, this list is not exhaustive.

  • Missing required fiels - Somehow that does not work darn....
  • Does not check for duplicate entries. For example you can enter duplicate stories and it will mess up the navigation a bit.
  • There is no proper state model to show the valid next actions. For example you must add goals and modules before creating feature sets, or else you will not be able to pick feature sets.
  • Filling in forms (command) feel a bit awkward - This is being worked on. It will render "inline" on some future release.