Software Engineering Class 6 - Software Engineering(CSC 4350\/6350 Rao Casturi Recap UML Introduction Basic UML concepts GSU Software Engineering

Software Engineering Class 6 - Software Engineering(CSC...

This preview shows page 1 - 9 out of 37 pages.

Software Engineering (CSC 4350/6350) Rao Casturi
Recap UML Introduction Basic UML concepts GSU: Software Engineering - CSC4350/6350 - Rao Casturi 2
Basic Notations of UML GSU: Software Engineering - CSC4350/6350 - Rao Casturi 3 1. Use Case Diagrams 2. Class Diagrams 3. Interactive Diagrams 4. State Machine Diagrams 5. Activity Diagrams Requirement Phase Analysis Phase Design Phase Object Design Phase
3 Major areas of focus in System Development 4 System Development Functional Model Object Model Dynamic Model Use Case Diagrams Class Diagrams Interaction, State Machine , Activity Diagrams Output or produces Output or produces GSU: Software Engineering - CSC4350/6350 - Rao Casturi UML helps us in modeling our problem to get a meaningful solution Functional Model Functionality of the system from users view. Represented in UML via use case diagrams. Object Models Represented in UML: via class diagrams describing the Structure of the system in terms of objects, associations and operations. Dynamic Models Represented in UML via sequence diagrams (ID), state charts and activity diagrams describing the internal behavior of the system.
Format for an Use Case 5 Use Case Name UC_001_BalancePortfolio Actors/Participants Portfolio Manager Flow of events 1. Select the Portfolio name 2. Get the Portfolio market value and available case in portfolio 3. Select sell/buy option depending on the cash balance to deploy 4. Confirmation notification for the selected order 5. Confirm the order 6. Generate the trade ticket and request the order and generate order code 7. Enter the order code on trade transmission and submit the order Entry Condition When a Portfolio Manager should be logged on to the Trade Order Management Module Exit Condition When the case in the portfolio is near zero or less than .01 % of the portfolio value Quality constraints The transaction should be completed with in 3 minutes from the time the system generates an order code GSU: Software Engineering - CSC4350/6350 - Rao Casturi
Scenarios Use case is an abstraction that describes all possible scenarios involved in a functionality Scenario is an instance of the use case describing a concrete set of action from a single user point There is no need for Entry or Exit Conditions Scenario describes only a specific situation so exit and entry conditions won’t apply GSU: Software Engineering - CSC4350/6350 - Rao Casturi 6 Scenario Name PortfolioMarketValue Actors/Participants Rao:PortfolioManager Flow of events 1. System will get go to the holdings database to filter the portfolio name 2. Sum all the holding for a given date 3. Return the sum value as market value
4. Schedule Mapping of task on a timeline or plot Each task has a life of its own (Start and End) 2 Types of Schedule Charts are widely used PERT and Gantt Charts Gantt Chart ( TASK vs Time) 7 GSU: Software Engineering - CSC4350/6350 - Rao Casturi
PERT Charts (Program Evaluation Review Technique) GSU: Software Engineering - CSC4350/6350 - Rao Casturi 8 1 2 3 4 7 5 8 6 9 11 10

  • Left Quote Icon

    Student Picture

  • Left Quote Icon

    Student Picture

  • Left Quote Icon

    Student Picture