11

CS691z / CS 791zCS691z / CS 791zTopics on Software EngineeringTopics on Software Engineering

Spring 2007Spring 2007Course Syllabus (tentative)Course Syllabus (tentative)

January 23, 2007January 23, 2007

22

Outline The InstructorThe Instructor The StudentsThe Students The CourseThe Course The Texts & Initial WWW PointersThe Texts & Initial WWW Pointers Grading Scheme: CS691z/791z & ScaleGrading Scheme: CS691z/791z & Scale PoliciesPolicies Summary of Course ObjectivesSummary of Course Objectives A Look AheadA Look Ahead

33

The Instructor.

Sergiu DascaluRoom SEM-236Telephone 784-4613E-mail dascalus@cse.unr.eduWeb-site www.cse.unr.edu/~dascalusOffice hours:

T 4:00 - 5:00 pm; R 5:00 – 6:00 pm or by appointment or chance

44

.The Instructor

Sergiu Dascalu PhD, Dalhousie U., Halifax, NS, Canada, 2001 Faculty member at UNR since July 2002 Lecturer & RA at Dalhousie University, 1993-2001

(software engineering focus) Teaching and research at the University Politehnica

Bucharest, Romania, 1984-1993 (RTS focus) Consultant for software development companies in

Canada and Romania

55

The Students

Registered as of today:8 in CS691z + 4 in CS791z

Prerequisite: CS 425 Software Engineering or Instructor’s approval

66

The Course.The Course.

Classroom: Classroom: LP-104, TR 2:30 - 3:45 pmLP-104, TR 2:30 - 3:45 pm

Outline: This course explores research and This course explores research and development topics on software engineering, development topics on software engineering, encompassing principles, methods, and tools. Areas of encompassing principles, methods, and tools. Areas of research include software processes, requirements research include software processes, requirements analysis and specification, design, prototyping, analysis and specification, design, prototyping, implementation, validation and verification, evolution, implementation, validation and verification, evolution, documentation, project management, UML-based documentation, project management, UML-based modeling, development environments, and domain-modeling, development environments, and domain-specific applications. specific applications.

77

.The Course.The Course

Outline [continued]:

The course will allow the students to broaden their The course will allow the students to broaden their knowledge of software engineering concepts, principles, knowledge of software engineering concepts, principles, techniques and tools, study relevant research techniques and tools, study relevant research publications in the field, prepare and present a high publications in the field, prepare and present a high quality software engineering project and, based on this quality software engineering project and, based on this project, write a paper that could be submitted to a project, write a paper that could be submitted to a scientific conference. scientific conference.

88

The Texts.The Texts.

Required textbooks [to be confirmed]: Albert Endres, Dieter Rombach, A Handbook of

Software and Systems Engineering: Empirical Observations, Laws, and Theories, Pearson Addison-Wesley, 2003. ISBN: 0-321-15420-7.

99

.The Texts.The Texts Recommended textbooks (initial):

Ian Sommerville, Software Engineering, 8th Ed., Addison-Wesley, 2006.

Jim Arlow and Ila Neustadt, Jim Arlow and Ila Neustadt, UML and the Unified Process: UML and the Unified Process: PracticalPractical Object-Oriented Analysis and DesignObject-Oriented Analysis and Design, Addison Wesley, , Addison Wesley, 2002.ISBN: 0-201-77060-1.2002.ISBN: 0-201-77060-1.

Lecture notes:Lecture notes: Presentations by the instructorPresentations by the instructor Notes you take in the classroomNotes you take in the classroom

Additional material (papers, tutorials, etc.) that will be indicated Additional material (papers, tutorials, etc.) that will be indicated later by the instructorlater by the instructor

1010

Initial WWW PointersInitial WWW Pointers

IEEE’s Digital Library, via IEEE’s Digital Library, via www.ieee.orgwww.ieee.org ACM Digital Library, via ACM Digital Library, via www.acm.orgwww.acm.org The Software Engineering Institute, at Carnegie Mellon The Software Engineering Institute, at Carnegie Mellon

University, University, www.sei.cmu.eduwww.sei.cmu.edu IEEE Computer Society’s Technical Council on Software IEEE Computer Society’s Technical Council on Software

Engineering, Engineering, www.tcse.orgwww.tcse.org The Object Management Group, The Object Management Group, www.omg.comwww.omg.com IBM / Rational Software, IBM / Rational Software, www.rational.comwww.rational.com More will be indicated laterMore will be indicated later

1111

Grading Scheme..Grading Scheme..

Grading Scheme (subject to slight modifications):Grading Scheme (subject to slight modifications):

Assignments: A1, 2, [3] 10% Presentations: PRES1, [2], 3, 4 15% Midterm test: EXAM 20% Project: P1, 2, 3, 4 30% Paper:DRAFT, PPR 20% Class participation: PART* 5% [* assumes good presence; a large number of absences will affect the grade much

more significantly]

TOTAL 100%

1212

.Grading Scheme..Grading Scheme.

CS791Z CS791Z versusversus CS691Z CS691ZIn CS791Z there will be:In CS791Z there will be:

