How often do we utilize our productive capital, productive capital being the equipment that we purchase for daily activities as individuals, businesses, governments, or universities? In Canada, individual households purchase tools only to be used for short periods of time in only parts of the year. What if web technology collectively shifted the narrative of how we utilize this productive capital, opening the idea of building stronger communities through equipment sharing for common benefits. What if we unleashed the capacity of our productive capital to “volunteer” alongside other human volunteers in joint community projects? How might universities be able to optimize equipment use in times of resource constraints? Ultimately, how might a shift in valuing productive capital as having autonomy, as is the trend with autonomous automobiles, potentially increase the productive capacity, competitiveness , and quality of life of our communities and our quest for sustainability? Current software lacks this perspective.
Representation and Data Structures
The Sharing Productive Capital Platform is in a critical position of the sustainable ecosystem. Community users can search the platform just through pressing an icon to find the item they need. While for sharing, they just need to take a picture of the item, and upload to the platform. The platform will pre-fill all the information needed for the item been shared by the users.
Modern enterprise application are built using several components connected to one another, each providing a specific functionality. Components that perform similar functions are generally grouped into layers. These layers are further organized as a stack where components in a higher layer use the services of components in a lower layer. Figure 4 shows the architecture of the Sharing Productive Capital Platform:
Mainly, the platform can be divided into three layers: which are Presentation layer, Business Layer, and Data Access Layer. For presentation layer, step 2 and step 10 (in Figure 4) are located. Service layer has more steps: 3, 6, 8, 9. And data access layer is responsible for the steps, 4, 5, and 7. From left to the right, users send browser Http request through step 1. The Web.UI will look for the right service, which is step 2. Service component requests the DAO component via step 3 and DAO component will query the database through step 4. Meanwhile, DBMS will return the search result. DAO will wrap the result into Java Beans through step 7 and also notify the upper service layer in step 6. Once service layer receive the result and send a response to Web.UI component, and Web.UI component will render the jsp through step 10 and send back to the end users through step 11.
Here you will find my source code in github. https://github.com/darkcar/saskshare
Techniques and Algorithms
To build the working Sharing Productive Capital Platform needs numerous techniques. I utilized the most popular technique in current world. Here, I will list the major ones, and give a short description about each technique.
- Front-end libraries / frameworks: Bootstrap, jQuery, ml5.js.
- Back-end libraries / frameworks: J2EE, Model-View-Controller.