Microsoft Word Master master doc

5.3
 
Evaluation 
5.3.1
 
Security 
Table 5-1: Evaluation of Security quality attribute for TMMS Service based on OSA API 
S1: Service is available for legitimate use and sustains Denial of Service attacks 
Availabili
ty
 
Service is made available through the service agreement between the TMMS PR 
and the OSA provider. 
S2: Data is not altered during transmission 
In
tegr
it
y 
No end-to-end data integrity check, suck as checksums, is done to ensure that 
data is not altered. The client needs to trust the service. 
S3: Sender and receiver confirms that they are who they claim to be
Authentication 
The sender is authenticated with the TMMS PR, so given that the receiver trusts 
the TMMS PR it can also be sure that the message received comes from the 
claimed sender. 
S4: Only authorized users get access to the service 
Authori
zation 
The TMMS PR needs to check with User Storage if a user is authorized to use the 
service. 
S5: Only sender and the intended destination part is able to know the content of 
the message 
Confidentiality 
By encrypting the message content only recipients who know how to decrypt it 
may know the content of the message. 

---

5.3 TMMS Service based on OSA API: : Evaluation 
Page 72 of 93 
5.3.2
 
Usability 
Table 5-2: Evaluation of Usability quality attribute for TMMS Service based on OSA API 
5.3.3
 
Modifiability 
Table 5-3: Evaluation of Modifiability quality attribute for TMMS Service based on OSA API 
U1: Distribution of the client application 
Client must manually retrieve the client application. 
U2: Which parameters are necessary for the client to communicate with the 
Proxy-Relay
Parameters needed are: the TMMS PR IP address, local port number and server 
port number. 
U3: Address handling (GSM SMS vs. TMMS addresses)