r5 - 2019-11-08 - 19:31:59 - NickCrossleyYou are here: TWiki >  LinkedData Web > LinkedDataReviewBoard > PublishingRdfVocabularies > LinkedDataWebVocabularies > SseVocabulary
This wiki: The development wiki is a work area where Jazz development teams plan and discuss technical designs and operations for the projects at Jazz.net. Work items often link to documents here. You are welcome to browse, follow along, and participate. Participation is what Jazz.net is all about! But please keep in mind that information here is "as is", unsupported, and may be outdated or inaccurate. For information on released products, consult IBM Knowledge Center, support tech notes, and the Jazz.net library. See also the Jazz.net Terms of Use.

New product names: The CE/CLM products were renamed in version 7.0. For details on the name change, see Renaming the IBM Continuous Engineering Portfolio. Some content might continue to use the previous names or contain a combination of the previous and current names.

IBM Software and Systems Engineering Vocabulary

Licensed Materials (See https://jazz.net/ns/license.html) - Property of IBM.
© Copyright IBM Corporation 2019. All Rights Reserved.
U.S. Government Users Restricted Rights: Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp.

The namespace URI for this vocabulary is:

http://jazz.net/ns/sse#

Description:

Vocabulary terms describing typical resources used for software and systems engineering.

This page lists the RDF classes, properties, and individuals that make up the Software and Systems engineering core vocabulary.

Following W3C best practices, this information is available as HTML (this page) and as RDF.

More details on how this page is generated and other related material can be found at Publishing RDF Vocabularies on jazz.net.


Classes in this vocabulary:

Actor, Approval Types, Collection, Disposition, Disposition, Free-Form Diagram, Hardware Requirement, Heading, How Found, Impact, Information, Module, Non-Functional Requirement, Non-Functional Requirement Types, Origin, Probability, Rating scale (High/Medium/Low), Release Collection, Review Verification Methods, Risk Categories, Role, Software Architecture Design, Software Detailed Design, Software Requirement, Stakeholder Requirement, Standard, Supporting Resource, System Architecture, System Requirement, Term, Use Case, Use Case Property Values, User Requirement, Vision

Properties in this vocabulary:

Accepted, Approved By, Approver Position, Benefits, Blocked, Change Reason, Constrains, Contingency Plan, Customer Approval Status, Depends On, Disposition, Estimated Cost, Exposure (%), How Found, Identification Date, Impact, Impact Assessment, Impacts, Integrates with Hardware, Is Derived From, Maturity, Mitigates, Mitigates, Mitigation Plan, Nonfunctional Type, Occurrence Date, Origin, Owner, Probability, Reason, Resource Requirements, Reviewers, Review Findings, Review Stakeholders, Risk Category, Scheduling Issues, Stability, Supplier Approval Status, Use Case Property, Verification Criteria, Verification Method

Individuals in this vocabulary:

100% - Blocker, 100% - Very High, 20% - Minor, 20% - Very Low, 40% - Low, 40% - Moderate, 60% - Major, 60% - Moderate, 80% - Critical, 80% - High, Accepted, Accessibility, Alternate Flow, Analysis, Analyzing, Approved, Audit, Availability, Avoided, Basic Flow, Brief Description, Capacity, Change Request, Competitive, Competitive Analysis, Compliance, Customer, Customer, Deprecated, Development, Development, Done, Draft, Duplicate, Economic, Fixed, Fixed Upstream, Hardware Requirements Module, Implementing, In Analysis/Review, In Development, Inspection, Interoperability, In Test, Invalid, Invalid, Invalid, Market, Market Analysis, Name, New, Nonfunctional Requirements Module, Not Approved, Not Reproducible, Not Started, Obsolete, Partner, Peer review, Performance, Political, Post-Condition, Postponed, Pre-Condition, Quality Assurance, Ready (for Approval), Regulatory/legal, Rejected, Reliability, Resolved, Retired, Reviewing, Scalability, Security, Services, Socio-cultural, Software Requirements Module, Special Requirement, Stakeholder Requirements Module, Standards/Legal, Support, Supportability, System Requirements Module, Technology, Test, Transferred/Shared, Unassigned, Unassigned, Uncertainty, Under Review, Unknown, Use Case Module, Verifying, Walkthrough, Won't Fix, Works as Designed, Works for Me


Vocabulary Details

100% - Blocker

TypeAn individual.
Description The Risk is a blocker.

See Also:

100% - Very High

TypeAn individual.
Description Very high probability that the risk will occur.

20% - Minor

TypeAn individual.
Description The Risk has minor impact.

See Also:

20% - Very Low

TypeAn individual.
Description Very low probability that the risk will occur.

40% - Low

TypeAn individual.
Description Low probability that the risk will occur.

40% - Moderate

TypeAn individual.
Description The Risk has moderate impact.

See Also:

60% - Major

TypeAn individual.
Description The Risk has major impact.

See Also:

60% - Moderate

TypeAn individual.
Description Moderate probability that the risk will occur.

80% - Critical

TypeAn individual.
Description The Risk has significant or critical impact.

See Also:

80% - High

TypeAn individual.
Description High probability that the risk will occur.

Accepted

Typerdf:Property
Description Indicates whether or not the requirement or work has been accepted. Typically expressed as a boolean value.

Accepted

TypeAn individual.
Description Work has been successfully implemented and tested, and accepted by the business owner/stakeholder.

Accessibility

TypeAn individual.
Description Requirement related to accessibility.

Actor

Typerdfs:Class
Description Represents a role that a human, hardware device, or another system can play in a use case or scenario.

Alternate Flow

TypeAn individual.
Description Alternate flow property for a use case.

Analysis

TypeAn individual.
Description Review to be verified by analysis.

Analyzing

TypeAn individual.
Description The artifact is being analyzed to understand vision, feasibility, cost, impact, iterative delivery and benefit.

Approval Types

Typerdfs:Class
Description Types of approvals.

Approved

TypeAn individual.
Description Registers approval.

Approved By

Typerdf:Property
Description Approver of the artifact.

Approver Position

Typerdf:Property
Description Position of the person approving the artifact.

Audit

TypeAn individual.
Description Review to be verified by audit.

Availability

TypeAn individual.
Description Requirement related to availability.

Avoided

TypeAn individual.
Description The risk has been avoided.

Basic Flow

TypeAn individual.
Description Basic flow property for a use case.

Benefits

Typerdf:Property
Description Benefits to be gained by implementing a change or cabability.

Blocked

Typerdf:Property
Description Indicates a 'soft dependency', that the work is blocked by some other required work.

Brief Description

TypeAn individual.
Description Brief description property for a use case.

Capacity

TypeAn individual.
Description Requirement related to capacity.

Change Reason

Typerdf:Property
Description Reason for requesting a change.

Change Request

TypeAn individual.
Description Request for a change to some aspect of the product.

Collection

Typerdfs:Class
Description A logical grouping of related artifacts.

Competitive

TypeAn individual.
Description Competitive risk.

Competitive Analysis

TypeAn individual.
Description Originated from competition or competitive analysis.

Compliance

TypeAn individual.
Description Requirement related to compliance.

Constrains

Typerdf:Property
Description Link type indicating that a requirement constrains another. For example, a non-functional requirement constrains a system requirement.

Contingency Plan

Typerdf:Property
Description Contingency plan for a risk.

Customer

TypeAn individual.
Description Indicates a customer found the defect or issue.

Customer

TypeAn individual.
Description Originated from a customer.

Customer Approval Status

Typerdf:Property
Description The approval status for a customer.

See Also:

Depends On

Typerdf:Property
Description Shows dependency between requirements.

Deprecated

TypeAn individual.
Description The artifact or work defined has been deprecated and there might be a newer version of it.

Development

TypeAn individual.
Description Originated from the development team.

Development

TypeAn individual.
Description Indicates the development team found the defect or issue.

Disposition

Typerdfs:Class
Description Disposition of the resolved risk.

Disposition

Typerdf:Property
Description Indicates the disposition of a resolved defect (how it was resolved). Typically expressed as a value of type jazz_sse:DefectDisposition.

See Also:

Disposition

Typerdfs:Class
Description Disposition of the resolved defect.

Done

TypeAn individual.
Description The artifact or work defined is completed and delivered.

Draft

TypeAn individual.
Description Initial state of the artifact.

Duplicate

TypeAn individual.
Description Duplicate of another defect.

Economic

TypeAn individual.
Description Economic risk.

Estimated Cost

Typerdf:Property
Description Estimated cost of delivery.

Exposure (%)

Typerdf:Property
Description The risk exposure to the plan as a result of the risk identified.

Fixed

TypeAn individual.
Description Defect has been corrected.

Fixed Upstream

TypeAn individual.
Description Defect has been corrected as part of another change.

Free-Form Diagram

Typerdfs:Class
Description A diagram to help illustrate or communicate a solution or requirement.

Hardware Requirement

Typerdfs:Class
Description A requirement allocated to hardware.

Hardware Requirements Module

TypeAn individual.
Description A module for hardware requirements.

Heading

Typerdfs:Class
Description An artifact used as a heading in a strucured module.

How Found

Typerdfs:Class
Description Describes how a defect was found.

How Found

Typerdf:Property
Description Indicates how the defect was found. Typically expressed as a value of type jazz_sse:HowFound.

See Also:

Identification Date

Typerdf:Property
Description Date when the risk was identified.

Impact

Typerdf:Property
Description Impact associated with a risk or change. Typically expressed as a value of type jazz_sse:RiskImpact.

See Also:

Impact

Typerdfs:Class
Description Impact values associated with risks.

See Also:

Impact Assessment

Typerdf:Property
Description Description of the impact of making the change.

Impacts

Typerdf:Property
Description Shows impacts, for example of a system requirement on other elements of the operating environment.

Implementing

TypeAn individual.
Description Work is allocated to one or more Value Streams or Programs.

In Analysis/Review

TypeAn individual.
Description The approval is in analysis/review.

In Development

TypeAn individual.
Description Development work has started.

Information

Typerdfs:Class
Description Artifact used to contain non-requirement content, such as instructions related to managing requirements or modules.

Inspection

TypeAn individual.
Description Review to be verified by inspection.

Integrates with Hardware

Typerdf:Property
Description Shows integration relationship between hardware and software requirements.

Interoperability

TypeAn individual.
Description Requirement related to interoperability.

In Test

TypeAn individual.
Description Development tasks are complete and code is delivered for testing.

Invalid

TypeAn individual.
Description Not valid.

Invalid

TypeAn individual.
Description The risk is invalid.

Invalid

TypeAn individual.
Description The artifact or work defined is not valid.

Is Derived From

Typerdf:Property
Description Shows the derivation of lower level requirements from higher level requirements.

Market

TypeAn individual.
Description Market risk.

Market Analysis

TypeAn individual.
Description Originated from marketing or market analysis.

Maturity

Typerdf:Property
Description Assessed maturity of the artifact.

See Also:

Mitigates

Typerdf:Property
Description Shows that a requirement mitigates another, such as in the case of a hazard or risk.

Mitigates

Typerdf:Property
Description Shows that a requirement satisfies another requirement.

Mitigation Plan

Typerdf:Property
Description Plan to mitigate the risk.

Module

Typerdfs:Class
Description A hiearchy of requirements.

Name

TypeAn individual.
Description Name property for a use case.

New

TypeAn individual.
Description Initial state of the artifact.

Non-Functional Requirement

Typerdfs:Class
Description The Non-Functional Requirement (NFR) describes system attributes such as security, reliability, maintainability, scalability and usability (i.e. 'Utilities').

Nonfunctional Requirements Module

TypeAn individual.
Description A module for nonfunctional requirements.

Non-Functional Requirement Types

Typerdfs:Class
Description Types of non-functional requirements.

Nonfunctional Type

Typerdf:Property
Description Type or category of non-functional requirement, for example, usability, performance, serviceability. Can be expressed as a value of type jazz_sse:NonFunctionalType.

See Also:

Not Approved

TypeAn individual.
Description Registers lack of approval.

Not Reproducible

TypeAn individual.
Description Defect cannot be reproduced.

Not Started

TypeAn individual.
Description The approval is not yet started (default).

Obsolete

TypeAn individual.
Description The artifact or work defined is obsolete.

Occurrence Date

Typerdf:Property
Description Date when the risk actually occurred.

Origin

Typerdfs:Class
Description Origin of a requirement or request.

Origin

Typerdf:Property
Description Indicates where the requirement originated. Can be expressed as a value of type jazz_sse:OriginValue.

See Also:

Owner

Typerdf:Property
Description Owner or responsible party for the artifact or action.

Partner

TypeAn individual.
Description Originated from one or more business partners.

Peer review

TypeAn individual.
Description Review to be verified by peer review.

Performance

TypeAn individual.
Description Requirement related to performance.

Political

TypeAn individual.
Description Political risk.

Post-Condition

TypeAn individual.
Description Post-condition property for a use case.

Postponed

TypeAn individual.
Description The artifact or work defined is postponed.

Pre-Condition

TypeAn individual.
Description Pre-condition property for a use case.

Probability

Typerdfs:Class
Description Probability values for a risk occurring.

Probability

Typerdf:Property
Description Probability that a risk will occur. Typically expressed as a value of type jazz_sse:RiskProbability.

See Also:

Quality Assurance

TypeAn individual.
Description Originated from the Quality assurance team.

Rating scale (High/Medium/Low)

Typerdfs:Class
Description Ordinal scale (high/medium/low) for rating properties. Typically expressed as a value of type oslc_cm:Priority.

See Also:

Ready (for Approval)

TypeAn individual.
Description Analysis is completed and the epic is submitted for approval.

Reason

Typerdf:Property
Description Explanation of the 'soft dependency' that is blocking the work.

Regulatory/legal

TypeAn individual.
Description Regulatory/legal risk.

Rejected

TypeAn individual.
Description The artifact or work defined is rejected and no further work will be done.

Release Collection

Typerdfs:Class
Description A logical grouping of related artifacts specifically associated with a release.

Reliability

TypeAn individual.
Description Requirement related to reliability.

Resolved

TypeAn individual.
Description The artifact or work defined is resolved.

Resource Requirements

Typerdf:Property
Description Resources required to address a change request.

Retired

TypeAn individual.
Description The artifact or work defined has been retired and is now closed.

Reviewers

Typerdf:Property
Description Participants in the review.

Review Findings

Typerdf:Property
Description Documents any discovery or new findings as a result of a review.

Reviewing

TypeAn individual.
Description The artifact is being reviewed.

Review Stakeholders

Typerdf:Property
Description Parties who are interested in the review and its outcome, but are not reviewers.

Review Verification Methods

Typerdfs:Class
Description Verification methods used in review activities.

Risk Categories

Typerdfs:Class
Description Category values for risks.

Risk Category

Typerdf:Property
Description Category or classification of the type of risk. Typically expressed as a value of type jazz_sse:RiskCategory.

See Also:

Role

Typerdfs:Class
Description Describes a role that performs activities within the context of a scenario, for example, Systems Engineer, Product Owner, Architect, Software Engineer, Hardware Engineer.

Scalability

TypeAn individual.
Description Requirement related to scalability.

Scheduling Issues

Typerdf:Property
Description Scheduling issues associated with a change request.

Security

TypeAn individual.
Description Requirement related to security.

Services

TypeAn individual.
Description Originated from the services team.

Socio-cultural

TypeAn individual.
Description Socio-cultural risk.

Software Architecture Design

Typerdfs:Class
Description Represents the architectural design for the software of a system or product.

Software Detailed Design

Typerdfs:Class
Description Represents the detailed architectural design for the software of a system or product.

Software Requirement

Typerdfs:Class
Description A requirement for software.

Software Requirements Module

TypeAn individual.
Description A module for software requirements.

Special Requirement

TypeAn individual.
Description Special requirement property for a use case.

Stability

Typerdf:Property
Description Assessment of how stable the requirement is, as opposed to likely to change.

See Also:

Stakeholder Requirement

Typerdfs:Class
Description A requirement from the business or enterprise operations level (users, acquirers, customers, other stakeholders) as they relate to the problem or opportunity, that describe the solution required.

Stakeholder Requirements Module

TypeAn individual.
Description A module for stakeholder requirements.

Standard

Typerdfs:Class
Description A specific type of requirement that defines a regulatory or system constraint.

Standards/Legal

TypeAn individual.
Description Originated from a standard or legal contraint.

Supplier Approval Status

Typerdf:Property
Description The approval status for a supplier.

See Also:

Support

TypeAn individual.
Description Originated from the Help Desk or support team.

Supportability

TypeAn individual.
Description Requirement related to supportability.

Supporting Resource

Typerdfs:Class
Description An artifact that does not fit one of the other categories. A supporting resource will often be leveraged when uploading artifacts where one of the artifact types does not apply.

System Architecture

Typerdfs:Class
Description Represents the architecture of the overall system.

System Requirement

Typerdfs:Class
Description An requirement describing a function that the system as a whole should fulfill to satisfy the stakeholder needs and requirements.

System Requirements Module

TypeAn individual.
Description A module for system requirements.

Technology

TypeAn individual.
Description Technology risk.

Term

Typerdfs:Class
Description Captures phrases or words that require a description.

Test

TypeAn individual.
Description Indicates the test or QA team found the defect or issue.

Transferred/Shared

TypeAn individual.
Description The risk is transferred or shared with another team.

Unassigned

TypeAn individual.
Description Review verification method has not been assigned.

Unassigned

TypeAn individual.
Description Unassigned ordinal scale value.

Uncertainty

TypeAn individual.
Description Uncertainty risk.

Under Review

TypeAn individual.
Description The artifact is under review reviewed.

Unknown

TypeAn individual.
Description Indicates that the origin of the defect is not known or not defined.

Use Case

Typerdfs:Class
Description The set of actions performed by a system, which yeilds an observable result that is, typically of value for one or more actors or other stakeholders of the system.

Use Case Module

TypeAn individual.
Description A module describing a particular use case.

Use Case Property

Typerdf:Property
Description Property of a use case. Typically expressed as a value of type jazz_sse:UseCasePropertyValues.

See Also:

Use Case Property Values

Typerdfs:Class
Description Values for a use case property.

User Requirement

Typerdfs:Class
Description A User Requirement specifically describes a capability required by end-users or customers. User Requirements are typically implemented by Features or Stories.

Verification Criteria

Typerdf:Property
Description Specifies the verification criteria used to conduct a review.

Verification Method

Typerdf:Property
Description Indicates the method of review to be used. Can be expressed as a value of type jazz_sse:ReviewMethod.

See Also:

Verifying

TypeAn individual.
Description A problem is in the process of being verified.

Vision

Typerdfs:Class
Description The Vision is a description of the future state of the Solution under development. It reflects Customer and stakeholder needs, as well as the Feature and Capabilities, proposed to meet those needs.

Walkthrough

TypeAn individual.
Description Review to be verified by a walkthrough.

Won't Fix

TypeAn individual.
Description Defect will not be fixed.

Works as Designed

TypeAn individual.
Description Working as designed.

Works for Me

TypeAn individual.
Description Unable to reproduce.
Topic attachments
I Attachment Action Size Date Who Comment
Htmlhtml sse-vocabulary.html manage 73.6 K 2019-11-08 - 19:31 NickCrossley IBM Software and Systems Engineering Vocabulary, in HTML
Ttlttl sse-vocabulary.ttl manage 37.9 K 2019-11-08 - 19:31 NickCrossley IBM Software and Systems Engineering Vocabulary
Edit | WYSIWYG | Attach | Printable | Raw View | Backlinks: Web, All Webs | History: r5 < r4 < r3 < r2 < r1 | More topic actions
 
This site is powered by the TWiki collaboration platformCopyright © by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
Contributions are governed by our Terms of Use
Ideas, requests, problems regarding TWiki? Send feedback