M
Maria Mela
Hello everyone...
Anybody can help me on this project??
Thks for your time...
Requirements Information: of the Card Each card will have a set of
information associated. These information include information of the usuary,
last transactions and balance. Thus for each card, the following information
must exist in the system:
Information Type of Data
Example
N.º Card Int
145
Name Usuary Characters (Max: 255)
"Bruno Silva"
Type Usuary Enumeration {"Pupil", "Employee", "Professor"}
dates Emission Dates
5/12/2006
Balance (Euros) Real
24,55
Last Transactions TRANSACCAO
(To see next table)
Details:
the numbers of the cards will have automatic and to be attributed of
incremental form.
This archetype only needs to keep last the 10 last transactions.
Information of Transaction:
For transaction any use of the card is considered, either it a shipment, a
debit or a transference. The information that must consist on each
transaction is the following one:
Information Type of Data
Example
Data Date
6/12/2006
Type Enumeration {"CRG", "DBT", "TRF"}
DBT
Sum (Euros)
-0,35
New Balance (Euros) Real
24,20
Comments Enumeration {"Bar", "Bookstore",
"Refectory",
"Another one", "Card_<NumCard>"}
Bar
Details:
the Sum will have to be negative whenever to leave money the account.
the New Balance keeps the resultant balance of the transaction.
In shipment case ("CRG") the Comments must contain "Another one".
In transference case ("TRF") the Comments must contain "Card_<NumCard>".
After each transaction the Balance of the card will have to be changed!
Operations on Cards:
The program will have to allow the following operations:
1) To create Card - Being filled all the necessary data of the card.
2) To annul Card - Indicating the number of the card and asking for
cancellation confirmation.
3) To modify Data of Card - Indicating the number of the card and cahnge the
data of the same, except the date of emission.
4) Information of Card - After indication of the card number, the
information of the same it will have to be shown, as well as the last
transactions.
5) To carry through transactions:
.. Shipment - Indicating the amount that will be credited and the
number of the card.
b. Debit - the balance not to allow a debit, the operation will
not have to be efectuada.
c. Transference - Indicating the number of origin card and
destination and asking for confirmation. If the origin account will not have
enough balance for the transference, the operation
will not have to be effected.
Listings
The program will have to allow to generate some general listings:
1) Listing Cards - the cards of the system Will have to be listed all,
indicating in the end the minimum balance, maximum balance and average
balance of all the existing accounts, for statistical effect.
2) Commanded listing of Cards - The same that in the previous operation, but
the choice in the way of ordinance of the listing will have to be given to
the user. The ways are:
.. It dates Emission, Name;
b. Name;
c. Balance, Dates Emission, Name.
3) Listing of Movements - After the introduction of the card number will
have to be created a text filing-cabinet contends the information of the
card and the last efectuados movements. The name of the filing-cabinet will
have to be Card_< N.ºCard>.txt.
4) Transferences between Cards - After the introduction of the card number
will have to be created a text filing-cabinet contends the efectuadas
information of the card, transferences and the information on the involved
cards in the transferences. The name of the filing-cabinet will have to be
Transactions_Card_< N.ºCard>.txt.
Implementation of the Project
Language and Codification will have to be developed using language C.
Anybody can help me on this project??
Thks for your time...
Requirements Information: of the Card Each card will have a set of
information associated. These information include information of the usuary,
last transactions and balance. Thus for each card, the following information
must exist in the system:
Information Type of Data
Example
N.º Card Int
145
Name Usuary Characters (Max: 255)
"Bruno Silva"
Type Usuary Enumeration {"Pupil", "Employee", "Professor"}
dates Emission Dates
5/12/2006
Balance (Euros) Real
24,55
Last Transactions TRANSACCAO
(To see next table)
Details:
the numbers of the cards will have automatic and to be attributed of
incremental form.
This archetype only needs to keep last the 10 last transactions.
Information of Transaction:
For transaction any use of the card is considered, either it a shipment, a
debit or a transference. The information that must consist on each
transaction is the following one:
Information Type of Data
Example
Data Date
6/12/2006
Type Enumeration {"CRG", "DBT", "TRF"}
DBT
Sum (Euros)
-0,35
New Balance (Euros) Real
24,20
Comments Enumeration {"Bar", "Bookstore",
"Refectory",
"Another one", "Card_<NumCard>"}
Bar
Details:
the Sum will have to be negative whenever to leave money the account.
the New Balance keeps the resultant balance of the transaction.
In shipment case ("CRG") the Comments must contain "Another one".
In transference case ("TRF") the Comments must contain "Card_<NumCard>".
After each transaction the Balance of the card will have to be changed!
Operations on Cards:
The program will have to allow the following operations:
1) To create Card - Being filled all the necessary data of the card.
2) To annul Card - Indicating the number of the card and asking for
cancellation confirmation.
3) To modify Data of Card - Indicating the number of the card and cahnge the
data of the same, except the date of emission.
4) Information of Card - After indication of the card number, the
information of the same it will have to be shown, as well as the last
transactions.
5) To carry through transactions:
.. Shipment - Indicating the amount that will be credited and the
number of the card.
b. Debit - the balance not to allow a debit, the operation will
not have to be efectuada.
c. Transference - Indicating the number of origin card and
destination and asking for confirmation. If the origin account will not have
enough balance for the transference, the operation
will not have to be effected.
Listings
The program will have to allow to generate some general listings:
1) Listing Cards - the cards of the system Will have to be listed all,
indicating in the end the minimum balance, maximum balance and average
balance of all the existing accounts, for statistical effect.
2) Commanded listing of Cards - The same that in the previous operation, but
the choice in the way of ordinance of the listing will have to be given to
the user. The ways are:
.. It dates Emission, Name;
b. Name;
c. Balance, Dates Emission, Name.
3) Listing of Movements - After the introduction of the card number will
have to be created a text filing-cabinet contends the information of the
card and the last efectuados movements. The name of the filing-cabinet will
have to be Card_< N.ºCard>.txt.
4) Transferences between Cards - After the introduction of the card number
will have to be created a text filing-cabinet contends the efectuadas
information of the card, transferences and the information on the involved
cards in the transferences. The name of the filing-cabinet will have to be
Transactions_Card_< N.ºCard>.txt.
Implementation of the Project
Language and Codification will have to be developed using language C.