Create a requirements management tool (RMT) based on a graph database.
This is my personal space page where I will be keeping notes and such:
First, I'm a requirements engineer, have been for 15 years, and I've used a variety of RMTs in that time. Most are cumbersome, expensive beasts that most engineers hate to use. I think I have the experience and insight to design an RMT that does its job well and won't earn the ire of its users.
Second, graph databases fascinate me and I would love the chance to learn about them in the context of an RMT. A cornerstone of requirements management is traceability, i.e. linking between requirements. I believe a graph database would naturally solve problems that RMTs have in traceability.
Third, my programming language of choice is Ruby and I would like to learn Ruby on Rails.
Example RMTs (strong, heavy engineering, expensive, used in automotive, aviation, etc. industries) include DOORS, DOORS Next Generation, Polarion, Jama. I would consider Jira a weak RMT, in that it can be wrestled into being an RMT but was not designed for it.
Learn to use graph database Neo4j in the context of managing requirements.
Learn to use Ruby on Rails in the context of submitting searches to Neo4j and displaying/interacting with results.
- I learn by example so I would like to make examples of what I/we learn that could be easily dissected and copied.
Of course, if you joined and had other goals I would love to hear about them!
Setup server/VM thingy to host the project.
Install Neo4j graph database and be able to manipulate data and query from the command line.
Come up with small dataset of requirements including linking to initially populate graph database.
Install Ruby on Rails and make sure initial canned page can be accessed from outside the server/VM thingy.
Setup git somewhere to version control the project.
Essentially, what I want to have in the end is this:
Login page, something standard and secure.
Query page, where you type in the search query. First step would be entering "cypher" which is what the Neo4j search language is called. The next two are stretch goals... Second step would be coming up with some kind of JQL (Jira Query Language) like thing that typical users are used to. Third step is developing a search/results chain - this idea I would have to explain to you with pictures, it's hard to describe in pure text.
Results page, where you see and interact with the search results. First step would be displaying the results in a traditional spreadsheet-like matrix. Rows are nodes, columns are attributes. Rows come from the search results. Would need a way to add columns including linked content. Second step would be interacting with the results like changing attribute values and linking. Also sorting of results. Would really need to implement all of this for the project to be useful.
Port page, where you can export the results. First step is export to CSV, Excel, XML, JSON, YAML, whatever. Second step would be importing to change database. The whole Port page is a stretch goal.
I have a bunch more notes and drawings about how I want it to look and work and I will try to get those added here before Hack Week starts.
I could really use someone experienced in setting up, configuring, and developing Ruby on Rails, or at least willing to learn with me. I know Ruby but have never worked with Ruby on Rails.
Someone has expressed interest in helping me here = I could really use someone experienced in setting up and configuring the infrastructure. My main problem with these kinds of projects is the infrastructure and initial setup. I usually fail miserably in this regard. Or even if you could help me pre-Hack Week during off hours, that would be a big help! Learning how to do this stuff is not a goal of mine. I've always been bad at this and I have no interest in getting better. I just want it done.
And this is Hack Week after all, so anyone is welcome to join me!
By the way, I don't know if this is a Hack Week thing but I would certainly accept partial commitments of some hours. Especially for infrastructure. I would like to focus on my primary goals and not wrestling with setup.
requirements, requirements management, requirements engineering, graph, graph database, ruby, ruby on rails
That didn't go well... I won't complain though; I am very appreciative to SUSE for giving me the opportunity to work on the project on their dime and time.
This project is part of:
Hack Week 20
This project is one of its kind!