WBL Image Ad Directory

WBL consists primarily of paid-for image-linked ads in different sizes and page placements. The homepage has image-links reflecting Premium and Value-sized ads which appear in ordered rotation as they are paid for. Value-sized ads appear below the Premium ads in rows and columns from left to right. The most recently published appear top left. When the homepage is full, the ads at the bottom right of the page reappear as search results or as random image-links below search results. Premium image-linked ads appear at the top of all pages and in rotation based on the total number of available. A draft of the look of this Web advertising/business directory is at [request if needed] Current site design draft at [request if needed] The scope of work to realize WBL is seen as follows. Project Specification The project specification includes a process model that focuses on three types of users of the application (actors): Visitor Customer Administrator In the process model below, we can use the following naming conventions for the actors and objects represented in the system: ACTORS and OBJECTS Actor types and object interactions: VISITOR – views, searches for, and selects ADVERTISEMENTS CUSTOMER – creates, edits, maintains an ACCOUNT, purchases and deletes ADVERTISEMENTS ADMIN – adds/edits/deletes CONTENT, adds/edits/deletes display rules for ADVERTISEMENTS, adds/edits/deletes ADVERTISEMENTS, adds/edits/deletes ACCOUNTS PAYPAL – accepts PAYMENTS, interacts with APPLICATION to confirm PAYMENT status, sends email PAYMENT confirmation to CUSTOMER APPLICATION – the system that controls the actions and workflow of all the actors listed above The process model, in outline form, can be read as follows: VISITOR or CUSTOMER arrives at the homepage If user is VISITOR APPLICATION Displays homepage with ADVERTISEMENTS APPLICATION Displays extended description of ADVERTISEMENT on mouse over VISITOR Searches for ADVERTISEMENTS Search by Keyword Select filters (optional) Search by Industry (predetermined selection) Select filters (optional) If user is CUSTOMER If CUSTOMER is not registered CUSTOMER Creates ACCOUNT Enter Username (equal to Email address) Enter Password Enter First Name Enter Last Name APPLICATION Sends email confirmation (Welcome Message, Username, Password, Login link) to CUSTOMER Else If CUSTOMER is registered CUSTOMER Login to ACCOUNT CUSTOMER Orders ADVERTISEMENT CUSTOMER Provides ADVERTISEMENT info Premium/top, Preferred/middle, or Value/anywhere placement Upload image APPLICATION resizes image to specific dimensions if needed Enter description Enter keywords Enter duration CUSTOMER Makes PAYMENT to PAYPAL If PAYPAL approves PAYMENT PAYPAL emails CUSTOMER receipt of PAYMENT APPLICATION confirms PAYMENT with PAYPAL (details) APPLICATION updates ADVERTISMENT status to “active” APPLICATION sends CUSTOMER confirmation CUSTOMER Deletes ADVERTISEMENT APPLICATION sends CUSTOMER email confirmation APPLICATION updates ADVERTISEMENT status to “inactive” CUSTOMER Updates ACCOUNT Change password Change language preference ADMIN arrives at Login page ADMIN login APPLICATION Displays ADMIN homepage Update content supplied to VISITOR Add/Edit/Remove ACCOUNT Add/Edit/Remove ADVERTISEMENTS Special Considerations Language preferences have been omitted from the preceding specifications. However, this feature should be considered in the application design in order to facilitate the implementation of this feature at a later date. The prices for ads and ad types should be read from the database, not hardcoded. The Web administrator should be able to change these as the market requries, including offering free ads. Google AdSense "blocks" will be used to increase possible revenue. PayPal "buy now" buttons is the preferred ad/listing payment module. Images to be stored on the server, not in the database. If an ad is deleted, the database should record this and the corresponding image file on the server deleted. Plan Formalize and finalize, in detail, all functional application requirements. Design application, including database structure and application modules. Write the PHP/MySQL source code for the application. While doing the above, communicate frequently with contractor with detail. Implement the application on a development (testing) web server to test all aspects of functionality including quality assurance and error reporting. All work must be guaranteed 100% satisfaction. Copyright and non-technical administrator functionality of final product required.