ruby on rails web开发代写: COSC2675 Rapid Application Development

COSC2675 Rapid Application Development

Computer Science and Information Technology School of Science, RMIT

Assignment 2 – Semester 1 2018

Introduction
This assignment is worth 35% towards your final grade. You are required to develop a web

application as specified below. It is designed to: ! Practise your knowledge of Rails development

! Practise testing and debugging

This is a group assignment. A group should not have more than 2 members. Individual submission does not receive any extra marks. By default, both group members receive the same mark unless there is a significant discrepancy in their contributions.

Academic Integrity

The submitted assignment must be your own work. No marks will be awarded for any parts, which are not created by you. More on http://www.rmit.edu.au/academicintegrity.

Plagiarism is treated very seriously at RMIT. Plagiarism includes copying code directly from other students, internet or other resources without proper reference. Sometimes, students study and work on assignments together and submit similar files which may be regarded as plagiarism. Please note that you should always create your own assignment even if you have very similar ideas.

Plagiarism-detection tools may be used for all submissions. Penalties will be applied in cases of plagiarism.

Client Request

This assignment is developed based on the following fictitious message from the school admin team.

Dear Andy

Our school is thinking of building a news website to let everyone share relevant news. RAD students may be able to help as we’ve heard from many that they know how to quickly build a good website from scratch.

There is no formal specification yet. We just want a news-sharing site, which is easy to use and has good look-n-feel, for our staff and students. People with a proper RMIT email address should be able to register to be a user. Do you think we should only allow registered users to post, update and remove news? Viewing the news should not be a problem. Mmm… it would be nice that the site looks like Hacker News. Students and staff can comment on the news and see latest comments from fellow users.

Thank you and talk soon.

RMIT News

