10GI25

System Requirement Study

3.0 SYSTEM REQUIREMENT STUDY

3.1 USER CHARACTERISTICS In our application there are 3 types of users which are as below: Customers / Passengers. Moderators. Admin.

3.2 HARDWARE AND SOFTWARE REQUIREMENTS

Minimum software and hardware requirements to run our system are as follows. 3.2.1. Server side: Hardware Requirements 3.2.2 Client side: Hardware Requirements Processor : Pentium IV or higher RAM : 512 MB or above Processor : Pentium IV or higher RAM : 2 GB or above HDD:-160 GB or above

Software Requirements OS :- Windows Or Any OS IDE :- NetBeans DB :- My SQL Server 2008 Language :- Java

Software Requirement Operating System : Any ( Windows, Linux etc.) Web Browser : Any ( IE, Firefox, Google chrome, Opera etc.)

SOCET (CE)

10GI25

System Requirement Study

3.3 Constraints 3.3.1: Regulatory Policies

As per the Company's policy any developer has to maintain the Coding Standards. Also each and every user should maintain the subversion and commit the modification with appropriate comment so to have track of work and also of the code modification. From the clients perspective: DEVELOPER SHOULD USE WELL KNOWN TECHNOLOGY. DEVELOPER SHOULD USE WELL KNOWN CODING STANDARDS.

3.3.2: Hardware Limitations

The hardware limitation is very low. The configuration of the client's PC should be high memory wise.

3.3.3: Interfaces to other Applications

There is no application using this application as an interface so-far.

3.3.4: Parallel Operations

There are no parallel operations as such executing during the operation of the current application.

3.3.5: Higher Order Language Requirements

No high order language is required as such. Java language is the only language used in the application. If there is some need to use then we can use that easily.

SOCET (CE)

10GI25

System Requirement Study

3.3.6 Reliability Requirements

Reliability requirements of the system are one of the prime ones in the list. The system needs to be highly reliable in terms of performance but at this stage where the complete system is far from completion we cannot gauge its reliability. All we could do is to make the individual module we have developed to be as reliable as possible.

3.3.7: Criticality of the Application:

Criticality means any occurrence of miss operating of the system or any accidental event in software which can damage the resources of software as well as hardware. As per my knowledge there is no criticality in our application.

3.3.8: Safety and Security Considerations

The main concern for the safety is that there should not be any errors during the time when customers pay for the tickets online. Moreover the management of the system to be moved to middlemen employees, Moderators, having admin rights rather than completely depending upon the admin in order to manage the system. Both these concerns have been attended to by using various measures.

SOCET (CE)