skip to main content
research-article

Towards a specific software development process for high integrity systems

Published:24 January 2011Publication History
Skip Abstract Section

Abstract

The software development process is the main tool of project management. It serves to plan optimally all activities related to the production of software. It is mainly a scheduling policy of these activities which allows to control and to follow them in time.We moved here toward an adaptation of the RUP for real-time systems. First, our approach is to enrich the current process with other phases, secondly, we consider that the requirements of strategic type must be completely identified, specified, verified since they are those which lead all the development; last, we are redefining the lifecycle which puts the models of highest level of abstraction (analysis, architecture) as the main objectives to reach. The enrichment of the development process relates to additional phases and a parallelization of its sub-processes. The software development process that we propose is subdivided into three sub-processes whose principal is led by the strategic use cases. This allows a seamless development, involving intermediate languages to move gradually from the informal to the formal and provides the opportunity to compose languages of different types.

References

  1. Sebastien Gerard, Peter Feiler, JF Rolland, Mamoun Filali, Marc-Olivier Reiser, Didier Delanote, Yolande Berbers, Laurent Pautet, and Isabelle Perseil. UML&AADL '2007 Grand Challenges. ACM SIGBED Review, A Special Report on UML&AADL Grand Challenges, 4(4), october 2007. Google ScholarGoogle ScholarDigital LibraryDigital Library
  2. Ivar Jacobson, Grady Booch, and James E Rumbaugh. Excerpt from "The Unified Software Development Process": The Unified Process. IEEE Software, 16(3):82--90, 1999.Google ScholarGoogle Scholar
  3. Philippe Kruchten. The Rational Unified Process: An Introduction, Third Edition. Object Technology Series. Addison-Wesley Longman Publishing Co., Inc., Boston, MA, USA, 2003. Google ScholarGoogle ScholarDigital LibraryDigital Library
  4. Leslie Lamport. Specifying Systems: The TLA+ Language and Tools for Hardware and Software Engineers. Addison-Wesley Professional, Jul 2002. Google ScholarGoogle ScholarDigital LibraryDigital Library
  5. Leslie Lamport. The +CAL Algorithm Language. In +CAL, Jul 2006.Google ScholarGoogle Scholar
  6. Object Management Group (OMG). Software & Systems Process Engineering Meta-Model Specification, v2.0 (SPEM 2.0), April 2008.Google ScholarGoogle Scholar
  7. OMG. A UML Profile for MARTE: Modeling and Analysis of Real-Time Embedded systems, Beta 3, ptc/09-05-13. http://www.omg.org/cgi-bin/doc?ptc/09-05-13, May 2009.Google ScholarGoogle Scholar
  8. Sam Owre, John M. Rushby, and Natarajan Shankar. PVS: A Prototype Verification System. In CADE-11: Proceedings of the 11th International Conference on Automated Deduction, pages 748--752, London, UK, 1992. Springer-Verlag. Google ScholarGoogle ScholarDigital LibraryDigital Library
  9. Richard F. Paige. Case Studies in Using a Meta-Method for Formal Method Integration. In Michael Johnson, editor, AMAST, volume 1349 of Lecture Notes in Computer Science, pages 395--408, Sydney, Australia, December 1997. Springer. Google ScholarGoogle ScholarDigital LibraryDigital Library
  10. Isabelle Perseil and Laurent Pautet. A Co-Modeling Methodology Designed for RT Architecture Models Integration. In 12th International Conference on Engineering of Complex Computer Systems, ICECCS, pages 371--376, Auckland, New Zealand, July 2007. IEEE Computer Society. Google ScholarGoogle ScholarDigital LibraryDigital Library
  11. Isabelle Perseil and Laurent Pautet. A Concrete Syntax for UML 2.1 Action Semantics Using + CAL. In IEEE Computer Society, editor, 13th IEEE International Conference on Engineering of Complex Computer Systems (ICECCS 2008), pages 217--221, april 2008. Google ScholarGoogle ScholarDigital LibraryDigital Library
  12. Isabelle Perseil and Laurent Pautet. Foundations of a new software engineering method for real-time systems. Innovations in Systems and Software Engineering, 4(3):195--202, September 2008.Google ScholarGoogle ScholarCross RefCross Ref
  13. Isabelle Perseil and Laurent Pautet. An Emerging Need for a New Software Engineering Method. In IEEE Computer Society, editor, 14th IEEE International Conference on Engineering of Complex Computer Systems (ICECCS 2009), pages 359--364, june 2009. Google ScholarGoogle ScholarDigital LibraryDigital Library
  14. James E. Rumbaugh. What is a Method? JOOP, 8(6):10--16, 26, 1995.Google ScholarGoogle Scholar
  15. SAE AS-2C Architecture Description Language Subcommittee.Google ScholarGoogle Scholar
  16. T. Vergnaud, B. Zalila, and J. Hugues. Ocarina: a Compiler for the AADL. Technical report, Télécom Paris, 2006.Google ScholarGoogle Scholar

Index Terms

  1. Towards a specific software development process for high integrity systems

        Recommendations

        Comments

        Login options

        Check if you have access through your login credentials or your institution to get full access on this article.

        Sign in

        Full Access

        PDF Format

        View or Download as a PDF file.

        PDF

        eReader

        View online with eReader.

        eReader