Getting the requirements right is 60% of the job.
Making the site is only 40% of the job (provided you can code like a banshee, that is.)
* What do they want the site to 'do'
* tell people about the business, obviously.
* browse a catalogue?
* search for products?
* place orders?
* pay by credit card?
* advertise promotions or such?
* what else?
* How do they want the site to work?
Keep it fairly conceptual. Make a site map, and
sketch the way you'll guide visitors though the
site. Like, what do you do when a customer
wants to change an order?
* How do they want the site to look?
What fonts to use, how do the menus look, etc.
At this point you have everything you need to
make a mock up of all the pages in Paint (or
a similar program). Visualizing the final product
really helps to work out additional requirements
and to correct flaws in the flow.
* How will you/ they keep the site and the
catalogue up-to-date?
* Start thinking about the technical requirements
* You might want to use cascading style sheets.
* If you want customers to place orders, you'll
need to make a database, too - or perhaps
even integrate the business' existing database.
You'll have to learn SQL.
* If you want your site to communicate with a
database, you'll also need to include ASP.NET,
ColdFusion, or some other language in your
HTML. You'll have to learn that.
* You'll need an idea of the security concerns
and how to adress them.
With all of this information, you'll have some idea of how long it will take you to actually make the site. You'll also have all the information you need to figure out how much the site will cost to make and operate (If you use a lot of fancy stuff, the price goes up for hosting the site. It also costs a fee to accept credit card payments. Then, you might need to buy software or reference books. You might need to hire a guy for a day or two to help out with stuff. Things like that.)
Based on this, you might decide you're not up to the task, or that it would simply take you to long. Or your relatives might decide that the cost isn't worth it, and they'd rather stick with a simple site.
Please note that even a really experienced guy would need at least two or three weeks for something moderately sophisticated. Then add a week for testing and minor adjustments. But if you have to teach yourself as you go, you could easily spend two weeks just on the graphics.
2006-09-23 14:52:41
·
answer #1
·
answered by OMG, I ♥ PONIES!!1 7
·
0⤊
0⤋
you should start with requirements before seriously persuing any development project, but until you decide on them, start familiarizing yourself with web programming languages such as ASP, PHP or ASP.NET if you aren't already, as well as web sites of your relatives' competitors.
Decide on features, what is on the must have list vs the "wish" list. Prioritize the features, group them into "releases", and come up with a time frame for each release, then get to coding. Remember to get feedback along the way.
2006-09-23 14:03:08
·
answer #2
·
answered by Stanley 3
·
0⤊
0⤋
utility existence cycle: The structures progression existence cycle (SDLC), additionally talked approximately through fact the appliance progression existence-cycle, is a term utilized in structures engineering, counsel structures and utility engineering to describe a technique for making plans, arising, finding out, and deploying an counsel device. The structures progression existence-cycle thought applies to countless hardware and utility configurations, as a device could be composed of hardware in basic terms, utility in basic terms, or a mixture of the two. utility progression: A utility progression technique (additionally universal as a utility progression technique, sort, or existence cycle) is a framework it somewhat is used to shape, plan, and administration the mindset of arising counsel structures. a great form of such frameworks have progressed by using the years, each with its very own known strengths and weaknesses. There are various diverse strategies to utility progression: some take a extra popular, engineering-based mindset to arising corporation suggestions, while others might take a extra incremental mindset, the place utility evolves because it is progressed piece-by utilising-piece. One device progression technique isn't inevitably appropriate to be utilized by utilising all projects. all of the available methodologies is maximum suitable ideal to precise forms of projects, in keeping with multiple technical, organizational, undertaking and team concerns. maximum methodologies share some mix of here tiers of utility progression: reading the difficulty marketplace study accumulating standards for the proposed corporation answer Devising a plan or layout for the utility-based answer Implementation (coding) of the utility finding out the utility Deployment
2016-12-15 13:15:10
·
answer #3
·
answered by salguero 4
·
0⤊
0⤋
go to http://msdn.microsoft.com/vstudio/express/vwd/default.aspx
download visual web dev. for free and use vb.net if your starting out and they have lessons if u down load the msdn as well
http://www.w3schools.com/ for your lessons on every latest web tech u can think of showing u examples!!
i would recommend vb.net and asp.net serverside languages which run on the server so they can't steal your code......and javascript can be stolen even thou it's unusally powerful enough but i think vb.net and asp.net is easier than php or jsp plus you can use your vb.net skills to build windows apps or games if you ever want! so if you learn vb.net it's a skill you can use for other projects if you are ever interested in programming.
2006-09-23 14:13:47
·
answer #4
·
answered by groundbrandon 3
·
0⤊
0⤋