Netsnapper Client Rt01 Windows

Requirements Traceability
Project Name
Document Title
Product Release No.
Document No.
Netsnapper
Netsnapper_Client_rt01_Windows
9
2
Document Revision History

Rev No.
Date of Issue
Author
Approved by
0.1
12/18/2014 Ashok Kumar D
Suriya Mohan
0.2
12/23/2014 Pradeep VR
Suriya Mohan
0.3
0.4
1
1.1
1.2
1.3
1.4
2
2.1
3
12/29/2014
12/30/2014
12/31/2014
2/12/2015
2/12/2015
2/12/2015
2/12/2015
2/12/2015
2/26/2015
2/27/2015
Suriya Mohan
Suriya Mohan
Suriya Mohan
Suriya Mohan
Suriya Mohan
Suriya Mohan
Suriya Mohan
Suriya Mohan
Suriya Mohan
Suriya Mohan
Pradeep VR
Karthikeyan
Karthikeyan
Ashok Kumar D
Ashok Kumar D
Ashok Kumar D
Ashok Kumar D
Karthikeyan
Karthikeyan
Karthikeyan
Scope
Initial Version
Added SRS
Updated Design Mapping and
Code Mapping
3.1
3/30/2015 Karthikeyan
Suriya Mohan
Updated with SRS Modifications

Updated with ST cases
Baselined
Updated with update service
requirements
Updated with update service
design sections
Updated
code mappings for new
requirements
Updated UT mappings for new
requirements
Baselined
Updated with ST cases
Baselined
Updated with Granted service
cases
Suriya Mohan
Baselined
4.1
Suriya Mohan
4.2
Suriya Mohan
Updated SRS Modifications

Code Mapping
Suriya Mohan
Baselined
5.1
Suriya Mohan
5.2
Suriya Mohan
5.3
Suriya Mohan
Updated
Modifications
Updated SRS
Design
Mapping for
ForgotPassword and SHA1 to
SHA2
feature
Updated
Code Mapping for
SHA2 feature
5.4
Suriya Mohan
Updated Unit Test Mapping for

SHA2 feature
5.5
Suriya Mohan
Updated SITcases ID's
Suriya Mohan
Baselined
6.1
Suriya Mohan
Updated SRS Modifications
6.2
Suriya Mohan

Code Mapping forExe installer,
UI font change and
authentication message handling
6.3
Suriya Mohan
Updated UI Mapping forExe

installer, UI font change and
authentication message handling
6.4
7/24/2015 Mullaisellvan
Suriya Mohan
Updated SITcases ID's
7/30/2015 Mullaisellvan
Suriya Mohan
Baselined
Updated SRS, Design Mapping,
Code Mapping and SIT Cases
for Windows 10 software
requirement
7.1
Suriya Mohan
Suriya Mohan
8.1
Suriya Mohan
8.2
Suriya Mohan
8.3
Suriya Mohan
BaselinedSRS Modifications for

Updated
Serverlist, Datalimit and custom
option
Updated Design Mapping for
ServerList, Data Limit and
custom
Updatedoption
Code requirements
Mapping for
custom option requirements
8.4
Pradeep VR,
11/5/2015 Haemachandar
Suriya Mohan
Updated Unit Test Mapping for

8.4
11/5/2015 Mullai Parvathi G
Suriya Mohan
Updated SIT cases ID for

11/6/2015 Mullai Parvathi G
Suriya Mohan
Baselined
9.1
Pradeep VR,
12/16/2015 Arulmanickam
Suriya Mohan
Updated SRS Modifications for

Split Tunneling feature
9.2
Pradeep VR,
1/18/2015 Arulmanickam
Suriya Mohan
Updated with Design Mapping for

Split Tunneling feature
Copyright 2006-2014The Aricent Group. All Rights Reserved. No part of this document may be reproduced, stored in a
retrieval system, distributed or transmitted, in any form, or by any means, electronic or otherwise, including photocopying,
reprinting, or recording, for any purpose, without the express prior written permission of The Aricent Group.
Printed in ________
TRADEMARKS: Aricent and the Aricent Logo are trademarks and registered trademarks of The Aricent Group or its
subsidiaries or affiliates in the U.S. and certain other countries. The use of these trademarks without Aricents prior written
consent is strictly prohibited. Other third party trademarks referenced are the property of their respective owners. Please note
that the above list is not all-inclusive, and the absence of any mark from this list does not mean that it is not an Aricent
trademark.
DISCLAIMER The information in this book is provided AS - IS, without warranty of any kind, express or implied, including but
not limited to a warranty of merchantability, fitness for any particular purpose, title or non-infringement of third party rights, and
Aricent specifically disclaims all other warranties, conditions or representations. This document is provided for informational
purposes only, and should not be construed as a representation or a commitment on the part of Aricent. Information in this
document is subject to change without notice.
REQUESTSFor information requests or for obtaining permission for the use of this work, please submit a written request to:
Corporate Marketing and Legal, The Aricent Group, 303 Twin Dolphin Drive, Suite 600 Redwood City, CA 94065
Printed in ________
TRADEMARKS: Aricent and the Aricent Logo are trademarks and registered trademarks of The Aricent Group or its
subsidiaries or affiliates in the U.S. and certain other countries. The use of these trademarks without Aricents prior written
consent is strictly prohibited. Other third party trademarks referenced are the property of their respective owners. Please note
that the above list is not all-inclusive, and the absence of any mark from this list does not mean that it is not an Aricent
trademark.
DISCLAIMER The information in this book is provided AS - IS, without warranty of any kind, express or implied, including but
not limited to a warranty of merchantability, fitness for any particular purpose, title or non-infringement of third party rights, and
Aricent specifically disclaims all other warranties, conditions or representations. This document is provided for informational
purposes only, and should not be construed as a representation or a commitment on the part of Aricent. Information in this
document is subject to change without notice.
REQUESTSFor information requests or for obtaining permission for the use of this work, please submit a written request to:
Corporate Marketing and Legal, The Aricent Group, 303 Twin Dolphin Drive, Suite 600 Redwood City, CA 94065
ws
Scope
sion
RS
Design Mapping and
pping
with SRS Modifications

with ST cases
with update service
nts update service
with
ctionsmappings for new
code
ntsmappings for new
UT
nts
with ST cases
with Granted service
SRS Modifications
Design Mapping and
pping
SRS
Modifications
Design
Mapping for
ssword and SHA1 to
ture Mapping for
Code
ssword and SHA1 to
ture
Unit Test Mapping for

ssword and SHA1 to
ture
SITcases ID's
SRS Modifications
Design Mapping and

pping forExe installer,
ange and
ation message handling
UI Mapping forExe
UI font change and
ation message handling
SITcases ID's
SRS, Design Mapping,

pping and SIT Cases
ws 10 software
nt
SRS Modifications for

Datalimit and custom
Design Mapping for
, Data Limit and
ption requirements
Code
Mapping for
, Data Limit and
ption requirements
Unit Test Mapping for

, Data Limit and
ption requirements
SIT cases ID for

, Data Limit and
ption requirements
SRS Modifications for

eling feature
with Design Mapping for

eling feature
roduced, stored in a
luding photocopying,
Group.
cent Group or its

Aricents prior written
tive owners. Please note
t is not an Aricent
s or implied, including but

t of third party rights, and
vided for informational
ent. Information in this
mit a written request to:

, CA 94065
NOTE: This Requirement Tracebility sheet allows you to identify the bi-directional trace of the managed requirements. By chos
can see against any specific entity the requirements that are satisfied. E.g.all requirements satiesfied by design document section x
Project Name :
Netsnapper
PRD / SOW / URD / RFC / ITU Standards / User

Requirements (reference to the exact section / subsection in the relevant international standard if
applicable)
(\\chent032\Netsnapper\WORK\docs\SRS
Document\NS
Client\Netsnapper_Client_Windows_PRD01.xls/11.0)
Requirement ID (reference to
requirement ID as in SRS)
(\\chent032\Netsnapper\WORK\doc
s\SRS Document\NS
Client\Netsnapper_Client_Window
s_PRD01.xls/11.0)
NAPI
NSC.NAPI
Netsnapper Client should provide an XML based

API interface for Netsnapper Application to
communicate with Netsnapper Core module.
NSC.NAPI.01
AUTHENTICATION
Username and Password
NSC.AUT
NSC.AUT.UP
Should have a provision for the user to enter

username and password
NSC.AUT.UP.01
Should have a provision for the user to allow the

system to remember the password
NSC.AUT.UP.02
Should show the password if the remember

password provision has been chosen.
NSC.AUT.UP.03
Should leave the password textbox empty if the

remember password provision has been not been
chosen
NSC.AUT.UP.04
Forgot password option should be available to

revoke the password to registered email id
NSC.AUT.UP.05
Server IP and Port
NSC.AUT.IP
Should have a provision for the user to enter Server

IP
NSC.AUT.IP.01
Should have a provision for the user to enter Port

number
NSC.AUT.IP.02
NSC.AUT.IP.03
Should have a provision to enter the Server IP or
customize it
Should enable the Host IP and port number text
boxes if the customize option is chosen in Server IP
Should disable the Host IP and port number text
box if the Server IP is selected from the existing
entries.
Saving and Cancelling
Should have a provision for the user to save the
credentials and send them to the Netsnapper Core
Should have a provision for the user to cancel the
changes made in credentials
Connection/Disconnection
NSC.AUT.IP.04
NSC.AUT.IP.05
NSC.AUT.SC
NSC.AUT.SC.01
NSC.AUT.SC.02
NSC.AUT.CONN
Should have a provision for the user to connect to

the server
NSC.AUT.CONN.01
When the connection provision is clicked by the

user, the connection should be established and the
credentials should be sent to MAM for
authentication
NSC.AUT.CONN.02
Should display the connection information to the

user whether the connection has been established
or not.
NSC.AUT.CONN.03
Should apply the following forced or permitted

Client Profile settings from MAM to the client while
logging in such as:
1. Disable the interface
2. Backup interface
3. Hidden interface
4. Priority of interfaces
5. Selected profiles in each interface such as
WLAN, DUN and VPN and their priority.
6. Use Wifi Manager
7. Profile manager
8. Selected Routing rules and their priority
9. Selected granted services and their priority
10. Use the granted services
11. Access to choose the encryption level
12. Compress option
13. Connect on start option
14. Keep alive mode option
15. Connect on demand option
16. Hidden service operation
17. Simple UI mode
18. Remember password option
19. Start UI agent on OS start option
20. Displaying the connection page
21. Displaying the Dashboard page
22. Allowing user to choose the language
23. Auto-Update
NSC.AUT.CONN.04
Should provide Netsnapper virtual IP address
NSC.AUT.CONN.05
Should provide multitunneling: Primary/Backup
NSC.AUT.CONN.06
Should provide automatic connection repair
NSC.AUT.CONN.07
Should provide automatic intelligent network

connection management
NSC.AUT.CONN.08
Should provide peer-to-peer connection
NSC.AUT.CONN.09
Should establish a primary and a backup

connection if the Use as Backup provision is
enabled
Should establish only a primary connection if the
Use as Backup provision is disabled.
NSC.AUT.CONN.10
NSC.AUT.CONN.11
NSC.AUT.CONN.12
When two interface is selected as backup interface,
connection should be established using the
interface with high priority when primary tunnel
disconnects
When two clients are connected with same
credential, appropriate error message should be
shown.
SECURITY
Should authenticate the user using Netsnapper

certificate
Should authenticate the user using Password

authentication
Should authenticate the user using IMEI
authentication
NSC.AUT.CONN.13
NSC.SEC
NSC.SEC.01
NSC.SEC.02
NSC.SEC.03
Should accomplish authentication in three ways:

Locally(Internal authentication), using LDAP
protocol and using RADIUS protocol(External
authentication).
NSC.SEC.04
Should access MAM for Local authentication
NSC.SEC.05
Should access AAA server for LDAP and RADIUS

protocols.
NSC.SEC.06
Should provide System based IPSec
NSC.SEC.07
Customized VPN
Establishment of connection
Socket should be created and VPN connection
should be established when the connect provision
is clicked
On receiving connect request ,Create a TCP socket

for NSServer to send and receive packets .
If socket is created successfully send hello
message to NSServer and wait for response. Else
return error.
If hello message is received Mode should be set.
Else return error.
On receiving Mode Packet create SSL socket and
Zlib socket depending on the mode received.
NSC.VP
NSC.VP.CONN
NSC.VP.CONN.01
NSC.VP.CONN.02
NSC.VP.CONN.03
NSC.VP.CONN.04
NSC.VP.CONN.05
NSC.VP.CONN.06
Send MAM authentication request to server.
On receiving response for authentication from
server ,notify connection success or failure.
Sending Packets
Read the TCP packet from TUN interface and send
the packet to Zlib if compression is enabled else to
SSL socket if encryption is enabled.
Add SSL headers to payload received in SSL
socket if encryption is enabled.
Add Zlib headers to payload received in Zlib socket
if compression is enabled.
NSC.VP.CONN.07
NSC.VP.SP
NSC.VP.SP.01
NSC.VP.SP.02
NSC.VP.SP.03
NSC.VP.SP.04
Add Netsnapper header.
Add the TCP/IP headers.
NSC.VP.SP.05
NSC.VP.SP.06
Add ethernet frame header.

Receiving Packets
NSC.VP.RP
NSC.VP.RP.01
Remove the ethernet frame header

Remove the TCP/IP headers
NSC.VP.RP.02
NSC.VP.RP.03
Remove the Netsnapper header

Remove the SSL headers if encryption has been
set.
Remove the Zlib headers if compression has been
set.
NSC.VP.RP.04
NSC.VP.RP.05
NSC.VP.RP.06
Write the payload to TUN interface
SEAMLESS SWITCHING
Should manage a list of available interfaces to
achieve seamless switching
NSC.SS
NSC.SS.01
If the interfaces are not available, then the backup

interface should "switch on" automatically and
connection should switch to that interface
seamlessly if Wifi Manager is enabled
NSC.SS.02
Should switch to the backup interface without any

time lag since its switching to an already connected
backup interface
NSC.SS.03
Should switch to other interfaces available with a

small switching time since a new connection is
established.
NSC.SS.04
Switching on Priority basis
NSC.SS.SP
Should provide connection to an interface based on

highest priority interface or user settings.
NSC.SS.SP.01
As soon as an interface with a higher priority

becomes available and not other interface is locked,
the switching should occur to that newly found
interface with higher priority
NSC.SS.SP.02
There must be a provision for the user to adjust the

priority of interfaces
NSC.SS.SP.03
Priority of the available interfaces should be

adjustable by the user only if this is allowed in the
configuration received from the server side.
NSC.SS.SP.04
Switching should not be allowed when the current

interface is locked.
For seamless switching to occur, there must be
atleast two interfaces available.
NSC.SS.SP.05
NSC.SS.SP.06
Seamless switching should occur if the current

interface becomes unavailable.
NSC.SS.SP.07
When switching occurs it must be intimated to the

user by displaying a message in the connection
page.
NSC.SS.SP.08
DATA COMPRESSION
NSC.DC
Should have provision for the user to choose to use

the data compression.
NSC.DC.01
Should have a provision to compress the data

before sending
Should use the Zlib algorithm for compressing the
data
Should have a provision to compress different data
such as text, images, videos.
NSC.DC.02
NSC.DC.03
NSC.DC.04
Should have a provision to change the settings of

using data compression, without any data loss and
session persistence when the client is connected.
NSC.DC.05
Should maintain the session when the user turns

on/off the use of compression
NSC.DC.06
Zlib version should be upgraded to version 1.2.8
NSC.DC.07
DATA ENCRYPTION
Should provide encryption with different levels of
encryption strength such as low, medium and high
Should have provision for generating different key
for encryption for each and every session for which
TKIP should be used
Should use WEP method for a protection fetch and
intercept of information
NSC.DE
NSC.DE.01
NSC.DE.02
NSC.DE.03
Should have a provision to change the Encryption

level even when the client is in Connected State
NSC.DE.04
Should use AES algorithm for encryption
NSC.DE.05
Key size of encryption may be 128 or 192 or 256

bits
NSC.DE.06
Should maintain the session when the encryption

level is changed by the user.
NSC.DE.07
OpenSSL version should be upgraded to version

1.0.2a
NS Client solution should support both SHA1 and
SHA2
NSC.DE.08
NSC.DE.09
Selecting Encryption level as LOW, should use

128bit encryption key
NSC.DE.10
Selecting Encryption level as MEDIUM, should use

256bit encryption key
NSC.DE.11
Selecting Encryption level as HIGH, should use

256bit or higher encryption key
CLIENT KERNEL
NSC.DE.12
NSC.CK
Should have provision for Netsnapper Virtual

Ethernet Driver/VPN interface
NSC.CK.01
Should have provision for Network interface

Scanner/Manager
NSC.CK.02
Should have provision for System based QoS
NSC.CK.03
Should have provision for MAC Address Translation
NSC.CK.04
Should have provision for Broadcasting for

Netsnapper Virtual Network
NSC.CK.05
ADDITIONAL FEATURES
Should have provisions for displaying forced
parameters as disabled
Should have provisions for making the unpermitted
parameters disappear
Should provide automatic network
configuration(DHCP, DNS. NAT, etc)
NSC.AF
NSC.AF.01
NSC.AF.02
NSC.AF.03
Should provide Interface(low cost)intelligent choice
NSC.AF.04
Should provide Mobile Operator Network Access

points management
NSC.AF.05
CONNECTION INFORMATION
NSC.CI
Should have provision to show the connection and

switching information
NSC.CI.01
Should have provision for the user to view the

session duration, Optimised/actual download speed
and Optimized/actual up speed
NSC.CI.02
Should have provision to display the current

username, current server, current interface and
current profile
NSC.CI.03
Should have provision to display the backup server,

backup interface, backup profile
NSC.CI.04
Should have provision for displaying server virtual

IP and client Virtual IP
NSC.CI.05
Should have provision to disconnect the connection
NSC.CI.06
Should have provision for the recent notification

(i.e) the status of the client.
NSC.CI.07
Should have provision to go the credentials page on

disconnection
NSC.CI.08
Should have a provision to display the VPN session

