List view
<ins>**General Requirements**</ins> 1. The submission deadline is Monday 27th of march 2023, kl. 23:59. 2. The required materials should be submitted in Blackboard 3. One submission per group. Remember to write the names of all participants in the group. 4. Technical requirements 4.1. Clean CSS. No use of CSS frameworks like Tailwind 4.2. Spring Boot/REST based backend. Each endpoint should have proper authentication/authorization, for example based on JWT and Spring Security. 4.3. Database communication using plain JDBC or Spring JDBC / JPA 4.4. The solution should contain tests. The code coverage shall be at least 50% 4.5. The group should make sure to use CI/CD during development. 4.6.OWASP and universal design principles/techniques should be used in the project 4.7. Session storage can be used to provide short-lived login session on the frontend 5. Documentations requirements (for each module) 5.1. End points (API) must be documented, for example, using Swagger. Note, an explanation of what the endpoints do and what the different attributes are is required. In addition, code must be documented as usual (javadoc). 5.2. System documentation is also a requirement., i.e., documentation that enables a new developer to quickly get the project up and running for testing and further development (architecture sketches/class diagram). Instructions for how to run the project can preferably be done as a README file, while other documentation should be as a PDF. 5.3. Test data that can be used while testing the app, for example, test user credentials, database credentials, etc. 5.4. The prerequisites must be documented if the project/module is dependent on other projects 6. Submission materials. 6.1. A zip file including all the modules/files 6.2. A runnable source code of each project/module. For example • Properly documented Source and Test files. • Configuration files like pom.xml (maven), package.json, Dockerfile, etc. • Flyway or normal DB schema scripts with test data 6.3. Description of how to run tests and get the system running. This should be made easy (for the user) - as a script, docker/maven command or the like.
No due date10. The application shall have a main menu towards top of the screen with relevant menu items
No due date•1/1 issues closed8. There will be two types of user roles a. Normal user - can list, buy/sell items, etc. b. Administrator – can add/update/modify categories, can do other administrative actions
No due date•1/1 issues closed7. Users shall be a. able to register themselves, b. able to edit their profile including credentials 9. A logged-in user(s) a. can add new items, can update, delete, and archive their own listed items only b. can add items into their favorite or bookmarked list. c. can negotiate price on a listed item d. can buy an item listed by other users
No due date•5/5 issues closed5. Upon clicking an icon thumbnail or map marker, an item details page shall be shown. In item details page, a. Shall include information about the item such as item description, price, location, contact information of the seller and so on. b. Shall include pictures gallery of the related item. c. Shall allow the logged-in user to bookmark the item, for example by clicking the bookmark logo displayed on the top-right corner of the items page. d. Shall allow the logged-in user able to contact the user who posted the item, for example via message inbox/dialogue.
No due date•4/4 issues closed1. Listing of items on the main page can be done in scrollable, paginated, and thumbnail (default) view or map view. a. A frontend shall have support for multiple sizes of item thumbnails such as full-width, half-width, quarter-width, double-height, etc. b. The frontend should retrieve items from the backend using APIs c. The backend shall provide APIs for adding, getting, updating, deleting such items. d. The backend APIs should be documented with Swagger. 2. Listed items can be filtered based on, for example, categories, locations etc. 3. Items can be searched based on item descriptions, locations, categories etc
No due date•5/5 issues closed