The trouble of finished software(nenadsabo.com)

submitted by ruffleleslrufflelesl(141) 6 months, 5 days ago

I think that there is a very important question, and that is the question of what constitutes a finished software. Well, that might seem easy. It should just work as specified.

3 comments |category: |Views: 187

tags: another

new Add a live kick counter to your blog >> liveImage

You can even customize the image by choosing your own colors, and then clicking the button below to update the preview and the html code:

  • "Kick It" text
  • "Kick It" background
  • kick count text
  • kick count background
  • border

Simply copy and paste this HTML into your blog post.


Users who kicked this story:
Comments:

posted by dpetersondpeterson(4397) 6 months, 5 days ago 0

I agree with avoiding terms like "finished". We usually call it acceptance testing, and we go through formal design process with our clients which involves us mocking up UI and describing the functionality of screens, processes, and reports. That design document is then made part of the contract. We have also considered writing BDD style language (gherkin syntax) in our design documents so that the agreed upon design can be directly tested against.

Reply

posted by vijaystvijayst(1311) 6 months, 5 days ago 0

Specifying requirements is more about communicating and understanding. Usually, business, IT, suppliers, partners do not meet eye to eye on requirements. There are always gaps in implementing the requirements because of the underlying flaws of the software that is being integrated. Completeness to me means both verifying the software against the requirements and validating if the requirements are right.

Reply

posted by NoldorinNoldorin(829) 6 months, 4 days ago 0

Indeed. Software is never finished; it just meets some (vaguely acceptable) criteria.

Reply

information Login or create an account to comment on this story