Govind Anil

a) Worked as a Java Developer and hence, was responsible for

i. Delivering Build Deliverables consisting of Java Task classes, JSP, Java Scripts,
Xml files;
ii. Delivering Design Deliverables like Detailed Technical Design Documents consisting of UML Diagrams, Requirement Traceability Matrix, Component Test Plan, and Application Test Plan.

b) Worked as an Impact Assessment Team member and was responsible for
i. Preparing an end to end architectural design of a new functionality.
ii. Providing estimates for different phases of Software Development Life Cycle.

c) Worked as an Analysis Team member and was responsible for
i. Requirement gathering from client and stake holders
ii. Understanding the functional Specification and identifying if something is amiss.
iii. Delivering Analysis Deliverable like mock screen flows, Theme Documents, RTM.

d) Worked as ‘Release Point Of Contact’ and was responsible for
i. Delivering the code from ‘Development’ stream to ‘Integration’ stream.
ii. Raising the ‘Work Requests’ which includes requesting the Database team to
execute the ‘SQL’ queries provided by me.
iii. Raising ‘Red Boxes’, Co-coordinating with team members if any environment issues.

a) Working as a Design and Build Team Member and hence, responsible for
i. Delivering Design Deliverables like ‘Technical Design’ documents representing
flow in UML diagram, Component Test Plan, Assembly Test Plan.
ii. Delivering Build deliverables using JSF screens, Application flow control XMLs,
Web Service Integration and Hibernate for persisting data.
iii. Preparing design approaches of enhancements using UML diagrams
iv. Helping new joiners and peers by conducting knowledge sharing sessions for
functional knowledge, code walk through and work space setup.

b) Worked as a Tester and hence, responsible for
i. Testing the enhancements and raising an alarm so that minimum number of
defects arises in Integration and User Acceptance Testing.
ii. Writing JUnit Test cases and running Cobertura report for finding Code Coverage.
Make sure that minimum 85% of code base has JUnit Test Cases.

iii. Made sure that number of defects raised within User Acceptance Testing is less than 5.