1.1 --- a/data/dictionary.xml Sun Aug 11 13:16:50 2013 +0200
1.2 +++ b/data/dictionary.xml Sun Aug 11 13:22:24 2013 +0200
1.3 @@ -44,10 +44,13 @@
1.4 <explanation language="en">
1.5 <text>
1.6 for pre-paid subscribers the standard way to charge services is online
1.7 - – subscriber's balance is checked and if sufficient, the service (e.g. sending a SMS) is provided, otherwise the service is denied;
1.8 - if the billing system is not currently available (so we can't say if the subscriber's balance is high enough), we can provide the service and try to charge it later
1.9 + – subscriber's balance is checked in the billing system and if sufficient, the service (e.g. sending a SMS) is provided, otherwise the service is denied;
1.10 + if the billing system is not currently available (so we can't say if the subscriber's balance is high enough), we can provide the service anyway and try to charge it later;
1.11 + this feature requires saving state (transactions which weren't charged yet) in some persitent storage (CDR files, SQL database etc.)
1.12 + and can be done at the billing gateway or directly at system like SMSC
1.13 </text>
1.14 </explanation>
1.15 + <tag>charging</tag>
1.16 </concept>
1.17 <concept>
1.18 <term abbreviation="SMS" completeForm="short message service" language="en"/>
1.19 @@ -80,7 +83,12 @@
1.20 <concept>
1.21 <term abbreviation="DMS" completeForm="donors message service" language="en"/>
1.22 <term abbreviation="DMS" completeForm="dárcovská SMS" language="cs"/>
1.23 - <explanation language="en"><text>specific kind of MOAT short message which is used to donate money to charity or some organization; the donation is charged from sender's pre-paid balance or in his monthly bill alongside the fees for placed calls and sent SMS</text></explanation>
1.24 + <explanation language="en">
1.25 + <text>
1.26 + specific kind of MOAT short message which is used to donate money to charity or some organization;
1.27 + the donation is charged from sender's pre-paid balance or in his monthly bill alongside the fees for placed calls and sent SMS
1.28 + </text>
1.29 + </explanation>
1.30 <tag>messaging</tag>
1.31 </concept>
1.32 <concept>
1.33 @@ -149,6 +157,7 @@
1.34 <explanation language="en">
1.35 <text>
1.36 a text-based client-server protocol for sending e-mail messages
1.37 + uses TCP and standard port is 25 (STARTTLS or unencrypted) or 465 (SSL/TLS) or 587 (STARTTLS or unencrypted for Message Submission – RFC 6409)
1.38 </text>
1.39 </explanation>
1.40 <tag>computer</tag>
1.41 @@ -1496,28 +1505,68 @@
1.42 <tag>computer</tag>
1.43 </concept>
1.44 <concept>
1.45 - <term abbreviation="CR" completeForm="Change Request" language="en"/>
1.46 - <explanation language="en"><text></text></explanation>
1.47 + <term abbreviation="CR" completeForm="change request" language="en"/>
1.48 + <explanation language="en">
1.49 + <text>
1.50 + a request for changing a software – new features or modification of existing ones;
1.51 + when one or more CRs are developed, they are delivered as new version of software product;
1.52 + CR is requested by the customer (mobile network operator) and is delivered by the development team;
1.53 + CR consists of one or more DT which are assigned to particular developers
1.54 + </text>
1.55 + </explanation>
1.56 <tag>computer</tag>
1.57 </concept>
1.58 <concept>
1.59 - <term abbreviation="DT" completeForm="Development Ticket" language="en"/>
1.60 - <explanation language="en"><text></text></explanation>
1.61 + <term abbreviation="DT" completeForm="development ticket" language="en"/>
1.62 + <explanation language="en">
1.63 + <text>
1.64 + a task assigned to a software developer;
1.65 + one or more DTs together usually forms a CR;
1.66 + it is also possible to have an internal DT which is not linked to any CR (e.g. some refactoring or fixes or maintenence which was not requested by the customer);
1.67 + each commit in the versioning system should be linked to a DT
1.68 + </text>
1.69 + </explanation>
1.70 + <tag>computer</tag>
1.71 + </concept>
1.72 + <concept>
1.73 + <term abbreviation="TT" completeForm="trouble ticket" language="en"/>
1.74 + <explanation language="en">
1.75 + <text>
1.76 + a request for fixing something in the production;
1.77 + requires some investigation and then can be solved by changing the configuration on site or by fixing the software (development)
1.78 + </text>
1.79 + </explanation>
1.80 <tag>computer</tag>
1.81 </concept>
1.82 <concept>
1.83 <term abbreviation="SRS" completeForm="System Requirement Specification" language="en"/>
1.84 - <explanation language="en"><text></text></explanation>
1.85 + <explanation language="en">
1.86 + <text>
1.87 + requirements on a software product or its particular change;
1.88 + is written from the system's point of view
1.89 + </text>
1.90 + </explanation>
1.91 <tag>computer</tag>
1.92 </concept>
1.93 <concept>
1.94 <term abbreviation="URS" completeForm="User Requirement Specification" language="en"/>
1.95 - <explanation language="en"><text></text></explanation>
1.96 + <explanation language="en">
1.97 + <text>
1.98 + requirements on a software product or its particular change;
1.99 + is written from the user's point of view
1.100 + </text>
1.101 + </explanation>
1.102 <tag>computer</tag>
1.103 </concept>
1.104 <concept>
1.105 <term abbreviation="" completeForm="engineering build" language="en"/>
1.106 - <explanation language="en"><text>A build of a software product which was not done according to regular procedure and processes. Might be used only for testing on site or during development – not in production. Such software is often delivered as a tar.gz or JAR, WAR etc. file to be patched into existing installation, not as regular package (RPM, DEB etc.) as production version.</text></explanation>
1.107 + <explanation language="en">
1.108 + <text>
1.109 + a build of a software product which was not done according to regular procedure and processes;
1.110 + might be used only for testing on site or during development – not in production;
1.111 + such software is often delivered as a tar.gz or JAR, WAR etc. file to be patched into existing installation, not as regular package (RPM, DEB etc.) as production version
1.112 + </text>
1.113 + </explanation>
1.114 <tag>computer</tag>
1.115 </concept>
1.116 <concept>