Nothing Special   »   [go: up one dir, main page]

skip to main content
research-article

Process-oriented abstraction of the complex evolvable systems: problem model construction

Published: 01 May 2008 Publication History

Abstract

Architectural design and lifecycle management of complex Evolvable Systems encounter contexts and environments in which ambiguity and volatility are of essence. Ambiguity relates to the content of the information the architect has available at the time of the design and maps to the aspects, dimensions and boundaries of the system. Volatility represents constant changes of vision, knowledge and information due to the advances in science or techniques of handling and demands the architect to redesign the system to match the new realities of the time. As a result, the nature of the complex Evolvable Systems introduces serious challenges to the conventional Software Architecture and Software Engineering. This paper presents a new method called Nuclear-Process Oriented Analysis and Modeling (NPOAM), for the design of complex Open Evolvable Systems [1], and focuses on its implementation within the scope of the Problem Model construction [2] for a Cardiac Arrhythmia Management model. Our Problem Model construction develops its conceptualization on the premises of the complexities and requirements of scientific domains. Yet its applicability is not exclusive to scientific domains but since it is designed for more complex scientific environments, it is perfectly applicable to business domains as well. One of the critical contributions of NPOAM is providing the capability of random process modeling and design. The paper concludes with addressing the model analysis and verification issues.

References

