Implementation of decision modules

S. Roubtsov; E.E. Roubtsova

doi:10.1145/2630768.2630775

Implementation of decision modules

S. Roubtsov
, E.E. Roubtsova

Research output: Chapter in Book/Report/Conference proceeding › Conference contribution › Academic › peer-review

Abstract

Separation of concerns can have different forms. The well accepted concern is an object behavior usually specified as a life cycle module. In this paper, we define another type of concern, a decision module, and identify it in requirements and models. Separation of decision modules in programs may improve traceability of requirements and simplify code analysis. We present the results of our experiments with implementation of decision modules. We implement the modules using object composition, reflection, the publisher-subscriber design pattern and aspects. We present the possibilities of different implementation forms and illustrate our observations of pros and cons with an example of a document submission system. Keywords: Decision Module, Requirement, Model, Program, Protocol Contracts

Original language	English
Title of host publication	6th Workshop on Behaviour Modelling - Foundations and Applications (BM-FA'14, York, UK, July 22, 2014)
Place of Publication	New York NY
Publisher	Association for Computing Machinery, Inc.
Pages	7/1-10
ISBN (Print)	978-1-4503-2791-6
DOIs	https://doi.org/10.1145/2630768.2630775
Publication status	Published - 2014
Event	conference; 6th Workshop on Behaviour Modelling-Foundations and Applications; 2014-07-22; 2014-07-22 - Duration: 22 Jul 2014 → 22 Jul 2014

Conference

Conference	conference; 6th Workshop on Behaviour Modelling-Foundations and Applications; 2014-07-22; 2014-07-22
Period	22/07/14 → 22/07/14
Other	6th Workshop on Behaviour Modelling-Foundations and Applications

Access to Document

10.1145/2630768.2630775

Cite this

@inproceedings{610e3d8f6cfd41d5ab6d342b82bbd1b6,

title = "Implementation of decision modules",

abstract = "Separation of concerns can have different forms. The well accepted concern is an object behavior usually specified as a life cycle module. In this paper, we define another type of concern, a decision module, and identify it in requirements and models. Separation of decision modules in programs may improve traceability of requirements and simplify code analysis. We present the results of our experiments with implementation of decision modules. We implement the modules using object composition, reflection, the publisher-subscriber design pattern and aspects. We present the possibilities of different implementation forms and illustrate our observations of pros and cons with an example of a document submission system. Keywords: Decision Module, Requirement, Model, Program, Protocol Contracts",

author = "S. Roubtsov and E.E. Roubtsova",

year = "2014",

doi = "10.1145/2630768.2630775",

language = "English",

isbn = "978-1-4503-2791-6",

pages = "7/1--10",

booktitle = "6th Workshop on Behaviour Modelling - Foundations and Applications (BM-FA'14, York, UK, July 22, 2014)",

publisher = "Association for Computing Machinery, Inc.",

address = "United States",

note = "conference; 6th Workshop on Behaviour Modelling-Foundations and Applications; 2014-07-22; 2014-07-22 ; Conference date: 22-07-2014 Through 22-07-2014",

}

Roubtsov, S & Roubtsova, EE 2014, Implementation of decision modules. in 6th Workshop on Behaviour Modelling - Foundations and Applications (BM-FA'14, York, UK, July 22, 2014). Association for Computing Machinery, Inc., New York NY, pp. 7/1-10, conference; 6th Workshop on Behaviour Modelling-Foundations and Applications; 2014-07-22; 2014-07-22, 22/07/14. https://doi.org/10.1145/2630768.2630775

TY - GEN

T1 - Implementation of decision modules

AU - Roubtsov, S.

AU - Roubtsova, E.E.

PY - 2014

Y1 - 2014

N2 - Separation of concerns can have different forms. The well accepted concern is an object behavior usually specified as a life cycle module. In this paper, we define another type of concern, a decision module, and identify it in requirements and models. Separation of decision modules in programs may improve traceability of requirements and simplify code analysis. We present the results of our experiments with implementation of decision modules. We implement the modules using object composition, reflection, the publisher-subscriber design pattern and aspects. We present the possibilities of different implementation forms and illustrate our observations of pros and cons with an example of a document submission system. Keywords: Decision Module, Requirement, Model, Program, Protocol Contracts

AB - Separation of concerns can have different forms. The well accepted concern is an object behavior usually specified as a life cycle module. In this paper, we define another type of concern, a decision module, and identify it in requirements and models. Separation of decision modules in programs may improve traceability of requirements and simplify code analysis. We present the results of our experiments with implementation of decision modules. We implement the modules using object composition, reflection, the publisher-subscriber design pattern and aspects. We present the possibilities of different implementation forms and illustrate our observations of pros and cons with an example of a document submission system. Keywords: Decision Module, Requirement, Model, Program, Protocol Contracts

U2 - 10.1145/2630768.2630775

DO - 10.1145/2630768.2630775

M3 - Conference contribution

SN - 978-1-4503-2791-6

SP - 7/1-10

BT - 6th Workshop on Behaviour Modelling - Foundations and Applications (BM-FA'14, York, UK, July 22, 2014)

PB - Association for Computing Machinery, Inc.

CY - New York NY

T2 - conference; 6th Workshop on Behaviour Modelling-Foundations and Applications; 2014-07-22; 2014-07-22

Y2 - 22 July 2014 through 22 July 2014

ER -

Implementation of decision modules

Abstract

Conference

Access to Document

Fingerprint

Cite this