1. 1/3/2016  1998-Present Fayad KSU – SWE Process and Modeling Software Process and Modeling Dr. M.E. Fayad, Professor Software Engineering Department, Room #2022 College of Computer and Information Sciences (CCISs) King Saud University P.O. Box 51178 Riyadh 11543 http://www.engr.sjsu.edu/fayad, mefayad@gmail.com

2. L1-S2Introduction 1/3/2016  1998-Present Fayad KSU – SWE Process and Modeling 2 Lesson 1: Introduction

3. L1-S3Introduction 1/3/2016  1998-06 Fayad KSU – SWE Process and Modeling Lesson Objectives 3 Discuss the following terms: Standards Methodology/paradigm/process Models Methods processes Discuss the essential properties of a process Explore Process Models

4. L1-S4Introduction 1/3/2016  1998-06 Fayad KSU – SWE Process and Modeling Standards imply regulations, guidelines, rules, laws, and so on. Standards can dictate named methodologies, such as IEEE standards or DOD standards (Ex: DOD-STD-2167A). A standard alone is not sufficient on getting a task completed. Why? 4 Standards [Fayad-Laitinen 1998]

5. L1-S5Introduction 1/3/2016  1998-06 Fayad KSU – SWE Process and Modeling Because standards focus on the attributes of the results instead of how the results will be achieved A standard also includes a type, model, or example commonly or generally accepted or adhered to, such a criterion set for usage or practices (moral standards) Standards applies to some measure, principle, model, and so on, with which things of the same class are compared to determine their quantity, value, quality, and so forth (standards of purity in drugs) 5 Standards [Fayad-Laitinen 1998]

6. L1-S6Introduction 1/3/2016  1998-06 Fayad KSU – SWE Process and Modeling A methodology is “a science of method or orderly arrangement” Webster. A methodology is used to refer to the very highest level of the way we do things. A methodology also refers to “a system of methods, as in particular science” The methodology we will consider here cover only the development of software applications. 6 Methodology [Fayad-Laitinen 1998]

7. L1-S7Introduction 1/3/2016  1998-06 Fayad KSU – SWE Process and Modeling A method implies a regular, orderly, logical procedure for doing something, such as a method of finding software requirements. Exs: Waterfall model, spiral model [Boehm84], and fountain model [Henderson-Selers90]. Jacobson defines a method as a planned procedure by which a specific goal is approached step by step [Jacobson92]. Examples of software design method are a set of work procedures, a set of notations, or a set of heuristics. 7 Methods or Techniques

8. L1-S8Introduction 1/3/2016  1998-06 Fayad KSU – SWE Process and Modeling Software engineering methods can be divided into three major categories: 1. Process-Oriented Methods [Yourdon89] 2. Data-Oriented Methods [Martin90] 3. Object-Oriented Methods [Fayad93, Rumnaugh91, etc..] 8 Methods or Techniques

9. L1-S9Introduction 1/3/2016  1998-06 Fayad KSU – SWE Process and Modeling 9 POM vs. OOM

10. L1-S10Introduction 1/3/2016  1998-06 Fayad KSU – SWE Process and Modeling 10 Method Provides Foundation for Software Engineering

11. L1-S11Introduction 1/3/2016  1998-06 Fayad KSU – SWE Process and Modeling 11 The Myth of the Single Software Development Method

12. L1-S12Introduction 1/3/2016  1998-06 Fayad KSU – SWE Process and Modeling 12 How Many OO Methods Exist? UML

