Karl Levitt (KL), Nicole Carlson (NC), Jim Hoagland (JH)
News
Negotiating Software Requirements
Brief Synopsis of Jim's Presentation
News
KL: I have just contacted Baiju about coming to visit in June or July.
JH: I will be out of town June 25th-July 2nd. Back
on July 6th.
NC: I'm leaving the 18th, will likely have a job with NASA Ames
until the Aug 6th when I come back for Summer Session.
Next Week, we'll invite the GrIDS people to the Intel meeting - Chris,
Jeff, Rick, Matt
Negotiating Software Requirements
KL: It a bit fuzzy
Requirements Engineer and a Customer- how to extract what you really want.
Consider performance requirements, function requirements, tradeoff
JH: The customer may not know what they want.
NC: Ask leading questions to determine what they want.
JH: Price is a consideration
KL: There may be conflicting requirements.
Apply security requirements - come up with a model.
JH: Negotiate security policy between a customer who needs security
SCIPAD - Communication partner - what security you want
Security Service Provider - medium size business negotiate with IBM for
insurance, backups, port costs
Exploration - software tools, plug in what you like, determine how it works
with each system
KL: Capture what each customer wants as a final state machine
Brief Synopsis of Jim's and Nicole's Presentation
JH: We've worked on 3 situations of transferring GrIDS into LaSCO
Simple Policy - one edge in GrIDS
One edge and additional state
Two edges to trigger and external state
JH: Problems with the isolated node. Add more to the rulesets, determine
how to solve it.
The way we maintain external state with separate graphs with information
accumulating. Merge in with reports coming in. Reason why not sufficient
for lone node policy.
The order of the merged graphs matters, need to label them to distinguish
them or add functioning
JH: After we solve the isolated node problem, then we'll look at an edge
and an isolated node, then hierarchy.
NC: I looked at the GrIDS technical report, looked at the ruleset, but
I don't know Perl yet.
JH: You had to look at the code for the semantics.