1. -1- CSCI3100 Software Engineering Course Policies and Procedures (class syllabus) Professor Michael Rung-Tsong LYU 呂榮聰 January 11, 2016

2. -2- STUDENT EXPECTATIONS 1.a positive, respectful, and engaged academic environment inside and outside the classroom; 2.to attend classes at regularly scheduled times without undue variations, and to receive before term-end adequate make-ups of classes that are canceled due to leave of absence of the instructor; 3.to receive a course syllabus 4.to consult with the instructor and tutors through regularly scheduled office hours or a mutually convenient appointment;

3. -3- STUDENT EXPECTATIONS 5.to have reasonable access to University facilities and equipment for assignments and/or objectives; 6.to have access to guidelines on University’s definition of academic misconduct; 7.to have reasonable access to grading instruments and/or grading criteria for individual assignments, projects, or exams and to review graded material; 8.to consult with each course’s faculty member regarding the petition process for graded coursework.

4. -4- FACULTY EXPECTATIONS 1.a positive, respectful, and engaged academic environment inside and outside the classroom; 2.students to appear for class meetings timely; 3.to select qualified course tutors; 4.students to appear at office hours or a mutual appointment for official academic matters; 5.full attendance at examination, midterms, presentations, and laboratories;

5. -5- FACULTY EXPECTATIONS 6.students to be prepared for class, appearing with appropriate materials and having completed assigned readings and homework; 7.full engagement within the classroom, including focus during lectures, appropriate and relevant questions, and class participation; 8.to cancel class due to emergency situations and to cover missed material during subsequent classes; 9.students to act with integrity and honesty.

6. -6- Course Objective Teach the principles of software engineering in the context of contemporary specification, design, coding, testing, evaluation, and maintenance methodologies. Practice software engineering life-cycle with a real- world project which involves current design and development techniques. Introduce modern software system development techniques including software-intensive applications, mobile access adaptation, Web services, software tools, and agile development.

7. -7- Course Description Details include: –software requirement engineering, –specification techniques, –structured design, –structured programming, –top-down design and development, –segmentation and modularization techniques, –information hiding, –iterative enhancement, –design and code inspection techniques, –correctness, –the software life cycle methodology, –extreme programming, –software management, –software validation and verification techniques, –software metrics, –software reliability measurement, –data collection and analysis. This course will focus on state of the art techniques in software design, development, measurement and evaluation. Laboratory experience in applying these techniques will be covered in the development of a modern Web-based mobile software project.

8. -8- Major Topics Motivation – why Software Engineering instead of ad hoc techniques? General terminology; Introduction to process models Software quality concepts Requirements engineering and analysis Specification techniques Specification languages Design principles Design techniques (Object-Oriented Design, UML) Implementation issues Unit test issues and tools System integration testing techniques and tools Modern support tools and automated systems (git) Basic principles of Quality Assurance, risk reduction, Configuration Management. Quantitative measurement and metrics Software reliability modeling and measurements Distributed computing (Web Services, Cloud Computing) HTML5 & Java technologies Mobile apps and tools (e.g., Bootstrap) Android programming Extreme Programming & Agile Programming

9. -9- References Major reference book: Fundamentals of Software Engineering, Ghezzi, Jazayeri, and Mandrioli, Prentice Hall, 2 nd Edition, 2003. Note: 1-2 copies are reserved in the main library Other references include –Software Engineering: A Practitioner’s Approach, Pressman, McGraw-Hill, 8 th Edition, 2014. –Software Engineering, Sommerville, Pearson/Addison Wesley, 9 th Edition, 2011. –Code Complete: A Practical Handbook of Software Construction, Steve McConnell, 2 nd Edition, 2004 (24 th printing in 2015) –Handbook of Software Reliability Engineering, Lyu (ed.), McGraw-Hill, 1996. –Other papers, articles, news (check course website periodically for technology innovation scan articles and presentations)

10. -10- Teaching Staff Lecturer – Prof. Michael R. LYU, Office: Rm 927, E-mail: lyu, Phone: 39438429 Office Hour: Monday at 11:30-12:30, Wednesday at 11:00-12:00 TA – Ms. GAO Cuiyun, Office: Rm 101, E-mail: cygao, Phone: 39434257 TA – Mr. LI Jian, Office: Rm 101, E-mail: jianli, Phone: 39434257 TA – Mr. HE Pinjia, Office: Rm 101, E-mail: pjhe,Phone: 39434257 TA – Mr. ZENG Jichuan, Office: Rm 101, E-mail: jczeng, Phone: 39434257 TA – Mr. SU Yuxin, Office: Rm 101, E-mail: yxsu, Phone: 39434257 TA – Mr. ZHU Fengyuan, Office: Rm 903, E-mail: fyzhu,Phone: 26098411 TA – Ms. ZHENG Qingqing, Office: Rm 903, E-mail: qqzheng, Phone: 26098411 TA – Mr. CHEN Guangyong, Office: Rm 903, E-mail: gychen, Phone: 26098411

