Tag Info

English grammar. For the second and third persons, will is declarative while shall is imperative, while the first person is the reverse.
The classic example:
Struggling in the water: "No-one will save me! I shall drown!"
Suicide: "No-one shall save me! I will drown!"

A general guideline is to focus on what is required without constraining how this will be done. Considerations concerning policy-decisions and specific concerns on implementation and security should be clarified in the Limitations, Questions and Issues-section and the relevant impacts referred to in the Recommendations-section.
Report Template
Executive ...

Basically, RFC 2119 says so. The real answer is just that English is imprecise unless you very specifically state what you mean in more words than people care to read, and someone took the time to state exactly what certain words should mean.

You should tell them that you can keep the IE5 and FF2 compatibility, but those browsers will have a gracefully degraded experience. Up-to-date browsers will have the full "web 2.0" experience.
This will take more time and effort to ensure compatibility, but you would probably want to have it graceful degrade in the face of no JavaScript or RIA support ...

No, you can't. What you can do, however, is use an abstract base class instead of an interface, and make equals() abstract:
abstract class Command {
// put other methods from Command interface here
public abstract boolean equals(Object other);
public abstract int hashCode();
}
Subclasses of Command must then provide their own equals and hashCode ...

Try to point them to this page:
The product Lifecycle for IE5 is already over.
http://support.microsoft.com/gp/lifesupsps/#Internet%5FExplorer
The product support from MS for these Versions of the browser has ended several years ago already. Tell them that you are unable to get any vendor support for this version anymore

Controlling an outsourced project quality
If you want a particular project quality, you will have to :
Integrate clear quality objectives in your contract
Have a clear vision of the project's quality during the development
Use an independent system that acts as a trusted third party to validate the level of quality
Clear quality objectives
To help ...

Let me start by saying that if a PM is "sneaking in scope creep" he is a very bad project manager.
Having said that...it's not your job to say no to a project manager. It's your job to ensure that he knows and understands the costs and risks of the change he is making. If the PM insists on changing the scope and adjusting nothing else in the project, get ...

This is a somewhat deep question, so I am hesitant to give a short answer. It is a good idea to read a few good books that describe different approaches, such as The Inmates Are Running the Asylum, which describes scenario-based function design. Another approach is to use high-level use-cases, as described in Writing Effective Use Cases.
Some guidelines:
...

Avoid assumptions. Spell out with as much detail as you can what you want to be done. Make sure every question can be answered with "yes", "no", or X, where X is a definitive value. Don't leave anything up to interpretation or any maybes in your instructions.
Specify every item that should be available to the end-user, its behavior and style. Make sure ...

Most AI algorithms are fuzzy -- typically learning as they go along. For items that are of critical safety importance what you want is deterministic. These algorithms are easier to prove correct, which is essential for many safety critical applications.

Every craft has its unsexy sides. Things that HAVE to be done, but nobody notices them directly. In a grocery store somebody has to organize how and when to fill the grocery shelves so they always look fresh. In a laundry you need somebody who thinks about how the processes should be optimized so that the customer gets his clothes in time.
The tricky part ...

A good rule of thumb is to always answer, "Okay. What should we drop to get this in by the deadline?" and/or "Okay. If we move the deadline to X, we can add that in."
Every change affects completion time. There's no such thing as a zero-time task. Forcing a project manager to realize that quality, deadline, or feature list will suffer every time they make a ...

When asking for more detail, one is informed that you are asking for too much detail and since this is agile, the requirement will become clearer later during the sprint (2 week sprint) and you should not worry about the detail just then, but rather to just give the story a weight in "doll hairs" and stop being difficult. Be a big picture guy. Don't worry ...

"Now, this might be an overkill for a small project. But more importantly, this could be a nightmare to maintain when there are changing features and documents are constantly updated."
Yes, this can be very hard to maintain. The way it happend on a couple of very large projects where I worked to this kind of quality level (ISO9000 etc) was to be ...

Karl Wiegers, author of Software Requirements and More About Software Requirements also has a website called Process Impact. Although most of the stuff is for sale, you should check out the Goodies section, which has documents that are released for the nominal sum of $5. One of the files that you can download is a set of Sample requirements documents, ...

Write a product requirements document.
http://en.wikipedia.org/wiki/Product_requirements_document
Read this series by Joel Spolsky
http://www.joelonsoftware.com/articles/fog0000000036.html
And here's an example
http://www.joelonsoftware.com/articles/WhatTimeIsIt.html

For successful requirement elicitation you need to
have your customer on site, discuss the requirements, let him explain them to you
the requirements have to be testable, verifiable. Having a list of them, at the end you should be able to go over the list and directly verify their correct implementation on the end-product.
they should have an appropriate ...

Yes. And this is important: Don't accept changes to stories after a sprint starts.
This will take much effort on behalf of scrum masters to tell the product owners that this is not permitted. The important thing to emphasise to them is that as developers you undertake to estimate and deliver the stories as specified, and any changes negates that effort.
In ...

Use a test balloon: Let them start with a small package first containing only a small feature set (equivalent to a very first milestone). Indicate clearly in the contract, that you expect a high quality of the code.
They might possibly get that a successful delivery will lead to a new contract and deliver high quality. If you are not satisfied you might ...

Managing a large backlog in an aggressive manner is almost always wasteful. By the time you get to the middle of a prioritized pile things have more often than not changed. I'd recommend adopting something like what Corey Ladas calls a priority filter:
http://leansoftwareengineering.com/2008/08/19/priority-filter/
Essentially, you have a few buckets of ...

The NLTK site does list a command line interface for downloading packages and collections at the bottom of this page :
http://www.nltk.org/data
The command line usage varies by which version of Python you are using, but on my Python2.6 install I noticed I was missing the 'spanish_grammar' model and this worked fine:
python -m nltk.downloader ...

Actually, the original use cases (see Jacobson's OOSE) were pretty lightweight, much as user stories are now. Over time, they evolved until a common format for "use cases" now is a complicated document with inputs, outputs, inheritance, uses relationships, pseudocode, etc. Programmers, in general, try to convert everything into programming.
In any case, ...

Your suggestion does require you to add a class to all your tables, existing ones as well as the new, wide ones; although you say "a few pages" and thus one would assume that there are only a few tables.
If you can consider the 500px tables as standard and 600px as the exceptions, then continuing to set a default would probably be more useful:
table
{
...

Functional parts are those that relate to the function of the application - what it does.
Non functional are the parts that do not directly relate to the function - things like:
performance
quality
portability
maintainability
quality
availability
extensibility
and many more...
For example, in a calculator application, the functional parts are how the ...