SE310 Analysis and Design of Software Systems

Transcription

1 SE310 Analysis and Design of Software Systems Lecture 2-2 Systems Engineering for OO January 17, 2018 Sam Siewert

2 Learning Objective Software Engineering Process? Lifecycle Phases feedback SPIRAL in Agile XP Extreme In Agile WATERFALL Agile Manifesto that Hosts Spiral, XP, Scrum, Feature- Driven or any Iterative Process [Waterfall with Feedback] Requirements? Architecture? First Phase is Research, Analysis and Specification Sam Siewert 2

3 Notes on Research for Systems Software is Often Integrated in Specific Domains (Requires Research) Energy Transportation, Shipping Security, Remote Sensing, Defense Information Storage and Retrieval, Enterprise Systems Decision Support Systems Aviation, Aerospace Research can Start with Simple Google Search or Wikipedia, but should follow pointers to peer-reviewed resources [citations and references] IEEE Xplore, ACM Digital Library Google Scholar, Microsoft Academic Search Research Gate [research social network] ERAU Library Resources Industry Specifications, Journals, Developer Papers, White Papers [IBM, Intel, NVIDIA, Texas Instruments, ] Non-profit research institutes and agencies [CERT, SEI, NDIA, FAA, FIPS, CSRC, ] Who are you referencing and citing and why? Sam Siewert 3

4 Overall OO Lifecycle Overall Learning Objectives Requirements, Architecture, Unit/Sub-System Construction, Integration & Test, CM Translation of OOA/OOD to an OOP (C++ or Java) Recall that Testing starts with SWE Kick-off SQA is a Concurrent Effort Cross-Validation During Each Phase Test Requires Design and Development Test Execution Starts with Design if Possible, But with Code Units for sure Sam Siewert 4

5 When Does OOP Code Construction HW & SW Engineering can be Concurrent Start? Test and Design/Dev can be Concurrent Regression Testing Depends upon Process Used Sam Siewert 5

6 Exploratory Coding Early Coding Must be Done Carefully, But Can Be Useful Prototyping Throw-Away Connotation Sometimes Frowned Upon Proof-of-Concept Algorithms or Design Aspects Where Implementation is Expected to Be Large Challenge, Computationally Complex Operational Specification Best! Executable Design is the Goal. CASE (Computer Aided Software Engineering) Tools MySQL Workbench Schema Analysis and Design, SQL Generation GUI Builders, E.g. Qt, Java GUI Builders Sam Siewert 6

7 Java Applet - AddressBook Same Issue with Java Security (allow site) Sam Siewert 7

8 Java Prototyping If You Like Java and Want to Prototype Designs or build PoC Apps, Try Dr. Java on Windows or use javac bytecode compiler on PRClab E.g. fibonacciseq.java is a simple Example Class Sam Siewert 8

9 Dr. Java for Windows, Nice IDE Java Development Udacity Course on Java - ity.com/course/cs 046 Absolute Java Book Sam Siewert 9

10 Traditional SA/SD Useful, But Not OO Data Flow Diagrams Data [Messages] Between Processes and is Transformed Stores, Flows, Processes, External Entities Entity Relationship Diagrams Lacks Operations, but Defines Entities [Objects] and Relationships SE300 State Machines [in Common, but Typically for Each Process in DFD] Flow-Charts Detailed Procedural Design [Interaction, Logic] Sam Siewert 10

11 Code, Analysis, Design, Test - CMVC Any Non-Binary File (Binary Ok, but Less Useful) SSH is Best Option with PRClab See Lecture-Notes-on-Git-for-CMVC.pdf Sam Siewert 11

12 Architecture and Design Patterns OO Has Goal of Design and Software Re-Use Encapsulation of Data and Operations Class Hierarchy and Object Instances Well Understand Use Cases Well Understand Interaction Between Objects Study 4 Key System Types 1. Interactive E.g. GUI, CLI 2. Event Driven E.g. Anit-lock Breaking System Software 3. Transformational E.g. Image Processing, Encode/Decode [MPEG Digital Video, RAID] 4. Transaction Oriented E.g. DBMS Sam Siewert 12

13 Domain Models Use Case Details UML is Universal Modeling Language [OMG, UML.org] Use to Support Requirements Analysis Start Here! USE Modelio 3.7 SD as your DESIGN TOOL OMG UML 2.5 Standard Structural Diagrams Start with Class Diagram and CRC Then Object Diagram Package and Deployment Behavioral Diagrams Start with Use Case Diagram Interaction Sequence Diagram after Class and Object Done Add State Machine and Activity Diagrams for concurrency and statefulness Helpful Validation and Verification Features for Design Integrated Models Checklists Completeness CPP and Java Code Generation Sam Siewert 13

14 Start with Use Case and/or Level-0 Class Diagram Modelio Examples Hands-on Class Diagram (Level-0) Names and Relationships Generalization (sub-class or type-of) Composition (Elements of a Class that compose) Association (Money comes from 1 cash dispenser) Add Attributes Leave Methods for Level-1 Sam Siewert 14

15 Use Case Defines What is in Scope Must be Designed, Subsystem in System Interfaces to Users or External Agents Sam Siewert 15

16 Navigation and Types Indicate Level of Diagram (L0 specification only, L1 spec + methods, L2 full detail) Some CASE Tools support Leveling, Some Do Not if not, use naming convention Built-in Types Derived Types (Classes) Sam Siewert 16

17 Refine to Create Modules Group Classes into Modules (C++ Files) Sam Siewert 17

18 Generating Code For Source Code Management, Verify Modelio C++ Designer or Java Designer Modules Built-into SD Version (licensed) on SE Workstation Not Available in Open Source Version Sam Siewert 18

19 Modelio Academic Version Includes C++ Designer (C++, C#) for Code Generation from Modesl Includes Java Designer for Code Generation Forward and Reverse Engineering Auto-generation of Diagrams from UML XMI (XML Metadata Interchange) Can Target Windows, Linux, Unix Sam Siewert 19

20 Code Generation from Class Model Class kind must be C++ Class (not UML) Use Code Generation and Code View Buttons on C++ Tab Can Generate a Makefile Sam Siewert 20

21 Code is Generated for Export to Target Makefile (not working), but compile with g++ Can add int main(void) and start writing test driver Bring back to model and retrieve updates to synchronize Sam Siewert 21