Picture of Ryan Adams
Architectural Principles
by Ryan Adams - Wednesday, 25 September 2013, 12:17 PM
 

Here's a spreadsheet I have created to try and tease out the principles of the application.  This will help us decide on the right technology to use and what NFRs (Non-Functional Requirements) we should implement.

There are two important worksheets.  The first, lists the statements from the Product Vision, and I've extracted themes from them.  The second draws out principles for the architecture of the application from those themes. 

I have a feeling that it's incomplete, but before I hit 40 principles I thought that was enough to share with you all.

The original is a Google doc, which it might be worthwhile opening up if we wanted to add to the list of themes or the principles.

Paul Welch
Re: Architectural Principles
by Paul Welch - Wednesday, 25 September 2013, 1:20 PM
 

Hi Ryan,

This is great and I think captures where we've come from and where we want to be heading. 

I'll get my thinking cap on and see if I can spot anything which needs adding. There might be something around in-built learner support and the relationship between assessment and related content as part of either extensible or good user experience. 

Cheers,

Paul

 

 

Picture of Ryan Adams
Re: Architectural Principles
by Ryan Adams - Wednesday, 25 September 2013, 1:37 PM
 

Thanks Paul,

the key concept is that the architecture falls out of the product vision and requirements.  So it should be possible to derive a requirement or principle from the Vision Statements, and if it's not then we may need to adjust the vision to allow it.

I think that's a useful approach to testing that we have the right vision for the product too.

me
Re: Architectural Principles
by Sven Laux - Tuesday, 12 November 2013, 4:45 PM
 

Hi Ryan,

Thanks for the chat on this just now. Updating this thread to bring it up into people's consciousness again and post an update:

As part of the review of the design stream documentation, we talked through the architectural principles document and have agreed that this document is important and should be brought up to date. It represents how our work on the architecture ties back to achieving the vision we have set.

The document will ideally serve the following purpose:

  • To be used regularly as a checklist for those actively working on architecture related tasks.
  • To be part of the briefing of new architects and developers as they take an active part in the project.

I have renamed the document and uploaded it (as is) to Github at https://github.com/adaptlearning/documentation/blob/master/01_cross_workstream/principles_architecture.xlsx

I will now add my changes and comments and work with you to bring this up to date. Once we’re happy with it, we will send it our for review to the design stream and present it at the design stand-up meeting for discussion and acceptance.

Sven

Picture of Ryan Adams
Re: Architectural Principles
by Ryan Adams - Wednesday, 13 November 2013, 2:08 PM
 

I wonder whether this document would be better presented as a document rather than a spreadsheet (I think I picked the wrong format back in September).  I think we could craft it such that the principles were more clearly related to the Themes and the Vision Statements.

I'm happy to create that document when you've updated the spreadsheet Sven.

me
Re: Architectural Principles
by Sven Laux - Wednesday, 13 November 2013, 2:43 PM
 

Hi Ryan,

that aligns well with what I have been thinking. My current thoughts are to create section, which pulls out and describes the themes and then follow that up with a section each for the various disciplines (e.g. architecture, development, design, commercial considerations etc).

Will play with this some more and get it back over to you ASAP.

Sven