![](bg4.png)
perform business practice in an integrated model. A
more focused modelling might give more value in
fewer models. This assumption is based on the
nature of development processes. A system
development is dependent on knowledge from diffe-
rent stakeholders who want to spend as little time as
possible in a useful manner. Christiansson &
Christiansson, 2004 a)
By using an integrated core business process
model we enable the possibility to:
– Ease the difficulty to state and to communicate
requirements by found those in daily practice.
– Handle the natural uncertainty and lack of
understanding regarding software requirements
by found those in daily practice.
6 CONCLUSIONS
In the increasingly competitive software industry the
need for new innovative techniques to deliver
satisfying software systems is greater than ever. This
may in some sense explain the great belief and
adaptation of new techniques, strategies and/or tools
that are made out to be the great solution to the
different problems that the software industry is
facing. We believe that by combining business
process modelling with software component
specifications, we have a solution that addresses and
handle many fundamental problems with software
development. This core model can be used as an
enabler of acquisition. The barriers between business
analysis and systems development can be mended by
embedding focus on software components within the
business process model. By using a business model
that integrates essential knowledge concerning
actions in business processes and software
components ability to support, gives new innovative
ways to perform business actions, and new ways to
handle management of component-based
information systems. With our approach we avoid
treating business development and information
systems development as separate issues, and instead
regard them as one integrated task. We believe that
using an integrated core model we can capture
essential knowledge concerning software component
requirements based on the desired business
processes expressed by people who run and perform
business practice. We can also facilitate the fact that
software requirements change at the same time as
the business change and a core business process
model can be used without the time consuming job
to update a lot of related documents. A core business
process model may serve as a basis to enter deeply
in related models to capture knowledge but with
different motives, perspectives and purposes than
software component acquisition.
REFERENCES
Beck, K. (2000) Extreme Programming Explained,
Addison Wesley Longman, Inc., California, Menlo
Park, USA.
Christiansson, M-T. (2001) Business modeling in inter-
organisational cooperation – what to describe, why
and how? in Nilsson, A. G. & Pettersson, J. S. (Eds.)
On Methods for Systems Development in Professional
Organisations – The Karlstad University Approach to
Information Systems and its Role in Society,
Studentlitteratur, Lund.
Christiansson, B. & Christiansson, M-T. (2003) The
Missing Approach for Component Specification, in
Assar, S., Semmak, F. & Barkhi, R. (Eds.)
Proceedings of 1:st International Workshop on
Component-Based Business Information Systems
Engineering (CBBISE'03), 2 September, Geneva.
Christiansson, M-T. Christiansson, B. (2004 a) Extreme
Modeling – Less is More, Proceedings of IRMA 2004,
23-26 May, New Orleans (forthcoming).
Christiansson, M-T. Christiansson, B. (2004 b) A Generic
Framework for a Software Component Specification –
founded in Business Processes, (submitted paper).
Hammer, M. (1990) “Reengineering Work: Don’t
Automate, Obliterate”, Harvard Business Review, Vol.
59, No. 4, pp.104-112.
Heineman, G. T. Councill, W. T. (2001) Component-
Based Software Engineering Putting the Pieces
Together, Addison Wesley Longman, Inc., California,
Menlo Park, USA.
Langefors, B. (1973) Theoretical Analysis of Information
Systems, 4:th ed., Studentlitteratur, Lund.
Langefors, B. (1995) Essays on Infology – Summing up
and Planning for the Future, Studentlitteratur, Lund.
Nellborn, C. (1999) Business and Systems Development:
Opportunities for an Integrated Way-of-Working, in
Nilsson, A G. Tolis, C. Nellborn, C. (Eds.)
Perspectives on Business Modelling – Understanding
and Changing Organisations, Springer-Verlag, Berlin.
Steel, J. (1996) Component Technology Part I An IDC
White Paper, Proc. Int. Data Corporation, London.
Szyperski, C. (2002) Component Software Beyond
Object-Oriented Programming, Addison Wesley
Longman, Inc., California, Menlo Park, USA.
Taylor, J. R. (1993) Rethinking the Theory of
Organizational Communication: How to Read an
Organization, Ablex Publishing, Norwood, New
Jersey.
Tolis, C. Nilsson, A. G. (1996) Using Business Models in
Process Orientation, in: Lundeberg, M. & Sundgren B.
(eds.). Advancing Your Business – People and
Information Systems in Concert, Studentlitteratur,
Lund.
ICEIS 2004 - INFORMATION SYSTEMS ANALYSIS AND SPECIFICATION
650