3.2 System features 3.2.1 System Feature - remote access. 3.2.1.

1 Introduction/Purpose of feature Researchers may come from distributed research groups from all over the world. T he idea is to allow them to collaborate on one document regardless of their curr ent location. 3.2.1.2 Stimulus/Response sequence The user demands access to the system from a remote machine. The system provides all its functionality to the user. 3.2.1.3 Associated functional requirements ???????? The req about offline work 3.2.1.3.1 Functional requirement 1 The system should provide web-based interface to the users over World Wide Web. 3.2 System features 3.2.1 System Feature - paper search support. 3.2.1.1 Introduction/Purpose of feature The system should support papers searching process. The researchers should be ab le to define the search protocol that will be used for the searching. It should include what was being searched for, exact search strings, time of search, resul ts as number of papers according to the search terms. The system should also hav e functionality to manage references of selected papers. 3.2.1.2 Stimulus/Response sequence The user fills in the search protocol which is saved to the system and other use rs who collaborate on it are able to see the information when they log into the system and are associated with current project. The user defines the protocol and uses it to search for papers in selected digit al library. The user requests to import the references to the system. The search results are imported to the system. The user wants to attach full text to the references list. He uploads the file t o the system. The system links the file and resource. The user is now able to ac cess the reference via this link. 3.2.1.3 Associated functional requirements 3.2.1.3.1 Functional requirement 1 The system should allow researchers to define the search protocol. 3.2.1.3.1 Functional requirement 2 The system should allow extracting references directly from search results web p age. 3.2.1.3.1 Functional requirement 3 User should be able to attach full text to the references. 3.2 System features 3.2.1 System Feature - papers selection support Researchers decide which papers from previous phase could be usefull in further review. As there may be a big number of papers to go through, it should be possi ble to devide the work among researchers 3.2.1.1 Introduction/Purpose of feature 3.2.1.2 Stimulus/Response sequence The administrator of review assigns selected studies to selected users. He can a ssign all to all or split them manually among researchers. The system registers the changes and assigned work is seen on each user's profile information. The researcher decides on inclusion/exclusion of a paper. He chooses a category from category list to which he wants to assign the paper. The system categorizes the papers in hierarchy given by the categories.

The administrator wants to see distribution of work among researchers. He can se e the list of researchers and numbers of papers assigned to them. The system sho ws whether each paper is already assigned to a category. The user can see the list of papers that were gathered for selection phase. He c an choose from a list of selection measures to calculate the agreement scale. Wh en he select particular metric the system calculates and returns the results to the user. 3.2.1.3 Associated functional requirements 3.2.1.3.1 Functional requirement 1 Primary study selection - assigning studies to researchers (all to all, splittin g) 3.2.1.3.1 Functional requirement 2 System should provide several paper inclusion categories (include, exclude, not sure) 3.2.1.3.1 Functional requirement 3 Calculation of realm between researchers. 3.2.1.3.1 Functional requirement 4 Calculation of agreement on selection - Fleiss, Cohen Kappa 3.2.1.3.1 Functional requirement 5 The metric should be extendable, to add new ones. (by who?)???????????????????? 3.2.1.3.1 Functional requirement 6 See inclusion/exclusion criteria for papers??????????????????? 3.2 System features 3.2.1 System Feature - paper extraction support 3.2.1.1 Introduction/Purpose of feature The system should support the extraction phase of SLR. Traceability between the form and selected papers should be provided. Users should be able to provide att ributes that they want to extract from papers. 3.2.1.2 Stimulus/Response sequence The administrator wants to define a set of attributes that should be extracted f or a set of papers. He specifies the fields. The system saves the template. It i s now available for researchers and they can fill in the information. The administrator of review assigns selected studies to selected users. He can a ssign all to all or split them manually among researchers. The system registers the changes and assigned work is seen on each user's profile information. The user wants to add a comment to the template while doing the extraction. He s pecifies the text which is later on saved by the system and assigned to the extr action form. Other researchers are now able to view the comment. 3.2.1.3 Associated functional requirements 3.2.1.3.1 Functional requirement 1 Extraction - Users should be able to specify attributes which they want to extra ct from the paper. It should be possible to define the extraction form in a very customized way. 3.2.1.3.1 Functional requirement 2 Data extraction - assigning studies to researchers (all to all, splitting) 3.2.1.3.1 Functional requirement 3 Adding comments to the template 3.2 System features 3.2.1 System Feature - reports generation 3.2.1.1 Introduction/Purpose of feature The administrator the a SLR should be able to generate reports on the work. Repo rts should reveal actual progress of work. Given attributes would allow to extra ct particular information.

3.2.1.2 Stimulus/Response sequence The user has a list of reports that he can generate. He selects the report type and select attributes from a multiple choice form that he wants to see. The syst em generates the report and exports the information to a file. 3.2.1.3 Associated functional requirements 3.2.1.3.1 Functional requirement 1 Reports generation on selection, extraction, agreements.

*The system should support collaboration across global distance. *The system should allow researchers to define the search protocol. *The system should manage references. (import from webpage) *It should be possible to attach full text *Users should be able to create projects. (start of SLR) TODO: SEE IF IT"S COVERED IN CREATION OF A PROJECT Assigning roles (researcher, admin) to people. *Primary study selection - assigning studies to researchers (all to all, splitti ng) *System should provide several paper inclusion categories (include, exclude, not sure) *Calculation of realm between researchers. *Calculation of agreement on selection - Fleiss, Cohen Kappa *The metric should be extendable, to add new ones. *See inclusion/exclusion criteria for papers *Extraction - Users should be able to specify attributes which they want to extr act from the paper. It should be possible to define the extraction form in a very customized way. It should be possible to decide if all should extract from the same paper or the work should be split Traceability between the form and paper. it should be able to add your own comments that are not given in the template, s o that you can add more info to the template. Reports generation on selection, extraction, agreements. It should be possible to select attributes for the report.