details
NSC.CI.09
ACCOUNTING INFORMATION
Should have provision for the user to select a
period(session, day, week, month and total) for
which the statistics should be displayed
NSC.AI
NSC.AI.01
Should have provision for the user to select the

interface for the the statistics should be displayed.
NSC.AI.02

received and sent actual/compression rate and
size.
NSC.AI.03
Should show the accounting info to the user

depending on the permission from Server side.
NSC.AI.04
The statistics should be in the form of

charts/graphs.
NSC.AI.05
Should have a provision to reset the statistics
NSC.AI.06
Should display a message if the statistics are not

available
NSC.AI.07
INTERFACE MANAGEMENT
Interface List
Should have provison to show the hidden devices
changes and send them to the Netsnapper Core
NSC.IM
NSC.IM.IL
NSC.IM.IL.01
NSC.IM.IL.02

changes made
NSC.IM.IL.03
Should have provision to display the number of

interfaces of each type
NSC.IM.IL.04
Recognition of Interfaces on Start Up
NSC.IM.RECS
Should have a provision to recognize all the

available interfaces and show the user
NSC.IM.RECS.01
WiFi should be recognized if its available.
NSC.IM.RECS.02
Ethernet should be recognized if its available.
NSC.IM.RECS.03
USB tethering should be recognized if its available.
NSC.IM.RECS.04
Recognition of Interfaces on its availability
NSC.IM.RECA
Interface list should be updated when a new

interface is available.
Should have provision for the user to know the

status of each interface such as Dialing, Disabled,
Hidden, Locked, Unavailable, Used by the system,
Used for backup.
Interface Settings
NSC.IM.RECA.01
NSC.IM.RECA.02
NSC.IM.IS
Should have provisions to change the settings of

each interface
NSC.IM.IS.01
In the settings, provisions such as customizing the

name of the interface, setting the status of the
interface and selecting profiles should be provided
to the user
NSC.IM.IS.02
Should have provision to save the settings and

send them to the Netsnapper Core
Should have provision to go back to the interface
list page
Should not allow any connection via any interface
other than the locked interface if Locked option is
enabled
Should not allow connection via the interface which
is selected as disabled.
Should enable "hidden" facility only when an
interface is disabled.
PROFILE MANAGEMENT
Should maintain a list of networks such as LAN,
VPN, DUN, WLAN
Should have provision for the user to change the
priority
Should have provision for the user to apply the
changes made in priority
Should provide Sim Manager functionality for clients
whose connections are established via DUN
interface
Network Settings
Profiles
NSC.IM.IS.03
NSC.IM.IS.04
NSC.IM.IS.05
NSC.IM.IS.06
NSC.IM.IS.07
NSC.PM
NSC.PM.01
NSC.PM.02
NSC.PM.03
NSC.PM.04
NSC.PM.NS
NSC.PM.NS.01
Should maintain a list of profiles in each network
NSC.PM.NS.01.01
Should have provision for the user to add a profile
NSC.PM.NS.01.02
Should have provision for the user to change the

priority
NSC.PM.NS.01.03
Should have provision for the user to apply the

NSC.PM.NS.01.04
Should not allow creating profiles for LAN
NSC.PM.NS.01.05
Should have provision for the user to cancel the

NSC.PM.NS.01.06
Add profile - WLAN

Should have provisions for the user to enter profile
name
Should have provisions for the user to enter SSID
Should have provisions for the user to choose the
authentication type among open, shared, WPA,
WPAPSK, WPA2 and WPAPSK2
Should have provisions for the user to select the
encryption among none or WEP.
Should have provision to save the profile and send
them to the Netsnapper Core
Should have provision to go back to the profile list
Add Profile - VPN
NSC.PM.NS.02
NSC.PM.NS.02.01
NSC.PM.NS.02.02
NSC.PM.NS.02.03
NSC.PM.NS.02.04
NSC.PM.NS.02.05
NSC.PM.NS.02.06
NSC.PM.NS.03
Should have a provision to enter the profile name
NSC.PM.NS.03.01
Should have a provision to enter the Host name
NSC.PM.NS.03.02
should have a provision for the user to choose the

type such as PPoE
NSC.PM.NS.03.03
Should have a provision to enter the user name
NSC.PM.NS.03.04
Should have a provision to enter the password
NSC.PM.NS.03.05

NSC.PM.NS.03.06
NSC.PM.NS.03.07
Add Profile - DUN
NSC.PM.NS.04
Should have a provision to enter the profile name
NSC.PM.NS.04.01
Should have a provision to enter the phone number
NSC.PM.NS.04.02
Should have a provsion to enter the APN
NSC.PM.NS.04.03
Should have a provision to enable or disable Use

modem init string
NSC.PM.NS.04.04
Should have a provsion to enter the init string
NSC.PM.NS.04.05
Should have a provision to enter the user name
NSC.PM.NS.04.06
Should have a provision to enter the password
NSC.PM.NS.04.07

NSC.PM.NS.04.08

Sim Manager
Should have a provision for the displaying the
current interface and operator
NSC.PM.NS.04.09
NSC.PM.NS.05
NSC.PM.NS.05.01
Should have a provision for the user to lock the sim
NSC.PM.NS.05.02
Should have a provision for the user to change the

PIN
NSC.PM.NS.05.03
Should have a provision for the user to send SMS

in which there should provisions for the user to i)
select the folder ii) create a new text message iii)
forward a message iv) delete a message v) display
information about the number of messages stored
and vi) move back to the Sim Manager page
NSC.PM.NS.05.04
Should have a provision for the user to go the

operator panel for switching in which there should
have a provision for the user i) to scan the
operators available along with their status ii) to the
selected operator iii) to come back to sim manager
page
NSC.PM.NS.05.05
For locked sims, Should verify the PIN each and

every time the user wants to access the sim
NSC.PM.NS.05.06
GRANTED SERVICES(FIREWALL)
Use granted service
NSC.GS
NSC.GS.U
Should have a provision for the user to select

whether the user wants the granted services
NSC.GS.U.01
Should not allow the connections passing through

ports that are not in the granted services list.
NSC.GS.U.02
Should have provision to block specific applications

for any predifined time period
NSC.GS.U.03
Should have provision for a connection to be closed

automatically if there is no network activities during
timeout
NSC.GS.U.04
Should have provision for all network activities to be

blocked for specific applications
Granted services list
NSC.GS.U.05
NSC.GS.L
Should maintain a list of granted services and

should be enabled for users who need it
NSC.GS.L.01
Should have a provision for the user to add a

granted service
NSC.GS.L.02
Should have a provision for the user to remove a

granted service
NSC.GS.L.03
Add a granted service
NSC.GS.A
Should have a provision for the user to enter the

service name
NSC.GS.A.01
Should have a provision for the user to enter the

port number
NSC.GS.A.02
Should have a provision for the user to select the

protocol(TCP or UDP)
NSC.GS.A.03

direction(outgoing or incoming)
NSC.GS.A.04

granted service and send them to the Netsnapper
Core
NSC.GS.A.05
Should have the provision for the user to go back to

the granted service list
NSC.GS.A.06
Saving and cancelling
NSC.GS.SC
Should have a provision for the user to apply the

changes
NSC.GS.SC.01

changes
NSC.GS.SC.02
OTHER OPTIONS
NSC.OO

language
NSC.OO.01
Should have provision for the user to keep in alive

mode
NSC.OO.02
Should have provision for the user to Start the UI

agent on OS start
NSC.OO.03
Should have a provision for the user to establish the

connection on start
NSC.OO.04
Should have a provision for the user to switch

ON/OFF the WiFi manager
NSC.OO.05

ON/OFF the data compression
NSC.OO.06

encryption level if he has the permission from
server
NSC.OO.07

ON/OFF the encryption
NSC.OO.08
Should have a provision for the user to apply the

changes
NSC.OO.09

changes
NSC.OO.10
UPDATION
Should have provision to verify every time the client
connects to the server whether the new Client
version is available for downloading on the Server
side.
NSC.UP
NSC.UP.01
For Updation as a permitted setting from Server

side, Should have a provision to send a message to
the client if the new version download is possible
NSC.UP.02
For Updation as a forced setting from the Server

side, should download the new version
authomatically
NSC.UP.03
Should have a provision for the user to view the

current client version, Update version, Update
filename and Update file size
NSC.UP.04
Should have provision to Update after downloading

manually
NSC.UP.05
Should have a provision to stop the update

download for sometime and later continue it
NSC.UP.06
Should have a provision to disable the manual

download facility when firewall is turned on
NSC.UP.07
Should provide Download/Install functionality with

progress bar
NSC.UP.08
Client should support https urls for getting update

information from MAM server
NSC.UP.09
Client should support https urls of updated software
NSC.UP.10
Client should support http urls for getting update

information from MAM server
NSC.UP.11
Client should support http urls of updated software
NSC.UP.12
SERVER LIST
Client should send "ServerListRequest" request
should be sent while starting nscore process
For getting Server list, Client should load certificate
and if it is not available, request for certificate from
server. Then Client should send
NSCOMM_TYPE_SERVER_LIST_HELLO
message and
NSCOMM_TYPE_SERVER_LIST_REQUEST message.
Client should list the server in the same order, as it
received from Mam Server.
Client should show "Default" option as first followed

by server list
Should have provision for the user to select any of

the server list
user, if any of the server name is selected, client
should try to connect all interface list for the
selected server, and if none of the interface for
selected server is available then client should try to
connect to other interface also.
When connection provision is clicked by the user, if
default option is selected, client should try to
connnect to all servers in the order it is received
When no server IP is reachable while establishing
connection, then Client should show "Server
Unreachable" error message
When
NSCOMM_TYPE_SERVER_LIST_REQUEST fails
while launching, client should show "Default" and
"Custom" option in drop down list.
When
NSCOMM_TYPE_SERVER_LIST_REQUEST fails
while launching, client should connect to Default or
Custom option
Client should check domain configuration when
connection provision is clicked and should update
the server list in UI, if it has been changed
NSC.SL
NSC.SL.01
NSC.SL.02
NSC.SL.03
NSC.SL.04
NSC.SL.05
NSC.SL.06
NSC.SL.07
NSC.SL.08
NSC.SL.09
NSC.SL.10
NSC.SL.11
When Server list is changed in Mam server, client

should try to fetch new Server list and update in UI
whenever it detects domain hash value change.
When client has selected a server and connected,
and if domain configuration changes, then
connection should be re-established with the same
selected server
When client has selected a server and connected,
and if domain configuration changes and obtained
server list doesnt have the same selected server,
then client should connect in default mode.
NSC.SL.12
NSC.SL.13
NSC.SL.14
In case of switching, Client should try to connect

with the previously connected server
NSC.SL.15
Client should load the Credentials Page of Settings

Tab when the Application is launched after
installation
NSC.SL.16

user, if server name selected is unreachable then
client should try to connect with all other servers in
the order it is received from MAM
NSC.SL.17
In case of switching, if previously connected server

is unreachable then the client should try to connect
with all other servers in round robin sequence.
NSC.SL.18
CUSTOM SUPPORT
NSC.CS
Client should show "custom..." option as last in the

drop down server list
When custom option is selected by user, client
should have provision to enter Host IP and Port
should have 6671 as default value for connecting
with server
When other than custom option is selected by user,
Host IP and port fields should be hidden.
When custom option is selected and connection
provision is clicked by the user, after disconnection,
client should show custom option as selected in
drop down list
provision is clicked by the user, after closing and
launching the application client should show custom
option as selected in drop down list
provision is clicked by the user, client should try to
connect with list of interface IPs received for custom
server from MAM server.
NSC.CS.01
NSC.CS.02
NSC.CS.03
NSC.CS.04
NSC.CS.05
NSC.CS.06
When server list is fetched by the server and

custom option is selected, client should show the
same server list after disconnecting from the server
SPLIT TUNNELING
Client should have provision to receive VNET

configuration and routing rules from MAM server
Client should send
ClientNetworkConfigurationRequest to MAM for
receiving VNET configuration
Client should able to parse the
ClientNetworkConfiguration response for getting
routing rules.
Client should add the Source based routing rules
received from MAM server to the routing table once
the NSClient connection and firewall configuration
is complete
Client should delete the routing rules from the
routing table while disconnecting the client and
persist the same for next connection
NSC.CS.07
NSC.ST
NSC.ST.01
NSC.ST.02
NSC.ST.03
NSC.ST.04
NSC.ST.05
Client should send NetworkConfigurationHash

value in authentication request packet in order to
get updated hash value
NSC.ST.06
Client should send NetworkConfigurationHash

value in client check configuration request packet
sends in a period of configuration request interval
NSC.ST.07
During connection establishment, client should

fetch the updated split tunneling configuration if the
ClientNetworkConfiguration hash is changed
NSC.ST.08
In case of Switching, client should fetch the updated

split tunneling configuration if the
ClientNetworkConfiguration hash is changed
If any changes made in routing rules in MAM server,
client should apply the updated routing rules while
checking configuration change in a period of
configuration request interval
For routing entries added under "Forward to VPN,
the traffic from these IP adddresses should be
routed over Netsnapper VPN
For routing entries not added under "Forward to
VPN, the traffic from these IP adddresses should
directly access provider's server
NSC.ST.09
NSC.ST.10
NSC.ST.11
NSC.ST.12
When Use VNET as default gateway is set in MAM

server, client should route all traffic over netsnapper
VPN except the routing rules configured for
bypassing VPN
When 'Use VNET as default gateway' is not
checked in MAM server, client should bypass VPN
for all traffic except the specific IPs configured for
routing through VPN
In case of backup connection, client should apply
the same routing rules when switches from primary
connection to backup connection
If routing rule is applied for specific traffic to route
through VPN, then client statistics should be
updated for particular traffic
TRANSPORT
NSC.ST.13
NSC.ST.14
NSC.ST.15
NSC.ST.16
NSC.TR
Should provide 3rd PPTP support
NSC.TR.01
Should provide 3rd L2TP-IPSec support
NSC.TR.02
Should provide 3rd PPPoE support
NSC.TR.03
Should support IPv4 over Physical IPv4
NSC.TR.04
Should support IPv6 over Physical IPv6
NSC.TR.05
Should provide congestion control management
NSC.TR.06
ABOUT NETSNAPPER
information about current Netsnapper Client version
and Build number
Should have provision for the user to view client
network interface
Should have provision for the user to exit/shutdown
Netsnapper application
Should disconnect the connection of client with the

server when the client logs out.
NSC.AN
NSC.AN.01
NSC.AN.02
NSC.AN.03
NSC.AN.04
Should have indication of Plain TCP mode,

compression and encryption
NSC.AN.05
DATA LIMIT
NSC.DL
When data limit checkbox is checked in MAM, client

should have provision to get the data limit value
from MAM for each and every session
NSC.DL.01
When data limit checkbox is not checked in MAM,

client should get only authentication status code in
authentication response. And there should not be
any provision to check download and upload data
limit for this client.
NSC.DL.02
Client should parse the authentication response

packet for getting the data limit value
NSC.DL.03
Client should able to check whether both optimized

download and upload data size reaches data limit
value or not
NSC.DL.04
Should disconnect the connection of client with the

server when optimized download and upload data
size reaches data limit value.
NSC.DL.05
When sum of optimized download and upload data

size reaches data limit value, client should display
the error message as "Data usage limit exceeds for
this client"
NSC.DL.06
When data limit error code is getting from MAM,

client should display the error message as "Data
usage limit exceeds for this client"
NSC.DL.07
QUERIES
Connection/Disconnection Management
To order the Core to begin connection
establishment with the Server, the following query
should be sent to the Core:QUERY_CONNECT
To order the Core to disconnect from the Server, the
following query should be sent to the
Core:QUERY_DISCONNECT
Connection Status Management
To view connection status on the Client UI, the
query QUERY_CONNECTION_STATUS should be
sent to the Core
NSC.QU
NSC.QU.CM
NSC.QU.CM.01
NSC.QU.CM.02
NSC.QU.CSM
NSC.QU.CSM.01
The response from the Core is

RESPONSE_CONNECTION_STATUS with the
following objects:ConnectionStatus
ConnectionHasBeenEstablished
ConnectionStatus
ConnectRequest
ConnectRequestOnDemand
encryptionLevel
PrimaryServer
PrimaryInterface
BackupServer
BackupInterface
serverVirtualIP
clientVirtualIP
userName
ConnectionProtocol
ConnectionCompressed
ConnectionEstablishedTimestamp
If connection status is changed in the Core, the

event
EVENT_CONNECTION_STATUS_CHANGED is
sent to the Client UI
Connection Data Management
To view connection data on the Client UI, the query
QUERY_CONNECTION_DATA should be sent to
the Core
RESPONSE_CONNECTION_DATA with the
following objects:ConnectionData
Host
port
customHost
customPort
User
password
IMEIS
RequestAuth
anonGuid
To set new connection data, they should be sent to
the Core with the following message:
SET_CONNECTION_DATA
If connection data are changed in the Core, the
following event is sent to the Client
UI:EVENT_CONNECTION_DATA_CHANGED
Accounting Information Management
NSC.QU.CSM.02
NSC.QU.CSM.03
NSC.QU.CDM
NSC.QU.CDM.01
NSC.QU.CDM.02
NSC.QU.CDM.03
NSC.QU.CDM.04
NSC.QU.AIM
To view accounting information on the Client UI, the

following query should be sent to the
Core:QUERY_ACCOUNTING_INFO with the
objects such as
AccountingInfo
AccountingEntry
User
Guid

:RESPONSE_ACCOUNTING_INFO with the
following objects :AccountingInfo
AccountingEntry
Guid
User
AccountingData
RawSent
RawReceived
CompressedSent
CompressedReceived
Period
TimeStamp
DownloadRawConnectionSpeed
UploadRawConnectionSpeed
DownloadOptimizedConnectionSpeed
UploadOptimizedConnectionSpeed
To reset accounting information for some period

