CS 425 625 Software Engineering

1
CS 425 / 625Software Engineering

• Fall 2003
• Course Syllabus
• August 25, 2003

2
Outline

• The Instructor
• The Students
• The Course
• The Texts
• Initial WWW Pointers
• Grading Scheme
• Policies
• A Look Ahead

3
The Instructor.

• Sergiu Dascalu
• Room SEM-236
• Telephone [phone]
• E-mail dascalus_at_cs.unr.edu
• Web-site www.cs.unr.edu/dascalus
• Office hours
• Tuesday and Thursday 100 230 pm or by
  appointment or chance

4
.The Instructor

• Sergiu Dascalu
• PhD, Dalhousie U., Halifax, NS, Canada, 2001
• Teaching and research at Dalhousie University,
  1993-2001 (software engineering focus)
• Teaching and research at the University
  Politehnica Bucharest, Romania, 1984-1995
• (RT embedded systems focus)
• Consultant for software development companies in
  Canada and Romania

5
The Students

• Registration as of yesterday
• 425.001 35 students
• 425/625.002 17 students
• Prerequisites
• CS311 Challenges and Social Aspects in Computing
• Senior standing and Junior level coursework

6
The Course

• Outline This course examines the software
  process, from requirements elicitation and
  analysis, through specification and design, to
  implementation, integration, testing, and
  maintenance (evolution). A variety of concepts,
  principles, techniques, and tools will be
  presented, covering topics such as requirements
  engineering, project management, semi-formal and
  formal specifications, system models,
  architectural and detailed design, programming
  practices, verification and validation,
  re-engineering, and reverse engineering. Although
  the emphasis will be on object-oriented
  approaches some more traditional, structured
  software engineering techniques will also be
  discussed.

7
The Texts

• Textbook
• Ian Sommerville, Software Engineering, 6th
  Edition, Addison-Wesley, 2000 (ISBN
  0-201-39815-X)
• Lecture notes
• Presentations by the instructor
• Notes you take in the classroom
• Additional material as indicated later by the
  instructor

8
Initial WWW Pointers

• Ian Sommervilles web-page for the 6th edition of
  his Software Engineering book
• www.comp.lancs.ac.uk/computing/resources/IanS/
• SE6/index.html
• The Software Engineering Institute, at Carnegie
  Mellon University
• www.sei.cmu.edu
• The Object Management Group web-site
• www.omg.com
• More will be indicated later

9
Grading Scheme..

• Tentative (slight modifications are possible)
• Individual assignments 10
• Team project 30
• Midterm tests 24
• Final exam (comprehensive) 30
• Class participation 6
• TOTAL 100
• Note that there are no make-up tests or homework
  in this course

10
.Grading Scheme.

• Passing conditions (all must be met)
• 50 overall
• 50 in tests (midterm tests and final exam)
• 50 in assignments, project, class participation

11
..Grading Scheme

• In addition, for graduate and honors students a
  technical essay is required, worth 10. In this
  essay you must obtain at least 50 (in addition
  to the passing conditions on the previous page).
  Thus, graduate students and honors students will
  have a maximum possible of 110 points for the
  course.

12
Grading Scale regular

• Numerical-letter grade correspondence (regular)
• A 90 -100
  maximum 100
• A- 86 - 89
• B 83 - 85
• B 77 - 82
• B- 73 - 76
• C 70 - 72
• C 64 - 69
• C- 61 - 63
• D 58 - 60
• D 54 - 57
• D- 50 - 53
• F lt 50

13
Grading Scale grad/honors

• Numerical-letter grade correspondence
  (grad/honors)
• A 100 110
  maximum 110
• A- 95 - 99
• B 91 - 94
• B 85 - 90
• B- 80 - 84
• C 77 - 79
• C 71 - 76
• C- 67 - 70
• D 64 - 66
• D 59 - 63
• D- 55 - 58
• F lt 55

14
Policies..

• Late submission policy
• Maximum 2 late days per assignment/project
  deliverable
• Each late day penalized with 10
• No subdivision of late days
• Example a 90/100 worth assignment gets 81/100 if
  one day late (900.9 81) or 72/100 if two days
  late (900.8 72)

15
.Policies.

• Legal notices on the world-wide web Read and
  comply with accompanying legal notices of
  downloadable material
• Specify references used in assignments and
  project
• Do not plagiarize (see next slide)

16
..Policies

• Plagiarism and cheating Will not be tolerated.
  Please read the policies of University of Nevada,
  Reno regarding academic dishonesty
• www.unr.edu/stsv/acdispol.html

17
A Look Ahead

• The 7 parts of Ian Sommervilles textbook on
  Software Engineering (6th edition)
• Overview
• Requirements
• Design
• Critical Systems
• Verification and Validation
• Management
• Evolution

18
.A Look Ahead..

• Summary of course objectives
• Comprehensive study of structured and
  object-oriented software engineering concepts,
  principles, and techniques
• Extensive coverage of phases and activities of
  the software process
• Study of several advanced software engineering
  topics
• Practical software development work

19
..A Look Ahead.

• My intentions/expectations
• Provide guidance in the complex software
  engineering spectrum
• Help you be better prepared for practical
  software development work
• Open perspectives on software engineering topics
• Hope that you will both work hard and enjoy your
  work in this course

20
A Look Ahead

• Your intentions/expectations?
• In what ways do you think this course could help
  your professional development?
• What topics are you most interested in?
• What suggestions do you have for the instructor
  and/or the course?
• Are you ready for the ride?