Enhanced V-Model
DOI:
https://doi.org/10.31449/inf.v42i4.2027Abstract
Typically, software development processes are time consuming, expensive, and rigorous, particularly for safety-critical applications. Even if guidelines and recommendations are defined by sector-specific functional safety standards, development process may not be completed because of excessive costs or insufficient planning. The V-model is one of the most well-known software development lifecycle model. In this study, the V-model lifecycle is modified by adding an intermediate step. The proposed modification is realized by checking the fault diagnosability of each module. The proposed modification provides three advantages: (1) it checks whether the constructed model covers all software requirements related with faults; (2) it decreases costs by early detection of modeling deficiencies before the coding and testing phases; and (3) it enables code simplicity in decision of fault occurrence.References
IEC61508 (2010). Functional safety of electrical/electronic/programmable electronic safety-related systems, Parts 1–7. International Electrotechnical Commission.
Rook P (1986). Controlling Software Projects. Software Engineering Journal, 1, pp. 7-16.
IEC 61508-4 (2010). Functional safety of electrical/electronic/programmable electronic safety-related systems, Part 4: Definitions and Abbreviations. International Electrotechnical Commission.
Munassar NM, Govardhan A (2010). A Comparison Between Five Models of Software Engineering. International Journal of Computer Science Issues, 7, pp. 94-101.
Krishna ST, Sreekanth S, Perumal K, Kumar Reddy KR (2012). Explore 10 Different Types of Software Development Process Models. International Journal of Computer Science and Information Technologies, 3:4580-4584.
Royce WW (1970). Managing the Development of Large Software Systems: Concepts ad Techniques. Proceedings Wescon, pp. 1-9.
Boehm BW (1988). A Spiral Model of Software Development and Enhancement. Computer, 21, pp. 61-72.
Lehman MM (1980). Programs, Life Cycles, and Laws of Software Evolution. Proceedings of the IEEE, 68, pp. 1060-1076.
Rahman RA, Pulm U, Stetter R (2007). Systematic Mechatronic Design of a Piezo-Electric Brake. 16th International Conference on Engineering Design, 28-31 July, Paris, France, pp. 1-12.
Märtin L, Schatalov M, Hagner M, Goltz U, Maibaum O (2013). A Methodology for Model-Based Development and Automated Verification of Software for Aerospace Systems. IEEE Aerospace Conference, 2-9 March, Big Sky, MT, USA, pp. 1-19.
Scippacercola F, Pietrantuono R, Russo R, Zentai A (2015). Model-Driven Engineering of a Railway Interlocking System. 3rd Int Conf on Model-Driven Eng and Soft Development, 2-9 September, Angers, France, pp pp. 509-519.
SSG-39 (2016). Design of Instrumentation and Control Systems for Nuclear Power Plants. IAEA Safety Standards Series.
Kwiatkowska M, Norman G, Parker D (2002). PRISM: Probabilistic Symbolic Model Checker. Field T, Harrison PG, Bradley J, Harder U (ed) Computer Performance Evaluation: Modeling Techniques and Tools, Lecture Notes in Computer Science, Springer, Berlin, Heidelberg, pp. 200-204.
Holzmann GJ (2003). Spin model checker, the: primer and reference manual. Addison-Wesley.
BS EN 50128 (2011). Railway Applications-Communication, Signalling and processing systems: Software for railway control and protection systems. International Electrotechnical Commission.
IEC 61508-3 (2010). Functional safety of electrical/electronic/programmable electronic safety-related systems, Part 3: Software Requirements. International Electrotechnical Commission.
Ratcliffe A (2011). SAS Software Development with the V-Model. 3SAS Global Forum, Coder's Corner, 4-7 April, Las Vegas, Nevada, USA, pp. 1-9.
Brat GP (2017). Reducing V&V Cost of Flight Critical Systems: Myth or Reality? AIAA Information Systems, AIAA SciTech Forum, American Institute of Aeronautics and Astronautics, 9-13 January, Grapevine, Texas, USA, pp. 1-10.
Boehm BW (1984). Verifying and Validating Software Requirements and Design Specifications. IEEE Software, 1, pp. 75-88.
Boehm BW (1984). Software Engineering Economics. IEEE Transactions on Software Engineering, SE-10, pp. 4-21.
Boehm BW (1987). Industrial Software Metrics: A Top Ten List. IEEE Software, 4, pp. 264-271.
Haskins B, Stecklein J, Dick B, Moroney G, Lovell R, Dabney J (2004). Error Cost Escalation Through the Project Life Cycle. 14th Annual Int Symp, Int Council on Systems Engineering, 19-24 June, Toulouse, France, pp. 1723-1737.
Schneider GM, Martin J, Tsai WT (1992). An Experimental Study of Fault Detection in User Requirements Documents. IACM Transactions on Software Engineering and Methodology, 1, pp. 188-204.
Cassandras CG, Lafortune S (2008). Introduction to Discrete Event Systems. Springer, New York.
Sampath M, Sengupta R, Lafortune S, Sinnamohideen K, Teneketzis D (1995). Diagnosability of discrete-event systems. IEEE Trans on Automatic Control, 40, pp. 1555-1575.
Ushio T, Onishi I, Okuda K (1998). Fault detection based on Petri net models with faulty behaviours. International Conference on Systems, Man, and Cybernetics, 11-14 October, San Diego, CA, USA, pp. 113-118.
Sampath M, Sengupta R, Lafortune S, Sinnamohideen K, Teneketzis D (1996). Failure diagnosis using discrete-event models. IEEE Transactions on Control Systems Technology, 4, pp. 105-124.
Murata T (1989). Petri nets: Properties, analysis and applications. Proceedings of the IEEE, 77, pp. 541-580.
Li ZW, Zhou MC, Wu NQ (2008). A survey and comparison of Petri net-based deadlock prevention policies for flexible manufacturing systems. IEEE Trans on Systems, Man, and Cybernetics, Part C: Applications and Reviews, 38, pp. 173–188.
Chung SL (2005). Diagnosing PN-based models with partial observable transitions. International Journal of Computer Integrated Manufacturing, 18, pp. 158-169.
Durmuş MS, Takai S, Söylemez MT (2014). Fault Diagnosis in Fixed-Block Railway Signaling Systems: A Discrete Event Systems Approach. IEEJ Transactions on Electrical and Electronic Engineering, 9, pp. 523-531.
Downloads
Published
How to Cite
Issue
Section
License
I assign to Informatica, An International Journal of Computing and Informatics ("Journal") the copyright in the manuscript identified above and any additional material (figures, tables, illustrations, software or other information intended for publication) submitted as part of or as a supplement to the manuscript ("Paper") in all forms and media throughout the world, in all languages, for the full term of copyright, effective when and if the article is accepted for publication. This transfer includes the right to reproduce and/or to distribute the Paper to other journals or digital libraries in electronic and online forms and systems.
I understand that I retain the rights to use the pre-prints, off-prints, accepted manuscript and published journal Paper for personal use, scholarly purposes and internal institutional use.
In certain cases, I can ask for retaining the publishing rights of the Paper. The Journal can permit or deny the request for publishing rights, to which I fully agree.
I declare that the submitted Paper is original, has been written by the stated authors and has not been published elsewhere nor is currently being considered for publication by any other journal and will not be submitted for such review while under review by this Journal. The Paper contains no material that violates proprietary rights of any other person or entity. I have obtained written permission from copyright owners for any excerpts from copyrighted works that are included and have credited the sources in my article. I have informed the co-author(s) of the terms of this publishing agreement.
Copyright © Slovenian Society Informatika