13. L1-S13Introduction 1/3/2016  1998-06 Fayad KSU – SWE Process and Modeling 13 Engineering Process Hierarchy Engineering ComputerElectronics SoftwareHardware SASDOOT UML Scientific Area Standards Methodologies (Macrodevelopment Processes) Techniques (Methods) (Minidevelopment Processes) Processes (Microdevelopment Processes OMT Identify Classes Identify Attributes

14. L1-S14Introduction 1/3/2016  1998-06 Fayad KSU – SWE Process and Modeling 14 Processes are Important for a new OO Teams New methods and tools introduce confusion Processes define exactly who, what, when, and how –“big-picture”

15. L1-S15Introduction 1/3/2016  1998-06 Fayad KSU – SWE Process and Modeling 15 Method vs. Process Processes take OO methods out of the classroom and put them to work Theoretical Ideas Predictions Practical Concrete Actions Metrics

16. L1-S16Introduction 1/3/2016  1998-06 Fayad KSU – SWE Process and Modeling Software engineering life cycles or phased software development models, such as –Waterfall model –Prototyping –Spiral Model –Automatic Programming –Reuse Models –Incremental Model –Fountain Model –XP Model –Software Stability Model 16 Software Engineering

17. L1-S17Introduction 1/3/2016  1998-06 Fayad KSU – SWE Process and Modeling 17 Waterfall Model Requirements Analysis Design Coding Requirements Specifications Testing

18. L1-S18Introduction 1/3/2016  1998-06 Fayad KSU – SWE Process and Modeling 18 Prototyping Requirements Specifications Requirements Analysis Coding Demonstration Design Coding Testing Maintenance Design Prototype Coding DesignCode Test Maintenance Requirements Build Prototype Document Requirements Test Prototype

19. L1-S19Introduction 1/3/2016  1998-06 Fayad KSU – SWE Process and Modeling 19 Spiral Model

20. L1-S20Introduction 1/3/2016  1998-06 Fayad KSU – SWE Process and Modeling. A UTOMATIC P ROGRAMMING Requirements Analysis Formal Specifications Automatically Generated Code 20

21. L1-S21Introduction 1/3/2016  1998-06 Fayad KSU – SWE Process and Modeling. R EUSABLE M ODULES Decompose Application Domain Specify Module Requirements Module Design Module Code Module Test Application Requirements Configure Reusable Modules Customize Reusable Modules Integrate Modules Testing OTI-93F-0014 21

22. L1-S22Introduction 1/3/2016  1998-06 Fayad KSU – SWE Process and Modeling. I NCREMENTAL M ODEL Product Design Verification Increment 3 Increment 2 Operations and Maintenance Revalidation Detailed Design Verification Code Unit Test Integration Product Verification Implementation System Test Increment 1 Detailed Design Verification Code Unit Test Integration Detailed Design Verification Code System Feasibility Validation Software Plans & Reqmts Validation 22

23. L1-S23Introduction 1/3/2016  1998-06 Fayad KSU – SWE Process and Modeling. Coding Design Software Requirements Specification Requirements Analysis System Testing Coding Module Specification Maintenance Further Development Module Design Real-World Systems Real-World Entity [Henderson-Sellers90] Program Use Maintenance Further Development Acceptance into Library F OUNTAIN M ODEL 23

24. L1-S24Introduction 1/3/2016  1998-06 Fayad KSU – SWE Process and Modeling What are the differences between requirement analysis and software design? What are the requirement analysis and software design? 24 Analysis & Design

25. L1-S25Introduction 1/3/2016  1998-06 Fayad KSU – SWE Process and Modeling 25 Analysis & Design Fuzzy line Problem space Analysis One problem The “What” Solution space Design Many solutions The “How”

26. L1-S26Introduction 1/3/2016  1998-06 Fayad KSU – SWE Process and Modeling List all the major process activities in the lifecycle phases: Requirement analysis, software design, software construction, software testing, software maintenance List all major activities in software project management: Software planning, Staffing, Controlling and tracking the project, etc. T/F –Software processes should be fixed. –Software process should be measurable. –Software process specifies the why and ignore the how. Define: –Automatic Programming and Fountain Model 26 Discussion Questions

27. L1-S27Introduction 1/3/2016  1998-06 Fayad KSU – SWE Process and Modeling The manager’s roles and responsibilities in software process Measure process rather than people The top five excuses for no process documentation Process assessment Process improvement models The trouble with process assessment How to use processes as a baseline for improvement Software process hierarchy How to document process Recommendations for documenting processes 27 Questions for the Next Lecture