A quick comment: I think this is great that we're gathering
requirements, but before we delve down into specific functional
requirements I'd like to see this described in terms of some use cases.
What are the tasks that the user needs to accomplish. What will the
user experience be like -- what specific steps and interactions will
they have with the system? Will the user interface be command-line or
GUI? What does the user need to specify prior to running the migration
tool? What kinds of errors can occur?
For a user-based tool such as this these types of task-based,
user-oriented descriptions I think are crucial for guiding the actual
functional requirements.
Thanks!
David
Apache Wiki wrote:
Dear Wiki user,
You have subscribed to a wiki page or wiki category on "Db-derby Wiki" for
change notification.
The following page has been changed by RaminMoazeni:
http://wiki.apache.org/db-derby/MysqlDerbyMigration/RequirementDocument
------------------------------------------------------------------------------
This section describes the capability (functional) requirements of the
proposed system. A capability requirement is a function that the proposed
system must (be designed and implemented to) perform. All capability
requirements are specified in a sufficiently concrete way that they can be
implemented and tested.
Table 15: Source and Target Database Management System
+ || Capability Requirement || '''PR-14: The conversion of data in the system
from one format to another shall be reliable and accurate. ''' ||
+ || Priority || The data migration from source DBMS to the target DBMS over
network of machines or instances must not change the data and not corrupt the
format. Also, the transaction must be atomic and task of the transfer of data
from one end to the other must be achieved ||
+ || Description || Must Have ||
