KEY TERMS

Business Model: A model of a company that shows
the company’s function in the world, what it does, how
and when. It is designed to serve the needs of one or more
types of handlers, and it should contain the information
these handlers need “ no more and no less (Marshall,
1999).
Conceptual Model: A mental model that allows under-
standing and simplification of the problem. The purpose
of domain modeling is to contribute to an understanding
of the system’s context, and thereby also to understand-
ing of the system’s requirements as they originate from
this context. The system’s internal way of solving this
problem will be dealt with in the analysis, design and
implementation workflows (Jacobson, Booch, &
Rumbaugh, 1999).
Rational Unified Process: A use case driven, archi-
tecture-centric, iterative and incremental software devel-
opment process that uses UML to describe the artifacts
(Jacobson, Booch, & Rumbaugh, 1999).
Requirements: Defined during the early stages of a
system development as a specification of what should be
implemented. They are descriptions of how the system
should behave, application domain information, con-
straints on the system’s operation, or specifications of a
system property or attribute. Sometimes they are con-
straints on the development process of the system
(Kotonya & Sommerville, 1998).
Requirements Traceability: The ability to define,
capture and follow the traces left by requirements on other
elements of the software development environment and
the traces left by those elements on requirements (Pinheiro,
2000).
Stakeholder: People or organizations who will be
affected by the system and who have a direct or indirect
influence on the system requirements. They include end-
users of the system, managers and others involved in the
organizational processes influenced by the system, engi-
neers responsible for the system development and main-
tenance, customer of the organization who will use the
system to provide some services, external bodies such as
regulators or certification authorities (Kotonya &
Sommerville, 1998).
Unified Modeling Language (UML): A standard
graphical language for visualizing, specifying, construct-
ing, and documenting the artifacts of a software-intensive
system (Booch, Rumbaugh, & Jacobson, 1999).