Patent US6205575B1 successfully refreshed from Google Patents.
US6205575B1
Expired / Lapsed
US
⏱️ 0.0 years remaining
Scenario presentation tool
Assignee: Siemens Corp
•
Filing: 1997-08-04
•
Granted: 2001-03-20
•
Expires: 2017-08-04
Abstract
Abstract A scenario presentation tool or system provides for the definition, maintenance, and presentation of scenarios. The scenarios comprise a series of steps representing the dynamic behavior of a system. The tool utilizes a system description and includes arrangements for reading and presenting the system description and an arrangement for selecting elements from the system description and for facilitating the definition, maintenance, and presentation of scenarios. The method comprises the steps of defining a sequence of steps by selecting elements from the system description in accordance with a predetermined syntax and saving the steps with sufficient information to reproduce the scenarios.
Inventors
- 👤 William Sherman
- 👤 Wen-Pao Liao
- 👤 Marina Klinger
Bibliographic Details
Application Number
—
Jurisdiction
US
Data Source
google_patents
Last Synchronized
2026-10-30 12:40
CPC Classifications
G; G06; G06F; G06F8/00; G06F8/10; Y; Y10; Y10S; Y10S715/00; Y10S715/961; Y10S715/965; Y10S715/966; Y10S715/967
Claims Analysis
Total Claims: 68
Claim 1
Independent Claim
141 words
A scenario presentation method for use in software development for the definition, maintenance, and presentation of scenarios, said scenarios comprising a series of steps representing the dynamic behavior of a system, said method comprising the steps of: utilizing a system description comprising a hierarchy of purely symbolic data flow diagrams with the data representing software subsystems so that said data flow diagrams represent a functional decomposition of said system, wherein said data flow is in purely symbolic form; reading and presenting the system description, defining software elements from the system description for facilitating the definition, maintenance, and presentation of scenarios; defining a sequence of steps by defining software elements from said system description as represented by selecting software elements on said data flow diagrams in accordance with a predetermined syntax; and saving said steps with sufficient information to reproduce the scenarios.
Claim 2
Dependent Claim
141 words
A scenario presentation method for use in software development for the definition, maintenance, and presentation of scenarios, said scenarios comprising a series of steps representing the dynamic behavior of a system, said method comprising the steps of: utilizing a system description comprising a hierarchy of purely symbolic data flow diagrams with the data representing software subsystems so that said data flow diagrams represent a functional decomposition of said system, wherein said data flow is in purely symbolic form; reading and presenting the system description, defining software elements from the system description for facilitating the definition, maintenance, and presentation of scenarios; defining a sequence of steps by defining software elements from said system description as represented by selecting software elements on said data flow diagrams in accordance with a predetermined syntax; and saving said steps with sufficient information to reproduce the scenarios.
Claim 3
Dependent Claim
95 words
A scenario presentation method as set forth in claim 1 wherein said system description comprises an object model of the type utilized in object oriented analysis and including means for reading and displaying such object information and selecting elements therefrom, said object model representing the result of an object oriented analysis of said system, wherein said sequence of steps is defined by selecting and defining software elements from said model in accordance with a predetermined syntax and said steps are saved with sufficient information to reproduce the scenarios in the event the model has changed.
Claim 4
Dependent Claim
38 words
A scenario presentation method as set forth in claim 2 wherein, when a scenario is at least in part defined, including a step of sequential animation wherein said steps are animated sequentially by way of a graphical technique.
Claim 5
Dependent Claim
22 words
A scenario presentation method as set forth in claim 3 wherein said animation step includes the presentation of a pertinent textual annotation.
Claim 6
Dependent Claim
22 words
A scenario presentation method as set forth in claim 3 wherein said animation step includes the presentation of a pertinent voice annotation.
Claim 7
Dependent Claim
21 words
A scenario presentation method as set forth in claim 3 wherein said sequential animation is synchronized with said pertinent voice annotation.
Claim 8
Dependent Claim
41 words
A scenario presentation method as set forth in claim 3 wherein said sequential animation is synchronized with said pertinent voice annotation such that animation of a step does not begin until completion of the voice annotation pertaining to the preceding step.
Claim 9
Dependent Claim
20 words
A scenario presentation method in accordance with claim 3 wherein said animation occurs in single steps subject to user control.
Claim 10
Dependent Claim
17 words
A scenario presentation method in accordance with claim 3 wherein said animation occurs in a continuous mode.
Claim 11
Dependent Claim
20 words
A scenario presentation method in accordance with claim 3 wherein said chosen scenario is displayed as a message sequence chart.
Claim 12
Dependent Claim
23 words
A scenario presentation method as set forth in claim 2 , wherein said scenario comprises a header, diagram information and a step list.
Claim 13
Dependent Claim
22 words
A scenario presentation method as set forth in claim 11 , wherein said scenario comprises a requirements list and a columns list.
Claim 14
Dependent Claim
37 words
A scenario presentation method as set forth in claim 12 , wherein said header comprises a scenario name, a filename version, textual annotation or description, a methodology, a viewform, an initial state a voice annotation or soundfile.
Claim 15
Dependent Claim
24 words
A scenario presentation method as set forth in claim 12 wherein said columns list comprises an object and an initial state for said object.
Claim 16
Dependent Claim
20 words
A scenario presentation method as set forth in claim 12 wherein said Requirements list comprises a name and a description.
Claim 17
Dependent Claim
34 words
A scenario presentation method as set forth in claim 11 wherein said diagram information comprises a model, a diagram ids, diagram names, elements, element types, positions, sizes, names, instance numbers, ids, and flow direction.
Claim 18
Dependent Claim
25 words
A scenario presentation method as set forth in claim 11 wherein said Step list diagram source object destination object, a method invocation on the destination.
Claim 19
Dependent Claim
112 words
A scenario presentation method as set forth in claim 1 wherein said system description comprises a hierarchy of data flow diagrams of the type utilized in structured analysis and structured design, and including means for reading and displaying such data flow diagrams and selecting elements thereon, for facilitating the definition, maintenance, and presentation of scenarios, said data flow diagrams representing a functional decomposition of said system, wherein said sequence of steps is defined by selecting elements on said data flow diagams in accordance with a predetermined syntax and said steps are saved with sufficient information to reproduce the scenarios in the event the data flow diagrams are missing, at least in part.
Claim 20
Dependent Claim
127 words
A scenario presentation system as set forth in claim 18 and including a browse mode, wherein said definition comprises the following steps: upon selection by a user of one of New Scenario and Define steps, said system leaves said browse mode and enters a Define steps mode, said system at this point awaiting said user to select one of a source node and a flow; selection of a unidirectional flow being sufficient to define a step because it is unambiguous and it connects two nodes to each other; upon selection of a bidirectional flow, this being an ambiguous state requiring a definition of which one of said nodes is the destination, said system awaits a destination node; and upon receiving an invalid entry, issues a complaint signal.
Claim 21
Dependent Claim
128 words
A scenario presentation system as set forth in claim 19 wherein said definition comprises the following steps: upon selection by a user of one of New Scenario and Browse modes, said system transitions from Browse mode to a Define steps mode; upon selection of a source column by the user, said system awaits selection of a destination column; upon selection of an invalid column while waiting for destination, said system will issue a complaint message; upon selection of a valid column, said system presents for selection all legal connections, since this is on a SASD data flow, all the legal connections can be presented for selection; and in the event of only one single valid connection being possible, said system provides it automatically and the step is defined.
Claim 22
Dependent Claim
48 words
A scenario presentation method as set forth in claim 18 wherein a step conveys information from a source node to a destination node by way of data flow, wherein said step of saving includes storing diagrammatic information on said source node, said destination node, and said data flow.
Claim 23
Dependent Claim
29 words
A scenario presentation method as set forth in claim 21 wherein said diagrammatic information includes name, position, and type information on said nodes and data flow, with directionality information.
Claim 24
Dependent Claim
44 words
A scenario presentation method as set forth in claim 18 including a step of conveying information from a source node to a destination node by way of data flow, wherein said information includes any of a value, a data type, and a symbolic reference.
Claim 25
Dependent Claim
44 words
A scenario presentation method as set forth in claim 18 insluding a step of conveying information from a source node to a destination node by way of data flow, wherein said information includes any of a voice annotation, textual annotation, and state change information.
Claim 26
Dependent Claim
23 words
A scenario presentation method as set forth in claim 18 , wherein said scenario comprises a header, diagram information and a step list.
Claim 27
Dependent Claim
22 words
A scenario presentation method as set forth in claim 25 , wherein said scenario comprises a requirements list and a columns list.
Claim 28
Dependent Claim
37 words
A scenario presentation method as set forth in claim 26 , wherein said header comprises a scenario name, a filename version, textual annotation or description, a methodology, a viewform, an initial state a voice annotation or soundfile.
Claim 29
Dependent Claim
20 words
A scenario presentation method as set forth in claim 26 wherein said columns list comprises a diagram and a node.
Claim 30
Dependent Claim
128 words
A scenario presentation method as set forth in claim 28 wherein said definition comprises the following steps: upon selection by a user of one of New Scenario and Browse modes, said system transitions from Browse mode to a Define steps mode; upon selection of a source column by the user, said system awaits selection of a destination column; upon selection of an invalid column while waiting for destination, said system will issue a complaint message; upon selection of a valid column, said system presents for selection all legal connections, since this is on a SASD data flow, all the legal connections can be presented for selection; and in the event of only one single valid connection being possible, said system provides it automatically and the step is defined.
Claim 31
Dependent Claim
20 words
A scenario presentation method as set forth in claim 26 wherein said Requirements list comprises a name and a description.
Claim 32
Dependent Claim
34 words
A scenario presentation method as set forth in claim 25 wherein said diagram information comprises a model, a diagram ids, diagram names, elements, element types, positions, sizes, names, instance numbers, ids, and flow direction.
Claim 33
Dependent Claim
47 words
A scenario presentation method as set forth in claim 25 wherein said diagram information comprises model column information (MSC) saved in the order it was last displayed, column names, column positions, rows saved as flows in sequence from top to bottom, names, positions, directions, source, and destination.
Claim 34
Dependent Claim
39 words
A scenario presentation method as set forth in claim 25 wherein said Step list comprises a diagram, a source node, a flow id, a destination node, an id value, a description, a state, a state scope, and a soundfile.
Claim 35
Dependent Claim
30 words
A scenario presentation method as set forth in claim 25 wherein said Step list comprises a diagram, a source object, a destination object, and a method invocation on the destination.
Claim 36
Dependent Claim
162 words
A scenario presentation method for use in software development for the definition, maintenance, and presentation of scenarios, said scenarios comprising a series of steps representing the dynamic behavior of a system, said method comprising the steps of: utilizing a hierarchy of purely symbolic data flow diagrams and means for reading and displaying data flow diagrams, with the data representing software subsystems so that said data flow diagrams represent a functional decomposition of said system, wherein said data flow is in purly symbolic form; selecting elements on said data flow diagrams for facilitating the definition, maintenance, and presentation of scenarios, said data flow diagrams representing a functional decomposition of said system; defining a sequence of steps by selecting and defining software elements as represented by selecting software elements on said data flow diagrams in accordance with a predetermined syntax; and saving said steps with sufficient information to reproduce the scenarios in the event the data flow diagrams are missing, at least in part.
Claim 37
Dependent Claim
162 words
A scenario presentation method for use in software development for the definition, maintenance, and presentation of scenarios, said scenarios comprising a series of steps representing the dynamic behavior of a system, said method comprising the steps of: utilizing a hierarchy of purely symbolic data flow diagrams and means for reading and displaying data flow diagrams, with the data representing software subsystems so that said data flow diagrams represent a functional decomposition of said system, wherein said data flow is in purly symbolic form; selecting elements on said data flow diagrams for facilitating the definition, maintenance, and presentation of scenarios, said data flow diagrams representing a functional decomposition of said system; defining a sequence of steps by selecting and defining software elements as represented by selecting software elements on said data flow diagrams in accordance with a predetermined syntax; and saving said steps with sufficient information to reproduce the scenarios in the event the data flow diagrams are missing, at least in part.
Claim 38
Dependent Claim
127 words
A scenario presentation method as set forth in claim 35 and including a browse mode, wherein said definition comprises the following steps: upon selection by a user of one of New Scenario and Define steps, said system leaves said browse mode and enters a Define steps mode, said system at this point awaiting said user to select one of a source node and a flow; selection of a unidirectional flow being sufficient to define a step because it is unambiguous and it connects two nodes to each other; upon selection of a bidirectional flow, this being an ambiguous state requiring a definition of which one of said nodes is the destination, said system awaits a destination node; and upon receiving an invalid entry, issues a complaint signal.
Claim 39
Dependent Claim
48 words
A scenario presentation method as set forth in claim 35 wherein a step conveys information from a source node to a destination node by way of data flow, wherein said step of saving includes storing diagrammatic information on said source node, said destination node, and said data flow.
Claim 40
Dependent Claim
29 words
A scenario presentation method as set forth in claim 35 wherein said diagrammatic information includes name, position, and type information on said nodes and data flow, with directionality information.
Claim 41
Dependent Claim
22 words
A scenario presentation method as set forth in claim 38 , wherein said scenario comprises a requirements list and a columns list.
Claim 42
Dependent Claim
37 words
A scenario presentation method as set forth in claim 38 , wherein said header comprises a scenario name, a filename version, textual annotation or description, a methodology, a viewform, an initial state a voice annotation or soundfile.
Claim 43
Dependent Claim
34 words
A scenario presentation method as set forth in claim 38 wherein said diagram information comprises a model, a diagram ids, diagram names, elements, element types, positions, sizes, names, instance numbers, ids, and flow direction.
Claim 44
Dependent Claim
47 words
A scenario presentation method as set forth in claim 38 wherein said diagram information comprises model column information (MSC) saved in the order it was last displayed, column names, column positions, rows saved as flows in sequence from top to bottom, names, positions, directions, source, and destination.
Claim 45
Dependent Claim
39 words
A scenario presentation method as set forth in claim 38 wherein said Step list comprises a diagram, a source node, a flow id, a destination node, an id value, a description, a state, a state scope, and a soundfile.
Claim 46
Dependent Claim
30 words
A scenario presentation method as set forth in claim 38 wherein said Step list comprises a diagram, a source object, a destination object, and a method invocation on the destination.
Claim 47
Dependent Claim
44 words
A scenario presentation method as set forth in claim 35 including a step of conveying information from a source node to a destination node by way of data flow, wherein said information includes any of a value, a data type, and a symbolic reference.
Claim 48
Dependent Claim
20 words
A scenario presentation method as set forth in claim 45 wherein said columns list comprises a diagram and a node.
Claim 49
Dependent Claim
20 words
A scenario presentation method as set forth in claim 45 wherein said Requirements list comprises a name and a description.
Claim 50
Dependent Claim
22 words
A scenario presentation method as set forth in claim 46 wherein said animation step includes the presentation of a pertinent textual annotation.
Claim 51
Dependent Claim
22 words
A scenario presentation method as set forth in claim 46 wherein said animation step includes the presentation of a pertinent voice annotation.
Claim 52
Dependent Claim
37 words
A scenario presentation method as set forth in claim 49 , wherein said header comprises a scenario name, a filename version, textual annotation or description, a methodology, a viewform, an initial state a voice annotation or soundfile.
Claim 53
Dependent Claim
34 words
A scenario presentation method as set forth in claim 49 wherein said diagram information comprises a model, a diagram ids, diagram names, elements, element types, positions, sizes, names, instance numbers, ids, and flow direction.
Claim 54
Dependent Claim
25 words
A scenario presentation method as set forth in claim 49 wherein said Step list diagram source object destination object, a method invocation on the destination.
Claim 55
Dependent Claim
21 words
A scenario presentation method as set forth in claim 46 wherein said sequential animation is synchronized with said pertinent voice annotation.
Claim 56
Dependent Claim
24 words
A scenario presentation method as set forth in claim 53 wherein said columns list comprises an object and an initial state for said object.
Claim 57
Dependent Claim
20 words
A scenario presentation method as set forth in claim 54 wherein said Requirements list comprises a name and a description.
Claim 58
Dependent Claim
22 words
A scenario presentation method as set forth in claim 30 , including the step of generating a textual transcript of said scenario.
Claim 59
Dependent Claim
22 words
A scenario presentation method as set forth in claim 1 , including the step of generating a textual transcript of said scenario.
Claim 60
Dependent Claim
44 words
A scenario presentation method as set forth in claim 35 insluding a step of conveying information from a source node to a destination node by way of data flow, wherein said information includes any of a voice annotation, textual annotation, and state change information.
Claim 61
Dependent Claim
23 words
A scenario presentation method as set forth in claim 35 , wherein said scenario comprises a header, diagram information and a step list.
Claim 62
Dependent Claim
158 words
A scenario presentation method for use in software development for the definition, maintenance, and presentation of scenarios, said scenarios comprising a series of steps representing the dynamic behavior of a system, said method comprising the steps of: utilizing a hierarchy of purely symbolic data flow diagrams, with the data representing software subsystems so that said data flow diagrams represent a functional decomposition of said system, wherein said data flow is in purly symbolic form; reading and displaying such data flow diagrams; selecting elements on said data flow diagrams for facilitating the definition, maintenance, and presentation of scenarios, said data flow diagrams representing a functional decomposition of said system; defining a sequence of steps by defining software elements, as represented by selecting software elements on said data flow diagrams in accordance with a predetermined syntax; and saving said steps with sufficient information to reproduce the scenarios in the event the data flow diagrams are missing, at least in part.
Claim 63
Dependent Claim
158 words
A scenario presentation method for use in software development for the definition, maintenance, and presentation of scenarios, said scenarios comprising a series of steps representing the dynamic behavior of a system, said method comprising the steps of: utilizing a hierarchy of purely symbolic data flow diagrams, with the data representing software subsystems so that said data flow diagrams represent a functional decomposition of said system, wherein said data flow is in purly symbolic form; reading and displaying such data flow diagrams; selecting elements on said data flow diagrams for facilitating the definition, maintenance, and presentation of scenarios, said data flow diagrams representing a functional decomposition of said system; defining a sequence of steps by defining software elements, as represented by selecting software elements on said data flow diagrams in accordance with a predetermined syntax; and saving said steps with sufficient information to reproduce the scenarios in the event the data flow diagrams are missing, at least in part.
Claim 64
Dependent Claim
38 words
A scenario presentation method as set forth in claim 60 wherein, when a scenario is at least in part defined, including a step of sequential animation wherein said steps are animated sequentially by way of a graphical technique.
Claim 65
Dependent Claim
23 words
A scenario presentation method as set forth in claim 60 , wherein said scenario comprises a header, diagram information and a step list.
Claim 66
Dependent Claim
22 words
A scenario presentation method as set forth in claim 60 , wherein said scenario comprises a requirements list and a columns list.
Claim 67
Dependent Claim
22 words
A scenario presentation method as set forth in claim 60 , including the step of generating a textual transcript of said scenario.
Claim 68
Dependent Claim
41 words
A scenario presentation method as set forth in claim 46 wherein said sequential animation is synchronized with said pertinent voice annotation such that animation of a step does not begin until completion of the voice annotation pertaining to the preceding step.
References Cited (Backward Citations)
USPTO Annuity & Maintenance Windows
| Annuity Stage | Window Opens | Payment Deadline | Surcharge Period Until | Estimated Fee | Status |
|---|---|---|---|---|---|
| 3.5 Years (Year 4) | 2004-03-19 | 2004-09-18 | 2005-03-20 | $2000.00 | Window Closed / Lapsed |
| 7.5 Years (Year 8) | 2008-03-19 | 2008-09-18 | 2009-03-20 | $3760.00 | Window Closed / Lapsed |
| 11.5 Years (Year 12) | 2012-03-19 | 2012-09-18 | 2013-03-20 | $7700.00 | Window Closed / Lapsed |