Project Requirements - Archaeological Survey of India

Request for Proposal for establishing e-Governance Systems
proposed solution meets all the requirements of the project. For proposed
solutions which are implemented using off-the-shelf solutions available from
reputed vendors, a prototype may not be required.
5.7 Phase 6: Entry of Historical Data
5.7.1 SI shall be responsible for digitization and migration of data for financial planning
and budgeting module from existing data sources to the ASI’s application being
developed as a part of this project, to provide for availability of all data for the
current financial year.
5.8 Phase 7: Testing and Acceptance
During this phase, SI shall conduct various types of testing including:
5.8.1 Application Functional Testingof the e‐governance systems shall be carried out to
validate whether the application meets the specified functional requirements
covering the work flows, navigations, and business and data Validation rules for
the defined user categories with access rights. The functional testing should be
done following black box approach and using end‐to‐end user scenarios.
5.8.2 Application Usability Testing shall include systematic observation under controlled
conditions to determine how well users can use the application. The proposed
systems are likely to be used by users of different levels of computer knowledge.
Usability testing will ensure that the all types of users are comfortable to use the
system. This shall be done by using defined international standards which
recommend extensive user interaction and analysis of userbehavior for a defined
task.
5.8.1 Performance Testing of the system shall be done to ensure that system is capable
of handling defined user as well as transactional load. The performance testing of
the e‐governance system will include measuring the response time of the system
for defined scenarios. Also the manner/ trend in which performance changes with
load will determine the scalability of the e‐governance systems.
5.8.2 Application Security Testing conducted to unearth various application security
vulnerabilities, weaknesses and concerns related to Data /Input Validation,
Authentication, Authorization /Access Control, Session Management, Error
Handling, Use of Cryptography, etc. Typical issues which may be discovered in an
application security testing include Cross‐site scripting, Broken ACLs/Weak
passwords, Weak session management, Buffer overflows, Forceful browsing,
Form/hidden field manipulation, Command injection, SQL injection, Cookie
poisoning, Insecure use of cryptography, Mis‐configurations, Well‐known platform
vulnerabilities, Errors triggering sensitive information leak etc.
5.8.3 Penetration Testing shall be done remotely from public domain (Internet) and also
RFP Volume 1:Project Requirements P a g e | 17