Call for Paper - September 2020 Edition
IJCA solicits original research papers for the September 2020 Edition. Last date of manuscript submission is August 20, 2020. Read More

U2Z Framework for Improving the Readability of Requirements of Safety Critical Systems

Print
PDF
International Journal of Computer Applications
Foundation of Computer Science (FCS), NY, USA
Year of Publication: 2017
Authors:
Monika Singh, V. K. Jain
10.5120/ijca2017914387

Monika Singh and V K Jain. U2Z Framework for Improving the Readability of Requirements of Safety Critical Systems. International Journal of Computer Applications 168(6):6-11, June 2017. BibTeX

@article{10.5120/ijca2017914387,
	author = {Monika Singh and V. K. Jain},
	title = {U2Z Framework for Improving the Readability of Requirements of Safety Critical Systems},
	journal = {International Journal of Computer Applications},
	issue_date = {June 2017},
	volume = {168},
	number = {6},
	month = {Jun},
	year = {2017},
	issn = {0975-8887},
	pages = {6-11},
	numpages = {6},
	url = {http://www.ijcaonline.org/archives/volume168/number6/27877-2017914387},
	doi = {10.5120/ijca2017914387},
	publisher = {Foundation of Computer Science (FCS), NY, USA},
	address = {New York, USA}
}

Abstract

The aim of this paper is to present a framework which helps in accessing and improving the specification especially for Safety Critical System. This proposed framework takes use case diagram as input and produces a formal model of functional requirements as output. This formalization allows the developer to document a correct and complete specification which is the ultimate need for the reliable software. The more accurately the functional requirements are mentioned, the more reliable system will be implemented. In case of the Safety Critical System, correct and complete specifications are indeed. This paper discusses such an integrated framework. We rely on Z Notation for formalization. The further verification and validation of specification is done with Z/EVES.

References

  1. W. R Dunn, 2002. Practical Design of Safety-Critical Computer Systems, USA: Reliability Press.
  2. J. Burcsuk, 2007, "Development of safety related systems," in Strategic Technology, 2007. IFOST 2007. International Forum on 3-6 Oct. 2007, pp.564,569.
  3. S. Yang, N. Sang, G. Xiong, 2004. Safety Testing of Safety Critical Software Based on Critical Mission Duration. In 10th IEEE Pacific Rim International Symposium on Dependable Computing (PRDC'04 ), pp. 97-102.
  4. K. E. Wiegers, 2003. Software Requirements Microsoft Press.
  5. Object Management Group (OMG), 2003. OMG Unified Modeling Language Specification, version 1.5.
  6. G. Booch, J. Rumbaugh, and I. Jacobson, 1999. The Unified Modeling Language User Guide. Addison-Wesley.
  7. Groote, J.F., Osaiweran, A.A.H. and Wesselius, J.H. (2011) Benefits of Applying Formal Methods to Industrial Control Software. 1-10.
  8. Fulara, J. and Jakubczyk, K. (2010) Practically Applicable Formal Methods. Lecture Notes in Computer Science, 5901, 407-418.
  9. N. Amálio, S. Stepney, and F. Polack, 2004. "Formal Proof from UML Models", ICFEM, USA, pp 418-433, Springer.
  10. J. Michael Spivey, 2001. The Z Notation: A Reference Manual, Prentice Hall, Englewood Cliffs, NJ, 2nd Edition.
  11. Saaltink, M., 1999. The Z/EVES 2.0 User’s Guide, Technical Report TR-99-5493-06a, ORA Canada, One Nicholas Street, Suite 1208 - Ottawa, Ontario K1N 7B7 – CANADA.
  12. C. B. Jones, 1990. Systematic Software Development using VDM, In Prentice Hall.
  13. S. Schneider, 2001. B Method- an Introduction Palgrave, Cornerstones of Computing series.
  14. J. Guttag and J. J. Horning, 1978. The algebraic specification of abstract abstract data types, Acta Inform., vol. 10, pp. 27-52.
  15. C. A. R. Hoare, 1985. Communicating Sequential Processes, In Prentice Hall.
  16. Howard Bowman, 1998. A LOTOS based tutorial on formal methods for object-oriented distributed systems, New Generation Computing, Volume 16, Issue 4, pp 343-372.

Keywords

Critical systems, Formal specification, functional requirements, UML, Z Notation, Use case Diagram.