This project is the registration component for new software users. Team lead and then team members.

[login to view URL] is a SaaS platform for small business coaching and action tracking. This project is the registration component for new software users. It is the first step in a long-term project and we will have more parcels of work like this. We are going through a process at the moment to establish a group of people who we will invite to tender for subsequent parcels. We will evaluate performance of our Fiverr vendors by considering: • Understanding what we want and delivering it • Price • Quality of what you deliver (i.e. efficient software with no bugs) • Good communication with us • Suggestions and improvements over our base specifications where appropriate • Speed of delivery • Well-documented code This component is focused on functionality, not visual design. The UI elements should be as basic as possible, to be fit into a framework at a later date. Technical Requirements Your code should be written in PHP for standard LAMP/WAMP stack using Zend Framework 2.3. Users/authentication information are stored in mySQL. Passwords are hashed with SHA2 using both a static and dynamic salt. Documentation The specific functionality and workflow is documented in the attached Powerpoint and Excel files. The Excel document contains an illustrative model of the database structure. Each tab corresponds to a separate table. The italic text in row A describes the field requirements, and the bold text in row B contains the field names; you may change the names to fit your purpose, but they should correspond as closely to this document as possible. The other rows (C and below) are only sample data. You may make alterations to the fields or structure of the database to improve efficiency, but these changes should not change the overall functionality. All of the fields are either user input or are backend references (e.g. DBIDs). The only exception is the Industries tab, which contains the dropdown options from slide 10 of the “New Company Registration workflow” Powerpoint document. These should not be editable except by an internal user. The Powerpoint documents show the user inputs and workflow. There are notes in the comments section throughout. “New Company Registration workflow” is the primary workflow for registering new users. On slide 4 the user nominates other users and the system should send these users email invitations containing a link to register. The registration workflow for these users is documented on the “Nominated User workflow” Powerpoint. Other requirements • Transitions between screens should be quick and clean. • UI customization should be kept to a minimum. The functionality should be adaptable to a future UI template. • Users must be able to use their browser’s forward/back buttons without error throughout. • Data should be saved constantly so the user can exit and return to the same point later. Hold points Based on experience, we think that projects like these can work better if there are pre-defined “hold points” where we “approve” one or more deliverables, before you move on with the project. One important one is the development of the ERD (entity relationship diagram). So, as a first step, we would like to you to produce one of these for our project and await approval to proceed. Your quote should include all stages of the project and also any other hold points that you think would be useful. Thank you and good luck! Please do not hesitate to reply with any questions.