Manuals / IBM / Fitness & Sports / Fitness Equipment

IBM SG24-7368-00 manual Index

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 9

Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 199

Contents vii

Image 9

IBM SG24-7368-00 manual Index

Related pages Troubleshooting for Samsung SCD22 Common specifications for GE C11 About the Indicator Lights for Sony VGN-S100 PCB Diagrams for Sharp SGH-F250 Sound changes when I connect my headphones for Onkyo SR308 Installation Instructions for Miele G 7804 Parts List for Desa FPVF33PR Remote Control Operation/Code List for Panasonic TQB2AA0756 Cleaning for Mitsubishi Electronics CP3020DAE Milyen alkatrészeket kell ellenőrizni a mosógép beüzemelése előtt?

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