Front end model for outreach portal-3.0

[ksripathi]

1) Templates has to be designed with respect to the role (Role Based Templates) 2) Each Role Based Template should consist of 3 sections ( Control Panel, Data Panel and Action Panel). 3) Data model for the views has to be designed. 4) Define/Design the system model for the web application

[MSSoumya]

Minutes of Meeting [2016-07-01]

• Agenda Discuss the front end design with Prof. Devi Prasad
• Attendees Prof. Venkatesh, Prof. Devi Prasad, Thirumal, Sripathi, Soumya.
• Discussion We discussed about the possible inconsistencies that can arise because of concurrency, ie. when multiple users are logged into the system. The subtle differences between single page applications and our application were mentioned. It was pointed out by Prof. Devi that the front end is a view of the projection of the backend state space. The discussion later went on about how the front end and back end must be synchronous. It was demonstrated by Prof Devi with the movie ticket booking example that it need not be a continuous sync, although a timely synchronization of the backend with the front end would work. An important point agreed upon by all was that the front end would have its own states and the event occurring could be state and role based. The meeting continued after Prof. Devi left with the current implementation of the outreach portal as the subject. On further discussion it was realised that the policies for deciding which permissions are to be assigned for which user can all be composed into a a separate modules name guard and output filters. Also, the system information about objects cannot be leaked for the sake of modularization. The output filters were assumed to output a json format in which the conditions for each operation of a particular user are sent as input to the view templates. See the diagram below for better understanding.

• Action Items
  • Have clear input/output boundaries for the modules of the application.
  • Understand how to implement the front end of the application.
  • Identify, design and implement the guard and the output filters.
  • Explore the use of
  • Understand how to implement the view templates in the front end. Identify its dependency is on AngularJs or it can be implemented independently. If so, is an interpreter required on the client side.