Beruflich Dokumente
Kultur Dokumente
Proposal
March 16, 2016
Julia Butchen
Jamie Carfora
Jay Dattani
Dayton Geddes-Key
Zach Hochstetter
Marissa Serge
Table of Contents
Letter of Transmittal ..... Page 2
Executive Summary ... Page 3
Hello Srikanth,
We have created a written document containing all of the work we have done up to this
point. Enclosed in our proposal, you will find all of the deliverables that we have created as well
as all of the steps that were necessary to complete these deliverables. We have organized our
work based on the order in which they were completed. The sequence in which we completed
these deliverables is important because this is the order that the CIS team that develops the
system should follow in order to ensure all of the details and instructions of the requirements
of the system are met.
Thank you for giving us the opportunity to work on this project with you. We believe
that with your guidance, our team will be able to provide the system that you are looking to
build. We have worked diligently in order to develop a very detailed proposal that will allow
MARGA to be made into a highly functional portal.
Sincerely,
The HRIM Team
Julia Butchen
Jamie Carfora
Jay Dattani
Dayton Geddes-Key
Zach Hochstetter
Marissa Serge
Executive Summary
The HRIM department has asked us to set up the requirements for a system that will be
implemented by the CIS department. Our system will allow an alternative way for scholars to
get their research published into academic journals. The as-is system has many flaws and
potential opportunities for improvement. The MARGA Research Portal, our solution to this
2
problem, will be unlike any other existing system. Through a highly credible reviewing process,
it will ensure that the best articles become published and recognized.
Our research thus far is seen through our created deliverables. The deliverables
included are the building blocks for the platform that will be developed by the Computer
Science team this upcoming fall. They serve as a status update, to keep you and your team
informed on what processes and data are required for the system to be successful and run
according to our clients wants and needs.
In our next phase of the system research and development, we will be creating more
design documents, with clear instructions on what each page requirements are and how each
page will function. We will also be including a data flow diagram, so you can see how the
system will operate in the backend.
Project Objective
The MARGA Academic Portal is a research portal that will revolutionize the way
academic scholars publish manuscripts. It will allow scholars to have their manuscripts
reviewed and published in a much more efficient manner than ever before. The portal will
provide academics with a platform to submit their work to be reviewed by credible reviewers,
all of whom have been approved by the system. It will promote learning by allowing users to
interact and browse through a database full of scholarly work. The goal is for this portal to
become an egalitarian community for all to ultimately participate in.
Project Scope
The mission of the HRIM team is to determine all requirements for the requested
system and create all deliverables so that the team that develops the system has clear
instructions of the visual design of the system, the functionality of the system, and the purpose
of the system.
problem in the research community. Our system will have checks to ensure the same people
are not always reviewing each others articles. Oftentimes, researchers have to review other
articles as a part of their job, but through our research we found that they usually do not want
to do this. Another major benefit of our system is that it will alert users when an article has
been posted matching their expertise and interests, as well as reward users for giving helpful
reviews. This will make users more likely to want to review other users articles. Finally, the
system is going to rate papers based on the quality of their reviews, ensuring that only the best
papers get published.
Deliverables
Week One
Gantt Chart: MARGA Portal Development Scheduling Plan
This is our scheduled project plan, which we have been following to be sure that all of
our required deliverables were completed in a timely and efficient manner.
Week Two
Industry: Academic Research
The current process for getting academic research articles published has a lot of room
for improvement. It starts with the author submitting an article they have written to an
academic journal. From there, the editor then sends it to be reviewed by an expert of their
choosing. This leaves a lot of room for potential collusion. In addition, it is often difficult to
choose who specifically will review each manuscript. Each review needs to be analyzed to
ensure its credibility. This means the review process is often arduous and takes a lot of time.
While the current system is not necessarily broken, there are many ways to improve it and
make the process flow more efficiently.
The MARGA Academic Portal is our proposed solution to the problems mentioned
above. It is a research portal that will allow academic scholars to have their manuscripts
reviewed and published in a much more efficient manner. It will be a portal unlike any of the
other academic portals that currently exist, such as GoogleScholar, ScholarOne, or the
University of Delawares database, Academic OneFile. It will provide academics with a platform
to submit their work to be reviewed by credible reviewers, who have been approved by the
system. The goal is for this portal to become an egalitarian community for all to ultimately
participate in.
This portal will prove to be extremely helpful in the world of research. It will allow
articles to be categorized based on keywords as well as by the expertise level of the author who
wrote it. This is important because research is used every day for so many different reasons,
ranging from medical breakthroughs, to creating new fields of study.
Requirements Definition:
We created an intensive list of requirements that the system needs, which was further
broken down into categories including, Login and Sign-Up Requirements, User as a Scholar
Requirements, User as a Reviewer Requirements, and Article Requirements. These are the four
main entities of the system, and each have a specific set of rules that our client would like them
to be able to do. Here are our requirements, broken down into functional and nonfunctional
requirements:
Login/Sign-Up Requirements
Functional (process & data):
System must ask for required information (i.e. username, email address, name, etc.)
System must generate a pop-up asking user to verify that all information is correct
System must generate a report of the new user request to be sent to faculty member to
be approved or denied
System must generate an email alert informing requested user they are denied access (If NOT
approved)
System must be able to locate all articles written by user (i.e. through Google Scholar)
System must be able to send a new temporary password to the user if they forget their
password (via email)
System must be able to verify the combination of the username and password
User must be able to rate reviews based on helpfulness and constructive criticism
User must be able to rate comments based on helpfulness and constructive criticism
System must be able to parse key terms to formulate expertise level of manuscripts
System must be able to parse key terms to formulate expertise level of author
System must notify reviewers when an article in their area of expertise is posted
User must be able to view Activity Report (history of all manuscripts reviewed)
System must allow for different level badges for highly rated reviewers
System must allow for different level badges for reviewers with n number of articles
reviewed
System must allow for different level badges for reviewers who have been reviewing
for x amount of time
Article Requirements
Functional (process & data):
System must be able to pair manuscripts and reviewers based on a correlation of expertise and
keywords
System must be able to recognize when an Article of Consideration can convert to an Article of
Recognition
System must be able to recognize when an Article of Recognition can be listed as an Article of
Merit
Score will be more weighted when correlation between area of expertise of article and
are of expertise of reviewer is high
Week Three
Work Breakdown Structure:
Our Work Breakdown Structure was used to help us decide what was needed to ensure
all of our information was accurate and detailed. This also helped us to ensure nothing
important was left out. Here is our Work Breakdown Structure:
Level 1: What major, intermediate, or final products/deliverables must be produced to achieve
the projects objectives?
Development Schedule
Requirements Definition
Design Documents
Status Update Proposal
Final Proposal
Level 2: Component Deliverables
Development Schedule
Gantt chart
Project charter
Requirements definition
Interview with Sri
Research on industry
Design Documents
Research current websites
Interview with CIS
Flowcharts of model
Status Update Proposal
Meeting with Sri
Executive Summary
Updated Design Document
Final Proposal
Prepare presentation
Rehearse presentation
Follow-up if needed
Week Four
First Stage Design Documents:
Our design documents are the first stage templates of what the main pages should look
like. Using these templates, an actual website portal will be able to be developed.
11
Homepage logged in
12
13
14
15
16