CS 425 / CS 625 Software Engineering

1
CS 425 / CS 625Software Engineering

• Fall 2009
• Course Syllabus
• August 24, 2009

2
Outline

• The Instructor the TAs
• The Students
• The Course
• The Texts
• Initial WWW Pointers
• Grading Scheme
• Policies
• A Look Ahead
• Tentative Schedule

3
The Instructor TAs

• Instructor Sergiu Dascalu
• Room SEM-236
• Telephone [phone]
• E-mail dascalus_at_cse.unr.edu
• Web-site www.cse.unr.edu/dascalus
• Office hours
• WED 530 700 pm
• or by appointment or chance
• TAs (partial)
• Zack Norcross
• Sohei Okamoto
• Muhanna Muhanna
• Web-site www.cse.unr.edu/muhanna

4
The Students

• Registration as of today
• CS 425 37 students
• Prerequisites
• CS 446 Operating Systems, CH 201, ENG 102

5
The Course.

• Catalog description
• Lecture Lab 3 0 Credit(s) 3
• Requirements specifications, structured
  analysis,
• modeling, top down design, testability,
  maintainability,
• portability, verification and validation,
  modification,
• configuration, management, reliability,
  efficiency,
• complexity, compatibility, modularity,
  interfacing, hardware and language issues. (Major
  capstone course.) Pre-requisite CS446
• Outline This course covers the software
  development process, from requirements
  elicitation and analysis, through specification
  and design, to implementation, integration,
  testing, and evolution (maintenance).
  continued on next page

6
.The Course

• Outline contd A variety of concepts,
  principles, techniques, and tools are presented,
  covering topics such as software processes,
  project management, people management, software
  requirements, system models, architectural and
  detailed design, user interface design,
  programming practices, verification and
  validation, and software evolution.
• Although the emphasis will be on modern,
  object-oriented approaches some more traditional,
  structured software engineering techniques will
  also be discussed.

7
The Texts

• Textbook
• SE-8 Ian Sommerville, Software Engineering,
  8th Edition, Addison-Wesley, 2006.
• 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 8th edition of
  his Software Engineering book
• http//www.cs.st-andrews.ac.uk/ifs/Books/SE8/ind
  ex.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 12
• Team project 40
• Midterm test 14
• Final exam (comprehensive) 28
• Class participation 6
• TOTAL 100
• Note that there are no make-up tests or homework
  in this course
• Poor class participation will impact
  significantly your grade, beyond 6

10
.Grading Scheme.

• Passing conditions (all must be met)
• 50 overall
• 50 in tests (midterm test and final exam)
• 50 in assignments, project, class participation
• For grade A at least 90 overall and at least
  90 in class participation

11
..Grading Scheme

• In addition, for 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,
  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 honors

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

14
Disability statement

• If you have a disability for which you need to
  request accommodations, please contact as soon as
  possible the instructors or the Disability
  Resource Center (Thompson Student Services -
  107).

15
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)

16
.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)

17
..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

18
A Look Ahead..

• The 7 parts of Ian Sommervilles textbook on
  Software Engineering (8th edition)
• Overview
• Requirements
• Design
• Development
• Verification and Validation
• Managing People
• Emerging Technologies

19
.A Look Ahead tentative schedule.
Week Dates (M, W) Contents
1 Aug 24, 26 Lectures Overview
2 Sep 02, 04 Lectures Overview, A1 given
3 Sep --, 09 Lecture Overview
4 Sep 14, 16 Lectures Requirements, A2 given A1 due
5 Sep 21, 23 Lectures Requirements, Invited talk IT
6 Sep 28, 30 Lecture Requirements, Analysis, Project P1 given, A2 due
7 Oct 5, 7 Lectures Design, Technical essay given TESS
20
..A Look Ahead tentative schedule
8 Oct 12, 14 Lectures Design, P2 given Project P1 due
9 Oct 19, 21 Lectures Design, Midterm 10/21
10 Oct 26, 28 Lectures Design, Development, Project P3 Given Project P2 due
11 Nov 02, 04 Lectures Development
12 Nov 09, -- Lecture Verif. Validation, Project P4 given Project P3 due
13 Nov 16, 18 Lecture Verif. Validation, Invited talk IT
14 Nov 23, 25 Lectures Managing People
15 Nov 30, Dec 02 Lectures Emerging Technologies Technical essay (TESS) due
16 Dec 07, - Project P4 due, Demo (12/ 07 08) Final EXAM (12/14)
21
A Look Ahead..

• Summary of course objectives
• Comprehensive study of software engineering
  concepts, principles, and techniques
• Extensive coverage of the phases and activities
  of the software process
• Study of several advanced software engineering
  topics such as real-time software designs, agile
  methods, and critical systems
• Practical software development work within the
  framework of integrated development environments

22
.A Look Ahead.

• Our 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 Hope
  that you will both work hard and enjoy the work
  in this course

23
..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 instructors
  and the course?

24
Course updates

• Only one midterm instead of two
• In project part 3, focus on analysis instead of
  design
• More emphasis on project prototyping
• Hopefully, more project topics from industry
• Likely, one short class presentation on project

25
Next classes

• WED Aug 26
• Class on the need for software engineering
  short videos with well-known SE researchers and
  practitioners
• Students introduction (be prepared to talk 1
  minute or so about yourself)