Institutional Software Repository: Enabling Intellectual Property Awareness on Academic Campuses
Published in the Proceedings of the PLANNER 2006 Conference, India
Software is a critical digital content component that is generated on academic campus by way of mandatory course... more Software is a critical digital content component that is generated on academic campus by way of mandatory course requirements. These software need to be protected with an assigned ownership and a specific terms of use. Software that is generated on campuses typically does not get archived or catalogued in campus-wide repositories. SALIS a prototype software repository addresses these needs and serves to augment typical institutional repositories. This paper attempts to bring out the need for protecting the software generated on campuses and the need to archive it in an orderly manner. Additionally SALIS also addresses Intellectual Property concerns such as ownership, protection and terms of use of the software produced and provide an effective way of archiving
28 views
Seen by:
Download (.pdf) 9 views
Seen by: 
Software Reuse Methods to Improve Technological Infrastructure for e-Science
Co-authored with Robert R. Downs and Chris A. Mattmann
Tools to Support the Reuse of Software Assets for the NASA Earth Science Decadal Survey Missions
Co-authored with Chris A. Mattmann, Robert R. Downs, Neal F. Most, and Shahin Samadi
Reuse of Software Assets for the NASA Earth Science Decadal Survey Missions
Co-authored with Chris A. Mattmann, Robert R. Downs, and Shahin Samadi
A Study of Earth Science Software Reuse Enablement Systems
Co-authored with Ryan Gerard, Shahin Samadi, and Robert E. Wolfe
Software Reuse Within the Earth Science Community
Co-authored with Stephen W. Olding, Robert E. Wolfe, and Victor E. Delnore
Reusing Software to Build Data Processing Systems: NPP Science Data Segment Case Study
Co-authored with Shahin Samadi, Ryan Gerard, Mary Hunter, Robert J. Schweiss, Robert E. Wolfe, and Edward J. Masuoka
The Software Reuse Working Group: A Case Study in Fostering Reuse
Co-authored with Ryan Gerard, Robert R. Downs, and Robert E. Wolfe
Software Reuse to Support Earth Science
Co-authored with Robert R. Downs, Shahin Samadi, Neil S. Gerard, Robert E. Wolfe
Relevance of Software Reuse in Building Advanced Data Processing Systems
Co-authored with Robert R. Downs and Shahin Samadi
A Proposal on Using Reuse Readiness Levels to Measure Software Reusability
Co-authored with Robert R. Downs
Progress Towards a NASA Earth Science Reuse Enablement System (RES)
Co-authored with Robert R. Downs and Chris A. Mattmann
Reuse of Software Assets for the NASA Earth Science Decadal Survey Missions
Co-authored with Chris A. Mattmann, Robert R. Downs, Neal F. Most, and Shahin Samadi
Towards an Ontology-based Retrieval of UML Class Diagrams
by Jorge Morato
Robles, K., Fraga, A., Morato, J., Lloréns, J. "Towards an Ontology-based Retrieval of UML Class Diagrams" Information and Software Technology (to appear). doi:10.1016/j.infsof.2011.07.003
Context
Software Reuse has always been an important area amongst software companies in order to increase their... more
Context
Software Reuse has always been an important area amongst software companies in order to increase their productivity and the quality of their products, but code reuse is not the only answer for this. Nowadays, reuse techniques proposals include software designs or even software specifications. Therefore, this research focuses on software design, specifically on UML Class Diagrams. A semantic technology has been applied to facilitate the retrieval process for an effective reuse.
Objective
This research proposes an ontology-based retrieval technique by semantic similarity in order to support effective retrieval process for UML Class Diagrams. Since UML Class Diagrams are a de facto standard in the design stages of a Software Development Process, a good technique is needed to reuse them, i.e. reusing during the design stage instead of just the coding stages.
Method
An application ontology modeled using UML specifications was designed to compare UML Class Diagram element types. To measure their similarity, a survey was conducted amongst UML experts. Query expansion was improved by a domain ontology supporting the retrieval phase. The calculus of minimal distances in ontologies was solved using a shortest path algorithm.
Results
The case study shows the domain ontology importance in the UML Class Diagram retrieval process as well as the importance of an element type expansion method, such as an application ontology. A correlation between the query complexity and retrieved elements has been identified, by analyzing results. Finally, a positive Return of Investment (ROI) was estimated using Poulin’s Model.
Conclusion
Because Software Reuse has not to be limited to the coding stage, approaches to reuse design stage must be developed, i.e. UML Class Diagrams reuse. This approach proposes a technique for UML Class Diagrams retrieval, which is one important step towards reuse. Semantic technology combined with information retrieval improves the retrieval results.
Suitable Reusable Components Mining to assist Developers using a Rule Based System
Fifth International Conference on Information and Management Sciences (IMS 2006) pp:266-270
Modem software engineering technologies and paradigms have been vastly affected by using reusable components.... more Modem software engineering technologies and paradigms have been vastly affected by using reusable components. Reusability of software components stands for using the existing design and developed components in new software applications to save the cost and time. Against these persuading facts, some vexing problems also subsist there as to reuse which components and how to search those particular components from the given designed scenario. The newly designed rule based framework is fairly efficient in searching desired information from a given scenario. This research has been conducted to incorporate this obvious capability of the designed framework of analyzing the given scenario and extract the required reusable components to assist the developers according to the given guidelines. The designed system provides a quick and reliable way to extract required components that are used for reuse purposed on later stages. The application with such abilities can be more intelligent and pertinent specifically for the user to save the time.
27 views
Seen by: A Modular Approach to Build Workflow Engines
Sánchez M., Puentes D., Villalobos J., A Modular Approach to Build Workflow Engines. In: BPM 2011 International Workshops. LNCS, Springer-Verlag, 2011 (to appear)
To provide BPM and workflow solutions with the dynamism to support frequent changes in the corporate environment, it... more To provide BPM and workflow solutions with the dynamism to support frequent changes in the corporate environment, it is neces- sary to adopt novel strategies to efficiently develop and adapt workflow engines. One such strategy is to build new engines by reusing as much as possible from existing components. This requires two things: firstly, the mechanisms and technologies to build a library of reusable, exten- sible and adaptable workflow components; secondly, a platform to in- tegrate those components into full applications. In this paper we show that Cumbia, being a platform for the development of workflow engines based on the modularization of workflows according to concerns, suits this task. This is illustrated with YOC, a Cumbia based implementation of YAWL.
Copyright in Custom Code: Who Owns Commissioned Software?
by TJ McIntyre
Published in 'Journal of Intellectual Property Law and Practice', 2008
When software is commissioned, it is important that the parties agree what rights are being acquired and what rights... more
When software is commissioned, it is important that the parties agree what rights are being acquired and what rights retained. Copyright is the most important such right, but moral rights and database rights must also be considered. When there is no explicit agreement on these rights, the courts are often faced with claims that there is an implied term that they should vest in the client (or be waived in the case of moral rights). This article examines the issues that arise in such cases.
The article outlines the development of case law dealing with implied terms as to ownership of commissioned works. It explains how the courts have applied older principles to the new area of commissioned software, and how those principles have evolved to make it more difficult for a client to establish an implied term in their favour. The article examines in particular issues arising from code reuse, the disclosure of source code, and the application of database rights and moral rights to software. It also considers case law where clients have claimed to be joint authors of software by virtue of their involvement in its design and testing.
There are an increasing number of cases where software is commissioned on an informal basis and disputes later arise as to the ownership of that software. This article provides a framework for considering such disputes.