Refer to included Specification for an overview of this project. We are keen to receive realistic quotes that demonstrate clearly the steps to be undertaken and measures that will be employed to ensure our requirements are met.
This represents the first stage of the development of an new online business. The Concept is to establish a 'prototype' that we can demonstrate and evolve prior to commercialising, however quality in the way the system is to be built is paramount. We are not looking for the design to be 'beautiful' at this stage, simply clean and tidy and well laid out.
No hackers or students please. We are looking for professionals who can deliver; who listen and who are punctual.
We appreciate those who know when to ask questions and when to offer suggestions.
Good luck. We look forward to receiving your quotes.
Additional Project Description:
02/24/2013 at 23:00 AST
We will also accept the use of the Zend Framework in place of Yii.
To clarify the objective of this first phase:
To achieve a working prototype of the administration functions that will be required. These are centric around the creation of QR Codes, the Entities to which they are related e.g. People or Places of Interest, and the standard CRUD and User authentication functions.
03/06/2013 at 3:01 AST
I have rewritten the Specification document and attached an updated version - please refer to v1.1.
To clarify the objectives (milestones) of this project:
1) Administrator login
- email & password
- salt encrypted
2) Admin Dashboard
2.1) Generate QR Codes for given parameters e.g. URI type (e.g. URL), GUID, Status; in batches of 10,50,100, etc
2.2) CRUD a Person Entity with attributes: family & first name, date of birth, birth location, date of death, buried location
2.3) For a given Person, create a Profile. A standard Profile is a Webpage which displays their details (2.2) and allows an Obituaray (story about their life) and some photo's to be uploaded. *** Note: this only needs to be basic at this stage.
2.3.1) Ability to 'publish' and 'version' each change made to a profile. ** Note: this only needs to be basic at this stage.
1) QR Codes can contain more than just a URL. The system must cater for 'future' variation to the URL type.
2) The Person entity is not the only Entity that will be added in the future, therefore other Variations e.g. Place or Thing needs to be catered for - not part of v1
3) A Profile in future could be someone's Facebook page, or whatever, so the system must be able to cater for expansion to this area
The overall objective is to build a prototype that in it's simplest form demonstrates the basic transaction, which is:
A person sees a QR Code somewhere and uses their SmarPhone to navigate to an online Profile. The Profile, in the first instance, is an Obituary of someone who has died. It contains their name, date of birth and a story about their lives along with some pictures.
The admin system is to focus initially on the generation of QR Codes as these will be printed onto little signs to be installed at a location e.g. someones grave stone.