Automated verification of a software system
US-9536093-B2 · Jan 3, 2017 · US
US2016179477A1 · US · A1
| Field | Value |
|---|---|
| Publication number | US-2016179477-A1 |
| Application number | US-201414574488-A |
| Country | US |
| Kind code | A1 |
| Filing date | Dec 18, 2014 |
| Priority date | Dec 18, 2014 |
| Publication date | Jun 23, 2016 |
| Grant date | — |
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.
The present disclosure relates to maintaining assertions in an integrated development environment (IDE) tool. According to one embodiment, the IDE receives a request to add an assertion at a specified location within source code of an application from a user interacting with an integrated development environment (IDE) tool. The source code is stored in a first file associated with a development project. The IDE tool receives a definition for the assertion and stores the definition for the assertion in a second file associated with the development project. The IDE tool creates an association in the development project between the source code of the application and the assertion.
Opening claim text (preview).
1 .- 7 . (canceled) 8 . A computer program product, comprising: A non-transitory computer-readable storage medium having computer readable program code embodied therewith, the computer readable program code configured to perform an operation for managing assertions, the operation comprising: receiving, from a user interacting with an integrated development environment (IDE) tool, a request to add an assertion at a specified location within source code of an application, wherein the source code is stored in a first file associated with a development project; receiving a definition for the assertion; storing the definition for the assertion in a second file associated with the development project; and creating an association in the development project between the source code of the application and the assertion. 9 . The computer program product of claim 8 , wherein the operations further comprise: receiving a request to compile the source code of the application; inserting the assertion in the source code at the specified location; and compiling the application from the source code. 10 . The computer program product of claim 8 , wherein the definition includes one or more of: a scope defining one or more users with access to the assertion; an expiration time; an indication whether the assertion is static or dynamic, wherein a static assertion is inserted into the source code before the application is compiled from the source code and wherein a dynamic assertion is inserted at into the source code dynamically when executing the application; and a number of times to insert the assertion into the program source code, when compiling the application from the source code. 11 . The computer program product of claim 8 , wherein the definition of the assertion comprises one or more lines of source code specifying a condition assumed to be true at the specified location. 12 . The computer program product of claim 8 , wherein the operations further comprise: receiving a request to edit the source code stored in the first file; identifying the specified location in the source code of the assertion based on the association between the source code of the application and the assertion; and presenting an indication of the assertion in an editing pane of the IDE tool at the specified location. 13 . The computer program product of claim 12 , wherein the indication identifies a scope of the assertion. 14 . The computer program product of claim 12 , wherein the indication identifies whether the assertion is active or inactive. 15 . A system, comprising: a processor; and a memory storing instructions, which, when executed by the processor, performs an operation for managing assertions, the operation comprising: receiving, from a user interacting with an integrated development environment (IDE) tool, a request to add an assertion at a specified location within source code of an application, wherein the source code is stored in a first file associated with a development project; receiving a definition for the assertion; storing the definition for the assertion in a second file associated with the development project; and creating an association in the development project between the source code of the application and the assertion. 16 . The system of claim 15 , wherein the operations further comprise: receiving a request to compile the source code of the application; inserting the assertion in the source code at the specified location; and compiling the application from the source code. 17 . The system of claim 15 , wherein the definition includes one or more of: a scope defining one or more users with access to the assertion; an expiration time; an indication whether the assertion is static or dynamic, wherein a static assertion is inserted into the source code before the application is compiled from the source code and wherein a dynamic assertion is inserted at into the source code dynamically when executing the application; and a number of times to insert the assertion into the program source code, when compiling the application from the source code. 18 . The system of claim 15 , wherein the definition of the assertion comprises one or more lines of source code specifying a condition assumed to be true at the specified location. 19 . The system of claim 15 , wherein the operations further comprise: receiving a request to edit the source code stored in the first file; identifying the specified location in the source code of the assertion based on the association between the source code of the application and the assertion; and presenting an indication of the assertion in an editing pane of the IDE tool at the specified location. 20 . The system of claim 19 , wherein the indication identifies a scope of the assertion.
Related publications grouped by family.
Answers are generated from the same data shown on this page.