Requirements Traceability Model Generation for Evolving Software Systems

Philip, Milu Mary; Varma, R. V.; Balakrishn, Vijayakumar

doi:10.3923/jse.2017.282.289

Cited by 3 publications

(2 citation statements)

References 11 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…This unique product identification can provide information about the route of a product at the package level, and a good traceability system would provide critical information when a product recall is triggered (Marucheck et al, 2011). According to Viaene and Verbeke (1998), traceability is seen as a key instrument of the SCQM, as it improves product quality by ensuring that the product is being implemented based on stakeholder's requirements (Philip et al, 2017) However, the supply chain traceability is affected by the length and complexity of the supply network, and by extensive sub-contracting (Roth et al, 2008). The failure of buyers to clarify the responsibility for ensuring product quality (i.e., who should take the responsibility) could encourage opportunism on the part of upstream suppliers.…”

Section: Traceability Uncertaintymentioning

confidence: 99%

Perception of supply chain quality risk: Understanding the moderation role of supply market thinness

Tse

Zhang

Zeng

et al. 2021

Journal of Business Research

View full text Add to dashboard Cite

Section: Traceability Uncertaintymentioning

confidence: 99%

Perception of supply chain quality risk: Understanding the moderation role of supply market thinness

Tse

Zhang

Zeng

et al. 2021

Journal of Business Research

View full text Add to dashboard Cite

“…The input details pertain to the name of the filters required for the processing of input data, their sequence of operation, type of execution and the number of stages in which the processing should take place. The traceability model is generated [26] initially, which shows the dependencies between the different filters, followed by the generation of the specification file as per the structure described earlier.…”

Section: Architectural Specification For Composite Architectural Pamentioning

confidence: 99%

Composite pattern to handle variation points in software architectural design of evolving application systems

et al. 2020

Self Cite

View full text Add to dashboard Cite

The variation points in software architecture arise as a result of the availability of large number of filters and component libraries. An integration of different architectural styles is crucial and necessary in the development of large-scale software application systems to handle the variation points. This article proposes a composite software architectural style for building application systems involving data streams, user interactivity, and dynamic mode. It uses a pattern within a pattern approach for combining the architectural styles. This approach provides flexibility to add or delete any filter or component at run time. In addition, the changes in the order of processing of the different filters or components can also be incorporated. The software architectural specification for any combination of input components and their order of processing is generated automatically. This specification acts as a baseline for the subsequent design and implementation phases of the application system. This model is generic and has been successfully validated for a prototype application system involving all the three modes of operation.

show abstract

Estimation and Generation of Software Architectural Specification to Handle Variation Points

Philip

Shah

Vijayakumar

2018

Int. J. Soft. Eng. Knowl. Eng.

View full text Add to dashboard Cite

The development of a reliable and efficient software application system requires a competent software architecture which can attune to any design improvement opportunity in the early stages of software architectural design. An Architectural Description Language provides a description of all the component elements and their interactions. The proposed model determines all possible ways of connecting the components and connectors, after eliminating the transitive and symmetric conflicts among the connections, followed by the generation of the software architectural specification. An estimate on the maximum number of architectural specifications generated for a given number of components has been carried out. The syntax for specifying the components and the connectors has been formulated. The model proposed in the current work is generic and it will significantly help a software architect in building reliable, efficient and flexible software architecture, for any valid combination of components and connectors. It has been successfully tested for two prototype applications that involve processing of images and documents.

show abstract

Requirements Traceability Model Generation for Evolving Software Systems

Cited by 3 publications

References 11 publications

Perception of supply chain quality risk: Understanding the moderation role of supply market thinness

Perception of supply chain quality risk: Understanding the moderation role of supply market thinness

Composite pattern to handle variation points in software architectural design of evolving application systems

Estimation and Generation of Software Architectural Specification to Handle Variation Points

Contact Info

Product

Resources

About