Skip to main content
36 votes

Where can I find requirements specification for Open Source software?

Requirements don't need to be captured in a formal software requirements specification or any other kind of document. They can be captured in tests (primarily acceptance tests and system tests, but ...
Thomas Owens's user avatar
  • 83.3k
20 votes
Accepted

Where can I find requirements specification for Open Source software?

Don't let the software prevent you from seeing the projects. I challenge the idea that you need requirements for a software. And suggest that requirements are for software projects. And that there are ...
Theraot's user avatar
  • 9,151
19 votes
Accepted

How to document non-functional requirements in User Stories?

Non-functional requirements come in many forms, but they have one thing in common: The don't describe functional behavior of the system but rather put constraints on the design choices that you can ...
Bart van Ingen Schenau's user avatar
18 votes

Where can I find requirements specification for Open Source software?

Some good answers here already, especially for your question where requirements are found in Open Source projects. Let me say something about the reasons why is it hard to find a formal spec document ...
Doc Brown's user avatar
  • 209k
17 votes
Accepted

Why bother gathering requirements when we know they will change?

Because not all requirements do change, and not all requirements change in the same ways. You're not going to spend awhile working on software to manage a warehouse, only to suddenly decide to instead ...
whatsisname's user avatar
  • 27.6k
11 votes

Why bother gathering requirements when we know they will change?

Why do we spend so much time gathering detailed requirements at the beginning if we know that they will be invalidated and change in the not so distant future? It's time to stop gathering ...
candied_orange's user avatar
10 votes

Why are software requirements allowed to change if it means more work for software engineers?

Because software engineering isn’t done for some abstract pursuit of software engineering, it’s about building a useful result. If halfway through the construction of device A you find out that it won’...
Alexander's user avatar
  • 4,954
9 votes

Why bother gathering requirements when we know they will change?

One facet of this; If you have no requirements why are you writing any code at all? Code doesn't exist to please itself. Whatever reason you're writing for has a requirement hidden in it, and the ...
Daenyth's user avatar
  • 8,147
7 votes

Why bother gathering requirements when we know they will change?

What you're probably thinking of is Big Design Up Front, and yeah, it's not necessarily the best way to manage a software project. But you still need a clear picture of what you want to accomplish ...
Robert Harvey's user avatar
7 votes

How to document non-functional requirements in User Stories?

"Non-functional requirements" is a bit vague and open to interpretation. Going on your specific example, I would say that those requirements should be used as acceptance criteria for other stories. ...
Bryan Oakley's user avatar
  • 25.3k
7 votes

How minimum-documentation agile development is compatible with requirement that business processes should be documented?

This is a rather unusual interpretation of “Working Software over comprehensive documentation” value. This value of Agile manifesto was created as a reaction to the projects where documentation ...
Arseni Mourzenko's user avatar
7 votes
Accepted

How do I explain to my team "there is no problem if the requirements need to change after a sprint?"

There may be many stakeholders in the real world, but as far as the developers are concerned, there is only one: The product manager who was selected by the companies involved to have the ...
gnasher729's user avatar
  • 45.9k
7 votes
Accepted

Are constraints design software requirements?

If you are producing a software requirements specification (SRS), I would expect that both GUI requirements and design constraints would be captured in that document. In ISO/IEC/IEEE 29148-2011, the ...
Thomas Owens's user avatar
  • 83.3k
7 votes

What is the importance of the vision document and how it helps development?

Considering you are working alone the vision document would be less useful for you than most as it's mostly a communication tool. More importantly however, the vision document is a reference point, ...
Erdrik Ironrose's user avatar
7 votes

Use Cases in Clean Architecture, in Requirements Specifications from Software Engineering and Use Case Diagrams in UML

In short In the general sense, use-cases are meant to focus on user objectives and answer the question: "why would a user use this system? And for what purpose?". They therefore focus on ...
Christophe's user avatar
  • 78.4k
6 votes

