UNIVERSITY OF MARYLAND UNIVERSITY COLLEGE

Software Engineering Principles and Techniques

CMIS 330, SECTION 4072

Fall Semester 2005

Tuesdays and Thursdays, 7 to 10 PM
Biology/Psychology 1124
College Park

September 6 through October 25, 2005

INSTRUCTOR: Nicholas Duchon.
I can be reached at:
540-338-7120 (home), and
duchon@nova.umuc.edu (e-mail),
Subject Code: "CMSC 130 - ".
Web pages start at: http://nova.umuc.edu/~duchon
Generally, mornings are the best times to call.
Normally, I will respond to e-mail within 24 hrs.
TA: Michael Elms
Work 301-497-5820
Home 410-480-8422
e-mail: melms1972@yahoo.com
Be nice - he is here to help with the projects but don't overburden him!
WebTycho enhanced: http://tychousa.umuc.edu
Weather related cancellations: http://www.umuc.edu/weather

Corrections:

Prerequisite(s):

Description:

A study of the process of software engineering from initial concept through design, development testing, and maintenance to retirement of the product. Development life-cycle models are presented. Issues in configuration management, integration and testing, software quality, quality assurance, security, fault tolerance, project economics, operations, human factors, and organizational structures are considered. Students may receive credit for only one of the following courses: CMIS 330 or CMIS 388A.

Objectives:

After completing this course, you should be able to:

Required Texts:

Author
Title
Publisher
ISBN
Pressman, Roger S.
Software Engineering: A Prectitioner's Approach,
6th Edition
McGraw Hill
0-07-285318-2

Grading Information and Scale:

 

Course Grading

Assignment Weights

Project Grading

Homework Grading

A 90 - 100
B 80 - 89
C 70 - 79
D 60 - 69
F 0 - 59

Final 25%
Midterm 20%
Projects 34%
Homework
21%

Label
Weight %
Explanation
s
20%
Sections -
Correct document structure
c
60%
Content -
Appropriate information in each section
p
20%
Presentation -
Writing, graphics, etc.

Label
Weight %
Explanation
r
20%
Relevance -
How well the material addresses the topic
c
60%
Content -
Depth of presentation
Connections to material in text
p
20%
Presentation -
Writing, graphics, etc.


Detailed Assignment weights:


Name
Abbreviation
Points
% of final ave
Due Date
Notes.
Extra information about individual project and homework requirements
will be posted in the appropriate Tycho conference.
final
f
100
25
10/25
Final Exam - open book, open notes, calculator OK
midterm
m
100
20
10/4
Midterm Exam - open book, open notes, calculator OK
System Specification (SSS)
p1
100
6
9/15
http://rspa.com/docs/Systemspec.html
Software Requirements (SRS)
p2
100
7
9/22
http://rspa.com/docs/Reqmspec.html
Software Design Document (SDD)
p3
100
7
9/29
http://rspa.com/docs/Designspec.html
Software Test Specification (STS)
p4
100
7
10/11
http://rspa.com/docs/Testspec.html
Software Project Plan (SPP)
p5
100
7
10/18
http://rspa.com/docs/Projectplan.html
Personal Experience
h1
100
3
9/8
2-3 pages - describe a personal experience developing software, using the language presented in out text
Spectacular Failure
h2
100
3
9/13
2-3 pages - research and describe a spectacular software failure. Include the situation, the problem, and the effects
Requirements Conversation
h3
100
3
9/20
2-3 pages - present an actual or hypothetical requirements elicitation conversation between a customer and software engineer. Include an evaluation of each questions and response in terms of realism and effectiveness.
OO vs Functional
h4
100
3
9/22
2-3 pages - Describe at least 4 scenarios, two where the OO approach is better, and two where the functional approach is more appropriate.
Test Plan
h5
100
3
9/27
2-3 pages - Develop a detailed test plan for a function. We will present a few possibilities in class, you may select your own.
Web Work
h6
100
3
10/6
2-3 pages - Discuss how software development for web applications is different than other software projects.
Paper Report
h7
100
3
10/13
2-3 pages - Present a summary of a published project estimate, and your assessment in light of the topics we have discussed in this class.

Cross-curricular initiatives for this Course:

