Wireshark-dev: Re: [Wireshark-dev] I am interested about your project : Wireshark
Hi Ποποβίδης,
I would like to introduce you to a wonderful piece called "The Cathedral and the
Bazaar". It basically shows the difference between software projects which are
directed top-down (Cathedral style) and as a cooperative effort (Bazaar style).
Cathedral style projects start off with business cases, market research, with
product managers producing all kinds of documents, requirements, etc. Then
Architects go about writing specifications, designs, test specifications. Then
the programmers start coding, integrators integrating, testers testing, etc.
This is the style of project a Software Requirements Specification fits in.
Bazaar style projects start off with someone coding up a basic idea and
publishing it. Others pick up on the code, extend and enhance it in ways they
think is valuable. This way projects grow 'organically' or die due to lack of
interest, actually responding to market requirements.
So, back to Wireshark. When you read the history on Ethereal
(http://www.wireshark.org/docs/wsug_html_chunked/ChIntroHistory.html) you'll see
that it's a typical Bazaar style project. Gerald Combs started it from
requirements he personally had. Some other people liked the idea, and extended
on it. Due to the fact the design was smart to be open to incremental
improvements it started growing by contributions from others. Look at the list
http://www.wireshark.org/about.html, and these are only the ones explicitly listed.
This process is still ongoing. Every time it amazes me what people think of,
code up and put up for inclusion.
So, so we have a need for an SRS? I don't think so, it just doesn't fit the
projects style. Do we need documentation? Yes! If you can extend on the
Developer Guide or User Guide, that would really help.
Just my 2 cents.
Thanks,
Jaap
Αντώνης Ποποβίδης wrote:
Dear Developers,
I am writing to ask for your permission about a project I am about to make.
This project is about Software Requirements Specifications (SRS).
A Software Requirements Specification (SRS) is a complete description of
the behavior of the system to be developed. It includes a set of use
that describe all the interactions the users will have with the
software. Use cases are also known as functional requirements. In
addition to use cases, the SRS also contains non-functional (or
supplementary) requirements. Non-functional requirements are
requirements which impose constraints on the design or implementation
(such as performance engineering requirements, quality standards, or
design constraints).
The software requirements document is a written statement of what the
software will do, It does not state how the software will do it.
I am interested in your open source software, Wireshark.
Can you inform me if a SRS already exists for your software?
If not, I will be glad to be welcomed and cooperate with you.
Thank you for your attention,
Popovidis Antonis
