Sunday, April 12, 2009

I am continuing work on reviewing and defining requirements for a SCM tool. I have found a tool called Protégé that I am reviewing to use to enter my detailed requirements. Then I can analyze these and create N3 and RDF I hope. I am curious to see how this can be used to evaluate requirements and help determine the best choice for a tool.

So my abstract is as follows for my paper:
Semantic web technologies provide a way to add meaning to data and to use software tools to help navigate that data in new and interesting ways. This paper explores the use of semantic web technologies in the area of Software Configuration Management (SCM) tools and how to select the correct one for your project or organization. Specifically, this paper reports on how variables in selecting a tool have been used to help solve the problem of what requirements are met by analyzing the functionality of each tool and determining how each requirement has or has not been met. The results of this effort will show that we were able to select the best SCM tool for the job.

This paper will attempt to break down the requirements for a SCM tool and develop an ontology so that they can be analyzed, rated, and matched to specific tools provided by several vendors. N3 notation can be used to structure the requirements and to convert them into RDF. I will be exploring a tool called Protégé in an attempt to explore the requirements for this topic in SCM tools. There are many levels of requirements when looking at tools and semantic web technology is a good mechanism to help delve into these requirements to create a tree structure of classes, subclasses and inference components.

So my main goal is here is to determine the best way to break the components down from the requirements. I will create a spreadsheet to list the requirements, and review a product called Protégé that I will enter the requirements into and be able to graph and evaluate further to try and simplify the presentation of the requirements in terms of evaluating them for each tool vendor. Then from Protégé I will be able to export the requirements to N3 notation and RDF.