- The activity involved in the system design activity:
Environment:
CCIS already has in most of the countries as it is not, country-specific it is on the web so anyone can use it. The key feature of the CCIS is that there is an author, reviewer, and editor. An author can come and upload their paper by filling an online form; then, the editor will assign it to the reviewer, and then the final call will be taken by the editor.
External systems included are after the paper is approved there is a proper conference workshop for the authors which have panel sessions and guest presentations along with workshops. Microsoft SQL database is used to store the papers and camera-ready papers, information about the reviewers and authors.
The system is now available for mobile devices and apps also. It supports web technology, and social networking is also involved. For input and output, mobile devices or computers can be used.
The user interface for the CCIS will include a website in which authors can upload the conference paper. Then the editor will assign to the reviewer who will also interact with CCIS only.
Architectural Diagram used in System Design:
- Network Diagram:
- Deployment Diagram:
- Design of Application components:
1.Actors:
- Shared Data:
- Events:
Grouping the use cases by actors who are Author, reviewer, and editor
Use case | User/actor | Domain class | Events | Group |
Create /update Author | Author, Editor | Author_details, Address, online form | Author request to be a new author or update information | A |
Create/Update reviewer | Reviewer, editor | Reviewer_details, Address, information form | Reviewer request to be a new reviewer or update information | B |
Result Paper | Editor | Final_outcome | Editor updates result of paper status | C |
Search reviewer | Editor | List_of_options, Reviewer_details | Editor request for a search for the reviewer | C |
Send email | Automatic by system | Email_details, Author_details, Reviewer_details, outcome. | The application automatically sends mail to the reviewer for submission before the deadline / Author for the introduction of changes before time. | C |
Arrange Conference workshop | Editor | Final_outcome | Editor requests for the final arrangement of the workshop for authors. | C |
Collect camera recording paper | Editor | Author_details, paper_upload | Editor request to the author for the final recording of the paper. | |
Track status of the paper | Editor | Final_outcome | Editor request for paper status | C |
Submit paper | Reviewer | Paper_information | Reviewer submit a final paper after checking | C |
Upload paper | Author | Paper_upload | Author upload paper by an online form | C |
Now grouping has been made it can be further divided into 3-layer architecture which includes:
The data layer, Business layer, and view layer. The system needs to divide it into the layer as it becomes easy for the developer to see each layer and built the system accordingly.
The layer is divided as follows:
View layer contains:
- Author
- Reviewer
- Editor
- Submissions
The business layer contains all the use cases of author and reviewer.
The data layer contains the database of the system, which includes all the information of the authors and reviewers.
- 3-layer architecture:
The 3-layer architecture is important because it speeds up the performance of the developing team as they are now able to integrate it in 3 different zones rather than sticking to one for the coding. Scalability becomes easy as, by different layers, it becomes easy to select on the request received by the web. We can also improve the cached results by dividing it into separate segments for reliability and availability.
System integration showing data flow:
It represents the scene of the process integration. To combine all the parts of the layer, which includes import/export or combines everything to produce a whole or large system data flow. We can divide this into different regions, which include: import/export, Data flow, and all the roles playing by the actors in the system.
Data flow of the system