Exchange Rate Calculation System Development
Info: 9640 words (39 pages) Dissertation
Published: 11th Dec 2019
Tagged: Information SystemsTechnology
1. INTRODUCTION
1.1 Purpose of the system:
Employees request the application in which he/she holds his/her savings amount to convert it into the currency of his/her respective country. In order to do that, this application has a scope to check for current currency exchange rates. He/she has to register in ERCS module and can apply for the currency conversion. This application will be used by any bank to compute the value of respective currency and it can change for user specified foreign currency. Then the employee can view his/her required currency converted details.
1.2 Scope:
Scope of the system is to provide Exchange Rate Calculation System. This application is being developed only for the purpose of Currency Conversion and it is developed in such a way that it makes the user to convert his/her savings to their respective foreign currency easily.
Disadvantages:
1.The Administrator(s) has the authority to change the conversion rate.
2. SYSTEM REQUIREMENTS
Fig: Use Cases
Third, a node is a physical component that subsists at runtime and comprises a computational imagination, in general having at least some computer memory and frequently actioning capacity.
Fig: Nodes
Behavioral things are the dynamic parts of UML models. The behavioral thing used is:
Interaction:
An interaction is a behaviour that contains a set of contents changed amidst a set of objects amongst a detail circumstance to achieve a particular aim. An interaction involves an amount of other components, including messages, activity sequences (the behavior invoked by a message, and links (the connection between objects).
Fig: Messages
2. Relationships in the UML:
There are four kinds of relationships in the UML:
Fig: Dependencies
An association is a structural relationship that describes a set associates, a associate being a connecter among objects. Aggregation is a special kind of association, being a structural relationship amongst a whole and its parts.
Fig: Association
A generalization is a specialization/ generalization relationship in which objects of the differentiated component (the child) are commutable for objects of the generalized component (the parent).
Fig: Generalization
A realization is a semantic relationship amongst classifiers, whereas in one classifier assigns a abbreviate that some other word assures to accomplish.
Fig: Realization
6.4.2 UML DIAGRAMS:
1. USE CASE Diagram
FIG 6.4.2.1 USE CASE DIAGRAM
The above diagram is Use Case diagram of our system. It shows the set of actions performed by various users. In our system we have 3 types of users. They are 1) Administrator 2) Registered User and 3) Unregistered User. As described earlier, the content in the Ovals are actions performed in the system and those actors are like symbols represent users in system. Those dashed lines from user to action means users are performing those actions respectively.
2. COMPONENT DIAGRAM
FIG 6.4.2.2 COMPONENT DIAGRAM
A component diagram shows various components invoked in system at time of execution of various functions in the system.
3.Deployment Diagram:
FIG 6.4.2.3 DEPLOYMENT DIAGRAM
The deployment diagram shows the architechture of the system as deployment of software artifacts to deployment targets.
Sequence Diagrams:
FIG 6.4.2.4 SEQUENCE DIAGRAM 1
This shows the sequence of actions performed in cases of loggin into the application and loggin out.
FIG 6.4.2.5 SEQUENCE DIAGRAM 2
This sequence diagram shows the sequence of actions performed when the conversion takes place.
FIG 6.4.2.6 SEQUENCE DIAGRAM 3
This sequence diagram shows the sequence of actions performed in order to enter registration details of new users and to submit the registration and add the new user details to the database used.
7. SYSTEM TESTING
The motive of testing is to find out errors. Testing is the sequence of trying to find out every possible fault or weakness in a work product. It gives a way to check the functionality of components, sub-assemblies, assemblies and/or a finished product It is the process of utilizing software with the intention of ensuring that the Software system meets its requirements and user expectations and doen’t fail in an deniable manner. There are various types of tests. Each test type defines a specific testing requirement.
7.1 TYPES OF TESTS
1. Unit testing
Unit testing includes the design of test cases that validate that the internal program logic is working correctly, and that program inputs produce valid and required outputs. All decision branches and internal code flow should be checked. It is the testing of each and every software units of the application . It is done after the completion of an individual unit before integration. This is a structural testing, that depends on understanding of its creation and is invasive. Unit tests perform primary tests at component level and test a particular business process, application, and system configuration. Unit tests check for each unique path of a business process functions accurately to the documented requirements and contains clearly defined inputs and expected results.
2. Integration testing
Integration tests are structured to test integrated software components to check if they actually run as one single program. Testing is event driven and is more bothered about the primary outcome of screens or fields. Integration tests depict that despite the fact that the components were individually satisfied, as shown by successfully unit testing, the combination of components is correct and homogeneous. Integration testing is specially aimed at finding out the problems that come up from the combination of components.
3. Functional test
Functional tests gives systematic demonstrations that functions tested are obtained as specified by the business and technical requirements, system documentation, and user guides.
Functional testing concentrates on the following items:
· Valid Input : recognised classes of valid input must be accepted.
· Invalid Input : recognized classes of invalid input must be rejected.
· Functions : recognised functions must be executed.
· Output : recognized classes of application outputs must be exercised.
· Systems/Procedures: interfacing systems or procedures must be implored.
Organization and preparation of functional tests is concentrated on requirements, key functions, or special test cases. In addition, systematic coverage involved to identify Business process flows; data fields, predefined processes, and successive processes must be appraised for testing. Before functional testing is completed, additional tests are found out and the effective value of current tests is determined.
4. System Test
System testing checks that the whole integrated software system meets requirements. It tests a configuration to check the known and predictable results. An example of system testing is the configuration oriented system integration test. System testing is based on process descriptions and flows, focusing pre-driven process links and integration points.
5. White Box Testing
White Box Testing is a testing in which the software tester has resourceful knowledge of the internal workings, architecture and language of the software, or at least its purpose. It is purposeIt is used to check areas that can’t be reachedand tested from a black box level.
6. Black Box Testing
Black Box Testing is checking the software without any understanding of the internal functions, design architecture or language of the module being tested. Black box tests, as most other kinds of tests, must be written from a most reliable source document, such as specification or requirements document, such as specification or requirements document. It is a testing in which the software under test is considered, as a black box .You cannot “see” inside the box. The test gives inputs to the software and responds to outputs without bothering about how the software actually works.
7.2 Unit Testing:
Unit testing is usually performed as part of a combination of code and unit test phases of the software lifecycle, inspite of it it is not uncommon for coding and unit testing to be conducted as two distinct phases.
Test procedure and approach
Field testing will be conducted manually and functional tests will be written in detail.
Test objectives
• All field entries must function correctly properly.
• Pages must be operated from the indicated link.
• The initial screen, messages/promts and responses/outputs must not be delayed.
Features to be tested
• Verify that the inputs are of the appropriate format
• No duplicate/equivalent inputs should be allowed
• All links should take the user to the correct specified page.
7.3 Integration Testing
Software integration testing is the progressive integration testing of two or more integrated software components on a single platform to produce errors caused by interface flaws. The task of the integration test is to validate that components or software applications, e.g. components in a software system or – one step up – software applications at the company level – interplay without fail.
Test Results: All the test cases mentioned above passed successfully. No flaws encountered.
7.4 Acceptance Testing
User Acceptance Testing is a crucial phase of any project and requires noteworthy participation by the end user. It also safeguards that the system meets the functional requirements.
Test Results: All the test cases mentioned above passed successfully. No flaws encountered.
8. OUTPUT SCREENS
FIG 8.1 MAIN HOME PAGE
FIG 8.2 USER LOGIN PAGE
FIG 8.3 USER LOGIN CREDENTIALS PAGE
FIG 8.4 ADMIN LOGIN PAGE
FIG 8.5 USER HOME PAGE
FIG 8.6 USER DETAILS PAGE
FIG 8.7 USER EDIT DETAILS PAGE
FIG 8.8 CONVERSION PAGE
FIG 8.9 CONERSION PAGE WITH CONVERTED AMOUNT
FIG 8.10 VIEW EXCHANGE RATE CHART PAGE
FIG 8.11 REGISTRATION PAGE
FIG 8.12 CONTACT US PAGE
FIG 8.13 ABOUT US PAGE
FIG 8.14 ADMIN HOME PAGE
FIG 8.15 ADMIN VIEW USERS PAGE
FIG 8.16 ADMIN’S UPDATING CURRENCY RATE PAGE
FIG 8.17 FOR FORGOT PASSWORD
FIG 8.18 MOBILE NUMBER ENTERED IN FORGOT PASSWORD POPUP
FIG 8.19 SECURITY QUESTION IN FORGOT PASSWORD POPUP
FIG 8.20 PASSWORD OBTAINED
9. CONCLUSION
This application helps employees to convert their savings into homeland currency. The users can create ids and link their bank accounts to their id. This would make it easy for the user to have an overall idea about his savings. The admin handles the currency rates and has a record of the registered users and their details.
10. BIBLIOGRAPHY
Sites references Made From:
1)https://msdn.microsoft.com/en-us/library/h43ks021(v=vs.110).aspx
2)http://www.codeproject.com/Articles/1564/ADO-NET-Programmer-s-Reference-Chapter-COM-Inte
3) http://www.informit.com/guides/content.aspx?g=dotnet&seqNum=72
4) http://www.proitonlinetraining.com/online-asp-dot-net-training.html
5)http://msdn.microsoft.com/en-us/library
6)http://www.xe.com/currencyconverter/
2.1 H/W System Configuration:-
Processor - Core 4 duo
Speed - 2.5 GHz RAM - 2 GB(min) Hard Disk - 70 GB Key Board - Standard Windows Keyboard Mouse - Two or Three Button Mouse Monitor - SVGA2.2 S/W System Configuration:-
Operating System : Windows95/98/2000/XP Software : Visual Studio 2010 Database Connectivity : MySQL. 2.3 MODULES OF THE SYSTEM- Rate
- Convert
- Get rates
- Get currency
- ECONOMICAL FEASIBILITY
- TECHNICAL FEASIBILITY
- SOCIAL FEASIBILITY
4.1 .NET
The .NET Framework (pronounced dot net) is a software framework acquired by Microsoft that runs mainly on Microsoft Windows. It consists a big class library known as Framework Class Library (FCL) and has language ability(each language can use code written in other languages) across various programming languages. Programs composed for .NET Framework carry out in a software environment (as contrested to hardware environment), acknowledged as Common Language Runtime (CLR), an application virtual machine that allows services such as protection, memory management, and exception handling. FCL and CLR together constitute .NET Framework. 4.2 Design Goals For .NET:- Leverage current ActiveX Data Objects (ADO) knowledge.
- Support the n-tier programming model
- Integrate XML support
- Carry data about past actions, present condition or expulsions of the
- Signal crucial cases, chances, troubles, or admonitions.
- Activate an action.
- Affirm an action.
- Visualizing
- Specifying
- Constructing
- Documenting the artifacts of a software intensifier system.
- Things
- Relationships
- Diagrams
- Structural things
- Behavioral things
- Grouping things
- Annotational things
| Window |
| Origin Size |
| open() close() move() display() |
Fig: Classes
Second, a use case is a description of set of succession of accomplishes that a system does that affords an evident result of assess to detail actor.
Fig: Use Cases
Third, a node is a physical component that subsists at runtime and comprises a computational imagination, in general having at least some computer memory and frequently actioning capacity.
Fig: Nodes
Behavioral things are the dynamic parts of UML models. The behavioral thing used is:
Interaction:
An interaction is a behaviour that contains a set of contents changed amidst a set of objects amongst a detail circumstance to achieve a particular aim. An interaction involves an amount of other components, including messages, activity sequences (the behavior invoked by a message, and links (the connection between objects).
Fig: Messages
2. Relationships in the UML:
There are four kinds of relationships in the UML:
- Dependency
- Association
- Generalization
- Realization
Fig: Dependencies
An association is a structural relationship that describes a set associates, a associate being a connecter among objects. Aggregation is a special kind of association, being a structural relationship amongst a whole and its parts.
Fig: Association
A generalization is a specialization/ generalization relationship in which objects of the differentiated component (the child) are commutable for objects of the generalized component (the parent).
Fig: Generalization
A realization is a semantic relationship amongst classifiers, whereas in one classifier assigns a abbreviate that some other word assures to accomplish.
Fig: Realization
6.4.2 UML DIAGRAMS:
1. USE CASE Diagram
FIG 6.4.2.1 USE CASE DIAGRAM
The above diagram is Use Case diagram of our system. It shows the set of actions performed by various users. In our system we have 3 types of users. They are 1) Administrator 2) Registered User and 3) Unregistered User. As described earlier, the content in the Ovals are actions performed in the system and those actors are like symbols represent users in system. Those dashed lines from user to action means users are performing those actions respectively.
2. COMPONENT DIAGRAM
FIG 6.4.2.2 COMPONENT DIAGRAM
A component diagram shows various components invoked in system at time of execution of various functions in the system.
3.Deployment Diagram:
FIG 6.4.2.3 DEPLOYMENT DIAGRAM
The deployment diagram shows the architechture of the system as deployment of software artifacts to deployment targets.
Sequence Diagrams:
FIG 6.4.2.4 SEQUENCE DIAGRAM 1
This shows the sequence of actions performed in cases of loggin into the application and loggin out.
FIG 6.4.2.5 SEQUENCE DIAGRAM 2
This sequence diagram shows the sequence of actions performed when the conversion takes place.
FIG 6.4.2.6 SEQUENCE DIAGRAM 3
This sequence diagram shows the sequence of actions performed in order to enter registration details of new users and to submit the registration and add the new user details to the database used.
7. SYSTEM TESTING
The motive of testing is to find out errors. Testing is the sequence of trying to find out every possible fault or weakness in a work product. It gives a way to check the functionality of components, sub-assemblies, assemblies and/or a finished product It is the process of utilizing software with the intention of ensuring that the Software system meets its requirements and user expectations and doen’t fail in an deniable manner. There are various types of tests. Each test type defines a specific testing requirement.
7.1 TYPES OF TESTS
1. Unit testing
Unit testing includes the design of test cases that validate that the internal program logic is working correctly, and that program inputs produce valid and required outputs. All decision branches and internal code flow should be checked. It is the testing of each and every software units of the application . It is done after the completion of an individual unit before integration. This is a structural testing, that depends on understanding of its creation and is invasive. Unit tests perform primary tests at component level and test a particular business process, application, and system configuration. Unit tests check for each unique path of a business process functions accurately to the documented requirements and contains clearly defined inputs and expected results.
2. Integration testing
Integration tests are structured to test integrated software components to check if they actually run as one single program. Testing is event driven and is more bothered about the primary outcome of screens or fields. Integration tests depict that despite the fact that the components were individually satisfied, as shown by successfully unit testing, the combination of components is correct and homogeneous. Integration testing is specially aimed at finding out the problems that come up from the combination of components.
3. Functional test
Functional tests gives systematic demonstrations that functions tested are obtained as specified by the business and technical requirements, system documentation, and user guides.
Functional testing concentrates on the following items:
· Valid Input : recognised classes of valid input must be accepted.
· Invalid Input : recognized classes of invalid input must be rejected.
· Functions : recognised functions must be executed.
· Output : recognized classes of application outputs must be exercised.
· Systems/Procedures: interfacing systems or procedures must be implored.
Organization and preparation of functional tests is concentrated on requirements, key functions, or special test cases. In addition, systematic coverage involved to identify Business process flows; data fields, predefined processes, and successive processes must be appraised for testing. Before functional testing is completed, additional tests are found out and the effective value of current tests is determined.
4. System Test
System testing checks that the whole integrated software system meets requirements. It tests a configuration to check the known and predictable results. An example of system testing is the configuration oriented system integration test. System testing is based on process descriptions and flows, focusing pre-driven process links and integration points.
5. White Box Testing
White Box Testing is a testing in which the software tester has resourceful knowledge of the internal workings, architecture and language of the software, or at least its purpose. It is purposeIt is used to check areas that can’t be reachedand tested from a black box level.
6. Black Box Testing
Black Box Testing is checking the software without any understanding of the internal functions, design architecture or language of the module being tested. Black box tests, as most other kinds of tests, must be written from a most reliable source document, such as specification or requirements document, such as specification or requirements document. It is a testing in which the software under test is considered, as a black box .You cannot “see” inside the box. The test gives inputs to the software and responds to outputs without bothering about how the software actually works.
7.2 Unit Testing:
Unit testing is usually performed as part of a combination of code and unit test phases of the software lifecycle, inspite of it it is not uncommon for coding and unit testing to be conducted as two distinct phases.
Test procedure and approach
Field testing will be conducted manually and functional tests will be written in detail.
Test objectives
• All field entries must function correctly properly.
• Pages must be operated from the indicated link.
• The initial screen, messages/promts and responses/outputs must not be delayed.
Features to be tested
• Verify that the inputs are of the appropriate format
• No duplicate/equivalent inputs should be allowed
• All links should take the user to the correct specified page.
7.3 Integration Testing
Software integration testing is the progressive integration testing of two or more integrated software components on a single platform to produce errors caused by interface flaws. The task of the integration test is to validate that components or software applications, e.g. components in a software system or – one step up – software applications at the company level – interplay without fail.
Test Results: All the test cases mentioned above passed successfully. No flaws encountered.
7.4 Acceptance Testing
User Acceptance Testing is a crucial phase of any project and requires noteworthy participation by the end user. It also safeguards that the system meets the functional requirements.
Test Results: All the test cases mentioned above passed successfully. No flaws encountered.
8. OUTPUT SCREENS
FIG 8.1 MAIN HOME PAGE
FIG 8.2 USER LOGIN PAGE
FIG 8.3 USER LOGIN CREDENTIALS PAGE
FIG 8.4 ADMIN LOGIN PAGE
FIG 8.5 USER HOME PAGE
FIG 8.6 USER DETAILS PAGE
FIG 8.7 USER EDIT DETAILS PAGE
FIG 8.8 CONVERSION PAGE
FIG 8.9 CONERSION PAGE WITH CONVERTED AMOUNT
FIG 8.10 VIEW EXCHANGE RATE CHART PAGE
FIG 8.11 REGISTRATION PAGE
FIG 8.12 CONTACT US PAGE
FIG 8.13 ABOUT US PAGE
FIG 8.14 ADMIN HOME PAGE
FIG 8.15 ADMIN VIEW USERS PAGE
FIG 8.16 ADMIN’S UPDATING CURRENCY RATE PAGE
FIG 8.17 FOR FORGOT PASSWORD
FIG 8.18 MOBILE NUMBER ENTERED IN FORGOT PASSWORD POPUP
FIG 8.19 SECURITY QUESTION IN FORGOT PASSWORD POPUP
FIG 8.20 PASSWORD OBTAINED
9. CONCLUSION
This application helps employees to convert their savings into homeland currency. The users can create ids and link their bank accounts to their id. This would make it easy for the user to have an overall idea about his savings. The admin handles the currency rates and has a record of the registered users and their details.
10. BIBLIOGRAPHY
Sites references Made From:
1)https://msdn.microsoft.com/en-us/library/h43ks021(v=vs.110).aspx
2)http://www.codeproject.com/Articles/1564/ADO-NET-Programmer-s-Reference-Chapter-COM-Inte
3) http://www.informit.com/guides/content.aspx?g=dotnet&seqNum=72
4) http://www.proitonlinetraining.com/online-asp-dot-net-training.html
5)http://msdn.microsoft.com/en-us/library
6)http://www.xe.com/currencyconverter/
Cite This Work
To export a reference to this article please select a referencing stye below:
Reference Copied to Clipboard.
Reference Copied to Clipboard.
Reference Copied to Clipboard.
Reference Copied to Clipboard.
Reference Copied to Clipboard.
Reference Copied to Clipboard.
Reference Copied to Clipboard.
Related Services
View all
Related Content
All TagsContent relating to: "Technology"
Technology can be described as the use of scientific and advanced knowledge to meet the requirements of humans. Technology is continuously developing, and is used in almost all aspects of life.
Related Articles
DMCA / Removal Request
If you are the original writer of this dissertation and no longer wish to have your work published on the UKDiss.com website then please: