Lawrence Bernstein and

1
Software Engineering
Lawrence Bernstein and David Klappholz Stevens
Institute of Technology Catherine Kelley
Fairleigh-Dickinson University
2
NJCSE Affiliates

• ATT
• AVAYA
• IBM
• OMSOFT-(will pay once profitable)
• Rational
• Telcordia

3
2001 Software Engineering Exchanges

• Fiour Colloquia by world-class software
  engineers
• David Korn
• Naftaly Minsky
• Dennis Ritchie
• Bjourne Stroustrop
• Ten e-mail newsletters
• UCITA alarm
• Windows Security
• etc.

4
Participating Organizations

• ATT
• AVAYA
• Business Edge
• Crescent
• Lucent
• Monmouth University
• Morris County Development Group
• NJIT

• OMSOFT
• PRICE
• Rational
• Reuters
• Rutgers University
• Stevens
• Telcordia
• Verizon

5
Objective

• Software engineering practices become a habit.
• Well crafted software.
• Students aspire to learn practices.
• Executives invest to prevent software failure.

6
The Problem

• Only 30 of all software projects
•  
• meet stakeholders' requirements
• handle offered load
• perform as specified
• estimate schedules and resources reasonably

7
Situation Improving
IEEESoftware Dec 2001
8
Industry View

• Lack of Know-how
• Expensive Tools
• Unproven Practices
• Weak Software Engineering Education

9
University View

• State-of-the-Art vs. State-of-Practice
• Soft technology
• Tools clumsy for individual work
• Small is beautiful

10
Attitude Adjustment

• Students only see the stupidity of others in
  failure case histories.
• Solution Students gain experience by
  living-through project set up to fail.

11
Select Process

• Rigorous requirements engineering
• Design Simplification
• Risk Management

12
LIVE-THRU Design

• Choose a troubled case history.  
• Challenge students with the same problems the
  developers faced.
• Hide pitfalls

13
Design Simplification

• Systems become easier to build and more reliable.
• Eliminates gold plating
• Reuses software components
• Reduces algorithm complexity
• Refactoring

14
Viewpoint

• There is elegance in simple designs. This is
  not easy work, but it is important.

15
Agile Design

• Refactoring
• Eliminate redundant code.
• Eliminate dead-end code.
• Simplify Computations.

16
Software Acquisition

• Named Architect
• Named Project Manager
• Functional Specification
• Performance Specification
• OAM Specification

17
What are Trustworthy Systems?

• Assure that software works as predicted and
  without failure
• Tolerate Faults
• Secure

18
Software Reliability

• Performance is repeatable
• Software is not complex.
• Crashes and hangs rare.
• Bugs are uncommon

19
Undergraduate Industry Projects

• Avaya Configuration Control Utility
• Fall 2000/Spring 2001
• Nine Students
• Software developed in production use
• ContactReinhard Klemm (1 staff month)
• Value 3 staff month _at_ 15k/sm 45k

20
Avaya

• Web Mediation
• - Fall 2001/Spring 2001
• - In progress
• - Five students
• - Software Engineering Lab used
• - Architecture set
• - Contact Joann Ordille (1 Staff Month)
• Value 30k

21
Crescent Technologies

• Web Based Non-Profit Administration
• - 10 students
• - Memberships
• \ - Conference Coordination
• - NJ based Hydraulic Society first
• Customer
• - Donated Project Manager for 6 months
• - Contact Hesham Tamraz
• - Value 40k

22
ATT

• Natural Language Web Search
• - 11 students
• - Web Crawler under development
• - State-of-the-Art Approach
• - Contact Du Eguyen
• -Donated Machine Access to server and two
  people for 2 months
• - Value Unknown

23
Other Projects

• Fuji- Medikey, State-of-the-Art use of miniature
  storage technology. Donated six storage devices
  1200
• Virtual Gold- Web Mining for automobile crash
  data Using Software Engineering Lab
• Donated 1 staff month
• Submarine- School Project

24
Stevens Institute of Technology  Masters
Degree in Quantitative Software Engineering
25
QUANTITATIVESOFTWARE ENGINEERING

• THEORY MOTIVATED BY PRACTICE
•  INDUSTRY-STANDARD TOOLS
• WHEN TO USE AND WHEN NOT TO USE

26
MS COURSES

• Fundamentals of Quantitative Software Engineering
• Requirements Acquisition and Analysis
• Software Design and Architecture
• Software Construction and Configuration
  Management
• Software Testing and Quality Assurance
• Software Economics and Metrics
• Software Technology, Tools and Methods
• Embedded Software
• Software Project I
• Software Project II

27
GRAD CERTIFICATE COURSES

• Fundamentals of Quantitative Software Engineering
• Requirements Acquisition and Analysis
• Software Design and Architecture
• Software Economics and Metrics