J
J
JeeneFG2017-09-01 11:15:51
Analytics
JeeneFG, 2017-09-01 11:15:51

One or more SRS for one product?

Good afternoon, colleagues.
At the moment, I am working on the creation of a requirements specification for an information system, consisting of several modules, described below.
1. A web application is used to create objects and send them to mobile devices.
2. The mobile application is used to receive objects and perform various manipulations on them.
3. The core of the system serves as a connecting link and implements process automation and optimization.
Each module is handled by different development teams.
What is the best way to document the requirements for a given system? Describe everything in one specification or break it into modules so that the document is more easily perceived by different development teams?
Who has already had experience with such systems, please share your experience. I will be glad to any advice.

Answer the question

In order to leave comments, you need to log in

1 answer(s)
D
Dimonchik, 2017-09-03
@dimonchik2013

by modules, of course, there is also a REST API for a bunch, the rest of the modules do not need to know about each other

Didn't find what you were looking for?

Ask your question

Ask a Question

731 491 924 answers to any question