Manuals / IBM / Fitness & Sports / Fitness Equipment

IBM SG24-7368-00 manual Model Driven Systems Development with Rational Products

Models: SG24-7368-00

1 224

Download 224 pages 36.08 Kb

Install Mdsd Create a context diagram Early detection of errors How to Service GPS navigation system features Using the Web material

Page 190

174Model Driven Systems Development with Rational Products

Page 189 Page 191

Image 190

IBM SG24-7368-00 manual Model Driven Systems Development with Rational Products

Page 189 Page 191

Our partner
Обсуждение вопроса Какова примерно цена аренды? из чата Гаражний кооператив "Мюнхен" 🇺🇦, Мюнхен, Германия

Related pages Additional Information Troubleshooting for Pioneer SRC7127-B/N Specifications for Sharp MD-MT180H Error Codes for Honeywell UDC3200 Flowchart 2.3-No Power, Part for HP dv5000 dv5000 HOW to Prepare the Engine for Murray 425303x92B Without finisher With finisher installed for Lexmark X945E Parts List Price for Graco ISPA081AA TV Brand Code List for Samsung HT-TX25 Circuit Configuration for Fujitsu MPA3017AT Can I find maintenance tips in the Emerson HIPULSE UPS user manual?

Contents

Model Driven Systems Development with Rational Products Page Model Driven Systems Development with Rational Products First Edition February Contents Views Transformation methods Summary The core Mdsd process Page Summary of SysML basics Index Viii Model Driven Systems Development with Rational Products Copyright License Trademarks RUP Preface Team that wrote this book Become a published author Thank you Comments welcome Introduction Challenges of systems development Changed context for systems development Management of complexity Creative/dynamic and transactional complexity Overview of model-driven systems development Central problems Mdsd addressesBenefits of modeling Introduction Multiple views to address multiple concerns Integration of form and function Two analogies Project management Benefits of model-driven systems development Scalability Isomorphic composite structures and recursion Reduction of risk Enhanced team communication Explicit processes for reasoning about system issues Early detection of errors High cost of requirements errors Integration as you go-better architecture Traceability Well defined semantics Core processes of model-driven systems development Defining context Defining collaborations Prerequisites/required foundational concepts/languages Distributing responsibilities How the book is organized UML Definitions, design points, and key concepts System ServiceDefinitions Requirement Artifact Use case Actor OperationLocality Connection Design pointsFour basic principles Additional design points RUP Process Framework adopted by Mdsd Provide tool assets Key conceptsEmploy the appropriate semantics and modeling languages Maintain all model levels as program assets Context level Model levelsAnalysis level Design level ViewpointsImplementation level Viewpoint Expresses Concern Views Transformation methods System of systems decomposition Operations analysis Levels of system decomposition Joint realization Summary The core Mdsd process Requirement derivation Definitions, design points, and key concepts Model Driven Systems Development with Rational Products Black-box thinking Defining the system context Importance of understanding context Context and description System in context An important context Usage Usage-driven versus feature-driven system design GPS navigation system features GPS navigation system usages Mdsd Define the system context Actors and boundariesMdsd Finding actors Primary and secondary actors Questions to discover actors Actors and value Actors and the system boundary Mdsd Create a context diagram Sample context diagram Entities Mdsd Finding I/O entities Retail system context diagram Use cases Black-box thinking Defining the system context Mdsd Finding use cases What do you use your car for? Black-box thinking Defining the system context Writing a brief description Retail use case diagram Actor involvement in use cases Level of detail in use case flows Use case flows of eventsMdsd Write use case flows of events Initiation of the use case Understanding collaboration from a black-box perspective Using activity diagramsExamples of use case initiation Identifying operations Mdsd Operation identification Incorrect sequence diagram Requests The key to operations Specifying request signatures Information in the Mdsd model Message naming a quiz Which messages are correct? Toward better requests Unlocking car Cumbersome sequence Identifying operations from the sequence diagram Sequence diagram with arrowheads circled in red Model Driven Systems Development with Rational Products More about operations Refactoring operationsMdsd Refactoring and consolidating enterprise operations Model Driven Systems Development with Rational Products Summary Model Driven Systems Development with Rational Products White-box thinking Understanding collaboration Logical viewpoint Operation realizationMdsd Operation realization Mdsd Creating element context diagrams Operation analysis Black-box sequence diagram Operation specification example Enterprise operation Initiate New Sale White-box thinking Understanding collaboration White-box sequence diagram for operation Compute Online Sale Flowdown to further levels Mdsd Create use case models at levels below the enterprise Model Driven Systems Development with Rational Products Understanding distribution of responsibility Localities and systems engineering LocalitiesMdsd Developing a locality model Locality semantics Connection semantics Descriptor diagrams For the design level Localities, services, and interfacesLocalities and nodes Design trades System locality view Example Sequence diagrams with localities Sequence diagram with localities Joint realization Joint realization diagram Joint realization tables DRF1 PRF1 LRF4 Raster Image Processing Logical view Distribution view Association of logical entities, localities, and interfaces Model Driven Systems Development with Rational Products Tool support for Mdsd Model structure Organizing an Mdsd model Level 0 model organization Project Level 1 model organization Mdsd UML Profile Level 2 and beyond model organization Stereotypes Mdsd Profile applied to the model Mdsd UML Profile stereotypes Levels of decomposition Two levels of a sample Mdsd model Actors Model with first level expanded Logical entities 10shows an example context diagram 11 Level 1 model structure Use cases and operations 13 Level 1 use case structure 15 Locality diagram Distribution entities 16 Joint realization diagram Automation Creating Mdsd artifacts UML diagrams for systems modelingPreparing the environment Preparing the Workbench 17 Workspace Launcher Create a new UML Modeling Project Select File → New → Project Name the new project Weather Tracking System 19 Create UML Project Select Window → Preferences Select Stereotype Style → Shape Image Installing the Mdsd plug-in 22 Preferences Shape Image Click New Local Site Figure Name the new site Mdsd Figure Select Mdsd as the only site, and click Finish Figure Create the system model Modeling the system as a black boxSelect Standard template 29 Create the Systems Model Create the context diagram Type Weather Tracking System and press Enter Click Apply Stereotypes Select Weather Tracking System in the diagramExpand 00 Enterprise Level → Actors → $Building Blocks 33 Copy $actor.name and find/replace 35 Drag an actor into the context diagram 37 Drag use case into the use case diagram Expand 00 Enterprise Level → Use Cases → $Building Blocks 38 Create an association in the use case diagram 39 Use case diagram 41shows the context diagram Repeat these steps to create the associations listed inTable Create black-box sequence diagram Expand 00 Enterprise Level → Actors → LocalForecaster 45 Drag actor into sequence diagram Select Create Message Figure Label the operation provide local weather data Figure Summary Modeling the system at levelIdentify systems that will collaborate at L1 Realize a system operation 52 Rename the use case Open the WB Sequence Diagram Expand 01 System Level → Logical Elements Name the operation provide local weather data Figure Repeat these steps to create the messages listed in Table Creating a localities diagram 58 White-box sequence diagram with messages Create associations Click Apply Stereotypes Select connection From Stereotype Summary Model Driven Systems Development with Rational Products Mdsd and SysML 143 Introduction Mdsd RUP SE as contributor to SysML Basics of SysML Comparison of SysML1.0 with UML2.0 Areas of focus of SysML Requirements modeling Mdsd and SysML Model Driven Systems Development with Rational Products Mdsd and SysML Block definition diagram Block semantics Mdsd and SysML Example of requirement allocation Internal block diagram Ports Model Driven Systems Development with Rational Products Mdsd and SysML SysML Block Definition Diagram to type ports Constraints Mdsd and SysML Parametrics Parametric diagram for the windshield Behavior modeling Blocks as basic structural units Using blocks to stand for systemsMdsd with SysML Understanding context 11 Context diagram with blocks and associations 12 Context diagram with blocks and ports Requirements and understanding context Understanding collaborations 15 SysML interaction diagram 16 SysML joint allocation diagram Understanding distribution of responsibilities Parametrics Model Driven Systems Development with Rational Products 18 Requirements diagram for radar R4 varies by P x a x T 20 Simplified Radar Power and Range parametric diagram Summary of SysML basics Mdsd and SysML Model Driven Systems Development with Rational Products 175 What is systems engineering? Why we build systemsSystems engineering Systems concerns Main concern Subordinate concern How does Mdsd fit in? Conclusion Model Driven Systems Development with Rational Products Appendix A. Mdsd use case specification template 181 Model Driven Systems Development with Rational Products Revision History Document Approval Table of Contents Brief Description Use-Case Specification Use-Case NameActor Catalog Basic Flow of Events PreconditionsPostconditions Precondition One Flow of Event Formats Alternative Flows Area of Functionality Na First Alternative Flow S1 First Subflow SubflowsAnother Area of Functionality S2 Second Subflow Additional Information Extension PointsSpecial Requirements Name of Extension Point Model Driven Systems Development with Rational Products Locating the Web material 193 Using the Web material Abbreviations and acronyms 195 Model Driven Systems Development with Rational Products Other publications IBM Redbooks publications197 Online resources How to get IBM RedbooksHelp from IBM Index 199 Incose Stereotype 107 Logical Architecture RMC Information Page Model Driven Systems Development with Rational Products Page Page Model Driven Systems Development with Rational Products

Top Page Image Contents