Office and Addresses

Delta 171 Phone 281.283.3805
email: boetticher@uhcl.edu
Secretary: Ms. Kim Edwards, Delta 161 281.283.3860

Face-to-Face Class Hours

There is no face-to-face section.

Office Hours

Thur. 12 - 4, or by appointment. If the suite door is locked, then call my extension (last 4 digits) using the phone in the hallway.

Teaching Assistant

TBD, email : tbd
Office Hours: TBD

WebCT link

Required Textbook

None

Reference Materials

TBD

Course Description

Software engineering tools is a very practical course that focuses on which tools are needed for effective management and implementation of a software project. Students will have the opportunity to try different tools, and assess them for their merits. The traditional graduate student load is 3 courses. Be prepared to commit 15 to 20 hours per week to this course!

Learning Outcomes

Upon completion of the course, students are expected to be able to:

• select a set of tools appropriate to their company with respect to the specific phases of the software life cyle. These include requirements (Rational), project estimation, design (OO Modeling and UML), coding, documenting, testing, and installation phases.

• distinguish between two or more tools for various life-cycle phases.

• critique software engineering tool assessment made by peers.

• synthesize knowledge regarding the features of various tools in a case study.

Prerequisites

The prerequisite for this course is CSCI 3133 (programming in C). SWEN 4432 (software engineering).  If you do not meet the prerequisites then you need to drop this course!

Methodology

Web-based material and seminar and Lecture. All the material for this class is available on the web. The lectures will be highly interactive and fun.

Appraisal

Grading Scale

93+ = A; 90 = A-; 87+ = B+; 83+ = B; 80+ = B-; 77+ = C+;
73+ = C; 70 = C-; 67+ = D+; 63+ = D; 60+ = D-; 0+ = F

My motto:

Seek the Truth.

Show altruistic love.

Appreciate beauty.

Tentative Schedule

Aug 26 – Course overview, Criteria for evaluating SE tools

FOR NEXT WEEK (IF NOT SOONER)  

·  Read:  Orientation

· Review at least 2 tools from the following link:

·   Requirements Tools

· Review the following:

·   Requisite Pro Overview

·   Requisite Pro Tutorial

·   Requisite Pro Examples

·   Requisite Pro Use Cases

·   Requisite Pro Video Tutoria

Sep 06 – Requirements tools

FOR NEXT WEEK (IF NOT SOONER)  

· Review the following tools:

·   Project Kick Start

·   Turbo Project

·   Microsoft Project

Sep 13 – Resource management tools

FOR NEXT WEEK (IF NOT SOONER)  

· Review the following tools:

·   Human-based exercise

Function Point Analysis (Trial version)

·   SLIM Estimate

·   SLIM Controller

Sep 20 – Project Estimation tools: Human Estimation Tool

FOR NEXT WEEK (IF NOT SOONER)  

· Review the COCOMO II Tool and documentatin posted on WebCT

Sep 27 – Project Estimation tools: COCOMO II

FOR NEXT WEEK (IF NOT SOONER)  

· Review the Function Point Analysis Tools posted on WebCT

Oct 04 – Project Estimation tools: Function Point Analysis

FOR NEXT WEEK (IF NOT SOONER)  

· Review the Rational Rose Tool:

·   Rational Rose Overview

·   Rational Rose Examples

·   Rational Rose Use Cases

·   Rose Video Tutorial 1

·   Rose Video Tutorial 2

· Review at least 1 tool from the following link (if you do not plan

   to attend the face-to-face, then review 2 tools):

·   Design Tools

Oct 11 – Design Tools

FOR NEXT WEEK (IF NOT SOONER)  

Oct 18 – Software IDE tools

Oct 25 – Source Code Control tools

Nov 15 – Coding tools: Debugging

Nov 22 –  Bug tracking tools

· Review at least 1 tool from the following link:

·   Installation Tools

· Review at least 1 tool from the following link:

·   Software Protection and License Control

Nov 29 –  Software Installation and licensing

· Respond to the essay questions which was posted on the WebCT discussion board on November 18, 2008. Your submission is due on Monday, Dec. 6th, 7 PM.

Dec 06 – Review of essays 

Other Policies

Homework, Projects, Research Paper

• Homework and projects are due exactly at the prescribed time (usually the beginning of class). As soon as a homework or project is collected, then all others are considered 1 day late (even if it only 3 minutes). In the event you might be running late, you might want to email the assignment. Also, when preparing your assignment, be mindful of possible backlogs at the printer, jammed printer, printer out of toner, etc.