Cross-curricular initiatives Activity in this class that fulfills the initiative
Effective Writing Development of detailed technical  documentation including  the system specification , software requirements specification, software design document, software test specification, and software project plan
Competence in Information Technology Use of software engineering tools
Historical Perspective Understanding the evolving role of software
International Perspective Global uses of software engineering
Civic Responsibility Discussions on software quality assurance and software safety
Information Literacy Research of object-oriented analysis methods and tools available on the web

Writing Resources:

UMUC has an online guide to writing and research in available at http://tychousa.umuc.edu/writinggde/

Project Descriptions:

You may choose to work in groups of up to 5 members.

To reinforce the software development process, the course project entails submitting software development products. These products are documents that are generated in the course of software development. The only software development product not to be submitted is the program source code. Refer to the course schedule for project submission due dates.

The software development documents that you are to submit are:
  1. The system specification (SS)
  2. The software requirements specification (SRS)
  3. The software design document (SDD)
  4. The software test specification (STS)
  5. The software project plan (SPP)
Recommended outlines are available at Pressman and Associate's web site: http://www.rspa.com/, under Process Models.

Each of these documents should be on the order of 7 to 10 typed pages delivered in MS Word format. Technical content rather than document size is the factor that will be considered for grading. Graphical content will satisfy the page requirements if supported by explanatory text.

More information on each document will be available in the appropriate Tycho conference topic and will be discussed in class.

Project Statement:

This problem statement will be the focus of your project.

We will discuss possible project topics and their specifications in class.

Course Schedule:

The assignments are from the reinforcement exercises in G&T, the projects are described above.

Date
Week
Starting
Class Module Topic

Readings

Pressman 6th

Chapters

Assignments


Date Due
Submit by
WebTycho
9/6
1 1.I
The Process
1, 2

-
9/8
2 1.II-III
Models
3, 4
h1: Personal Experience
9/8
9/13
3 1.IV
System Engineering
5, 6
h2: Spectacular Failure
9/13
9/15
4 1.IV, 2.I, 2.II
Requirements and Analysis
7, 8
Project - p1 - System Specification
9/15
9/20
5 1.V, 2.III
Design
9, 10, 11
h3: Requirements Conversation
9/20
9/22
6 3.II,
Human/Computer Interface and Testing
12, 13, 14
h4: Two scenarios: better functional vs better OO
Project - p2 - Software Requirements
9/22
9/27
7 3.I
Web Planning
16, 17
h5: Test plan for math function
9/27
9/29
8 3.I
Web Designing and Testing
18, 19, 20
Project - p3 - Software Design Document
9/29
10/4
9
MIDTERM

10/4
10/6
10 6.I, 6.II
Management and Metrics
21, 15, 22
h6: What makes web work special?
10/6
10/11
11 6.IV-VI
Estimation, Scheduling and Risk
23, 24, 25
Project - p4 - Software Test Specification
10/11
10/13
12
4.II
Quality and Change
26, 27
h7: Report on a project estimate professional paper
10/13
10/18
13
-
Advanced Topics
28, 29, 30, 31, 32
Project - p5 - Software Project Plan
10/18
10/20
-
-
HOLIDAY


-
10/25
14
-
FINAL

10/25

Policies and Expectations

Make-up exams:

Exams are to be taken on the dates specified in the syllabus. Make-up exams will only be given with valid and verifiable reasons and only if the student notifies the instructor prior to the exam date. If approved by the instructor, make-up exams will be administered through the Test Center. There is a fee for this service.

Late Assignments:

Late assignments will only be accepted with prior approval from the instructor and for valid and verifiable reasons.

Final Exam Format:

The format of all exams is open notes and open book. You may use a calculator. There are between 5 and 10 questions, some short answer.

Attendance:

The student is responsible for attending all classes and any related activities regularly and punctually. Absences from class do not excuse a student from missed coursework. Much of the benefits of this course is derived from practice with other during class sessions. It is expected, therefore, that the assigned chapters be read before each class meeting so students may participate during class time to the fullest.

Withdrawal:

In the event you must withdraw from this course, follow the formal procedure found in the UMUC undergraduate catalog. Your request to withdraw, resulting in a grade of "W", must be submitted to the appropriate parties at least two weeks before the last scheduled class session. Failure to adhere to the appropriate process will result in a Grade of "F".

