The IRMA Community
Newsletters
Research IRM
Click a keyword to search titles using our InfoSci-OnDemand powered search:
|
UML 2.0 in the Modelling of the Complex Business Processes of Reporting and Control of Financial Information System
Abstract
The General Inspectorate of Financial Information is instituted under the Ministry of Finance. Its duty is to counteract bringing into financial circulation pecuniary assets derived from illegal sources and to intercept any possible signs of money laundering. The procedure requires institutions such as banks and insurance companies to forward information of “over-the-limit” transactions in which the amounts involved exceeds the value specified by the Ministry. The efficiency of collecting information about these transactions is actually working, and is determined to a large extent by the speed and efficiency of the information systems in particular institutions responsible for those issues. The chapter discusses and analyses problems associated with the sending information about such transactions by the institution under such obligation. It lays out the range of possibilities opened up by the Unified Modeling Language (UML), which constitutes a universal tool for exchanging information within IT groups and specifying complex business processes. The potential of the language lies in its numerous extensibility mechanisms, which allow the application of various stereotypes, depending on the area given. The chapter also emphasizes significance of the CASE tool, which makes it possible to control and create UML diagrams. Programs of the CASE type are also able to generate a skeleton code used subsequently by programmers during implementation.This chapter includes an analysis and design of a system with a task of improving the efficiency of the information forwarding process by the institutions under obligation so that the criteria laid down by law are met. The description of the system has been created in accordance with the specifications of UML 2.0 and - based on many diagram types and the architecture - the business processes that it extends to and the database structure required to collect information about transactions are set forth. Thanks to the application of use cases the main functionality of the system is defined: searching for and bringing together particular transactions followed by transformation and the dispatching of reports. Complex business processes are presented by corresponding activity and interaction diagrams. The architecture and the placement of the system within the structure of the organization, however, are depicted with the help of structure diagrams such as class, component and deployment diagrams. The use made of the extensibility mechanisms of UML merits attention here. The database stereotype presented in the work made it possible for the database to be designed at the level of implementation, and the functionality of the CASE tool enabled the complete software script to be compiled on this basis.
Related Content
|
Babita Srivastava.
© 2024.
21 pages.
|
|
Sakuntala Rao, Shalini Chandra, Dhrupad Mathur.
© 2024.
27 pages.
|
|
Satya Sekhar Venkata Gudimetla, Naveen Tirumalaraju.
© 2024.
24 pages.
|
|
Neeta Baporikar.
© 2024.
23 pages.
|
|
Shankar Subramanian Subramanian, Amritha Subhayan Krishnan, Arumugam Seetharaman.
© 2024.
35 pages.
|
|
Charu Banga, Farhan Ujager.
© 2024.
24 pages.
|
|
Munir Ahmad.
© 2024.
27 pages.
|
|
|