Angular JS - PHP REST - CRUD

= CONTEXT = We are building a full ERP system for construction companies specialized in slabs / stones materials. Right now we are working in the Purchases Module and we require a Purchase Order CRUD, this is, a module to Create, List, View and Update this kind of entities. It is not necessary to Delete orders. A Purchase Order is an entity that contains a list of products that we are buying from a specific provider. = 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 so you will need solid knowledge in all this frameworks and tools. = FUNCTIONAL REQUIREMENTS = 1. CREATE A PURCHASE ORDER (P.O.) The creation of a purchase order is a two steps process. a. STEP 1 – Creation of the Order [[TASK 1]] (See detail in attached document). b. STEP 2 – Addition of Products associated to the Purchase Order [[TASK 2]] (See detail in attached document). 2. LIST OF PURCHASE ORDERS [[TASK 3]] (See detail in attached document). 3. VIEW / EDIT A PURCHASE ORDER a. Change the Basic Information of a Purchase Order [[TASK 4]] (See detail in attached document). b. Add / Edit / Delete Products of a Purchase Order [[TASK 2]] This is the same Task 2. = TASKS SUMMARY = TASK 1: Development of Create Purchase Order Form. TASK 2: Development of Add / List / Edit / Delete Products of the Order. TASK 3: Development of the List of Orders TASK 4: Development of the Change Basic Information of an Order. = NON – FUNCTIONAL REQUIREMENTS = - 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. - 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, this is, 4) 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 4 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.