[1]
Bastani, B., H. Bastani (Nov. 2007): High-level Open Evolvable Systems Design by Process-oriented Modeling: Application to DNA Replication Mechanism. ACM SIGSOFT Software Engineering Notes, Volume 32, Issue 6.
[2]
Bastani, B. (March 2007): A Requirements Analysis Framework for Open Systems Requirements Engineering. ACM SIGSOFT Software Engineering Notes, Volume 32, Issue 2.
[3]
http://www.merriam-webster.com/dictionary/methodology.
[4]
Brooks, F. (April 1987): No Silver Bullet: Essence and Accidents of Software Engineering. Computer (IEEE Computer Society Press), Volume 20 Issue 4.
[5]
Jackson, M. (1995): Software Requirements & Specifications. New York, New York: The ACM Press.
[6]
Booch, G., et al. (1999): The Unified Modeling Language User Guide. New York, New York: Addison-Wesley.
[7]
Vargas-Solar, G., et al. (Sep. 2004): Toward Aspect Oriented Services Coordination for Building Modern Information Systems. Proceedings of the Fifth Mexican International Conference, pp 353--360. Digital Object Identifier 10.1109/ENC.2004.1342627.
[8]
Ambler, S. (2004): The Object Primer. Cambridge, UK: Cambridge University Press.
[9]
Microsoft MSDN Library: Introduction to Windows Service Applications. http://msdn2.microsoft.com/enus/library/d56de412(VS.80).aspx.
[10]
OASIS Reference Model for Service Oriented Architecture: http://www.oasisopen.org/committees/tc_home.php?wg_abbrev=soa-rm.
[11]
Erl, T. (2004): Service-Oriented Architecture. Saddle River, NJ: Prentice Hall PTR. ISBN: 0131428985.
[12]
http://www.sei.cmu.edu/architecture/.
[13]
Bass, L., et al. (1998): Software Architecture in Practice. Reading, Massachusetts: Addison Wesley.
[14]
Fielding, R. (2000): Architectural Styles and the Design of Network-based Software Architectures. PhD Dissertation. University of California, Irvine, California.
[15]
Shaw, M., P. Clements (Oct. 1996): Toward Boxology: Preliminary Classification of Architectural Styles. Proceedings of the Second International Software Architecture Workshop (ISAW-2), San Francisco, California.
[16]
Taylor, R., et al. (June 1996): A Component-based Architectural Style for GUI Software. IEEE Transactions on Software Engineering, 22(6).
[17]
Di Nitto, E., D. Rosenblum (May 1999): Exploiting ADLs to specify architectural styles induced by middleware infrastructures. Proceedings of the 21st International Conference on Software Engineering, Los Angeles, California, pp. 13--22. ISBN: 1-58113-074-0.
[18]
Perry, D., A. Wolf (Oct. 1992): Foundations for the Study of Software Architecture. ACM SIGSOFT Software Engineering Notes, Volume 17, Issue 4, pp. 40--52.
[19]
Shaw, M., P. Clements (Aug. 1997): A Field Guide to Boxology: Preliminary Classification of Architectural Styles for Software Systems. Proceedings of the Twenty-First Annual International Computer Software and Applications Conference (COMPSAC'97), Washington, D.C., pp. 6--13.
[20]
Garlan, D., M. Shaw (1993): An Introduction to Software Architecture. Advances in Software Engineering and Knowledge Engineering, Volume I, World Scientific Publishing Co., New Jersey.
[21]
Mikic-Rakic, M., et al. (2002): Architectural Style Requirements for Self-healing Systems. Proceedings of the first workshop on Self-healing systems, Charleston, South Carolina. ISBN: 1-58113-609-9.
[22]
The 6th International Conference on Evolvable Systems, ICES 2005: http://147.83.49.249:8090/.
[23]
Dellarocas, C., et al. (1998): An Architecture for Constructing Self-evolving Software Systems. Proceedings of the third international workshop on Software architecture, Orlando, Florida, USA.
[24]
Fischer, G. (1998): Seeding, Evolutionary Growth and Reseeding: Constructing, Capturing and Evolving Knowledge in Domain-Oriented Design Environments. Automated Software Engineering, 5(4): pp. 447--464.
[25]
Buschmann, F., et al. (1996): A System of Patterns. New York, New York: Wiley. ISBN: 0471958697.
[26]
Gamma, E., et al. (1995): Design Patterns. Reading, Massachusetts: Addison-Wesley. ISBN: 0201633612.
[27]
Zimmermann, O., et al. (2003): Perspectives on Web Services. Springer-Verlag Berlin Heidelberg New York. ISBN: 3540009140.
[28]
Arlow, J., et al. (2005): UML 2 and the Unified Process. Addison Wesley. ISBN: 0321321278.
[29]
Kholkar, D., et al. (May 2005): Visual Specification and Analysis of Use Cases. SoftVis 2005: Proceedings of the 2005 ACM symposium on Software visualization.
[30]
Meyer, B. (1997): Object-Oriented Software Construction. Upper Saddle River, NJ: Prentice Hall PTR. ISBN: 0136291554.
[31]
Jacobson, I., et al. (1992): Object-Oriented Software Engineering: A Use Case Driven Approach. Addison-Wesley Professional.
[32]
Stroustrup, B. (1991): The C++ Programming Language. Reading, Massachusetts: Addison-Wesley. ISBN: 0201539926.
[33]
Ellis, J. (1994): Objectifying Real-Time Systems. New York, New York: SIGS Books. ISBN: 0962747785.
[34]
http://www.ncbi.nlm.nih.gov/sites/entrez.
[35]
Tortora, G, Amitrano, R. (2001): Anatomy and Physiology, Laboratory Manual. Upper Saddle River, NJ: Prentice Hall. ISBN: 0130896705.
[36]
http://www.peacehealth.org/kbase/topic/detail/other/te7526/detail. htm.
[37]
Tortora, G., Derrickson, B., (2006): Principles of Anatomy and Physiology. New York, New York: Wiley. ISBN: 0471689343.
[38]
http://www.nlm.nih.gov/medlineplus/ency/article/003868.htm.
[39]
http://www.306.ibm.com/software/integration/wbimodeler/library/.

Cited By

View all
  • (2015)Model-Based System Specification With Tesperanto: Readable Text From Formal GraphicsIEEE Transactions on Systems, Man, and Cybernetics: Systems10.1109/TSMC.2015.240675345:11(1448-1458)Online publication date: Nov-2015
  • (2012)Software architecture challenges in evolvable systemsProceedings of the 2012 ACM SIGSOFT symposium on Industry Day10.1145/2304636.2304641(9-10)Online publication date: 27-Jun-2012
  • (2009)Complex open-system design by quasi-agentsACM SIGSOFT Software Engineering Notes10.1145/1543405.154341234:4(1-14)Online publication date: 6-Jul-2009

Recommendations

Comments

Please enable JavaScript to view thecomments powered by Disqus.

Information & Contributors

Information

Published In

cover image ACM SIGSOFT Software Engineering Notes
ACM SIGSOFT Software Engineering Notes  Volume 33, Issue 3
May 2008
85 pages
ISSN:0163-5948
DOI:10.1145/1360602
Issue’s Table of Contents

Publisher

Association for Computing Machinery

New York, NY, United States

Publication History

Published: 01 May 2008
Published in SIGSOFT Volume 33, Issue 3

Check for updates

Author Tags

  1. abstractions
  2. architectural style
  3. complex systems
  4. conceptual modeling
  5. design
  6. design patterns
  7. evolvable systems
  8. framework
  9. method
  10. methodologies
  11. modeling
  12. open systems
  13. process-oriented modeling
  14. requirements analysis
  15. requirements and architecture modeling
  16. reuse
  17. software architecture
  18. software engineering
  19. specification

Qualifiers

  • Research-article

Contributors

Other Metrics

Bibliometrics & Citations

Bibliometrics

Article Metrics

  • Downloads (Last 12 months)1
  • Downloads (Last 6 weeks)0
Reflects downloads up to 26 Sep 2024

Other Metrics

Citations

Cited By

View all
  • (2015)Model-Based System Specification With Tesperanto: Readable Text From Formal GraphicsIEEE Transactions on Systems, Man, and Cybernetics: Systems10.1109/TSMC.2015.240675345:11(1448-1458)Online publication date: Nov-2015
  • (2012)Software architecture challenges in evolvable systemsProceedings of the 2012 ACM SIGSOFT symposium on Industry Day10.1145/2304636.2304641(9-10)Online publication date: 27-Jun-2012
  • (2009)Complex open-system design by quasi-agentsACM SIGSOFT Software Engineering Notes10.1145/1543405.154341234:4(1-14)Online publication date: 6-Jul-2009

View Options

Get Access

Login options

View options

PDF

View or Download as a PDF file.

PDF

eReader

View online with eReader.

eReader

Media

Figures

Other

Tables

Share

Share

Share this Publication link

Share on social media