41
edits
Changes
Jump to navigation
Jump to search
Line 20:
Line 20: + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
Summer of Code/Sugarizer Server Dashboard (view source)
Revision as of 10:28, 23 March 2016
, 10:28, 23 March 2016no edit summary
The development of Server dashboard will help create a user friendly interface through which the user will be able to interact with the Sugarizer server and control various aspects as mentioned in the feature list. This will help the users get up and running with the Sugarizer server quickly and will help in increasing the adoption of the Sugarizer web platform.
The development of Server dashboard will help create a user friendly interface through which the user will be able to interact with the Sugarizer server and control various aspects as mentioned in the feature list. This will help the users get up and running with the Sugarizer server quickly and will help in increasing the adoption of the Sugarizer web platform.
=='''Development Approach'''==
The approach of Evolutionary Prototyping would be followed which will involve following phases:
*'''Phase 1''': Gathering of requirements
*'''Phase 2''': Prototype development based on requirements
*'''Phase 3''': Feedback from the mentor for the developed prototype
*'''Phase 4''': Refinements based on the gathered feedback
This approach will help in making the development easily adaptable to changes in the requirements as well as help in identifying and rectifying bugs in the early development phase hence resulting in a better software at the end of the development cycle.
=='''Technology Stack'''==
For the development of dashboard the following technologies will be used:
*'''Frontend''': HTML5, CSS3, Javascript, Bootstrap framework
*'''Backend''': node.js, mongodb
The use of frameworks like bootstrap will help to build a responsive frontend which will help improve the user experience. The backend being powered by node.js and mongodb will help in better utilization of resources since most of the work will be IO based and the non-blocking IO of node.js will help improve the performance. This will also help in reducing the number of language dependencies the Sugarizer project is based on.
=='''Milestones'''==
===22 April-23 May===
*Bonding with the community
*Gathering the requirements for the project
*Feedback from the mentor
===23 May - 10 June===
*Semester exams
During the exam period the time being devoted to the development will be reduced. To compensate for the same, more tasks will be achieved during the pre and post examination period.
===11 June - 17 June===
*First prototype
*Feedback and improvisation
===18 June - 24 June===
*Second prototype
*Feedback and improvisation
*Submission for mid term evaluation
===25 June - 1 July===
*Feedback and improvisation
===2 July - 14 July===
*Documentation for the dashboard
*Writing test cases
===15 July - 31 July===
*First Beta
*Feedback and bug fixing
===1 August - 7 August===
*Second Beta
*Feedback and bug fixes
===8 August - 15 August===
*Release candidate
*Preparation for final submission
===16 August - 23 August===
*Final Submission
*Deliverable: A dashboard for Sugarizer server
===
=='''About Me'''==
=='''About Me'''==