ICTAD-OTC is an organization established in 1982 that provides training to construction equipment operators. It faced problems with cost controlling, inefficient management, time lagging in decision making, financial reporting issues, and lack of integration. The presented solution is an ERP system to integrate all departments, save time in decision making, control costs, and efficiently manage decision making. The presenter's roles included UI design, development, system design, and creating web services for communication with external parties like suppliers.
5. ICTAD-OTC Overview
• Was established in 1982.
• Provide training to construction equipment operators.
• Students have so many opportunities locally and
internationally.
6. Problems faced by ICTAD
• Cost Controlling issues
• Inefficiency in Management
• Time lagging in decision making
• Financial reporting issues
• Lack of Integration
7. Current System used in ICTAD
• Entire business process of ICTAD was performing
manually.
9. OUR Solution
• To Integrate all departments
• To save time In decision making
• To Control costs
• To efficiently manage decision making
through OCTAD ERP System
11. My Roles – Finance Module
• Performing SDLC
• Designing user interfaces for Finance Module.
• Engage in development phase.
12. My Roles - System Designer
• Identifying the system architecture
• Determining the software type
• Completing database design
• Designing a reusable application basement
14. My roles - continued
• Create web services for the system.
– Web service to communicate with external parties
such as suppliers.
– Create prototype system for suppliers using PHP.
– Sending purchase request to the remote system of
suppliers.
15. Technologies- Web services
• RESTful web services using HTTP.
– JSON as Communication medium .
• Suppliers System Prototype.
– PHP
– Jquery
– Ajax
– Javascript
17. Technologies
• Programming Language – Java (EE)
• Frameworks
– Spring MVC
• Provide MVC architecture
• Security (user authentication and http session
management)
• Bridge between JSF and Hibernate
• Hibernate session, transaction management
18. – Hibernate
• Database manipulation in ORM manner
• Support many common database languages
• Use HQL and Criteria API
– Java Server Faces (JSF)
• Ease of creating user interfaces
• Rich look in user interfaces
• High Ajax support
• Primefaces library
19. • Tools
– Visual Paradigm
• Drawing UML diagrams
• Drawing ER diagram
• Generate physical database from ER diagram
– Eclipse J2ee IDE
– Apache Maven
• Building tool
• Library repository
– GIT
20. Conclusion
•Extend the Dashboard capabilities.
•Extend communication with external Parties Using
Web services.
•SMS, Email functionality
•Vehicle tracking system
•Mobile app for admins