11. -11- Teaching Schedule Course account : csci3100 (http://course.cse.cuhk.edu.hk/~csci3100)http://course.cse.cuhk.edu.hk/~csci3100 (https://wiki.cse.cuhk.edu.hk/user/csci3100)https://wiki.cse.cuhk.edu.hk/user/csci3100 Tutor Group mail : csci3100@cse.cuhk.edu.hk Schedule Lecture: Monday 10:30am-11:15am (LSB LT1) Tuesday 10:30am-12:15pm (LSK LT7) Large Tutorial (TU): Monday 5:30pm-6:15pm(ERB 407) 74 students Wednesday 5:30pm-6:15pm(LSB LT6)140 students Small Tutorial (HW): T01: M5:30-6:15 (ERB 407)25 students (25 max.) T03: M5:30-6:15 (LSB C3),, T04: M5:30-6:15 (LSB C4),, T02: W5:30-6:15 (LSB LT6)28 students (30 max.) T05: W5:30-6:15 (LSB C3),, T06: W5:30-6:15 (LSB C4),, T07: W5:30-6:15 (LSB C5),, T08: W5:30-6:15 (LSB G34),,

12. -12- Tutorial Schedule WeekDate TypeTopicsWork 1Jan-11Jan-13N.A.Tutorial policies, schedule, and session assignment (on Web)Read the procedure. No tutorial this week. 2Jan-18Jan-20LTU1: CSCI3100 Project introduction, requirement and demonstrationProject assigned HW1 assigned 3Jan-25Jan-27LTU2: Client Side Development 1: HTML5 4Feb-1Feb-3SHW1 demo (Lecture Topic 1-3)HW2 assigned 6Feb-15Feb-17SHW2 demo (Topic 4 Software Spec – Data Flow Diagram, FSM)HW3 assigned 7Feb-22Feb-24LTU3: Client Side Development 2: JavascriptDesign Report 8Feb-29Mar-2SHW3 demo (Topic 4 Software Spec – Petri Net) 9Mar-7Mar-9LTU4: Server Side Development: Node.jsMidterm Exam HW4 assigned 10Mar-14Mar-16LTU5: Mobile Adaption: Bootstrap (+ midterm inspection) 11Mar-21Mar-23SHW4: demo (Topic 5 Software Design – TDN, GDN, Refinement)Initial Code 3/29 HW5 assigned 14Apr-11Apr-13SHW5 demo (Topic 5 Software Design – UML, programming technique)Project Demo 15Apr-18Apr-20LTU6: Agile Development Process and TechniqueHW6 assigned Note: L – 2 Large tutorial sessions; S – 8 small tutorial sessions

13. -13- Course Marking Structure Homework Homework will be assigned 6 times in this term, with about 4 questions in each assignment. The Mid-term Exam There will be a closed-book, “open 1-A4-page written-only, no-photocopy note” mid-term exam on 8 March (Tuesday) at 10:30am-12:15pm. The mid-term exam venues and details will be announced later. The Final Exam There will be one comprehensive final exam according to the final exam schedule. The final exam is open-book, open-note, photo-copying allowed. It will be a 3-hour exam. Final Course Grade Weightings Your final grade will be determined by applying a curve which looks for natural breakpoints. This policy recognizes the fact that it is difficult to write exams for which the class will provide a predictable and well-behaved mean and variance. Your raw percentage for the course will be calculated based on the following weights: –Homework: 15% –Mid-term Exam: 20% 8 March, 2016 (Tuesday) 10:30am-12:15pm –Project: 30% –Final Exam: 35%

14. -14- “The CSCI 3100 Project” Laboratory of a phased-project will be assigned and conducted according to the schedule in the appended Table. Deliverables of each phase will be graded by the instructor and the tutors. A missing deliverable will receive a score of 0 for that phase assignment. Late submission of a deliverable will be marked and subject to 20% grade reduction per day as penalty. A complete package for the project assignment could be picked up through the course website when the project kicks off on 18 January 2016 (next Monday). You may use any computing facility of your convenience to develop the software for the project, but it has to be compatible to the compiler in the CSE department’s computing facility, where you would turn in your program for demo. “Demo Day” of your project will be individually signed-up on 14 April 2016 (Thursday). Note: Laboratory project assignments are to be worked within the team boundary (4-5 members in a team). Form a team yourselves and sign up to the Group Registration Link before 15 January 2016, the coming Friday, regarding who are the members of your team. Teams for the rest students will be assigned by the instructor and the tutors randomly after the deadline. The teams will be announced on course website before 18 January 2016.

15. -15- Project Schedule and Weightings Phase DeliverablesWeightingsDurationsDue Date 0. Project Assignment-- 18 Jan (on Web) 1. Project Design Document10%5 weeks24 Feb (midnight) 2. Initial Code5%4 weeks23 Mar (midnight) 3. Final Code and Demo60%3 weeks14 Apr (full day) 4. Final Report and Commented Code 25%3 weeks6 May (midnight) Total100%15 weeks Note: Project grouping registration and tutorial session assignment system is available today by noon through Group Registration Link on course website. Sign up before Friday if you can form a team.