IP Library Granted Patent US 8,589,858
Granted Patent B1
US 8,589,858 · App. 12/559,050 · Granted Nov 19, 2013

Requirement manager for UML and SysML application

Inventor: John Watson (Levittown, PA)
Assignee: Lockheed Martin Corporation
View Patent ↗
Loading inventors, assignments & file history…
Monitor This Case
Get email alerts when status or documents change.
Order Certified Copies
Most orders are placed with the USPTO same day — all within 24 business hours.
Order via The Patent Place →
Pre-filled with this patent's details
Quick Facts
Patent No.
US 8,589,858
App. No.
12/559,050
Granted
Nov 19, 2013
Kind
B1
Abstract

A system for displaying relationships between data of one of a UML or a SysML application includes a machine readable storage medium and a processor. The machine readable storage medium is configured to store a plurality of data for a project designed using one of the UML or the SysML applications. The processor is in signal communication with the machine readable storage medium. The processor is configured to search the computer readable storage medium for a first model element, identify a requirement relationship between the first model element and a second model element, and display the first model element and the second model element on a monitor such that the requirement relationship between the first model element and the second model element is identifiable to a user.

Claims (78)

1. A system for displaying requirement relationships between data of one of a UML or a SysML application, comprising:

a non-transitory machine readable storage medium storing a plurality of data for a project designed using one of the UML or the SysML applications; and

a processor in signal communication with the non-transitory machine readable storage medium, the processor configured to:

search the non-transitory computer readable storage medium for a first model element of the project;

identify a requirement relationship between the first model element and a second model element; and

display the first model element and the second model element on a monitor such that the requirement relationship between the first model element and the second model element is identifiable to a user;

wherein identifying the requirement relationship between the first model element and the second model element includes displaying a count of all requirements that have been satisfied, and a count of all requirements that have not been satisfied.

2. The system of claim 1 , wherein the processor is further configured to:

receive an instruction to modify data associated with the first model element; and

modify the data associated with the first model element in the non-transitory computer readable storage medium in real time.

3. The system of claim 1 , wherein the processor is further configured to:

receive a display instruction, the display instruction identifying one or more requirement relationship types to display;

store the display instruction in the non-transitory computer readable storage medium; and

cause the first model element and the one or more requirement relationships to be displayed in accordance with the display instruction.

4. The system of claim 1 , wherein the requirement relationship is one of a satisfaction, a derived, a refined, a verify, a decompose, a copy, and an allocation relationship.

5. The system of claim 1 , wherein the processor is further configured to:

receive a search term as an input;

identify data matching the search term in the non-transitory computer readable storage medium; and

cause the matching data to be displayed on the monitor.

6. The system of claim 5 , wherein the processor is further configured to receive an instruction from the user to identify requirement relationships associated with the matching data.

7. The system of claim 1 , wherein the processor is further configured to:

receive an instruction to add a requirement relationship to the first model element;

create the requirement relationship; and

store the requirement relationship in the non-transitory computer readable storage medium.

8. The system of claim 1 , wherein the processor is further configured to:

cause one of a number of unsatisfied project requirements or satisfied project requirements to be displayed on the monitor.

9. The system of claim 8 , wherein an unsatisfied project requirement includes project requirements in violation of one or more rules of the project being designed.

10. The system of claim 1 , wherein one of the first and second model elements is a requirement of the project.

11. The system of claim 1 , wherein the processor is further configured to:

identify each requirement relationships between the first model element and each of a plurality of other model elements in the non-transitory machine readable storage medium; and

display the first model element and each of the plurality of other model elements on the monitor such that the requirement relationships between the first model element and each of the plurality of other model elements is identifiable to the user.

12. A non-transitory computer readable storage medium encoded with program code, wherein when the program code is executed by a processor, the processor performs a method, the method comprising:

searching for a first model element of a project designed using one of a UML or a SysML application;

identifying a requirement relationship between the first model element and a second model element; and

displaying the first model element and the second model element such that the requirement relationship between the first model element and the second model element is identifiable to a user;

