1. September 6, 2016CS410 – Software Engineering Lecture #1: Introduction 1 Welcome to CS 410 – Introduction to Software Engineering Fall 2016 Instructor: Marc Pomplun Instructor: Marc Pomplun

2. September 6, 2016CS410 – Software Engineering Lecture #1: Introduction 2 Main Instructor – Marc Pomplun Office:S-3-171 Lab:S-3-135 Office Hours: Tuesdays and Thursdays 3:15 – 4:00pm and 5:15 – 6:00pm Phone: 287-6443 (office) E-Mail: marc@cs.umb.edu Website: http://www.cs.umb.edu/~marc/cs410/

3. September 6, 2016CS410 – Software Engineering Lecture #1: Introduction 3 Additional Instructors Lere Williams Co-founder, Engineering at Beanstock, Nigeria (https://www.beanstock.ag/) https://www.beanstock.ag/ Nam Chu Hoai Fullstack Developer, Wellframe, Germany (https://www.wellframe.com/) https://www.wellframe.com/ Srinath Vaddepally Chief Executive Officer, RistCall, India (http://www.ristcall.com/) http://www.ristcall.com/

4. September 6, 2016CS410 – Software Engineering Lecture #1: Introduction 4 The Visual Attention Lab Eye movement research

5. September 6, 2016CS410 – Software Engineering Lecture #1: Introduction 5 The new EyeLink-2K System

6. September 6, 2016CS410 – Software Engineering Lecture #1: Introduction 6 Example: Distribution of Visual Attention

7. September 6, 2016CS410 – Software Engineering Lecture #1: Introduction 7 Selectivity in Complex Scenes

8. September 6, 2016CS410 – Software Engineering Lecture #1: Introduction 8 Selectivity in Complex Scenes

9. September 6, 2016CS410 – Software Engineering Lecture #1: Introduction 9 Selectivity in Complex Scenes

10. September 6, 2016CS410 – Software Engineering Lecture #1: Introduction 10 Selectivity in Complex Scenes

11. September 6, 2016CS410 – Software Engineering Lecture #1: Introduction 11 Selectivity in Complex Scenes

12. September 6, 2016CS410 – Software Engineering Lecture #1: Introduction 12 Selectivity in Complex Scenes

13. September 6, 2016CS410 – Software Engineering Lecture #1: Introduction 13 Modeling of Brain Functions

14. September 6, 2016CS410 – Software Engineering Lecture #1: Introduction 14 Modeling of Brain Functions unit and connection in the interpretive network unit and connection in the gating network unit and connection in the top-down bias network layer l +1 layer l -1 layer l

15. September 6, 2016CS410 – Software Engineering Lecture #1: Introduction 15 Computer Vision:

16. September 6, 2016CS410 – Software Engineering Lecture #1: Introduction 16 Human-Computer Interfaces:

17. September 6, 2016CS410 – Software Engineering Lecture #1: Introduction 17 Now back to CS 410: Textbook (available at the UMB Bookstore): C++ programming with design patterns revealed. By Thomasz Müldner. Addison-Wesley, ISBN 0-201-72231-3 Course materials on the Web: http://www.cs.umb.edu/~marc/cs410/ (contains all kinds of course information and also my slides in PPT and PDF formats, updated after each session)

18. September 6, 2016CS410 – Software Engineering Lecture #1: Introduction 18 Mailing List Please use the ‘apply’ command on the UNIX system to register for our mailing list (CS410, section 1). I expect everyone to be on the list, because I will use it to make announcements. Also, I would like to encourage you to use the list for discussion. If you have a question that you think is important for many students in the course, please send it to the list at cs410-1@cs.umb.edu, cs410-1@cs.umb.edu and I will respond to the list. Send all other questions to me. For these questions, I will send my reply only to you. me

19. September 6, 2016CS410 – Software Engineering Lecture #1: Introduction 19 Your Evaluation 3 sets of exercises each set 3.33% 10% (only individual submissions allowed)3 sets of exercises each set 3.33% 10% (only individual submissions allowed) software project 40% (groups of 3 or 4 students)software project 40% (groups of 3 or 4 students) midterm (1.5 hours) 20%midterm (1.5 hours) 20% final exam (2.5 hours) 30%final exam (2.5 hours) 30%

20. September 6, 2016CS410 – Software Engineering Lecture #1: Introduction 20 Grading  95%: A  90%: A-  74%: C+  70%: C  66%: C-  86%: B+  82%: B  78%: B-  62%: D+  56%: D  50%: D-  50%: F For the assignments, exams and your course grade, the following scheme will be used to convert percentages into letter grades:

21. September 6, 2016CS410 – Software Engineering Lecture #1: Introduction 21 Complaints about Grading If you think that the grading of your assignment or exam was unfair, write down your complaint (handwriting is OK), write down your complaint (handwriting is OK), attach it to the assignment or exam, attach it to the assignment or exam, and give it to me or put it in my mailbox. and give it to me or put it in my mailbox. I will re-grade the whole exam/assignment and return it to you in class.

22. September 6, 2016CS410 – Software Engineering Lecture #1: Introduction 22 Software Engineering 1968: Conference on ‘software crisis’.1968: Conference on ‘software crisis’. Delivery of software was sometimes years late.Delivery of software was sometimes years late. Its cost was often much higher than predicted.Its cost was often much higher than predicted. Many programs were unreliable.Many programs were unreliable. Maintenance of software tended to be difficult.Maintenance of software tended to be difficult. The software often poorly performed the task for which it was designed.The software often poorly performed the task for which it was designed.  The term ‘software engineering’ was coined.

23. September 6, 2016CS410 – Software Engineering Lecture #1: Introduction 23 Questions about Software Engineering Q: What is software engineering? A: Software engineering is an engineering discipline which is concerned with all aspects of software production, for example, software specification, development, validation and evolution. Q: What is the difference between software engineering and computer science? A: Computer science is concerned with theory and fundamentals; software engineering is concerned with the practicalities of developing and delivering useful software.

24. September 6, 2016CS410 – Software Engineering Lecture #1: Introduction 24 Problems: Complexity and Change Complexity: Software systems can include a huge number of functions and components.Software systems can include a huge number of functions and components. Many participants with usually different backgrounds participate in the development of software systems.Many participants with usually different backgrounds participate in the development of software systems. Often no single person can understand the whole system.Often no single person can understand the whole system. Sometimes systems become so hard to understand that they are never finished: ‘vaporware’.Sometimes systems become so hard to understand that they are never finished: ‘vaporware’.

25. September 6, 2016CS410 – Software Engineering Lecture #1: Introduction 25 Problems: Complexity and Change Change: Requirements are updated when errors are discovered and when developers get a better understanding of the application.Requirements are updated when errors are discovered and when developers get a better understanding of the application. Long-term projects involve high staff-turnaround.Long-term projects involve high staff-turnaround. Often, important technological changes occur during the development of a software system.Often, important technological changes occur during the development of a software system. The client’s needs may change during the development process.The client’s needs may change during the development process.  It is impossible to specify a static set of requirements.