Chronological Thread 

< Chronological >      < Thread >

---

Yes I think the document should be incorporated into the LibCellML project, after changes have been made.

I think that this document is a fine place for managing a list of use cases. Each use case is turned into an issue on GitHub when it is needed and then worked on following the development process.

I see this list as the basis for work that needs to be carried out to satisfy the aims of the libCellML project. So it fits in very well with agile methodologies where you have a big list of items that need to be completed to meet your aims and you adjust the list as your aims vary.


On 01/28/15 15:30, Randall Britten wrote:

Hi

Before I jump in and work on formatting, and so on, I think the bigger question is: is this document considered valuable, and something we want to incorporate into the LibCellML project?

If the consensus is that we should adopt this, then I agree that there is lots of room for improving the layout etc, but we should perhaps also consider something better than a document for managing lists of use cases (UCs) (we’ve already discussed that perhaps each UC becoming a GitHub issue, we could do that in bulk, or as we select what to work on next.)

I don’t agree that a use case should be worked on (including documenting the use case itself) prior to the point that it is selected as the next work item. This is based on my understanding of agile methodologies such as Scrum and Extreme Programming (XP).

Regards,
Randall

From: Hugh Sorby
<h.sorby AT auckland.ac.nz

<mailto:h.sorby AT auckland.ac.nz>>
Reply-To: "cellml-tools-developers AT lists.cellml.org <mailto:cellml-tools-developers AT lists.cellml.org>" <cellml-tools-developers AT lists.cellml.org <mailto:cellml-tools-developers AT lists.cellml.org>>
Date: Wednesday, 28 January 2015 3:02 pm
To: "cellml-tools-developers AT lists.cellml.org <mailto:cellml-tools-developers AT lists.cellml.org>" <cellml-tools-developers AT lists.cellml.org <mailto:cellml-tools-developers AT lists.cellml.org>>
Subject: Re: [[cellml-dev] ] libCellML use cases


feedback:

* I would like to see the document re-ordered have the notes at the
bottom, categories as headings and the use case(s) listed below
the category headings
* have the use cases listed in order of priority or if the priority
is not known the order that they are going to be worked on
* have the use cases listed as they would be tested using gtest
* have the first few use cases explicitly written out
* turn the linked google doc into an actual table in the document

Cheers,
Hugh.

On 01/28/15 11:10, Randall Britten wrote:

Hi all

Some months ago, I started this document listing brief and informal descriptions of potential libCellML use cases: https://github.com/codecurve/libcellml/blob/listUsecases01/docs/source/usecases.rst

These could help with project planning. During a discussions today and last week, we decided to mail this out for feedback. We foresee that many of these use cases will map to issues created in the libCellML tracker on GitHub, and hence become work items on the project and get implemented.

I’ll respond to feedback the same day or the next working day where applicable.

Regards,
Randall Britten

---

• [[cellml-dev] ] libCellML use cases, Randall Britten, 01/28/2015
  • Re: [[cellml-dev] ] libCellML use cases, Hugh Sorby, 01/28/2015
    • Re: [[cellml-dev] ] libCellML use cases, Randall Britten, 01/28/2015
      • Re: [[cellml-dev] ] libCellML use cases, Hugh Sorby, 01/28/2015
        • Re: [[cellml-dev] ] libCellML use cases, David Nickerson, 01/29/2015

---

Archive powered by MHonArc 2.6.18.