Business modeling and requirements in RUP: a dependency analysis of activities, tasks and work products

Most artifacts developed during the requirements engineering process relate themselves in different ways. In order to understand in detail how they affect each other during the software development process, it is relevant to iden-tify their interdependencies. This paper presents a systematization of the existing interdependencies between the different elements of the Rational Unified Process (RUP) in the Business Modeling and Requirements disciplines. This work, which highlights knowledge about the different interdependencies and traceability of RUP elements, is useful to avoid unconscious decisions during software the de-velopment process and also, to detect potential problems due to the violation of the existing interdependencies.This work has been supported by COMPETE: POCI-01-0145-FEDER-007043 and FCT – Fundação para a Ciência e a Tecnologia within the Project Scope: UID/CEC/00319/2013.info:eu-repo/semantics/publishedVersio

Using semantic web to establish traceability links between heterogeneous artifacts

Semantic Web enables the users of the World Wide Web (WWW) to create non-traditional data repositories. The data can be linked in a flat hierarchy structure that allows the extensibility of data without the need for changing the structure itself. The linked data along with other rules can be used to infer or extract other data. We propose a semantic web technique that employs the Resource Description Framework (RDF) for building a trace links taxonomy. The taxonomy can be utilized to link heterogeneous artifacts coming from different domains of expertise. This technique allows users to refer to any trace link type in the taxonomy using a unique Uniform Resource Identifier (URI). The taxonomy can also be integrated to a traceability framework using the Open Service for Lifecycle Collaboration (OSLC) in order to accommodate the traceability of heterogeneous artifacts. We present validation criteria for validating the taxonomy requirements and validate the solution through a set of test cases. A simple case study is used in order to provide meaningful results