Skip to main content
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
[alf-req] ALF Requirements Meeting Minutes 10/12/2005, 10/19/2005
 
ALF Requirements Meeting Minutes
10/26/2005  
 
Attendees
 
Aldon 
BuildForge
Secure Software
Segue
Serena Software
 
Review Requirements Document
 
Discussion: As with the past two weeks, this week we concentrated on reviewing the ALF requirements document. Besides looking at the requirements themselves, we are also discussing priorities so we can defer features if necessary. I'll summarize the findings here. See the document for the resulting requirements definitions.
  • AEB4. Approved.
  • AEB8. Approved.
  • AEB11. Added additional parameters to the standard logging. 
  • AEB13. Requires additional review before we defer.
  • ASR1. Added comment indicating that while the credentials need to be recognized, it is up to the tool to apply permissions to the user represented by the credentials.
  • ASR3. Remains as requiring review since we need to understand how credentials will be implemented. This may seem backwards, but ASR3 may be invalid depending on how authentication is handled in ALF.
  • ASR5. Homework for the committee: look at this list of options for weakly ALF compliant services to see what needs to be added or removed. I'm going to pull these out and put them in a best practices document.
  • AWS1. Review. May be duplicate.
  • AWS4. Updated the definition of weakly compliant web services to be services that can be called from the BPEL engine.
  • AWS5 - AWS7. Approved.
  • AWS8. The fate of this requirement is tied to ASR3. Still for review.
  • AWS9. Added a new web service ALF will expose to export an official ALF timestamp. This can be used to synchronize log entries between the tools and ALF.
  • ADM5. Approved.
  • ADM6. Added a requirement to allow administrators to specify multiple logging levels, not just default and debug. This will spawn a number of logging requirements related to overriding logging levels for certain event sources (E.g. All TT events will be logged at the debug level,) for certain event types (E.g. only log warnings for requirement created events,) or for specific event structures. It is likely we will defer a number of these features until after 1.0, so I'll make them fairly granular in the new doc.
  • POC1. I'll be pulling this out of the requirements doc and sending this to Mirinda since it relates only to the POC.

Homework for next week

Look at all of the requirements and see if any need a priority shift. 

 Next Meeting

The next requirements meeting will be from 10:00 - 11:00 Pacific on Wednesday, 2 November. Shaw will send the meeting announcement and agenda to alf-events and alf-req and will post the announcement to the newsgroup. Shaw will also request the webmaster to update the requirements document before the next meeting.

Kelly Shaw
Sr. Product Marketing Manager
Serena Software
719-457-8811

**********************************************************************

This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. Any unauthorized review, use, disclosure or distribution is prohibited. If you are not the intended recipient, please contact the sender by reply e-mail and destroy all copies of the original message.

Back to the top