* Larry Beaty: About to contact A&D about the broken monitors.
William and Steven are progressing to laying out circuit boards
using Eagle, but the library of parts isn't sufficiently complete,
so they are creating templates. Want to recruit some technical
leads so we can support projects in the fall.
* Chris: Working on Phoenix Requirements & Architecture. 1
to 2 months. Wants to discuss hosts and servers.
* Bob: Working on HealthVault. Concerned about how they will prevent
loss of data, i.e. when data is brought in and passed through
an organization, what is the method of retaining data through
accidental loss of data? Chris said this is a design pattern issue.
For example, an MS Word document that isn't changed may have its
timestamp changed. El asked, isn't this an operating system issue,
specifically the file system?
Local vs Remote
Rich Internet vs.
Loose vs Tight
Various scenarios from the scenario descriptions.
For example, a person "gets a sphygmochron", says this isn't adequate and "sends sphygmochron to clinic" to get help.
A physiologist "gathers sphygmochron:", then "builds model" to get a reference database, to model and determine what is common and define parameters. To a physiologist, get a sphygmochron means build a model.
In both cases, this interaction is loose. This suggests a service-oriented architecture, enabling building an application by defining a service layer. This defines database management systems, application containers and servers.
To use a applications server, like:
* JBOSS
* TOMCAT.
Need description that implies money: i.e. ISP, ASP, scale. We are assuming FOSS, free Open Source Software.
El suggested that the architecture include "free hosting"
such as a individual's home computer or freely available ASPs,
and scale up from this to large expansively hosted systems.
This page is maintained by Ellis S Nolley. It was last updated on 12 May 2009.
The author(s) provide this information as a public service, and agree to place any novel and useful inventions disclosed herein into the public domain. They are not aware that this material infringes on the patent, copyright, trademark or trade secret rights of others. However, there is a possibility that such infringement may exist without their knowledge. The user assumes all responsibility for determining if this information infringes on the intellectual property rights of others before applying it to products or services.
Copyright (C) 2009 Ellis S. Nolley.
Copying and distribution of this page is permitted in any medium,
provided this notice is preserved.
Back to the Meeting Archive Page