|
From: Bart M. <ba...@cs...> - 2002-08-11 00:15:09
|
Here's my full list. Implement as much of this as you have
time for, and as little as you like.
+ As noted, phasing is broken in both directions wrt user
requirements. Fix this, but annotate the fixes.
+ I have not checked traceability with requirements in
both directions. Someone should.
+ The spec should be traced to the design, and vice versa.
+ Section 1, "About This Document": fill it in or delete
it.
+ The stuff in 2.2, 3.x wrt attributes and resources
and classes is not clear to a casual outside user.
Preface the specification with an informal description
of the model.
+ 4.4-4.8: These attributes are obviously interdependent:
specify what happens in case of conflict.
+ 4.12: "amount of a specific resource" ... "any number of
resources". Seems to conflict with itself: needs to be
fixed.
+ 5.3-5.8: Before implementing this, try to come up with
a more general system that covers these cases.
+ 5.9: This seems like a bad idea to me. I understand the
intent, but it doesn't really fit very well into
standard models of project scheduling. The use case you
give can be treated by having driving the truck consume
person-hours, fuel, and dollars separately. I would
make this a very low priority requirement.
+ 8.8: Add 8.9, End Date Task Sort. This is often more
useful, and gives orthogonality.
+ 9.2: This is not specific and clear enough. Say what
actually is needed.
+ 10.1: The first clause is not a requirement. You have
a set of required platforms, now enumerate a set of
desired platforms. What platforms are phase 1, and what
are later phases?
+ 10.2: This is not a requirement. I don't even
understand it. Replace it with real performance
criteria, e.g. imperceptible time delay in response to
data entry, max bytes per task in representations, etc.
Bart
In message <1029001589.512.73.camel@zoo> you wrote:
> Could somebody glance over the specifications to see if there's anything
> important I should change? Bart, it'd be especially useful if you could
> do this.
>
> Hey, if any of you are like me, you're trying to use hevea to translate
> LaTeX to HTML, and you're running the unstable distribution of Debian.
> Well, hevea doesn't work with unstable's ocaml-base package, version
> 3.05-1, so I had to pin that back to testing with a priority that
> allowed downgrades. But you're probably not like me, so I won't bore you
> with details. :) Just e-mail me if you'd find it useful to know about
> APT pinning.
> --
> Jamey Sharp <ja...@sh...> - http://jamey.is.dreaming.org/
>
>
>
> -------------------------------------------------------
> This sf.net email is sponsored by:ThinkGeek
> Welcome to geek heaven.
> http://thinkgeek.com/sf
> _______________________________________________
> hotproject-devel mailing list
> hot...@li...
> https://lists.sourceforge.net/lists/listinfo/hotproject-devel
|