*God*, I love this project

[jducoeur]

I'm rapidly fleshing out the Querki Use Cases and Features. The Feature list is growing terrifyingly fast, but that's what the Use Cases are for: they are going to help drive which features get implemented when. (And more importantly, which features to *not* implement yet. I'm going to have to pick my battles carefully. Nothing gets implemented until we have a concrete use for it.) I'm starting to sincerely believe that this will be useful enough that people will buy memberships.

I think I'm going to start talking about Use Cases, something like one a day, over on the development blog (querki_project). Please come join in over there, kibitz and comment, point potentially interested friends at it, and keep the ideas coming! The "what we're going to try to accomplish" train is rapidly gaining steam, and the project is looking ever-cooler and more useful...

Comments

[mermaidlady]

Yesterday new_man and I were talking about how Querki might be the right tool for cataloging our theatre stuff: costumes, props, raw materials, set pieces, lighting gear, &c. Right now it's all chaos.

It's going to be really important that we be able to have photographs (possibly multiple photographs) associated with each item.

[dervishspin.livejournal.com]

SO I thought you had captured one of the Use Cases I would ask for. It's inherent in the name. Then after reading it I realized I had made an assumption which was not true, so I'll ask a different way.

How about a Requirements Inventory?
Managing requirements for IT projects is... OMG awful. The DBs that are out there are hideous, limited in functionality and expensive. As a result, most companies are effectively tracking their requirements through email and excel spreadsheets. There must be a better, more intuitive way. Someplace that allows multiple people to work on it at the same time. Some way to track which business area came up with what requirement for what system which matches what High Level Requirement or Scope Statement.

I think as you manage your requirements for Querki, you will see what I mean.

Managing Requirements for a Managing Requirements Use Case will probably feel pretty "meta" and strange, actually.

[dsrtao]

It looks like several of these use cases could be improved by a Feature: Timeline. A Timeline is a list of things that have a time/date attribute, and is by default sorted on them.

Closely related would be a dependency relationship, and a priority list. Combining the three together you get most of project management.

[kihou.livejournal.com]

It's cool to see you running with something that's conceptually a lot like my Bazki personal project (http://bazki.mit.edu/, but there's not much there), but sufficiently ambitious and aimed at the real world instead of Assassins' Guild LARPers. You certainly have some nifty ideas.