BOEING MEETING
March 19, 1999
2:00 – 3:00
1131 ENG II
In attendance:
Karl Levitt (KL), David Klotz (DK), Jeff Rowe (JR) and Jason Schatz
(JS)
-
Assign Boeing Tasks to Researchers
-
Task 1: Get all values/costs from Dalen and Kelley's cost model
and determine whether our cost model is a reasonable design.
-
Jeff, Jason and Karl to work on simulating the cost model on paper and
then writing a program
-
Lost conactivity to Tick - use existing typology
-
Consider that Boeing adds parameters without much thought
-
Task 2: Determine capability of responders in cost model
-
Ways of propagating numbers - conditional probabilities
-
Look at chapter in AI book for ECS 170, Elaine Rich's pages on CYC
-
Include in typology what responder can do.
-
Task 3: Output from correlation engine - use CIDF
-
Jeff and David K: correlation out of GrIDS; express GrIDS using CIDF
-
Express worm in language gives an idea what to do
-
Express in connection-type language
-
Jeff to have preliminary information next week
-
Look at Todd Heberlein's master's thesis
-
Task 4: Ability to override actions of the cost model (UNDO button)
-
Listening for message that says to stop.
-
Task 5: List of responses we want to take (specifications) - Chris
Wee will do this task.
-
Chris Wee to user wrapper project from TIS to do host-based response.
-
Not possible to stop the person, can only stop all processes from a particular
user.
-
Task 6: We currently rely on IDIP connection timeouts. We need to
be able to tell local IDIP nodes to remove blocking.
-
Wrappers can't do everything; need utility routines
-
Wrapper can intercept system calls
-
How to stop a particular user if the jobs are set on a timer.
-
Look at Calvin Ko's execution monitor or Sekar's work
-
Jeff will contact Calvin, regarding a visit.
-
Write specs for wrapper
-
Bob Balser à Lee Badger
-
Task 7: Make an OS response toolkit (wrappers can't do it).
-
Task 8: Documentation for Boeing - no one knows how to run code
-
All have a responsibility to do documentation.