Scottwnelson Jul 21, 2010   0:36 AM GMT

Software Development Life Cycle (SDLC) is the general terminology for the evolution of a piece of software from inception to retirement/replacement. It is not a "methodology" in and of itself. The "methodology" used to implement the SDLC (or various phases of it) can range from structured and rigid (waterfall) to fast and flexible (any of the many "Agile" methodologies such as Scrum, XP, Spiral, and more). Which one you use (or even your own custom methodology) really depends on the environment in which you are working and the nature of the project. For example, if you are building automation software for hospital power management you want to be very thorough and get it right the first time (probably) so you want a highly controlled waterfall methodology. But if you are building a web application to let users custom design their own trendy footwear before they order it, you can probably go more towards the agile end of the spectrum. But this advice is all based on general assumptions, your project's unique requirements and environment should determine the methodology approach you use.

265 pointsBadges:

Scottwnelson Jul 21, 2010   0:47 AM GMT

A big consideration too is time available for the project scale of the project. Given that this sounds like a school project, you probably don't have time to use any methodology other than an "agile" methodology. Is this a team effort? Scrum might be a good one to look at first.

265 pointsBadges:

Mahjong Jul 21, 2010   10:32 AM GMT

Thank you Sir, yes its a university final year project, and its an individual effort. The system is a census management application, analyzing census survey forms collected from a student portal, in a campus intranet. This data is processed to create mean, medium, range, total, comparison from the census made on the intranet, putting the data into graphs and charts etc.

30 pointsBadges:

Scottwnelson Jul 22, 2010   0:11 AM GMT

You are welcome. Remember that a given methodology is strictly a process for getting the work done- it is a project management philosophy- not a blueprint for writing code. Some, key issues a methodology will help you with are: Discovering what needs to be done and why. Setting a schedule for getting the work done and setting various milestones if appropriate. Prioritizing work (must have items and could have items if there is time). Recording and clarifying decisions and agreements. And more... A methodology doesn't help you write code, it helps you determine what code to write and in what order. Bon voyage!

265 pointsBadges:

Mahjong Jul 22, 2010   5:35 PM GMT

Yes Sir I understand what the use of a methodology is and how it will help, But my concern would choosing "which one" to use in my system development. Its quite a urgent matter......

30 pointsBadges:

Scottwnelson Jul 23, 2010   1:09 AM GMT

Here's what I would do: Pick up Extreme Programming Pocket Guide: http://oreilly.com/catalog/9780596004859 The thing about XP is that all it's processes can be taken as a whole or selectively, based on what you think will be practical for the project. Know too that most "agile" methodologies espouse the same concepts, they tend to just be named and arranged differently for copyright-ability. Good luck!

265 pointsBadges: