Professional Documents
Culture Documents
Credit Agenc y
created or consumed by activities
Time and
Attendanc e
GPO
Scheduling Leave
Stereotype Automated and Manual Activity States
Management
We implemented stereotypes of Activity Diagrams to
represent automated and manual activities. The
automated activity state is depicted with a standard
white background and a manual activity is depicted
Figure 2: USCP Enterprise Context Diagram with a red background on the original colored diagram,
as shown in figure 3 below.
<<Manual>>
Each BAP depicted in figure 2 has a detailed Verify T&A
<<Automated>>
Perform Check In
description associated with it. For example, the T&A Certification Report
<<Automated>>
Perform Check In
Use Case:
Perform Check In
UC-TA-006-01 Reset application for next Check In
Ongoing Check in/out process:
Repeated for each employee each working day
<<Automated>>
Perform Check out
Use Case:
Perform Check Out
UC-TA-007-01 Use Case:
Perform close out pay period edits
UC-TA-010-01
creates
Specific : Employee
Use Case:
Release T&A Record for <<Automated>>
Release T&A Record for
Transmit
Transmit
UC-TA-015-01
Chec k In
Chec k Out
Officer Transmit Final T&A Recor d to NFC
NFC
Supervis or
Infor mati on T echnolog y
Admi nistrat or
Recruiting Application
Add Personnel Record
NFC
Supervisor
Line Organization
NFC
We are continuing to develop our enterprise [10] Booch, G., J. Rumbaugh, and I. Jacobson.
architecture ontology with additional elements using 1998. The Unified Modeling Language Reference
Manual, Addison-Wesley, Reading, MA.
UML 1.4 stereotyping and profiling mechanisms. We
are developing extensions to UML for the work, [11] Sowa, J. and Zachman, J. 1992. “Extending and
Information and Technical Infrastructure views well as Formalizing the Framework for Information Systems
the business and functional views discussed in this Architecture,” IBM Systems Journal, 31(3):590-616.
paper.
[12] OMG Unified Modeling Language Specification,
UML currently does not provide a mechanism for version 1.3, June 1999http://www.omg.org
modeling the content of interactions between actors.
We are investigating agent markup languages [13] US Capitol Police. 1999. Strategic Plan, Washington,
DC
(specifically DAML [17]), which are themselves
extensions of XML, as a mechanism for modeling [14] US Capitol Police. 2000. IT Strategic Plan, Washington,
interaction content. DAML provides a descriptive DC
mechanism for syntactic and semantic information.
This will also enable us to develop tools in the future [15] US Capitol Police. 2000. Technology Assessment,
that analyze properties of systems described through Washington, DC
DAML. We have also begun to investigate a better
mechanism for modeling the dynamic properties of [16] Zachman, J. 1987. "A Framework for Information
business systems through further extensions to UML. Systems Architecture." IBM Systems Journal, Vol. 26, no. 3,
IBM Publication G321-5298.
References
[17] DAML website, http://www.daml.org
[1] Armour, F., Kaisler, S., and S. Liu. 1999. A Big Picture
Look at Enterprise Architectures. IEEE IT Pro 1(1): 35-42 Acknowledgements
[2] Armour, F., Kaisler, S., and S. Liu. 1999. *We would like to acknowledge the work performed
Building an Enterprise Architecture Step-by-Step. on the OPSCO project, HSBC London, UK 2001 in
IEEE IT Pro 1(3):49-57 which several of the use case stereotyped actor
[3] Armour, F. and Kaisler, S. 2001. Building an concepts and icons represented in this paper were
Enterprise Architecture Step by Step, Part 2: Agile created. We specifically would like to thank: Maz Al-
Transition and Implementation. IEEE IT Pro, Shaikh-Ali, Charles Edwards, Giorgio L Mazza, and
Nov/Dec 2001. Luca Vetti Tagliati.
[4] Armour, F. and G. Miller. 2001. Advanced Use
Case Modeling: Software Systems, Addison-
Wesley, Reading, MA