It is already well known and proved that quality oriented development is better than time oriented development in terms of quality and time.
Time Oriented Development
Developing software with fixed schedule. For example, we should complete this project by 10th of March.
In this case, usually, functionality has priority to show progress. And, quality is put behind. So, software is not tested enough during development. Usually, real stage for test and debugging begins at the latter part of project. This is main cause that make time for test and debugging be longer than expected.
Quality Oriented Development
Development focusing on software quality. Software continuously tested during development to keep software quality good. So, software is debugged at the early stage. So, cost for debugging lessen(It's well known that debugging at the early stage is much cheaper than debugging at the latter stage.). This shorten time and increase quality.
'Development' 카테고리의 다른 글
|[Dev] Sharing between members and leader... (0)||2009.12.04|
|[Dev] Key point to succeed in large project... (0)||2009.08.01|
|[Dev] User Interface Specification in Handset Software Development (0)||2008.10.23|
|[Dev] Time oriented vs Quality oriented development (0)||2008.10.17|
|[Dev] Items to check in the first step for co-working. (0)||2008.09.22|
|[Development] Why should we shorten product developement time? (0)||2008.09.20|