-
Notifications
You must be signed in to change notification settings - Fork 0
Planning Meeting 06.11.2017 (Draft for the Weekly Meeting)
Or Abramovich edited this page Nov 6, 2017
·
1 revision
The product
- Client side: the most flexible & convenient way to implement such solution is a website (client runs in a web browser).
- Server side: dedicated server (Linux OS based).
Languages & frameworks
- Server side application: Java
- UI: Javascript, HTML, CSS (based on Bootstrap template).
- Framework: Spring (to be discussed with Adi).
DB
- Relevant candidates (based on the research): MySQL or MongoDB (to be discussed with Adi).
Features
Must:
- Logger
- Exception handling
- Roles: Student, owner.
- Main dashboard (available for registered and unregistered users). Including distance & time information and filtering & search options.
- Registration form.
- Login form.
- Adding apartment.
- User profile page.
- Comments
- Who is interested.
- Apartment profile & description page.
Nice to have:
- Adding information about public transport
- Another role: admin
- Rent history.
- Prices in the area and other statistics.
Geolocation Service
- Google Maps API
Requirements
- Hosting
- Domain
- Conneting to mLab
- Connecting to Heroku
- How to Run Tests
- DB Server Setup Procedure
- Developer Guide
- Azure Deployment Steps
- Azure DB Deployment Steps
- Introduction to MongoDB
- Introduction to ElasticSearch
- Introduction to Spring
- MongoDB Tutorial
- Introduction to Bootstrap
- Introduction to Amazon S3
- Introduction to Vue.js
- RESTful API Tutorial
- HLD
- Back-end-API
- location review API
- Test Plan
- Sprint 1A Presentation
- Sprint 2A Presentation
- Roommates Report
- Working with the Sockets Server
- Close The Deal Flow Definition
- Sprint 1B Presentation
- Project Poster
- Back end Components Diagram
- Use Cases Diagram
- Deployment Diagram
- Azure Deployment Diagram
- Business Flow