Academic Integrity:

Students of University College are expected to conduct themselves in a manner that will contribute to the maintenance of academic integrity. All students are responsible for adhering to the UniversityØs policies regarding integrity and dishonesty stated in the college catalog. All incidents of inappropriate academic integrity will be turned over to the Administration for investigation and will result in all students involved receiving a 0 or "F" on the assignment or exam.

Academic Policies (School of Undergraduate Studies)

Grading Methods

There are four grading methods at UMUC. The most commonly used is the standard method. The pass/fail alternative is available only under limited conditions. The satisfactory/D/fail method is restricted to certain specified courses at higher levels. Any course may be audited.

GRADE INTERPRETATION QUALITY POINTS
A Outstanding scholarship 4
B Good scholarship 3
C Satisfactory scholarship 2
D Marginal performance 1
F Failure 0
I Incomplete 0
AU Audit 0
W Withdrawal 0

Incomplete: The Mark of I

The mark of I (incomplete) is an exceptional mark given only to students whose work in a course has been satisfactory but who for reasons beyond their control have been unable to complete all the requirements of a course. The following criteria must be met:
The procedure for awarding the mark of I is as follows:
If the mark of I is not made up within six months or by the agreed-upon deadline, the I is changed to an F.

The mark of I cannot be removed by means of credit by examination, nor can it be replaced by a mark of W (defined below). Students who elect to repeat an incomplete course must register again for the course, pay all applicable fees, and repeat the course. For purposes of academic retention, the course grade is counted as an F. The mark of I is not used in determining grade-point averages.

Withdrawal: The Mark of W

Students may receive the mark of W by withdrawing through the Interactive Registration and Information System (IRIS), by completing a registration-change form in Undergraduate Student Affairs, or by submitting a written request approximately two weeks before the last scheduled class in a semester or term. Any of these procedures constitutes official withdrawal.

This mark appears on the permanent record unless withdrawal is completed before a course begins. For purposes of academic retention, the mark of W is counted as attempted hours. It is not used in determining grade-point averages.

Attendance

The student is responsible for attending all classes and any related activities regularly and punctually. Absence from class does not excuse a student from missed coursework. The student is responsible for obtaining detailed information about missed class sessions, including their content, activities covered, and any announcements or assignments. Failure to complete any required coursework may adversely affect the student's grade. Teachers are not expected to repeat material that a student has missed because of the student's absence from class.

In some courses, in which active participation is integral to the learning process, teachers may base part of the final grade on class participation; those courses obviously require regular attendance. Teachers must announce any such requirement at the beginning of the semester.

Examinations

The student is responsible for obtaining information about quizzes and examination schedules and policies at http://www.umuc.edu. Final examinations are usually given during the last scheduled class meeting.

Make-up examinations and tests may be given to students who for valid reasons are unable to take exams at the scheduled time. Teachers are not required to offer make-up examinations because of a student's absence unless the student can present evidence that it was caused by unavoidable circumstances or occurred on a religious holiday. In such cases, an examination may be rescheduled for the mutual convenience of student and teacher and must cover only the material for which the student was originally responsible. Such a rescheduling must not cause a conflict with the student's other classes. The Testing Center schedules make-up exam sessions for students whose teachers cannot schedule a special make-up session. There is a fee for this service. You can reach the Testing Center at dess@www.umuc.edu. To make arrangements, contact the Testing Center at 301-985-7645 or 1-800-283-6832, extension 7645.

Photo ID Policy for Exams

When you take examinations and tests, the proctor will require you to show a picture ID such as a valid driver's license or similar ID. Please remember to bring your ID.

Academic Integrity

Integrity in teaching and learning is a fundamental principle of a university. UMUC believes that all members of the university community share the responsibility for academic integrity, as expressed in the University System of Maryland policy "Faculty, Student, and Institutional Rights and Responsibilities for Academic Integrity." Details are available from the Office of the Dean, School of Undergraduate Studies.

At UMUC, faculty members are expected to establish classroom environments conducive to the maintenance of academic integrity by promptly giving students a complete syllabus describing the course and its requirements, grading submitted work promptly and adequately, and arranging appropriate testing conditions, including having faculty members monitor examinations given in class.

