Methodologies

andrwleong · #1 (**permalink**) Jan 10th, 2008, 11:16

Hi everyone

I am new to this site so hello all.

my questions is about methodologies. methodologies such as SSADM following the waterfall model dont seem to be appropriate for web desgin as SSADM is for large government projects and building a website will probably have many requirement changes.

So I was wondering are there any specific methodologies for building websites??? If so could any one point me in the right direction.

welshstew · #2 (**permalink**) Jan 10th, 2008, 11:31

We use a combination of ASD (agile software development) and RAD (rapid application development).

We are, however, further complicated by needing to adhere to FSA, SarbOX, DDA regulations.

I would say that no one method is the best, and that a great deal of fluidity and flexibility is needed when building websites.

What type of project are you working on?

andrwleong · #3 (**permalink**) Jan 10th, 2008, 11:39

thanks, thats great and fast advice

I am doing a disssertation on web desgin with the finished product being a small e-commerce website for a friends shop.

so for my research I am looking for the best way to go about it in the sense of a methodology.

So what methodology do you recommend for an ecommerce website??? I am guessing I will need some techniques to capture entity relationships for the database side of the website.

welshstew · #4 (**permalink**) Jan 10th, 2008, 11:50

just found this, it is basically what we do, and what you should follow for your project.

Quote:

I am guessing I will need some techniques to capture entity relationships for the database side of the website.

that would be part of the technical spec

andrwleong · #5 (**permalink**) Jan 10th, 2008, 12:00

Quote:

Originally Posted by welshstew

just found this, it is basically what we do, and what you should follow for your project.

that would be part of the technical spec

You are an absolute star. Thank you so much.

I will read into these now, am assuming these follow the object-oriented approach.

I will be sure to give you a shout in my dissertation for this help.

thank you so much

welshstew · #6 (**permalink**) Jan 10th, 2008, 12:22

Quote:

Originally Posted by andrwleong

am assuming these follow the object-oriented approach.

OOP is a programming approach, what we are talking about here is how to manage the project, not how to code it.

You will use the AWD process / cycle to help you plan and deliver the project in a timely manner, with all deliverables defined and met, etc.

Within your documentation you will state that the code was developed in line with OOP, and meets blah blah standards, and so on.

You will then need to code it.

Does that make sense?

andrwleong · #7 (**permalink**) Jan 10th, 2008, 12:29

Quote:

Originally Posted by welshstew

OOP is a programming approach, what we are talking about here is how to manage the project, not how to code it.

You will use the AWD process / cycle to help you plan and deliver the project in a timely manner, with all deliverables defined and met, etc.

Within your documentation you will state that the code was developed in line with OOP, and meets blah blah standards, and so on.

You will then need to code it.

Does that make sense?

aaaaa see this is were i get confused.

I know waterfall, RAD etc are not methodologies but software development processes. But structured methodologies such as SSADM or Object-oriented’s UML are methodologies.

This is where I get confused.

I thought if u followed the waterfall model then automatically you follow the SSADM structured approach. And if you followed for example Prototyping then you automatically follow object-oriented approach.

Daniel · #8 (**permalink**) Jan 10th, 2008, 14:08

use spiral.

welshstew · #9 (**permalink**) Jan 10th, 2008, 15:26

Quote:

Originally Posted by Daniel

use spiral.

archimedean, logarithmic or hyerbolic?

Only joking

Andrew, check here for the spiral model

To me it seems to be very similar to AWD but for larger projects

welshstew · #10 (**permalink**) Jan 10th, 2008, 16:16

Quote:

Originally Posted by andrwleong

Object-oriented’s UML are methodologies

UML is a modelling tool to help you define each class / object etc, as well as understand and visualise how the objects interact

Quote:

Originally Posted by andrwleong

I thought if u followed the waterfall model then automatically you follow the SSADM structured approach. And if you followed, for example ,Prototyping then you automatically follow object-oriented approach

Agile (iterative) and Waterfall are processes, where as OO is a methodology.

I can therefore have a waterfall process, structured start middle and end, and still have a OO methodology when I approach how to develop the code.

OO is just a way of seeing the "world" in which your code exists. The best analogy is to think of OO as lego. Each object defines itself and can be used to make something bigger once the interaction is defined.

i.e. I can have a tyre object, an engine object, and a wheel object. I can combine these to make a car, or a motorbike, or a go-cart

andrwleong · #11 (**permalink**) Jan 11th, 2008, 17:10

THANKS EVERY ONE

especially welshstew who has taken a lot of time and effort.

The particular chapter in my dissertation is about Methodologies. So I have talked about Systems Development Life Cycle, Structured methodologies and OO.

I then hoped to add to this chapter by explaining there are now newer methodologies and methods specific for web design and I think I have it with Agile Methodologies and agile web development.

This is just to show that I have considered options other than Traditional methods.

When I have done my research I will then follow one of the processes to make the website. So you all say to follow Spiral

andrwleong · #12 (**permalink**) Jan 11th, 2008, 17:15

Quote:

Originally Posted by welshstew

UML is a modelling tool to help you define each class / object etc, as well as understand and visualise how the objects interact

Agile (iterative) and Waterfall are processes, where as OO is a methodology.

I can therefore have a waterfall process, structured start middle and end, and still have a OO methodology when I approach how to develop the code.

OO is just a way of seeing the "world" in which your code exists. The best analogy is to think of OO as lego. Each object defines itself and can be used to make something bigger once the interaction is defined.

i.e. I can have a tyre object, an engine object, and a wheel object. I can combine these to make a car, or a motorbike, or a go-cart

haha thanks, I and every one else in uni get very confused about methodologies.

we are taught so we believe if you follow waterfall then u follow SSADM which is Structured and if you follow prototyping then you follow OO

sekuchi · #13 (**permalink**) Jan 14th, 2008, 23:08

I use waterfall approach it's easy to follow. I'm confused with the spiral model.

andrwleong · #14 (**permalink**) Jan 15th, 2008, 08:52

Quote:

Originally Posted by sekuchi

I use waterfall approach it's easy to follow. I'm confused with the spiral model.

whaaaaaaaaaaaaaaaaaaaaaaaaaat really. How does that work mate.

I would assume a customer wouldnt realy know what he wants

"I cant say what i want but i'l know it when I see it" Barry Boehm

How do you deal with requirement changes.

Andrew

		Webforumz.com > Main Forums > Planning Your Website > Website Planning
Methodologies