CSE 8314 (Fall 2013): Software Metrics and Quality Engineering
Prof. Jeff Tian, CSE Dept., SMU, Dallas, TX 75275
Phone: (214)768-2861; Fax: (214)768-3085
tian@lyle.smu.edu; lyle.smu.edu/~tian/class/8314.13f
1. General Information
One fundamental characteristics of a maturing discipline is the regirous
measurment used in characterizing the objects of its study and the
associated behavior.
Software engineering is in the transition phase from a "soft" discipline,
such as humanities and arts,
to a "hard" (or "solid") one,
such as natural sciences and (traditional) engineering.
This advanced course will cover important measurement aspects
as related to software systems as the objects of our study.
We will take a balanced approach,
covering basic ("classical") material such as the many well established
software metrics that have been around for decades,
with an additional focus on recent research and applications
in the subject area that may have a great practical impact and
that may lead to subsequent innovative research.
CSE 8314 will be organized as a combined lecture and research seminar
with active student participation.
This participatory nature is reflected in all the course elements,
ranging from discussions/presentations related to students homework/project
to specific topics to be studied and discussed in our class.
2. Course Contents
We will have in-depth discussions about several important
topics concerning software measurement.
The major focus will be on five areas:
-
Foundation and Frameworks:
We will focus on the GQM (Goals/Questions/Metrics)
paradigm as the guiding framework for our class.
Related topics will also be discussed,
such as QIP (quality improvement paradigm),
EF (experience factory),
other measurement frameworks
(particularly internal vs external measurement).
In addition,
some basic concept from measurement theory
as well as measurement in other disciplines will be reviewed.
A metrics classification framework will also be discussed.
-
External Software Metrics:
We will focus on (external) quality metrics,
but will also cover other metrics,
such as cost/effort, time/schedule, productivity, etc.
This category typically involves the surrounding environment of
a software product and its development process.
-
Internal Software Metrics:
This is typically the "core" of a "software metrics" class.
This category is typically uniquely determined by the objects
of our study themselves, but not dependent on the surrounding environment.
Most of the so-called "complexity" metrics will be covered here.
-
Metrics Selection and Validation:
The research community has paid particular attention to the metrics
selection and validation question.
In particular, some formal models have been developed and applied,
which will receive detailed coverage in our class.
-
Other Advanced Topics:
Recent research in relavant areas will also be discussed,
including the role of metrics in software experiments and empirical
software engineering,
formal hypothesis testing,
data mining of software engineering project repository, etc.
We will also discuss
new applications in cloud computing,
web-based, embedded, service-oriented, and net-centric software systems.
3. Textbooks and Class Material
4. Workload and Grading
The course grade each student receives will reflect the weighted
average of homework, a major project, a comprehensive exam,
and other assignments:
- Project:
See the online project information for more details.
- Homework:
See the online homework assignments.
- Student presentation:
See the online student presentation information
for more details.
- (Midterm) Exam:
There will be a comprehensive exam to cover
the breadth of the students' knowledge
in software metrics
(as the students' depth of knowledge is demonstrated in their projects already).
The approximate weight assignment is as follows:
-
Project (proposal, report, and presentation): 40%
-
Comprehensive (midterm) exam: 30%
-
Homework: 15%
-
Presentation/participation: 15%
No late assignments will be accepted nor graded
unless prior approval was granted by the instructor
or a valid (acceptable to the instructor) reason is
given in case of an emergency.
Notice 1:
If you need to make alternative arrangements for turning-in
material or taking exams,
you must contact the instructor ahead of time,
unless it is truly an emergency.
(Otherwise you'll receive 0 for the specific item.)
Notice 2
(Relevant SMU policies):
* Disability Accommodations:
Students needing academic accommodations for a disability
must first be registered with Disability Accommodations
& Success Strategies (DASS) to verify the disability and
to establish eligibility for accommodations.
Students may call 214-768-1470 or visit
http://www.smu.edu/alec/dass.asp to begin the process.
Once registered, students should then schedule an appointment
with the professor to make appropriate arrangements.
* Religious Observance:
Religiously observant students wishing to be absent on holidays
that require missing class should notify their professors in
writing at the beginning of the semester,
and should discuss with them, in advance,
acceptable ways of making up any work missed because of the absence.
(See University Policy No. 1.9.)
* Excused Absences for University Extracurricular Activities:
Students participating in an officially sanctioned,
scheduled University extracurricular activity should be given
the opportunity to make up class assignments or other graded
assignments missed as a result of their participation.
It is the responsibility of the student to make arrangements
with the instructor prior to any missed scheduled examination
or other missed assignment for making up the work.
(University Undergraduate Catalogue)
Prepared by Jeff Tian
(tian@lyle.smu.edu).
Initially posted: Aug. 4, 2013.
Last update: Aug. 17, 2013.