Case Study about Formal and Informal Specifications through an Industrial
Abstract: In this paper, we discuss a case study in which we have taken a problem from industry and specified it both in B and UML. The object of our case study is the teletext module of a new generation TV. We have discussed our experience, and presented an analysis of both the specifications. We found that, in order to specify a real-time event-driven system, some amount of formality is necessary, which UML does not usually provide. Our industrial collaborators are considering changing their specification process basedon our findings.
Introduction: In this paper, we perform a comparative study of formal specifications and informal specifications. We have taken a medium size system from a project in industry, and have specified it both formally and informally. For the formal specification, we used B [Abr 96] as the specification language, and for the informal specification, we used UML [Boo 99]. Our most important conclusion is that UML is not sufficient to specify requirements, which may be complex and rigorous in nature. Some amount of formality is necessary to take care of particularly complex issues. Conversely we found that the UML was helpful for visualising the structure of the models compared with a formal specification. keep reading..
Case Study about Architecture-based Software Reliability Analysis: Large-Scale Industrial
Abstract: Architecture-based software reliability analysis methods shall help software architects to identify critical software components and to quantify their inﬂuence on the system reliability. Although researchers have proposed more than 20 methods in this area, empirical case studies applying these methods on large-scale industrial systems are rare. The costs and beneﬁts of these methods remain unknown. On this behalf, we have applied the Cheung method on the software architecture of an industrial control system from ABB consisting of more than 100 components organized in nine subsystems with more than three million lines of code.
Introduction: Software reliability is deﬁned as the ability of a software system to operate without failures. Analyzing software reliability during early design stages bears the potential for signiﬁcant cost savings of future testing activities. Researchers have proposed several architecture-based software reliability analysis (ABSRA) methods. They allow to predict system reliability based on formal, stochastic software models (e. g., Markov chains). Using these models, developers can identify critical software components and quantify their inﬂuence on the overall system reliability to optimize future testing activities.
This paper describes the main design choices of a software process improvement course. The course is organized around an industrial case study. In addition it is based on lectures and group exercises. The case study is centered around four questions: Why is process improvement important [in your company]? Which processes does your company have? Which improvement initiatives does your company implement? Which relationships exist between software improvement and software quality? During the case study, the students come in contact with actors from the local software industry. This paper gives an evaluation of the work and shows how the authors were able to provide real examples from the Norwegian software industry. Read more…
Abstract: Globalization and rapid evolving of Internet and Web-based technologies have revolutionized the product development process. Engineering a product is a complex process involving the integration of distributed resources, such as human beings, engineering tools, and a large variety of product-related information systems. Software agents have been playing an increasingly important role in this area to reduce the need for large, complex, and centralized systems. This paper presents the results of an industrial case study in the development of a collaborative e-Engineering environment for mechanical product design engineering by applying intelligent software agents, Internet/Web, workflow, and database technologies. Click here to read more…