Functional use-case generation

US9864587B2 · US · B2

Patent metadata
FieldValue
Publication numberUS-9864587-B2
Application numberUS-201615208450-A
CountryUS
Kind codeB2
Filing dateJul 12, 2016
Priority dateMar 26, 2015
Publication dateJan 9, 2018
Grant dateJan 9, 2018

How to read this patent

A practical reading order for non-experts. Skip the full description unless you need deep technical detail.

  1. Title

    What the patent document calls the invention.

  2. Abstract

    A short plain-language summary of the technical disclosure.

  3. Assignees and inventors

    Who owns or filed the patent and who is credited as inventor.

  4. Key dates

    Filing, priority, publication, and grant dates set the timeline.

  5. First independent claim

    The legal scope of protection — read this for what is actually claimed.

  6. CPC / IPC classifications

    Technology tags used to group this patent with similar filings.

  7. Citations and related patents

    Prior art links and similar publications in this corpus.

Abstract

Official abstract text for this publication.

Functional use-case generation may include determining whether a requirements context is available. In response to a determination that the requirements context is available, the requirements context may be determined as a task context and as a rule context for a requirements sentence of a requirements document. The task context and the rule context may be used to select a functional model from a plurality of functional models. A functional use-case that includes an entity that is to perform a task based on a rule may be generated. Further, in response to a determination that the requirements context is not available, a functional model may be selected from the plurality of functional models based on process context, where the functional model includes a process related to the process context, and the functional model that includes the process related to the process context may be used to generate the functional use-case.

First claim

Opening claim text (preview).