What is the importance of the vision document and how it helps development?

The vision document describes how the stakeholders see what the future for the product should be. The goal of the vision document is to keep everyone who is involved in the development of the product ...
Bart van Ingen Schenau's user avatar
6 votes

How do I know how much to bill and how long a software development project will take, before analysis?

One thing that makes software projects special is that once you have fully analyzed everything, you are basically done with the job. Of course you can't afford to do this as long as it is unclear if ...
Frank Puffer's user avatar
  • 6,429
6 votes
Accepted

Requirements engineering done in Excel and Word?

On an OOP conference in Munich, ~20 years ago, I asked one of the speakers (Chris Rupp, author of several books about requirements engineering) which tools she would recommend for collecting ...
Doc Brown's user avatar
  • 209k
5 votes

How to deal with redundant requirements when using Scrum

It sounds like this should be covered by grooming. Constant change means that stories often need to be corrected, expanded, split, condensed, joined, re-estimated etc. It is a good idea to groom all ...
Robbie Dee's user avatar
  • 9,815
5 votes
Accepted

Formulating requirements using ISO/IEC/IEEE 29148-2011/2018

One of the characteristics of a good requirement is that it is atomic. That is, the requirement defines one and only one behavior. Although not the only way, requirements with conjunctions (such as "...
Thomas Owens's user avatar
  • 83.3k
4 votes

is there a standard for documenting requirements interview

The standard related to the development and management of software requirements is ISO/IEC/IEEE 29148:2011 - Systems and software engineering - Life cycle processes - Requirements engineering, which ...
Thomas Owens's user avatar
  • 83.3k
4 votes

How to centralize functional requirements and domain knowledge for quick access?

Doors... (shudders uncontrollably) A well-organized wiki can serve this purpose very well. Articles about "features" and "components" can be organized with any useful structure, and cross-linked for ...
zerobandwidth's user avatar
4 votes

How to document non-functional requirements in User Stories?

You can incorporate them into your DOD "Definition Of Done". Non-functionals are problematic in agile though, if they change you have no way of tracking which stories have been done against what ...
Ewan's user avatar
  • 77k
4 votes

How to deal with changes in the requirements because design decisions?

The basic business requirement is that documents should be signed electronically. The fact you have decided to use a third party solution does not change the business requirement. At the end of the ...
Greg Burghardt's user avatar
4 votes

Why aren't databases secondary actors in use case diagrams?

It all depends on the boundaries of the system under design. Personally, I've never included printing systems as actors when modeling use cases of a system. When modeling a use case about printing, I ...
Thomas Owens's user avatar
  • 83.3k
4 votes

Should operating system configuration parameters, like disabled automatic updates or sleep timer, be part of the software specifications?

To me, testing is about validating the required functionality, testing is not about how a requirement is implemented. Since disabling updates is required functionality, it should be tested. That's ...
Jeff Siver's user avatar
  • 1,721
4 votes

Why are software requirements allowed to change if it means more work for software engineers?

why are requirements changes allowed to happen They aren't "allowed" to happen. They happen. There is simply a non-zero amount of time between the point in time where the requirements are ...
Jörg W Mittag's user avatar
4 votes

Requirements engineering done in Excel and Word?

Whenever I hear students complaining about the approach taken by a professor, I advise them to watch Karate Kid 1. Half of the film is about stupid tasks that a karate professor is making his student ...
Christophe's user avatar
  • 78.4k
4 votes

Functional or non functional requirements?

This is functional. The user says they needs a csv and XML versions and will complain if they are not available, so it's a functional requirement. This is also functional, and part of the above. You ...
Rad80's user avatar
  • 376
4 votes

Functional or non functional requirements?

functional requirements define what a system is supposed to do and non-functional requirements define how a system is supposed to be. Wikipedia - Non functional requirements “The system shall produce ...
candied_orange's user avatar

Only top scored, non community-wiki answers of a minimum length are eligible