CPSC 372: SOFTWARE ENGINEERING

Transcription

1 CPSC 372: SOFTWARE ENGINEERING Substitute: Yates Monteith, Fall 2013

2 Schedule Who am I? UML Use Cases SysML Requirements Sequence TopCASED SonarQube

3 Who am I? Yates Monteith B.S. CompSci, Manhattan College 2008 M.S. CompSci, Clemson University, 2010 Ph.D. CompSci, Clemson University 2014? Research Software Ecosystems Software Architecture Strategic Software Engineering Interests Video Games, Radio Broadcasting

4 Unified Modeling Language (UML) Standardized, general purpose modeling standard. Standardized General Purpose Primarily Object Oriented Can be used with non-oo systems. Less powerful. Standardized way to visualize: Activities and Actors Programming Routines and Software Components Deployment Models and Database Schema And much more

5 UML: A Brief History OO Languages Modeling Languages In the 90s, during the rise of OO, many existed Needed something better. Too many languages meant too much model incompatibility. Jacobsen Use Classes Rumbaugh (OMT) Object Models (Object Diagram) Dynamic Models (State Machines) Functional Models (Process Models) Booch Class Diagrams

6 UML Models What is a model?

7 UML Models What is a model? A pretty picture.

8 UML Models What is a model? A pretty picture. Errata: That [hopefully] that provides understanding and semantic meaning behind the thing it is describing.

9 UML Models What is a model? A pretty picture. Errata: That [hopefully] that provides understanding and semantic meaning behind the thing it is describing. Models help us specify code or design in a nontextual way. Why is this a good thing? Yes! Models provide

10 UML Models Models can provide: Communication on details in an unambiguous way. Documentation of the inner-workings of a system. Ways of performing reasoning on and measuring a system before it is built. And so much more

11 Types of UML Models Structural Profile Class Composite Structure Component Deployment Object Package Behavioral Activity Use Case State Machine Interaction Sequence Timing Communication Interaction Overview

12 UML Diagram of UML Diagrams

13 Use Case Diagrams Pronounced YOOSE-CASE Depicts a set of high level functionalities from the perspective of different actors. What is an actor? Anything that can interact with the system. Usually Stick Figures. With Top Hats. What is a YOOSE-CASE High level functionality that is associated with actors and other use cases through various relationships. Usually ovals or circles. No Top Hats.

14 Use Case Diagrams Also, Relationships. Use Case Use Case Relations Use Case Actor Relations Actor Actor Relations What kind of relations? Association Generalization Extension Composition Etc, etc, etc

15 Use Case Diagram Composed from Scenarios. Scenarios are English descriptions of a high level functionality. Scenarios are engineered during a Requirements Elicitation. Example Scenario: User is typing an SMS message and receives a phone call. Incomplete message is stored in local memory during call and recalled once call is completed. What sorts of Use Cases do we see here?

16 Use Case Diagrams Primarily created during the Requirements Specification phase of the Software Development Life Cycle. What do we use Use Cases for?

17 Use Case Diagrams Primarily created during the Requirements Specification phase of the Software Development Life Cycle. What do we use Use Cases for? Everything. Literally everything. Requirements analysis. Test planning Client communication Even more When do we use the Use Case Diagram?

18 Use Case Diagrams Primarily created during the Requirements Specification phase of the Software Development Life Cycle. What do we use Use Cases for? Everything. Literally everything. Requirements analysis. Test planning Client communication Even more When do we use the Use Case Diagram? Every phase of the SDLC.

19 Use Case Diagrams What are the limitations of the Use Case Diagram?

20 Use Case Diagrams What are the limitations of the Use Case Diagram? Can t model non-functional requirements effectively. Fast something loads (Performance) Memory footprint (Efficiency) They can be very difficult to write. There s a lot of research and books on writing good Use Cases. Next up: An exercise.

21 Sequence Diagram Shows how processes interact with each other, and the order of that interaction. Composed of a series of lifelines, i.e. processes. Interaction is modeled as the passing of messages. Modeled by horizontal arrows between lifelines. Activation Boxes represent processing being done in response to a message. Opaque vertical rectangles over the lifeline. Next up: SysML

22 SysML Extension of the UML profile primarily targeted at Systems Modeling. Managed by the Object Management Group (OMG) Adds several additional diagrams to the UML Profile. Notably the Requirements Diagram Let s head to TopCASED.