Presentation is loading. Please wait.

Presentation is loading. Please wait.

ONLINE TECHNICAL REPORT SYSTEM Team Crash Course Ryan Ashe, Eileen Balci, James Kirk, Taylor Paschal.

Similar presentations


Presentation on theme: "ONLINE TECHNICAL REPORT SYSTEM Team Crash Course Ryan Ashe, Eileen Balci, James Kirk, Taylor Paschal."— Presentation transcript:

1 ONLINE TECHNICAL REPORT SYSTEM Team Crash Course Ryan Ashe, Eileen Balci, James Kirk, Taylor Paschal

2 System Overview  The system shall be able to have faculty authors and coauthors submit technical reports that will be reviewed by other faculty members selected by the admin.  Approved technical reports will be stored in a repository that can be accessed and viewed by the public.

3 Iteration Overview  In this iteration, we’re adding functionality to the Author and Reviewer Users of the system.  Authors will be able to upload their papers and copy and paste their abstracts to the database for review.  Reviewers will be able to download and review the papers, adding comments for the author to see.  In turn, Authors can view the comments as well as the status of their papers. For this iteration, it is a blind review, authors will not know who the comment came from.  Users will be able to view papers stored in the repository.  Also, the Web Interface (from iteration 1) is being completely redone to better suit the client’s tastes.

4 Iteration Testing Overview  The Author upload features for the paper and the ‘copy and paste’ abstract upload were tested.  The user will browse for a.pdf file to upload and will paste their abstract in its respective field and submit it to the database.  For the character limit in the abstract text field, we’ll be testing for the max amount of characters to be 500 or less.  The Database was checked to see if the text was indeed stored.  For the Reviewer functionality, we tested the comment and download report functionality.  Input for the comment testing was typing in text and modifying the database fields for the Author to view.  Input for downloading reports was simply be having a Reviewer download a report from the database and checking to see if the report was the same as the one from the database.  All features developed in this iteration are first version features with the exception of the web interface which is in its second version.

5 DEMO Website Address https://php.radford.edu/~softeng07/rep/home.php

6 User Stories not Met  NONE!

7 User Acceptance Testing Please go to: Download the document CustAccptTests.doc Here you will have a list of tests you can perform and validate If you have any questions you can the team

8 Some Stuff Coming Up For Phase 3  Admin Functionality!  Admin Free Form Query Functionality and Results Page  Admin Reviewer selection  Admin Paper Approval/Denial  Author & Co-Author Functionality!  Author resubmission/withdrawal  Co-Author’s Full-Author Capabilities  Paper Review Notifications!  To Admin when Review is finished  To Author when Review is finished  And Much More!

9


Download ppt "ONLINE TECHNICAL REPORT SYSTEM Team Crash Course Ryan Ashe, Eileen Balci, James Kirk, Taylor Paschal."

Similar presentations


Ads by Google