Advertisement
Guest User

Untitled

a guest
Jul 15th, 2018
72
0
Never
Not a member of Pastebin yet? Sign Up, it unlocks many cool features!
text 3.79 KB | None | 0 0
  1. Price
  2.  
  3. $200
  4.  
  5. Upfront Payment
  6.  
  7. $100 - When everything described below is finished, the rest of payment must be executed.
  8.  
  9. During this time lapse the internal structure of this project will be developed under the general base that consists of Tutors, Students and Subjects/Courses.
  10.  
  11. General Infrastructure
  12.  
  13. This web application will be built mainly using Laravel's PHP framework to ensure a correct MVC structure that will allow this project development to grow over time, including database migrations, code modularity and a general security layer to prevent any bottlenecks or flaws in the system. MySQL will be used for storage purposes due their ability to provide fast queries and data access. When it comes to front end technology, JavaScript will be used to provide a seamless browser experience.
  14.  
  15. Users
  16.  
  17. Basic user authentication system, with hashed passwords to ensure user's private details are fully secure in this platform. User authentication will be based on e-mail as the primary key so that will be the main communication way between Scholarly and the users. Users could be administrators, but they're only assignable in the database for security reasons.
  18.  
  19. Subjects/Courses
  20.  
  21. Administrators and content creators will be able to define new subjects and courses, assign questions and modify certain settings (exactly, 'Questions Quota' is the amount of correct questions the user must have in order to pass the exam, and 'Questions Display Amount' is the amount of questions to display in a test, these are chosen randomly to add diversity to the exams) to an exam that tutors can attend and prove that they're capacitated enough to teach students about this subject. The subjects structure content are meant to be specific and not generalized, like, for example, Programming subject is general, Web Development is ambiguous while HTML is more specific, and Advanced HTML5 is a lot more specific.
  22.  
  23. Tutors
  24.  
  25. User term is ambiguous for this project, that means that an user can receive classes as a student or give classes as a tutor at the same time. In the case of tutors, they must pass exams in order to prove they're capacitated enough to give classes and teach about a certain subject. They can assign a fixed session cost to charge the users and users can rate them, the tutor's rating and subject capability will be taken in account for the matching algorithm.
  26.  
  27. Tutors will be able to try the exams of any subject, and as long as the subjects exam's quota are fulfilled they will be credited as tutors of that specific area. If they fail to pass the exam, they can attempt to pass it again.
  28.  
  29. Students
  30.  
  31. Students will be able to have sessions with tutors about a specific subject, they will be able to find tutors with a matching algorithm organized by subject and tutors ratings. Once they request a specific tutor, he will be asked to respond to the student's request to provide a class session for him.
  32.  
  33. Search and Matching Algorithm
  34.  
  35. Matching tutors with students. Student has a number of tutors to choose from organized by rating and subject. They can narrow the search using specific keywords (I.E. : Mathematics - Calculus). The matching system will match the said student with a tutor that matches those parameters (I.E.: Subject, Category).
  36.  
  37. General Web Design / Interface
  38.  
  39. The interface will be written using Semantic UI's framework to stay in margin with most recent UX standards, providing a responsive template for all the views required to add functionality to the features listed in this summary. All the resources provided by the client related to Scholarly will be used, and while the contractor has creative freedom to style the website, the client also has a solid and considerable opinion about the website's design and interface.
  40.  
  41.  
  42. Approximate time lapse to complete the previous description: 4-6 weeks
Advertisement
Add Comment
Please, Sign In to add comment
Advertisement