and network interface, the following query should be
sent to the Core:
QUERY_RESET_ACCOUNTING_INFO with
objects such as
AccountingInfo
AccountingEntry
User
Guid
AccountingData
Period
RawSent
If accounting information is changed in the Core,
the following event is sent to the Client
UI:EVENT_ACCOUNTING_INFO_CHANGED
General Settings Management
To view general application settings on the Client
UI, the following query should be sent to the
Core:QUERY_GENERAL_SETTINGS
NSC.QU.AIM.01
NSC.QU.AIM.02
NSC.QU.AIM.03
NSC.QU.AIM.04
NSC.QU.GSM
NSC.QU.GSM.01

RESPONSE_GENERAL_SETTINGS with the
following objects :GeneralSettings
Mam2General
forceUnderivable
forceStartOnOsStart
forceConnectOnStart
forceRememberUserPassword
forceKeepAliveMode
forceEncryptionLevel
forceLanguage
forceRequestAuth
forceWifiManager
forceGrantedServices
forceNicProfileManager
forceNicOrderListForbid
forceNicPrioritiesForbid
forceNicSettings
forceServerless
forceUpdate
forceSimplifyUI
forceConnectOnDemand
LocalSettings
KeepAliveMode
Language
encryptionLevel
StartOnOsStart
ConnectOnStart
useWifiManager
useGrantedServices
RememberUserPassword
ShowHidden
SimplifyMode
To set new general application settings, they should

be sent to the Core with the following
message:SET_LOCAL_SETTINGS with the objects
such as LocalSettings
Language
KeepAliveMode
ConnectOnStart
StartOnOsStart
encryptionLevel
useWifiManager
useGrantedServices
RememberUserPassword
ShowHidden
SimplifyMode
If local application settings is changed in the Core,
UI:EVENT_LOCAL_SETTINGS_CHANGED
Device List Management
To view the list of existent devices on the Client UI,
the following query should be sent to the
Core:QUERY_DEVICE_LIST
NSC.QU.GSM.02
NSC.QU.GSM.03
NSC.QU.GSM.04
NSC.QU.DLM
NSC.QU.DLM.01
The response from the Core is the

following:RESPONSE_DEVICE_LIST with objects
such as DeviceList
Device
CustomName
UseCustomName
DeviceFileName
TunnelNumber
ConnectionId
Metric
AccountingType
Alive
Available
Locked
Disabled
Hidden
Dialing
Deleted
UseForBackup
Home
OSEnabled
IMEI
IMSI
modemParamsScanned
serverOrderIndex
Forbidden
ActiveProfile
Profiles
Id
Interface
Index
MacAddress
ipAddress
IpMask
Gateway
NameServer
Dublicated objects
name
Description
type
Guid
NSC.QU.DLM.02
To set device list with new settings, it should be sent

to the Core with the following
message:SET_DEVICE_LIST and with the objects
such as DeviceList
Device
Guid
name
Description
CustomName
type
Metric
Alive
Available
Dialing
Disabled
Locked
UseForBackup
ActiveProfile
UseCustomName
Hidden
Profiles
Id
If device list is changed in the Core, the following

event is sent to the Client
UI:EVENT_DEVICE_LIST_CHANGED
Update Management
To get the information about update, the following
query should be sent to the
Core:RESPONSE_UPDATE_INFO with the objects
such as Mam2Update
ClientUpdateUrl
Release
Link
File
Size
MD5
Version
Subversion
Patch
Build
NSC.QU.DLM.03
NSC.QU.DLM.04
NSC.QU.UM
NSC.QU.UM.01
If update information is changed in the Core, the

UI:EVENT_UPDATE_INFO_CHANGED
NSC.QU.UM.02
To get the status of update, the following query

should be sent to the
Core:QUERY_UPDATE_STATUS
NSC.QU.UM.03

following:RESPONSE_UPDATE_STATUS with the
objects such as UpdateStatus
LocalPath
DownloadedSize
Status
CurrentVersion
NSC.QU.UM.04
To begin/resume update downloading, the following

Core:QUERY_DOWNLOAD_UPDATE
NSC.QU.UM.05
To pause update downloading, the following query

Core:QUERY_PAUSE_UPDATE
NSC.QU.UM.06
To install downloaded update, the following query

Core:QUERY_INSTALL_UPDATE
NSC.QU.UM.07
Granted Services Management

To view on the Client UI the list of the granted
services defined locally, the following query should
be sent to the
Core:QUERY_LOCAL_GRANTED_SERVICES_LIS
T
following:RESPONSE_LOCAL_GRANTED_SERVI
CES_LIST with the objects such as
grantedServiceManager
grantedService
grantedService attributes
serviceName
servicePort
serviceProtocol
serviceDirection
To view on the Client UI the list of the granted
services defined on the server side, the following
Core:QUERY_REMOTE_GRANTED_SERVICES_L
IST
following:RESPONSE_REMOTE_GRANTED_SER
VICES_LIST with the objects such as
grantedServiceManager
grantedService
serviceName
servicePort
serviceProtocol
serviceDirection
NSC.QU.GS
NSC.QU.GS.01
NSC.QU.GS.02
NSC.QU.GS.03
NSC.QU.GS.04
To set a list of new local granted service, it should

be sent to the Core with the following
message:SET_GRANTED_SERVICES_LIST witht
the objects such as : grantedServiceManager
grantedService
serviceName
servicePort
serviceProtocol
serviceDirection
If local granted services list is changed in the Core,

UI:EVENT_LOCAL_GRANTED_SERVICES_LIST_
CHANGED
If remote granted services list is changed in the
Core, the following event is sent to the Client
UI:EVENT_REMOTE_GRANTED_SERVICES_LIS
T_CHANGED
UI Permissions Management
To get the permissions on the access to some parts
of the application Core through UI, the following
Core:QUERY_UI_PERMISSIONS
following:RESPONSE_UI_PERMISSIONS with the
objects such as permissionManager
uiStartOnOsStart
uiConnectOnStart
uiRememberPassword
uiKeepAliveMode
uiEncryptionLevel
uiNicProfileManager
uiNicSettings
uiLanguage
uiUpdate
uiTracer
uiAccounting
uiWifiManager
uiGrantedServices
NIC Order List Management
To view on the Client UI the list of the NIC types
ordered by priority, the following query should be
sent to the Core:QUERY_NIC_ORDER_LIST
NSC.QU.GS.05
NSC.QU.GS.06
NSC.QU.GS.07
NSC.QU.UPM
NSC.QU.UPM.01
NSC.QU.UPM.02
NSC.QU.NOLM
NSC.QU.NOLM.01

following:RESPONSE_NIC_ORDER_LIST with the
objects such as nicOrderList
nicOrderList attributes
fixed
nicOrder
nicOrder attributes
order
nic
disabled
useForBackup
invisible
To set a list of NIC types ordered by priority, it

should be sent to the Core with the following
message:SET_NIC_ORDER_LIST with the objects
such as nicOrderList
nicOrderList attributes
fixed
nicOrder
nicOrder attributes
order
nic
disabled
useForBackup
invisible
If the order of the NIC types or their settings is
changed in the Core, the following event is sent to
the Client
UI:EVENT_NIC_ORDER_LIST_CHANGED
VPN Profiles Management
To view on the Client UI the list of the VPN profiles,
Core:QUERY_VPN_PROFILES
following:RESPONSE_VPN_PROFILES with the
objects such as vpnDataList
vpnData
vpnData attributes
profileId
profileType
order
VPNProfile
name
vpnHostName
vpnType
useSystemProfiles
vpnMSM
vpnSecurity
vpnSecurity attributes
userName
password
NSC.QU.NOLM.02
NSC.QU.NOLM.03
NSC.QU.NOLM.04
NSC.QU.VPN
NSC.QU.VPN.01
NSC.QU.VPN.02
To set new VPN profiles list (with new profiles or

with changed priority), the whole list should be sent
message:SET_VPN_PROFILES with the objects
such as vpnDataList
vpnData
vpnData attributes
profileId
profileType
order
VPNProfile
name
vpnHostName
vpnType
useSystemProfiles
vpnMSM
vpnSecurity
vpnSecurity attributes
userName
password
If VPN profiles list is changed in the Core, the

