oship-dev team mailing list archive

[Tim Cook <timothywayne.cook@xxxxxxxxx>]

Hi All,

I hope that this will be the beginning of a HOWTO to help others
understand the application development process(es) for OSHIP based
applications.  Please add your thoughts and experiences so that we can
gather information for a document to post on OSHIP.org.

=========================================================================
A. An application based on archetypes and templates (in the future to be
known as constraint definitions)

1. The application requirements team selects available archetypes /
templates for use.

2. If needed; additional archetypes / templates are created to support
the requirements.

3. The UI designer(s) will create the UI using standard WYSIWYG html
editors.  The UI designers should work in close collaboration with the
requirements team so that comments can be included in the html pages to
indicate the archetype/template and attribute where specific input and
display components are sourced from. If creating a report then the
sorting information should be included in a comment at the top of the
page as well. See attached app_ui_draft.html as a simple example using
OOo HTML Editor.

4. The UI file(s) are then passed on to the application programmers who
can create the necessary code to connect the forms with application
data.

During steps 3 & 4 the application requirements team should be creating
scenarios and data sets in order to build known input and output
conditions.  

... (more)

B.  In this case the application is built NOT using archetypes and
templates.  Instead, Python classes are created to express the
constraints directly on the reference model. 

This is NOT the preferred way to build OSHIP apps.  But it can be done
to save time **IF AND ONLY IF** you are absolutely certain that the
information will never need to be shared.  A possible case for this
could be made in the EpiS3 project.  A DSS is built to evaluate animal
bites for the risk that the patient might have contracted rabies.

If the tool is only used to do the evaluation and never meant to be kept
in the patient record then it fits into this category.  

1.

2.

3.

4.

=======================================================================================


Okay, there is much more to write but I would like to get feedback first
at this point.

Kind Regards,
Tim





-- 
***************************************************************
Timothy Cook, MSc

LinkedIn Profile:http://www.linkedin.com/in/timothywaynecook 
Skype ID == (upon request)
Academic.Edu Profile: http://uff.academia.edu/TimothyCook

You may get my Public GPG key from  popular keyservers or    
from this link http://timothywayne.cook.googlepages.com/home

Attachment: signature.asc
Description: This is a digitally signed message part