meta data for this page
  •  

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision 		Previous revision
otsocase2015winter:group3:start [2015/12/11 11:47]
coffee [Features] 		otsocase2015winter:group3:start [2015/12/17 16:00] (current)
coffee [PaavoMobiel]
Line 7: Line 7:
 | Anna Osipova | Code | | Anna Osipova | Code |
  
-App is running here:   +App is running here (if cloud9 server is still up):   
-https://ide.c9.io/lasshi/otso-cc+https://otso-cc-lasshi.c9users.io/ 
 + 
 +whole source and PROPER DOCUMENTATION can be found at git repository: 
 +https://github.com/lasshi/otso-cc   
 + 
 +Link to our course report, which will discuss project in depth is here: 
 +[[https://docs.google.com/document/d/1NsvPyfmmsD1wCs2x39Vm1WNjHJE0ldgjEl0gVZvLLyA/edit?usp=sharing|Google Docs]] or {{:otsocase2015winter:group3:otsocodecampwinter2015.pdf|pdf file}} 
 ===== Idea ===== ===== Idea =====
  
-Our idea was to implement all the three core functionalities for customers, subcontractors and manufacturers. +Local IT company LTC Otso provided us with a case that we had to solve. They had a few criteria what they wanted to see, and we planned to implement them all, since we felt quite confident in our programming skills. We also wanted to make our final application completely functional, with real client - server communication. 
 + 
  
 ===== Features ===== ===== Features =====
  
-**a +In the end we were able to implement all of our planned features, with some extra features. We have functionality for basic customers, subcontractors and manufacturers. The basic logic of the application is that a manufacturer can make an order and assign it to chosen subcontractors. After the work is done, a custom feedback link is sent to the customer as an email, and the given feedback is connected to the relative subcontractor. After this loop has ran a few times, the manufacturer can review their subcontractors based on given feedbacks. Manufacturers can also sort their subcontractors in different orders, to see e.g who has the best ratings. 
-**b+
 ===== Design ===== ===== Design =====
  
Line 25: Line 33:
 Mobile Interface Guidelines Mobile Interface Guidelines
 ===== Screen shots ===== ===== Screen shots =====
 +[[https://github.com/lasshi/otso-cc/blob/master/doc/poster.svg|Poster]]
 +[[https://github.com/lasshi/otso-cc/blob/master/doc/screenshot1.png|ScreenShot]]
 +[[https://github.com/lasshi/otso-cc/blob/master/doc/screenshot2.png|ScreenShot]]
 +[[https://github.com/lasshi/otso-cc/blob/master/doc/screenshot3.png|ScreenShot]]
 +[[https://github.com/lasshi/otso-cc/blob/master/doc/screenshot4.png|ScreenShot]]
 +[[https://github.com/lasshi/otso-cc/blob/master/doc/screenshot5.png|ScreenShot]]
 +[[https://github.com/lasshi/otso-cc/blob/master/doc/screenshot6.png|ScreenShot]]
  
 ===== Technology ===== ===== Technology =====
  
-Server: Node.js REST architecture with numerous node modules +Server uses node.js REST architecture, and all data passed between client and server are pure JSON. Also numerous node modules are used, like Express and Jade. 
-Client: HTML5(Javascript, jQuery, Ajax-calls) and ReactJS for native cross platform mobile.+Client is based on HTML5 principles (JavaScript, jQuery, Ajax-calls) and ReactJS is used for making the client look like a native mobile application
  
 ===== Presentation ===== ===== Presentation =====
Line 38: Line 53:
 Source: https://github.com/lasshi/otso-cc Source: https://github.com/lasshi/otso-cc
  
 +Final report: [[https://docs.google.com/document/d/1NsvPyfmmsD1wCs2x39Vm1WNjHJE0ldgjEl0gVZvLLyA/edit?usp=sharing|Google Docs]] or {{:otsocase2015winter:group3:otsocodecampwinter2015.pdf|pdf file}}