Figure 3 - uploaded by Paulo Romero Martins Maciel
Content may be subject to copyright.
Source publication
Arterial oxygen saturation and heart rate measured by pulse oximetry is widely used to monitor critical care patients. This kind of system is classified as embedded hard real-time system and requires rigorous development methodologies to guarantee the correctness and timeliness of the application. Therefore, the proposed development methodology com...
Context in source publication
Context 1
... product management processes group is composed of the following processes: product requirements, project man- agement, bug tracking, sprint requirements, product line, and implementation priority. Figure 3 depicts the processes that are related to product management processes group. The product requirements process (that also belongs to the system platform processes group) aims to obtain the sys- tem's requirements (functional and non-functional) that must be part of the product. ...
Similar publications
We present an augmented reality application that can supplement a live video sequence with virtual labels associated with the scene content captured by an agile video camera moving inside an explored environment. The method proposed is composed of two main phases. First, a matching phase where reference images are successively compared with the cap...
This demonstration highlights the capabilities of the OpenAirInterface platform in terms of Agile RF spectrum-access and rapidly-deployable networking technologies. With respect to application scenarios, the latter target broadband public-safety communications. We demonstrate the real-time baseband and RF capabilities of the platform components as...
Citations
... 1. Creation of a new agile method: for example [18] report the development of a new agile method using XP and Scrum as well as organizational patterns as agile patterns. 2. Modifying the agile principles to suit embedded behavior: the authors of [19] modified the agile principles and created their own set principle. ...
Agile has been the subject of safety and critical domain in recent years. Emerging medical devices are highly relying on embedded software that runs on the specific platform in real time. The development of embedded software is different from ordinary software development due to the hardware-software dependency. Previous literature reviews discussed the challenges of bringing Agile practices to embedded software developments in general. This paper outlines the challenges and addresses the future work from medical embedded software development perspective.
... Studies S12 and S13 present the development of a digital softstarter [23] and of a induction motor simulator prototypes, respectively [24]. Besides that, studies S8 and S10 present the development of a pulse oximeter [19,21]. Moreover, studies S2, S6, S17, and S21 focused on the development of large embedded systems. ...
... This method is composed of practices from "traditional" software engineering and agile methods (in particular, Scrum and XP), and aims at minimizing the main problems in software development (i.e., requirement volatility and risk management), and of practices that are needed to achieve hardware and software development. TXM was also successfully applied in industry projects [19,21,23,24]. We also found a unique primary study (study S23) that investigates a specific software development phase, i.e., requirements engineering [31]. ...
Embedded systems are widely used in diverse areas, such as avionics, consumer electronics, and medical equipments, causing a considerable impact on modern society. Since these systems sometimes deal directly with human lives, and require a considerable level of quality, their development should be subject to a rigorous process. In another perspective, agile methods (or agile processes) have been adopted by the software industry as a lightweight, iterative, and collaborative approach for developing software systems. Although agile methods do not seem to be suitable to embedded systems, they have been successfully used for building such systems. However, there exists no detailed and analytical overview of the use of such methods in the embedded systems domain. The main objective of this paper is to present a detailed view of how agile methods have been used in the development of embedded systems, and to describe their benefits, challenges, and limitations. For this, we have applied Systematic Review, a technique for systematically exploring, organizing, summarizing, and assessing potentially all works conducted in a specific research area. As the main result, we have observed that agile methods have brought advantages to embedded systems development; however, more studies should be conducted. Furthermore, this work is also intended to contribute to the identification of important new research lines.
... Targeting the market of small interconnected CE devices, varying from interactive display panels and energy meters, to digital microphone and wireless 2D scanner applications, requires effort intensive software development activities that often create a bottleneck in the product life cycle, unless formal software engineering methodologies are followed, applications are ported in a variety of hardware platforms, and tested with several similar components before the final decisions are taken [3], [9]. And this has to be anticipated with the rapid changes imposed by the market needs, in terms of technology used and functionality provided [1], [6]. ...
The CE market demands such flexibility and fast results that the developer teams have serious difficulties to follow, unless they adopt a unique HW/SW platform and smoothly evolve it over time. However, this reasonable approach results to tying them up with their initial choices and the specific electronic components that they have modeled. In order to cope with this phenomenon, new SW architecture and design patterns that make possible the virtualization of hardware components are presented in this paper, and the experience of their application in the OS porting process is reported. Finally, it is explained why they can further contribute to the evolution of a platform independent CE application development paradigm.
... ology in order to get the benefits of agility while maintaining discipline around certain areas such as documentation. [15] implemented Agile (XP and Scrum) in Medtronic, a company developing class III medical device 4 software. They found that the practices of pair-programming and test-driven development provided early feedback and better quality. [16] discuss the successful implementation of Agile practices within Abbott " s diagnostic division, and concluded that: " …an agile approach is the approach best suited to development of FDA-regulated medical devices " . A strong endorsement indeed. [17] made use of a combination of XP, Scrum and Organisational Patterns to overcome system c ...
peer-reviewed Choosing the appropriate software development methodology is something which continues to occupy the minds of many IT professionals. The introduction of “Agile” development methodologies such as XP and SCRUM held the promise of improved software quality and reduced delivery times. Combined with a Lean philosophy, there would seem to be potential for much benefit. While evidence does exist to support many of the Lean/Agile claims, we look here at how such methodologies are being adopted in the rigorous environment of safety-critical embedded software development due to its high regulation. Drawing on the results of a systematic literature review we find that evidence is sparse for Lean/Agile adoption in these domains. However, where it has been trialled, “out-of-the-box” Agile practices do not seem to fully suit these environments but rather tailored Agile versions combined with more plan-based practices seem to be making inroads. SFI
... For this kind of system, the choice of the implementation architecture usually determines whether a given functionality is implemented as a hardware or software component. Due to the high pressure imposed by the market to launch new products coupled with evolving system's specification , semiconductor and system development companies are forced to choose flexible implementations where new products can quickly be built [7]. The increasing computational power and decreasing size and cost of processors, enables system's designers to move increasingly more functionalities to software [20] . ...
... Therefore, according to the business value (priority ) of the system's functionalities defined in the product backlog, we must first write the unit test for a given functionality and thereafter we must compile successfully the unit test before really writing the functionality's code. There are some benefits if we design and compile the unit test before writing the code [7]. These benefits fall into the following categories: (i) reflect about the design before coding the system functions, (ii) test the correctness of the functionalities by stressing and covering difficult scenarios, and (iii) achieve better results in terms of cyclomatic complexity v(φ) in order to facilitate the verification activities. ...
... These benefits fall into the following categories: (i) reflect about the design before coding the system functions, (ii) test the correctness of the functionalities by stressing and covering difficult scenarios, and (iii) achieve better results in terms of cyclomatic complexity v(φ) in order to facilitate the verification activities. Low cyclomatic complexity v(φ) levels (where φ means the CFG of the program) make white-box testing easier due to the fact that they decrease substantially the number of paths (i.e., the control flow) that should be tested to reasonably guard against errors [7]. After designing the tests and developing the ESW, the model translator converts the ESW and microprocessor model to BDDs (Binary Decision Diagrams) or CNF (Conjunctive Normal Form) formulas with the purpose of allowing the engineer to verify that certain system's properties hold in the model by using BDD-based or SAT-based model checking techniques. ...
In recent days, the complexity of software has increased significantly in embedded products in such a way that the verification of Embedded Software (ESW) now plays an important role to ensure the product's quality. Embedded systems engineers usually face the problems of verifying properties that have to meet the application's deadline, access the memory region, handle concurrency, and control the hardware registers. This work proposes a semiformal verification approach that combines dynamic and static verification to stress and cover exhaustively the state space of the system. We perform a case study on embedded software used in the medical devices domain. We conclude that the proposed approach improves the coverage and reduces substantially the verification time.
Safety critical embedded software is a software that needs to provide correct functionality to avoid loss of human life. Embedded software controls much of the functionalities in Medical, Automotive, Aerospace and Cyber-Physical-Systems. The development of embedded software is different from ordinary software development as such development needs to be coordinated with the hardware development. Additionally, regulation processes and audits are also in place before placing the products to market. The objectives of this study are to understand the challenges of embedded safety critical software development, to investigate agile practices which have been in use in the domain, the factors affecting agile implementation in embedded safety critical software development. We have performed a systematic review to achieve these objectives. Our review has identified challenges related to hardware development, team-based communication and regulation process. This paper outlines the result of the systematic review.
Context: Safety-critical software systems are increasingly being used in new application areas, such as personal medical devices, traffic control, and detection of pathogens. A current research debate is regarding whether safety-critical systems are better developed with traditional waterfall processes or agile processes that are purportedly faster and promise to lead to better products. Objective: To identify the issues and disputes in agile development of safety-critical software and the key qualities as found in the extant research literature. Method: We conducted a systematic literature review as an interpretive study following a research design to search, assess, extract, group, and understand the results of the found studies. Results: There are key issues and propositions that we elicit from the literature and combine into a conceptual model for understanding the foundational challenges of agile software development of safety-critical systems. The conceptual model consists of four problematic practice areas and five relationships, which we find to be even more important than the problematic areas. From this review, we suggest that there are important research gaps that need to be investigated. Conclusions: We suggest that future research should have a primary focus on the relationships in the resulting conceptual model and specifically on the dynamics of the field as a whole, on incremental versus iterative development, and on how to create value with minimal but sufficient effort.
Software development methods are attempting to offer an eager business community lightweight and faster solutions in the latest advancement in the software development world, which includes the practice of Cloud Computing, Service Oriented Engineering (SOE), and Agile and Lean approaches in software development.
