Friday, 11 February 2011

Project Specifications in Software Engineering

For what purpose Specifications are actually meant?

A specification document describes how something is supposed to be done. This document may be very detailed, defining the minutia of the implementation; for example, a specifications document may list out all of the possible error states for a certain form, along with all of the error messages that should be displayed to the user. Sometimes, when a project doesn't meet its expected result, it may be referred to as being out of specification; the abbreviation OOS may also be used.

Five different specifications a project may have are:

1) Game company's product and game specifications are much more important for determining the quality of the product and their different games.

2) As with all performance measures, a company ensures that specifications are reasonable and measurable.

3) Company conveys financial information concerning desired products from a buyer to a seller.

4) With prescriptive specifications given by company there is little scope for misunderstanding in any dealing.

5) User of their games and buyers of their products have more opportunity to pass risk onto the company organizers, as they have the responsibility for the way the specification is met.

No comments:

Post a Comment