User talk:Neil crasto

isha aanchal bharti

4.0	Prototype Not Applicable. 5.0	Acceptance 5.1	Acceptance Criteria These conditions and the functionalities should define the acceptance criteria of the delivered software – i.	Application Environment 1.	Hardware – Intel Pentium core 2 Duo at least 3 GHz processor speed, RAM >= 4GB, Hard disk space 60GB for Installation of necessary software and data storage. 2.	Software – Internet Explorer, Java Development Kit v1.5, Apache Tomcat v6.0, Eclipse Indigo IDE v3.7 MySQL Server 2005 should be installed in the database server. 3.	Network - a.	All the branches should be connected in LAN or WAN. b.	The application server should be accessible to all the branches. 4.	Legal/Statutory – a.	Client has to take care of the license of necessary software installed at test server and production server. b.	Development environment needs Internet Explorer installed. Either Client has to provide the software to the team or they have to identify a development machine with Eclipse Indigo, Apache Tomcat v6.0, MySql Server 2005 client and Internet Explorer installed and give the L&T Infotech development team access to that. ii. Testing to be Carried out – 1.	Normal Testing – Development team will carry out unit testing and integration testing and provide Client with the test cases and test results. Client should review the test cases and test results before going ahead with the UAT at their end. 2.	Load Testing – It is recommended to carry out a load testing at the Client test server. iii. Test Task Responsibilities – 1.	Preparing Test Unit Cases – L&T Infotech Java Project Gladiator Team 2.	Preparing Integration Test Cases – L&T Infotech Java Project Gladiator Team 3.	Executing Unit Testing – L&T Infotech Java Project Gladiator Team 4.	Executing Integration Testing – L&T Infotech Java Project Gladiator Team 5.	Documenting Unit and Integration Test Results – L&T Infotech Java Project Gladiator Team. 6.	System Testing – L&T Infotech Java Project Gladiator Team. 7.	Load Testing – Client and L&T Infotech Java Project Gladiator Team. 8.	Documenting Acceptance Test results - Client 9.	Test Data to be Provided by – L&T Infotech Java Project Gladiator Team. iv. Volumetric data – 1.	Application should support 100-150 odd users simultaneously v.	Performance – No transaction (mainframe update) should take more than 40 seconds vi. User profiles – System should recognize Gatekeeper, Team Member and User.

3.0	Requirements Specifications 3.1	Details of requirements gathering process A brief description of the strategy and technique used for gathering requirements, which could be one of the following or other: - Interviews of Customer Representatives - Questionnaires - Enhancement requests We are making use of the comprehensive requirement gathering mechanism inclusive of interview and questionnaire. The enhancement requests of the customer were included. Direct interaction with the customer gave us an in-depth knowledge of his/her needs.

3.4.2	Software •	Ecllipse Indigo •	MySQL 2005 •	Internet Explorer 9 3.4.3	Network

3.4.4	Communication •	Email •	L&T Project Gladiator Team Conducts direct interview with client

3.5	External interface requirements

3.5.1	User Interface GUI based web application where internet browser is the only tool for users

3.5.2	Hardware Interface

3.5.3	Software Interface

3.5.4	Database Requirements •	MySQL 2005 will be used as the relational database for this project •	The growth of the database will be by 1 MB unrestricted.

3.5.5	Operational Requirements These requirements can be of the following nature: a.	Multi user operation – This site should support 100-150 users at any given time. b.	Online operations for Users to view and raise new tickets 3.5.6	Fit Criteria Non-Functional requirement: The product must have a satisfactory response time. Fit Criteria: The system is expected to respond fast enough so that it does not take more than 10-12 sec to login, connect to database and no more than 60 sec to update data. ITIL	Information Technology Infrastructure Library LAN	Local Area Network WAN	Wide Area Network SQL	Structure Query Language