Hi Jean -
Here is some feedback on the doc:
Section 2. Assumptions and Dependencies
What about including dependencies on other technologies, like IPS?
3.3 Interface Tables
Under IPSTransfer, set_type is listed twice.
3.4.1.3.8 9 - 11
Is the _args attribute cpio_args?
3.4.2 IPS Functionality
There is no explanation of the functionality like you have for the
Media functionality. That would make things more explicit.
3.4.2.3.2
typo - performthe/perform the
3.4.3. SVR4 Functionality
There is no explanation of the functionality like you have for the
Media functionality. That would make things more explicit.
4 Use Case/Diagrams
The first use case implies that the transfer module is engaged, but it's
not clearly called out.
Second use case:
typo: the esystem / the system
General question:
There is duplicate methods in all of the Classes. Is there a way to
combine that commonality into
a class that the other classes could then be sub-classes of?
thanks,
--
Ginnie
