Is there a tool to outline Website/Web app requirements?
While starting a new project, basic requirements can go like:
-
A user can click on 'X' button to reach 'Y' page and he will be displayed a form with 5 fields. After submitting the form, an email will be sent to admin with some details, etc. Or,
-
Third-party website will send a request to our API endpoint to fetch x details and will need to be authenticated by token or something.
Does anyone use any tool to quickly put together all these details to share with respective parties?
Perhaps for the first point using a prototyping tool like Invision can visually provide those basic requirements like what happens if I click on this and so on.
The second point is a bit more technical perhaps using something like Mindnode or visual-paradigm to create the backend architecture or use case scenarions.
I'm a designer so I'm not sure if MindNode is best option for architecture mapping.
Thanks Ali,
Yeah, Invision is great for sharing images with comments. Will surely checkout Mindnode.
There are a handful of tools that I'm building, of which a tool like this is one of the most exciting (to me, at least). Absent a tool which does a really nice job of documenting requirements, I've found documents- google docs in particular- to be a very useful medium. With the discipline to use the right level of detail, less is more and google docs can be very beneficial.
Thanks for sharing your thoughts.
You're right. Plain document is enough sometimes as far as the requirements are simple and can be specified without long paragraphs.
An problem that I've seen with analysis in general is that one or more of these three seem to take place when defining requirements:
This is the problem that I'm looking to solve- how to you gather requirements in a way that is both intuitive to the user/analyst (stories, stream of consciousness) but can be broken down into details needed to support traceable development and testing.
Because there isn't tooling (that I'm aware of, anyway) that supports these two different goals, you may be better off avoiding tooling and use documents to structure your projects. As complexity grows, however, this gets unwieldy.