[UNIVERSIDAD POLITECNICA DE MADRID]

Secure Exchange Money UNIVERSIDAD POLITECNICA DE MADRID Software Requirements Specification

Laura Zapata Aspiazu.

2011 UPM

Revision History
Date (mm/dd/yy) 11/13/11 Revisi on 1.0 Description Initial Version Author Laura Zapata Aspiazu

ii

Table of Contents
1. PURPOSE .............................................................................................................................................. 1 1.1. SCOPE............................................................................................................................................... 1 1.2. DEFINITIONS, ACRONYMS, ABBREVIATIONS .................................................................................... 2 1.2.1. Definitions ............................................................................................................................... 2 1.2.2. Acronyms ................................................................................................................................. 2 1.3. REFERENCES .................................................................................................................................... 2 1.4. OVERVIEW ....................................................................................................................................... 2 2. OVERALL DESCRIPTION ................................................................................................................. 4 2.1. 2.2. 2.3. 2.4. 2.5. 3. PRODUCT PERSPECTIVE .................................................................................................................... 4 PRODUCT FUNCTIONALITY/FEATURES ............................................................................................. 4 USER CHARACTERISTICS .................................................................................................................. 4 CONSTRAINTS................................................................................................................................... 5 ASSUMPTIONS AND DEPENDENCIES .................................................................................................. 5

SPECIFIC REQUIREMENTS ............................................................................................................. 6 3.1. FUNCTIONAL REQUIREMENTS .......................................................................................................... 6

iii

Software Requirements Specification

1.

Purpose
This document is a Software Requirements Specification Document (SRS) for Secure Exchange Money System. The purpose of this SRS is to establish the bases for elaborate a new software tool, describing the main characteristics that will be implemented. This document is intended to people with roles of Financial Business Administrators, Project Managers and Software Development Team, as a starting point to develop this new system.

1.1.

Scope
Secure Money Exchange (SMEX) shall be a secure and reliable system for the mediation of exchanging money between users who want to send it (money) to relatives, friends or others who live abroad and do not necessarily use different monetary systems. The main goal is that money does not leave the country, just go to their final recipients in the local currency. For example, a user "A" in Spain need to transfer Euros to Ecuador to a user "A1"; at the same time in Ecuador a user "B" needs to transfer Dollars to a user B1 in Spain, our subsidiaries in Spain and Ecuador would host the money in Euros and Dollars respectively, then the subsidiary would make a local transfer for users a1 and b1 respectively, which are the final beneficiaries, the money given would be the equivalent according to the current conversion rate, so the company would charge a commission to broker the transaction. The main idea is this: If a user needs to send money abroad, we have to find another user (in that foreign country) that wants to send money either (to the country of the first user), so our subsidiary in each of these countries has to manage the success of the transaction. At the beginning we must implement the system with 2 subsidiaries. We will start using USD Dollars and Euros at the very beginning. The free CurrencyServer Web Service from Daenet shall provide us with hourly updated exchange rates for practically every currency in the world. Exchange rate: In most countries, money that is being sent will be changed into local currency at the time it reaches its destination. To determine the amount of local currency, companies will use an exchange rate that often hurts the user. This is the reason because this business could be very successful, through which the money would not leave the country but would be delivered directly to end users, with our mediation assures that the transaction is carried out and use the current exchange rate

Software Requirement Specification

Date 11/15/2011 11:58:00 AM

Rev 1

Page 1

Software Requirements Specification

without harming the economy of the user, avoiding scams and receive more money than using existing methods.

1.2.

Definitions, Acronyms, Abbreviations

The following is a list of commonly used definitions used throughout this document:

1.2.1. Definitions
ORM: Object-relational mapping is a programming technique for converting data between incompatible type systems in object-oriented programming languages. This creates, in effect, a "virtual object database" that can be used from within the programming language. There are both free and commercial packages available that perform object-relational mapping, A Web service is a method of communication between two electronic devices over a network. The W3C defines a "Web service" as "a software system designed to support interoperable machine-to-machine interaction over a network". It has an interface described in a machine-processable format (specifically Web Services Description Language, known by the acronym WSDL). Other systems interact with the Web service in a manner prescribed by its description using SOAP messages, typically conveyed using HTTP with an XML serialization in conjunction with other Web-related standards."[1]