UI:EVENT_VPN_PROFILES_CHANGED
DUN Profiles Management
To view on the Client UI the list of the DUN profiles,
Core:QUERY_DUN_PROFILES
following:RESPONSE_DUN_PROFILES with the
objects :dunDataList See objects description in
DUN Profiles Management Objects.
See sample structure below to check, what objects
are included into the parent ones.
dunData
dunData attributes
profileId
profileType
order
DUNProfile
name
providerName
type
phoneNumber
accessPointName
modemInitString
useModemInitString
dunMSM
dunSecurity
dunSecurity attributes
userName
password
NSC.QU.VPN.03
NSC.QU.VPN.04
NSC.QU.DUN
NSC.QU.DUN.01
NSC.QU.DUN.02
To set new DUN profiles list (with new profiles or

message:SET_DUN_PROFILES with the objects
such as dunDataList See objects description in
DUN Profiles Management Objects.
See sample structure below to check, what objects
are included into the parent ones.
dunData
dunData attributes
profileId
profileType
order
DUNProfile
name
providerName
type
phoneNumber
accessPointName
modemInitString
useModemInitString
dunMSM
dunSecurity
dunSecurity attributes
userName
password
If DUN profiles list is changed in the Core, the

UI:EVENT_DUN_PROFILES_CHANGED
WLAN Profiles Management
To view on the Client UI the list of the WLAN
profiles, the following query should be sent to the
Core:QUERY_WLAN_PROFILES
NSC.QU.DUN.03
NSC.QU.DUN.04
NSC.QU.WLAN
NSC.QU.WLAN.01

following:RESPONSE_WLAN_PROFILES with the
objects such as wifiDataList
wifiData
wifiData attributes
profileId
profileType
order
webAuthType
webAuthLogin
webAuthPassword
webAuthTail
webAuthPort
identity
password
WLANProfile
name
SSIDConfig
SSID
hex
name (SSID)
nonBroadcast
connectionType
connectionMode
autoSwitch
MSM
security
authEncryption
authentication
encryption
useOneX
sharedKey
keyType
keyMaterial
protected
keyIndex
NSC.QU.WLAN.02
To set new WLAN profiles list (with new profiles or

message:SET_WLAN_PROFILES with the objects
such as wifiDataList
wifiData
wifiData attributes
profileId
profileType
order
webAuthType
webAuthLogin
webAuthPassword
webAuthTail
webAuthPort
identity
password
WLANProfile
name
SSIDConfig
SSID
hex
name (SSID)
nonBroadcast
connectionType
connectionMode
autoSwitch
MSM
security
authEncryption
authentication
encryption
useOneX
sharedKey
keyType
keyMaterial
protected
keyIndex
If WLAN profiles list is changed in the Core, the
UI:EVENT_WLAN_PROFILES_CHANGED
New Profile ID getting
To get the identifier that should be assigned to any
new created profile, the following query should be
sent to the Core:QUERY_NEW_PROFILE_ID
following:RESPONSE_NEW_PROFILE_ID with the
objects such as
StringData
Content
Server List Getting
To get the list of servers that can be used for
connection and MAC address assigned to the Client
on the server side, the following query should be
sent to the Core:QUERY_MAM_2_CONNECTION
NSC.QU.WLAN.03
NSC.QU.WLAN.04
NSC.QU.NP
NSC.QU.NP.01
NSC.QU.NP.02
NSC.QU.SLG
NSC.QU.SLG.01

following:RESPONSE_MAM_2_CONNECTION with
the objects such as Mam2Connection
Mam2Connection attributes
clientMac
server
name
serverAddressList
serverAddress
order
ipAddress
port
compression
tunnelAddress
ipAddress
IpMask
ServerTunnelMacAddress
ServerTunnelIpAddress
Device Status Getting

To get status information about network devices,
Core:QUERY_DEVICE_STATUS_LIST
following:RESPONSE_DEVICE_STATUS_LIST with
the objects such as DeviceStatusList
DeviceStatus
SignalLevel
type
InProcess
Available
Guid
StatusHolder
StatusHolder attributes
type
PIN
PINLocked
Roaming
IMEI
IMSI
GSMOperator
name
ShortName
Id
AcTech
Status
GSMOperatorsList
Device status information is sent by other

Netsnapper module (Netsnapper Helper) to the
Core with the following
message:SET_DEVICE_STATUS_LIST
NSC.QU.SLG.02
NSC.QU.DSG
NSC.QU.DSG.01
NSC.QU.DSG.02
NSC.QU.DSG.03
If device status information is changed in the Core,

UI:EVENT_DEVICE_STATUS_LIST_CHANGED
Notifications
To notify about Core status changing, the following
event is sent to the Client
UI:EVENT_CORE_SUSPENDING
EVENT_CORE_SUSPEND
EVENT_CORE_RESUMING
EVENT_CORE_RESUME
If new configuration is received from MAM, the
UI:EVENT_MAM_CONFIG_RECEIVED
If some error occurs, the following event is sent to
the Client UI:EVENT_GENERIC_ERROR.The
possible errors:NAPI_CONNECTION_LOST
TUNNEL_INTERNAL_ERROR
TUNNEL_COULD_NOT_RESOLVE_DN
TUNNEL_REQUEST_CERT
TUNNEL_ROOT_CERT
TUNNEL_CONNECTION
TUNNEL_INVALID_HOST
TUNNEL_AUTHENTICATION
TUNNEL_RECONNECTING
TUNNEL_INVALID_USERNAME
TUNNEL_VNET_ENABLE
TUNNEL_VNET_CONFIGURE
TUNNEL_BINDER_ENABLE
TUNNEL_BINDER_CONFIGURE
TUNNEL_SESSION_REINITIALIZED
TUNNEL_MAM_NO_CONFIGURATION
TUNNEL_AUTHENTICATION_FATAL
INTERFACES_NO_AVAILABLE_DEVICE
INTERFACES_NO_AVAILABLE_INTERFACE
Interface Requirements
GUI
Installation
NSC.QU.DSG.04
NSC.QU.NT
NSC.QU.NT.01
NSC.QU.NT.02
NSC.QU.NT.03
NSC
NSC.IN
Double clicking on exe file should open the

Welcome screen
NSC.IN.01
Application should provide Back button, Next button

and cancel button in Welcome screen
NSC.IN.02
Should disable the Back button in Welcome Screen
NSC.IN.03
Clicking Next button should take you to End-User

License Agreement Screen if you have not installed
previously
NSC.IN.04
Clicking Next button should take you to

Change,repair, or remove installation screen if you
have installed previously
NSC.IN.05
Should disable Change option in Change,repair, or

remove installation screen
NSC.IN.06
Should click Repair to open the installation wizard

and start installation
NSC.IN.07
Clicking Remove should take you to the Netsnapper

Client Setup wizard ended prematurely screen
NSC.IN.08
Netsnapper Client Setup wizard ended prematurely

screen should provide disabled Back, Cancel button
and enabled Finish button
NSC.IN.09
Clicking Finish button in Netsnapper Client Setup

wizard ended prematurely screen should ask you to
restart the system
NSC.IN.10
In restart window, clicking Yes should restart

immediately
NSC.IN.11
In restart window, click No to select manually

Restart later
NSC.IN.12
In End-User License Agreement Screen, there

should be check box for I accept the terms in the
License Agreement
NSC.IN.13
In End-User License Agreement Screen, Next

button should be disabled if I accept the terms in
License Agreement checkbox is unchecked
NSC.IN.14
In End-User License Agreement Screen, Next

button should be enabled if I accept the terms in
License Agreement checkbox is checked
NSC.IN.15
End-User License Agreement Screen should

provide Print, Back, Next, Cancel button
NSC.IN.16
Clicking Next in End-User License Agreement

Screen, should take to Destination Folder screen
NSC.IN.17
Destination Folder screen should provide Change,

Back, Next , Cancel button
NSC.IN.18
In Destination Folder Screen, click Change button

to select the Destination folder to install the
Netsnapper
NSC.IN.19
After selecting folder in Destination Folder screen,

click Next to go Ready to install Netsnapper Client
screen
NSC.IN.20
Ready to install Netsnapper Client screen should

provide Back, Install, Cancel button
NSC.IN.21
Should click Install in Ready to install Netsnapper

Client screen to start the Installation
NSC.IN.22
After clicking Install in Ready to install Netsnapper

Client screen , you will be asked to finish installation
process
NSC.IN.23
Click ok button in Finish installtion Process

window which displays Nestsnapper Client Setup
Wizard ended prematurely window
NSC.IN.24
Nestsnapper Client Setup Wizard ended

prematurely window should provide Disabled Back,
Cancel button and Enabled Finish button
NSC.IN.25
Click Finish in Nestsnapper Client Setup Wizard

ended prematurely window to complete installation
process
NSC.IN.26
Should create an exe installer for the Netsnapper

client application, which should be used to start the
netsnapper installation
APPLICATION
NSC.IN.27
NSC.AP
Netsnapper Client application should have two

tabs : Connection and Settings before it is logged in
NSC.AP.01
Netsnapper Client application should have three

tabs : Connection, Dashboard and Settings once
the Logon botton is clicked
NSC.AP.02
Netsnapper Application on start up should provide

the Icon and Name as "Netsnapper Client for
Windows 7" in the Top Left corner
NSC.AP.03
The Netsnapper application should provide the

close button at the top right corner
NSC.AP.04
Editing the already existing data in any tab should

not allow user to navigate to any other tab
NSC.AP.05
User can navigate to other tabs only after Applying

the changes or undo the changes
NSC.AP.06
Closing the application should minimize the

application to tray
NSC.AP.07
Firewall Tab , Connect on Start & Use Wi-fi

manager in Options Tab should be displayed only
after the successful connection establishment for
the first time after being installed
NSC.AP.08
String changes from "Connection Info" to

"Connection" and "Accounting Info" to "Dashboard"
NSC.AP.09
Forgot Password option should be available to get

the account password to registered mail id
NSC.AP.10
Select Forgot Password option and once the

password has been sent successfully, the
application should show the message "Password
has been sent successfully to your registered mail
id"
NSC.AP.11
While forgot password option is selected, if the

username doesnt exist in the registry, the
application should show the error message "Invalid
Username."
NSC.AP.12
While forgot password option is selected, if there is

no internet connectivity, application should show the
error message "Connection impossible (no
available route via network device found)"
NSC.AP.13
While forgot password option is selected, if the

server/host ip is invalid, the application should show
the error message "Server Unreachable"
The Netsnapper application user interface should
be updated with the Latest Ux Design
NSC.AP.14
NSC.AP.15
Connect, "Disconnect", "Forgot Password" and

"Cancel" button should be made invisible if "Forgot
Password" button is clicked and make visible after
Forgot Password response is received from MAM.
NSC.AP.16
"Forgot Password" button should be made invisible

when the connect button is clicked and should be
made visible and enabled only in Disconnected
state
NSC.AP.17
Forgot password request should be made similar to

connect request.(i.e) Hello, Mode and Authenticate
message should be sent and new request and
response xml should be created for Forgot
password
NSC.AP.18
While the connect option is selected, if the user's

subscription has been expired, then the application
should show the error message "Your subscription
has been expired"
NSC.AP.19

trial subscription has been expired, then the
application should show the error message "Your
trial subscription has been expired"
NSC.AP.20

premier subscription has been expired, then the
application should show the error message "Your
premier subscription has been expired"
NSC.AP.21
The Font type of the Netsnapper application should

be "Trebuchet MS"
NSC.AP.22
SETTINGS TAB
NSC.SE
Settings Tab should have the following five tabs :

Credentials, Interfaces, Profiles, Firewall, Options
NSC.SE.01
Application should highlight the Tab being selected
NSC.SE.02
Credentials Tab
NSC.SE.CR
Application should provide a dropdown list for Server
NSC.SE.CR.01
Application should provide a text box for Host, Port ,

User and Password
NSC.SE.CR.02
Application should provide a checkbox for

Remember password
NSC.SE.CR.03
Application should provide a connect button
NSC.SE.CR.04
Application should provide Apply and Undo button
NSC.SE.CR.05
On selecting a server from server list, server

configuration such as host and port should be filled
by default
NSC.SE.CR.06
On selecting a server from server list, Host and Port

fields should be disabled
NSC.SE.CR.07
Provide custom option in server list dropdown box

to enter new server configurations
On selecting custom option application should allow
user to enter host
On selecting custom option application should allow
user to enter port
NSC.SE.CR.08
NSC.SE.CR.09
NSC.SE.CR.10
There should be Connect button to connect the

client to server
NSC.SE.CR.11
On successful connection with NSServer, connect

button should be changed to DisConnect button to
disconnect client from the server.
NSC.SE.CR.12
Should click Cancel button to interrupt the

connection process
NSC.SE.CR.13
Application should provide a check box for

remembering the password to avoid entering
password in subsequent connections.
NSC.SE.CR.14
Click Apply button to save the new configurations of

the connection data and send them to Netsnapper
core
NSC.SE.CR.15
Connect button should be disabled if the data is

changed and saved in any of the following : Server,
Host, Port, Username, Password
NSC.SE.CR.16
Apply and Undo button should be enabled if the

data is changed in any of the following : Server,
Host, Port, Username, Password
NSC.SE.CR.17
Connect button should be enabled if the already

available data is not changed in any of the following
: Server, Host, Port, Username, Password
NSC.SE.CR.18
Apply and Undo button should be disabled if the

already available data is not changed in any of the
following : Server, Host, Port, Username, Password
NSC.SE.CR.19
Application should maintain already connected

server configuration info in server list
NSC.SE.CR.20
If the Host field is empty, the notification "Incorrect

host" should be displayed at the bottom left corner
NSC.SE.CR.21
If the Port field is empty, the notification "Incorrect

port number" should be displayed at the bottom left
corner
NSC.SE.CR.22
If the Host and Port is entered and only username

is empty, the notificcation "Incorrect user name"
should be displayed at the bottom left corner
NSC.SE.CR.23
Giving URL in Host field should be accepted
NSC.SE.CR.24
Interfaces Tab
NSC.SE.IN
Should list the currently available interfaces
NSC.SE.IN.01
Available interfaces should be ordered by interface

priorities
NSC.SE.IN.02
Application should provide Up and Down button to

move the position of interfaces
NSC.SE.IN.03
NSC.SE.IN.04
Priorities can be adjusted manually by selecting the

interface and moving up or down
NSC.SE.IN.05
Interface which is in the top position must have

Highest Priority
Interface which is in the bottom position must
have lowest Priority
Application should provide check box for Show
hidden devices
Application should provide Apply button to save the
order of the list of interface priority and send it to
Netsnapper core
Should click Undo button to cancel all the changes
in the list
Should display the number of assigned profiles
within brackets
The state icon should be displayed after the
interface name representing the state of the
interface.
Dialing icon should be shown when Netsnapper
client tries to dial interface to connect through it or
to rise it as backup
Disabled icon should be shown when interface is
disabled and it is impossible to establish connection
through it
Hidden icon is shown when interface is disabled
and hidden from the interface list
Locked icon should be shown when the interface is
locked and connection is possible only through this
interface
NSC.SE.IN.06
NSC.SE.IN.07
NSC.SE.IN.08
NSC.SE.IN.09
NSC.SE.IN.10
NSC.SE.IN.11
NSC.SE.IN.12
NSC.SE.IN.13
NSC.SE.IN.14
NSC.SE.IN.15
NSC.SE.IN.16
Unavailable icon should be shown when interface is

unavailable for connection establishment
Used by the system icon should be shown when the
connection is made through the system profiles
instead of Netsnapper profiles
Used by the system icon should also be shown for
profiles received from MAM side
NSC.SE.IN.17
NSC.SE.IN.18
NSC.SE.IN.19
Used for backup icon should be shown when

interface is selected to be used as backup for
switching to backup tunnel when primary tunnel is
disconnected.
NSC.SE.IN.20
On unchecking the Show hidden devices checkbox

interfaces with hidden status from the list should be
removed
NSC.SE.IN.21
On checking the Show hidden devices checkbox

interfaces with hidden status from the list should be
shown
NSC.SE.IN.22
On double clicking the left mouse button over the

interface or clicking the arrow button should open
its own interface settings
Interface settings should provide a check box for
Use custom name
Checking the Use custom name checkbox should
make the text box active and be able to enter a
more convenient name
Application should provide check boxes for
Disabled, Locked, Used for Backup and Hidden
Ticking the Locked checked box should bring up the
lock status
As soon as an available interface is locked,
Netsnapper client should not try to switch to other
interface untill it is unlocked
When the needed interface is locked, the previous
locked interface should be unlocked
NSC.SE.IN.23
NSC.SE.IN.24
NSC.SE.IN.25
NSC.SE.IN.26
NSC.SE.IN.27
NSC.SE.IN.28
NSC.SE.IN.29
check the Disabled check box to disable interface

and exclude it from the list of interfaces being used
NSC.SE.IN.30
Check Used for backup check box to allow using an

interface as a reserve connection in case the
current connection is lost.
NSC.SE.IN.31
The backup tunnel should be established with the

next interface by priority, when the Used for backup
checkbox is turned on
Check the Hidden checkbox to remove disabled
interface from the Interface list
Profile field should display all profiles, created with
help of Profiles tab or received from the server side
Each profile should provide a checkbox to select
the profile
If the force settings use only original profiles
obtained from the server side, other profiles created
by the user should be ignored.
NSC.SE.IN.32
NSC.SE.IN.33
NSC.SE.IN.34
NSC.SE.IN.35
NSC.SE.IN.36
Application should provide Undo and Ok button

below the Profiles field
Clicking the Ok button, should save the changes in
profiles field
Clicking the Undo button, should return to the
previous page without changes
in the Interfaces Tab
Clicking the Apply button,should save the new
configuration of the interface and send them to the
Netsnapper Core
Clicking the Undo button, should cancel all the
changes
NSC.SE.IN.37
NSC.SE.IN.38
NSC.SE.IN.39
NSC.SE.IN.40
NSC.SE.IN.41
NSC.SE.IN.42
The Up button should be disabled when the top

interface is selected
NSC.SE.IN.43
The Down button should be disabled when the

bottom interface is selected
NSC.SE.IN.44
Both Up and Down button should be disabled when

there is only one interface
NSC.SE.IN.45
For the selected interface, the Hidden checkbox

should be enabled only if the Disabled checkbox is
checked.
Editing made for the interface must be saved or
undone inorder to navigate to the other tabs
Application should highlight the corresponding
interface icon, when it becomes available
Application should not highlight the corresponding
interface icon, when it becomes unavailable
Profiles Tab
Profiles Tab should provide Up and Down button to
move the selected interfaces up or down
NSC.SE.IN.46
NSC.SE.IN.47
NSC.SE.IN.48
NSC.SE.IN.49
NSC.SE.PR
NSC.SE.PR.01
Profiles Tab should provide Apply and Undo button
NSC.SE.PR.02
Click on the Apply button to save the new order of

the priority list and send it to the Netsnapper Core
NSC.SE.PR.03
To cancel all changes click on the Undo button
NSC.SE.PR.04
The number of profiles configured for each network

type(WLAN, VPN, DUN) should be displayed in
brackets.
NSC.SE.PR.05
If the Netsnapper Client obtains the forced settings

from the server-side, the priority of the networks is
determined automatically and the user cannot
change it.
NSC.SE.PR.06
Select the interface and Double click with the left

mouse button or click on the button with arrow to
add/remove the profiles and change its priority
NSC.SE.PR.07
To add a new profile click on the Add button.

Depending on the chosen type of network (WLAN,
VPN or DUN) fill in all required fields on the opened
page
NSC.SE.PR.08
To save the created profile click on the Ok button
NSC.SE.PR.09
To cancel all changes in created profile, click the

Undo button
To return to the previous page without changes click
on the Back button
To delete the created profile choose it and click on
the Remove button.
You could change the priority of profiles.Should use
buttons Up and Down to change. The upper profile
should be higher by the priority.
To modify existing profile, choose it and click on the
arrow button. Make required modifications and click
on the Ok button
in the Profiles Tab
On clicking the Apply button newly created
profile,changes in the priority list of the profiles
should be sent to NEtsnapper Core
NSC.SE.PR.10
NSC.SE.PR.11
NSC.SE.PR.12
NSC.SE.PR.13
NSC.SE.PR.14
NSC.SE.PR.15
NSC.SE.PR.16
To cancel all changes, click on the Undo button
NSC.SE.PR.17
Netsnapper Client can obtain the force Profiles

settings from the server-side, which forbid the user
to add profiles, remove it and change their priority
NSC.SE.PR.18
If such forced settings is obtained, all profiles

created by the user should be ignored by the
connection establishment
Profiles creation for LAN network type should be
impossible.
There should be Profile name field to enter the
name of the profile
There should be SSID field to enter the Service Set
Identifier of the access point into this field.
Application should provide Authentication type field
to choose the authentication type of the access
point in the drop-down list containing : open,
shared, WPA, WPAPSK, WPA2, WPA2PSK
Application should provide Encryption field to
choose the encryption method depending on the
chosen authentication type
Application should provide Apply, Undo and Back
button in the WLAN Profile
NSC.SE.PR.19
NSC.SE.PR.20
NSC.SE.PR.21
NSC.SE.PR.22
NSC.SE.PR.23
NSC.SE.PR.24
NSC.SE.PR.25
Clicking the Ok button,should save the created or

changed profile
NSC.SE.PR.26
Clicking the Undo button,should cancel all changes
NSC.SE.PR.27
Clicking the Back button, should return to the

There should be predefined System-defined VPN
Interface profile in the VPN profiles list
System-defined VPN Interface profile should allow
choosing VPN type of network connection and
could not be deleted
NSC.SE.PR.28
NSC.SE.PR.29
NSC.SE.PR.30
To return to the previous page without changes

VPN type drop-down list with values : ANY, PPTP,
L2TPIPSec and PPPoE.
NSC.SE.PR.31
Application should provide ANY option , choosing it

should select the first available VPN network
connection for connection establishment.
NSC.SE.PR.32
Application should provide option to create new

VPN profile
Application should provide Profile name field to
enter the name of the profile
Application should provide Host field to enter the
name of the VPN's host
Application should provide drop-down list for
protocol type
Application should provide username field to enter
the user name
Application should provide password field to enter
the password
Application should provide Apply, Undo and Back
button in the VPN Profile
changed profile
NSC.SE.PR.33
NSC.SE.PR.34
NSC.SE.PR.35
NSC.SE.PR.36
NSC.SE.PR.37
NSC.SE.PR.38
NSC.SE.PR.39
NSC.SE.PR.40
NSC.SE.PR.41

NSC.SE.PR.42
If system VPN connection has been already

established, then launch the Netsnapper application
and try to connect via VPN, Netsnapper tunnel
should be created through the existent system VPN
connection.
NSC.SE.PR.43
Application should provide option to create new

profile of the DUN
Application should provide Name field to enter the
convenient name to the new profile
Application should provide Phone # field to enter
the number of the telephone by which the
connection is implemented.
Application should provide Access point name field
to enter the access point name
Application should provide check box for Modem
init string to enter init string instead of apn
NSC.SE.PR.44
NSC.SE.PR.45
NSC.SE.PR.46
NSC.SE.PR.47
NSC.SE.PR.48
When the modem init string checkbox is checked,

then modem init field should be enabled and apn
field should be disabled
Application should provide Username Field to enter
the user name
Application should provide Password Field to enter
the password
Application should provide Ok, Undo and Back
button in the DUN Tab
changed profile
in the Profiles Tab
NSC.SE.PR.49
NSC.SE.PR.50
NSC.SE.PR.51
NSC.SE.PR.52
NSC.SE.PR.53
NSC.SE.PR.54
NSC.SE.PR.55
NSC.SE.PR.56
Clicking the Apply button, should save the created

profiles and send them to the Netsnapper Core
NSC.SE.PR.57
NSC.SE.PR.58
The Up button should be disabled when the top

profile is selected
The Down button should be disabled when the
bottom profile is selected
Both Up and Down button should be disabled when
there is only one profile
Firewall Tab
NSC.SE.PR.59
NSC.SE.PR.60
NSC.SE.PR.61
NSC.SE.FW
Netsnapper Client can obtain granted services from

the server-side
NSC.SE.FW.01
If Netsnapper Client obtains the forced settings

from the server-side, the granted services created
by the user should be ignored
NSC.SE.FW.02

from the server-side, the user should not be able to
add new or removed obtained services.
NSC.SE.FW.03

from the server-side, all buttons in the Firewall Tab
should be inactive
NSC.SE.FW.04
To remove one of the created services, click on

them with left mouse button and then click on the
Remove button
NSC.SE.FW.05
To add new granted service, click on the Add button
NSC.SE.FW.06
Application should provide Service Name Filed to

enter the name of the new service
Application should provide Port field to enter the
port number
NSC.SE.FW.07
NSC.SE.FW.08
The Service name should be mandatory
NSC.SE.FW.09
The Port field should be mandatory
NSC.SE.FW.10
Application should display warning when the

Service name is not entered.
Application should display warning when the Port is
not entered.
Application should provide drop-down list to choose
the protocol you need.There are two possible
protocols: TCP and UDP.
Application should provide Back, Ok, Apply and
undo button in the Firewall Tab
The ok, Undo, Apply button should be disabled
when any of the field is not entered
Application should provide option to choose the
traffic direction in the drop-down list. It could be
outgoing or incoming.
changed profile
NSC.SE.FW.11
NSC.SE.FW.12
NSC.SE.FW.13
NSC.SE.FW.14
NSC.SE.FW.15
NSC.SE.FW.16
NSC.SE.FW.17
NSC.SE.FW.18

NSC.SE.FW.19
Clicking on the Apply button, should save the new

granted service and send them to the Netsnapper
Core
NSC.SE.FW.20
NSC.SE.FW.21
Options Tab
From the server side,Netsnapper Client can
receive the forced settings. In this case the needed
check boxes will be marked and cannot change its
status.
NSC.SE.OP
Application should provide Language Drop down list
NSC.SE.OP.01
NSC.SE.OP.02
Language option should be used to switch between

different languages. Language selection will affect
Netsnapper Client interface only.
NSC.SE.OP.03
Language drop down list should provide languages

like : English, Deutsch, Malay, Italiano etc.. and
cannot be empty
NSC.SE.OP.04
Application should provide Checkbox for Keep alive

mode, Start UI Agent on OS Start, Connect in start,
Use Wifi Manager
NSC.SE.OP.05
Application should provide Start UI Agent on OS

start checkbox to enable or disable start of the
Netsnapper Client UI on the OS start
NSC.SE.OP.06
Connect on OS start option should be used to

connect the Netsnapper Core automatically to the
server on OS start
NSC.SE.OP.07
To connect Netsnapper Core automatically to the

server on OS start , the program should remember
username and password to make automatic
connection
NSC.SE.OP.08
If user turn on the option Connect on OS start the

check box Remember Password on the Connection
Data window will be marked automatically and it
should be impossible to change its status
NSC.SE.OP.09
There should be wireless manager to operate

wireless cards installed on user computer so as to
provide automatic authentication on available
access point(s).
NSC.SE.OP.10
Application should provide Encryption level option

to change the encryption level of the connection
NSC.SE.OP.11
Application should provide drop down list for

encryption level with values : ANY, LOW, MEDIUM,
HIGH
NSC.SE.OP.12
Application should provide Apply button and Undo

button
Clicking the Apply button, should save the new
parameters of the connection data and send them
to the Netsnapper ore
Clicking on the Undo button, should cancel all
changes
If all general settings are forced from the serverside the buttons Apply and Undo should be inactive
CONNECTION TAB
Errors notified by Netsnapper Core should be
displayed in the Last Notification field of Connection
tab
NSC.SE.OP.13
NSC.SE.OP.14
NSC.SE.OP.15
NSC.SE.OP.16
NSC.CO
NSC.CO.01
Open related page button should be disabled when

there is no error
NSC.CO.02
Open related page button should be enabled when

there is an error message and used to fix the
problem
NSC.CO.03
The Connection tab should display the status of the

connection such as
connecting,connected,disconnected and switching
NSC.CO.04
The Connection tab should be available only if the

corresponding permissions will be obtained from
the server-side
NSC.CO.05
If permissions were not received from the serverside, you should not be able to see Connection tab
NSC.CO.06
Next to the status info icon, the icon

should be
displayed to mean that all traffic is compressed
NSC.CO.07
This icon
should be enabled only if Netsnapper
TCP connection protocol is used by the Client to
establish connection and compression is turned ON
on the server side.
NSC.CO.08
denotes Netsnapper Client is connected using

Netsnapper TCP connection protocol. Compression
is turned off. Or Netsnapper Client is connected
using Plain TCP connection protocol.
NSC.CO.09
Next to the status info icon, the icon

should be
displayed to mean that the encryption is turned on
NSC.CO.10
The icon
should be enabled only if Netsnapper
TCP connection protocol is used by the Client to
establish connection and any encryption level (low,
medium or high) is selected on the client side or on
the server side.
NSC.CO.11

Netsnapper TCP connection protocol. Encryption is
turned off. Or Netsnapper Client is connected using
Plain TCP connection protocol.
NSC.CO.12
This icon
should be enabled only if Plain UDP
connection protocol is used by the Client to
establish connection.
NSC.CO.13

Netsnapper TCP or Plain TCP connection protocol.
NSC.CO.14
Connect button should be available to connect

Netsnapper Client to the Server
NSC.CO.15
Disconnect button should be available to abort the

connection
NSC.CO.16
Cancel button should be available to interrupt the

connection process
NSC.CO.17
On clicking the open related page button,user

should be taken to specific window where error has
occurred
NSC.CO.18
Application should provide the following details

below the status : Session
duration,Optimized/actual download speed,
Optimized/actual up speed
NSC.CO.19
Application should provide the following details in

the connection tab : Current user, Current server,
Current interface, Current profile, Backup server,
Backup interface, Backup profile, Server Virtual IP,
client virtual IP
NSC.CO.20
The Netsnapper icon below the Connection should

be indicated as unhighlighted in black & white when
disconnected, highlighted in blue when connected,
highlighting in green colour when connecting,
highlighting in yellow when switching
NSC.CO.21
The Netsnapper status indication should be

reflected in the tray icon
NSC.CO.22
Doulbe clicking the tray icon should restore the

netsnapper client with same tab while it was closed
NSC.CO.23
Right clicking the netsnapper tray icon should show

the menu with the following options : Simple UI
mode, Monitor, Disconnect when the client is in
connected state/Connect when the client is in
disconnected state, About, Options, Show All
Windows, Hide,Quit
NSC.CO.24
Clicking Exit from the tray icon menu should prompt

the Netsnapper client popup window with the
message "Do you want to exit the Netsnapper UI
Agent?" and also provide Yes and No buttons
NSC.CO.25
clicking Yes button in the Netsnapper client popup

window should Exit the application and remove icon
from the tray
Clicking No button should close the netsnapper
client popup window
NSC.CO.26
NSC.CO.27
Clicking About option from the tray icon menu

should provide About window in netsnapper client
with the Netsnapper icon, name, Version no, Build
no, organisation name and ok button at the bottom
NSC.CO.28
Clicking ok button in the About window should

display the previously displayed window
NSC.CO.29
Clicking connect button in the tray icon menu

should make the client to connect to the server
NSC.CO.30
Clicking disconnect button in the tray icon menu

should make the client to disconnect to the server
NSC.CO.31
The Monitor option in the tray icon menu should

contain the submenu with the options : Connection ,
Dashboard, Settings
NSC.CO.32
Clicking the Connection from the Monitor submenu

should display the Connection window in the
netsnapper client
NSC.CO.33
Clicking the Dashboard from the Monitor submenu

should display the Dashboard window in the
netsnapper client
NSC.CO.34
The Settings option in the Monitor submenu should

contain the following options : Credentials,
Interfaces, Profiles, Firewall, Options
NSC.CO.35
Clicking the Credentials option from the Settings

submenu of Monitor submenu should display the
Credentials window in the netsnapper client
NSC.CO.36
Clicking the Interfaces option from the Settings

Interfaces window in the netsnapper client
NSC.CO.37
Clicking the Profiles option from the Settings

Profiles window in the netsnapper client
NSC.CO.38
Clicking the Firewall option from the Settings

Firewall window in the netsnapper client
NSC.CO.39
Clicking the Options option from the Settings

Options window in the netsnapper client
NSC.CO.40
Clicking the simple UI mode should display the

Connection summary window with the Following :
Netsnapper status indicator icon, status and below
the status : Current interface, Optimized/actual
down traffic,Optimized/actual up traffic
NSC.CO.41
In Simple UI Mode , the connection summary

window should provide the following fields in the
Connection data Field : Server dropdown list,Host,
Port, User, Password, Check box for Remebering
password, Apply button and Undo button
NSC.CO.42
In Simple UI Mode , the connection summary

window should provide the Last notification field to
display the notifications
NSC.CO.43
DASHBOARD TAB
NSC.AC
The Dashboard tab should show traffic statistics for

the current session, day, week, month or total
statistics for every interface.
NSC.AC.01
Application should provide dropdown list for

Interface
NSC.AC.02
Application should provide dropdown list for Period
NSC.AC.03
Application should provide option to select the

period from Period drop down list to access
accounting info for that period
NSC.AC.04
Should select the interface from Interface drop

down list to access accounting info for that interface
NSC.AC.05
The Dashboard tab should be available only if the

corresponding permissions will be obtained from
the server-side
NSC.AC.06
The x-axis of the graph should denote the size in

KB
NSC.AC.07
Application should provide two different coloured

bar to differentiate Actual and Compressed data
NSC.AC.08
The Bar graph should be represented for both Sent

and received data with the compression rate
respectively
NSC.AC.09
Application should provide the Reset button to

cancel statistic data for the chosen interface and
period
NSC.AC.10
Confirm data deletion should be done after reset

button is clicked
STATUS VISUALIZATION
NSC.AC.11
NSC.ST
Netsnapper is connecting to the Server
NSC.ST.01
Netsnapper is launching
NSC.ST.02
Netsnapper is disconnected from the Server
NSC.ST.03
Netsnapper is disconnecting from the Server
NSC.ST.04
Netsnapper is not connected. Error.
NSC.ST.05
Netsnapper is in switching state
NSC.ST.06
Netsnapper is waiting
NSC.ST.07
Netsnapper is connected to the Server via

LAN
NSC.ST.08

WLAN
NSC.ST.09

DUN
NSC.ST.10

VPN
NSC.ST.11
Environmental Requirements
Hardware Requirements
Client machine provide minimum 15MB of free
space on Hard Disk Drive
Client machine should provide installed and
configured network connection (with a LAN card,
PCMCIA network adapter, modem etc.)
Software Requirements
NSC.HR
NSC.HR.01
NSC.HR.02
NSC.SR
Client machine should have any of the following

Operating System: Windows XP SP2, SP3,
Windows Vista, Windows7
NSC.SR.01
Client machine should have any of the following

Operating System: Windows XP SP2, SP3,
Windows Vista, Windows7, 8, 8.1 and 10
NSC.SR.02
Performance Requirements
Memory Requirements
Client machine should provide minimum 128MB of
RAM
NSC.MR
NSC.MR.01
onal trace of the managed requirements.

By chosing appropriate 'customised auto-filter option', one
CLICK
equirements satiesfied
HERE by design document section x.y or Source file f.c.
-
REQUIREMENT ID - 'Impact?
Analysis'
Auto Log Update Off
Design -- LLD (description or

reference to design document with
exact section)
(\\chent032\Netsnapper\WORK\d
ocs\Design Document\NSClient\Netsnapper_Client_dd01/
10)
Source Code (description or reference to code file with

exact section)
(Revision/Issue No.)
napiInit(),napiFinal() methods in napi.cpp

Section 3.2.4.2
_napiOpenAccess(),_napiCloseAccess(),_napiPostMessag
e(),_napiRegisterCallback() in napi_main.cpp
napi_manager.cpp
ApplyConnectionData () , SetConnectionData () method in

nsclient_state_controller.cpp
Section 3.2.4.1
Section 3.2.4.1
Section 3.2.4.1
wx_check_list.cpp
wx_check_list.cpp
Section 3.2.4.1
nsclient_actions.cpp
SetControlsToUnconfiguredState()
wx_base_controls.cpp
nsPasswordEdit()
Section 3.2.3.8
CommandForgotPassword()
Section 3.2.4.1

Section 3.2.4.1

ApplyConnectionData () , SetConnectionData ()
method in nsclient_state_controller.cpp
Section 3.2.4.1
CreateFrame(),CreateComponent(),CreateMenu() methods
of wx_factory.cpp
SettingsPage_ApplyButtonClick() method in
nsengine_configurator.cpp
Section 3.2.4.1
Section 3.2.4.1
Section 3.2.4.1

Section 3.2.4.1
of wx_factory.cpp
Section 3.2.4.1
Section 3.2.4.1
Section 3.2.4.1
wx_connection_status.cpp
ConnectionDataPanel_Connect() method in
CommandConnect() method in nsclient_state_controller.cpp
of wx_factory.cpp
nsclient_state_controlle.cpp
Section 3.2.4.1
ApplyDeviceToPage(),ApplyPageToDevice(),ApplyLockedC
heckboxEnabled in wx_nid_manager.cpp
Section 3.2.4.1
connection_manager.cpp, interface_manager.cpp,
tunnel_manager.cpp
CreateTunnelsForDevice(),CreateTunnelsForAllActiveDevic
es() in tunnels_controller.cpp
Section 3.2.4.1
Section 3.2.4.1
SetTunnelUseForBackup(),ExtractPrimaryTunnelInfo(),Extra
ctBackupTunnelInfo() in tunnel_pool.cpp
SetUseForBackup(),SetTunnelActive() in tunnel.cpp
OnTunnelConnectionLost(),OnTunnelDropped(),DestroyTun
nelsForDevice() in tunnels_controller.cpp
ExtractBackupTunnelInfo(),ActivateTunnel(),DestroyTunnel(
) in tunnel_pool.cpp
SetTunnelActive() in tunnel.cpp
Section 3.2.4.1
TunnelsActivateBestTunnel(),TunnelsDisconnectUseless()()
in tunnels_controller.cpp
Section 3.2.4.1
Open(),close(),mode(),authenticate() in Connection.cpp
Section 3.2.4.1
Section 3.2.4.1
CreateTunnelsForDevice(),CreateTunnelsForAllActiveDevic
es() in tunnels_controller.cpp
Section 3.2.4.1
Section 3.2.4.1
OnInterfacesChanged() in if_processor.cpp
CreateTunnel (),ConnectTunnels (),ActivateTunnel
(),DestroyUselessTunnels (),DestroyTunnel
(),DestroyAllTunnels (),GetTunnelConnectionAddress () in
tunnel_pool.cpp
StartConnection(),MakeConnectionActive(),SetTunnelActive
() in tunnel.cpp
EstablishConnection(),CloseConnection(),ResetConnection(
) in raw_connection.cpp
Tunnels_Controller.cpp
OnTunnelRecievedDisconnectSignal()
SetConnectionMode() in raw_connection.cpp
Section 3.2.4.2
cert_utils.cpp
SetCertificates() in src\cpp\client\driver\tunnel\common\
Socket.cpp
Negotiate() in SslSocket.cpp
Section 3.2.4.2
Tunnel.cpp
EstablishTunnelConnectionUnderLock()
Section 3.2.4.2
SetIMEI(),GetIMEI() in modem.cpp
Section 3.2.4.2
Tunnel.cpp
EstablishTunnelConnectionUnderLock()
radius_client.c
radius_client_init_acct()
Section 3.2.4.2
Tunnel.cpp
TunnelRequestMamConfigurations()
Section 3.2.4.2
radius_client.c
radius_client_init_acct()
Section 3.2.4.2
ras_phonebook_entry.cpp
InitVpnEntry()
nsprotocol_to_mam_config.cpp
ApplyVpnProfileList
Section 3.2.4.3
TreckAdapter.cpp
open()
Section 3.2.4.3
TreckAdapter.cpp
open()
connection.cpp
open()
Section 3.2.4.3
connection.cpp
open()
QueueProtocolPacket()
Section 3.2.4.3
connection.cpp
ReceiveProtocolPacket()
Section 3.2.4.3
BioSocket.cpp, SslSocket.cpp, ZLibSocket.cpp,

src\cpp\client\driver\openssl
Section 3.2.4.3
tunnel.cpp
TunnelAuthenticate()
connection.cpp
Authenticate()
Section 3.2.4.3
connection.cpp
ReceiveProtocolPacket()
Section 3.2.4.3
TreckSocket.cpp
send()
connection.cpp
QueueProtocolPacket()
Section 3.2.4.3
SslSocket.cpp
send()
Section 3.2.4.3
ZLibSocket.cpp
send()
Section 3.2.4.3
BufferedSocket.cpp
send()
TrectSocket.cpp
send()
Section 3.2.4.3
TrectSocket.cpp
send()
Section 3.2.4.3
BufferedSocket.cpp
send()
TrectSocket.cpp
send()
Section 3.2.4.3
BufferedSocket.cpp
receive()
TrectSocket.cpp
receive()
Section 3.2.4.3
TrectSocket.cpp
receive()
Section 3.2.4.3
BufferedSocket.cpp
receive()
TrectSocket.cpp
receive()
Section 3.2.4.3
SslSocket.cpp
receive()
Section 3.2.4.3
ZLibSocket.cpp
receive()
Section 3.2.4.3
BufferedSocket.cpp
send()
TrectSocket.cpp
send()
Section 3.2.4.3
OnTunnelDropped(),OnTunnelRedirect(),ActiveDeviceAppe
ared(),ActiveDeviceDisappeared(),CreateTunnelsForDevice
(),DestroyTunnelsForDevice(),OnTunnelConnectionLost in
tunnels_controller.cpp
Section 3.2.4.3
Section 3.2.4.3
Section 3.2.4.3
Section 3.2.4.3
Section 3.2.4.3
tunnel_pool.cpp
() in tunnel.cpp
tunnel_pool.cpp
() in tunnel.cpp
OnTunnelDropped(),OnTunnelRedirect(),ActiveDeviceAppe
ared(),ActiveDeviceDisappeared(),CreateTunnelsForDevice
(),DestroyTunnelsForDevice(),OnTunnelConnectionLost in
UpButtonClick(),DownButtonClick(),SetComponentEnabled
UpButton(),SetComponentEnabledDownButton in
wx_nid_manager.cpp
Section 3.2.4.3
GetNicOrderList(),SetNicOrderList() in
wx_nid_manager.cpp
Section 3.2.4.3
Section 3.2.4.3
Section 3.2.4.3
ApplyDeviceToPage(),ApplyPageToDevice() in
wx_nid_manager.cpp
Section 3.2.4.3
Section 3.2.4.3
ReconfigureMenus() method in nsclient_actions.cpp
Section 3.2.4.3
State_GeneralSettings() in nsclient_actions.cpp
GetForceCompression () in nsclient_state_controller.cpp
Section 3.2.4.3
ZLibSocket.cpp
send()
Section 3.2.4.3
ZLibSocket.cpp
send()
Section 3.2.4.3
ZLibSocket.cpp
send()
Section 3.2.4.3
Section 3.2.4.3
SetComponentRect(),DrawChart() in wx_chart.cpp
State_AccountingInfo() in nsclient_actions.cpp
GetAccountingDeviceName () in
Section 3.2.4.3
src\cpp\client\driver\zlib\
Section 3.2.4.3
GetForceEncryptionLevel () in nsclient_state_controller.cpp
Section 3.2.4.3
wlan_profile.cpp
SetEncrData()
Section 3.2.4.3
device_processor.cpp
ConnectUsingBruteForce()
Section 3.2.4.3
Section 3.2.4.3
Section 3.2.4.3
Section 3.2.4.3
Section 3.2.4.3
src\cpp\client\driver\openssl\windows\
Section 3.2.4.3
Section 3.2.4.3
Section 3.2.4.3
SslSocket.cpp
Negotiate()
SslSocket.cpp
Negotiate()
SslSocket.cpp
Negotiate()
Section 3.2.4.3
Section 3.2.4.1
SslSocket.cpp
Negotiate()
multiplexer_wrapper.cpp
src\cpp\client\core\tunnel_manager\ioctl_wrappers\windows\
desktop \vnet_wrapper.cpp
Section 3.2.4.1
interface_scanner.cpp, if_processor.cpp,
device_scanner.cpp
Section 3.2.4.1
trqosnd.c
qossend()
Section 3.2.4.1
ApplyVnetMacAddress() method in tunnel_manager.cpp

src\cpp\client\core\tunnel_manager\ioctl_wrappers\windows\
desktop \vnet_wrapper.cpp
Section 3.2.4.1
Miniport.cpp
Section 3.2.4.1
wx_nid_manager.cpp
Section 3.2.4.1
wx_nid_manager.cpp
Section 3.2.4.3
ChangeInterfaceConfiguration
Section 3.2.4.3
TunnelsActivateBestTunnel(),TunnelsDisconnectUseless()()
in tunnels_controller.cpp
Section 3.2.4.3
src\cpp\client\core\sim_manager
Section 3.2.4.1
Section 3.2.4.1
Section 3.2.4.1
Section 3.2.4.1
of wx_factory.cpp
ApplyConnectionStatus() method in
of wx_factory.cpp
of wx_factory.cpp
Section 3.2.4.1
Section 3.2.4.1
Section 3.2.4.1
Section 3.2.4.1
Section 3.2.4.1
Section 3.2.4.1
Section 3.2.4.1
Section 3.2.4.1
Section 3.2.4.1
of wx_factory.cpp
of wx_factory.cpp
GetDownloadRawSpeed(),GetUploadRawSpeed(),GetDown
loadCompressedSpeed(),GetUploadCompressedSpeed() in
GetAccountingPeriod (),SetAccountingPeriod() in
Section 3.2.4.1
Section 3.2.4.1
ResetAccounting() in nsclient_state_controller.cpp
Section 3.2.4.1
GetAccounting() in nsclient_state_controller.cpp
Section 3.2.4.1
wx_nid_manager.cpp nsclient_state_controller.cpp
Section 3.2.4.1

Section 3.2.4.1

wx_nid_manager.cpp
Section 3.2.4.1
wx_nid_manager.cpp
Section 3.2.4.2
wx_nid_manager.cpp
Section 3.2.4.2
tunnel_pool.cpp
Section 3.2.4.2
wx_nid_manager.cpp
tunnel_pool.cpp
Section 3.2.4.2
wx_nid_manager.cpp
tunnel_pool.cpp
Section 3.2.4.2
wx_nid_manager.cpp
Section 3.2.4.1
Section 3.2.4.1
ApplyDeviceToPage(),ApplyPageToDevice(),ApplyDisableC
heckboxEnabled() in wx_nid_manager.cpp
wx_nid_manager.cpp nsclient_state_controller.cpp
Section 3.2.4.1
wx_nid_manager.cpp
Section 3.2.4.1

Section 3.2.4.1
SetComponentEnabledUpButton(),SetComponentEnabledD
ownButton in wx_nid_manager.cpp
Section 3.2.4.2
Section 3.2.4.2
Section 3.2.4.1
wx_nid_manager.cpp
Section 3.2.4.2
wx_profile_manager.cpp
Section 3.2.4.2
SelectedProfileMoveUp(),SelectedProfileMoveDown() in
Section 3.2.4.1
Section 3.2.4.2
SendSimManagementCmd(),SimButtonState() in
wx_nid_manager.cpp
Section 3.2.4.2
GetNewLocalProfiles(),MergeProfiles() in
Section 3.2.4.1
RemoveSelectedProfile(),AddNewProfile() in
Section 3.2.4.1
Section 3.2.4.1
Section 3.2.4.1
Section 3.2.4.1
Section 3.2.4.1
Section 3.2.4.1
Section 3.2.4.1
Section 3.2.4.1
Section 3.2.4.1
Section 3.2.4.1
Section 3.2.4.1
Section 3.2.4.1
Section 3.2.4.1
Section 3.2.4.1
Section 3.2.4.1
Section 3.2.4.1
Section 3.2.4.1
Section 3.2.4.1
Section 3.2.4.1
Section 3.2.4.1
Section 3.2.4.1
Section 3.2.4.1
Section 3.2.4.1
Section 3.2.4.1
Section 3.2.4.1
Section 3.2.4.1
Section 3.2.4.1
wx_nid_manager.cpp
Section 3.2.4.1
wx_nid_manager.cpp
Section 3.2.4.1
wx_nid_manager.cpp
Section 3.2.4.1
wx_nid_manager.cpp
Section 3.2.4.1
wx_nid_manager.cpp
Section 3.2.4.2
wx_nid_manager.cpp
Section 3.2.4.1
Section 3.2.4.2
Section 3.2.4.1
Section 3.2.4.1
InitFirewallIcons () , GetFirewallIcon () in
ApplyGrantedServicesManagerPage() in
GetUseGrantedServices(),SetUseGrantedServices() in
Section 3.2.4.1
Section 3.2.4.2
Section 3.2.4.1
Section 3.2.4.1
Section 3.2.4.1
Section 3.2.4.1
Section 3.2.4.1
Section 3.2.4.1
Section 3.2.4.1
Section 3.2.4.1
Section 3.2.4.1
Section 3.2.4.1
Section 3.2.4.1
GetForceLanguage() in nsclient_state_controller.cpp
Section 3.2.4.1
GetForceKeepAliveMode () in nsclient_state_controller.cpp
Section 3.2.4.1
GetForceStartOnOsStart () in nsclient_state_controller.cpp
Section 3.2.4.1
GetForceConnectOnStart () in nsclient_state_controller.cpp
Section 3.2.4.1
GetForceWifiManager () in nsclient_state_controller.cpp
Section 3.2.4.1
Section 3.2.4.1
Section 3.2.4.1
Section 3.2.4.1
Section 3.2.4.1
Section 3.2.4.2
State_Update() in nsclient_actions.cpp
GetUpdateVersion() in nsclient_state_controller.cpp
Section 3.2.4.2
Section 3.2.4.2
Section 3.2.4.1
Section 3.2.4.1
GetUpdateDownloaded () in nsclient_state_controller.cpp
Section 3.2.4.1
Section 3.2.4.1
Section 3.2.4.1
Section 3.2.4.1
Section 3.2.4.1
Section 3.2.4.1
Section 3.2.4.1
Section 3.2.3.9
ApplyActiveDevices() in tunnels_controller.cpp
Section 3.2.3.9
ServerList() in tunnel.cpp
Section 3.2.3.9
ApplyMam2Connection() in nsclient_state_controller.cpp
Section 3.2.3.9
Section 3.2.3.9
Section 3.2.3.9
CreateAddressList() in smart_server_address_list.cpp
Section 3.2.3.9
Section 3.2.3.9
EstablishTunnel() in tunnel.cpp
Section 3.2.3.9
Section 3.2.3.9
Section 3.2.3.9
ApplyDomainConfig() in nsprotocol_to_mam_config.cpp
Section 3.2.3.9
ApplyDomainConfig() in nsprotocol_to_mam_config.cpp
Section 3.2.3.9
RememberPrefferedTunnelConnectionAddress() in
Section 3.2.3.9
Section 3.2.3.9
RememberPrefferedTunnelConnectionAddress() in
tunnels_controller.cpp & CreateAddressList() in
smart_server_address_list.cpp
Section 3.2.3.9
TrayIcon_DoubleClick() in nsclient_actions.cpp
Section 3.2.3.9
Section 3.2.3.9
Section 3.2.3.11
Section 3.2.3.11
FillServerHostAndPort() in nsclient_actions.cpp
Section 3.2.3.11
Section 3.2.3.11
Section 3.2.3.11
Section 3.2.3.11
Section 3.2.3.11
Section 3.2.3.1
Section 3.2.3.1
Section 3.2.3.1
Section 3.2.3.12
Section 3.2.3.12
Section 3.2.3.1
Section 3.2.3.1
Section 3.2.3.1
Section 3.2.3.1
Section 3.2.3.12
Section 3.2.3.12
Section 3.2.3.12
ApplyMamConfig() in mam_config_processor.cpp
Section 3.2.3.12
Section 3.2.3.12
Section 3.2.3.12
Section 3.2.3.12
Section 3.2.4.3
PPTPConnect() in network_service_wrapper.cpp
pptp_configurator.cpp
src\cpp\client\driver\tunnel
Section 3.2.4.3
L2TPConnect() in network_service_wrapper.cpp
Section 3.2.4.3
PPPOEConnect() in network_service_wrapper.cpp
Section 3.2.4.3
ConfigureAddress() in TreckAdapter.cpp
src\cpp\client\driver\include\driver\ typedefs.h
Section 3.2.4.3
ConfigureAddress() in TreckAdapter.cpp
src\cpp\client\driver\include\driver\ typedefs.h
Section 3.2.4.3
tfTcpRcvSynOptionsSocImp() in trsocimp.c
Section 3.2.4.1
SetMainFrame()
Section 3.2.4.1
SetMainFrame()
Section 3.2.4.1
SetMainFrame()
Section 3.2.4.1
Section 3.2.4.1
Section 3.2.3.10
TunnelAuthenticate() in tunnel.cpp
Section 3.2.3.10
Section 3.2.3.10
Section 3.2.3.10
Socket.cpp - IsLimitReached()
Section 3.2.3.10
Connection.cpp - ReceiveProtocolPacket(),
SendProtocolPacket()
Section 3.2.3.10
OnTunnelConnectionNotification()
Section 3.2.3.10
Section 3.2.4.2
Section 3.2.4.2
Section 3.2.4.2
GetMessageCodeFirstNode() in
message_code_converter.cpp
Section 3.2.4.2
Section 3.2.4.2
Section 3.2.4.2
Section 3.2.4.2
Section 3.2.4.2
Section 3.2.4.2
Section 3.2.4.2
Section 3.2.4.2
Section 3.2.4.2
Section 3.2.4.2
Section 3.2.4.2
Section 3.2.4.2
Section 3.2.4.2
Section 3.2.4.2
Section 3.2.4.2
Section 3.2.4.2
Section 3.2.4.2
Section 3.2.4.2
Section 3.2.4.2
Section 3.2.4.2
Section 3.2.4.2
Section 3.2.4.2
Section 3.2.4.2
Section 3.2.4.2
Section 3.2.4.2
Section 3.2.4.2
Section 3.2.4.2
Section 3.2.4.2
Section 3.2.4.2
Section 3.2.4.2
Section 3.2.4.2
Section 3.2.4.2
Section 3.2.4.2
Section 3.2.4.2
Section 3.2.4.2
Section 3.2.4.2
Section 3.2.4.2
Section 3.2.4.2
Section 3.2.4.2
Section 3.2.4.2
Section 3.2.4.2
Section 3.2.4.2
Section 3.2.4.2
Section 3.2.4.2
Section 3.2.4.2
Section 3.2.4.2
Section 3.2.4.2
Section 3.2.4.2
Section 3.2.4.2
Section 3.2.4.2
Section 3.2.4.2
Section 3.2.4.2
Section 3.2.4.2
Section 3.2.4.2
Section 3.2.4.2
Section 3.2.4.2
Section 3.2.4.2
Section 3.2.4.2
Section 3.2.4.2
Section 3.2.4.2
Section 3.2.4.2
data_error.cpp
Section 3.2.4.1
win_app.cpp
init()
preinstaller.cpp
Section 3.2.4.1
win_app.cpp
init()
preinstaller.cpp
Section 3.2.4.1
win_app.cpp
init()
preinstaller.cpp
Section 3.2.4.1
win_app.cpp
init()
preinstaller.cpp
Section 3.2.4.1
win_app.cpp
init()
preinstaller.cpp
Section 3.2.4.1
win_app.cpp
init()
preinstaller.cpp
Section 3.2.4.1
win_app.cpp
init()
preinstaller.cpp
Section 3.2.4.1
win_app.cpp
init()
preinstaller.cpp
Section 3.2.4.1
win_app.cpp
init()
preinstaller.cpp
Section 3.2.4.1
win_app.cpp
init()
preinstaller.cpp
Section 3.2.4.1
win_app.cpp
init()
preinstaller.cpp
Section 3.2.4.1
win_app.cpp
init()
preinstaller.cpp
Section 3.2.4.1
win_app.cpp
init()
preinstaller.cpp
Section 3.2.4.1
win_app.cpp
init()
preinstaller.cpp
Section 3.2.4.1
win_app.cpp
init()
preinstaller.cpp
Section 3.2.4.1
win_app.cpp
init()
preinstaller.cpp
Section 3.2.4.1
win_app.cpp
init()
preinstaller.cpp
Section 3.2.4.1
win_app.cpp
init()
preinstaller.cpp
Section 3.2.4.1
win_app.cpp
init()
preinstaller.cpp
Section 3.2.4.1
win_app.cpp
init()
preinstaller.cpp
Section 3.2.4.1
win_app.cpp
init()
preinstaller.cpp
Section 3.2.4.1
win_app.cpp
init()
preinstaller.cpp
Section 3.2.4.1
win_app.cpp
init()
preinstaller.cpp
Section 3.2.4.1
win_app.cpp
init()
preinstaller.cpp
Section 3.2.4.1
win_app.cpp
init()
preinstaller.cpp
Section 3.2.4.1
win_app.cpp
init()
preinstaller.cpp
Section 3.2.4.1
windesk.sh
Section 3.2.4.1
Section 3.2.4.1
Section 3.2.4.1
Section 3.2.4.1
Section 3.2.4.1
Section 3.2.4.1
Section 3.2.4.1
Section 3.2.4.1
Section 3.2.4.1
of wx_factory.cpp
of wx_factory.cpp
of wx_factory.cpp
of wx_factory.cpp
of wx_factory.cpp
of wx_factory.cpp
of wx_factory.cpp
strings-eng.xml
CommandForgotPassword()
Section 3.2.3.8
Section 3.2.3.8
Section 3.2.3.8
Section 3.2.3.8
Section 3.2.3.8
N/A
N/A
Section 3.2.3.8
ConnectionDataPanel_ForgotPassword()
Section 3.2.3.8
ConnectionDataPanel_ForgotPassword()
ForgotPassword()
tunnel.cpp
Section 3.2.3.8
Section 3.2.3.1
N/A
N/A
N/A
N/A
N/A
N/A
Section 3.2.4.1
of wx_factory.cpp
Section 3.2.4.1
of wx_factory.cpp
Section 3.2.4.1
Section 3.2.4.1
Section 3.2.4.1
Section 3.2.4.1
Section 3.2.4.1
Section 3.2.4.1
Section 3.2.4.1
of wx_factory.cpp
of wx_factory.cpp
wx_check_list.cpp
of wx_factory.cpp
of wx_factory.cpp
ApplyMam2Connection() method in
wx_list_control.cpp
ApplyMam2Connection() method in
wx_list_control.cpp
Section 3.2.4.1
wx_nid_manager.cpp
Section 3.2.4.1

Section 3.2.4.1

Section 3.2.4.1
Section 3.2.4.1
Section 3.2.4.1
Section 3.2.4.1
Section 3.2.4.1
Section 3.2.4.1
Section 3.2.4.1
of wx_factory.cpp
of wx_factory.cpp
of wx_factory.cpp
wx_check_list.cpp
wx_check_list.cpp
wx_check_list.cpp
Section 3.2.4.1
SetConnButtonsState()
Section 3.2.4.1
UndoSettingsChangings()
Section 3.2.4.1
State_ConnectionData()
Section 3.2.4.1
CheckConnectionDataControls()
Section 3.2.4.1
Section 3.2.4.1
Section 3.2.4.1
Section 3.2.4.1
NidManager_Changed
CheckNidManagerChanges
Section 3.2.4.1
ApplyNicOrderList()
Section 3.2.4.1
wx_nid_manager.cpp
Section 3.2.4.1
State_GeneralSettings()
Section 3.2.4.1
Section 3.2.4.1
ApplyNicOrderList()
Section 3.2.4.1
ApplyNicOrderList()
Section 3.2.4.1
SettingsPage_ApplyButtonClick
Section 3.2.4.1
of wx_factory.cpp
ApplyNicOrderList()
Section 3.2.4.1
Section 3.2.4.1
ProfileManager_Changed()
Section 3.2.4.1
GetConnectionStatusString()
State_ConnectionStatus()
Section 3.2.4.1
GetConnectionStatusString()
Section 3.2.4.1
Section 3.2.4.1
Section 3.2.4.1
Section 3.2.4.1
Section 3.2.4.1
Section 3.2.4.1
Section 3.2.4.1
wx_nid_manager.cpp
Section 3.2.4.1
wx_nid_manager.cpp
Section 3.2.4.1
wx_nid_manager.cpp
Section 3.2.4.1
Menu_ShowProfileManager()
Section 3.2.4.1
FillInterfaceChoice()
Section 3.2.4.1
FillInterfaceChoice()
Section 3.2.4.1
State_GeneralSettings
Section 3.2.4.1
State_GeneralSettings
Section 3.2.4.1
NidManager_Changed()
Section 3.2.4.1
Section 3.2.4.1
Section 3.2.4.1
Section 3.2.4.1
Section 3.2.4.1
SettingsPage_ApplyButtonClick()
Section 3.2.4.1
State_Profiles()
Section 3.2.4.1
State_Profiles()
Section 3.2.4.1
State_Profiles()
Section 3.2.4.1
Section 3.2.4.1
Section 3.2.4.1
Section 3.2.4.1
Section 3.2.4.1
Section 3.2.4.1
Section 3.2.4.1
wx_nid_manager.cpp
Section 3.2.4.1
wx_nid_manager.cpp
Section 3.2.4.1
wx_nid_manager.cpp
Section 3.2.4.1
State_GeneralSettings()
Section 3.2.4.1
Section 3.2.4.1
Section 3.2.4.1
Section 3.2.4.1
SelectedProfileMoveUp(),SelectedProfileMoveDown()wx_pr
ofile_manager.cpp
Section 3.2.4.1
Section 3.2.4.1
Section 3.2.4.1
Section 3.2.4.1
Section 3.2.4.1
Section 3.2.4.1
Section 3.2.4.1
Section 3.2.4.1
Section 3.2.4.1
Section 3.2.4.1
Section 3.2.4.1
Section 3.2.4.1
Section 3.2.4.1
Section 3.2.4.1
Section 3.2.4.1
Section 3.2.4.1
Section 3.2.4.1
Section 3.2.4.1
Section 3.2.4.1
Section 3.2.4.1
Section 3.2.4.1
ApplyWlanProfileList() in nsprotocol_to_mam_config.cpp
Section 3.2.4.1
Section 3.2.4.1
Section 3.2.4.1
src\cpp\client\core\common\nsprotocol
Section 3.2.4.1
Section 3.2.4.1
Section 3.2.4.1
Section 3.2.4.1
Section 3.2.4.1
Section 3.2.4.1
Section 3.2.4.1
Section 3.2.4.1
Section 3.2.4.1
Section 3.2.4.1
Section 3.2.4.1
Section 3.2.4.1
Section 3.2.4.1
Section 3.2.4.1
Section 3.2.4.1
Section 3.2.4.1
Section 3.2.4.1
Section 3.2.4.1
Section 3.2.4.1
Section 3.2.4.1
Section 3.2.4.1
Section 3.2.4.1
Section 3.2.4.1
Section 3.2.4.1
Section 3.2.4.1
Section 3.2.4.1
Section 3.2.4.1
Section 3.2.4.1
Section 3.2.4.1
Section 3.2.4.1
Section 3.2.4.1
Section 3.2.4.1
Section 3.2.4.1
Section 3.2.4.1
Section 3.2.4.1
Section 3.2.4.1
Section 3.2.4.1
Section 3.2.4.1
Section 3.2.4.1
Section 3.2.4.1
Section 3.2.4.1
Section 3.2.4.1
Section 3.2.4.1
SetComponentEnable()
Section 3.2.4.1
Section 3.2.4.1
Section 3.2.4.1
Section 3.2.4.1
Section 3.2.4.1
Section 3.2.4.1
FillServerHostAndPort()
FillServerHostAndPort()
Known server list ApplyMam2Connection() method in
wx_list_control.cpp
Section 3.2.4.1
Section 3.2.4.1
Section 3.2.4.1
Section 3.2.4.1
Section 3.2.4.1
Section 3.2.4.1
Section 3.2.4.1
Section 3.2.4.1
Section 3.2.4.1
Section 3.2.4.1
Section 3.2.4.1
Section 3.2.4.1
Section 3.2.4.1
Section 3.2.4.1
Section 3.2.4.1
Section 3.2.4.1
wx_check_list.cpp
Section 3.2.4.1
Section 3.2.4.1
GetForceWifiManager () in nsclient_state_controller.cpp
Section 3.2.4.1
Section 3.2.4.1
Section 3.2.4.1
Section 3.2.4.1
Section 3.2.4.1
Section 3.2.4.1
Section 3.2.4.1
Section 3.2.4.1
of wx_factory.cpp
Section 3.2.4.1
of wx_factory.cpp
Section 3.2.4.1
Section 3.2.4.1
Section 3.2.4.1
of wx_factory.cpp
of wx_factory.cpp
CreateFrame(),CreateComponent(),CreateMenu()
methods
of wx_factory.cpp
Section 3.2.4.1
of wx_factory.cpp
Section 3.2.4.1
of wx_factory.cpp
Section 3.2.4.1
of wx_factory.cpp
Section 3.2.4.1
of wx_factory.cpp
Section 3.2.4.1
of wx_factory.cpp
Section 3.2.4.1
of wx_factory.cpp
Section 3.2.4.1
of wx_factory.cpp
Section 3.2.4.1
of wx_factory.cpp
Section 3.2.4.1
of wx_factory.cpp
Section 3.2.4.1
of wx_factory.cpp
Section 3.2.4.1
of wx_factory.cpp
of wx_factory.cpp
Section 3.2.4.1
Section 3.2.4.1
of wx_factory.cpp
Section 3.2.4.1
Section 3.2.4.1
of wx_factory.cpp
Section 3.2.4.1
SetTrayIconTitleAndExecuteButton()
Section 3.2.4.1
TrayIcon_DoubleClick()
N/A
SetTrayIcon()
SetClickAction()
Section 3.2.4.1
SetTrayIcon()
Section 3.2.4.1
SetTrayIcon()
Section 3.2.4.1
SetTrayIcon()
Section 3.2.4.1
ShowAbout()
Section 3.2.4.1
ShowAbout()
Section 3.2.4.1
Section 3.2.4.1
Section 3.2.4.1
ReconfigureMenus()
Section 3.2.4.1
SetIconTooltip()
Section 3.2.4.1
Section 3.2.4.1
Section 3.2.4.1
Section 3.2.4.1
GetAccounting() in nsclient_state_controller.cpp
ReconfigureMenus()
of wx_factory.cpp
Section 3.2.4.1
GetVpnProfiles(),GetDunProfiles(),GetLanProfiles(),GetWL
anProfiles() in nsclient_state_controller.cpp
Section 3.2.4.1
Section 3.2.4.1
Section 3.2.4.1
Section 3.2.4.1
Section 3.2.4.1
Section 3.2.4.1
Section 3.2.4.1
Section 3.2.4.1
Section 3.2.4.1
Section 3.2.4.1
Section 3.2.4.1
Section 3.2.4.1
Section 3.2.4.1

Section 3.2.4.1
Section 3.2.4.1
Section 3.2.4.1
Section 3.2.4.1
Section 3.2.4.1
Section 3.2.4.1
Section 3.2.4.1
Section 3.2.4.1
Section 3.2.4.1
Section 3.2.4.1
Section 3.2.4.1
Section 3.2.4.1
Section 3.2.4.1
Section 3.2.4.1
N/A
N/A
N/A
N/A
N/A
N/A
N/A
N/A
N/A
N/A
-> Click this button to remove the color code from sheet
Unit Test Plan (reference to test

System Test Plan (reference to
case id or test plan section
test case id or test plan section
Integration Test Plan (reference to
number)
number)
test case id or test plan section
number)
ocs\TestCases\UTP\NSClient\Ne
ocs\TestCases\NS
tsnapper_Client_Windows_Mac
Client\Netsnapper_Client_windo
_Ubuntu_ut01.xlsx/7)
ws_sit01.xlsx/10)
N/A
NSC.INSCT.01
N/A
NSC.AUT.UP.01
N/A
NSC.AUT.UP.02
N/A
NSC.AUT.UP.03
N/A
NSC.AUT.UP.04
N/A
NSC.AUT.UP.05
N/A
NSC.AUT.IP.01
N/A
NSC.AUT.IP.02
N/A
NSC.AUT.IP.03
N/A
NSC.AUT.IP.04
N/A
NSC.AUT.IP.05
N/A
NSC.AUT.SC.01
N/A
NSC.AUT.SC.02
N/A
NSC.AUT.CONN.01
N/A
NSC.AUT.CONN.02
N/A
NSC.AUT.CONN.03
N/A
NSC.AUT.CONN.04,
NSC.AUT.CONN.05,
NSC.AUT.CONN.06,
NSC.AUT.CONN.07,
NSC.AUT.CONN.08,
NSC.AUT.CONN.09
N/A
NSC.AUT.CONN.10
N/A
NSC.AUT.CONN.11
N/A
NSC.AUT.CONN.12
N/A
NSC.AUT.CONN.13
N/A
NSC.AUT.CONN.14
N/A
NSC.AUT.CONN.15
N/A
NSC.AUT.CONN.16
N/A
NSC.AUT.CONN.17
N/A
NSC.AUT.CONN.18
N/A
NSC.SEC.01
N/A
NSC.SEC.02
N/A
NSC.SEC.03
N/A
NSC.SEC.04
N/A
NSC.SEC.05
N/A
NSC.SEC.06
N/A
NSC.SEC.07
N/A
NSC.VP.CONN.01
N/A
NSC.VP.CONN.02
N/A
NSC.VP.CONN.03
N/A
NSC.VP.CONN.05
N/A
NSC.VP.CONN.06
N/A
NSC.VP.CONN.07
N/A
NSC.VP.CONN.08
N/A
NSC.VP.SP.01
N/A
NSC.VP.SP.01
N/A
NSC.VP.SP.02
N/A
NSC.VP.SP.02
N/A
NSC.VP.SP.03
N/A
NSC.VP.SP.04
N/A
NSC.VP.RP.01
N/A
NSC.VP.RP.01
N/A
NSC.VP.RP.02
N/A
NSC.VP.RP.02
N/A
NSC.VP.RP.03
N/A
NA
N/A
NSC.SS.01
N/A
NSC.SS.02
N/A
NSC.SS.03
N/A
NSC.SS.04
N/A
NSC.SS.SP.01
N/A
NSC.SS.SP.02
N/A
NSC.SS.SP.03
N/A
NSC.SS.SP.04
N/A
NSC.SS.SP.05
N/A
NSC.SS.SP.06
N/A
NSC.SS.SP.07
N/A
NSC.SS.SP.08
N/A
NSC.DC.01
N/A
NSC.DC.02
N/A
NSC.DC.03
N/A
NSC.DC.04
N/A
NSC.DC.05
N/A
NSC.DC.05
N/A
NSC.DC.05
N/A
NSC.DE.01
N/A
NSC.DE.02
N/A
NSC.DE.03
N/A
NSC.DE.04
N/A
NSC.DE.05
N/A
NSC.DE.06
N/A
NSC.DE.07
N/A
NSC.DE.08
NSCLIENT_EN_04,
NSCLIENT_EN_05,
NSCLIENT_EN_06
NSC.DE.09
NSCLIENT_EN_01
NA
NSCLIENT_EN_02
NA
NSCLIENT_EN_03
NA
N/A
NA
N/A
N/A
NA
NA
N/A
NA
N/A
N/A
N/A
N/A
N/A
N/A
NA
NSC.AF.01
NSC.AF.02
NA
NSC.AF.03
NA
N/A
NSC.CI.01
N/A
NSC.CI.02
N/A
NSC.CI.03
N/A
NSC.CI.04
N/A
NSC.CI.05
N/A
NSC.CI.06
N/A
NSC.CI.07
N/A
NSC.CI.08
N/A
NSC.CI.09
N/A
NSC.DB.01
N/A
NSC.DB.02
N/A
NSC.DB.03
N/A
NSC.DB.04
N/A
NSC.DB.05
N/A
NSC.DB.06
N/A
NSC.DB.07
N/A
NSC.IM.IL.01
N/A
NSC.IM.IL.02
N/A
NSC.IM.IL.03
N/A
NSC.IM.IL.04
N/A
NSC.IM.RECS.01
N/A
NSC.IM.RECS.02
N/A
NSC.IM.RECS.03
N/A
NSC.IM.RECS.04
N/A
NSC.IM.RECA.01
N/A
NSC.IM.RECA.02
N/A
NSC.IM.IS.01
N/A
NSC.IM.IS.02
N/A
NSC.IM.IS.03
N/A
NSC.IM.IS.04
N/A
NSC.IM.IS.05
N/A
NSC.IM.IS.06
N/A
NSC.IM.IS.07
N/A
NSC.PM.01
N/A
NSC.PM.02
N/A
NSC.PM.03
N/A
NSC.PM.04
N/A
NSC.PM.04
N/A
NSC.PM.05
N/A
NSC.PM.06
N/A
NSC.PM.07
N/A
NSC.PM.LAN.01
N/A
NSC.PM.LAN.02
N/A
NSC.PM.WIFI.01
N/A
NSC.PM.WIFI.02
N/A
NSC.PM.WIFI.03
N/A
NSC.PM.WIFI.04
N/A
NSC.PM.WIFI.05
N/A
NSC.PM.WIFI.06
N/A
NSC.PM.VPN.01
N/A
NSC.PM.VPN.02
N/A
NSC.PM.VPN.03
N/A
NSC.PM.VPN.04
N/A
NSC.PM.VPN.05
N/A
NSC.PM.VPN.06
N/A
NSC.PM.VPN.07
N/A
NSC.PM.DUN.01
N/A
NSC.PM.DUN.02
N/A
NSC.PM.DUN.03
N/A
NSC.PM.DUN.04
N/A
NSC.PM.DUN.05
N/A
NSC.PM.DUN.06
N/A
NSC.PM.DUN.07
N/A
NSC.PM.DUN.08
N/A
NSC.PM.DUN.09
N/A
NA
N/A
NA
N/A
NA
N/A
NA
N/A
NA
N/A
NA
N/A
NSC.GS.01
N/A
NSC.GS.02
N/A
NSC.GS.03
N/A
NSC.GS.04
N/A
NSC.GS.05
N/A
NSC.GS.06
N/A
NSC.GS.07
N/A
NSC.GS.08
N/A
NSC.GS.09
N/A
NSC.GS.10
N/A
NSC.GS.11
N/A
NSC.GS.12
N/A
NSC.GS.13
N/A
NSC.GS.14
N/A
NSC.GS.15
N/A
NSC.GS.16
N/A
NSC.OO.01
N/A
NSC.OO.02
N/A
NSC.OO.03
N/A
NSC.OO.04
N/A
NSC.OO.05
N/A
NSC.OO.06
N/A
NSC.OO.07
N/A
NSC.OO.08
N/A
NSC.OO.09
N/A
NSC.OO.10
N/A
NSC.UP.01
N/A
NSC.UP.02
N/A
NSC.UP.03
N/A
NSC.UP.04
N/A
NSC.UP.05
N/A
NSC.UP.06
N/A
NSC.UP.07
N/A
NSC.UP.08
NSCLIENT_US_01,NSCLIENT_U
S_02,NSCLIENT_US_03,NSCLIE
NT_US_04
NSC.UP.09
NT_US_04
NSC.UP.10
NT_US_04
NSC.UP.11
NT_US_04
NSC.UP.12
NSCLIENT_SL_01,
NSCLIENT_SL_03,
NSCLIENT_SL_05,
NSCLIENT_SL_29
NSC.SERVER.LIST.01
NSCLIENT_SL_01
NSC.SERVER.LIST.01
NSC.SERVER.LIST.02
NSCLIENT_SL_36
NSC.SERVER.LIST.13
NSCLIENT_SL_35,
NSCLIENT_SL_37
NSC.SERVER.LIST.03
NSCLIENT_SL_36
NSC.SERVER.LIST.04
NSCLIENT_SL_29
NSC.SERVER.LIST.05
NSCLIENT_SL_29
NSC.SERVER.LIST.08
NSCLIENT_SL_18
NSC.SERVER.LIST.10
NSCLIENT_SL_30
NSC.SERVER.LIST.07
NSCLIENT_SL_30
NSC.SERVER.LIST.07
NSCLIENT_SL_36
NSC.SERVER.LIST.12
NSCLIENT_SL_36
NSC.SERVER.LIST.11
NSCLIENT_SL_25
NSC.SERVER.LIST.09
NSCLIENT_SL_09
NSC.SERVER.LIST.06
NSCLIENT_SL_25
NSC.SERVER.LIST.14
NSCLIENT_SL_27
NSC.SERVER.LIST.10
NSCLIENT_SL_36
NSC.SERVER.LIST.10
NSCLIENT_SL_25
NSC.SERVER.LIST.20
NSCLIENT_SL_30
NSC.SERVER.LIST.03
NSCLIENT_SL_31,
NSCLIENT_SL_32
NSC.CS.01
NA
NSC.CS.02
NA
NSC.CS.03
NA
NSC.CS.04
NSCLIENT_SL_32,
NSCLIENT_SL_33
NSC.CS.05
NSCLIENT_SL_12,
NSCLIENT_SL_13
NSCLIENT_ST_03
NSCLIENT_ST_46
NSCLIENT_ST_47
NSCLIENT_ST_15
NSCLIENT_ST_18,
NSCLIENT_ST_20
NSCLIENT_ST_48
NSCLIENT_ST_49
NSCLIENT_ST_38
NSCLIENT_ST_40
NSCLIENT_ST_49
NSCLIENT_ST_44
NSCLIENT_ST_45
NSC.CS.06
NSCLIENT_ST_13
NSCLIENT_ST_14
NSCLIENT_ST_50
NSCLIENT_ST_44
N/A
NSC.TR.01
N/A
NSC.TR.02
N/A
NSC.TR.03
N/A
NSC.TR.04
N/A
NSC.TR.05
N/A
NA
N/A
NSC.AN.01
N/A
NSC.AN.02
N/A
NSC.AN.03
N/A
NSC.AN.04
N/A
NSCLIENT_DL_01,
NSCLIENT_DL_02,
NSCLIENT_DL_03,
NSCLIENT_DL_04
NSCLIENT_DL_01,
NSCLIENT_DL_02,
NSCLIENT_DL_03,
NSCLIENT_DL_04
NSCLIENT_DL_03,
NSCLIENT_DL_04
NSCLIENT_DL_05,
NSCLIENT_DL_06,
NSCLIENT_DL_07
NSC.AN.05
NSC.DATA.LIMIT.01
NSC.DATA.LIMIT.02
NSC.DATA.LIMIT.07
NSC.DATA.LIMIT.04
NSC.DATA.LIMIT.03
NSC.DATA.LIMIT.08
NSCLIENT_DL_08
NSCLIENT_DL_09
NSC.DATA.LIMIT.05
NSCLIENT_DL_05,
NSCLIENT_DL_06,
NSCLIENT_DL_07,
NSCLIENT_DL_10
NSC.DATA.LIMIT.05
NSC.DATA.LIMIT.06
NSCLIENT_DL_05,
NSCLIENT_DL_06,
NSCLIENT_DL_07,
NSCLIENT_DL_10
NSC.DATA.LIMIT.08
N/A
NA
N/A
NA
NA
N/A
NA
N/A
NA
N/A
NA
NA
N/A
NA
N/A
NA
N/A
NA
N/A
NA
NA
N/A
NA
N/A
NA
N/A
NA
N/A
NA
NA
N/A
NA
N/A
NA
N/A
NA
N/A
NA
NA
N/A
NA
N/A
NA
N/A
NA
N/A
NA
NA
N/A
NA
N/A
NA
N/A
NA
N/A
NA
N/A
NA
N/A
NA
N/A
NA
NA
N/A
NA
N/A
NA
N/A
NA
N/A
NA
N/A
NA
N/A
NA
N/A
NA
NA
N/A
NA
N/A
NA
NA
N/A
NA
N/A
NA
N/A
NA
N/A
NA
NA
N/A
NA
N/A
NA
N/A
NA
N/A
NA
NA
N/A
NA
N/A
NA
N/A
NA
N/A
NA
NA
N/A
NA
N/A
NA
N/A
NA
N/A
NA
NA
N/A
NA
N/A
NA
NA
N/A
NA
N/A
NA
NA
N/A
NA
N/A
NA
N/A
NA
N/A
NA
NA
N/A
NA
N/A
NA
N/A
NA
N/A
NSC.INSCT.02
N/A
NSC.INSCT.03
N/A
NSC.INSCT.04
N/A
NSC.INSCT.05
N/A
NSC.INSCT.06
N/A
NSC.INSCT.07
N/A
NSC.INSCT.08
N/A
NSC.INSCT.09
N/A
NSC.INSCT.10
N/A
NSC.INSCT.11
N/A
NSC.INSCT.12
N/A
NSC.INSCT.13
N/A
NSC.INSCT.14
N/A
NSC.INSCT.15
N/A
NSC.INSCT.16
N/A
NSC.INSCT.17
N/A
NSC.INSCT.18
N/A
NSC.INSCT.19
N/A
NSC.INSCT.20
N/A
NSC.INSCT.21
N/A
NSC.INSCT.22
N/A
NSC.INSCT.23
N/A
NSC.INSCT.24
N/A
NSC.INSCT.24
N/A
NSC.INSCT.24
N/A
NSC.INSCT.24
NSCLIENT_IN_01
NSC_INS_01
N/A
NSC.AP.01
N/A
NSC.AP.02
N/A
NSC.AP.03
N/A
NSC.AP.04
N/A
NSC.AP.05
N/A
NSC.AP.06
N/A
NSC.AP.07
N/A
NSC.AP.08
N/A
NSC.AP.09
N/A
NSC.AP.10
NSCLIENT_FP_08
NSC.AP.11
NSCLIENT_FP_09
NSC.AP.12
N/A
NSC.AP.13
NSCLIENT_FP_03,
NSCLIENT_FP_06
NSC.AP.14
N/A
NSC.AP.15
NSCLIENT_FP_20
NSC.AP.16
NSCLIENT_FP_21
NSC.AP.17
N/A
NSC.AP.18
NSCLIENT_SE_01,
NSCLIENT_SE_02
NSC_B2C_01
NSC_B2C_02
NSC_B2C_03
NSC_B2C_04
NSC_B2C_05
NSC_B2C_06
NSC_B2C_07
NSC_B2C_08
N/A
N/A
N/A
N/A
NSCLIENT_FT_01
N/A
NSC.SE.01
N/A
NSC.SE.02
N/A
NSC.SE.03
N/A
NSC.SE.04
N/A
NSC.SE.05
N/A
NSC.SE.06
N/A
NSC.SE.07
N/A
NSC.SE.08
N/A
NSC.SE.09
N/A
NSC.SE.10
N/A
NSC.SE.11
N/A
NSC.SE.12
N/A
NSC.SE.13
N/A
NSC.SE.14
N/A
NSC.SE.15
N/A
NSC.SE.16
N/A
NSC.SE.17
N/A
NSC.SE.18
N/A
NSC.SE.19
N/A
NSC.SE.20
N/A
NSC.SE.21
N/A
NSC.SE.22
N/A
NSC.SE.23
N/A
NSC.SE.24
N/A
NSC.SE.25
N/A
NSC.SE.26
N/A
NSC.SE.27
N/A
NSC.SE.28
N/A
NSC.SE.29
N/A
NSC.SE.30
N/A
NSC.SE.31
N/A
NSC.SE.32
N/A
NSC.SE.33
N/A
NSC.SE.34
N/A
NSC.SE.35
N/A
NSC.SE.36
N/A
NSC.SE.37
N/A
NSC.SE.38
N/A
NSC.SE.39
N/A
NSC.SE.40
N/A
NSC.SE.41
N/A
NSC.SE.42
N/A
NSC.SE.43
N/A
NSC.SE.44
N/A
NSC.SE.45
N/A
NSC.SE.46
N/A
NSC.SE.47
N/A
NSC.SE.48
N/A
NSC.SE.49
N/A
NSC.SE.50
N/A
NSC.SE.51
N/A
NSC.SE.52
N/A
NSC.SE.53
N/A
NSC.SE.54
N/A
NSC.SE.55
N/A
NSC.SE.56
N/A
NSC.SE.57
N/A
NSC.SE.58
N/A
NSC.SE.59
N/A
NSC.SE.60
N/A
NSC.SE.61
N/A
NSC.SE.62
N/A
NSC.SE.63
N/A
NSC.SE.64
N/A
NSC.SE.65
N/A
NSC.SE.66
N/A
NSC.SE.67
N/A
NSC.SE.68
N/A
NSC.SE.69
N/A
NSC.SE.70
N/A
NSC.SE.71
N/A
NSC.SE.72
N/A
NSC.SE.73
N/A
NSC.SE.74
N/A
NSC.SE.75
N/A
NSC.SE.76
N/A
NSC.SE.77
N/A
NSC.SE.78
N/A
NSC.SE.79
N/A
NSC.SE.80
N/A
NSC.SE.81
N/A
NSC.SE.82
N/A
NSC.SE.83
N/A
NSC.SE.84
N/A
NSC.SE.85
N/A
NSC.SE.86
N/A
NSC.SE.87
N/A
NSC.SE.88
N/A
NSC.SE.89
N/A
NSC.SE.90
N/A
NSC.SE.91
N/A
NSC.SE.92
N/A
NSC.SE.93
N/A
NSC.SE.94
N/A
NSC.SE.95
N/A
NSC.SE.96
N/A
NSC.SE.97
N/A
NSC.SE.98
N/A
NSC.SE.99
N/A
NSC.SE.100
N/A
NSC.SE.101
N/A
NSC.SE.102
N/A
NSC.SE.103
N/A
NSC.SE.104
N/A
NSC.SE.105
N/A
NSC.SE.106
N/A
NSC.SE.107
N/A
NSC.SE.108
N/A
NSC.SE.109
N/A
NSC.SE.110
N/A
NSC.SE.111
N/A
NSC.SE.112
N/A
NSC.SE.113
N/A
NSC.SE.114
N/A
NSC.SE.115
N/A
NSC.SE.116
N/A
NSC.SE.117
N/A
NSC.SE.118
N/A
NSC.SE.119
N/A
NSC.SE.120
N/A
NSC.SE.121
N/A
NSC.SE.122
N/A
NSC.SE.123
N/A
NSC.SE.124
N/A
NSC.SE.125
N/A
NSC.SE.126
N/A
NSC.SE.127
N/A
NSC.SE.128
N/A
NSC.SE.129
N/A
NSC.SE.130
N/A
NSC.SE.131
N/A
NSC.SE.132
N/A
NSC.SE.133
N/A
NSC.SE.134
N/A
NSC.SE.135
N/A
NSC.SE.136
N/A
NSC.SE.137
N/A
NSC.SE.138
N/A
NSC.SE.139
N/A
NSC.SE.140
N/A
NSC.SE.141
N/A
NSC.SE.142
N/A
NSC.SE.143
N/A
NSC.SE.144
N/A
NSC.SE.145
N/A
NSC.SE.146
N/A
NSC.SE.147
N/A
NSC.SE.148
N/A
NSC.SE.149
N/A
NSC.SE.150
N/A
NSC.SE.151
N/A
NSC.SE.152
N/A
NSC.SE.153
N/A
NSC.SE.154
N/A
NSC.SE.155
N/A
NSC.SE.156
N/A
NSC.SE.157
N/A
NSC.SE.158
N/A
NSC.SE.159
N/A
NSC.SE.160
N/A
NSC.SE.161
N/A
NSC.SE.162
N/A
NSC.SE.163
N/A
NSC.SE.164
N/A
NSC.SE.165
N/A
NSC.SE.166
N/A
NSC.SE.167
N/A
NSC.SE.168
N/A
NSC.SE.169
N/A
NSC.SE.170
N/A
NSC.SE.171
N/A
NSC.SE.171
N/A
NSC.SE.171
N/A
NSC.CO.01
N/A
NSC.CO.02
N/A
NSC.CO.03
N/A
NSC.CO.04
N/A
NSC.CO.05
N/A
NSC.CO.06
N/A
NSC.CO.07
N/A
NSC.CO.08
N/A
NSC.CO.09
N/A
NSC.CO.10
N/A
NSC.CO.11
N/A
NSC.CO.12
N/A
NSC.CO.13
N/A
NSC.CO.14
N/A
NSC.CO.15
N/A
NSC.CO.16
N/A
NSC.CO.17
N/A
NSC.CO.18
N/A
NSC.CO.19
N/A
NSC.CO.20
N/A
NSC.CO.21
N/A
NSC.CO.22
N/A
NSC.CO.23
N/A
NSC.CO.24
N/A
NSC.CO.25
N/A
NSC.CO.26
N/A
NSC.CO.27
N/A
NSC.CO.28
N/A
NSC.CO.29
N/A
NSC.CO.30
N/A
NSC.CO.31
N/A
NSC.CO.32
N/A
NSC.CO.33
N/A
NSC.CO.34
N/A
NSC.CO.35
N/A
NSC.CO.36
N/A
NSC.CO.37
N/A
NSC.CO.38
N/A
NSC.CO.39
N/A
NSC.CO.40
N/A
NSC.CO.41
N/A
NSC.CO.42
N/A
NSC.CO.43
N/A
NSC.DT.01
N/A
NSC.DT.02
N/A
NSC.DT.03
N/A
NSC.DT.04
N/A
NSC.DT.05
N/A
NSC.DT.06
N/A
NSC.DT.07
N/A
NSC.DT.08
N/A
NSC.DT.09
N/A
NSC.DT.10
N/A
NSC.DT.11
N/A
NSC.SV.01
N/A
NSC.SV.02
N/A
NSC.SV.03
N/A
NSC.SV.04
N/A
NSC.SV.05
N/A
NSC.SV.06
N/A
NSC.SV.07
N/A
NSC.SV.08
N/A
NSC.SV.09
N/A
NSC.SV.10
N/A
NSC.SV.11
N/A
NSC.HR.01
N/A
NSC.HR.02
N/A
N/A
N/A
N/A
N/A
NSC.MR.01
ARICENT CONFIDENTIAL
Acceptance Test Plan (reference

to test case id or test plan section
number)
CELL CHANGED
OLD VALUE
NEW VALUE
TIME OF CHANGE
Traceability Matrix ! $J$30

