This wiki is locked. Future workgroup activity and specification development must take place at our new wiki. For more information, see this blog post about the new governance model and this post about changes to the website.
-- GrayBachelor
See also OSLC Common Glossary
| Name | Description | Status | |
| Application Lifecycle Management (ALM) | Business concerns associated with managing a viable software delivery that constitutes or realises a software application | Proposed 16/2/2010 | |
| Product Lifecycle Management (PLM) | Business concerns associated with managing a product over its lifecycle to achieve the desired market and business objectives | Proposed 16/2/2010 | |
| System | An arrangement of deliverables or operating units regardless of scale | Draft 29/3/2010 | |
| Product | An item offered for sale which visible to customers, attracts a price and becomes the basis of a commercial transaction (contract) | Draft 29/3/2010 | |
| Application | Unit of (Software) delivery that provides some significant collection of functions. | Draft 29/3/2010 | |
| Product identity & classification | Recognised coding and description of products, such as within product types, families. Ultimatlely provides a uniqueidentifier plus multiple means to describe, find and promote a product (for usage) | Draft 29/3/2010 | |
| Content | Information that represents the design or how to realise an application, a product or system. For instance could include a quality spec but would typically exclude the measured quality data gathered | Draft 29/3/2010 | |
| Associate | Establish and maintain a linkage | Draft 29/3/2010 | |
| Pedigree | An assessment of a product, system, application, artefact | Draft 29/3/2010 | |
| Promotion | Progressive sanction of a product, system, application, artefact | ||
| Release | Promote for usage. Usage can mean further realization, integration, distribution, sale etc | Draft 29/3/2010 | |
| Availability | Begin formal provision of a product, system or service to into the market, make shippable to customers | Draft 29/3/2010 | |
| Workflow | Instantiation of a business process as a series oif steps of activities performed by roles and IT | Draft 29/3/2010 | |
| Transition | Implement a business rule on an artefact, configuration or work item | Draft 29/3/2010 | |
| Business Rule | An objective evaluation of criteria | Draft 29/3/2010 | |
| Configuration | Check jazz.net | ||
| Variant | Alternative configuration of a product or system by way of capability or capacity or location (NFRs) | Draft 29/3/2010 | |
| Effectivity | Indication of planned relevance of a release or change e.g. by date, release, product or system identity sequence | ||
Topic revision: r2 - 18 Jan 2011 - 16:37:34 - SteveSpeicher
Main Web
Create New Topic
Index
Search
Changes
Notifications
RSS Feed
Statistics
Preferences
Main|
|
Copyright � 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 this site? Send feedback