Answer:
Introduction
The report is about the developing the system for Data Science School which is a Private Registered Training Organization. The RTO specializes in IT & Business courses for international and domestic students. (Bazydlo, Adamski, & Stefanowicz, 2014)
There are lot of manual process which is taking toll on working of the DSS, which now requires the help of the online system that can automate the data entry and registration process. The development of the web based application is done using the requirement analysis, the requirements then being translated to the CURD table to support all the development work. Some of the developed prototype is being shown as screenshots. The case study requirements specifications, the automated system to manage the registration and students data that will overall reduce the manual work along with it will increase the efficiency of the administration and help them to reach their specific deadlines.
Critical Use Cases
Using the requirement elicitation techniques, we can develop the system and figure out the critical Use Cases based on the case study requirements. Using the use-case diagram we would be able to identify the overall functional requirements of the system. The Use Case Diagram is the representation of the interact of the users with the system under development, it shows the different relationships with users and the different use cases under the boundary line of the system under development. In use-case, you can identify the different types of users and cases that going to interact.
The actors in the use case diagram are Student, Staff and Agent. The use cases that have been identified are:
- Login
- SignUp
- Registration
- Academic Info.
- Offers
- Payment
- Course Info.
- Results
- Remuneration
As these Diagrams are quite simple in nature it becomes one of the best tools for the stakeholders to communicate with the development team and system analyzers. This diagram helps in mimicking the exact real-world tool that they are interested in to be designed. Researchers have researched on the necessity of the use-case diagrams but found that use-case conveyed the intended system in much better sense and structure as compared to the any other diagram, the simplicity of the use-case diagram is the reason for the simplest way of communicating with all the stakeholders of the system development. It is said to be that use-case communicate more clearly than class diagrams.
The purpose of the use-case is to provide the high-level view of the system, it conveys all the requirements in such a format that it is understood by all the stakeholders.
CRUD Table
The CRUD table as per the case study is being given below:
|
Student
|
Staff
|
Agent
|
Payment Process
|
Registration
|
CU
|
CRUD
|
CU
|
-NA-
|
Payment
|
UR
|
CRU
|
CU
|
UR
|
Offer
|
R
|
CRUD
|
CR
|
-NA-
|
Report
|
R
|
CRUD
|
R
|
-NA-
|
As per the requirements the prototype was developed and the few of the system process like index page, contact us page etc. have been shown below. For the prototype development, the website was used is www.wix.com, the website provided the tools to develop the overall design and developed. The prototype of the website is ready to be published and can be modified when required to fully functional website.
Conclusions
The current project was developed based on the UML diagrams that were developed, these diagrams presented the clear case on how exactly the system is going to work and how does a prototype is developed with all the required flow of the system.
As the requirement elicitation helped in developing the system, the analysis phase helped in developing the UML diagrams easily and system being shown to work efficiently. The prototype is also a way to grasp the hidden requirements.
There were certain aspects that were found while developing the project:
- Use case diagrams presented the entire case quite clearly and was understandable by all stakeholders
- ERD explained how all the system and its entities are related to each other
- System is now robust and able to handle multiple clients at the same time
- Recruiters can help in referring more students
- The system can now record and manage the data along with that will be able to meet the deadlines.
References
Bazydlo, G., Adamski, M., & Stefanowicz, L. (2014). Translation UML diagrams into Verilog. 2014 7Th International Conference On Human System Interactions (HSI). https://dx.doi.org/10.1109/hsi.2014.6860487
France, R., Dae-Kyoo Kim, Ghosh, S., & Eunjee Song. (2004). A UML-based pattern specification technique. IEEE Transactions On Software Engineering, 30(3), 193-206. https://dx.doi.org/10.1109/tse.2004.1271174
Ju?rjens, J. (2005). Secure Systems Development with UML (1st ed.). Berlin: Springer.
Lank, E., Thorley, J., Chen, S., & Blostein, D. On-line recognition of UML diagrams. Proceedings Of Sixth International Conference On Document Analysis And Recognition. https://dx.doi.org/10.1109/icdar.2001.953813
Maazoun, J., Bouassida, N., & Ben Abdallah, H. (2015). SPL-UML: Software product lines design language. 2015 IEEE/ACS 12Th International Conference Of Computer Systems And Applications (AICCSA). https://dx.doi.org/10.1109/aiccsa.2015.7507109
Rumpe, B. (2016). Modeling with UML (1st ed.). Cham: Springer International Publishing.
Secchi, C., Fantuzzi, C., & Bonfe, M. On the Use of UML for Modeling Physical Systems. Proceedings Of The 2005 IEEE International Conference On Robotics And Automation. https://dx.doi.org/10.1109/robot.2005.1570731