What is claimed is: 1. A functional use-case generation system comprising: at least one hardware processor; a requirements and process context selector, executed by the at least one hardware processor, to determine whether a requirements context is available; in response to a determination that the requirements context is available, a requirements context analyzer, executed by the at least one hardware processor, to determine the requirements context as at least one of a task context and as a rule context for a requirements document, and utilize a process context analyzer, executed by the at least one hardware processor, to generate, based on the at least one of the task context and the rule context, a functional use-case that includes an entity that is to perform a task based on a rule. 2. The functional use-case generation system according to claim 1 , further comprising: a dependent functional use-case selector, executed by the at least one hardware processor, to select a functional use-case from a plurality of functional use-cases, and use information from the selected functional use-case to augment at least one of the entity, the task, and the rule related to the functional use-case that is to be generated. 3. The functional use-case generation system according to claim 1 , further comprising: a document generator, executed by the at least one hardware processor, to generate the functional use-case based on a functional use-case template. 4. The functional use-case generation system according to claim 1 , wherein the requirements context analyzer is to utilize a sentence classifier, executed by the at least one hardware processor, to classify a requirements sentence of the requirements document as a task or as a rule, and determine the at least one of the task context and the rule context based on the classification of the requirements sentence as the task or as the rule. 5. The functional use-case generation system according to claim 4 , wherein for a requirements sentence classified as the task, the requirements context analyzer is to utilize an entity extractor, executed by the at least one hardware processor, to determine the entity related to the task, and for the requirements sentence classified as the rule, the requirements context analyzer is to utilize a constraint extractor, executed by the at least one hardware processor, to determine an attribute related to the rule. 6. The functional use-case generation system according to claim 1 , wherein the requirements context analyzer is to utilize a sentence classifier, executed by the at least one hardware processor, to perform subject, predicate, and object extraction for mapping of a requirements sentence of the requirements document to a task of a functional model associated with the at least one of the task context and the rule context for selection of the functional model from a plurality of functional models. 7. The functional use-case generation system according to claim 6 , wherein the requirements context analyzer is to utilize the sentence classifier to perform subject, predicate, and object extraction for mapping of the requirements sentence of the requirements document to the task of the functional model associated with the at least one of the task context and the rule context for selection of the functional model from the plurality of functional models by interchanging a passive verb of the requirements sentence with at least one of a subject and an object of the requirements sentence. 8. The functional use-case generation system according to claim 1 , wherein the requirements context analyzer is to utilize an ontology and database query analyzer, executed by the at least one hardware processor, to utilize the at least one of the task context and the rule context to determine related entities and rules to generate the functional use-case. 9. A method for functional use-case generation, the method comprising: determining, by a requirements and process context selector, executed by at least one hardware processor, whether a requirements context is available; and in response to a determination that the requirements context is available, utilizing, by the requirements context analyzer the requirements context to select a functional model from a plurality of functional models, wherein the functional models are based on entities, tasks, and rules, and a process context analyzer, executed by the at least one hardware processor, to generate, based on the functional model, a functional use-case that includes an entity that is to perform a task based on a rule. 10. The method for functional use-case generation according to claim 9 , further comprising: selecting, by a dependent functional use-case selector, executed by the at least one hardware processor, a functional use-case from a plurality of functional use-cases; and using, by the dependent functional use-case selector, information from the selected functional use-case to augment at least one of the entity, the task, and the rule related to the functional use-case that is to be generated. 11. The method for functional use-case generation according to claim 9 , further comprising: utilizing, by the requirements context analyzer, a sentence classifier, executed by the at least one hardware processor, to classify a requirements sentence of a requirements document related to the requirements context as a task or as a rule; and determining, by the requirements context analyzer, at least one of a task context and a rule context for the requirements sentence of the requirements document based on the classification of the requirements sentence as the task or as the rule. 12. The method for functional use-case generation according to claim 11 , further comprising: for a sentence classified as the task, utilizing, by the requirements context analyzer, an entity extractor, executed by the at least one hardware processor, to determine the entity related to the task; and for the sentence classified as the rule, utilizing by the requirements context analyzer, a constraint extractor, executed by the at least one hardware processor, to determine an attribute related to the rule. 13. The method for functional use-case generation according to claim 9 , further comprising: utilizing, by the requirements context analyzer, a sentence classifier, executed by the at least one hardware processor, to perform subject, predicate, and object extraction for mapping of a requirements sentence of a requirements document related to the requirements context to a task of the functional model for selection of the functional model from a plurality of functional models. 14. The method for functional use-case generation according to claim 13 , wherein utilizing, by the requirements context analyzer, the sentence classifier, executed by the at least one hardware processor, to perform subject, predicate, and object extraction for mapping of the requirements sentence of the requirements document related to the requirements context to the task of the functional model for selection of the functional model from the plurality of functional models further comprises: interchanging a passive verb of the requirements sentence with at least one of a subject and an object of the requirements sentence. 15. The method for functional use-case generation according to claim 9 , further comprising: utilizing, by the requirements context analyzer, an ontology and database query analyzer, executed by the at least one hardware processor, to utilize at least one of a task context and a rule context to determine

Assignees

Inventors

Classifications

  • G06F8/35Primary

    model driven · CPC title

  • Requirements analysis; Specification techniques · CPC title

  • Testing of software · CPC title

Patent family

Related publications grouped by family.

External sources

Frequently asked questions

Answers are generated from the same data shown on this page.

What does patent US9864587B2 cover?
Functional use-case generation may include determining whether a requirements context is available. In response to a determination that the requirements context is available, the requirements context may be determined as a task context and as a rule context for a requirements sentence of a requirements document. The task context and the rule context may be used to select a functional model from…
Who is the assignee on this patent?
Accenture Global Services Ltd
What technology area does this patent fall under?
Primary CPC classification G06F8/35. Mapped technology areas include Physics.
When was this patent published?
Publication date Tue Jan 09 2018 00:00:00 GMT+0000 (Coordinated Universal Time) (B2). Legal status and post-grant events are not shown on this page.
What related patents are in patentsdb?
We list 1 related publication on this page (citations in our corpus or others sharing the same primary CPC).