11

CS 790zCS 790zSeminar on Software Seminar on Software

EngineeringEngineering

Fall 2010Fall 2010Course Syllabus (tentative)Course Syllabus (tentative)

August 23, 2010August 23, 2010

22

Outline The InstructorThe Instructor The StudentsThe Students The CourseThe Course The Texts & Initial WWW PointersThe Texts & Initial WWW Pointers Grading Scheme & ScaleGrading Scheme & 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 3:30 - 4:30 pm; W 5:30 – 6:30 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 Teaching and research at the University Politehnica of

Bucharest, Romania, 1984-1993 Consultant for software development companies in

Canada and Romania

55

The Students

Registered as of today:18 students

Prerequisite: CS 425 Software Engineering or Instructor’s approval

66

The Course.The Course. Classroom: Classroom:

CB-111, MW 4:00 - 5:15 pmCB-111, MW 4:00 - 5:15 pm

Outline: This course explores research and development This course explores research and development topics in software engineering, with emphasis on topics in software engineering, with emphasis on software architecture. The research and study focus will software architecture. The research and study focus will be on concepts, principles, methods, and tools pertaining be on concepts, principles, methods, and tools pertaining to architecting software systems. Examples include, but to architecting software systems. Examples include, but are not limited to, architectural styles, specifying are not limited to, architectural styles, specifying requirements, design principles, modeling languages requirements, design principles, modeling languages and architectural descriptions, software architecture and architectural descriptions, software architecture quality, documenting software architecture, architecting quality, documenting software architecture, architecting complex systems, and the role of architects. complex systems, and the role of architects.

77

.The Course.The Course

Outline [continued]:

The course will enable the students The course will enable the students to broaden to broaden their their knowledgeknowledge of software architecture and software of software architecture and software engineering concepts, principles, techniques, and tools, engineering concepts, principles, techniques, and tools, study relevant research publicationsstudy relevant research publications in the field, in the field, develop develop a high quality software projecta high quality software project and, based on this and, based on this project, project, write a paper write a paper that could be submitted to a that could be submitted to a scientific conference. scientific conference.

88

The Texts.The Texts.

Required textbook [to be confirmed!]: Taylor, R.N., Medvidovic, N., and Dashofy, E.M.,

Software Architecture: Foundations, Theory, and Practice, Wiley, 2009. ISBN: 978-0470167748

99

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

Peter Eeles and Peter Peter Cripps, The Process of Software Architecting, Addison-Wesley, 2010. ISBN: 0-321-35748-5.

Ian Sommerville, Software Engineering, 9th Ed., Addison-Wesley, 2010.

Jim Arlow and Ila Neustadt, Jim Arlow and Ila Neustadt, UML and the Unified Process: PracticalUML and the Unified Process: Practical Object-Oriented Analysis and DesignObject-Oriented Analysis and Design, 2, 2ndnd Ed., Addison Wesley, 2005. Ed., Addison Wesley, 2005.

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

Additional material Additional material (papers, tutorials, etc.) that will be (papers, tutorials, etc.) that will be indicated later by the instructorindicated later 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 The Object Management Group, www.omg.orgThe Object Management Group, www.omg.org IBM/Rational Software, www.rational.com IBM/Rational Software, www.rational.com More will be indicated laterMore will be indicated later

1111

Grading Scheme.Grading Scheme.

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

Assignments: A 1, 2, 3 15% Presentations: PRES 1, 2, 3 10% Midterm test: TEST 25% Project: P 1, 2, 3, 4 30% Paper:DRAFT, PAPER 15% Class participation: PART* 5% [* assumes very good presence; a large number of absences will affect the grade

much more significantly]

TOTAL 100%

1212

.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

1313

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

1414

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)

1515

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

1616

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

1717

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

architecture concepts, principles, methods, and tools architecture concepts, principles, methods, and tools 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

1818

A Look Ahead.A Look Ahead.

My intentions & expectations:My intentions & expectations: Provide guidance in the SE spectrum; widen Provide guidance in the SE spectrum; widen

perspectives on SE research perspectives on SE research 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

1919

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

2020

Tentative schedule.Tentative schedule.Week Class Dates Contents

1 Aug 23, 25Course syllabusStudents’ introduction

2 Aug 30, Sep 1Lectures by the instructor, A#1 givenDraw for presentations’ order

3 -, Sep 08Lecture by the instructor, A#2 given Project teams set up (Sep 10)A#1 due

4 Sep 13, 15 Individual project meetings with the instructor

5 Sep 20, 22Lectures by the instructor, P#1 given, PRES#1 guidelines A#2 due

6 Sep 27, 29Presentations by students (PRES#1), P#2 given Project concept due (P#1)

7 Oct 04, 06 Presentations by students (PRES#1)

2121

.Tentative schedule.Tentative schedule

Week Class Dates Contents

8 Oct 11, 13 Lectures by the instructor, P#3 givenProject specification due (P#2)

9 Oct 18, 20 Presentations by students (PRES#1), Paper DRAFT given

10 Oct 25, 27 Lectures by the instructor, P#4 givenProject design due (P#3)

11 Nov 01, 03 Lectures by the instructor, A#3/PRES 2 guidelines Paper DRAFT due

12 Nov 08, 10 Lecture by the instructor, PAPER given Midterm exam (TEST - Nov 10)

13 Nov 15, 17 Presentations by students - additional readings (PRES#2)

14 Nov 22, 24 Presentations by students - additional readings (PRES#2)

15 Nov 29, Dec 1 Presentations by students - project (PRES#3)

16 Dec 06, - Project implementation (demos) due (P#4 - Dec 08 & 09)Paper due (PAPER - Dec 14)

2222

Next classNext class

Students’ introduction: be prepared to talk 2-3 Students’ introduction: be prepared to talk 2-3 minutes about yourself; you are encouraged to minutes about yourself; you are encouraged to have few slides prepared. have few slides prepared.

More on the need for software engineering & More on the need for software engineering & short videos with well-known SE researchers short videos with well-known SE researchers and practitionersand practitioners