A Concept for Orchestration of Microservices
US-2024281220-A2 · Aug 22, 2024 · US
US8996982B2 · US · B2
| Field | Value |
|---|---|
| Publication number | US-8996982-B2 |
| Application number | US-61657106-A |
| Country | US |
| Kind code | B2 |
| Filing date | Dec 27, 2006 |
| Priority date | Dec 27, 2006 |
| Publication date | Mar 31, 2015 |
| Grant date | Mar 31, 2015 |
A practical reading order for non-experts. Skip the full description unless you need deep technical detail.
What the patent document calls the invention.
A short plain-language summary of the technical disclosure.
Who owns or filed the patent and who is credited as inventor.
Filing, priority, publication, and grant dates set the timeline.
The legal scope of protection — read this for what is actually claimed.
Technology tags used to group this patent with similar filings.
Prior art links and similar publications in this corpus.
Official abstract text for this publication.
Embodiments of the present invention provide a method, system and computer program product for managing requirements planning in a collaborative computing environment. In one embodiment of the invention, a requirements planning management method can include identifying each approving stakeholder for a version of a requirement in a requirements plan, creating traceability links between each approving stakeholder and the version of the requirement, and notifying each approving stakeholder having a traceability link to the version of the requirement whenever a new version of the requirement is proposed by a stakeholder. The method also can include merging multiple versions of the requirement into a single document, displaying the single document to a viewing stakeholder, and marking up the single document to reflect differences between the single document and a most recent version of the requirement for the viewing stakeholder.
Opening claim text (preview).
We claim: 1. A requirements planning management method comprising: identifying in a requirements planning system executing in memory of a host computing platform, each approving stakeholder for a version of a requirement in a requirements plan of requirements for a software system; creating traceability links between each approving stakeholder and the version of the requirement, each traceability link connecting a stakeholder with a specific version of the requirement requiring…
Related publications grouped by family.
Free tools are coming soon. Tell us what you want to track and we'll notify you.
Answers are generated from the same data shown on this page.