Skip to content

Principles of Software Engineering, software development process and what constitutes well engineered software, software specification and requirements definition

Notifications You must be signed in to change notification settings

vincentclee/csci4050-software_engineering

Repository files navigation

Use Case Description
Course CSCI 4050/6050 Software Engineering
Term Fall 2013
Lecturer Krys J. Kochut, [email protected]
Office 546 GSRC
Office Hours T 1:30 - 3:30pm and W 9:00 - 10:00am and by appointment
TA Neda Abolhassani [email protected]
Office Hours W 2:30 - 3:30pm in 307 Boyd GSRC
Text Object-Oriented Software Engineering: Using UML, Patterns, and Java. 3nd Ed., by Bernd Bruegge and Allen H. Dutoit, Prentice Hall, 2010.
Grading Homeworks & quizzes 10%
Midterm 25%
Final 35%
Term project 30%
Grading Scale 90 - 100 A
88 - 89 A-
86 - 87 B+
80 - 85 B
78 - 79 B-
76 - 77 C+
70 - 75 C
68 - 69 C-
65 - 67 D
Notes In this course we will study the principles of Software Engineering. We will begin with introductory discussion of the software development process and what constitutes well engineered software. Then we will move on to software specification and requirements definition.

The next (major) part of the course will be devoted to software design. Although we will discuss several of the major design techniques, we will specifically concentrate on Object-Oriented Design (OOD). We will also discuss the principles of user interface design, concentrating on Graphical User Interfaces (GUIs).

A large portion of the course will be devoted to programming techniques, geared for reliable software development and software reuse. We will conclude the course with the discussions of software verification and validation techniques.

The programming projects will be done in either C++ or Java. Each project will include a permanent data store and a graphical user interface. The projects will be assigned and discussed at a later date.

Each student is expected to do his/her own work, but programming projects will involve team work, so communication is not only encouraged, but necessary. The grade of I (incomplete) is reserved for special cases only, such as a serious illness, and will be decided on individual basis.

All academic work must meet the standards contained in "A Culture of Honesty." Students are responsible for informing themselves about those standards before per- forming any academic work.

The course syllabus is a general plan for the course; deviations announced to the class by the instructor may be necessary.
Exam dates Midterm October 10, 2013, regular class time
Final December 10, 2013, 8:00 - 11:00am

About

Principles of Software Engineering, software development process and what constitutes well engineered software, software specification and requirements definition

Resources

Stars

Watchers

Forks

Releases

No releases published

Packages

No packages published

Languages