Improvement of Quality of Software Requirements with Requirements Ontology

Dzung, Dang Viet; Ohnishi, Akira

doi:10.1109/qsic.2009.44

Cited by 21 publications

(7 citation statements)

References 9 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…UML is a most popular semi-formal notation for software development now, and there are some challenges to introduce quality requirements into it [25], [26]. Using ontology, dictionary and/or thesaurus [27] is one of the useful ways to improve the quality of requirements with respect to semantic aspect. Most of them do not focus on comparison between as-is (measured) and to-be (recommended) quality requirements like our proposal.…”

Section: Related Workmentioning

confidence: 99%

Finding Incorrect and Missing Quality Requirements Definitions Using Requirements Frame

Kaiya

Ohnishi

2012

IEICE Trans. Inf. & Syst.

Self Cite

View full text Add to dashboard Cite

SUMMARYDefining quality requirements completely and correctly is more difficult than defining functional requirements because stakeholders do not state most of quality requirements explicitly. We thus propose a method to measure a requirements specification for identifying the amount of quality requirements in the specification. We also propose another method to recommend quality requirements to be defined in such a specification. We expect stakeholders can identify missing and unnecessary quality requirements when measured quality requirements are different from recommended ones. We use a semi-formal language called X-JRDL to represent requirements specifications because it is suitable for analyzing quality requirements. We applied our methods to a requirements specification, and found our methods contribute to defining quality requirements more completely and correctly.

show abstract

Section: Related Workmentioning

confidence: 99%

Finding Incorrect and Missing Quality Requirements Definitions Using Requirements Frame

Kaiya

Ohnishi

2012

IEICE Trans. Inf. & Syst.

Self Cite

View full text Add to dashboard Cite

show abstract

“…Understanding requirements does not only mean to trace them but also defining them in a clear state in order to become easy for the practitioners to use them. Many other models like model based testing process to determine traceability, win-win spiral model, Requirement Ontology to improve quality in the requirements are proposed to acquire a well defined requirement which is useful for a software project in a long run [8][9].…”

Section: Validation and Analysismentioning

confidence: 99%

Mitigation strategies to Major challenges Faced in Market Driven Development Scenario

Engu¹

2012

IJSEA

View full text Add to dashboard Cite

show abstract

“…UML is a most popular semiformal notation for software development now, and there are some challenges to introduce quality requirements into it [22], [23]. Using ontology, dictionary and/or thesaurus [24] is one of the useful ways to improve the quality of requirements with respect to semantic aspect. Most of them do not focus on comparison between as-is (measured) and to-be (recommended) quality requirements like our proposal.…”

Section: Related Workmentioning

confidence: 99%

Quality Requirements Analysis Using Requirements Frames

Kaiya

Ohnishi

2011

2011 11th International Conference on Quality Software

Self Cite

View full text Add to dashboard Cite

Defining quality requirements completely and correctly is more difficult than defining functional requirements because stakeholders do not state most of quality requirements explicitly. We thus propose a method to measure a requirements specification for identifying the amount of quality requirements in the specification. We also propose another method to recommend quality requirements to be defined in such a specification. We expect stakeholders can identify missing and unnecessary quality requirements when measured quality requirements are different from recommended ones. We use a semi-formal language called X-JRDL to represent requirements specifications because it is suitable for analyzing quality requirements. We applied our methods to a requirements specification, and found our methods contribute to define quality requirements more completely and correctly.

show abstract

Improvement of Quality of Software Requirements with Requirements Ontology

Cited by 21 publications

References 9 publications

Finding Incorrect and Missing Quality Requirements Definitions Using Requirements Frame

Finding Incorrect and Missing Quality Requirements Definitions Using Requirements Frame

Mitigation strategies to Major challenges Faced in Market Driven Development Scenario

Quality Requirements Analysis Using Requirements Frames

Contact Info

Product

Resources

About