1.2.2. Acronyms
SMEX: Secure Money Exchange. USD: United States Dollars. USA: United States of America. $: Currency named Dollar. : Currency names Euro. SRS: Software Requirements

1.3.

References
Wiegers_vision_and_scope_201110_ZapataLaura_en.doc, can be obtained emailing to lm.zapata@alumnos.upm.es.

1.4.

Overview
This document is structured in conformity with the IEEE Recommended Practice for Software Requirements Specification ANSI/IEEE Standard 830-1998. Sections that are not considered applicable have been omitted. Section 1 of this SRS describes en a general way the system, main features, stakeholders.

Software Requirement Specification

Date 11/15/2011 11:58:00 AM

Rev 1

Page 2

Software Requirements Specification

Section 2 of this SRS describes the general factors that affect the product and its requirements. This section provides a background for those requirements, which are establish in detail in next section.

Section 3 of the SRS contains all software requirements to a level of detail suficient to enable designers to design a system to satisfy those requirements, and testers to test that the system satisfies those requirements.

Software Requirement Specification

Date 11/15/2011 11:58:00 AM

Rev 1

Page 3

Software Requirements Specification

2.

Overall Description
2.1. Product Perspective
Secure Exchange Money is considered a new system, it doesnt have depend of others inside the same organization, but its functionality depends of other external system that is a Web Service that will provide currency information. For this system we found a Web Service from Daenet.

SECURE EXCHANGE MONEY (SMEX)

CURRENCYSERVER WEB SERVICE (DAENET)

2.2.

Product Functionality/Features
SMEX shall have next main features: Secure Money Exchange System shall be a WEB system, where WEB Client System and Server System interact. System shall be deployed on a free-license Server Application, Server Application must be work with J2EE platform. Database shall be relational and communication mechanism shall be using a free library for data persistense. Application access Google's Map library. Applications shall show geospatial ubication of each client. SMEX shall access Daenet's CurrencyServer for request currency exchange rates.

2.3.

User Characteristics

Software Requirement Specification

Date 11/15/2011 11:58:00 AM

Rev 1

Page 4

Software Requirements Specification

The customer is the person who sends money to a beneficiary, from his country to a foreign country. Beneficiary is a person who receive money send by a customer sender. Legal experts The person who analyze and set in the system earn commission allowed by Superintendent of Financial Institutions, and have another responsibility, review and correct constantly changes between country's currencies. Moderator Person who manage transaction between both customers, responsible that each part will receive their respective money.

2.4.

Constraints
SMEX shall have to provide a WEB interface only, standalone interface it is not required. System is not connected with bank information. Moderator shall have to verify externally the money give for each part (customer). Each customer bank account shall be out of the system. Customers shall to verify externally the money in his correspondent bank account. Currency data of each country shall be updated manually; system shall not be able to do it.

2.5.

Assumptions and Dependencies

SMEX shall be independent of any software bank system, and will have a dependence of world currency system.

Software Requirement Specification

Date 11/15/2011 11:58:00 AM

Rev 1

Page 5

Software Requirements Specification

3.

Specific Requirements
3.1. Functional Requirements
Specify required behavior and include parameters such as response times, throughput times, other timing constraints, sequencing, accuracy, capacities, priorities, etc. Customer shall be able to register in the system. Customer shall register personal information: Name and last name. Age. Sex. Country, state, city. Bank name, account number, account type. List of beneficiaries. Customer shall register beneficiarys information: Name and last name. Age. Sex. Country, state, city. Bank name, account number, account type. Customers shall be able to search other customer(s) in a desired country for establish a transaction. Customer shall be able to search other customer(s) by using web form. Customer shall be able to search other customer(s) by using google maps (Geospatial location). Customer shall be able to send a request for exchange money to another customer(s). Customer shall be able to accept the request for exchange money that another customer send to him. Request for exchange money shall be able for less than 5 days, after that the request shall be canceled. Customers shall be able to consult the requests.

Software Requirement Specification

Date 11/15/2011 11:58:00 AM

Rev 1

Page 6

Software Requirements Specification

Customers shall be able to cancel the requests send by themselves. Once moderator verified money is in SMEX's bank account, he shall proceed to finalize the transaction. Currency exchange data shall be updated each hour automatically using Daenet CurrencyServer Web Service. If one customer fails in deposit money, moderator shall be able to cancel transaction.

Software Requirement Specification

Date 11/15/2011 11:58:00 AM

Rev 1

Page 7