Skip to content

Final Report

Jump to bottom
daryne77 edited this page May 19, 2017 · 4 revisions

  • Project Inception

    End Date: 31st March 2017

    • Provide project's general context by defining the scope.

      • Responsibles:
        • Entire team
      • This project means to create an environment to connect the students that need guidance in their educational process with potential tutors.
      • In the first part of the project was very important to define the requirements, scope and clients in order to have a general idea and to develop it in the proper way.

    • Explain the integrated technology and it's purpose.

      • Responsibles:
        • Entire team
      • The technologies that will be used during developing the project will be for backend - Laravel, Eloquent ORM, Composer. For front-end we will use HTML, CSS, JavaScript and some already made plugins based on JavaScript.

    • Decide the application process.

      • Responsibles:
        • Entire team
      • One of the most important part was to decide how will the authentification process work because there are two types of accounts. One for instructors and the other one for students. Also we spoke about what are the most important information that we need about the student/instructor for the database.
      • In this part we established basic parts for the front-end part of the platform:
        • It has to be simple design
        • What can the instructor/student do on the profile page
        • Layout
        • There will be requests page

    • Agree on dates and contents (Milestones and Deliverables).

      • Responsibles:
        • Entire team
      • After we found out which is the deadline we tried to organise the phase of developing the project in a smart way in order to realize almost everything we established in the beggining.
      • When we had a clear idea about the project and after we had discussed everything, each member of the team wrote some parts of the documentation.

Difficulties:

  • At the beggining was hard to imagine a platform with its details that fits on everyone's thoughts.
  • It was complicated to write all the requirements because for this we needed to know exactly what will the project be and what problems it will solve

  • Project Analysis and Planning

    End Date: 7th April 2017

    • Draw Activity Diagrams (Process) and Entity-Relation Diagrams (Database).

      • Responsibles:
        • Elitsa Vrancheva, Berk Morkoç
      • In order for the application to work, since it collects data, it is needed to use database. Our task for these 2 weeks was to think of the best way to connect the different entities so as to avoid data redundancy, which is extremely important for the performance of the application.
      • The people, who were working on this part was Elitsa and Berk. After analyzing the requirements of the project, dividing the entities and finding out the relationship between them, we started to draw the Entity-Relation Diagram using Vertabelo. Since defining the right database is one of the most important thing, we had some hard time defining the right relationships. But after the discussion, everything was clear and with the help of diagram, we managed to visualize the data by ER diagram.

    • Set assumptions and constraints, business rules and development requirements.

      • Responsibles:
        • Alexandra Grama, Adina Țeudan
      • The assumption we set, which is of fundamental importance, is that the user who registers can be either student or instructor, but not both. Since we don’t have enough time to implement the two-role user, for the first version of the project the user can have only one role.
      • The important development requirements we set were defining the roles of every person of the team, how are we going to manage the tasks and what is most important to do and finish.

    • Assign tasks for each team member for the first sprint.

      • Responsibles:
        • George Marashilian, Elitsa Vrancheva
      • Front-end design: Alexandra Grama and Adina Țeudan.
      • Front-end implementation: Elitsa Vrancheva.
      • Translating the database to relational-model to SQL and building the database: Elitsa Vrancheva and Berk Morkoç.
      • Setting up the project and integrating the project’s technology: Elitsa Vrancheva.

  • First Sprint

    End Date: 28st April 2017

    • Front-end design for students and instructors.

      • Responsibles:
        • Design: Alexandra Grama, Adina Țeudan
        • Implementation: Elitsa Vrancheva
      • The layout of the website was designed (pages, structure, fonts, colours, …), then implemented, for the log-in page, register page, then in the accounts of students and instructors.
      • We aimed for simplicity and user-friendliness, so that our website would be intuitive and easy to navigate. We avoided clutter and unnecessary details.
      • During implementation, we also considered the aspect on mobile devices, as most people access the internet from their mobile phones. We used a responsive layout, to ensure a pleasant experience on any type of device.

    • Translate database relational-model to SQL and build database.

      • Responsibles:
        • Elitsa Vrancheva, Berk Morkoç
      • We used the relational-model previously designed in order to translate and build the database upon which our website is relying.
      • As stated in the technological examination, we used Laravel, Eloquent ORM, Composer for the back-end part, and for the front-end we used HTML, CSS, JavaScript and some already made plugins based on JavaScript.

    • Integrate project's technology.

      • Responsibles:
        • Elitsa Vrancheva
      • We created the connection between the back-end and the front-end, in order be able to start working on the functionality of the project.
      • We had to make sure that the components were functioning properly together before moving on to the second sprint.

  • Second sprint

    End Date: 12th May 2017

    • Implement back-end process and upload code.

      • Responsibles:
        • Elitsa Vrancheva, George Marashilian
      • The expected due date was 12th of may is when we should have completed this phase, by then it was 90% percent complete as we have faced a few problems connecting the front-end design along with our back-end architecture, the integration between this and the previous phase went seemingly but our platform (Bootstrap) had some unexpected anomalies that has to do with the CSS; as some back-end functions were being implemented, we had to go back and adapt the design.
      • Nevertheless, The phase has been completed to a margin of incompletion and is set for integration with the next part, the finalization process should be a crucial part to assess the completion of the objectives.

    • Connect Database System to the server.

      • Responsibles:
        • Elitsa Vrancheva, George Marashilian
      • The database was autogenerated by the platform and altered to meet the specifications and preset requirements, the entity relation diagram will be updated, Security wise, we have designed the back-end with logical steps to ensure concurrency and security but we will still have to run the project against a security patching software at some point if/and after launch.

    • Create data and environment for testing.

      • Responsibles:
        • George Marashilian
      • Mock data has been created and can be found here. We expect to alter some features and design elements in the upcoming days after assessing the project and finalizing it.

  • Finalization

    End Date: 19th May 2017

    • Test Project to requirements and constraints.

      • Responsibles:
        • Entire team
      • SmartSchool works on browsers and needs instructors and students. Everybody who wants to use SmartSchool should have a username and password. Each person can create an account that cannot be instructor and student simultaneosly.

    • Discuss features and security with stakeholders.

      • Responsibles:
        • Entire team
      • Firstly, you need to have an account to use SmartSchool. It forces you to choose instructor or student. If you need any help about your lesson you choose student, if you want to help students you choose instructor and you register by filling required lines. Your registration informations will be protected and not shared by SmartSchool. If you are a student you create course(s) request and the instructor who wants to help you contacts you. If you are an instructor you can share your specialized tasks or you can search students.

    • Run project real-time and introduce it to students.

      • Responsibles:
        • Entire team
      • The Project will be worked by stakeholders and we have already introduced it at the top part.

  • Project Presentation

    End Date: 26th May 2017

    • Complete changes and delete testing data.
    • Debug security and patch it
    • Present project to stakeholder.

Clone this wiki locally