AngularJS + PHP REST Server: Mobile Module PO Fulfillment

== RFP – TRITON MOBILE MODULE: PURCHASE ORDER FULFILLMENT == = CONTEXT = We are building a full ERP system for construction companies specialized in slabs / stones materials. Right now we are working in the Mobile Modules. This modules will run on modern mobile web browsers (Firefox, Safari, Chrome, etc.) and will provide to different users of the system with different functionalities of Catalog, Inventory, Sales, and Purchases. The Catalog is the set of products that the system offers to the clients. The inventory is the detailed information of the items the company has in its warehouses. = SYSTEM ARCHITECTURE = This is a web system. The client is built in AngularJS + Bootstrap CSS consuming REST services from a PHP server. The server uses the Framework Phalcon PHP with a MySQL Database. All the architecture and Database Model is fully defined and will be given to you at the beginning of development. For each requirement you’ll have to develop across all modules: Client / Business Server / Database. = FUNCTIONAL REQUIREMENTS = User: Purchases operative. Target Devices: 320px, 480px, 768px and 1024px MM1-R01: Search Purchase Order – PO. MM1-R02: Show PO Detail - List PO Products Inventory Lines. MM1-R03: Fulfill PO Product Inventory Lines using the Device Camera. MM1-R04: Fulfill PO Product Inventory Lines using the Device Camera – SLABS. *** View all the detail in the attached document. = NON – FUNCTIONAL REQUIREMENTS = - Most of the described functionalities are already developed for the desktop version of the system. Most of your work will be to make the system responsive and test all the web controls in the different devices. A special case is the image capture with the device: this will have to be developed because the desktop version doesn’t have this functionality. - Availability and Dedication: You should be available to start working immediately and start to deploy functionalities in the site very soon. - Code Documentation and Indentation: The code must be fully documented and correctly indented. - Look & Feel: There is a defined Look and Feel of the page that you’ll have to keep. A lot of styles are already defined in the main stylesheet and you should try to reuse them. - Architecture: You have to follow the architecture of the system. o All the business logic have to stay in the server. o Only presentation logic in the client. o Only RESTful services. No session handling in the server. - Configuration Files: All the forms and table have to be dynamically generated based on JSON configuration files. We already developed examples of this that you can use to guide your development process. - Development, Integration, and Deploy: You’ll have an isolated environment in our servers to develop on a daily basis. As soon as one of the functionalities is completed and tested you’ll have to merge your code and integrate with a special environment where other developers are also updating their changes. A second set of tests will be run then before accepting your development. - Daily Reports of the Status of Development: I’ll ask you to send me a daily quick report with: 1. Percentage of Progress (quotient of the fully completed tasks from the functional requirements table / total of tasks from the functional requirements table) 2. Table of tasks with the current status of each one. 3. Questions and information requirements. = PROPOSALS FORMAT = If you are interested in working with me, please make your bid specifying: - Amount of Hours you expect to spend working on the tasks. - The dates when you plan to release each task so I can plan the testing with my QA team. - Any questions or comments. I will be glad to clarify anything for you.