Codez un logiciel

A research institute intends to continue hosting of the famous “Emerging software technologies” Conference in 2016 but only after an innovation process of the conference organization. For this, the institute has approached your company to develop a software system for handling the business processes associated to the conference. Here are the user requirements your company received: The conference has 5 main tracks: Internet technologies, Software Agents, E-Government, Medicine 2.0 and Bioinformatics and should be entirely web-administrated within a site. A user can register as an author or as a reviewer. To send a paper or a review a user must first register online, that is create an account supplying his personal data, email address, password and choice to receive updates. If a user registers as a reviewer, he/she must also choose one track for the papers he/she will review. He/She is allowed to access only papers for which he/she is not an author. The registration is done on a web platform supporting multiple conferences and open journals. Once registered there a user can use the credentials at all of those venues, having of course different roles. The papers can be either long papers (8 pages) or short papers (4 pages). A paper consists of a title, authors, keywords, abstract, content, and bibliography. It should be also associated to a track. Any paper has a main author and eventually secondary authors. An author can be the main author for at most one paper for each track. If a user registers as an author, he/she must upload the paper till 15th of June and a notification of paper reception is sent to him/her. On the 16th June the organizers allocate papers to the registered reviewers by matching the paper track with the reviewers’ chosen track and then balancing the matching pairs in order to have 2-3 reviewers for each paper. Then the allocated papers are sent to reviewers by email. Once logged in, the reviewer is shown the list of his/her allocated papers with marking if reviewed or not. The reviewer comments each paper, gives a grade (an integer from 0 to 5) to it, and justifies the grade. During the review the reviewer can temporarily suspend his/her work and resume it later for more times. When he/she decides to submit his/her review, the paper title is cancelled from his/her paper list. On the 16th July the average grade as well as all the reviewers’ comments for the paper are sent to the main author by email. If the average grade is less than 3 the paper is rejected. The first papers, at most 20, in the descending list of papers’ average grades are accepted for each track. For the documentation use the project deliverables table of contents on the site. Propose to the professor what parts of the system should be automatized and, following his input, implement the computer system