Hello everyone,

We have upload into assignments a new version of our entity relationship diagram (New ER Diagram m-Billing V4.png).

m-Billing team

Hi,

We have upload into assignments a new version of our entity relationship diagram (New ER Diagram m-Billing V3.png).

Hello everyone,

This is the url to our javadocs, the API of our application, which will be updated as any change is made in our project.

url: http://mlp-vs1.mit.edu/mbilling/javadoc/

Regards,
m-Billing team.

Hi all,

We have upload into assignments a new version of our entity relationship diagram (ER Diagram_m-Billing V2.png). So you guys can check it out.

m-Billing team.

Hi m-Billign team, CD is thinking on the single sign on service and since you are an independent payment service, we think that you nee to provide a SSL connection in order to garantee the security. Besides let me know your requeriments for sign up an secure login. Thanks in advance.

Regards,

Common Denominator

Hi all, yesterday we posted a better explain and detailed document of functionlist but this version consider class develop for concentrate functions. Also we're managing packages to get better division beteween type of classes, this document also contain web services that works with the clases, please have a look of them, if theres any comment or question be free to contact us via the platform or by email at aldoinfanzon@hotmail.com or jmavs21@hotmail
The document is on assignments inside the folder class, function and web service list
See you on meeting ciao

Ok m-Billing thanks for your assumptions under Common Denominator services.

Regards,

Miguel Ugalde

Inputs, outputs of services to provide and to consume

<-- Services to provide -->

*User accounts*
Service we provide but we would like Common denominator to invoque when they executed
1. addUser -> output: answer "true or false" -> input: user details depending on type
2. deleteUser -> output: answer "true or false" -> input: userId
3. update User -> output: answer "true or false" -> input: userId + details depending on type accojnt

*Transfer Credits*
Service that will provided to moma
1. tranferCredits->input: amount, idAccountSender, idAccount Receiver -> output: successful operation

*Simple Login*
Service that will provide to Common Denominator
1. login -> input: userId, password ->output: Login confirmation

<--Services to consume-->

*Quotation*
Service we will consume from Smartlink
1. getListAmountProduct -> inputs: idUser, session -> output: List with the amount of each product (Array)
2. getListPriceProduct -> inputs: idUser, session -> output: List with the price of each product (Array)
3. getListProductName -> inputs: idUser, session -> output: List with the name of each product (Array)
4. getListProductDescription -> inputs: idUser, session -> output: List with the description of each product (Array)
----->>>>Comment this lists cointains a product of name delivery costs that is the cost for the service and anything needed to send the package

*Request Order*
Service that MoMa will provide to us
1. orderGeneration -> input: orderDetails -> output: confirmationDialog, orderNumber

For comments or clarify services please contanct us here or via msnmessenger to aldoinfanzon@hotmail.com || jmavs21@hotmail.com

m-Billing Assumptions

1) m-Billing is a separate platform for mobile payments, providing a service to NextLab akin to the PayPal and Ebay model
2) Agents will create their accounts directly and personally with m-Billing, providing the required documents and deposits
3) SmartLink & Mobilizers will generate a courier charge quotation for the shipper to provide the buyer in order for them to agree on a given final price
4) SmartLink will provide a list of couriers and their respective payments for a given invoice
5) When Common Denominator signs up new users for the NextLab platform, they will either link an existing m-Billing account (with m-Billing login and password) or create a new m-Billing account for that user