Lightweight Systems Engineering with ISO 29110 and Eclipse
Small organizations would like to use standards for systems development, using affordable tools. Recently, ISO 20110 evolved as a lightweight standard, while Eclipse tools are generally free of charge. But barriers of entry are still high, due to insufficient documentation and limited functionalities. To change this, we started the Teaching Systems Engineering* initiative, which aims to address these issues. Join this talk to see first-hand how ISO 20110-based system engineering can be practiced with Eclipse tools.
As the Eclipse ecosystem around systems engineering grows, it gets more and more attractive to small companies, as they see a compelling alternative to expensive commercial tools. But once the try to get started, they get quickly frustrated as there is little guidance on how to apply the various tools. For large organizations, guidance comes in the form of Standards like ISO 15288 "Systems and software engineering -- System life cycle processes". Such standards are powerful, but require a large up-front investment. ISO 29110 is a tailored-down standard, specifically for "VSEs" - Very Small Entities, meaning companies and teams with fever than 25 members. Further, ISO 29110 " is not intended to preclude the use of different life cycles such as: waterfall, iterative, incremental, evolutionary or agile." So in contrast to the large standards, you can leave the dreaded waterfall behind. In this session, you will learn how Eclipse can be used to breathe life into ISO 29110: We start by making it accessible with the Eclipse Process Framework (EPF). With this, we can visualize the workflow and individual tasks, allowing users to navigate the process with ease. Next, we will show a small case study, realized with Eclipse and ISO 29110. Requirements are captured with Eclipse RMF, with a data model built with EMF. A small excursus shows how for larger projects, Papyrus could be used for UML modeling instead. We will cover code generation and test stub generation, ultimately closing the cycle with manual acceptance tests, again modeled with RMF. While this resembles the V-Model, we demonstrate how smart change management allows an iterative, more agile work style.
*Note: There is a lot of activity that is not reflected by the website, so please don't judge the talk by the state of it. The project website will receive a significant overhaul in September 2015, which is timely enough for EclipseCon, but too late for the reviewers of this proposed talk.