Transcript PPT - University of Victoria

SENG130
Engineering Software Systems
Introduction
Rev. 2.1
©2007
Scott Miller, University of Victoria.
1
4/8/2016
Administrivia





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:301:30
or by appointment
E-mail: [email protected]
* I check e-mail regularly
©2007
Scott Miller, University of Victoria.
2
4/8/2016
Administrivia

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.
©2007
Scott Miller, University of Victoria.
3
4/8/2016
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:

–
–
–
–
©2007
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
Scott Miller, University of Victoria.
4
4/8/2016
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
©2007
Scott Miller, University of Victoria.
5
4/8/2016
Introduction to Software
Engineering
Application of engineering principals to software design…
Lead Time
Reliability
Interoperability
Cost Effectiveness
Specifications
Maintainability
©2007
Scott Miller, University of Victoria.
Testing
6
4/8/2016
Introduction to Software
Engineering
©2007
Scott Miller, University of Victoria.
7
4/8/2016
Introduction to Software
Engineering
Software Engineering Vs. Computer Science
Apply “well known”
Hypothesize
theories, math, etc.
Work on systems
Experimentation
(modularity)
Code for maintenance
Observation
Code for others’ use (S.
Engineer not end user)
©2007
Scott Miller, University of Victoria.
Conclusions
8
4/8/2016
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
©2007
Scott Miller, University of Victoria.
9
4/8/2016
System Development Model
Specifications Document
Requirements
Design Document
Design
Business
Analyst
• UML Descriptor
• Class Hierarchy
• Interfaces
Debugged Object Code
Implementation
Senior S.Eng
Software Architect
Software Engineers
QA Engineers
Integration Complete version
of
& Testing
software
Maintenance
Tester
©2007
Scott Miller, University of Victoria.
10
4/8/2016
Software Development Models
©2007
•
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
Scott Miller, University of Victoria.
11
4/8/2016
Software Development Models:
– Waterfall Model [1]
©2007
Scott Miller, University of Victoria.
12
4/8/2016
Software Development Models:
- Spiral Model [2]
©2007
Scott Miller, University of Victoria.
13
4/8/2016
Reading for Next Class

Good idea to start familiarizing self with
with NetBeans, UNIX, Java.

NEXT CLASS: SYSTEMS
©2007
Scott Miller, University of Victoria.
14
4/8/2016