One more assignment One more presentation Longer paper – by 1 page, 2-column IEEE format [possibly] one more question in the midterm exam

1313

..Grading Scheme..Grading Scheme

Passing conditions Passing conditions ((all must be met):): 50% overall & 50% overall & 50% in test &50% in test & 50% in project and paper & 50% in project and paper & 50% in assignments, presentations, and class 50% in assignments, presentations, and class

participationparticipation For grade A: at least 90% overall, at least 90% For grade A: at least 90% overall, at least 90%

in class participation and at least 60% in test in class participation and at least 60% in test Note that there are no make-up tests or

homework in this course

1414

Grading ScaleGrading Scale

Numerical-letter grade correspondenceNumerical-letter grade correspondence AA 90 -10090 -100 A-A- 87 - 8987 - 89 B+B+ 84 - 8684 - 86 BB 79 - 8379 - 83 B-B- 75 - 7875 - 78 C+C+ 72 - 7472 - 74 CC 68 - 7168 - 71 C-C- 65 - 6765 - 67 D+D+ 61 - 6461 - 64 DD 56 - 60 56 - 60 D-D- 50 - 5550 - 55 FF < 50< 50

1515

Policies..Policies..

Late submission policy:Late submission policy: Maximum 2 late days per assignment/project

deliverable Each late day penalized with 10% No subdivision of late days (e.g. in hours) No late days for presentations and test Example: a 90/100 worth assignment gets 81/100 if one

day late (90*0.9 = 81) or 72/100 if two days late (90*0.8 = 72)

1616

.Policies..Policies.

Legal notices on the world-wide web: Read and Legal notices on the world-wide web: Read and comply with accompanying legal notices of comply with accompanying legal notices of downloadable materialdownloadable material

Specify references used Specify references used Do not plagiarize (see next slide)Do not plagiarize (see next slide)

1717

....PoliciesPolicies

Plagiarism and cheating will not be tolerated. Plagiarism and cheating will not be tolerated. Please read the policies of University of Nevada, Please read the policies of University of Nevada, Reno regarding academic dishonesty:Reno regarding academic dishonesty:

www.unr.edu/stsv/acdispol.htmlwww.unr.edu/stsv/acdispol.html

1818

Summary of Course ObjectivesSummary of Course Objectives

Course objectives:Course objectives: Extension of SE knowledge, in particular of software Extension of SE knowledge, in particular of software

process phases and modeling notationsprocess phases and modeling notations Study and presentation of relevant research publicationsStudy and presentation of relevant research publications Development of a high quality software projectDevelopment of a high quality software project WWriting a paper that can be submitted to a scientific riting a paper that can be submitted to a scientific

conferenceconference

1919

A Look Ahead.A Look Ahead.

My intentions & expectations:My intentions & expectations: Provide guidance in the SE spectrumProvide guidance in the SE spectrum Help you be better prepared for research and Help you be better prepared for research and

development in SEdevelopment in SE Guide you in writing an SE research paper Guide you in writing an SE research paper Hope that you will both work hard and enjoy your Hope that you will both work hard and enjoy your

work in this coursework in this course

2020

.A Look Ahead.A Look Ahead

Your intentions & expectations:Your intentions & expectations:Why do you take the course?Why do you take the course? In what ways do you think this course could In what ways do you think this course could

help your professional development?help your professional development?What is your experience so far with SE? What is your experience so far with SE? What topics are you interested in?What topics are you interested in?What suggestions do you have for the What suggestions do you have for the

instructor?instructor?

2121

Tentative schedule.Tentative schedule.Week Class Dates Contents

1 Jan 23, 25Course syllabus: course objectives, outline, organizationStudents’ introduction

2 Jan 30, Feb 1Lectures by the instructorDraw for presentations’ order

3 Feb 6, 8Lectures by the instructor Project teams set up (Feb 8)A#1 due – SE tool (Feb 9)

4 Feb 13, 15 Individual project meetings with the instructor

5 Feb 20, 22Presentations by students based on A#1 (PRES-1)A#2 due – Background (Feb 19)

6 Feb 27, Mar 1Presentations by students based on A#1 (PRES-1)Project concept due (P1- Feb 26)

7 Mar 6, 8A#3 due, CS791z only, textbook presentation (Mar 5)Presentations by students based on A#3 (PRES-2, text, CS791z only)

2222

.Tentative schedule.Tentative schedule

Week Class Dates Contents

8 Mat 13, 15 Lectures by the instructorProject specification due (P2 - Mar 16)

9 Mar 20, 22 Spring break, no classes

10 Mar 27, 29 Lectures by the instructorProject design due (P3 - Mar 30)

11 Apr 3, 5 Invited talk & Lecture by the instructor, recap for midterm Paper draft due (DRAFT – Apr 6)

12 Apr 10, 12 Lecture by the instructorMidterm exam (TEST - April 12)

13 Apr 17, 19 Presentations by students - project (PRES-3)

14 Apr 23, 25 Presentations by students – additional book reading (PRES-4)

15 Apr 30, May 2 Presentations by students - additional book reading (PRES-4)

16 May 7 Project implementation (demos) due (P4 - May 7)Paper due (PPR - May 14)