Ramco Systems Limited

Rameo Systems Limited

Raghuram Devalla

Srinivasan Ramaswamy

Parthasarathy Sundararajan

Krishnamoorthy Meenakshisundaram

Shyamala Jayaraman

Suresh Sathiavageeswaran

Natarajan Krishnan

Subramanian Seetharaman

Venkatasubramanian Ramaratnam

Rajagopalan Sethuraman

Kannappan Gopalsamy

Madusudanan Rajaraman

Kanappan Gopalsamy

Kannappan Gopalswamy

Raman Srinivasan

Partasarathy Sundararajan

Aparna Ramnath

Priyadarshini Sridhar

Prema Subramaniam

Krishnan Natarajan

Srinivasan Sankaran

Shanmugavel R Ponnaiah

Srirangan Pandimani

A computer implemented model-driven method to generate platform specific code for a user interface is disclosed. In one embodiment, the method includes, capturing customer requirements of the software component in a schema, modeling business-software architecture of the software component in a first level of the schema, modeling technical architecture of the software system from the modeled business-software architecture in a second level of the schema, defining events in the schema that connect the first level and the second level of the schema, defining links in the schema that represent interactions between the user interfaces, defining integration services in the schema for each of the events, mapping each element in the first level to a corresponding one of the elements in the second level using the events, links, and integration services in the schema, loading the schema of the software component into a code generation repository.

Component based software system

Method and system for capturing device-independent user interface structure in a model based software system are disclosed. In one embodiment, at least one entry point is received from a user by a business system. Further, a user interface corresponding to the at least one entry point is provided. Furthermore, user interface meta-data associated with the user interface is captured. Also, at least one event associated with user interface elements is identified as a response to user actions based on the captured user interface meta-data. In addition, a pattern signature is identified in the model based software system for reuse in one or more model based software systems based on an expected behavior of the user interface when the identified at least one event occurs. Then, the identified at least one event is mapped to the identified pattern signature.

Method and system for capturing user interface structure in a model based software system

User interfaces and software reuse in model based software systems is disclosed. In one embodiment, user interface data is captured from business documents. Further, user interface elements are mapped to the business documents. A data model is formed for the business documents. A set of business rules for each business component in the data model is provided. A sequence of business rules associated with each action in the data model is scanned. In addition, a first pattern signature associated with an action that uniquely identifies each of the sequence of business rules is formed. It is determined if the first pattern signature is present in other actions in the data model. If so, the first pattern signature is included in a set of pattern signatures of the data model, else step of determining for a second pattern signature that is a subset of the first pattern signature is repeated.

User interfaces and software reuse in model based software systems

A system and method for testing a software development activity of an enterprise application is disclosed. In one embodiment, the method includes obtaining a software structure specification for an enterprise application and automatically generating test plans using the software structure specification. The method also includes automatically determining at least one test path in each test plan using the software structure specification, and automatically deriving a plurality of test cases using each test path. Further, the method includes executing each of the plurality of test cases and recording test results.

Method and system for testing a software development activity

In a model based software system, a set of business rules is scanned, and patterns are identified. The patterns are then compared, and similarities identified which indicate that software can be reused in the system. In one embodiment, identifiers of the rules are scanned. In another embodiment, usage patterns are used for designing a middle layer and generating code. In another embodiment of the invention, a data model is generated by capturing data from a user interface for a business document.

Software reuse in model based software systems

A system and method for model driven software is disclosed. In one embodiment, the method of handling changes to a software system in a business environment includes capturing customer requirements of the software system in a schema, modeling business-software architecture of the software system in a first level of the schema, modeling design architecture of the software system in a second level of the schema, defining events that connect the first level and second level of the schema, defining links that represent interactions between the user interfaces, defining integration services for each of the events, mapping each element in the first level to a corresponding one of elements in the second level using the events, links and integration services, creating a knowledge repository with a traversable user interface representing the mappings, identifying changes to the software system, and analyzing impact of the changes using the knowledge repository.

Model driven software

A method and system of a software development using visual action elements is disclosed. In one embodiment, the method includes providing a user interface with action elements, and providing a mechanism for specification and review of the action elements using the user interface. For example, providing a user interface includes providing a prototype of the user interface in a web browser and providing a mechanism for specification and review includes providing a toolbar with functionality to record user comments regarding the action elements. The method may also include providing a user interface to document the user interface. The method may further include providing an animated view of stimulus response behavior of the action elements.

Software development using visual interfaces

A system and method for auditing enterprise data is disclosed. A non-intrusive enterprise application audit trail has the ability to configure and track only data that is selected, thereby conserving system resources. In one embodiment, a method includes providing one or more configuration facilities in an enterprise application, viewing configuration parameters, viewing modified enterprise data in the context of change management, and changing said configuration parameters so that data tracking in said enterprise application is performed only on select data. The method also includes invoking a database triggers facility to identify said select data to be tracked.

System and method for auditing enterprise data

A system and method for deploying software is disclosed. In one embodiment, information regarding software components and their interactions, deliverables and deployment descriptors, hardware topology, layer information, and database information are all captured in a model. The model in then used to install the software on a particular machine. In another embodiment, an organizational structure is used to create an access map, and access rights to the installed software are generated and enforced.

Flexible deployment of software applications

A method and apparatus to afford a technical application for gathering, storing, tracking, and using requirements, engineering software for those requirements, and releasing finished enterprise software. A method is described that gathers requirements into a constrained data structure designed to facilitate the engineering of pre-specified definitions of the work to be done. A data structure and schema are described that organizes the gathering of requirements, the engineering of software that meet those requirements, and the orderly release of the software components. A computer readable medium is described, the medium having computer executable instruction to cause a system perform the method.

Software life cycle availability over the internet

Structured approach to software specification

A system monitors software development processes. In an embodiment, key components are identified in a requirements specification, verification rules are applied to delivered requirements, and entities is the requirements specification are validated. In another embodiment, a standard set of review types are generated, review checklists are generated, the review checklists are allocated, and review points are collected and tracked. In a further embodiment, a standard work break down structure and standard work products are defined, a high level plan is formed, and a planning template is formed. In another embodiment, the planning and tracking of a software development process and software product quality are stored in an integrated system, work products are reviewed, defects in the work products are recorded, and any defects are tracked until the completion of the software development process.

System for measuring, controlling, and validating software development projects

A system and method to analyze interactions among software artifacts within enterprise applications. The system includes an artifact analyzer module an artifact code parsing module and an artifact token processing module. The artifact analyzer module generates artifact tokens associated with trigger points in which processing control passes between a first software object and a second software object in the enterprise application and an interaction token repository for storing artifact tokens. The artifact tokens describe identity of the first software object, ownership of the first software object containing the trigger point, a location within first software object of the trigger point, and identity of the second software object. These artifact tokens are stored within an interaction token repository for later use.

Method and system for analyzing interaction among software artifacts

A system and method for generating software documentation and training material within a software development activity are described. The system includes a software coding module. a user interface module; and a testing module for providing an integrated testing environment within a software development system. The testing module includes an automated documentation generation module for generating documentation for an application and related software modules and an automated software training generation module for generating user training materials for an application and related software modules. The automated documentation generation module and the automated software training generation module utilize software specification structure defining the application and related software modules.

Growing community of inventors

Chennai, India

Raghuram Devalla