CSCI 4140 Advanced Database Systems
Assignment 5 – Demo, Code and Report
DB建模代写 Assignments and projects are structured so that they build upon each other:-Assignment 1 is asking students to demonstrate that students can ···
Context for Assignments and Project DB建模代写
Assignments and projects are structured so that they build upon each other:
-Assignment 1 is asking students to demonstrate that students can good understanding of DB design. And students can
utilize at least one DB management tool to create ER/EER diagram, then convert diagram to the actual tables in a
database.
You can use a simple database management to model the DB.
You need to generate DB modeling diagram by reverse engineering.
You need to generate SQL (DDL and DML) by forward engineering.
-Assignment 2 expands the functionality of the Assignment 1 and makes preparation for the web application implementation of database connectivity. Topics: REST API and JSON.
-Assignment 3 further expands the functionality of your software in Assignment 2 and it is requiring that you use web services (Update-delete-insert) for back-end processing. Besides, you need to utilize trigger or procedure to achieve the data manipulation cross different DB.
-Assignment 4 makes progress further to pick up the REST API constructed by A2 AND A3, THEN CONTRUCT UI BASED ON THE REQUIREMENTS.
-Assignment 5 integrate the implementations of A1-A4, and expands functionality requirements of implement 2-phase committing in distributed environment in which a transaction requires updates performed on independent DBs.
Context for Overall Application Requirements DB建模代写
There is a company, say company called X, that sells parts. The company provides a UI for the client companies to make purchase orders for parts. Company X provides each client company one user account that is used by a client company personnel to make. And retrieve information about a Purchase Order (PO) used by a client company to order parts from X.
(In other words, there is only one user account for a client company that is used by a single user who is an employee of a client company.) Client login credentials consist of a username and a password.
The company X has its own agents/users that are provided with a UI to retrieve and manage purchase orders. Each agent has her/his own user account (credentials are a simple username/password pair).Note that the objective of this assignment is not to produce a complete application, but it is to write a mockup (or partial) application that accesses a DB and to prepare the stage for subsequent assignments that build upon it.
For instance DB建模代写
We shall need different company user agents and different client companies for the purposes of demonstrating the use of transaction management in the following assignments. However, management of the client company info or management of company user agents is not included in specs as it is not germane to the course topics and would result in more coding and time required to complete the assignment, coding that would be more or less the same CRUD operations (create/insert,retrieve/read, update, delete) whether they are for parts, clients, or agent accounts.
In subsequent assignments, you will be expanding the UI to, eventually, support functionality for:
Client companies to fill-in and submit purchase orders and to enquire about their PO states
Company X agents to record processing of purchase orders that includes changes to the state of a purchase order. And if a purchase order is filled, that also includes updating information on the quantity of parts in stock.
Learning Outcomes DB建模代写
As in Assignment 1-4 plus
Integration version (3-tiers application) based on previous assignments.
Consider employing 2 phrase commit protocol on your application. Document 2-PC design and
implementation. (Implementation is optional) (If short of time for implementation, then document
the 2-PC consideration in “Future work” section. )
Understand and use transaction mechanisms when developing applications that support multiple users when accessing the same data in a DB server
Specifications
The rubric includes Software functionality, then Final Report organization and presentation and Demo.
A separate individual evaluation is provided for those team members whose contribution differs from those of the rest of the team.
Grading scheme:
Software – requirements satisfied, repo, etc 40 %
Final report organization, presentation, etc 40 %
Demo 20 % (from July 20th to August 7th)
Individual contribution (It counts when the contribution is worse than expectation)
* The mark obtained here will be, in general, a team-mark obtained by the team in the first three categories. Exceptions will be in cases where unusual individual performance is detected. For instance performance over and above expectations, or lack of contributions. In cases wherein a team member’s contribution is minimal, the overall project mark for that individual will be zero.
Individual contribution is to be determined based on his information and information gathered from the Instructor/TA’s evaluation, Self/Peer and Task evaluation forms.
Demo Requirements
Project Demo Testing DB建模代写
Your team is responsible to schedule the demo of your team with the TA ([email protected]). And the course instructor (please book one hour time-slot). All team members need to be present and. If anyone is unable to attend, I’ll need an advanced written notice (email) with an explanation.
All your project documentation and the task. And self-peer forms needs to need to be submitted at least 12 hours prior to your demo. Recall that the task form is submitted by the team (the form can be found attached to and is submitted to the same assignment box as the project (assignment box ProjGR). While the Self/peer evaluation form is submitted by each team member individually using the assignment box Proj-SelfPeer-Forms (the form, Proj2-Tasks-Form-4140fwin2021.docx, is attached to the same assignment box (Proj-SelfPeer-Form)).
The session will start with a few questions from me regarding your software organization. And completeness (this is the time to acknowledge shortcomings of your software (if any) – if some required functionality is missing or it does not work properly, it needs to be documented. However, this is preferred to your instructor discovering unacknowledged problems/bugs during testing.
Following this DB建模代写
You will need to demonstrate your software using the test sequence shown below. Then, I shall be instructing a member X to test a particular situation/case and while X is inputting data through your UI. I may be asking other members to perform some other activities. Such as listing a purchase order or parts at a particular company.
Recall that the project specs require that you have SQL scripts to create the DB, to seed your DB with content. And to initialize logs (to empty logs). Just in case there are problems, I recommend that you have a backup prepared, meaning. That you can relatively quickly switch (or start quickly) to a backup system.
For efficient testing, please ensure that before the demo starts. There is a different team member logged to each of the companies W, X, Y, and Z. So that I can ask for list of parts at each of the companies and then. Through sharing screen these team members can show me the results when asked.
Testing Sequence DB建模代写
Concurrent Testing of Software for Companies W, X, and Y
Each member, who is logged at one of the companies W, X, and Y, will perform each of the following operations. After each operation, I shall ask one of the members to share a screen and show the results of the operation.
Submission requirements
Your submission should have the usual packaging (front page, TOC (Table of Contents), etc.) and contain the following information: If you strive for A or A+, include an Submission Excellence section that briefly, but succinctly, describes why you should receive A or A+. Recall that in the Dal’s grading scheme, satisfying requirements is in the “good” range (B+ to A-), but not necessarily in “excellent” range. For an A to A+, your work must be in tip-top shape, including your submission format and content. Also, for an excellent range (A+), going over and above the requirements is a plus, but you need to highlight them in this section.
If your DB design is different from the default design, include your ER model (just the diagram created with the MySQL Workbench).
Section describing your software organization
Section describing 2PC utilization on your project.
An Individual Peer-review should be submitted.
Your code should be stored in the FCS git to which you provide your TA and with access privileges (my FCS username is my last name).
For an appeal of your grade, see the syllabus.
CSCI 4140 Advanced Database Systems
Assignment 4 – Rubric
Requirements that DB建模代写
“ … software, the names of your methods/functions/procedures must end with the last three digits of your student ID and the same applies about any parameter of a method/procedure/function” and that
“ … DB must be such that the names of your tables and of the columns must end with the last three digits of your student ID” must be satisfied or else the assignment receives a failure grade and is brought to my attention for a follow-up
Rubric
The rubric is presented by first describing requirements to obtain a C grade range (satisfactory). Meaning that the requirements were not quite met. Then, B range is described, following by the A (Excellent) range. Clearly, any submission that is not satisfactory is below C and will be reviewed.
Evaluation is performed by your TA who forwards it to the instructor who reviews it amends the grades and evaluations if necessary.
In general, if your submission satisfies the requirements and the submission is good or very good in all evaluation categories, the Dal grades
Satisfactory: C‐ to C+ range
The submission has sufficient information to convince the marker that the main objectives of the assignment were more or less satisfied. Documentation organization, presentation and completeness will affect the variations with the range …
Good: B‐ to range B+ range
As above but the functional requirements are satisfied, and all evaluation categories must be classified as good and ariations (range of “mostly good” -> “good” -> “very good” determine which of B-, B, and B+ applies.
Excellent: A‐ to A+ range
As above and software works correctly with submission quality being classified between very good to excellent. Your
marker is impressed with your work. As above but the functional requirements are satisfied, and all evaluation categories must be classif
更多其他：代写作业 数学代写 物理代写 生物学代写 程序编程代写 代写被发现怎么办
