aspose file tools*
The moose likes Agile and Other Processes and the fly likes Java interfaces in SRS? Big Moose Saloon
  Search | Java FAQ | Recent Topics | Flagged Topics | Hot Topics | Zero Replies
Register / Login


Win a copy of Java 8 in Action this week in the Java 8 forum!
JavaRanch » Java Forums » Engineering » Agile and Other Processes
Bookmark "Java interfaces in SRS?" Watch "Java interfaces in SRS?" New topic
Author

Java interfaces in SRS?

Pradeep Kadambar
Ranch Hand

Joined: Oct 18, 2004
Posts: 148
Hi,

We had a discussion on what should be there and what should not be. My colleague said we should include Java interfaces with all the methods in SRS. But I believe we should have only the system contract in laymans terms in SRS and leave the details to the design document.

Should we include the Java interfaces in SRS?
David O'Meara
Rancher

Joined: Mar 06, 2001
Posts: 13459

Score Reduction System?
Pradeep Kadambar
Ranch Hand

Joined: Oct 18, 2004
Posts: 148
Well I didn't exactly get what is Score Reduction System
David O'Meara
Rancher

Joined: Mar 06, 2001
Posts: 13459

Isn't that what "SRS" is?
Pradeep Kadambar
Ranch Hand

Joined: Oct 18, 2004
Posts: 148
I meant Software Requirement Specification

I'm sorry if this section or the ranch is inappropriate for this question.


:roll:
Klaus Meucht
Greenhorn

Joined: Jul 24, 2004
Posts: 13
I'm not really sure what you mean under Software Requirement Specification.

I think requirements must be independent from source code. I think it's the task of the customers (with help of the IT-Consultants) to write the requirements. But even if the IT-Spe******ts write the requirements, they have to write them in a language that customers can understand.

You can use the open source product FIT or Fitnesse (www.fitnesse.org) to write requirements and translate the requirements into java code.

If you mean with SRS a document that explains how to use or extend a framework it makes sense to use Java interfaces.
Peer Reynders
Bartender

Joined: Aug 19, 2005
Posts: 2906
An SRS (IEEE Std 830-1998 IEEE Recommended Practice for Software Requirements Specifications) is a Requirements Document. The problem is that some people seem to be under the impression that there is only "one" specification - categorizing something as the "specifications document" is pretty useless. In many waterfall based processes the Requirements Document (which can be an SRS) is used to drive the definition of the Functional Specifications which address the functional requirements and the definition of the Non-Functional Specifications to support the non-functional requirements. Additional detailed information is often captured in "Technical Specifications" to support the Functional and Non-Functional Specifications - it is usually at this level that you may find something like a Java interface.
[ November 28, 2006: Message edited by: Peer Reynders ]

"Don't succumb to the false authority of a tool or model. There is no substitute for thinking."
Andy Hunt, Pragmatic Thinking & Learning: Refactor Your Wetware p.41
Stan James
(instanceof Sidekick)
Ranch Hand

Joined: Jan 29, 2003
Posts: 8791
Pradeep, I vote with you.

But your organization is really free to define any document any way you like it. You'll need to get a good concensus from all players or you can spend forever debating what goes in some document and what doesn't. We had this experience with a consultant who just couldn't come around to our team's definitions. We had to ask the consulting company to take him away before somebody strangled him.


A good question is never answered. It is not a bolt to be tightened into place but a seed to be planted and to bear more seed toward the hope of greening the landscape of the idea. John Ciardi
 
I agree. Here's the link: http://aspose.com/file-tools
 
subject: Java interfaces in SRS?
 
Similar Threads
employee mgt system
Is System Requirement Specification Required for Migration Project??
SRS
Have You Used OFBiz or Something Else Together With the Struts Framework?
SRS for RUP