CI-SC-1
Si-SC-1 to SI-SC-54
2/19/2015 16:01
SI-SC-1 to SI-SC-54
2/19/2015 16:01
CI-SC-1
SI-SC-1 to SI-SC-54
2/19/2015 16:01
CI-SC-1
SI-SC-1 to SI-SC-54
2/19/2015 16:01
SC-AUTH1
SC-AUTH1
2/19/2015 16:02
SC-AUTH1 to
2/19/2015 16:02
SC-AUTH1 to SC-AUTH20 2/19/2015 16:03
SC-AUTH2 SC-AUTH1 to SC-AUTH20 2/19/2015 16:03
SC-AUTH3 SC-AUTH1 to SC-AUTH20 2/19/2015 16:03
INS-SC1
INS-SC1
2/19/2015 16:05
Traceability Matrix ! $J$119 SP-WN1 - 8
SP-WN1 - 8
2/19/2015 16:07
NS-CI-01- 09
2/19/2015 16:08
NS-CI-01- 09
NS-CI-01 to 09
2/19/2015 16:08
NS-CI-01 to 09
2/19/2015 16:08
CI-SC-1
CI-SC-1
2/19/2015 16:11
SP-WN1 to 8
2/19/2015 16:14
CI-SC-1
SP-WN1 to 8
2/19/2015 16:14
CI-SC-1
SP-WN1 to 8
2/19/2015 16:14
SP-WN1 to 8 NS_Client_REBRAND_1 2/19/2015 16:34
NS_Client_REBRAND_1 2/19/2015 16:34
NS_Client_REBRAND_1 to 202/19/2015 16:34
SP-WN1 toNS_Client_REBRAND_1
8
to 202/19/2015 16:34
NS_Client_REBRAND_1
NS_Client_REBRAND_1
to 20
to 212/19/2015 16:35
NS_Client_REBRAND_1
NS_Client_REBRAND_1
to 21
to 222/19/2015 16:35
SP-WN1 to 8
SP-WN1 to 8
2/19/2015 16:36
CI-SC-1
SP-WN1 to 8
2/19/2015 16:36
CI-SC-1
SP-WN1 to 8
2/19/2015 16:36
CI-SC-1
SP-WN1 to 8
2/19/2015 16:36
CI-SC-1
SP-WN1 to 8
2/19/2015 16:36
SP-WN1 to 8
NS-CI-01 to 09
2/19/2015 16:37
SP-WN1 to 8
NS-CI-01 to 09
2/19/2015 16:37
SP-WN1 to 8
NS-CI-01 to 09
2/19/2015 16:37
CI-SC-1
NS-CI-01 to 09
2/19/2015 16:37
Traceability Matrix ! $J$726 NS-CI-01 to 09
NS-CI-01 to 10
2/19/2015 16:37
SP-WN1 toNS_Client_REBRAND_1
8
to 202/19/2015 16:37
NS_Client_REBR
SP-WN1 to 8
2/19/2015 16:37
AND_1 to 20
CI-SC-1
SP-WN1 to 8
2/19/2015 16:38
CI-SC-1
SP-WN1 to 8
2/19/2015 16:38
CI-SC-1
SP-WN1 to 8
2/19/2015 16:38
CI-SC-1
SP-WN1 to 8
2/19/2015 16:38
CI-SC-1
SP-WN1 to 8
2/19/2015 16:39
CI-SC-1
SP-WN1 to 8
2/19/2015 16:39
NS_Client_REBR
SP-MN1 - 7
2/19/2015 16:39
AND_1 to 20
NS_Client_REBR
SP-MN1 - 7
2/19/2015 16:39
AND_1 to 20
N/A
2/19/2015 16:42
Traceability Matrix ! $J$148 SI-SC-1 - 54
N/A
2/19/2015 16:42
Traceability Matrix ! $C$247
Yes
Yes
2/26/2015 18:18
Client
Traceability
should Matrix
support!Client
$A$251
https should
urls forsupport
getting update
http urlsinformation
for getting from
update
MAM
information
server
2/26/2015
from18:19
MAM server
Traceability Matrix
Client should
! $A$252
supportClient
https should
urls of updated
support http
software
urls of updated2/26/2015
software 18:19
Traceability Matrix ! $B$251
NSC.UP.09
NSC.UP.11
2/26/2015 18:19
Traceability Matrix ! $B$252
NSC.UP.10
NSC.UP.12
2/26/2015 18:19
USERNAME
che36969
che36969
che36969
che36969
che36969
che36969
che36969
che36969
che36969
che36969
che36969
che36969
che36969
che36969
che36969
che36969
che36969
che36969
che36969
che36969
che36969
che36969
che36969
che36969
che36969
che36969
che36969
che36969
che36969
che36969
che36969
che36969
che36969
che36969
che36969
che36969
che36969
che36969
che36969
che36969
che36969
che36969
che36969
che36969
che36969
che36969
che33289
che33289
che33289
che33289
che33289
USER HELP CONTENTS

