Improving software systems by Flow Control Analysis

• Autorzy: Poznański P. , Wawrowski M.
• Języki publikacji: EN

Abstrakty

EN

Using agile methods during the implementation of the system that meets mission critical requirements can be a real challenge. The change in the system built of dozens or even hundreds of specialized devices with embedded software requires the cooperation of a large group of engineers. This article presents a solution that supports parallel work of groups of system analysts and software developers. Deployment of formal rules to the requirements written in natural language enables using formal analysis of artifacts being a bridge between software and system requirements. Formalism and textual form of requirements allowed the automatic generation of message flow graph for the (sub) system, called the “big-picture-model”. Flow diagram analysis helped to avoid a large number of defects whose repair cost in extreme cases could undermine the legitimacy of agile methods in projects of this scale. Retrospectively, a reduction of technical debt was observed. Continuous analysis of the “big picture model” improves the control of the quality parameters of the software architecture. The article also tries to explain why the commercial platform based on UML modeling language may not be sufficient in projects of this complexity.

Słowa kluczowe

EN

software engineering; architecture definition; requirements management; testing; agile; systems modeling

• Wydawca: Wydawnictwa AGH
• Czasopismo: Computer Science
• Rocznik: 2012
• Tom: Vol. 13 (2)
• Strony: 81--92
• Opis fizyczny: Bibliogr. 14 poz., rys., tab.

Twórcy

autor

Poznański P.

• Institute of Teleinformatics, CUT Kraków

autor

Wawrowski M.

• Motorola Solutions, Kraków

Bibliografia

• [1] George H. Fairbanks; Just Enough Software Architecture: A Risk-Driven Approach Marshall & Brainerd, 2010
• [2] Scott W. Ambler; The Object Primer: Agile Model-Driven Development with UML 2.0;Cambridge University Press; 2004
• [3] Bruce Powel Douglass; Real-Time Agility: The Harmony/ESW Method for for Real-Time and Embedded Systems Development (Kindle Edition); Addison- Wesley Professional, 2009.
• [4] Bruce Powel Douglass; Real Time UML Workshop for Embedded Systems (Embedded Technology); Newnes, 2006
• [5] Robert L. Nord,Mario R. Barbacci,Paul Clements,Rick Kazman,Mark Klein, Liam O’Brien, James E. Tomayko; Integrating the Architecture Tradeoff Analysis Method (ATAM) with the Cost Benefit Analysis Method (CBAM); Carnegie Mellon University, 2004
• [6] Cheng A.M.K.: Real-Time Systems: Scheduling, Analysis, and Verification. John Wiley & Sons, 2002
• [7] Porter A.; Accelerated Testing and Validation. Elsevier, 2004
• [8] Wayne P. Stevens, Glenford J. Myers, Larry L. Constantine: Structured Design ( IBM Systems Journal, 13 (2), 115-139, 1974 IBM Systems Journal, 13 (2), 115-139, 1974)
• [9] Bruza, P. D., Van der Weide, Th. P.:The Semantics of Data Flow Diagrams, University of Nijmegen, 1993
• [10] Morris, M. G., Speier, C. and Hoffer, J. A. (1999), An Examination of Procedural and Object-oriented Systems Analysis Methods: Does Prior Experience Help or Hinder Performance?. Decision Sciences, 30: 107-136. doi: 10.1111/j.1540- 5915.1999.tb01603.x
• [11] Samek, M. (2006). UML Statecharts at $10.99. Dr.Dobbs Journal, May 24, 2006
• [12] Bass, Len, Clements, Paul and Kazman, Rick: Software Architecture in Practice, 2nd edition.Addison-Wesley, 2003 Improving software systems by Flow Control Analysis 91
• [13] P. Poznanski, M. Wawrowski, J. Smagłowski. Trendy rozwoju architektury aplikacji osadzonych na systemach czasu rzeczywistego. KKIO, 2011
• [14] Mark Dalgarno, Matthew Fowler: “UML vs. Domain-Specific Languages”, Methods & Tools – Summer 2008