![](bg4.png)
3. Registers, containing supporting information
These registers are part of any major information
system. Common patterns what describe their
structure have been worked out and have been
published as patterns (Hay, 1996), (Fowler, 1997).
– Register of documents what contain information
about patterns or what have been used to create
or complement patterns. Patterns of documents
data model (Hay, 1996, p. 205-234) can be used
to develop the structure of this register.
– Register of parties (persons and organizations)
who have some role in the events, which have
happened or have been scheduled to happen with
patterns. Patterns of domain models about parties
(Fowler, 1997, p. 24-27) can be used to develop
the structure of this register.
– Register of planned and happened events, which
have happened with patterns (for example
creation, review or modification of a pattern).
Patterns of proposed and implemented actions
(Fowler, 1997, p. 158-160) can be used to
develop the structure of this register. For each
event next data will be stored: time of an event;
reference to the parties who participated in the
event, together with the information about their
roles in the event; references to the documents
what where used during the event, together with
the information about their roles in the event.
– Register of queries, what users of PMS have
constructed and stored for later usage by them or
other interested parties.
3 CONCLUSION AND FUTURE
In this paper, principles of Pattern Management
System (PMS) were presented. PMS could help find
solutions to the problems and store evolving
knowledge in the form of patterns. Author proposes,
that meta-data about structure of patterns and
database of patterns must guide the operation of
PMS in order to manage different types of patterns.
PMS must manage both narratives and information
extracted from models. It makes possible to use
query capabilities of existing database management
systems to search patterns based on model elements.
Future work will involve the development of
methods for searching patterns. Search based on user
evaluations should take into account the amount of
evaluations and quality of experts who make them.
One expert could evaluate patterns in regard to some
attributes many times. If lot of experts have changed
their opinion recently in one direction, then it could
also be taken into account.
One promising methods is to search patterns
according to semantic similarity. For example during
requirements analysis functional requirements to the
system are documented using use cases. Data model
can be constructed by searching data modeling
pattern which model elements (entities, attributes
and associations) have the biggest semantic
similarity to subset of the use case text.
REFERENCES
Backlund, P., & Jonasson, I., 2002. 'Patterns as a Means
for Managing Knowledge in the Information Systems
Engineering Process', in BalticDB&IS 2002, vol. 2,
eds H. M. Haav & A. Kalja, Tallinn Technical
University, Tallinn, pp. 15-25.
Baskerville, R., & Stage, J., 2001. 'Accommodating
emergent work practices: etnographic choice of
method fragments', in Realigning Research and
Practice in Information Systems Development: The
Social and Organizational Perspective, eds N. L.
Russo, B. Fitzgerald & J. I. DeGross, Kluwer
Academic Publishers, pp. 11-28.
Fowler, M., 1997. Analysis Patterns: Reusable Object
Models, Addison Wesley, Calif.
Gaedke, M., & Rehse, J., 2000. 'Supporting compositional
reuse in component-based Web engineering',
Proceedings of the 2000 ACM symposium on Applied
computing. Retrieved 17 Oct. 2003 from ACM digital
library.
Halaris, J., & Geroupoulus, S.T., 1996. 'Reuse Concepts
and a Reuse Support Repository', IEEE Symposium
and Workshop on Engineering of Computer Based
Systems, pp. 27-34. Retrieved 18 Aug. 2003 from
IEEE Xplore.
Hay, D. C., 1996. Data model patterns: conventions of
thought, Dorset House Pub, New York.
Marco, D., 2000. Building and Managing the Meta Data
Repository: A Full Lifecycle Guide, John Wiley &
Sons, USA.
Sugumuran, V., & Storey, V.C., 2003. 'A semantic-based
approach to component retrieval', ACM SIGMIS
Database, vol. 34, issue 3, pp.8-24. Retrieved 17 Oct.
2003 from ACM digital library.
Pattern and Component Markup Language. Draft 3.
Retrieved June 19 2003 from
http://www.objectventure.net/files/docs/PCMLSpecifi
cation.pdf
ICEIS 2004 - INFORMATION SYSTEMS ANALYSIS AND SPECIFICATION
658