Transcript Kein Folientitel

Identifying Types of ExtraFunctional Requirements
in the Context of BPS Systems
Elke Hochmüller
[email protected]
Carinthia Tech Institute, Klagenfurt
REBPS'03 Workshop
Austria, June 2003
Extra-Functional Requirements
 Extra-functional requirements (EFRs) are constraints
regarding
 quality (usability, performance, security, maintainability, ...)
 economics (time, cost, ...)
of
 process components
 product components
 We learned from traditional software system
development:
 EFRs are "wicked" requirements
REBPS‘03
Elke Hochmüller
2
Characteristics of BPS Systems
 Process orientation
 other way of working/thinking, culture change
 Close tie to the organization
 deep impact, everybody uses it on regular basis, smooth integration
 Large scale
 coordination of complex tasks
 Integration feature
 different agents/departments, interface between software systems
 Process control
 monitoring, metrics
 Process adjustments
 changes in environment (business, legal, infrastructure)
REBPS‘03
Elke Hochmüller
3
Hypotheses
 EFR types can act as indicators for key requirement
areas to be addressed in each business process support
project
 Do not assume that a tool would somehow magically
deal with them on its own!
 Systems will at best provide some framework for their
implementation
 EFRs have to be stated explicitly (for designers,
implementers,QA)
 database analogy (concurrency, transactions)
 Pure reliance on the tool/environment to meet
requirements is often equivalent to ignoring them
altogether
REBPS‘03
Elke Hochmüller
4
Types of EFRs for BPS (1)
 BPS Systems are here to stay!
 Key to support the new organizational culture
 Can‘t get rid of them without major casualties
 A BPS system must be able to tolerate and survive and
even facilitate organizational changes.
This means:
 The BPS system must cope with new situations
 There must be a „trustworthy“ operating base
 It must be used!
REBPS‘03
Elke Hochmüller
5
Types of EFRs for BPS (2)
 The BPS system must cope with new situations




Flexibility, changeability, extensibility
Traceability
Reusability
Prototyping or Simulation Facility
 There must be a „trustworthy“ operating base




Scalability
Technical availability and reliability
Commercial availability and reliability
Security and privacy
 It must be used!
 Usability
REBPS‘03
Elke Hochmüller
6
Q(&A?)
 How to elicit more information about these requirements
 for BPS in general?
 specific to the general organizational setting?
 specific to the current project?
 Elicitation templates for types of EFRs?
 Who are the stakeholders
 for types of EFRs?
 for actual requirements instances of EFR types?
 How can EFRs be integrated in BPS projects?
 responsibilities
 integration with business process modelling
 Risk assessment? Pilot projects!
 development process issues
 revolution vs. evolution
REBPS‘03
Elke Hochmüller
7