|
Instructor
Information
|
|
Name
|
Dr. William Mitchell
|
|
Email
|
wmmitchell@ualr.edu
|
|
Office location
|
ETAS 202
|
|
Office hours
|
9-11:30 & 2-5:30 Daily
|
|
Phone
|
683-7117
|
|
Biography
|
Associate Dean of the CyberCollege. Professor of
Information Science. Web page: www.ualr.edu/wmmitchell
|
|
Course Information
|
|
Course title
|
Software Engineering
|
|
Course number
|
CPSC 4373
|
|
Course discipline
|
Software and Programming
|
|
Course description
|
Prerequisites: CPSC 2380 and 3375 or 3385, MATH
1305.analysis of system requirements, software systems design techniques,
software processes, software life-cycle models, software economics,
configuration management, user interfaces, software testing and software
maintenance. Students gain experience in the team approach to medium/large
system development. Three hours lecture per week. Three credit hours.
|
|
Course date
|
Tuesday, August 26, 2003 through Tuesday, December 9,
2003
|
|
Location
|
ETAS 231
|
|
Meeting day(s)
|
Tues & Thurs
|
|
Meeting time(s)
|
1:40-2:55 pm
|
|
Prerequisite(s)
|
Data Structures and either Database or File Structures.
This is considered a capstone course for the CS major so you should be
experienced in programming.
|
|
Course Goals
|
|
Course Goals
|
During the course we will develop a piece of software,
read a text to become aware of issues that we may not encounter in our
exercise, and reflect upon the professional discipline of software engineering.
The project will be conducted as a team with each member responsible for
certain deliverables. At the conclusion of the course each student should
- appreciate
the mechanics of working in a software development team
- understand
the process of building software to specification on a schedule
- be
knowledgeable about the economics of software development (the
estimation and measurement of resources expended in building a
software product)
- comprehend the discipline of
software engineering and the problems of software quality.
|
|
Policies
|
|
Introduction
|
Regular attendance is essential. Tuesdays will focus on
the text and the theory of software engineering. Thursdays will focus on
the project (assignments will be due by 2 pm each Thursday). Lecture
material will be posted as power points and summarize the text. You are
expected to come to class ready to discuss the designated topics.
|
|
Additional information
|
DISABLED STUDENT POLICY:
It
is the policy of UALR to accommodate students with disabilities, pursuant
to federal and state law. Any student with a disability who needs
accommodation, for example in seating placement or in arrangements for
examinations, should inform the instructor at the beginning of the course.
The chair of the department offering this course is also available to
assist with accommodations. Students with disabilities are also encouraged
to contact the Office of Disability Support Services, which is located in
the Donaghey Student Center, Room 103, telephone 569-3143.
|
|
Textbook
|
|
Required reading
|
Software Engineering, Sommerville, Addison
Wesley, 6th, 0 201 39815 X
|
|
Course Requirements
|
|
Introduction
|
The major focus of the assignments is on planning, documenting,
implementing, and evaluating a software product. To accomplish this we must
survey the techniques of software engineering and apply those that are
appropriate, as well as study the application and its users.
|
|
Requirements
|
- The
project will count 40% of the course grade and will be evaluated in
three parts: the software grade, shared by all the team members: 40%
of the project grade. The individual deliverables, evaluated by the
instructor, 40% of the project grade. Peer evaluations on contributions
to the project effort, 20% of the project grade.
- The
midterm and the final will each count 15% of the course grade.
- Contribution
to Presentations will count 10% of the course grade
- A
5-page research paper on Software Engineering will count 10%
- Other homework assignments
will count 10%
|
|
Meeting Schedule
|
|
|
Date Topic
Aug 26 Chapter 1
Aug 28 Turning Machines
Sep 2 Chap 2&3
Sep 4 Chap 4
Sep 9 Chap 15
Sep 11 team roles
Sep 16 Chap 5&6
Sep 18 Prototype Presentations
Sep 23 Chap 7&8
Sep 25
Sep 30 Chap 10&11
Oct 2 functional specifications
Oct 7 Chap 12&14
Oct 9 Design Presentations
Oct 14 Chap 19&20
Oct 16 design specifications
Oct 21 review
Oct 23
Oct 28 Midterm exam
Oct 30 Testing Presentations
Nov 4 Chap 22&23
Nov 6
Nov 11 Chap 24&25
Nov 13 Alpha Presentation
Nov 18 Chap 26&27
Nov 20
Nov 25 Chap 28&29
Nov 27 Thanksgiving holiday
Dec 2
Dec 4 Beta Presentation
Dec 9 review
Dec 11 Final exam (1:30-3:30)
|