Court Filing Blue Requirements Subcommittee
Minutes for Meeting on 12/2/04
Attendees
Jim Cabral (MTG), Tom Clarke (Washington AOC), Scott Came (Justice Integration),
Shane Durham (Lexis Nexis)
Absent: Dallas Powell (Tybera), John Ruegg (L.A. County ISAB), Eric Tingom
(ecorrideor).
Message Types
The draft message types developed by Jim Cabral were significantly modified.
Supporting changes were also made to the core component use cases, which deal with
electronic filing but not electronic service. Error flows are handled more consistently.
Asynchronous messages are handled more consistently. Message type contents were
discussed and clarified.
Court Policy Interfaces
The group held a significant discussion about the impact of the component architecture
on the structure of court policy, based on an issue list developed by Scott Came. They
also discussed at length the separate issues around user, design and runtime policy
requirements, enlightened by comments from Shane Durham. Consensus was not
reached on all issues, so this is an area for significant discussion at the December face-to-
face meeting.
Electronic Service Use Cases
The group held a significant discussion about the impact of the component architecture
on the structure of e-service use cases. Shane's concept of an e-service user profile was
helpful, but it then raised a possible requirement for some kind of directory. Consensus
was not reached on all issues, so this is an for significant discussion at the December
face-to-face meeting.
Actions and Schedule
The group agreed to refer to deliverables that were ready in draft form to hand off to the
entire TC for their review, modification and acceptance as "baseline version." Note
below that all deliverables are scheduled to be at baseline version before the December
face-to-face meeting except for the court policy use cases. There is a disproportionate
short-term burden on Shane Durham, so the TC should interpret the dates accordingly.
Baseline versions will appear on the Wiki and the TC website as they are completed
before the December meeting. Deliverables currently in baseline version include the core
component use cases, the non-functional requirements, the web services profile, the
ebMS profile, the concepts and the glossary.
1. Complete baseline version of core User use cases (Shane Durham) - 12/10/04
2. Revise baseline version of e-service User use cases (Shane Durham) - 12/10/04
3. Produce baseline version of e-service Component use cases (Shane Durham) -
12/10/04
4. Revise core Component use cases for revisions of queries (Scott Came) - 12/12/04
5. Develop court policy use cases (Scott Came) - 2/1/05
6. Add a definition of a directory to the Concepts (Shane Durham) 12/10/04
Deliverables for December Face-to-face Meeting
1. Core User use cases (baseline version)
2. Core Component use cases (baseline version)
3. E-service User use cases (baseline version)
4. E-service Component use cases (baseline version)
5. Non-functional requirements (baseline version) - presented at September meeting
6. Draft non-functional requirements
7. Core Profile (baseline version) - includes deliverables #10 and #11
8. Web services profile (baseline version)
9. ebMS profile (baseline version)
10. Message types (baseline version)
11. Court policy use cases (pre-baseline version)
12. Concepts (baseline version) - previously, Nomenclature
13. Glossary (baseline version)