Request for Proposal for e Ticketing Project - Archaeological Survey ...
Request for Proposal for e Ticketing Project - Archaeological Survey ...
Request for Proposal for e Ticketing Project - Archaeological Survey ...
You also want an ePaper? Increase the reach of your titles
YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.
RFP <strong>for</strong> e-<strong>Ticketing</strong> <strong>Project</strong> Volume-I<br />
12. Documentation Requirements<br />
End-User Documents<br />
Documentation will be supplied and maintained by the Implementation Agency during the<br />
project. The ownership of all documents, supplied by the Implementation Agency, will be<br />
with ASI. The electronic copies shall be submitted along with all the paper documents and<br />
manuals, required <strong>for</strong> operating and configuring the system. The documents provided must<br />
include at least:<br />
User Manual (both online and paper copies) providing detailed instructions on how<br />
to use the software. In addition, it describes how to access, submit inputs to, and<br />
interpret outputs from the application<br />
System installation guide including the configuration of the supplied infrastructure.<br />
User will have the rights to duplicate the hardcopy and soft copy <strong>for</strong> the<br />
documents created by the Implementation Agency without any financial and legal<br />
implications<br />
e-<strong>Ticketing</strong> Application Training Manual<br />
Technical Documents:<br />
The Implementation Agency must ensure that the e-<strong>Ticketing</strong> system components being<br />
developed are thoroughly documented with comprehensive manuals and adhere to<br />
standard methodologies in software development as per ISO and/or CMM models. The<br />
documents including but not limited to are:<br />
Product installation and configuration steps;<br />
Application access procedures;<br />
User screen layout and content;<br />
Transaction entry procedures;<br />
Batch job setup, processing, and recovery/restart procedures;<br />
Error codes with full descriptions and recovery steps;<br />
Standard report layout and content;<br />
Internal processing controls;<br />
Application security;<br />
Operating specifications and system flowcharts;<br />
Database entity relationships, table <strong>for</strong>mats, and data element<br />
descriptions; and Program module descriptions<br />
Quality Assurance Plan Documenting the planned and systematic pattern<br />
of all actions necessary to assure confidence that the software developed<br />
will con<strong>for</strong>m to the ASI functional and technical requirements.<br />
Archeological <strong>Survey</strong> of India, Ministry of Culture Page 67 of 107