Hello Forum,
I am currently specifying the User requirements for an upgrade to or replacement of an existing Arrivals and Departures scheduling system for a major public transport service provider (Coach Services). This system need to interface with an Automatic Number Plate Recognition (ANPR)system. The ANPR system will capture the actual arrivals at and departures from the station.This ANPR system has to be procured separately and integrated with the Scheduling system. My question is, is it advisable to combine the requirements of the two systems into a single requirements specification document ?
Regards.
Perhaps you should be concentrating on the requirements and definition of the interface between the systems. That seems to be what your issue is?
If you are also gathering requirements for each system then whether they are in one document or two is not that important. If you're going to tender for each you might want to keep them separate I suppose. I trust you are gathering your business requirements without considering the limitations of your proposed solution.
Kimbo
Create a high level data flow diagram showing how the two systems interrelate. If there is just a few interrelationships (data flows) between the two systems, then you have a nice clean partitioning and you can go with two specs. If, however, there is alot of interrelationships between the two systems, then you need to combine the requirements and then repartition and then determine which way to go.
brought to you by enabling practitioners & organizations to achieve their goals using:
enabling practitioners & organizations to achieve their goals using: