140 likes | 260 Views
Industrial Project: Winter 2011-2012. License Manager. Final Meeting. Team. Supervisors : Nir orlev , bmc software. Ariel kogan , bmc software. Students : Afik avnon , 3 rd year student. Dima rudnik , 4 th year student. Goal.
E N D
Industrial Project: Winter 2011-2012 License Manager Final Meeting
Team • Supervisors : • Nir orlev , bmc software. • Ariel kogan , bmc software. • Students : • Afik avnon , 3rd year student. • Dima rudnik , 4th year student.
Goal • To develop a prototype for a SaaS that will handle the license management task. • Assigning license to employee. • Retrieving license from an employee. • Receive renewal alerts. • Updating license validity upon renewal. • Produce different kinds of reports and graphs : • Licenses by expiration date. • Licenses by company business unit. • Licenses by employee. • Licenses by software.
Methodology • Working Methodology : • 3 Agile cycles. • Weekly meetings. • Source control via riouxsvn.com. • Grails for RAD of client-server app. • LDAP (openDS) as the employee database. • mySQL was used as the application’s database. • Google chart used for graphs drawings. • Balsamic was used to create the web pages mockups. • FastStone capture was used to produce a video demo.
Achievements – Research & Design • License research was conducted. • Licenses types were narrowed down to 5 types. • A video demo was produced and circulated in bmc for feedbacks. • Getting familiar with new technologies : • Grails • LDAP • Google chart • Tomcat
Achievements - Development • A fully operational application, deployable as WAR on tomcat server. • A full connectivity to LDAP was reached. • Authentication is done exclusively by the LDAP data fields. • Four visual reports for license usage analysis. • Simple UI for the end-user. • highly informative UI for the administrator.
Licenses Types Licenses types were narrowed down to 5 types :
Examples • End User UI:
Examples • Administrator UI :
Examples • visual reports:
Deviations • Request Dashboard – improve usability (as a part of the midway error correction). • Demo Video – in order to validate our design. • Event Log for end user - improve usability. • Gradle build - Grails build tool proved to be suffice for our cause. • LDAP connectivity – consumed more time then we evaluate due to plugins problems.
Conclusions • Grails was a wise platform choice : • Class driven DB. • HTML templates. • HTML special tags. • Easy to use state machine (Controllers – GSP). • Designing mockups was proved beneficial. • Agile is an effective working method : • Tight feedback loop. • Frequent communication. • Adjusting features is easier.