• Post Reply Bookmark Topic Watch Topic
  • New Topic
programming forums Java Mobile Certification Databases Caching Books Engineering Micro Controllers OS Languages Paradigms IDEs Build Tools Frameworks Application Servers Open Source This Site Careers Other all forums
this forum made possible by our volunteer staff, including ...
Marshals:
  • Campbell Ritchie
  • Devaka Cooray
  • Liutauras Vilda
  • Jeanne Boyarsky
  • Bear Bibeault
Sheriffs:
  • Paul Clapham
  • Knute Snortum
  • Rob Spoor
Saloon Keepers:
  • Tim Moores
  • Ron McLeod
  • Piet Souris
  • Stephan van Hulst
  • Carey Brown
Bartenders:
  • Tim Holloway
  • Frits Walraven
  • Ganesh Patekar

Implied Requirements

 
Greenhorn
Posts: 11
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Hello all,

I'm having trouble deciding whether it necessary to implement obvious functionality not made explicit in the spec.

For example, my project is the B&S Contractor Manager program. It is explicit in its requirement for users to book a contractor for a particular customer. It is not so, with the requirement for users to be able to create new contractors.

OF course users need to be able to create new contractors right? But where does the implementation of implied requirments end? If this judgement call another aspect of the scjd?

Cheers,

Eamonn.
 
Enthuware Software Support
Posts: 4331
35
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
It is implied that there must be a way to add new contractors. However, it is not really implied that this application has to implement it. This is because the requirement document says that there are other custom written applications that manipulate the same file.

In general, it may not do any good to implement something which is not explicitly asked. You should implement X only if you believe that you cannot implement Y, which is asked, without implementing X.
 
Eamonn O'Connell
Greenhorn
Posts: 11
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Thanks for the advice. I was reluctant to att the create functionality would add a whole new aspect to mt design: user input validation.

Create is defined in the provide db interface though...
 
Greenhorn
Posts: 22
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Hi,

I believe you implement the functionality (for create) in your Data, since you are implementing the interface, but it is not exposed for use by the client. That's the route I went with.

-- Vince
SJCP(1.4), SCWCD(1.4), SJCD (almost there!)
 
Ranch Hand
Posts: 61
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
correct - I agree! implement the interface, not GUI (I doing it also)

Regards,
maciej
 
Consider Paul's rocket mass heater.
  • Post Reply Bookmark Topic Watch Topic
  • New Topic
Boost this thread!