SE310 Analysis and Design of Software Systems

Transcription

1 SE310 Analysis and Design of Software Systems Lecture 2 OO Examples and Process Introduction January 8, 2015 Sam Siewert

2 Overall Learning Objectives What to Build? Requirements as Capabilities Methods to Identify Requirements How to Specify It? Domain Modeling Architecture and Design Patterns (Object Oriented) Design Inspections OOA/OOD UML (Universal Modeling Language) Translation of OOA/OOD to an OOP (C++ or Java) Sam Siewert 2

3 Java Applet ATMExample Note You Must add Security Exception to Run with Configure Java as Show Below Sam Siewert 3

4 Java Applet - ATMExample Implements Sam Siewert 4

5 UML Use Cases Class Structure (Data and Operations on that Data) Use Cases and Corresponding Interaction Diagrams Actors in Use Case Behavior Shown by Interaction Diagrams Sam Siewert 5

6 UML Class Diagram Much Like ER / EER if you Have Had CS 317 Shows Class Relationships and Hierarchy Arrows Dashed Uses/Dependencies and Solid Relationships with Cardinality One ATM Instance Supports Many Sessions Over Time [Each Requires Card Read] One ATM Instance Supports Many Transactions (Abstract) Transaction Abstract Class Defines Specific (Refined) Transaction Types Sam Siewert 6

7 UML Interaction Diagrams Behavior Object Interactions over Time Solid Lines: Operations that Start Execution Sequences Dashed Lines: Messages Wide Vertical Lines: Active Process Started by Operation With Messaging X: End of Interaction (E.g. Specific Session) Sam Siewert 7

8 Detailed Design Class Public and Private Data Class Operations on Data Constructors and Destructors for Instantiation of Object Sam Siewert 8

9 Operations and State State Charts Operational Input Changes State of Objects [Output] At Any Time, Object is in One Well-known State Start State State: Object Instance Needs Specific Data, Waits on Next Input Input / Output On Transitions Termination State: End of Instance Sam Siewert 9

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

11 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 11

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

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

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

15 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 15

16 Assignment #1 Activities Bring Up Modelio and Start Entering Address Book or ATM Design Enter Classes and Diagrams Covered in Class Simplify, But Complete (At least 3 of each Diagram Type) Can You Implement in C++? Now? [g++ on PRClab] ATM Authors Use Java Dr. Java for Windows [Optional] When Should Code Construction Start? Sam Siewert 16