[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: FW: [courtfiling-blue] User Use Cases--comments
Scott,
I agree with your points about the use cases. I think the assembling/submitting filings and information queries are key “features” provided. Taking assembling/submitting, receiving/reviewing, and querying separately and in different combinations, such as in query for a case number and assemble/submit a related document based on the queried information, gives a good basic package for functions that need to be performed. Unless specific storing/processing functions are deemed within scope to be defined for the CourtRecord component, then for the communications, the ones listed seem sufficient to describe possible communications.
To the CF Blue Requirements group,
In general, when looking over the wiki and the latest user use cases released on the CFBlue subcommittee list, I keep getting the sense that the EFSP, EFM, and CM concepts have somewhat been renamed and slightly abstracted into FilingAssembly, FilingReview, and CourtRecord and we’re still at a level of distinction among several specific pieces which gives us mostly a one way street into the courts. It seems like the use case components start as abstracted pieces, but then as they are defined fall back in line with the older specific function EFSP, EFM, and CM/DM that we have tried to move away from after the Seattle FTF when each end of the communications was deemed a black box in which only the functions related to communications between black boxes were to be defined.
A possible example of the above statements about the components seeming to fall back to older terminology restrictions when being defined can be seen with the “FilingReview” component from the wiki. For small implementations, the review filings function will be beneficial as a distinct and separate component, as it was found in many EFM scenarios, but larger installations will likely customize their existing case management systems to interact with a middleware to provide the review of the filings within the case management system interface. Can the review function be either a part of receiving the filing as a possible function that is performed or a part of an extension to querying by the CourtRecord component of the FilingReview component/EFM/middleware?
For example of this type of review setup, one court that we are working with will possibly have the filings to come into a temporary db space that is accessible by their case management system for them to be able to review and accept/reject the documents from within their case management system. Assuming that the case management system would fall into the realm of a CourtRecord component would a situation like this violate the FilingReview component use case on the wiki or the user use case of ReviewFiling? Going from the way that the components seemed to be used in some of the use cases, as being similar to the older EFM/CM terminology of being specifically distinct components a situation like this would seem like it would violate the use cases even though the distinct functions are provided for, but with a mix of the components.
Also, could the components be mirrored on each side, for both filer and court? If both the filer and the court can assemble/submit, receive/review, store/process communications and query for information then the specification is more in the lines of data exchange which will make electronic filing more beneficial for filer and court. This would also broaden the usefulness of e-filing/data exchanges to allow for communications such as district attorney’s communicating with police as well as the courts.
Please let me know what you think and excuse any butchering of the terminology if I have understood it incorrectly.
Thanks,
Rex
Rex McElrath Administrative Office of the Courts 244 Washington St. SW Suite 300 Atlanta, GA 30334 404-657-9218
From: Scott Came [mailto:scott@justiceintegration.com]
Blue Drafting Subcommittee Members: |
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]