Abstract
achieving highly reliable software from the customer's perspective is a demanding job for all software engineers and reliability engineers. Consequently, reliability may be defined by the user's requirements. In addition, specifications are the basis for software development. Therefore, all means applicable ought to substantiate the specifications concerning requirements. To specifically and succinctly define the reliability, specifications must be written in formal and highly expressive language. Formal ontologies enable use of automated consistency checking of the software system with respect to declarative specifications. Therefore, we have proposed Ontology based protocol (OntoReliability) for developing software specifications in support of reliability advancement. We also present examples from the practice of our protocol that constitutes description, preconditions, post conditions, standard course, proxy course, exceptions, inclusions, primacy, rate of uses, exceptional requirements and remarks and concerns. This, conversely, necessitates revealing the benefits of implementing an OntoReliabilty protocol. Keywordsliability Protocol, OntoRelSpecifications
Published Version (
Free)
Talk to us
Join us for a 30 min session where you can share your feedback and ask us any queries you have
Schedule a call