| comment
| - Rückverfolgbarkeit (auch Nachvollziehbarkeit oder engl. Requirements Traceability) bezeichnet in der System- und Softwareentwicklung die Zuordenbarkeit von Anforderungen zu beliebigen Artefakten über den gesamten Entwicklungsprozess und ist somit Teil des Anforderungsmanagements. Rückverfolgbarkeit ist speziell bei der Entwicklung sicherheitskritischer Systeme relevant, wo Normen und Richtlinien wie ISO 26262, Automotive SPICE, und EN 50128 die Erfassung von Requirements Traceability fordern, um damit nachweisen zu können, dass kritische Anforderungen in angemessener Form umgesetzt und validiert wurden.
- Spårbarhetsåterhämtning (eng. traceability recovery eller trace recovery) är aktiviteten att identifiera spårbarhetslänkar mellan programvaruartefakter inom programvaruutveckling. Metoder för att göra detta inkluderar informationssökning, informationsutvinning och regelbaserade angreppssätt genom ontologier. De huvudsakliga användningsområdena för spårbarhetsåterhämtning är:
- El seguiment de requisits o la traçabilitat de requisits és una subdisciplina de la gestió de requisits en el desenvolupament de programari i l'enginyeria de sistemes. El seguiment de requisits es refereix a la documentació de la vida d'un requisit i que faciliti la traçabilitat bidireccional entre diversos requisits associats. Permet als usuaris o grup d'interessats trobar l'origen de cada requisit i fer un seguiment de cada canvi ocorregut a aquest requisit. Perquè aquest seguiment sigui possible, és necessari documentar els canvis realitzats en cada requisit existent.Es discuteix la utilitat de continuar amb la documentació de canvis als requisits després de finalitzar la implementació, d'haver desplegat i utilitzat l'aplicatiu.
- Requirements traceability is a sub-discipline of requirements management within software development and systems engineering. Traceability as a general term is defined by the IEEE Systems and Software Engineering Vocabulary as (1) the degree to which a relationship can be established between two or more products of the development process, especially products having a predecessor-successor or primary-subordinate relationship to one another; (2) the identification and documentation of derivation paths (upward) and allocation or flowdown paths (downward) of work products in the work product hierarchy; (3) the degree to which each element in a software development product establishes its reason for existing; and (4) discernible association among two or more logical entities, such as requireme
- 需求可追蹤性（Requirements traceability）也稱為需求可追溯性，是需求管理中的一部份，和软件开发及系统工程有關。IEEE Systems and Software Engineering Vocabulary有定義通用的可追溯性（Traceability），定義如下 1.
* 在開發過程中二個或是多個產品相關性的程度，特別是兩者之間有先後關係或主從關係的產品 2.
* 在產品層次結構中，工作產品的向上路徑及向下路徑的識別以及 3.
* 在軟體開發產品中，有關每一個元件存在原因的說明 4.
* 在二個或是多個邏輯實體中（例如需求、系統元件、驗證、任務）建立可以識別的關聯性。 若要定義需求可追蹤性，可以定義為：「描述以及追蹤一個需求的生命週期的能力，追蹤可能會往前追蹤，也可能會往後追蹤（追蹤其來源、其開發過程及對應規格、到最終的布署及使用，以及過程中每一個週期中相關的細化及迭代。）」。在需求工程的領域中，可追蹤性是明瞭高階的需求（目標、目的、期望、需求）如何轉換為低階需求的過程，主要關注的是不同資訊層（或開發產物）之間的滿足關係。不過，可追蹤性也可以用文件建立任何種類開發產物之間的關係，例如需求、規格敘述、設法、測試、型號以及所開發的元件。例如在進行展示時，常常需要找到驗證的關係，來確認某一個需求可以由特定的測試所驗證。
|
| dbo:abstract
| - Rückverfolgbarkeit (auch Nachvollziehbarkeit oder engl. Requirements Traceability) bezeichnet in der System- und Softwareentwicklung die Zuordenbarkeit von Anforderungen zu beliebigen Artefakten über den gesamten Entwicklungsprozess und ist somit Teil des Anforderungsmanagements. Rückverfolgbarkeit ist speziell bei der Entwicklung sicherheitskritischer Systeme relevant, wo Normen und Richtlinien wie ISO 26262, Automotive SPICE, und EN 50128 die Erfassung von Requirements Traceability fordern, um damit nachweisen zu können, dass kritische Anforderungen in angemessener Form umgesetzt und validiert wurden.
- Requirements traceability is a sub-discipline of requirements management within software development and systems engineering. Traceability as a general term is defined by the IEEE Systems and Software Engineering Vocabulary as (1) the degree to which a relationship can be established between two or more products of the development process, especially products having a predecessor-successor or primary-subordinate relationship to one another; (2) the identification and documentation of derivation paths (upward) and allocation or flowdown paths (downward) of work products in the work product hierarchy; (3) the degree to which each element in a software development product establishes its reason for existing; and (4) discernible association among two or more logical entities, such as requirements, system elements, verifications, or tasks. Requirements traceability in particular, is defined as "the ability to describe and follow the life of a requirement in both a forwards and backwards direction (i.e., from its origins, through its development and specification, to its subsequent deployment and use, and through periods of ongoing refinement and iteration in any of these phases)". In the requirements engineering field, traceability is about understanding how high-level requirements – objectives, goals, aims, aspirations, expectations, business needs – are transformed into development ready, low-level requirements. It is therefore primarily concerned with satisfying relationships between layers of information (aka artifacts). However, traceability may document relationships between many kinds of development artifacts, such as requirements, specification statements, designs, tests, models and developed components. For example, it is common practice to capture verification relationships to demonstrate that a requirement is verified by a certain test artifact. Traceability is especially relevant when developing safety-critical systems and therefore prescribed by safety guidelines, such as DO178C, ISO 26262, and IEC61508. A common requirement of these guidelines is that critical requirements must be verified and that this verification must be demonstrated through traceability.
|
![[RDF Data]](/fct/images/sw-rdf-blue.png)
