jducoeur: (Default)
[personal profile] 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 ([livejournal.com profile] 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...

(no subject)

Date: 2012-10-22 02:55 pm (UTC)
mermaidlady: heraldic mermaid in her vanity (Default)
From: [personal profile] mermaidlady
Yesterday [livejournal.com profile] 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.

(no subject)

Date: 2012-10-22 08:51 pm (UTC)
mermaidlady: heraldic mermaid in her vanity (Default)
From: [personal profile] mermaidlady
Yes, I'd love to. I'm quite excited about all the potential of this project.

(no subject)

Date: 2012-10-22 04:55 pm (UTC)
From: [identity profile] 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.

Did somebody say meta?

Date: 2012-10-22 05:28 pm (UTC)
From: [identity profile] etherial.livejournal.com
It sounds to me like [livejournal.com profile] jducoeur has a use case for tracking use cases. I'd start the requirements list with a field for Requirements Lists.

(no subject)

Date: 2012-10-22 06:59 pm (UTC)
From: [identity profile] dervishspin.livejournal.com
Oh good! Keep me posted. I am probably slightly less passionate than you about the usability of it, but possibly not by much. It is a bloody thorn in the side around here.

"Conventional" would be useful. We use Agile while we can, but we are not an Agile shop across the board so some of the voting stuff is interesting, but not required for most stuff we are doing, plain old prioritization functionality would be good enough.

(no subject)

Date: 2012-10-22 05:36 pm (UTC)
dsrtao: (glasseschange)
From: [personal profile] 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.

(no subject)

Date: 2012-10-22 06:58 pm (UTC)
ext_81047: (Dr. Morden clone #187)
From: [identity profile] 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.

(no subject)

Date: 2012-10-22 08:37 pm (UTC)
ext_81047: (My character from Rider on a Pale Horse)
From: [identity profile] kihou.livejournal.com
Sure, but "LARP-writing in general" and "for the Assassins' Guild" are not quite the same thing. You probably don't have mandatory features like:

* Subversion text file interface, or similar
* LaTeX-ish markup support
* LaTeX=>pdf rendering support

Presumably Querki will at some point give me enough rope that I could consider migrating to it, and it's presumably going to be much slicker than something I'm going to put together myself. And the multiple-app nature of it probably would be a cleaner way of handling the separation of "Game Content", "Player Apps", "Per-run State", and "Runtime Interface".

(no subject)

Date: 2012-10-22 09:54 pm (UTC)
ext_81047: (In a tree)
From: [identity profile] kihou.livejournal.com
The Subversion support isn't just for versioning; it's also to satisfy people who don't want to use a browser or learn a new workflow. (The Guild has both large "hates anything non-commandline" and "hates the commandline" contingents.)

LaTeX for the PDF export is mainly because then I can use our existing code for rendering pretty item cards, etc and be at prettyness-pariety with standard (i.e., GameTeX) games. I don't know what other options there are for pretty PDF, but it seems likely that you'll want some option there. (If I'm keeping my recipes there, I also want to be able to get the same recipes in a pretty book.)

Profile

jducoeur: (Default)
jducoeur

June 2025

S M T W T F S
12 34567
891011121314
15161718192021
22232425262728
2930     

Most Popular Tags

Style Credit

Expand Cut Tags

No cut tags