Functional use-case generation

US2016321042A1 · US · A1

Patent metadata
FieldValue
Publication numberUS-2016321042-A1
Application numberUS-201615208450-A
CountryUS
Kind codeA1
Filing dateJul 12, 2016
Priority dateMar 26, 2015
Publication dateNov 3, 2016
Grant date

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).

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

Assignees

Inventors

Classifications

  • Requirements analysis; Specification techniques · CPC title

  • Testing of software · CPC title

  • G06F8/35Primary

    model driven · 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 US2016321042A1 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 Thu Nov 03 2016 00:00:00 GMT+0000 (Coordinated Universal Time) (A1). 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).