• Late projects are accepted with a penalty of 10% deduction per day after the due date. No late project will be accepted one week after the due date. The last project cannot be late.

• There will be no extra-credit homework or projects in this course.

• All homework and projects must be typed not hand-written.  

• VERY IMPORTANT! In certain classes students are encouraged to work in groups. For this class you are expected to work on all homework and projects individually. Students may not discuss, use, email, show, give, buy, sell, borrow, trade, steal, download from the Internet, etc. in whole or part, any of the homework or projects in any manner not prescribed by the instructor. Handing in an assignment for another student is considered cheating. Penalty for cheating will be extremely severe and may result in an F for this course. This condition applies even after you complete this course! Penalty for cheating will be extremely severe and may result in an F for this course.

• VERY IMPORTANT! Failing to report to the instructor any incident in which a student witnesses an alleged violation of the Academic Honesty Code is considered a violation of the academic honesty code. Please see me to discuss any incidents.

• VERY IMPORTANT! Purchasing, or otherwise acquiring and submitting as one's own work any research paper or any other writing assignment prepared by others constitutes cheating. Penalty for cheating will be extremely severe and may result in an F for this course.

• VERY IMPORTANT! Plagiarism on either an abstract, draft of a paper, or final paper will result in a 0 for all three parts (abstract, draft version, final paper). Please review the following links regarding plagiarism very carefully: http://www.indiana.edu/%7Ewts/wts/plagiarism.html              http://www.hamilton.edu/writing/style/plagiarism/plagiarism.html                  http://ollie.dcccd.edu/library/Module4/M4-VII/plagar.htm                                                 http://www.realisticdiplomas.com/A-Guide-To-Plagiarism.aspx

• Standard academic honesty procedure will be followed. See the following link for additional information: http://b3308-adm.uhcl.edu/PolicyProcedures/Policy.html

Tests and Quizzes

• There are no make-up tests except in verified medical emergencies and with immediate notification. Rescheduling a final exam in order to catch a plane flight is unacceptable. Make up exams are harder, and different, than original exams.

• There are no make-up quizzes. Allow plenty of additional time in the event that webCT crashes.

• You are responsible for all the readings assigned throughout the semester.

• Students are to work on test and quizzes individually.  Students may not discuss, show, give, sell, borrow, trade, share, etc. their tests or quizzes. Penalty on cheating will be extremely severe. Standard academic honesty procedure will be followed.

• VERY IMPORTANT! Providing answers for any assigned work or examination when not specifically authorized by the instructor to do so. Or, informing any person or persons of the contents of any examination prior to the time the examination is given is considered cheating. Penalty for cheating will be extremely severe and may result in an F for this course.

• VERY IMPORTANT! Failing to report to the instructor any incident in which a student witnesses an alleged violation of the Academic Honesty Code is considered a violation of the academic honesty code. Please see me to discuss any incidents.

Miscellaneous

• Any person with a disability who requires a special accommodation should inform me and contact the Disability services office or call 281 283 2627 as soon as possible.

• Incomplete grades or administrative withdrawals occur only under extremely rare situations.

• The ringing, beeping, buzzing of cell phones, watches, and/or pagers during class time is extremely rude and disruptive to your fellow students and to the class flow. Please turn off all cell phones, watches, and pagers prior to the start of class. 

• This is not a Web-based class. You are expected to attend every class.

• I am willing to provide letters of recommendation/references only if you have attained an 'A' in one of my classes, or two 'A-' in two of my classes. Getting a letter of recommendation/reference does not guarantee that I will hire your for a TA/RA position.

• I highly recommend that you seek out your advisor and complete you Candidate Plan of Study (CPS) as soon as possible. I am normally not available for advising during the summer months.

• Pay very careful attention to your email correspondence. It reflects on your communication skills. Below is a compilation of email errors I have received during the past year.

dear sir.

wen r u gonna grad the homework, bcoz i have a doubt about the third problem

Some student

Common problems:

   *   wen instead of when

   *   bcoz instead of because

   *   r instead of are

   *   u instead of you

   *   lowecase i instead of I

   *   starting a sentence with a lowercase letter

   *   doubt instead of question

• I immediately discard anonymous emails.

Return to Top

Home • UHCL • SCE

2700 Bay Area Boulevard
Delta Building. Office 164
Houston, Texas 77058
Voice: 281-283-3805
Fax: 281-283-3869
boetticher@uhcl.edu

© 2002-2010 Boetticher Software Engineering Tools Course, All Rights Reserved.