1 / 22

CS 790z Seminar on Software Engineering

CS 790z Seminar on Software Engineering. Fall 2010 Course Syllabus (tentative) August 23, 2010. Outline. The Instructor The Students The Course The Texts & Initial WWW Pointers Grading Scheme & Scale Policies Summary of Course Objectives A Look Ahead. The Instructor. Sergiu Dascalu

kennedy-wilcox
Télécharger la présentation

CS 790z Seminar on Software Engineering

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. CS 790zSeminar on Software Engineering Fall 2010 Course Syllabus (tentative) August 23, 2010

  2. Outline • The Instructor • The Students • The Course • The Texts & Initial WWW Pointers • Grading Scheme & Scale • Policies • Summary of Course Objectives • A Look Ahead

  3. The Instructor. • Sergiu Dascalu • Room SEM-236 • Telephone 784-4613 • E-mail dascalus@cse.unr.edu • Web-sitewww.cse.unr.edu/~dascalus • Office hours: • T 3:30 - 4:30 pm; W 5:30 – 6:30 pm or by appointment or chance

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

  5. The Students Registered as of today: 18 students Prerequisite: CS 425 Software Engineering or Instructor’s approval

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

  7. .The Course • Outline [continued]: The course will enable the students to broaden their knowledge of software architecture and software engineering concepts, principles, techniques, and tools, study relevant research publications in the field, develop a high quality software project and, based on this project, write a paper that could be submitted to a scientific conference.

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

  9. .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 IlaNeustadt, UML and the Unified Process: PracticalObject-Oriented Analysis and Design, 2nd Ed., Addison Wesley, 2005. • Lecture notes: • Presentations by the instructor • Notes you take in the classroom • Additional material (papers, tutorials, etc.) that will be indicated later by the instructor

  10. Initial WWW Pointers • IEEE’s Digital Library, via www.ieee.org • ACM Digital Library, viawww.acm.org • The Software Engineering Institute, at Carnegie Mellon University, www.sei.cmu.edu • The Object Management Group, www.omg.org • IBM/Rational Software, www.rational.com • More will be indicated later

  11. Grading Scheme. • 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%

  12. .Grading Scheme • Passing conditions (all must be met): • 50% overall & • 50% in test & • 50% in project and paper & • 50% in assignments, presentations, and class participation • For grade A: at least 90% overall, at least 90% in class participation and at least 60% in test • Note that there are no make-up tests or homework in this course

  13. Grading Scale • Numerical-letter grade correspondence • A 90 -100 • A- 87 - 89 • B+ 84 - 86 • B 79 - 83 • B- 75 - 78 • C+ 72 - 74 • C 68 - 71 • C- 65 - 67 • D+ 61 - 64 • D 56 - 60 • D- 50 - 55 • F < 50

  14. Policies.. • 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)

  15. .Policies. • Legal notices on the world-wide web: Read and comply with accompanying legal notices of downloadable material • Specify references used • 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. Summary of Course Objectives • Course objectives: • Extension of SE knowledge, in particular of software architecture concepts, principles, methods, and tools • Study and presentation of relevant research publications • Development of a high quality software project • Writing a paper that can be submitted to a scientific conference

  18. A Look Ahead. • My intentions & expectations: • Provide guidance in the SE spectrum; widen perspectives on SE research • Help you be better prepared for research and development in SE • Guide you in writing an SE research paper • Hope that you will both work hard and enjoy your work in this course

  19. .A Look Ahead • Your intentions & expectations: • Why do you take the course? • In what ways do you think this course could help your professional development? • What is your experience so far with SE? • What topics are you interested in? • What suggestions do you have for the instructor?

  20. Tentative schedule.

  21. .Tentative schedule

  22. Next class • Students’ introduction: be prepared to talk 2-3 minutes about yourself; you are encouraged to have few slides prepared. • More on the need for software engineering & short videos with well-known SE researchers and practitioners

More Related