We think you have liked this presentation. If you wish to download it, please recommend it to your friends in any social system. Share buttons are a little bit lower. Thank you!
Presentation is loading. Please wait.
Published byMadison Brennan
Modified over 2 years ago
© Telelogic AB Trade Studies with Focal Point ®
© Telelogic AB Discuss Trade Studies on the design of a JTRS Radio Design
© Telelogic AB Trade Studies in Focal Point Need a team solution – spreadsheets are for individuals. Need the trade study to be integrated into DOORS Need a common methodology for architectural decisions Need a means to document the trade study
© Telelogic AB Architectural Trade Study I Analysis of Design Alternatives When designing a system, an experienced engineer will recognize alternate design choices at the system and subsystem levels. Each design alternative has its own cost, schedule, skill, performance and customer value implications. Design alternatives must be considered against these dimensions to pick the best alternative. Use trade studies to compare and select the optimal design alternative.
© Telelogic AB Architectural Trade Study II Component/Subcomponent Selection When designing a complex systems, software libraries, hardware components, sensors, or subsystems are often outsourced. Each vendors offering can be compared based on its cost, reliability, availability, key performance attributes, and integration requirements. For example, an infrared sensor subcomponent may be compared on the sensing distance, granularity of image, contrast sensitivity, power requirements, availability, reliability, and cost. Use trade studies to compare and select the best vendors product for the design.
© Telelogic AB Allocation of Requirements to Releases (Feature Prioritization) Complex systems are typically delivered in staggered releases. Allocation of features to releases is based the priority of functional behavior. How can we specify the inter-dependencies of requirements then intelligently allocate requirements to a set of staggered releases? Use Analytical Hierarchy Process to assess and assign a relative priority to the independent system requirements.
© Telelogic AB Seven Step Trade Study Methodology 1. Write TS Description, Criteria, and Alternatives in DOORS 2. Mark Alternatives with Trade Study enumeration in DOORS 3. Create Filter and View for each TS in DOORS 4. Create a Module in FP for each TS, create attributes to hold criteria values and normalized scores 5. Add the TS criteria to the FP Criteria module 6. Pairwise Comparisons to determine criteria weights 7. Visualize the results, scenarios analysis, sync to DOORS
© Telelogic AB Trade Studies in Focal Point Need a team solution – spreadsheets are for individuals. –Focal Point has a backend database and web based interface for team collaboration! Need the trade study to be integrated into DOORS –Focal Point and DOORS have a flexible, bi-directional data synchronization Need a common methodology for architectural decisions –Focal Point & DOORS have a 7 step methodology for Trade Studies Need a means to document the trade study –Results and visualizations can be exported for documentation
© Telelogic AB Use Focal Points web interface to manage Trade Studies
© Telelogic AB Visualize the Trade Study result of Vendors versus Criteria
© Telelogic AB Prioritize Criteria Weights and Qualitative Criteria Values using Pairwise Comparisons
Requirements Management Tools ents_Management_Tools.html.
1 Computer Systems & Architecture Lesson 3 5. Designing the Architecture.
What is Test Director? Test Director is a test management tool Test Director is a test management tool Currently available as a plug-in for Quality Center.
1 Note content copyright © 2004 Ian Sommerville. NU-specific content copyright © 2004 M. E. Kabay. All rights reserved. Software Re-use IS301 – Software.
© Telelogic AB Modeling DoDAF Compliant Architectures Operational Systems Technical.
© Telelogic AB 1 Managing Change From Customer Request to Implementation Jean-Louis Vignaud & Dominic Tavassoli.
Telelogic Lifecycle Solutions Connecting People, Process, and Tools Greg Gorman Vice President, Product Management Modeling and Test Products.
Ch:8 Design Concepts S.W Design should have following quality attribute: –Functionality –Usability –Reliability –Performance –Supportability (extensibility,
Overcoming Customer Constraints on Requirements Documents Presented by: Robert Smole Presented by: Robert Smole November 5, 2008 Sub-Optimization of Systems.
Presentation by Prabhjot Singh V-Model. Wikipedia ISTQB Exam Certification.com Resources.
ATAM Architecture Tradeoff Analysis Method Arnon Rotem-Gal-Oz.
1 Slide 1 Ontolog Conference Call – 20 April, 2006 Ontologizing the ONTOLOG Body of Knowledge W hat In It for Me? – Engineering the Value Proposition for.
Management Information Systems MANAGING THE DIGITAL FIRM, 12 TH EDITION GLOBAL EDITION ENHANCING DECISION MAKING Chapter 12 VIDEO CASES Case 1: Antivia:
COMP1007 Introduction to Requirements Analysis © Copyright De Montfort University 2002 All Rights Reserved COMP1007 Introduction to Requirements Analysis.
COMET Approach for UML Overview Chapter 6 Designing Concurrent, Distributed, and Real-Time Applications with UML Hassan Gomaa (2001)
Decision-Making Implications for the Design of IS/IT.
Distributed Processing, Client/Server and Clusters Chapter 16.
RMS and Scheduling for Future Generation Grids Ramin Yahyapour University Dortmund Leader CoreGRID Institute on Resource Management and Scheduling CoreGRID.
Page 1 R Copyright © 1997 by Rational Software Corporation Analysis and Design with UML.
COREP XBRL Project Office Steering Committee,
Recall The Team Skills 1. Analyzing the Problem (with 5 steps) 2. Understanding User and Stakeholder Needs 3. Defining the System 4. Managing Scope 1.
Expediting the Software RFP Process: The CTS EZ RFP.
©Ian Sommerville 2000 Software Engineering, 6th edition. Chapter 14Slide 1 Chapter 14 Design with Reuse.
Requirements Elicitation and Use Case Diagrams Prof. Hany Ammar, CSEE Dept., WVU.
Decision Support Systems and Executive Support Systems.
Sunday Business Systems SBS FMEA Database FMEA Background SBS Database Features and Benefits SBS Database Set-up and Use.
©Ian Sommerville 2000 Software Engineering, 6th edition. Chapter 8 Slide 1 Chapter 8 Software Prototyping.
IBM Rational Requirements Management Tools Achieving better control over your requirements.
1 Systems Engineering A Way of Thinking A Way of Doing Business Enabling Organized Transition from Need to Product August 1997 Systems Engineering Technical.
1 Software development WP6. 2 Team CEFAS: architecture and documentation IC: modules for calculating new functions (penalty prob.; enforcement cost) AZTI:
© 2016 SlidePlayer.com Inc. All rights reserved.