This course requires each
student to complete a single-page full-stack web project. Each application is required to perform the
following tasks:
1.
User Registration / Authentication
2.
Perform CRUD operations
3.
Reflect CRUD operations by other users
The students are highly
encouraged to use their own practice assignments as stepping blocks toward
their final project. They are welcome to
use the web for technical help – provided
they give full reference to the source in the comments and in their project
report. The students, however, are not allowed to share code or ideas with each
other. ANY sharing
code will result in a zero for all
students involved no matter who copied from whom. Grading Criteria:
Criteria |
Description |
Points |
Revise d Points |
Idea (Uniqueness
and Potential Demand) |
The idea for the application
should be as much as possible unique but at the same time there be a
potentially high demand for it. A search on Google would should how many applications are
already out there with the same general functionalities. For instance, a search for "Hotel Reservation Web Application" found about 1,680 such application.
The same search for "Space Travel Reservation Web
Application" found zero. Search
results less than or equal 1000 will get 13%. Every 500 over the 1000 will lose 1%. |
15% |
15% |
|
Search results over
7500 will get Zero. Please note that the search must be inside double
quotations. What about the
demand? You have to make the business
case that there will be such a demand. The business justification is worth 2%. Here is the proof for my idea http://www.spacefuture.com/archive/prospect s_of_space_tourism.shtml |
|
|
Using Vuex
|
Using
Vuex for state management |
15% |
15% |
Components Design |
No more than one component
per file. Naming convention: • PascalCase
• Single-used
components be named “The…” e.g.,
“TheHeading.vue” • Closely
named children components with their parents. “TodoList.vue” -> “TodoListItems.vue”
|
10% |
10% |
Application
Comments |
Document
you script by comments |
5% |
5% |
Single-page (SPA) |
Application
should show all changes without reloading the page. |
20% |
30% |
User Interface |
The
application must have a design consistency, which is a predictable
functionality. The Application must
have a user-focused with a minimalist UI design. |
5% |
5% |
Style and Static |
Consistency
in the overall brand of your application
|
5% |
5% |
Application |
|
60% |
70% |
DB Design |
NoSQL
design for the objects of interest. |
5% |
8% |
CRUD scripts |
Scripts
to create, retrieve, update and delete records in MongoDB |
5% |
7% |
MongoDB |
|
10% |
15% |
Performance |
The
students will demonstrate the performance of each of the major tasks
during their presentation. They
will use Chrome Development Tool. The students will upload |
5% |
5% |
Application Technical Document |
Each
application must include a technical document describing its dependencies and
components. |
5% |
5% |
Application User Guide |
Each
application must have a “help” page to guide the user and answer “frequently
asked questions” |
5% |
5% |
Project Total |
|
100% |
115% |
1. If you already don't have one, create a folder named Public under
your project folder
2. Save the project
marketing brochure, Application Technical Document, and User Guide under
the Public folder
3. If you already don't have one, create a folder named Resources
under your project folder
4. Save your project data in JSON format under Resources
folder. For more on JSON visit https://json-schema.org/understanding-json-schema/
You would need to have one document for every
record, you would want to insert into your collections. There should be
one JSON file for each collection.
1.
zip the project folder except for
the node_modules
Get Free Quote!
347 Experts Online