In this assignment, you will build a news sharing web application for RMIT. That is kind of a subset of famous hacker news (https://news.ycombinator.com/). For whom is new to Hacker News, it is a social news website focusing on computer science and entrepreneurship. It is run by Paul Graham’s investment fund and startup incubator, Y Combinator. In general, news that can be submitted is defined as “anything that gratifies one’s intellectual curiosity”.

Part 1

Section 1 – Home Page

Your application should meet the following requirements

1. It has a navigation bar with RMIT logo and site name on it
2. The navigation bar must contains at least four hyperlinks
   1. Home – to show the home page
   2. Comments – to show the latest comments (of all news)
   3. Submit – to submit a news (login required)
   4. Login – login or create user account

3. The news content

1. The news posts are sorted by the creation date using Unix timestamps.
2. The headline of a news contains the title and the source of the news (if exists)
   1. By clicking on the source, the user will be redirected to the source website.
   2. The source news text is the domain name of that particular news website.
3. The meta information about each news contains:
   1. The author who submitted the news
   2. The time when the news got submitted
   3. The number of total comments on that news
   4. The text e.g. “25 comments”, is clickable and will take the user to the

      comments page of that news. (see below)

4. The footer

1. API: a link to the API documentation

   (https://github.com/pigfly/RMIT-CSIT-RAD/tree/master/2018_S1/assignment2)

2. About: the makers of your web application

   i. The names of your group members
   ii. The student number of each member.

   iii. Your heroku deployed URL
   iv. Your assignment 2 bitbucket URL

5. Pagination

1. The news home page will show eight news per page
2. The pagination is triggered by pressing the more button

Section 2 – Home Page Pagination

2.3

Requirements:

1. When the more button is clicked, the page will show the next eight news
2. The page’s relative URL is /news?p=#{number} e.g. /news?p=2
3. The page title should be changed into

   Home page #{your_current_pagination_number}

   The page number for the above example is 1.
   The page number is zero indexed, meaning that number for the Home page is 0.

Section 3 – New Comments

3.2

Requirements:

1. The New Comments page shows the latest comments of all news posts.
2. The New Comments page’s relative URL path is /newcomments
3. The New Comments page is sorted by the creation date & time

4. Each comment has two parts:
   1. Headline: include the user who commented on that particular news, the date that

      the comment was created, and the title of the news.

   2. Body: the comment message body
5. The New comments page will show and only show three comments sorted by the creation date.

Section 4 – Comments Per News

4.3

Requirements:

1. The Comments page of each news shows a text area for commenting and all the

   comments related to that particular news. Comments are sorted by date and time.

2. The Comment Per News page’s relative URL path is /item?id=#{id_number}
3. The page title is the same title of the news, which is to be commented on.
4. The comment section has four parts:

a. Headline: the news title

2. Sub header: the creator of the news, the news creation date/time and the total number of comments at present
3. A text area for the commenting
4. A submit button – “add comment”

5. Validation rules for comment messages
   1. Must not be blank
   2. Must be at least 3 characters excluding white spaces, new lines and tabs
   3. Must be less than 1000 characters
6. Banner messages:
   1. If the comment doesn’t pass the validation, show a warning banner message (see

      banner message page in Section 6).

   2. If comment does pass the validation, show a success banner message (see

      banner message page in Section 6) and redirect the user to /newcomments

   3. You can decide the text for both types of banner messages yourself.
7. The list of all comments
   1. It should show all the comments that belongs to this particular news
   2. All the comments that belongs to this particular news should be sorted by creation

      date/time

   3. It should show no comments if there is no comment for that news

Section 5 – Submit

Requirements:

1. The Submit Page allows the user to submit a news
2. The Submit Page’s relative URL path is /submit
3. If the user is not logged in, redirect the user to the login page (/login)
4. The navigation title of this page should be “Submit a news”
5. The submit section has three parts
   1. The text area for the submitted news title (required)
   2. The source of the news (optional)
   3. The submit button
6. Validation rules for the submit text area:
   1. Must not be blank
   2. Must be at least 10 characters (including white spaces, new lines and tabs)
   3. Must be less than 200 characters

   Note: The text area is for entering the news title only. There is no news body.

7. Validation rule for the source of the news

a. Must be a valid URL if the URL is not empty

8. Banner messages

1. If a submission doesn’t pass the validation, show a warning banner message (see

   banner message page in Section 6).

2. If comment does pass the validation, show a success banner message (see

   banner message page in Section 6) and redirect the user to the home page. You can decide the text for both types of banner message yourself.

Section 5 – Login

Requirements:

1. The login page shows the login and creates an account
2. The login page’s relative URL is /login
3. The validation rule for user name
   1. Must not be blank
   2. Can only contain letters, digits, dashes and underscores.
   3. Should be between 2 and 15 characters.
   4. Must be a unique username in the database.
4. The validation rule for password
   1. Must not be blank
   2. Must contain at least one uppercase letter, one special character, one number and one lowercase letter
   3. Must contain at least 10 characters
5. Both username and password must be valid in order to pass the validation
6. Banner messages
   1. If a submission doesn’t pass the validation, show a warning banner message (see

      banner message page in Section 6).

   2. If comment does pass the validation, show a success banner message (see

      banner message page in Section 6) and redirect the user to the home page. You can decide the text for both types of banner message yourself.

Section 6 – Banner Message

Guidelines

• –  Your web application should be mobile friendly
• –  You can use your favourite CSS/HTML style as you wish

Part 2 API
In this part, you will implement your API endpoint for RMIT news.

Overview

This is sample documentation for RMIT News API (RAD course)
Please post your relevant thoughts in canvas if found anything unclear.

URI and Versioning

The first version will have URIs prefixed with http://*.*/v0/ and is structured as described below.

Design

The v0 API is essentially a dump of your database.

It’s not the ideal public API, but it’s the one you can get a taste how RESTful API works internally.

Items

News, comments are just items. They’re identified by their ids, which are unique integers, and live under /v0/item/<id>.

All items have some of the following properties, with required properties in bold:

For example, a news: http://yourownurl/v0/item/8863.json

comment: http://yourownurl/v0/item/2921983.json

another news: http://yourownurl/v0/item/121003.json

Endpoint to implement:

– /v0/item/<id>
o Request Type: GET

o Authentication: None
o Return status code: 200 for OK, 400 for Errors

– /v0/item/create
o Request Type: POST

o Request Body:

o Authentication: None
o Return status code: 200 for OK, 400 for Errors

https://bitbucket.org/