Computer Science ›› 2015, Vol. 42 ›› Issue (12): 65-70.

Previous Articles     Next Articles

Safety Requirements Description Method Based on RUCM

WU Xue, LIU Chao and WU Ji   

  • Online:2018-11-14 Published:2018-11-14

Abstract: Safety requirements have commanded increasing attention as software is playing a more and more important role in today’s safety critical systems.The extraction and description of software safety requirement are the key element of the whole software safety work.The subsequent software design and realization and test process will reference to software safety requirement.Nevertheless,most safety requirements are described in ordinary functional specification,lack of independent and normative description,especially the relationship between safety requirements and fault,failure.As a result,there is little practical guidance on how to describe safety requirements.So this paper designed a safety requirements specification-Safety RUCM,which is based on restricted use case modeling RUCM,and extended its specification template and restriction rules by adding fault specification and data specification in order to support the fault related information.We used this specification to describe an operating system safety requirement.Result shows that this specification is practicable.

Key words: Safety requirements,Restricted use case modeling,Data dictionary,Fault

[1] Hauge H J.A Survey of Software Safety[R].Trondheim:Department of Computer and Information Science at the Norwegian University of Science and Technology,2001
[2] Wu W H,Kelly T.Safety tactics for software architecture design[C]∥Proc.of the 28th Annual Int’l Computer Software and Applications Conf.2004
[3] Software Considerations in Airborne Systems and EquipmentCertification:RTCA DO-178C[S].Washington DC:RTCA,Inc,2011
[4] International Electrotechnical Commission.Functional safety of electrical/electronic/programmable electronic safety-related systems-Part 2:Requirements for electrical/electronic/programmable electronic safety systems:IEC-61508[S].London:International Electrotechnical Commission,2010
[5] Requirements for safety related software defence equipment indefence equipment:Def Stan 00-55[S].UK:Ministry of Defence,1997
[6] J unwei D,X Zhong-wei,M Meng.Verification of Scenario-Based Safety Requirement Specification on Components Composition[C]∥2008 International Conference on Computer Science and Software Engineering.IEEE,2008,2:686-689
[7] Navarro,Elena,Sanchez P,et al.A goal-oriented approach for safety requirements specification[C]∥ 13th Annual IEEE International Symposium and Workshop on Engineering of Computer Based Systems,2006(ECBS 2006).2006:27-30
[8] Bounds A C.Safety requirements specification for new safetysystems in older nuclear facilities in the UK[C]∥6th IET International Conference on System Safety.2011:1-5
[9] Jo H-J,Uiwang R,Hwang J-G.Formal Requirements Specification in Safety-critical Railway Signaling System[M]∥Transmission & Distribution Conference & Exposition:Asia and Pacific.2009.2009:26-30
[10] Troubitsyna E.Elicitation and specification of safety require-ments[C]∥Proc.of the 3rd Int’l Conf.on Systems.IEEE Computer Society,2008:202-207
[11] Yue Tao,Briand L C,Labiche Y.A Use Case Modeling Approach to Facilitate the Transition Towards Analysis Models:Concepts and Empirical Evaluation[M]∥Model Driven Enginee-ring Languages and Systems.Springer Berlin Heidelberg,2009:484-498
[12] Yue Tao,Briand L C,Labiche Y.Automatically Deriving a UML Analysis Model from a Use Case Model[M].Carleton University,2010
[13] Yue Tao,Briand L C,Labiche Y.Automatically Deriving UML Sequence Diagrams from Use Cases:Technical Report[R].Carleton University,Canada,2010
[14] Yue Tao,Briand L C,Labiche Y.Facilitating the Transitionfrom Use Case Models to Analysis Models:Approach and Experiments[J].ACM Transactions on Software Engineering and Methodology (TOSEM),2013,22(1):5
[15] Li Yun-xi,Shi Lei,Ren Xiao-rui.Design and Iimplementation of Process Managemen In Partition [J].Aeronautical Computing Technique,2005,5(4):12-15

No related articles found!
Viewed
Full text


Abstract

Cited

  Shared   
  Discussed   
No Suggested Reading articles found!