Model driven software

• US 20050216890A1
• Filed: 02/01/2005
• Published: 09/29/2005
• Est. Priority Date: 03/15/2004
• Status: Abandoned Application

• Current Assignee: Ramco Systems Limited
• Original Assignee: Ramco Systems Limited
• Inventors: Sundararajan, Parthasarathy, Gopalsamy, Kannappan, Ramaswamy, Srinivasan, Devalla, Raghuram, Rajaraman, Madusudanan, Sathiavageeswaran, Suresh, Jayaraman, Shyamala, Meenakshisundaram, Krishnamoorthy
• Application Number:
  US11/048,078
• Publication Number:
  US 20050216890A1
• Time in Patent Office: Days
• US Class Current: 717/120
• CPC Class Codes: G06F 8/71 Version control security arrangements therefor G06F21/57; Configuration management

Abstract

A software model is used to capture and store software system attributes resulting in a repository of system architecture elements. After creation of the model, changes may be proposed to the system, the impact of those changes analyzed using the repository, and a decision made based on the analysis whether to go forward with the proposed changes or take some alternative action.

Claims

1. A method comprising:

capturing software system attributes in a model to create a knowledge repository representing system architecture elements;

retrieving changes to said software system; and

analyzing the impact of said proposed changes using said knowledge repository.

2. The method of claim 1, wherein said knowledge repository comprises a representation of a software specification structure for said system.

3. The method of claim 2, wherein said system comprises technologically independent architectural elements that guide said software specification.

4. The method of claim 1, further comprising identifying impacted items in said software system through connections persisted in said repository.

5. The method of claim 1, further comprising conducting said analysis until no new additions appear on a list of items to alter in response to said changes.

6. The method of claim 1, further comprising using said repository to examine proper technology mapping in response to said changes.

7. The method of claim 4, further comprising changing said impacted items.

8. The method of claim 4, further comprising:

generating artifacts of one or more of said impacted items; and

associating said artifacts with said repository elements in a maintenance management system.

9. The method of claim 8, further comprising

creating a base schema with said artifacts and said model;

and

unit testing said artifacts.

10. The method of claim 1, wherein said attributes are captured through triggered events.

11. The method of claim 10, wherein said attributes are customer requirements.

12. The method of claim 1, wherein said model comprises business processes, functions, components, activities, user interfaces, tasks, and business flows.

13. A software system model comprising:

a business architecture node;

a technical node; and

a technology node;

wherein said technology node comprises information relating to Web artifacts, application artifacts, and resource management artifacts; and

wherein deliverable artifacts are listed and stored for packaging and installation.

14. The software system model of claim 13, further comprising a resource management area.

15. The software system model of claim 13, further comprising generated source code, said generated source code stored in said resource management area of said model.

16. The software system model of claim 13, further comprising a release manager, wherein said release manager manages a work schedule for said artifacts.

17. The software system model of claim 13, further comprising checkpoints for said artifacts.

18. The software system model of claim 13, wherein said model provides a history of information regarding said system through configuration management.

19. The software system model of claim 18, wherein said history is used in connection with software maintenance releases.

20. The software system of claim 18, wherein said information comprises sets of data, said sets of data comprising documentation for each set.

21. A process comprising:

conducting an impact analysis for a software system;

generating a list of artifacts from said impact analysis;

identifying affected areas of said system based upon said impact analysis;

generating final code of said affected areas based on said list of impacted artifacts; and

releasing said artifacts into a software system.

22. The process of claim 21, wherein said impact analysis is performed in different layers of said system.

23. A computer readable medium comprising instructions available thereon for executing instructions comprising:

capturing software system attributes in a model, thereby creating a knowledge repository regarding system architecture elements;

retrieving changes to said software system; and

analyzing the impact of said proposed changes using said knowledge repository.

24. The computer readable medium of claim 23, wherein said knowledge repository is related to a representation of the software specification structure for said system.

25. The computer readable medium of claim 23, wherein said system comprises technology independent architectural elements that guide said software specifications.

26. The computer readable medium of claim 23, further comprising instructions for identifying impacted items in said software system through connections persisted in said repository.

27. The computer readable medium of claim 23, further comprising instructions for conducting said analysis until no new additions appear on a list of items to alter in response to said changes.

28. The computer readable medium of claim 23, further comprising instructions for using said repository to examine proper technology mapping in response to said changes.

29. The computer readable medium of claim 26, further comprising instructions for changing said impacted items.

30. The computer readable medium of claim 26, further comprising instructions for

generating artifacts of one or more of said impacted items;

and

associating said artifacts with said repository elements in a maintenance management system.

31. The computer readable medium of claim 30, further comprising instructions for creating a base schema with said artifacts and said model;

and unit testing said artifacts.

32. The computer readable medium of claim 23, wherein said attributes are captured through triggered events.

33. The computer readable medium of claim 32, wherein said attributes are customer requirements.

34. The computer readable medium of claim 23, wherein said model comprises business processes, functions, components, activities, user interfaces, tasks, and business flows.

35. A computer readable medium comprising instructions available thereon for executing instructions comprising:

conducting an impact analysis for a software system;

generating a list of artifacts from said impact analysis;

identifying affected areas of said system based upon said impact analysis;

generating final code of said affected areas based on said list of impacted artifacts; and

releasing said artifacts into a software system.

36. The computer readable medium of claim 35, further comprising the instruction of performing said impact analysis of said artifacts in different layers of said system.