Syllabus
Home Syllabus Expertise Project Plan Specifications Design Test Plan User Manual Specifications Eval Design Eval Test Plan Eval Team Members Eval

 

Course

Software Engineering (CSIS640-01)

Credit Hours

3.0

Semester

Spring 2000

Time

1:00 -1:50

Days

MWF

Location

Kelce 215

Instructor

Kailash Chandra

Office

Room 223D Kelce

Office Phone

235-4536

E-Mail Address

kchandra@pittstate.edu

Office Hours

MWF     10:50 AM - 1:00 PM

TuTh      8:45 AM - 9:30 AM, 10:45 AM - 11:45 AM

Course Description

Survey of methods of definition, design, development, documentation, and implementation of significant software systems. Formal theories for representation, correctness, and related development tools. Individual and team projects drawn from computer science and information systems applications.

Prerequisite(s)

Principles of Software Design (CSIS 250), Systems Analysis and Design (CSIS 280), and Senior Standing.

Course Objectives

To review the software development process, to introduce modern tools and techniques used in software engineering and to gain experience with those techniques through group projects.

Text

Software Engineering, A Practitioner's Approach, Roger Pressman, 4th. Edition, McGraw-Hill, 1997.

Suggested Readings

Software Engineering Economics, B. Boehm, Prentice-Hall, 1981.

The Mythical Man-Month, F. Brooks, Addison-Wesley, 1975.

Object-Oriented Software Engineering, B. Bruegge and A. H. Dutoit, Prentice Hall, 2000.

The Unified Modeling Language User Guide, G. Booch, J. Rumbaugh, and I. Jacobson, Addision-Wesley, 1999.

Grading

There will be 2 exams. Each exam is 15% of the final grade.

There will be a final exam counting 15% of the grade.

There will be a written and oral report counting a total of 8% of the grade.

There will be group projects totaling 47% of the grade.

There will be several bonus point opportunities.

The grade scale is 90% A, 80% B, 70% C, and 60% D.

 

REPORT: Each student will prepare an oral and written report based on at least two articles from the recent literature related to Software Engineering. The oral report should be 5 - 10 minutes in length. The written report should be approximately 5 pages long (double spaced).

PROJECT: The project will involve working in a team environment. The team will prepare a formal functional specifications document, design document, test plan, and user's manual for the system that the team is implementing. The system can be coded in any language that is appropriate for the type of system being developed, is available, and is familiar to all the team members. The resulting system will be demonstrated in class at the end of the semester. Some class time will be devoted to evaluations, inspections, and presentations of team progress reports. Grades will be assigned for each project component as well as for the overall project.

 

Software Engineering Team Project Components and Grading

 

Project Component                                      Points

Project Plan                                                             50

Specifications Document                                          65

Design Document                                                    65

Test Plan                                                                 60

User Manual                                                           50

In-Class Presentation and Demonstration                60

Coding and Project Completion                             120

Total                                                                     470

 

The team project points will be computed as the sum of the points earned on each component of the project. Points will be deducted for documents which are not submitted on or before the due date.

The project grades for individual team members will be derived from the team project points and the team member's evaluation. Team members will evaluate their own contributions as well as the contributions of other team members to the team project. The average computed from the evaluation data will be used to determine whether or not the team member will receive all of the points earned by his/her team for the project. Team members will be evaluated on a scale of 1 to 10 in the areas of time spent on the project, cooperativeness, and total contribution to the project. The average of the evaluations in each area must be 5. The evaluation score for each team member is computed by computing the average of the sum of their evaluations as submitted by each team member. If that average is at least 12 then the team member will receive all of the points earned by his/her team for the project. If the average is below 12 a deduction will be made using a linear scale. If the average is above 18 then the team member will receive a bonus.

Topics to be Covered

The Product

The Process

Project Management Concepts

Software Process and Project Metrics

Software Project Planning

Risk Management

Project Scheduling and Tracking

Software Quality Assurance

Software Configuration Management

System Engineering

Analysis Concepts and Principles

Analysis Modeling

Design Concepts and Principles

Design Methods

Design for Real-Time Systems

Software Testing Methods

Software Testing Strategies

Technical Metrics for Software

Object-Oriented Concepts and Principles

Object-Oriented Analysis

Object-Oriented Design

Object-Oriented Testing

Technical Metrics for Object-Oriented Systems

Policy

Homework is due at the beginning of the class on the due date.  Late homework will be accepted, but you will lose 25% of the total points for each CALENDAR day past the deadline.

It is expected that the student meets his/her classes and it is the responsibility of the students to inform the instructor of reasons, for extended absences.

The instructor reserves the right to alter the sequence of topics and to substitute other topics for those listed.

Academic misconduct or dishonesty is inconsistent with membership in an academic community.  Please refer to page 32 in the 1995-97 University Catalog for details.

Students seeking assistance with academic program because of handicap should contact Teresa R. Massa, Director of Equal Opportunity, 125 Whitesitt Hall (telephone 235-4189).  Students with learning disabilities should contact Dr. Nick Henry, Special Services and Leadership Studies, College of Education Building (telephone 235-4966).  Please inform the instructor if you have a handicap or a disability that the instructor needs to know about.