Figure 1: Use case diagram for Brokerage system
(Source: Created by author)
Analysis of the possible software engineering design principles
The brokerage system can be accomplished using three-tier architecture model. At first, the software engineering design principles are analyzed based on the stakeholder or customer requirements (Shen & Liu, 2013). Then according to the stakeholder’s requirements, a chunk of data collected which is high-level system requirement and those requirements further synthesized and broke down into low-level requirements. Now some essential software engineering principal is determined and listed below:
This system will provide a reliable authentication mechanism.
Every transaction of information interchange should be secure.
Accessing data should be secure and reliable.
This system must allow millions of client’s access and its processing
efficiency should not be compromising (egundo, Herrera & Herrera, 2015).
Any update on the database server must be instantaneous.
The validation of every transaction must be done in very short time.
The expenses of installation must be low (Shen & Liu, 2013).
All graphical user interface must be clear.
This system must be capable of extending its resource at a very low cost.
This system must generate a helpful message for users guide.
The strengths and weaknesses of online Brokerage system
The strength of online Brokerage system are followings:
The system has continuous multiple access without having any interruption.
The system can exchange data over the internet (Chanda et al., 2015).
This internet trading is best for maximizing the internet's potential, and it can easily build the substantial customer base.
This system will make dynamic transformation of the Brokerage industry (Togher, Dunne & Hartheimer, 2014).
The system gained inconceivable resource through cost-effective access to capital market across the world.
This new brokerage system provides highly convenient information analysis (Schoenberg, 2014).
The weakness of online Brokerage system are followings:
The implementation an online Brokerage system, it should be noticed that system generated commissions are based on the size of the order, sometimes few kind of inactivity fees or closing account fees (Sundareswaran, 2014).
This system is tested from the server end; now many possible problems may encounter from the client end.
References
Chanda, J., Kanjilal, A., Sengupta, S., & Bhattacharya, S. (2015, December). Traceability of requirements and consistency verification of UML use case, activity and Class diagram: A Formal approach. In Methods and Models in Computer Science, 2009. ICM2CS 2009. Proceeding of International Conference on (pp. 1-4). IEEE.
Schoenberg, R. (2014). U.S. Patent No. 8,719,047. Washington, DC: U.S. Patent and Trademark Office.
Segundo, L. M., Herrera, R. R., & Herrera, K. Y. P. (2015, September). Uml sequence diagram generator system from use case description using natural language. In Electronics, Robotics and Automotive Mechanics Conference (CERMA 2007) (pp. 360-363). IEEE.
Sengupta, S., & Bhattacharya, S. (2016, June). Formalization of UML use case diagram-a Z notation based approach. In 2006 International Conference on Computing & Informatics (pp. 1-6). IEEE.
Shen, W., & Liu, S. (2013, November). Formalization, testing and execution of a use case diagram. In International Conference on Formal Engineering Methods (pp. 68-85). Springer Berlin Heidelberg.
Sundareswaran, S. (2014). GABE: A Cloud Brokerage System for Service Selection, Accountability and Enforcement (Doctoral dissertation, The Pennsylvania State University).
Togher, M., Dunne, M. F., & Hartheimer, R. (2012). U.S. Patent No. 6,014,627. Washington, DC: U.S. Patent and Trademark Office.
Togher, M., Dunne, M. F., & Hartheimer, R. (2014). U.S. Patent No. 5,375,055. Washington, DC: U.S. Patent and Trademark Office.
