Blog of Ken for CS 4348 - Software Quality Management
Friday, April 16, 2004
Monday, April 05, 2004
For CVS, we have to setup both CVS client and server.
Concurrent Versions System
The is the official site of CVS. It provide documentations and releases of the CVS programs for Unix/Linux platforms.
CvsGui
This is the web site for a CVS client (WinCVS) for Windows platforms.
The CVSNT Wiki
CVSNT is a CVS server for NT platforms. This tool is very useful for developers who are not familia with Unix/Linux platforms.
Tuesday, March 02, 2004
Once again, risk management.
This page is an detail descriptive article on software risk management. It shows the reasons and approaches for software risk management.
Know Your Enemy: Software Risk Management
Sunday, February 29, 2004
Through out the software development process, it is unavoidable to have risk. However, risk is not totally bad to us.
"Risk in itself is not bad; risk is essential to progress, and failure is often a key part of learning. But we must learn to balance the possible negative consequences of risk against the potential benefits of its associated opportunity."
[Van Scoy, Roger L. Software Development Risk: Opportunity, Not Problem. Software Engineering Institute, CMU/SEI-92-TR-30, ADA 258743, September 1992]
Visit the SEI Risk Management Overview and you will get more familiar with some principles for risk management.
Risk Management Overview
Friday, February 20, 2004
While I was searching for tools to check coding standard for my FYP, I found an open source tool, JCSC, to do this. I've tried it, and it really response with useful information on coding stardard violation and metrics on my code. For those who are writing JAVA, this tool will absolutely imporve your software quality in terms of coding standard and metrics.
Tuesday, February 10, 2004
While I was preparing for the lecture this week, I found several informative web sites on software metrics and would like to share with you.
In the Taxonomy of Structural Software Metrics section of this page, the traditional software metrics are classified into categories. It give some definition and constriant on the categories.
http://web.cs.mun.ca/~ulf/gloss/complex.html
Since OO methodology is becoming more and more popular, a set of OO software metrics is defined. You can find the detail definitions on these OO software metrics.
http://ourworld.compuserve.com/homepages/qualazur/$swmesu2.htm
This is another page on OO software metrics. It interests me because it explain the difference between OO and traditional metrics.
http://www.ipipan.gda.pl/~marek/objects/TOA/moose.html
With the above web pages, you would be more familiar with software metrics. However, when you are performing software measurement, there are 10 traps for you to avoid. Click the link below and learn how to avoid those traps.
http://www.processimpact.com/articles/mtraps.html
Hope you enjoy these sites.
Monday, February 09, 2004
Newly invented MDA, OCL and UML2.0 are marked to be the core components of the future software engineering. These 3 components are said to be able to combine and perform code generation task.
What is MDA, OCL and UML2.0?
How can they work together?
Is there any tool helping us in using these components?
We can find the answer in this web site. This web site briefly introduce MDA, OCL and UML, how they interact and some tools related to them.
http://www.klasse.nl/english/overig/index.html
