by Andres Baravalle
Flash cards are common in Agile software development methods. Used with a board, they allow to easily visualise the set of requirements to work on during the current iteration.
Volere shells are based on a broadly used template and come with extensive documentation on how to use the method.
A website wireframe, also known as a page schematic or screen blueprint, is a visual guide that represents the skeletal framework of a website.
Wireframes are created for the purpose of arranging elements to best accomplish a particular purpose. The purpose is usually being informed by a business objective and a creative idea. The wireframe depicts the page layout or arrangement of the website’s content, including interface elements and navigational systems, and how they work together.
The wireframe usually lacks typographic style, color, or graphics, since the main focus lies in functionality, behavior, and priority of content.
In other words, it focuses on what a screen does, not what it looks like.
Wireframes can be pencil drawings or sketches on a whiteboard, or they can be produced by means of a broad array of free or commercial software applications. Wireframes are generally created by business analysts, user experience designers, developers, visual designers and other roles with expertise in interaction design, information architecture and user research.
Wikipedia, 2013
You can:
First of all, familiariase yourself with XP or other agile methodologies; you will need to be familiar with the methodology that you aim to use before proceeding. The next steps assume that you are basing your development on XP principles.
Possibly something like this.
No
You need a data storage. You can use MongoDB, XML, Yaml or configuration files in PHP - just to mention a few options.
Of course, you are going to get more marks if you use MongoDB, which we will cover in the next weeks.
Check again the assignment - please.
1.
Yes and no.
Think at a web site with URLs like this:
It's a powerful approach (commonly called URL router or PHP router) - but not for the faint-hearted. It can also produce "pretty URLs" using custom Apache configuration (e.g. with .htaccess).
Create your classess - as many as needed - and some PHP pages - as few as possible.
That's why you should use a PHP router.
Alternatively, check Twig or Smarty, or simply use include files.
Do not use a flat folder structure. If in doubt, look at existing Open Source projects on sourceforge.net
I recommend you follow the PEAR coding guidelines.
Please follow the PHPDocumentor guidelines.