SE310 Analysis and Design of Software

Size: px

Start display at page:

Download "SE310 Analysis and Design of Software"

Shannon McGee
5 years ago
Views:

1 SE310 Analysis and Design of Software Lecture 14 REVIEW March 26, 2018 Sam Siewert

2 Domain Models Use Case Details Complete a Design Provide Code Re-Use Candidate and PoC/Prototype Start Here! USE Modelio as your DESIGN TOOL Helpful Validation and Verification Features for Design Integrated Models Checklists Completeness CPP and Java Code Generation Key Value of Each Model Proper Use Notation, Phase Consistency, Completeness Correctness Sam Siewert 2

3 Testing Strategies Considerations for Software Test and Evaluation NDIA Software Test Summit Dr. Ernest Seglie, Science Advisor to the Director, Operational Test and Evaluation Software Engineering: A Practitioner s Approach, 8/e (McGraw- Hill, 2014) copyright 2014 by Roger Pressman Process phase descriptions can vary. However, the concepts and theory are generally the same for a given model. Progression from Specification, to Analysis to High-Level Design (Architecture and System) to Components in Subsystems, to Units or Modules of Code Sam Siewert 3

4 OOSE Chapter 12 Part III (Interactive Systems, Beyond OIM) User Interface Design Interactive Systems Key Values [Human Computer Interaction] Window multi-tasking [ , web, IDE] Easy to Learn and Use [subjective, but most consumers prefer to command line] Multi-media Presentations [Video, Visualization Graphics, Audio, Animation] GUI Widgets [e.g. X-windows and Qt, MS Windows] Kung P. 303 Major System Displays, Figure 12.5 User Interface State Diagrams P. 306, Figure 12.9 in Kung Prototypes [Mock-Ups] Guidelines Sam Siewert 4

5 OOSE Chapter 13, Part IV Object State Modeling Event-Driven Collecting and Classifying State Behavior Extensions to Domain Models [Class Diagram and OIM] to add Domain State Machine Model P. 325, Figure 13.6 [Thermostat Domain State Machine] P. 326, Figure 13.4 [Cruise Control Domain State Machine] P. 336 State Pattern CFD/DFD [Transformations on State Transition] SDL FYI Not on Exam(s) For Event-Drive Architectures or Architectures with Event-Driven Aspects and Subsystems, EFSMs are High-Level (Domain) State Transition Tables UML Notation P. 331 event[guard] / act1; act2 Cruise Control P. 332 Sam Siewert 5

Petri-Net Formalism, Can Be Simulated and Used for Cleanroom SWE P.

6 OOSE Chapter 14 Activity Models Concurrency, Fork, Join for Tasks Task Could Be Implemented as Linux Process, POSIX Thread, VxWorks Task, Unix/Windows Service, etc. Petri-Net Formalism, Can Be Simulated and Used for Cleanroom SWE P. 352 CFD/DFD UML Activity Diagram Notation P. 355 Activity Table - Analysis Office of Int l Ed. P. 361 Sam Siewert 6

OOSE Chapter 18 Part VI (QA) Coding Standards Code Generation from Design, P. 459 in Kung SQL from MySQL Workbench [CS317] C++ from Modelio [Domain Model] Potentially All Code E.g. Telelogic SDL Generated Code Can be Ugly [Hard to Maintain] GOTO almost Unavoidable for State-Machines Make a Trade-off Test-Driven Development [Flowchart P.

7 OOSE Chapter 18 Part VI (QA) Coding Standards Code Generation from Design, P. 459 in Kung SQL from MySQL Workbench [CS317] C++ from Modelio [Domain Model] Potentially All Code E.g. Telelogic SDL Generated Code Can be Ugly [Hard to Maintain] GOTO almost Unavoidable for State-Machines Make a Trade-off Test-Driven Development [Flowchart P. 464 in Kung] Pair Programming [Agile Scrum and XP] Concurrent Test + Analysis/Design/Construction Sam Siewert 7

8 OOSE Chapter 19 - SQA P ilities, ISO/IEEE Quality Attributes Non-Functional Quality Metrics Table on P. 475 in Kung Structure Chart Complexity Metric Cyclomatic Complexity Reliability and Availability MTTF, MTBF, MTTR Inspections and Walk-throughs Verification and Validation [Design Level, Code Level] Design E.g. Verify that Model is Consistent, Adheres to Notation (Design Entry), Simulates (E.g. Petri-Net) Design E.g. Validate that Use Cases Trace to Requirements Code Validate Function Implements Class Diagram Method, Verify that Code Terminates Loop Given Input Vector Sam Siewert 8

9 OOSE Chapter 20 SWE Testing Dynamic Must Run Code Static Compiles, Passes Wall, Lint Bug vs. Defect [Reported vs. Root-Cause Verification] Types of Code Level Tests (Unit) Functional Black-box, P. 504 Equivalence Partitioning P. 506, Figure 20.2 Boundary Value Analysis, P. 508, Figure 20.3 Cause and Effect Construct Decision Table White-Box Path Testing (Coverage) Cyclomatic Complexity and Coverage Criteria Loops Dataflow Testing [Concept Only] Software Testing Process P. 517 Test Case Identification and Generation [from Design] Performance and Stress Testing EXIT Criteria for Testing Sam Siewert 9

10 Take Away Value of OOA/OOD and OOP Compared to or in Addition to SA/SD and other Formalisms (SDL, Petri- Nets, Box Notation) Practice and Proficiency with UML Addition of Block Diagrams and SA/SD to Complete Specifications Concurrent Test of Requirements, Analysis, Design, Prototypes/PoC and Constructed Modules Deployment, Maintenance, Refactoring Sam Siewert 10

SE310 Analysis and Design of Software Systems

SE310 Analysis and Design of Software Systems Lecture 2-2 Systems Engineering for OO January 17, 2018 Sam Siewert Learning Objective Software Engineering Process? Lifecycle Phases feedback SPIRAL in Agile