Assessing the Quality of Software Requirements Specifications for Automotive Software Systems

Takoshima, Akiyuki; Aoyama, Mikio

doi:10.1109/apsec.2015.57

Cited by 10 publications

(6 citation statements)

References 8 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…Synonym topic library for the similarity between the standard topic in the IEEE 830 table of content are build. The translation matrix is used to solve the structural issue in SRS document [2].…”

Section: A Structuralmentioning

confidence: 99%

“…The result from the case study would be discussed further below in Table 2. Method to calculate the topic similarity with IEEE 830 topic is adopted in study [2]. However, this prototype automates the pattern-matching process which limit the human error.…”

Section: Fig 4 Graph Number Of Topicsmentioning

confidence: 99%

“…The general properties would reflect the quality of the SRS document itself. It is important to consider that software developer meet the quality properties as the document tend to be shared among different level of the organization [2]. Two criteria need to be considered in writing the SRS [3].…”

Section: Introductionmentioning

confidence: 99%

See 2 more Smart Citations

Evaluation of Software Requirement Specification Based on IEEE 830 Quality Properties

Stephen

Mit

2020

Int. J. Adv. Sci. Eng. Inf. Technol.

View full text Add to dashboard Cite

Software requirement specification (SRS) documented an essential requirement of software and its external interface. Many studies found the quality of SRS, but lack of the informality organizing of document and representation of functional requirement. This paper aims to evaluate the quality properties of the software requirement specification (SRS). There are four quality properties to be assessed, which are completeness, correctness, preciseness, and consistency. Completeness quality is used to evaluate the structure of the SRS document; meanwhile, the other three qualities used to evaluate the functional requirement. The measurement for each quality properties has been proposed in the previous study. The evaluation process involves a few stages. In short, the prototype would extract text through the provided document, do a calculation, and came out with the result in the form of a similarity percentage. The prototype designs in such ways it minimizes the user interference. Those resulted in reducing human error. Corpus contains libraries of term and topic are expected to increase the reliability of detection. The corpus includes topics extracted from IEEE 830 standard, vague word, terms represent Create, Read, Update, and Delete (CRUD) operation, and terms denote possible datatype. The extracted functional requirement would be refined based on the Requirement Boilerplate (RB) template. RB adopted in the study to ensure the consistency of functional refinement requirements. The percentage of similarity is determined based on comparison with IEEE 830 standard. The rate of the result of each quality properties reflects the quality of the software requirement specification.

show abstract

Section: A Structuralmentioning

confidence: 99%

Section: Fig 4 Graph Number Of Topicsmentioning

confidence: 99%

See 1 more Smart Citation

Evaluation of Software Requirement Specification Based on IEEE 830 Quality Properties

Stephen

Mit

2020

Int. J. Adv. Sci. Eng. Inf. Technol.

View full text Add to dashboard Cite

show abstract

“…All such failures are due to misunderstandings while interpreting stakeholder's ambiguous requirements. e SRS document is considered unambiguous only if there is only one possible meaning for each software requirement [12].…”

Section: Introductionmentioning

confidence: 99%

An Intelligent Analytics Approach to Minimize Complexity in Ambiguous Software Requirements

Ashfaq

Bajwa

Kazmi

et al. 2021

Scientific Programming

View full text Add to dashboard Cite

An inconsistent and ambiguous Software Requirement Specification (SRS) document results in an erroneous/failed software project. Hence, it is a serious challenge to handle and process complex and ambiguous requirements. Most of the literature work focuses on detection and resolution of ambiguity in software requirements. Also, there is no standardized way to write unambiguous and consistent requirements. The goal of this research was to generate an ambiguity-less SRS document. This paper presents a new approach to write ambiguity-less requirements. Furthermore, we design a framework for Natural Language (NL) to Controlled Natural Language (CNL) (such as Semantic Business Vocabulary and Rules (SBVR)) transition and develop a prototype. The prototype also generates Resource Description Framework (RDF) representation. The SBVR has a shared meaning concept that minimizes ambiguity, and RDF representation is supported by query language such as SPARQL Protocol and RDF Query Language (SPARQL). The proposed approach can help software engineers to translate NL requirements into a format that is understandable by all stakeholders and also is machine processable. The results of our prototype are encouraging, exhibiting the efficient performance of our developed prototype in terms of usability and correctness.

show abstract

“…o-TaS 3 is one of the most studied Peierls conductors with a single Peierls transition at T P ≈ 220 K and with completely gaped Fermy surface. * e-mail: mina cplire@mail.ru As a result, below T P the temperature dependence of the ohmic conductance along the chain axis, G(T ), obeys an activation law with activation energy E ∆ ≈ 800 K. It is known that G(T ) begins to deviate from the initial activation law at T T P /2, a new activation energy being smaller [5], while the perpendicular conductance preserves the initial value E ∆⊥ ≈ 800 K in all lowtemperature range. G(T ) curve shape at T 100 K is known to be highly dependent on sample qualityimpurity contents and degrees of structural perfection.…”

Section: Introductionmentioning

confidence: 99%

Photoconduction in the Peierls conductor monoclinic TaS3

Minakova

Nasretdinova

Zaĭtsev-Zotov

2015

Physica B: Condensed Matter

View full text Add to dashboard Cite

Photoconduction in the monoclinic phase of quasi-one-dimensional conductor TaS 3 has been observed at T < 70 K. It was studied jointly with low-temperature ohmic and non-linear dark conduction. The strong sample quality dependence of both photoconduction and dark conduction at this temperature region has been observed. Together with a similarity of the main features of the photoconduction characteristic of both monoclinic (m-TaS 3 ) and orthorhombic (o-TaS 3 ) samples the following new peculiarities of photoconduction in m-TaS 3 were found: 1) the dependence of the activation energy of photoconduction on temperature, T , 2) the change of the recombination mechanism from the linear type to the collisional one at low T with a sample quality growth, 3) the existence of a fine structure of the electric-field dependence of photoconduction. Spectral study gives the Peierls energy gap value 2∆ * = 0.18 eV.

show abstract

Assessing the Quality of Software Requirements Specifications for Automotive Software Systems

Cited by 10 publications

References 8 publications

Evaluation of Software Requirement Specification Based on IEEE 830 Quality Properties

Evaluation of Software Requirement Specification Based on IEEE 830 Quality Properties

An Intelligent Analytics Approach to Minimize Complexity in Ambiguous Software Requirements

Photoconduction in the Peierls conductor monoclinic TaS3

Contact Info

Product

Resources

About