Freefall: translation of the Problem Specification Document from Italian to English
So, here is how the Freefall project actually begins: translating the Problem Specification Document I received from Italian to English. The goal of the project is to develop a Database for the electronic informative system of a mobile phone network operator. Description follows:
A brand-new mobile phone operator is making its entrance in the market. Part of the company’s electronic informative system relates to the management of contracts with customers. For each stipulated contract, the company registers customer data (which include, among other things, a set of alternative telephone numbers) and assigns a unique telephone number to him or her. Any given customer can stipulate more contracts, and therefore have multiple telephone numbers.
Each contract specifies the price plan chosen by the customer. Each price plan includes the price for voice calls, for video calls, for SMSes & MMSes and for international calls. Reduced price plans can be applied during calls made by certain telephone numbers (You&Me). Moreover, the customer contract provides the payment by a recharge voucher (“Pay&Go” tariff) or a monthly bill (“Pay monthly” tariff). If the customer tops up, then the balance must be known. If customers choose “Pay monthly” tariffs, then bank details must be known instead.
For each operation (call, SMS, etc.) made by a customer, the operator registers the dialed number, the date and time of the operation and its cost. For (video)calls, the operator registers the duration in seconds, too; for (video)messages, it registers the quantity of data transmitted (in bytes). At the end of each month, the operator ships bills to monthly-paying users. The first page of the bill contains the date, the customer details, and the total amount for each category of operation (call, message, etc.); following pages contain the details of each operation; each row reports the operation type, the date and time, the called number and the duration or the quantity of transmitted data, depending on the operation type. The operator provides these kind of bills to rechargeable users who prompt for them, too. It may happen that a customer finds errors in the bill. In this case, he notifies the company of the error, which registers the issue details, the reason and the associated bill; after evaluating the situation, the company may register the amount of the refund, too.
In order to advertise new products/technologies, the company may define temporary promotions to make those products/technologies available to customers on a reduced price basis. Each promotion can be associated to certain contracts.
For the current law regulations to be respected, the operator must associate each operation with the location in which the operation has been executed. (i.e. the city where the call comes from).
The next step will be that of extrapolating a first list of requirements. This rough list will be inevitably be ambiguous, incomplete, inconsistent and generally not very clear but later we will apply Requirements Analysis techniques to group requirements together based on each requirement’s scope, remove ambiguities and make all terms homogeneous throughout the requirements document in order to reach consistency.