Документ взят из кэша поисковой машины. Адрес оригинального документа : http://www.stsci.edu/ops/tof/tof_minutes/07-29-99_brainstorming Дата изменения: Tue Aug 3 01:44:25 1999 Дата индексирования: Sat Mar 1 16:34:35 2014 Кодировка: Поисковые слова: http astrokuban.info astrokuban

Brain storming sessions from 7/29/99 TOF meeting
------------------------------------------------

Discussion of the white paper draft:

Glenn thinks that sections 1 and 2 are irrelevant. Section 1 may be
handled more briefly by mentioning our charter, but we are not willing
to give up section 2. We think that the history is important to people
reading the paper that are not as familiar with the history of phase 2
user software.

Andy thinks we need to focus attention on three points:

1) New innovative tools to the user soon
3) A management strategy to support more innovation
3) An environment that integrates the new tools

The second decade demands innovative user support.

The white paper needs to show that there is a problem and that new
tools environment is the answer.

We must stress the environment aspect more in the white paper.

Andy will work on rewording the abstract.

Don't like the word "Phase", how about "Stage"?

Is this an evolutionary step or a revolutionary step? This issue
caused confusion for Glenn. We are following a staged roll out of
a completely different tools environment.

Does the new tools environment have to be able to do everything that
RPS2 does? Maybe we won't convert everything and you will have to
revert to RPS2 in some obscure cases.

When will RPS2 be completely gone? We don't know - but does it matter?

The house analogy. You buy a big chunk of land will an old house on
it. Then you slowly build your dream house, but you can go back to the
old house whenever you want for services that are not yet in the new
house.

Nick expanded the analogy. You build the pool and the garage first and
use those right away. (This is like the VTT.) Then you build the
house. (This is like the environment.) Eventually there is enough
amenities for some family members to move in, but a few stay back at
the old house until everything is ready.

CD player analogy. LPs and LP players didn't go away all at once.
People just started buying more and more CD players and CDs.

Nick is going to rewrite section 3.4.

Move the quality assurance goals into the success criteria section.

In the architecture section it should not say that our design goals
are to use particular languages (Java, XML, UML) but instead that we
want the value that those languages have and then give the language as
an example.

"keeping in mind that we are moving towards an observatory independent
design, the design should be documented so it is easily understood by
people not involved in its original design"

Maybe the wizards should be called out as a separate issue in the
architecture. And what do we mean by wizards anyway?

o more knowledgeable about tools

o expert help for a tool

o wizard knows what system can do

o a listener that makes recommendations based on what
has been done

o part instrument scientist (provides assistance)

o advice and wrapper around needed tools

Rob will edit the architecture section and send it to Anuradha.