RESTful client design and implementation - GoJamie/PWP GitHub Wiki
📑 Chapter summary
In this section your group must design, implement and test a client application that uses the RESTful API implemented by you. The application MUST provide a GUI for a user to control it. If you want to implement a machine-to-machine application please contact the assistants first. If you utilize HTML and JavaScript, it is mandatory that the HTML is contained in static files. It means that your server cannot generate HTML dynamically (using PHP or JSP). All modifications made to the webpage must be done in the client side using javascript. Of course, you can use anchors () to load a new URL. Please, consider the Same Origin Policy" because it might cause problems to your client implementation. It is recommend to host the files in a local HTTP server and not directly in your file system. We will give you more instructions in Exercise 4.It is not mandatory to write code for test the application. Client testing would be considered extra work.
- Learn how to use APIs
- Implement a client that uses the project API
✔️ Chapter evaluation (max 15.5 points)
You can get a maximum of 15.5 points after completing this section. More detailed evaluation is provided after each heading.📑 Content that must be included in the section
You must provide a description of the application. You must clarify which are the goals of the application and why a user would like to use this application. You must also state what is the functionality provided by the RESTful API used by this application.✔️ Evaluation criteria(max 1.0 points)
You can get a maximum of 1.0 points in this section:- The clients purpose is clearly described: 0.75
- Description of the API client not just a GUI: 0.25
📑 Content that must be included in the section
Provide a use case diagram of your application. For each case, specify which is the API resource/s that cover the given functionality✔️ Evaluation criteria(max 2.0 points)
You can get a maximum of 2.0 points in this section:- Diagram below presents the different use cases and they are correctly explained: 1.25
- Description + diagram shows clearly what functionality of the API the client uses: 0.75
✏️ Write here your text
In the client, we implement 6 different functions, including 4 methods post, put, post and delete. We also implement the identification things by log in and log out.
📑 Content that must be included in the section
Draw a diagram of the client layout. Students can use any software they want to do the sketching. For more professional-like design, students can use any wireframing tool available in Internet. Some of them can be found from http://webdesignledger.com/tools/13-super-useful-ui-wireframe-tools. Pencil is free, open source and easy to use. Other options are Visio and Balsamiq (you need a license). You can also create the UI using a paper and a pencil and scan the resulting drawing.✔️ Evaluation criteria(max 1.5 points)
You can get a maximum of 1.5 points in this section:- Client layout present: 0.5
- UI is stetically pleasant: 1.0
✏️ Add your diagrams here
📑 Content that must be included in the section
Draw the screen workflow of your client (which are the possible screens that you can access from one specific screen?)✔️ Evaluation criteria(max 1.0 points)
You can get a maximum of 1.0 points in this section:- Workflow diagram available. Coherent navigation is coherent 1.0
✏️ Add your diagrams here
💻 TODO: SOFTWARE TO DELIVER IN THIS SECTION
The code repository must contain:- The source code for the client application.
- External libraries. You can also report them in the README.md if the libraries are very big or need to be installed.
- The code for testing the application (if it exists).
- We recommend to include a set of scripts to run your application and tests.
- A README.md file containing:
- Dependencies (external libraries)
- How to setup/install the client
- How to configure and run the client
- How to run the different tests of your client (if you have implemented unit testing)
✔️ Evaluation criteria(max 10 points)
In this section you can get a maximum of 10 points.- Instructions to set up the client and run the tests are provided in the README.md file: 0.5
- this means there should be no undocumented extra steps in running the code/tests!
- The code has clear structure and naming for variables and methods: 1.0
- You have clearly marked which parts of the code are your own work and which is borrowed code: 0.5
- Client is usable and navigation is coherent (no broken links): 1.0
- Demonstrate through a presentation or screenshots that your client fulfills the minimum requirements: 1.0
- Client works as expected: 2.0
- We do not find errors while using the application
- The client uses a different API in addition to using your own API (i.e. finds additional information from somewhere else): 2.0
- For full points the client should utilize at least two different methods from the uniform interfaces OR utilize at least 4 differents API calls.
- For full points the functionality provided by the external API should be integrated in the client functionality and not as an incosistent addition.
- The client is a true hypermedia client (if you are not using an hypermedia API you won't get these points): 2.0
- this means that the client uses the hypermedia links to find URLs, uses forms from the hypermedia to form its requests, follows correctly link relations, workflow is mainly in the server, not the client... etc. If any of these aspects are not considered cannot get full points in this section.
- the ideal client is resistant to changes in the API because it only relies on information it gets from the API in runtime
| Task | Student | Estimated time |
|---|---|---|
| RESTful Client | Team work | 7 hours |
| Client design | Team work | 6 hours |
| Client implementation | Team work | 5 hours |