Software process modelling in EPOS

2Citations
Citations of this article
6Readers
Mendeley users who have this article in their library.

This article is free to access.

Abstract

EPOS1 is an instrumentable, kernel Software Engineering Environment (SEE). It consists of facilities for management of versioned products (configurations) through file-based workspaces attached to a versioned DBMS. EPOS will also manage the associated software development processes (tasks), being the subject of this paper. The EPOS-OOER semantic data model can describe deriver tools, human actors, tasks and subtasks, projects, and triggers/notifiers; as well as normal software products. EPOS-OOER incorporates object-oriented ERA modelling, extended with tasking (PRE, POST, CODE) and simple type constructors (FORMALS, DECOMPOSITION). Customization is done through versioning of task types in project-specific workspaces. Static task knowledge is expressed by types and subtyping, and is used for reasoning, planning, scheduling and execution of activities. Dynamic task knowledge is expressed by a versioned task network with a horizontal (temporal) and a vertical (decomposed) dimension. Tasks are connected to products by normal relationships.

Cite

CITATION STYLE

APA

Conradi, R., Lie, A., Osjord, E., Westby, P. H., Ambriola, V., Jaccheri, M. L., & Liu, C. (1990). Software process modelling in EPOS. In Lecture Notes in Computer Science (including subseries Lecture Notes in Artificial Intelligence and Lecture Notes in Bioinformatics) (Vol. 436 LNCS, pp. 109–133). Springer Verlag. https://doi.org/10.1007/BFb0000589

Register to see more suggestions

Mendeley helps you to discover research relevant for your work.

Already have an account?

Save time finding and organizing research with Mendeley

Sign up for free