Skip to content

Third Meeting Minutes

ishraqhossain edited this page Feb 10, 2019 · 2 revisions

Date: 02/05 Time: 4pm Location: Video Call

REQURIEMENTS: -Check the error in main requirement that Mostafa talks about. (done by gorkem) -Finish individual parts for requirements. -Check one last time for any redundancy. UML Diagram: -Finish the UML diagram -Add it to GitHub (class diagram) -Add the screenshot to wiki -Write a text to explain ------------- DEADLINE: TUESDAY NIGHT --------- Persistence Layer: -Individual research -A database hosted on a Postgres DBMS instance associated with a Heroku

  • A persistence layer needs to be developed to access this data from a Java application using (ORM) technologies: Hibernate. -The persistence layer should be compliant with the Domain Model, and it should be able to correctly persist data. ---------- DEADLINE: WEDNESDAY NIGHT ---------- Testing Persistence Layer: -A test suite of the persistence layer needs to be developed to try one read and one write operation foreach class of your domain model (i.e. two test cases for each class). The test suite should demonstrate the application can read and write 1) objects 2) attributes 3) references between objects. The test suite should allow to remove all contents of the database (Clean). ----------- DEADLINE: FRIDAY NIGHT ---------- Building System and Continuous Integration: -A Build system is needed to automate the process of compiling,and packaging for the auto-generated code corresponding to the Java Persistence API. -The project should successfully compile, build and run the test suite of the persistence layer while conforming to the Technological Constraints above. -Every push to the GitHub repository should trigger a build job on Travis CI, which uses the build system (Section 4) to compile and package the push the new version of the application -The build system and the CI specification must conform to the Technological Constraints above. ----- DEADLINE: SATURDAY NIGHT --------- Project Report: -Each group is expected to make use of the issue tracking features on GitHub in order to create and manage the project backlog.Each issue needs to have an assignee to trace core responsibilities within the team. ---------- DEADLINE: SUNDAY NIGHT BEFORE THE SUBMISSION---------

Meeting Duration: 2 hours

Gorkem Yalcinoz