project quicklook final presentation
play

Project Quicklook Final Presentation Tactical Satellite 3 System - PowerPoint PPT Presentation

Project Quicklook Final Presentation Tactical Satellite 3 System Design May 11, 2007 Team: Tactical Science Solutions (TSS) Team lead: David Alexander Team members: Soroush (Kevin) Sadeghian Siroos Sekhavat Thomas Saltysiak Faculty


  1. Project Quicklook Final Presentation Tactical Satellite – 3 System Design May 11, 2007 Team: Tactical Science Solutions (TSS) Team lead: David Alexander Team members: Soroush (Kevin) Sadeghian Siroos Sekhavat Thomas Saltysiak Faculty advisor: Prof. Kathryn Laskey External sponsor: Shana Lloyd (Aerospace Corporation) Project type: SE 1

  2. Agenda • Overview • Project Purpose • Results Overview • Project Methodology • Design Project Overview • Trade Study Overview • SysML Evaluation and Lessons Learned • Conclusion 2

  3. Project Purpose • Evaluate SysML as a Modeling Language • Understand capabilities and limitations of SysML • Assess learning curve involved for using SysML • Document capabilities of software tool – Chose IBM Rational Systems Developer • Evaluate SysML’s contribution to more efficient and effective performance analysis • Conduct behavior analysis • Perform a trade study of system design alternatives 3

  4. Results Overview Q: Can SysML perform as advertised? • Yes. SysML allowed traceability between requirements and design model • Yes. It allowed us to conduct a trade study on design alternatives • Yes. It allowed behavior analysis of the designed system Q: Would we use SysML in future projects? • Yes. SysML has proven valuable in designing a small system • The TSS team believes that SysML would be effective in designing large scale systems as well SysML is an adequate modeling language and the software tool SysML is an adequate modeling language and the software tool allowed us to effectively utilize SysML’s capabilities allowed us to effectively utilize SysML’s capabilities 4

  5. Project Methodology • Performed initial project planning and scoping • Elicited and analyzed requirements • Designed a satellite system • Learned Systems Modeling Language (SysML) • Learned relevant software packages – IBM Rational Systems Developer – Embedded Plus SysML toolkit • Conducted behavior analysis on the satellite design • Documented results and findings 5

  6. Project Scope • Design efforts consist of: • Relatively small satellite system • Scoped the design efforts to provide enough content for our trade study • Team training analysis focuses on: • Studying team members’ training and engineering hours • Assessing the learning curve involved with using SysML 6

  7. Design Definition • Tactical Satellite 3 (TacSat-3) is a low cost, small, and rapidly deployable satellite system • Receiving collection tasks • Gathering imagery information • Processing imagery and communication data • Communicating information to the warfighter in < 10 minutes • Focus is on the imagery and communication operations of the TacSat-3 System 7 *Picture from Air Force Research Laboratory Presentation: TacSat-3: Requirements Development for Responsive Space Missions by Capt Stan Straight

  8. Major Project Accomplishments • Monitored training and engineering hours • Completed the TacSat-3 design using SysML • Explored the behavior analysis capabilities of SysML • Documented lessons learned 8

  9. Design Overview • SysML diagrams provide views of the design model and promote communication • The Quicklook design contains over 630 elements and is organized into 26 packages with 45 diagrams • This portion of the presentation will explain our development process and provide diagram examples that highlight key findings 9

  10. SysML Hierarchical Design Model Conduct Requirement, Input/Output, and Conduct Logical Take Component from Higher Level Activity Decomposition of Current Higher Abstraction Level Analysis Level Block Definition Diagram(BDD) and Internal Block Diagrams(IBD) Review Requirements Decomposition/Derived Conduct Activity Requirements Decomposition of Current Level Based on BDD/IBD Confirm Decomposition Current Level Allocate Operations and Interfaces Develop Parametric Develop State Machine Diagrams and Diagrams and Executable Models 10 Attributes

  11. Requirements Requirement Analysis: • Identify any requirements not satisfied • Determine how design changes affect requirements and vice versa • All design elements not driven by original requirements are new derived requirements 11 11

  12. Space Domain and TacSat-3 Imagery Payload Is Imagery Payload Is Further Decomposed Further Decomposed Into Sensor, Processor, Into Sensor, Processor, and Database and Database The First Level Of Decomposition Of The First Level Of Decomposition Of The TacSat- -3 Is Composed Of The 3 Is Composed Of The The TacSat The Space Domain Block The Space Domain Block Imagery Payload and The Vehicle Imagery Payload and The Vehicle Definition Diagram Serves As Definition Diagram Serves As The Context For The TacSat- -3 3 The Context For The TacSat 12

  13. Activity Diagram/Use Cases All Activity Models All Activity Models Are Derived From Are Derived From The Use Cases The Use Cases TacSat- -3 Activity 3 Activity TacSat Diagram Allocates Diagram Allocates Activities To Partitions Activities To Partitions Representing Its Representing Its Activity Analysis: Components Components • Identify all activities that must be Sequence Diagrams Can Be Used To Sequence Diagrams Can Be Used To performed to complete each use case Further Refine Threads From Further Refine Threads From • Association of activities to partitions Activity Diagrams Activity Diagrams and lifelines allocates those activities to blocks in the design Activity Diagrams Define Activities Activity Diagrams Define Activities Of Each Use Case At The Current Of Each Use Case At The Current Level Of Abstraction Level Of Abstraction 13 13

  14. Structure Input/Output Library Input/Output Library During Design Repositories During Design Repositories Object- -Oriented Reuse Principles Oriented Reuse Principles Object The Block Definition The Block Definition Of Reused Entities Are Used Of Reused Entities Are Used Save Significant Design Effort Save Significant Design Effort Diagram Will Be Diagram Will Be To Reduce Duplication Of To Reduce Duplication Of Further Defined By The Further Defined By The Effort Effort Internal Block Diagram Internal Block Diagram Initial Internal Block Diagram Shows Components And Initial Internal Block Diagram Shows Components And External Interfaces External Interfaces 14 14

  15. Behavior and Parametric Diagrams Parametric Equations Parametric Equations Operations Perform Actions Operations Perform Actions Constrain Attribute Values Constrain Attribute Values in Active States in Active States The State Machine Is The The State Machine Is The Command Operations Command Operations Basis For The Discrete Event Basis For The Discrete Event Trigger State Changes Trigger State Changes Executable Model Executable Model Executable Model David Alexander’s Most Excellent Model Parametric Equations Parametric Equations Data Flows Provide Data Flows Provide Provide The Analytical Interfaces for Command Provide The Analytical Interfaces for Command Foundation For The Model Data Foundation For The Model Data 15 15

  16. Executable Model Overview • The executable model allows us to conduct: • Behavior analysis • Performance analysis • State space analysis • Trade study • The executable model provides traceability back to static SysML model • The executable model is tool dependent 16

  17. Executable Model Allocate Automatic Allocate Translation Allocate 17

  18. Trade Study Overview • We used the executable model to determine the following: • Given a captured image size and communications bandwidth, what type of system components are required to meet the system requirements? • What is the best achievable performance within mass and cost constraints? 18

  19. Morphological Box/Trade-off components Initial Conditions Intermediate Raw Image Size = 1,250 MB CalculationsFinal Results Compressed Image Size = 250 MB = Fails to Meet Requirements Total High Data Rate Total Low Data Rate Compressed Image Compressed Image Image Capture and Data Rate Transfer Transfer Time (min) Transfer Time (min) Transfer Time (min) Transfer Time (min) Cost and Processing Time Raw Image High High Data Rate Low Data Rate Total Mass (kg) Performance Total Cost (millions $) Time (min) Results (min) Design Alternative s IPS = 10 16.7 3.7 0.7 22.2 21.1 38.9 30.0 1.5 Option 1 LDRB = 1.5 HDRB = 45 IPS = 50 Performance 3.3 1.2 0.2 11.1 4.8 14.4 40.0 3.0 Option 2 LDRB = 3 HDRB = 137 Options IPS = 100 Option 3 1.7 0.7 0.1 3.3 2.5 5.0 50.0 4.5 LDRB = 10 HDRB = 234 IPS = Image Processing Speed LDRB = Low Data Rate Bandwidth HDRB = High Data Rate Bandwidth 19

  20. SysML Evaluation

Recommend


More recommend