The Architect lays out the database object structure and describes not only the HTML pages, web methods and graphical elements required, but also what share of the profits a Builder would receive for building each piece of required content.
The Architect requests X% of the profits for use of their plans and submits them to the Inventor for approval.
Here's a summary of what an Architect's plans might look like for a website that is a Marketplace of Robots:
Database Objects:
Robot categories
Category name
Category parent
Robot listings
Title
Description
Photo URL
Price
Contact Email
Static HTML Pages:
FAQ (15% of profits for completion of the FAQ)
Action Handlers:
Add new Robot Listing (5% of profits for completion of this Action Handler)
Delete Robot Listing (5% of profits for completion of this Action Handler)
Dynamic HTML Pages:
Home page - to display current categories (15% of profits for completion of the Home page)
Include cool robot graphic in home page(5% of profits...)
Category display page (5%)
Generic robot description page (10%)
Page to add new robot listing (10%)
Page to delete robot listing(5%)
Methods:
None
The Architect decided not to use any Methods for this site, but they could have included a Method such as "Pull Up all Matching Items from eBay", or "Pull Up News Headlines About This Type of Robot from Google News", etc. The Architect submits these plans to the Inventor and asks for 15% of the profit (or whatever) for their use.
Video Tutorials
 |
Planning 1 - Hello World |
|
Planning 2 - Display Time |
|
Planning 3 - Public Wall |