wherein identifying the requirement relationship between the first model element and the second model element includes displaying a count of all requirements that have been satisfied, and a count of all requirements that have not been satisfied.

13. The non-transitory computer readable storage medium of claim 12 , wherein the method further comprises:

receiving an instruction to modify data associated with the first model element; and

modifying the data associated with the first model element in the computer readable storage medium in real-time.

14. The non-transitory computer readable storage medium of claim 12 , wherein the method further comprises:

receiving a display instruction, the display instruction identifying one or more requirement relationship types to display;

storing the display requirement in a non-transitory computer readable storage medium; and

causing the first model element and the one or more requirement relationships to be displayed in accordance with the display instruction.

15. The non-transitory computer readable storage medium of claim 12 , wherein the requirement relationship is one of a satisfaction, a derived, a verify, a decompose, a copy, and an allocation relationship.

16. The non-transitory computer readable storage medium of claim 12 , wherein the method further comprises:

receiving a search term as an input;

identifying data matching the search term in a non-transitory computer readable storage medium; and

causing the matching data to be displayed to a user.

17. The non-transitory computer readable storage medium of claim 16 , wherein the method further comprises receiving an instruction from the user to identify requirement relationships associated with the matching data.

18. The non-transitory computer readable storage medium of claim 12 , wherein the method further comprises:

receiving an input instruction to add a requirement relationship to the first model element;

creating the requirement relationship; and

storing the requirement relationship in a computer readable storage medium that includes the data for the project designed using one of the UML or SysML applications.

19. The non-transitory computer readable storage medium of claim 12 , wherein the method further comprises displaying a number of unsatisfied project requirements to a user.

20. The non-transitory computer readable storage medium of claim 19 , wherein an unsatisfied project requirement includes project requirements in violation of one or more rules of the project being designed.

21. A method for displaying requirement relationships between data of one of a UML or a SysML application, the method comprising:

searching for a first model element of a project designed using one of a UML or a SysML application, in a computer process;

identifying a requirement relationship between the first model element and a second model element, in another computer process; and

displaying the first model element and the second model element such that the requirement relationship between the first model element and the second model element is identifiable to a user, wherein identifying the requirement relationship between the first model element and the second model element includes displaying a count of all requirements that have been satisfied, and a count of all requirements that have not been satisfied.

22. The method of claim 21 , further comprising:

receiving an instruction to modify data associated with the first model element; and

modifying the data associated with the first model element in real-time.

23. The method of claim 21 , further comprising:

receiving a display instruction, the display instruction identifying one or more requirement relationship types to display;

storing the display requirement in a computer readable storage medium; and

causing the first model element and the one or more requirement relationships to be displayed in accordance with the display instruction.

24. The method of claim 21 , wherein the requirement relationship is one of a satisfaction, a derived, a verify, a decompose, a copy, and an allocation relationship.

25. The method of claim 21 , further comprising:

receiving a search term as an input;

identifying data matching the search term in a computer readable storage medium; and

causing the matching data to be displayed to a user.

26. The method of claim 25 , further comprising receiving an instruction from the user to identify requirement relationships associated with the matching data.

27. The method of claim 21 , wherein the method includes:

receiving an input instruction to add a requirement relationship to the first model element;

creating the requirement relationship; and

storing the requirement relationship in a computer readable storage medium that includes the data for the project designed using one of the UML or SysML applications.

28. The method of claim 21 , further comprising displaying a number of unsatisfied project requirements to a user.

29. The method of claim 28 , wherein an unsatisfied project requirement includes project requirements in violation of one or more rules of the project being designed.

Assignments (2)
CONFIRMATORY LICENSE Recorded Jan 3, 2012
From: LOCKHEED MARTIN CORPORATION
To: THE GOVERNMENT OF THE UNITED STATES OF AMERICA AS REPRESENTED BY THE SECRETARY OF THE NAVY
Reel/Frame 027468/0714 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Sep 14, 2009
From: WATSON, JOHN
To: LOCKHEED MARTIN CORPORATION
Reel/Frame 023227/0236 →