1 Software and Software Engineering 2 Process Models 3 Agility and Process 4 Recommended Process Model 5 Human Aspects of Software Engineering 6 Principles That Guide Practice 7 Understanding Requirements 8 Requirements Modeling—A Recommended Approach 9 Design Concepts 10 Architectural Design—A Recommended Approach 11 Component-Level Design 12 User Experience Design 13 Design for Mobility 14 Pattern-Based Design 15 Quality Concepts 16 Reviews—A Recommended Approach 17 Software Quality Assurance 18 Software Security Engineering 19 Software Testing—Component Level 20 Software Testing—Integration Level 21 Software Testing—Specialized Testing for Mobility 22 Software Configuration Management 23 Software Metrics and Analytics 24 Project Management Concepts 25 Creating a Viable Software Plan 26 Risk Management 27 A Strategy for Software Support 28 Software Process Improvement 29 Emerging Trends in Software Engineering 30 Concluding Comments

1. Software Testing Background a. What is the software defect? b. Why do bugs occur? c. The Cost of bugs? d. What exactly does a tester do? e. The making of a software tester 2. The Software Development Process a. What is a software product? b. Software Project staff c. Software Lifecycle Models 3. The Realities of Software Testing a. Testing Principles b. Terms and Definitions for software testing

What is software Software is Everywhere Software Crisis and Software Failures From Software Development to Software Engineering Development Activities

• Computer-Aided Software Engineering • Formal Methods • Software Reuse • Reengineering • Component-Based Software Engineering • Cleanroom Software Engineering • Client/Server Software Engineering • Web Engineering

 About this course.  What is software reliability?  What factors affect software quality?  What is software reliability engineering?  Software reliability engineering process

• Software Process • Software Quality Assurance • Software Configuration Management • Software Project Management Concepts

The last decade has seen a revolution in software engineering tools and techniques. This revolution has been fueled by the ever-increasing complexity of the software component of delivered systems. Although the software component of delivered systems may not be the most expensive component, it is usually, however, “in series” with the hardware component; if the software doesn’t work, the hardware is useless

• Background • Software Security: Control-flow Hijack Attack ➢ Memory Layout , Stack frame, & Procedure ➢ Buffer Overflow: Vulnerability, & Defenses ➢ RILC, Return-Oriented Programming ➢ ASLR & CFI • Software Security: Non-control Data Attack ➢ Data Oriented Programming • Summary

Software is intangible Hard to understand development effort Software is easy to reproduce Cost is in its development —in other engineering products, manufacturing is the costly stage

Background OF TECHN Why is Software Engineering Hard? “Curse of flexibility \And they looked upon the software and saw that it was good. But they just had to add one other feature ... No physical constraints