IEEE SRS documents: lightweight version when working with outside contractors?
Typically we follow an Agile development process that tends not to put an emphasis on writing requirements and technical documents that nobody will read. We tend to focus our limited manpower to development and testing activities with collaborative design and whiteboarding as a key focus.
Formalizing a requirements spec written in narrative English
I have a fairly technical functionality requirements spec, expressed in English prose, produced by my project manager. It is structured as a collection of UI tabs, where the requirements for each tab are expressed as a lit of UI fields and a list of business rules for the tab.
System requirement specification vs functional one – separate docs? [duplicate]
The software requirements specification is sometimes called a
functional specification, a product specification…
How are “Json.org”-like specs graphs called and how can I generate them?
In http://www.json.org Douglas Crockford shows the specs of the JSON format in two interesting ways:
Describing requirements in SRS – use cases?
I do not have the access to the IEEE standard and information on the net are contradictory. Can I capture user requirements in SRS using use cases? Or I should keep use cases separate as they are more like scenarios than separate requirements?
Need interpretation of section in C# specification
I am reading the C# specification. I could use clarification on a segment:
How to avoid duplication between my issue tracker and the project specification documents?
I used to work for a professional consulting firm, and we worked under many different contract terms. When we could get a time & materials project, we ran it with SCRUM and tracked the backlog in our issue tracker system.
Requirement specifications with annotations? [closed]
Closed 9 years ago.
Software Requirement Specification documentation by professionals
I just wanted to know what is the significance of SRS(Software Requirement Specification) in programming? and what are the techniques used in preparation of an SRS .. also who writes the SRS.. is it the programmers?
Can you claim that your product is fit for purpose when it uses OSS software which does not guarantee it?
I am working on a product for a client that must be valid and fit for purpose.