10/20/2015 ©2007 Scott Miller, University of Victoria. 1 SENG130 Engineering Software Systems Introduction Rev. 2.1

10/20/2015 ©2007 Scott Miller, University of Victoria. 2 Administrivia Instructor:Scott Miller Office:ECS 609 Phone #: Lab (Where I am most of the time): ELW B325 Phone #: Office Hours:T 2:30pm-3:30pm, W 12:30- 1:30 or by appointment * I check regularly

10/20/2015 ©2007 Scott Miller, University of Victoria. 3 Administrivia Course website: –All relevant announcements, materials and official information will be listed on this page –Check regularly for news, TUTORIALS, marks –Schedule listed will be followed. This includes required readings.

GROUPS! You may not like them, but you have to deal with them in the real world. … and this course You have been placed in groups of 5 with: –1 x 4 th year students – project manager –1 x 3 rd year students – senior engineer –1 x 2 nd year students – java and JSP –1 or 2 x 1 st year students – java and JSP 10/20/2015 ©2007 Scott Miller, University of Victoria. 4

Goals of SENG130 Upon completion you will be able to: –Understand basic networking and Web protocols –Learn how to work in hierarchical groups –Learn Java, JSP, SQL –Design and build web applications 10/20/2015 ©2007 Scott Miller, University of Victoria. 5

10/20/2015 ©2007 Scott Miller, University of Victoria. 6 Introduction to Software Engineering Application of engineering principals to software design… Reliability Cost Effectiveness Maintainability Lead Time Interoperability Specifications Testing

10/20/2015 ©2007 Scott Miller, University of Victoria. 7 Introduction to Software Engineering

10/20/2015 ©2007 Scott Miller, University of Victoria. 8 Introduction to Software Engineering Vs. Software EngineeringComputer Science Apply “well known” theories, math, etc. Hypothesize Work on systems (modularity) Experimentation Code for maintenanceObservation Code for others’ use (S. Engineer not end user) Conclusions

10/20/2015 ©2007 Scott Miller, University of Victoria. 9 Software Engineering Code of Ethics Customers using your software should NOT be at risk. –Know what you don’t: do not take on work beyond your level of knowledge or expertise –Program with the knowledge that someday others will need to maintain the system

10/20/2015 ©2007 Scott Miller, University of Victoria. 10 System Development Model Requirements Design Implementation Integration & Testing Maintenance Business Analyst Senior S.Eng Software Architect Software Engineers QA Engineers Tester Specifications Document Design Document UML Descriptor Class Hierarchy Interfaces Debugged Object Code Complete version of software

10/20/2015 ©2007 Scott Miller, University of Victoria. 11 Software Development Models Methods of System Development Lifecycle 1.Build-and-Fix 2.Waterfall model 3.Spiral Model 4.Rapid Prototyping model Considerations for Software Interfacing 1.Hardware Design 2.Maintenance 3.TESTING

10/20/2015 ©2007 Scott Miller, University of Victoria. 12 Software Development Models: – Waterfall Model [1]

10/20/2015 ©2007 Scott Miller, University of Victoria. 13 Software Development Models: - Spiral Model [2]

10/20/2015 ©2007 Scott Miller, University of Victoria. 14 Reading for Next Class Good idea to start familiarizing self with with NetBeans, UNIX, Java. NEXT CLASS: SYSTEMS