A Concept for Orchestration of Microservices
US-2024281220-A2 · Aug 22, 2024 · US
US9262126B2 · US · B2
| Field | Value |
|---|---|
| Publication number | US-9262126-B2 |
| Application number | US-97131010-A |
| Country | US |
| Kind code | B2 |
| Filing date | Dec 17, 2010 |
| Priority date | Dec 17, 2010 |
| Publication date | Feb 16, 2016 |
| Grant date | Feb 16, 2016 |
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.
Methods and systems described herein implement a recommendation system for providing recommendations for generating a requirements specification for agile software development. In one implementation, the system includes a processor and a memory coupled to the processor. The memory comprises a mapping module and an agile recommendation module. The mapping module is configured to map knowledge elements of at least one ontology instance selected from among a plurality of ontology instances with another ontology instance selected from among the plurality of the ontology instances. The agile recommendation module is configured to generate a knowledge corpus based on the mapped knowledge elements of the ontology instances and at least one environmental parameter, receive modifications in the knowledge corpus, and provide recommendations to generate a requirements specification based at least, in part, on the received modifications.
Opening claim text (preview).
I claim: 1. A system for generating requirements specification to develop functionalities of a software, the system comprising: a processor; and a memory coupled to the processor, wherein the memory comprises, a mapping module configured to map knowledge elements of at least one ontology instance for a domain, selected from among a plurality of ontology instances in a knowledge base, with another ontology instance, selected from among the plurality of ontology instances based on an input received from a user and wherein the ontology instance defines a common vocabulary, in a machine-readable and processable format, for users who share information within the domain associated with the software being developed, for which the requirements specification is being generated, wherein the mapping module includes a plurality of bridge classes to specify semantic mappings of conclusions drawn from at least one said plurality of ontology instances; and an agile recommendation module configured to, generate a knowledge corpus from the knowledge base based on the mapped knowledge elements and one or more environmental parameters selected by the user, wherein: the one or more environmental parameters are selected to define requirements for developing functionalities of the software; the one or more environmental parameters include a geographic region; and the knowledge corpus includes features and associated knowledge elements based on the selected one or more environmental parameters; receive at least one modification in the knowledge corpus based on a selection of one or more of the features and the associated knowledge elements in the knowledge corpus by the user, wherein the selection includes one of a modification and enhancement of the features and the associated knowledge elements; generate recommendations specific to the domain from the knowledge base based on the received at least one modification, said generation facilitated by using a plurality of lexical decomposition techniques to resolve a plurality of requirement descriptions; and generate the requirements specification for the domain by incorporating the user's response to the recommendations, wherein the requirements specification indicates prioritization of a plurality of iterations, the plurality of iterations being indicative of logical and coherent units of functionalities of the software to be developed; and an extraction module configured to, apply at least one inference rule on the plurality of ontology instances in the knowledge base to identify an ontology instance from among the plurality of ontology instances based on the selected one or more environmental parameters; and extract semantic inferences from the identified ontology instance by matching the selected one or more environmental parameters and the mapped knowledge elements to provide the knowledge corpus. 2. The system as claimed in claim 1 , wherein the agile recommendation module is further configured to provide the recommendations based on the semantic inferences extracted from the identified ontology instances and the at least one modification. 3. The system as claimed in claim 1 , wherein the knowledge corpus comprises business processes, rules, policies, partial data models, use cases, test cases, user stories, features, tasks, product backlog, iterations, and prototype plans. 4. The system as claimed in claim 1 , wherein the at least one environmental parameter is one of a domain, line of business, and a type of project. 5. The system as claimed in claim 1 , wherein the plurality of ontology instances comprises a Problem Domain Ontology Instance, an Agile Requirements Ontology Instance, a Requirements Ontology Instance, and an Environmental Context Ontology Instance. 6. The system as claimed in claim 1 , wherein the requirements specification is at least one of a document detailing requirements, a prototype and an executable model. 7. A method for generating requirements specification to develop functionalities of a software, the method comprising: mapping knowledge elements of at least one ontology instance, selected from among a plurality of ontology instances in a knowledge base, with another ontology instance for a domain, selected from among the plurality of ontology instances based on an input received from a user and wherein the ontology instance defines a common vocabulary, in a machine-readable and processable format, for users who share information within the domain associated with the software being developed for which the requirements specification is being generated, wherein mapping knowledge elements using one or more bridge classes to specify semantic mappings of conclusions of a first ontology instance to the knowledge elements of a second ontology instance; providing a knowledge corpus from the knowledge base based at least on one or more environmental parameter selected by the user and the mapped knowledge elements, wherein: the one or more environmental parameters are selected to define requirements for developing functionalities of the software; the one or more environmental parameters include a geographical region; and the knowledge corpus includes features and associated knowledge elements based on the selected one or more environmental parameters; receiving at least one modification in the knowledge corpus based on a selection of one or more of the features and the associated knowledge elements in the knowledge corpus by the user, wherein the selection includes one of a modification and enhancement of the features and the associated knowledge elements; providing recommendations specific to the domain from the knowledge base based on the received at least one modification and using a plurality of lexical decomposition techniques to resolve a plurality of requirement descriptions, wherein the providing comprises: applying at least one inference rule on the plurality of ontology instances to identify an ontology instance from among the plurality of ontology instances based on the selected one or more environmental parameters; extracting semantic inferences from the identified ontology instance; and implementing the semantic inferences to the identified ontology instance for providing the knowledge corpus and the recommendations; and generating the requirements specification for the domain by incorporating the user's response to the recommendations, wherein the requirements specification indicates prioritization of a plurality of iterations the plurality of iterations indicative of logical and coherent units of functionalities of the software to be developed. 8. The method as claimed in claim 7 , wherein the one or more environmental parameters is one of a domain, a line of business, and a type of project. 9. The method as claimed in claim 7 , wherein the requirements specification is at least one of a document detailing requirements, a prototype, and an executable model. 10. The method as claimed in claim 7 , wherein the knowledge corpus comprises business processes, rules, policies, partial data models, use cases, test cases, user stories, features, tasks, product backlog, iterations, and prototype plans. 11. The method as claimed in claim 7 further comprises prioritizing the plurality of iterations based on the recommendations. 12. A non-transitory computer-readable medium having embodied thereon a computer program for executing a method comprising: mapping knowledge elements of at least one ontology instance, selected from among a plurality of ontology instances in a knowledge base, with another ontology instance for a domain, selected from among the plurality of ontology instances based on an inpu
Requirements analysis; Specification techniques · CPC title
Related publications grouped by family.
Answers are generated from the same data shown on this page.