[SOLVED] C graph EECS3421 A3

$25

File Name: C_graph_EECS3421_A3.zip
File Size: 178.98 KB

5/5 - (1 vote)

EECS3421 A3

Requirements:

There are three user roles that interact in an academic conference management system:

Program Committee Chair (or PC Chair), which oversees the enactment, coordination and monitoring of the necessary tasks.
PC

Regular Program Committee Member (or Reviewer), which evaluates the overall quality of a paper that usually falls in his or her area of expertise.

Contact Person (or Author), which submits documents (papers) of recent research.

Each of the user roles can register to the system by providing a login name, email and password information. Once logged in, they can provide further information about their profile, such as real name and demographics (e.g., institute they belong to, telephone, address, etc.). Reviewers can provide further information about their topics of expertise to help the PC Chair to assign them research papers that they are capable of reviewing.
PC

The organization of a conference might be separated in four main phases; setup, submission, reviewing and decision phase, as follows:

Setup phase: During the setup phase, the PC Chair provides functional information about the conference such as:
PC
o defining administrative conference information (dates, description, etc.)

o defining the topics of the conference (each conference has several topics)

o defining additional PC chairs (if any)
PC
o defining the program committee members

o defining the review form (each conference has a review form that reviewers use to submit their assessment)

o defining specific administrative settings (e.g., what is the number of reviewers assigned per paper?)

Submission phase: During the submission phase, authors submit papers. For an author to submit a paper he must first create an account to the conference. An author can submit more than one research paper to a conference. The submission of a paper is a three-step process. First the author submits the abstract of a paper along with information about at least the paper title, co-authors, and topics of the conference that the paper falls into. Then, he uploads the full version of the paper. Finally, if the paper is eventually been accepted, then the author would need to upload the camera-ready paper as well. During the submission, authors have also the option to provide information about conflicts of interest (COI). A COI occurs when a co-author of the submitted paper participates to the same conference as a reviewer.
COI COI

Reviewing phase: During the reviewing phase, each submitted paper goes through a reviewing process, where the program committee makes suggestions about which papers are accepted or rejected to appear in the conferences proceedings. Decisions are based on at least several reviews per paper, so one of the tasks of the PC Chair is to assign each paper to a number of knowledgeable reviewers (usually 3). To help in the assignment task, reviewers are asked to define preferences to specific submitted papers through a bidding process and by expressing interest to review papers that fall on specific topics of the conference.
PC3

Publishing/Decision phase: During the decision phase, the PC Chair makes decisions about whether a paper should be accepted or rejected based on the reviews submitted by reviewers about each paper. A notification letter is then sent to the author for notifying them about the outcome of their submission.
/PC

Part A [10%]: A detailed description of the assumptions you made about the systems functionality (minimum 10 assumptions, maximum 1 page).
(101)
ERaB
Part B [40%]: An Entity Relationship Diagram (ERD) of the system. Do not include any isa relationships or weak entities (these should be restructured to a final ERD). Your diagram should be computer-generated and not handwritten AND/OR scanned. You can choose to follow any of the notation conventions used in the slides but need to be consistent.
(ERD)isa(ERD)/
Part C [40%]: A translation of your ERD to a Relational Schema.
ERD
Part D [10%]: A definition of your Relational Schema following the PostgreSQL syntax.
PostgreSQL

Reviews

There are no reviews yet.

Only logged in customers who have purchased this product may leave a review.

Shopping Cart
[SOLVED] C graph EECS3421 A3
$25