Enterprise Applications-Reference-Cited by-同舟云学术

Enterprise Applications

Published:2013 Issue: Volume: Page:96-117
ISSN:
Container-title:Aligning Enterprise, System, and Software Architectures
language:
Short-container-title:

Author:

Choppy Christine¹,Hatebur Denis²,Heisel Maritta²,Reggio Gianna³

Affiliation:

1. LIPN, University Paris 13, France

2. University Duisburg-Essen, Germany

3. Universita di Genova, Italy

Abstract

The authors provide a method to systematically develop enterprise application architectures from problem descriptions. From these descriptions, they derive two kinds of specifications: a behavioral specification describes how the automated business process is carried out. It can be expressed using activity or sequence diagrams. A structural specification describes the classes to be implemented and the operations they provide. The structural specification is created in three steps. All the diagrams are expressed in UML.

Publisher

IGI Global

Reference31 articles.

1. Alebrahim, A., Hatebur, D., & Heisel, M. (2011). A method to derive software architectures from quality requirements. In T. D. Thu & K. Leung (Eds.), Proceedings of the 18th Asia-Pacific Software Engineering Conference (APSEC) (pp. 322–330). IEEE Computer Society.

2. Barroca, L., Fiadeiro, J. L., Jackson, M., Laney, R. C., & Nuseibeh, B. (2004). Problem frames: A case for coordination. In Coordination Models and Languages, Proceedings 6th International Conference Coordination (pp. 5-19).

3. Bertrand, P., Darimont, R., Delor, E., Massonet, P., & van Lamsweerde, A. (1998). GRAIL/KAOS: An environment for goal driven requirements engineering. In ICSE’98 - 20th International Conference on Software Engineering.

4. Validating strategic alignment of organizational IT requirements using goal modeling and problem diagrams

5. Tropos: An Agent-Oriented Software Development Methodology