Software Engineering CS3003 Lecture 1 Introduction to the module Dr Tracy Hall

2 Structure of this lecture The module team Overview of the module  Learning outcomes, Assessment, Course texts, Programme of study Introduction to Software Engineering Reading for the week

3 Module team Module Leader: Dr Tracy Hall   Always your queries first to Tracy Module Lecturer: Professor Rob Hierons 

4 More about Tracy Hall… Reader in Software Engineering Joined Brunel in 2007 Been a university lecturer in SE for the last 23 years Research in:  Fault prediction  Software development processes and methods  Human factors related to software engineers  Software code quality Published nearly 100 academic papers Many funded research grants Many successful PhD students On editorial board of two software engineering journals Senior Tutor in the Department

Our expectations… 5

Behaviour Our valuesStudents demonstrate this by: Respect: we treat each other with respect and courtesy.Preparing for labs and lectures Arriving on time Reflecting on feedback Being courteous to all students and staff Responsibility: we take our responsibilities seriously, are accountable for our actions. Taking charge of their education Studying hard Taking the initiative Meeting deadlines Being motivated to learn Attending all classes and activities Transparency: we set out what we will do and what we expect clearly and simply and communicate it in a timely way. We act fairly and honestly with each other. Being realistic and honest about work, progress and expectations Maintaining regular contact with their group and/or project tutor Being proactive in seeking support and advice Telling the Department as soon as possible if they have any difficulties Community: we care for and offer support and help to each other. We support and encourage each other to learn and reach our goals. Contributing in classes and other activities to the best of their ability Provide constructive feedback on teaching, programmes, the Department, and the University Being willing to support and be supported by peers Pulling their weight in team activities

Behaviour Our valuesStaff demonstrate this by: Respect: we treat each other with respect and courtesy. Preparing well for all teaching activities Arriving on time Listening to and acting on student feedback Being courteous to all students and staff Responsibility: we take our responsibilities seriously, are accountable for our actions. Providing a positive teaching and learning experience Inspiring and challenging their students Supporting student learning Offering academic and pastoral support Concentrating feedback on how their students’ can improve Transparency: we set out what we will do and what we expect clearly and simply and communicate it in a timely way. We act fairly and honestly with each other. Promoting honest dialogue around effort, achievement and expectations Publishing assessment details and submission dates at the start of each term Providing feedback on their students’ work by agreed dates Replying to within three working days Community: we care for and offer support and help to each other. We support and encourage each other to learn and reach our goals. Being available at published times to offer support and guidance Providing services and advice to help their students to find work Valuing student-staff activities, and learning from them Providing opportunities for their students’ personal and professional development outside core study

The module last year… Achievements last year:  5 fails  Lots of D’s  Lots of A’s Good students did really well 8

The module this year… More practical sessions for course work Continue to be supported in workshops only by lecturing staff Introduce a regular student feedback mechanism  Feedback this week via: 9

10 Overview of the module Learning outcomes, Assessment, Course texts, Programme of study  Study Guide…

11 Workshops… Timetabled on Tuesday afternoons Focused on using:  Netbeans  GIT  PMD

12 Introduction to Software Engineering (Based on Ch1, Sommerville, ed 8) More and more systems are software controlled Software engineering is concerned with theories, methods and tools for professional software development Software engineering expenditure represents a significant fraction of GNP in all developed countries

Software costs Software costs often dominate system costs. Software costs more to maintain than it does to develop. Roughly 60% of costs are development costs, 40% are testing costs. Costs vary depending on the type of system being developed Distribution of costs depends on the development model that is used 13

What is software engineering? Software engineering is an engineering discipline which is concerned with all aspects of software production Software engineers should adopt a systematic and organised approach to their work and use appropriate tools and techniques depending on the problem to be solved, the development constraints and the resources available 14

What are software engineering methods? Structured approaches to software development which include:  Model descriptions Descriptions of graphical models which should be produced  Rules Constraints applied to system models  Recommendations Advice on good design practice  Process guidance What activities to follow 15

Software Engineering… 16 Software functionality Software attributes Tools, techniques, methods, etc. Process and people

Software development lifecycle emotions… 17 Mail2wisdom.com

18 Reading for the week Sommerville Chapter 1