The document outlines the system requirements for Project ID 32. It describes the user characteristics including administrators who have full access rights, applicants who can register and manage their profiles, faculty who can review trainee logs, and supervisors who approve logs. It also lists the hardware and software requirements needed like the .NET framework, SQL Server, and Windows operating systems. Finally, it discusses some constraints including a limited 4 month timeline, beginner developers, need for reliability and uptime, and security considerations like password protection and restricted user access rights.

1. Project Id: 32 System Requirement Study
CCET (IT) 28
Chapter 3
SYSTEM REQUIREMENT STUDY
________________________________________________

2. Project Id: 32 System Requirement Study
CCET (IT) 29
3.1 USER CHARACTERISTICS
Administrator:
The administrator has all the rights to access the system. He is the one who has all rights
to view the applicant details, modify those details, The administrator also keeps a track of
the file status of the applicants.
User :
Applicant is the one who wish to visit HMIS website. The applicant can fill in his own
details and register himself for membership to use portal services. The applicant has rights
to view and modify his own details, generate its candidature of containing his own details
in academic web part. The applicant also rights to create groups, modify groups, invite
member, modify member, join group, slam book requests, etc. In sort, the applicant can
access the application like a moderator of his/her group.
Faculty :
He can view log sheet submitted by trainee day to day filled student which is applying for
his/her status and day to day log sheet submission- this can be done, only when the
supervisor approve their log sheet, faculty gives review to trainee after looking his/her
remarks by the supervisor.
Supervisor :
The Supervisor is approve the log sheet is done by administrator and give them remarks on
it and supervisor also update trainee log sheet.

3. Project Id: 32 System Requirement Study
CCET (IT) 30
3.2 HARDWARE AND SOFTWARE REQUIREMENTS
The following are minimum hardware and requirements that should be present to run the
project successfully.
Table 3.1 Tools and Technology
Development technologies .NET framework 3.5, SQL server 2005, AJAX,
JavaScript, XML
Development tools Microsoft visual studio 2008, SQL server 2005
management studio
Application server IIS 7.5
Database SQL
Operating system Windows XP Profession Edition, Windows Vista
Enterprise Edition
Web browser Internet Explorer 6.0 and above
Hardware P-IV 2.4, 1 GB RAM, 80 GB HDD
 Hardware Requirements
Table 3.2 Hardware Requirement
Client Configuration
Pentium IV, 750 MHz, 20GB HDD
Operating System: Windows XP/2000
RAM: 256 MB minimum
400MB Minimum Free Space on Drive
Microsoft Office
Server Configuration
2 Servers, each with following configuration
2 CPU
Operating System: Win XP
RAM: 512MB Minimum

4. Project Id: 32 System Requirement Study
CCET (IT) 31
40GB Minimum Free Space on Drive
750MHz
One Server with Sql Application Server
Other Server with Sql Database Server
 Software Requirements
Table 3.3 Software Requirement
3.3 CONSTRAINTS
3.3.1 Regulatory Policies
 The length of the project is 4 months which a limited amount of time.
 The project developers are beginners and will take time to understand about the
technology.
 The users of the system are any registered applicants to apply for membership
in HMIS, authorized administrator and non-registered users can also used
interface pages.
3.3.2 Reliability Requirements
System Software
MS Sql Application Server enterprise edition
MS Sql Database Server enterprise edition
Microsoft Office
Reporting server
IIS 6.0 or higher

5. Project Id: 32 System Requirement Study
CCET (IT) 32
 The system should be reliable enough so that the data found in the database
system is consistent at any point.
 The system should be able to handle loads of requests from different users
around the world at the same time.
3.3.3 Criticality Of The Application
 The system is a web-based application and so fails to work if there is no
Internet connection. The system might not work if the Internet connection
slows down.
 The system stops working in case if the database server or the application
server stops working.
 The system might give erroneous output if it fails to connect to the database
server.
3.3.4 Safety and Security Considerations
 The Intranet password security
 Each applicant is given a login account through which he can view his own
information and also modify and save it. He has the rights to access only his
own information.
 The administrator has rights through which he can access and manage whole
system.