04/20/23©2007 Scott Miller, University of Victoria.1

SENG130SENG130Engineering Software Systems

Introduction

Rev. 2.1

04/20/23©2007 Scott Miller, University of Victoria.2

AdministriviaAdministrivia

Instructor: Scott Miller Office: ECS 609

Phone #: 472-5714 Lab (Where I am most of the time): ELW B325

Phone #: 721-8773 Office Hours: T 2:30pm-3:30pm, W 12:30-

1:30or by appointment

E-mail: smiller@csc.uvic.ca* I check e-mail regularly

04/20/23©2007 Scott Miller, University of Victoria.3

AdministriviaAdministrivia

Course website:http://www.engr.uvic.ca/~seng130/– 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!GROUPS!

You may not like them, but you have to deal with them in the real world.

… and this courseYou have been placed in groups of 5 with:

– 1 x 4th year students – project manager– 1 x 3rd year students – senior engineer– 1 x 2nd year students – java and JSP– 1 or 2 x 1st year students – java and JSP

04/20/23©2007 Scott Miller, University of Victoria.4

Goals of SENG130Goals 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

04/20/23©2007 Scott Miller, University of Victoria.5

04/20/23©2007 Scott Miller, University of Victoria.6

Introduction to Software Introduction to Software EngineeringEngineering

Application of engineering principals to software design…

Reliability

Cost Effectiveness

Maintainability

Lead Time

Interoperability

SpecificationsTesting

04/20/23©2007 Scott Miller, University of Victoria.7

Introduction to Software Introduction to Software EngineeringEngineering

04/20/23©2007 Scott Miller, University of Victoria.8

Introduction to Software Introduction to Software EngineeringEngineering

Vs.Software Engineering Computer ScienceApply “well known” theories, math, etc.

Hypothesize

Work on systems (modularity)

Experimentation

Code for maintenance Observation

Code for others’ use (S. Engineer not end user)

Conclusions

04/20/23©2007 Scott Miller, University of Victoria.9

Software Engineering Code of Software Engineering Code of EthicsEthics

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

04/20/23©2007 Scott Miller, University of Victoria.10

System Development ModelSystem Development Model

Requirements

Design

Implementation

Integration& Testing

Maintenance

BusinessAnalyst

Senior S.EngSoftware Architect

Software Engineers

QA Engineers

Tester

Specifications Document

Design Document

• UML Descriptor• Class Hierarchy• Interfaces

Debugged Object Code

Complete version of software

04/20/23©2007 Scott Miller, University of Victoria.11

Software Development ModelsSoftware Development Models

• Methods of System Development Lifecycle1. Build-and-Fix2. Waterfall model3. Spiral Model4. Rapid Prototyping model

• Considerations for Software Interfacing1. Hardware Design2. Maintenance3. TESTING

04/20/23©2007 Scott Miller, University of Victoria.12

Software Development Models: Software Development Models: – Waterfall Model [1]– Waterfall Model [1]

04/20/23©2007 Scott Miller, University of Victoria.13

Software Development Models:Software Development Models:- Spiral Model [2]- Spiral Model [2]

04/20/23©2007 Scott Miller, University of Victoria.14

Reading for Next ClassReading for Next Class

Good idea to start familiarizing self with with NetBeans, UNIX, Java.

NEXT CLASS: SYSTEMS