1>
2>
3>
PURPOSE OF REQUIREMENT ID IMPACT ANALYSIS (FEATURE)

THREE SIMPLE STEPS TO USE THIS ' FEATURE ' IN TEMPLATE
ADDITIONAL FEATURES - AUTO LOG UPDATE (On / Off)
PURPOSE OF REQUIREMENT ID IMPACT ANALYSI

Identification of impacted (direct-indirect) requirements has always been a problem area in Requirement Management,
updation.
They can lead to incorrect mapping of related requirements and their work products.
In order to avoid such situations we have developed a new feature- Requirement ID Impact Analysis in the RTM tem
It will help us in effective and efficient tracking of impacted Requirements.
THREE SIMPLE STEPS TO USE THIS ' FEATURE ' IN TEMP

STEP 1: Click on the ' Requirement ID - Impact Analysis ' button.
STEP 2: Please enter the lookup requirement ID (Note: Please provide the ' Requirement ID ' as defined in collumn 2)
STEP 3: It will highlight the Direct related requirement (RED) and indirect related requirement (BLUE)
BACK TO USER HELP CONTENTS
If you have completed these simple steps, you have done the REQUIREMENT ID IMPACT
ADDITIONAL FEATURES - AUTO LOG UPDATE (On / O
Auto Log update (On / Off) feature, this feature will record all the changes made in sheet. User can disable this featur
RTM sheet. It is strongly recommended to enable this feature after completing initial draft of RTM sheet to track the cha
Changes tracked related to Cell Changed, Old value, 'New Value, 'Time of Change and Username in Log workshee
Back to Normal feature, , Click this button to remove the color code from sheet
END OF USER HELP
CONTENTS
NT ID IMPACT ANALYSIS
area in Requirement Management, especially during scope change and RTM
s.
D Impact Analysis in the RTM template.
HIS ' FEATURE ' IN TEMPLATE
ent ID ' as defined in collumn 2)
quirement (BLUE)
ELP CONTENTS
ne the REQUIREMENT ID IMPACT analysis.So, cheers!
TO LOG UPDATE (On / Off)
n sheet. User can disable this feature at the time of preparing initial draft of
al draft of RTM sheet to track the changes.
ge and Username in Log worksheet.
ER HELP
Click this button to

remove the color code
from sheet
(Back to Normal format)
Template Revision History

Rev.
Date of issue
Author
Approver
3.0
18-Sep-07
Anjana
Gangadharan
QG/SEPG
3.1
4-Jun-08
Nishu Lohia
R.Sathya
4.0
27-Jan-11
Aman Saxena
Ramachandran S
4.1
4.2
17-May-11
29-May-14
Jalaj Puri
Ramachandran S
Gunjan Srivastava Ramachandran S
ARICENT CONFIDENTIAL
evision History
Description of Change
Supercedes Traceability Matrix Ver2.0
Helpdesk ticket # 41926 - modified the column
heading for Requirement ID (cell B6).
Added the new feature of Requirement ID Impact Analysis
Updated the logo
Updated the logo and copyright information
CONFIDENTIAL

Netsnapper Client Rt01 Windows

Uploaded by

Copyright:

Available Formats

You might also like

Netsnapper Client Rt01 Windows

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Netsnapper Client Rt01 Windows

Uploaded by

Copyright:

Available Formats

Requirements Traceability

Document Revision History

12/18/2014 Ashok Kumar D

Updated with SRS Modifications

Updated SRS Modifications

Updated Unit Test Mapping for

Updated SITcases ID's

Updated SRS Modifications

Updated Design Mapping and

Updated UI Mapping forExe

Updated SITcases ID's

BaselinedSRS Modifications for

Updated Unit Test Mapping for

11/5/2015 Mullai Parvathi G

Updated SIT cases ID for

11/6/2015 Mullai Parvathi G

Updated SRS Modifications for

Updated with Design Mapping for

with SRS Modifications

with Granted service

Unit Test Mapping for

Design Mapping and

SRS, Design Mapping,

SRS Modifications for

Unit Test Mapping for

SIT cases ID for

SRS Modifications for

with Design Mapping for

cent Group or its

s or implied, including but

mit a written request to:

PRD / SOW / URD / RFC / ITU Standards / User

Netsnapper Client should provide an XML based

Should have a provision for the user to enter

Should have a provision for the user to allow the

Should show the password if the remember

Should leave the password textbox empty if the

Forgot password option should be available to

Server IP and Port

Should have a provision for the user to enter Server

Should have a provision for the user to enter Port

Should have a provision for the user to connect to

When the connection provision is clicked by the

Should display the connection information to the

Should apply the following forced or permitted

Should provide Netsnapper virtual IP address

Should provide multitunneling: Primary/Backup

Should provide automatic connection repair

Should provide automatic intelligent network

Should provide peer-to-peer connection

Should establish a primary and a backup

Should authenticate the user using Netsnapper

Should authenticate the user using Password

Should accomplish authentication in three ways:

Should access MAM for Local authentication

Should access AAA server for LDAP and RADIUS

Should provide System based IPSec

On receiving connect request ,Create a TCP socket