Students at UMUC are expected to conduct themselves in a manner that will contribute to the maintenance of academic integrity.

Failure to maintain academic integrity (academic dishonesty) may result in disciplinary action.

Academic dishonesty includes but is not limited to obtaining or giving aid on an examination, having unauthorized prior knowledge of an examination, doing work for another student, and plagiarism.

Plagiarism is the presentation of another person's idea or product as one's own. Plagiarism includes (but is not limited to) copying verbatim all or part of another person's work; using phrases, charts, figures, illustrations, computer programs, or mathematical or scientific solutions without citing the source; paraphrasing ideas, conclusions, or research without citing the source; and using all or part of a literary plot, poem, film, musical score, or other artistic product without attributing the work to its creator.

Students can avoid unintentional plagiarism by carefully following accepted scholarly practices. Notes taken for papers and research projects should accurately record sources of material to be cited, quoted, paraphrased, or summarized, and papers should acknowledge those sources in footnotes.

UMUC's policy on Academic Dishonesty and Plagiarism can be found in the current copy of the Undergraduate Catalog or is available from the Office of the Dean, School of Undergraduate Studies.

Appealing a Grade

Procedures for appealing a grade are available from the Office of the Dean, School of Undergraduate Studies or in the current copy of the Undergraduate Catalog.

There is a time limit for appealing a grade. Therefore, students who want to appeal a grade must initiate the process within 30 days of the posting of the grade.

Code of Student Conduct

Students are subject to the UMUC Code of Student Conduct, which can be found at in the current copy of the Undergraduate Catalog or is available from the Office of the Dean, School of Undergraduate Studies. Violations of the code are considered to be violations of UMUC policy and are grounds for discipline by UMUC. Allegations of misconduct by UMUC students should be referred to the associate provost, Undergraduate Student Affairs.

Change of Address

Students who move during the semester or term should not only leave a forwarding address with the U.S. Postal Service but should also notify Undergraduate Student Affairs as soon as possible.

Students with Disabilities

If you are a student with a disability who needs accommodations in this course, you must register with Veteran and Disabled Student Affairs. You will need to provide documentation of a disability and its impact on the course in order to receive accommodations. Please contact Veteran and Disabled Student Affairs at 301-985-7930 or 800-888-UMUC, extension 7930 or by email at vdsa@umuc.edu.

Additional Information:

STUDENT COLLABORATION: Students learn a great deal from working together on assigned out of class material. For this reason they are encouraged to discuss assignments among themselves freely. This discussion may include things ranging from general approach to resolving specific problems.

COMPUTER ACCOUNTS: See http://www.umuc.edu/suppserv/it/hosts/itfaq.html for information about creating student and class accounts.

REMINDER: It is essential that you read the system news every time you use this system.

FIRST CONTACT: Please include the code shown above in the subject field of all e-mail you send me about this class - I use mail filtering and this code will make help put me in the right frame of mind to answer your questions. As soon as possible, you should each get onto an e-mail system and send me (at duchon@nova.umuc.edu) a message with your name and telephone numbers. This will allow me to contact you should any problems occur during the semester, as well as make it possible for me to associate you with your computer account.

E-MAIL FORMATS: The simplest format for me to accept is an ASCII mail message, I can use my mailer to simply respond to the message. I can handle some other formats, but the more I have to work to decipher your message, the less happy I will be. You can submit a text file as an attachment from most mailers. The mailer I use is Netscape on a PC, so attaching PC format files (MS Word is the best) will not give me very much trouble. RTF formatted files seem to get to me without any problems. While I can interpret some MIME and uuencoded files, they do require a significant amount of effort, so I may simply respond with a message asking you to resend the message as ASCII text.

SPECIAL NOTE: Because many computer mailboxes are difficult to reach, I strongly suggest that you give me a permanent UMUC address (typically an account on polaris.umuc.edu) as your primary mailing address. You may forward your mail from that account using the ".forward" file. I have found that I seem to have the greatest problem with military mail servers. If you have sent me an e-mail message and I have not responded within 48 hours, I suggest that you try sending me another message with a more common return address. If I still do not respond, please contact me by telephone so we can arrange a better e-mail system.