Documente Academic
Documente Profesional
Documente Cultură
Business Actor:
An Actor is a user of the system; user can mean a human user, a machine, or even another system or subsystem in the
model. Anything that interacts with the system from the outside or system boundary is termed an Actor. Actors are
typically associated with Use Cases.
Actors can use the system through a graphical user interface, through a batch interface or through some other media. An
Actor's interaction with a Use Case is documented in a Use Case scenario, which details the functions a system must
provide to satisfy the user requirements.
Actors also represent the role of a user in Sequence Diagrams.
Toolbox Icon
uc Juv enile Actors
Court Coordinator
Toolbox Icon:
uc Juv enile Court Clerk ...
Manage Delinquency
Doc ket
Maintai n Logs
A Use relationship indicates that one element requires another to perform some interaction. The Use (or Usage)
relationship does not specify how the target supplier is used, other than that the source client uses it in definition or
implementation. A Use relationship is a sub-typed Dependency relationship.
You typically use the Use relationship in Use Case Diagrams to model how Actors use system functionality (Use Cases)
or to illustrate usage dependencies between Classes or Components.
Note: You may also use the Association connector between an Actor and a Use Case.
Court Coordinator
A Generalization is used to indicate inheritance. Drawn from the specific classifier to a general classifier, the generalize
implication is that the source inherits the target's characteristics. It is used typically in Class, Component, Object,
Package, Use Case and Requirements diagrams.
OMG UML Specification
The OMG UML specification (UML Superstructure Specification, v2.0, p. 66) states:
"A generalization is a taxonomic relationship between a more general classifier and a more specific classifier. Each
instance of the specific classifier is also an indirect instance of the general classifier. Thus, the specific classifier inherits
the features of the more general classifier."
Include:
uc JVCClerk_Manage Delinquency Docket
Manage Delinquency
Doc ket
«include»
Maintai n Logs
An include connection indicates that the source element includes the functionality of the target element. Include
connections are used in Use Case Models to reflect that one Use Case includes the behavior of another. Use an include
relationship to avoid having the same subset of behavior in many Use Cases; this is similar to delegation used in Class
models.
OMG UML Specification
The OMG UML specification (UML Superstructure Specification, v2.0, p. 518) states:
“Include” is a directed relationship between two use cases, implying that the behavior of the included use case is inserted
into the behavior of the including use case. The including use case may only depend on the result (value) of the included
use case. This value is obtained as a result of the execution of the included use case."
Extend:
uc JVCClerk_Prepare Order Documents
Prepar e Probable
Cause Docs
«extend» «extend»
Prepare J udgments
«extend»
«extend»
«extend»
Prepa re Or der
Docum ents
(from Family)
An Extend connection is used to indicate that an element extends the behavior of another. Extensions are used in Use
Case models to indicate that one Use Case (optionally) extends the behavior of another. An extending Use Case often
expresses alternate flows.
OMG UML Specification
The OMG UML specification (UML Superstructure Specification, v2.0, p. 515) states:
"This relationship specifies that the behavior of a use case may be extended by the behavior of another (usually
supplementary) use case. The extension takes place at one or more specific extension points defined in the extended use
case. Note, however, that the extended use case is defined independently of the extending use case and is meaningful
independently of the extending use case. On the other hand, the extending use case typically defines behavior that may
not necessarily be meaningful by itself. Instead, the extending use case defines a set of modular behavior increments that
augment an execution of the extended use case under specific conditions. Note that the same extending use case can
extend more than one use case. Furthermore, an extending use case may itself be extended."
Dependency:
uc JVCClerk_Process Sealings
«dependency»
Associate Judge
Dependency relationships are used to model a wide range of dependent relationships between model elements in Use
Case, Activity and Structural diagrams, and even between models themselves. The Dependencies package as defined in
UML 2.0 has many derivatives, such as Realization, Deployment and Use. Once you create a Dependency you can
further refine its meaning by applying a specialized stereotype.
OMG UML Specification
The OMG UML specification (UML Superstructure Specification, v2.0, p. 108) states:
"A dependency is a relationship that signifies that a single or a set of model elements requires other model elements for
their specification or implementation. This means that the complete semantics of the depending elements is either
semantically or structurally dependent on the definition of the supplier element(s)."
Realize:
uc JV_CR_Track Exhibits
Track Exhibits
(from Family)
A source object implements or Realizes its destination object. Realize is used in a Use Case, Component or
Requirements diagram to express traceability and completeness in the model. A business process or Requirement is
realized by one or more Use Cases, which in turn are realized by some Classes, which in turn are realized by a
Component, and so on. Mapping Requirements, Classes and such across the design of your system, up through the
levels of modeling abstraction, ensures the big picture of your system remembers and reflects all the little pictures and
details that constrain and define it.
OMG UML Specification
The OMG UML specification (UML Superstructure Specification, v2.0, p. 110) states:
"A Realization signifies that the client set of elements are an implementation of the supplier set, which serves as the
specification. The meaning of 'implementation' is not strictly defined, but rather implies a more refined or elaborate form in
respect to a certain modeling context. It is possible to specify a mapping between the specification and implementation
elements, although it is not necessarily computable."
Juvenile Court Actors
Actors were broken down into three categories, Internal Business, External Business and System actors:
• Internal Business actors are those that interact directly with the system or with the actor within the context of the
model to complete the process.
• External Business actors are those that are outside the realm of the internal business actor, but initiate or receive
some benefit form the process
• System actors are other applications or interfaces that the system interacts with
Associate Clerk
Bal iff Court Reporter
(from District Court Actors)
(from District Court Actors)
(from District Court Actors)
«inherits»
Distric t Judge
Probation Officer
Child S upport
Attorney OCA
(from External Entity Actors) DP S
(from External Entity Actors) (from District Court Actors)
The System Actors we identified for Juvenile are MS Word, MS Excel, MS Outlook, JIMS-Juvenile, J-PALM, KIDS, JCMS
and SAP.
System Actors
JIMS-Juv enile
J-P ALM KI DS JCMS
(from System Actors) (from District Court Actors)
(from District Court Actors) (from District Court Actors)
MS Exc el MS Ac cess
MS Outlook SAP
(from System Actors)
(from System Actors) (from District Court Actors)
Juvenile Delinquency High-Level Process Flow
analysis Juv enile Delinquent High Lev el Flow
Inv estigation
LEA
Process Intake
Recomme ndation
decision?
JV Intake
No Release to Guardian
JV Detention
remandIntoCustody?
enoughInformation?
No
Yes
prosecuteAsAdult?
preFileDisposition?
probableCause? Yes No No File Delinquency Petition
No
Yes
Yes
Caution
Class C Ticket
DPP
No
StudyComplete? Request Cert Diagnostic
JV Court Clerk
Study
Schedule Detention
Schedule Court Hearing
Yes Hearing (10 days)
Schedule Certification
Hearing
Psyc h E v al
keepInCustody? Yes
childCompetent?
Treatment Report
Yes No
No
No
Yes
No
Commi tted
TY C
JV Probation
Probation Plan
Route to County
childAtRisk?
Close Case
Inv estigation No
Yes
Yes evalPeriodComplete? Child Returned to
No Parent/Guardian
Yes
canBeMitigatedWithChildAtHome?
Yes Transfer to FBSS Monthly Monitoring File Petition to Remov e
No
No conditionsImproving?
isFlightRisk? No
No
awardTempCustody?
Yes
Yes
No
Place Child in Foster Prepare Case for Show Show Cause Hearing
Care Cause Hearing cpsRetainTempCustody?
Yes
Dev elop Serv ice Plans File Serv ice Plan w ith Status Rev iew Hearing
Court
at 6 months from the
removal
Initial Permanency
T his is not really formally filed at this point Rev iew Hearing
Monitor for Compliance Serv ic e Plan
since it was contained in the original 3 months later (month 9 from removal)
petition. This is really just a setting letter
that is sent out declaring that they are going
after permanent managing conservatorship.
Termination Hearing
inCompliance?
moveToTerminate?
File Motion to Modify for
Permanent Custody
Yes No
45 days before
PMC Setting
transferConservatorship? File Motion to Modify to
No Determine Transfer Managing Modification Hearing
Conserv atorship to Parent (PMC Setting)
Yes
Yes
No
Yes
No
Manage Juries
Prov ide Cour troom
Security
(from Family)
(from Family)
(from Family)
(from Family)
Bal iff
Call to Order
(from Family)
(from Family)
Court Reporter Use Cases
The high-level processes identified for Court Reporter include the following:
Court Coordinator
Record Pr oceedings
Track Exhibits
(from Family)
(from Family)
Court Reporter
Contact Attorneys
Correspondence
(from Family)
(from Family)
JV Court Reporter: Record Proceeding
uc JV_CR_Record Proceeding
Report i n Person
Create Backups
Record Pr oceedings
Court Reporter
(from Family)
(from District Court Actors)
uc JV_CR_Track Exhibits
Track Exhibits
Court Reporter
(from Family)
(from District Court Actors)
JV Court Reporter: Process Transcript Requests
Receiv e Request
Retriev e Exhib its or
Exhibi t List
Court Reporter
(from Family)
(from District Court Actors)
The high-level processes identified for Court Coordinator included the following:
«include»
(from Family)
(from Family)
Manag e Court
Genera te & Mail Appointed Juv enile
Noti ces Print & Distr ibute Attorney Database
Doc ket
(from Family)
(from Family) «dependency»
(from Family)
Assign Court
Appointed Attorney
Generate Reports
(from Family)
Proces s Appo inted
Correspondence Coordin ate Juv enile Attorney Inv oices (from Family)
Appeal Process
(from Family)
(from Family)
Select Appropriate
Template Form
Get Judge's
Signa ture
(from Family)
(from Family)
(from Family)
Send O rigina l to
Court Clerk
Distribute Copies
(from Family)
(from Family)
JV Court Coordinator: Maintain Attorney Vacation Schedule
Mainta in Attorney
Vacation Schedule
Court Coordinator
(from Family)
(from District Court Actors)
Proces s Appointed
Attorney Inv oices
Court Coordinator
(from Family) Submit P ay Vouchers to
(from District Court Actors) County Auditor for
Paym ent
Prepa re Juror
Submit Jury Panel
Certificates
Request
Court Coordinator
(from Family)
(from District Court Actors)
JV Court Coordinator: Order Interpreters
uc JVCCoordinator_Order Interpreters
Contact Interpreter
Order Interpreter
from Catholic
Chari ties
Determi ne Language
Nee ded
«extend»
«extend»
Manage Interns
Mana ge M isc
Proj ects
Court Coordinator
(from Family)
Assign Court
Appointed Attorney
Court Coordinator
Update Ca se Record
Manage Court
Appointed Juv enile Locate Appel late
«dependency» Attorney
Attorney Database
(from Family)
Prepa re Appeal
Pac ket
Establ ish Contact
Betw een Attorneys
Court Coordinator
(from Family)
(from District Court Actors)
JV Court Coordinator: Manage Court Appointed Attorney Database
Approv e Court
Appoitned Attorney
Applications
«dependency»
Submit Applic ation
for Court Appointed
Attorney
Manage Court
Appointed Juv enile
Attorney Database
uc JVCCoordinator_Generate Reports
Set up Queri es to
Retriev e Data Update Spreads heets
w ith New Data
Generate Reports
Court Coordinator
(from Family)
(from District Court Actors)
uc JVCCoordinator_Manage Dockets
Prepa re We ekly
Docke t Lis t &
Create Doc ket Rev iew s Sheet
Cale ndar
Distribute Docket
Court Coordinator
(from Family)
(from District Court Actors)
JPD Court Clerk & Associate Court Clerk (At Juvenile Probation Department)
uc Juv enile Court Clerk Use Cases
Process P etitions
Maintai n Logs
Handl e Problem
Petitions & Jackets
Juv enile Associate Court
Clerk
(from District Court Actors)
Enter Hear ing
Results in KIDS
Prepare E OM Report
Approv e Vacation
JPD Court Clerk: Prepare Order Documents
Prepar e Probable
Cause Docs
«extend» «extend»
Prepare J udgments
«extend»
«extend»
«extend»
Prepa re Or der
Docum ents
Access KIDS
JPD
Court Clerk: Manage Detention Docket
Manage Detention
Doc ket
«extend» «extend»
«extend»
Judgeme nt Withheld «extend» List of Red Flags
Log Rece iv ed or
«extend» «extend»
«extend» Disapprov ed
«extend»
«extend» «extend»
Seal Log
Maintai n Logs «extend»
«extend»
ILOG «extend» «extend» «extend»
Direc tiv e to
«extend» «extend» Apprehend Log
Detenti on Log
Recei v e Intake
Report from PO
FileMar k & Se nd to
DA Office
Proce ss Gr een
She ets
JPD
Court Clerk: Process Case Sealings:
uc JVCClerk_Process Sealings
D.A. O ffice
Associate Judge (from District Court Actors)
Delete PDAU & SETD
(from District Court Actors) Scre ens
Make Copies
Sign O rders
JPD Probation Officer Use Cases:
View Docket
Probation Officer
View Docket
Generate Reports
D.A. O ffice
(from District Court Actors)
View I maged
Docum ents
View Party Info
D.A. O ffice
(from District Court Actors)
DA: Generate Reports
uc DA_Generate Reports
Generate Reports
D.A. O ffice
uc DA_View Docket
View Docket
D.A. O ffice
uc DA_Run Queries
View Results
Execute Query
Print Results
D.A. O ffice
(from District Court Actors)
Associate Judge Use Cases
The high-level processes identified for Associate Judge included the following:
(from Family)
View Party Details
(from Family)
View Attorney
Data base
Update Doc ket
She ets
(from Family)
(from Family)
Sign O rders
Make Cas e Notes
(from Family)
(from Family)
District Judge Use Cases
The high-level processes identified for District Judge included the following:
Presi de ov er
Presi de ov er
Certificati on Hearing
Contested
Associate Judge Termination Hearings
(from District Court Actors)
Distric t Judge
Approv e All
Associate Judge
Administrativ e Orders
Proj ects