A first draft of a one view of the Technical Architecture of the Authoring Environment.
This view shows the high-level activities that a User will complete in the application (there are 7). I've outlined the systems that make up the Authoring Environment that are required to enable these activities, and some additional systems that they themselves depend on.
I've not yet documented the behaviours and characteristics of those sub-systems (that's today's job)
Setting aside the idea of MVP (which I've never completely understood) and looking at this from the perspective of "how do I get value quickest?", I think we could cut this down to 3 activities and get internal value (i.e. we could use it internally, relying on process to fill in the gaps), 5 and get some external value, which implies that the order of development should be
- content creation
- content export
- content review
- login/logout
- system administration
- reporting
- sign-off
The tool is useless until we get 1 and 2 above done.
