RISS 학술연구정보서비스

검색
다국어 입력

http://chineseinput.net/에서 pinyin(병음)방식으로 중국어를 변환할 수 있습니다.

변환된 중국어를 복사하여 사용하시면 됩니다.

예시)
  • 中文 을 입력하시려면 zhongwen을 입력하시고 space를누르시면됩니다.
  • 北京 을 입력하시려면 beijing을 입력하시고 space를 누르시면 됩니다.
닫기
    인기검색어 순위 펼치기

    RISS 인기검색어

      Embedded real-time systems

      한글로보기

      https://www.riss.kr/link?id=M296568

      • 저자
      • 발행사항

        Chichester ; New York : J. Wiley, c1993

      • 발행연도

        1993

      • 작성언어

        영어

      • 주제어
      • DDC

        004/.33 판사항(20)

      • ISBN

        0471935638 :

      • 자료형태

        단행본(다권본)

      • 발행국(도시)

        England

      • 서명/저자사항

        Embedded real-time systems / Jean Paul Calvez ; translators, Alan Wyche and Charles Edmundson.

      • 형태사항

        xxiii, 647 p. : ill. ; 24 cm.

      • 총서사항

        Wiley series in software engineering practice Wiley professional computing

      • 일반주기명

        Subtitle from cover: A specification and design methodology.
        Translation of: Spe>cification et conception des syste<mes.
        Includes bibliographical references and index.

      • 소장기관
        • 강원대학교 도서관 소장기관정보
        • 경기대학교 중앙도서관(수원캠퍼스) 소장기관정보
        • 경희대학교 국제캠퍼스 도서관 소장기관정보
        • 계명대학교 동산도서관 소장기관정보
        • 국립중앙도서관 국립중앙도서관 우편복사 서비스
        • 국립한국해양대학교 도서관 소장기관정보
        • 배재대학교 도서관 소장기관정보
        • 상명대학교 서울캠퍼스 도서관 소장기관정보
        • 서울대학교 중앙도서관 소장기관정보 Deep Link
        • 성균관대학교 삼성학술정보관 소장기관정보 Deep Link
        • 세종대학교 도서관 소장기관정보
        • 숙명여자대학교 도서관 소장기관정보
        • 아주대학교 도서관 소장기관정보
        • 용인대학교 도서관 소장기관정보
        • 원광대학교 중앙도서관 소장기관정보
        • 인하대학교 도서관 소장기관정보
        • 조선대학교 도서관 소장기관정보
        • 한국과학기술원(KAIST) 학술문화관 소장기관정보
        • 한국외국어대학교 글로벌캠퍼스 도서관 소장기관정보
        • 한국외국어대학교 서울캠퍼스 도서관 소장기관정보
        • 한남대학교 도서관 소장기관정보
        • 한양대학교 안산캠퍼스 소장기관정보
        • 한양대학교 중앙도서관 소장기관정보
        • 홍익대학교 중앙도서관 소장기관정보
      • 0

        상세조회
      • 0

        다운로드
      서지정보 열기
      • 내보내기
      • 내책장담기
      • 공유하기
      • 오류접수

      부가정보

      목차 (Table of Contents)

      • CONTENTS
      • PREFACE = xxiii
      • Part 1 : METHODOLOGY OVERVIEW
      • Ch 1 - INTRODUCTION = 3
      • 1.1 OBJECTIVES FOR A DEVELOPMENT = 4
      • CONTENTS
      • PREFACE = xxiii
      • Part 1 : METHODOLOGY OVERVIEW
      • Ch 1 - INTRODUCTION = 3
      • 1.1 OBJECTIVES FOR A DEVELOPMENT = 4
      • 1.2 DIFFICULTIES OF THE DESIGNER'S WORK = 4
      • 1.3 ADVANTAGES OF A METHODOLOGY = 6
      • 1.4 GENESIS OF THE MCSE METHODOLOGY = 7
      • 1.5 OBJECTIVE OF THIS BOOK = 9
      • Ch 2 - SYSTEMS CHARACTERISTICS = 13
      • 2.1 EVOLUTION OF IMPLEMENTATION TECHNIQUES AND METHODS = 13
      • 2.2 THE INDUSTRIAL DATA PROCESSING FIELD = 14
      • 2.3 EMBEDDED SYSTEMS = 16
      • 2.4 REAL-TIME SYSTEMS = 16
      • 2.5 SYSTEM QUALITIES = 18
      • 2.6 SYSTEM CATEGORIES = 18
      • Ch 3 - SYSTEM DEVELOPMENT LIFE CYCLE
      • 3.1 DEVELOPMENT CONTEXT = 22
      • 3.2 DEVELOPMENT PHASES = 24
      • 3.3 LIFE CYCLE MODELS = 26
      • 3.3.1 The "Waterfall" model = 26
      • 3.3.2 The V cycle = 27
      • 3.3.3 The "Spiral" model = 28
      • 3.3.4 The "Contractual" model = 29
      • 3.4 A FEW OBSERVATIONS = 29
      • 3.4.1 Phase overlapping = 29
      • 3.4.2 Cost of error correction = 31
      • 3.4.3 Productivity factors = 32
      • 3.4.4 Effort distribution = 33
      • 3.5 DEVELOPMENT OF AN ELECTRONIC SYSTEM = 34
      • 3.6 SCOPE OF MCSE = 36
      • Ch 4 - METHODOLOGY BASIS = 39
      • 4.1 TERMINOLOGY = 39
      • 4.1.1 Problem : definition, solution = 39
      • 4.1.2 Model and modeling = 40
      • 4.1.3 Method and methodology = 40
      • 4.2 DESIGN WORK CHARACTERIZATION = 40
      • 4.2.1 Design : a human activity = 40
      • 4.2.2 The design process = 42
      • 4.2.3 Refinement and abstraction = 43
      • 4.3 MAIN FEATURES OF A METHODOLOGY = 44
      • 4.3.1 Description model = 44
      • 4.3.2 Method and technique for each step = 45
      • 4.3.3 Solution models = 45
      • Ch 5 - MCSE OVERVIEW = 47
      • 5.1 DEVELOPMENT OF THE METHODOLOGY = 47
      • 5.2 THE DESCRIPTION MODEL = 49
      • 5.2.1 The functional model = 51
      • 5.2.2 The behavioral model = 52
      • 5.2.3 The executive model = 53
      • 5.2.4 Advantage of this model = 54
      • 5.3 THE DEVELOPMENT PROCESS = 55
      • 5.3.1 The specification step = 57
      • 5.3.2 The functional design step = 58
      • 5.3.3 The implementation specification step = 58
      • 5.3.4 The implementation step = 58
      • 5.4 MCSE CHARACTERISTICS = 59
      • Ch 6 - AN ILLUSTRATIVE EXAMPLE = 63
      • 6.1 REQUIREMENTS DEFINITION = 63
      • 6.1.1 Cruising speed control = 64
      • 6.1.2 Monitoring average speed = 65
      • 6.1.3 Monitoring fuel consumption = 65
      • 6.1.4 Maintenance = 65
      • 6.1.5 Complementary characteristics = 65
      • 6.2 SPECIFICATIONS = 66
      • 6.2.1 Modeling the environment = 66
      • 6.2.2 Functional specifications = 68
      • 6.2.3 Operational and technological specifications = 70
      • 6.3 FUNCTIONAL DESIGN = 73
      • 6.3.1 System delimitation = 73
      • 6.3.2 Initial functional structure = 74
      • 6.3.3 Refinement = 77
      • 6.3.4 Speed control function = 77
      • 6.3.5 Supervision function = 79
      • 6.3.6 Maintenance function = 81
      • 6.3.7 Time-generation function = 82
      • 6.4 IMPLEMENTATION SPECIFICATION = 82
      • 6.4.1 Interfaces introduction = 83
      • 6.4.2 Timing constraints analysis = 87
      • 6.4.3 Hardware / software distribution = 88
      • 6.4.4 Software specification = 89
      • 6.4.5 Hardware implementation specification = 90
      • 6.5 CONCLUSIONS : SOME REMARKS = 91
      • REFERENCES PART 1 = 93
      • Part 2 : MODELS AND METHODOLOGIES
      • Ch 7 - METHODOLOGIES SURVEY = 99
      • 7.1 METHODOLOGY CLASSIFICATION AND HSTORY = 100
      • 7.2 SADT = 102
      • 7.2.1 The model = 103
      • 7.2.2 The method = 104
      • 7.3 STRUCTURED ANALYSIS = 105
      • 7.3.1 The model = 105
      • 7.3.2 The method = 107
      • 7.4 STRUCTURED DESIGN = 108
      • 7.4.1 The mode = 108
      • 7.4.2 The method = 109
      • 7.4.3 Comments = 111
      • 7.5 JACKSON'S METHODOLOGY (JSD) = 111
      • 7.5.1 The models = 111
      • 7.5.2 The process = 113
      • 7.5.3 Comments = 117
      • 7.6 SREM = 118
      • 7.6.1 The model = 118
      • 7.6.2 The SREM method for specification = 119
      • 7.6.3 The SYSREM method for design = 119
      • 7.6.4 Comments = 121
      • 7.7 WARD AND MELLOR'S METHODOLOGY (SDRTS OR RTSA) = 122
      • 7.7.1 The model = 122
      • 7.7.2 The procedure = 123
      • 7.8 HATLEY AND PIRBHAI'S METHODOLOGY = 126
      • 7.8.1 The model = 126
      • 7.8.2 The process = 127
      • 7.9 LAVI AND HAREL'S METHODOLOGY (STATEMATE AS A TOOL) = 129
      • 7.9.1 The ECS (Embedded Computer Systems) model = 129
      • 7.9.2 The process = 132
      • 7.9.3 Comments = 132
      • 7.10 DARTS (DESIGN APPROACH FOR REAL-TIME SYSTEMS) = 132
      • 7.10.1 The DARTS model = 133
      • 7.10.2 The process = 134
      • 7.11 OBJECT-ORIENTED DESIGN (OOD) = 134
      • 7.11.1 The object model = 135
      • 7.11.2 Design process = 137
      • 7.12 SYSTEM DESIGN WITH MACHINE CHARTS = 140
      • 7.12.1 The model = 140
      • 7.12.2 The method = 141
      • 7.12.3 Comments = 144
      • 7.13 NIELSEN AND SHUMATES METHODOLOGY = 144
      • 7.13.1 The models = 144
      • 7.13.2 The design process = 144
      • 7.13.4 Comments = 146
      • 7.14 CONCLUSION = 146
      • Ch 8 - MODELS SURVEY = 149
      • 8.1 BASIS FOR MODEL ANALYSIS = 150
      • 8.1.1 Model qualities = 150
      • 8.1.2 Model classification = 150
      • 8.1.3 Analytic models = 151
      • 8.1.4 Conceptual models = 151
      • 8.2 OBJECTIVES OF MODELS FOR SYSTEMS = 153
      • 8.2.1 Modeling for specification = 153
      • 8.2.2 Modeling in design = 155
      • 8.3 MODELS SURVEY = 156
      • 8.3.1 Activities model = 156
      • 8.3.2 Data models = 156
      • 8.3.3 Function models = 158
      • 8.3.4 Behavior models = 160
      • 8.4 CONCLUSION THE MCSE MODELS = 164
      • REFERENCES PART 2 = 165
      • Part 3 : SYSTEM SPECIFICATION
      • Ch 9 - SYSTEM REQUIREMENTS = 177
      • 9.1 THE CUSTOMER : THE SOURCE OF THE NEED = 178
      • 9.2 THE DESIGNER : EXPERT IN THE IMPLEMENTATION FIELD = 178
      • 9.3 THE REQUIREMENTS DEFINITION : EXPRESSION OF THE NEED = 178
      • 9.4 CUSTOMERS WISHES = 179
      • 9.5 REQUIREMENTS DEFINITION PURPOSE AND IMPLICATION = 179
      • 9.6 REQUIREMENTS CONTENTS AND GUIDE = 181
      • 9.7 ANSWER TO A REQUIREMENTS DEFINITION = 182
      • 9.8 PROBLEM EXAMPLES = 183
      • 9.8.1 Centrifuge speed control system = 183
      • 9.8.2 Automation with a wire-guided trolley = 184
      • 9.9 SUMMARY = 187
      • Ch 10 - SYSTEM SPECIFICATIONS = 189
      • 10.1 SPECIFICATION ROLE = 190
      • 10.1.1 Distance between customer and designers = 190
      • 10.1.2 Diversity of customer partners = 190
      • 10.1.3 Importance of verification = 191
      • 10.1.4 A specification as a formal verifiable document = 192
      • 10.2 NATURE OF THE SPECIFICATION = 194
      • 10.3 SPECIFICATION CHARACTERISTICS = 195
      • 10.4 SPECIFICATION CONTENT GUIDELINES = 196
      • 10.5 SPECIFICATION WORK PROBLEMS = 197
      • 10.6 COMPETENCE FOR SPECIFYING = 198
      • 10.7 SUMMARY = 199
      • Ch 11 - MODELING CONCEPTS = 201
      • 11.1 WHAT MUST BE CHARACTERIZED? = 202
      • 11.2 CHARACTERIZATION NATURE : MODELING = 204
      • 11.3 ENTITY MODELING = 204
      • 11.3.1 Nature of an entity = 205
      • 11.3.2 Nature of characteristic elements = 205
      • 11.3.3 Dependency between characteristic elements = 206
      • 11.3.4 Nature of inputs and outputs = 207
      • 11.4 THREE VIEWS FOR AN ENTITY DESCRIPTION = 207
      • 11.5 DATA / INFORMATION MODELING = 209
      • 11.5.1 Two-level models = 209
      • 11.5.2 Model for the data entity description = 210
      • 11.5.3 Relation description model = 213
      • 11.5.4 Data modeling technique = 214
      • 11.6 BEHAVIOR MODELING = 215
      • 11.6.1 The various discrete state models = 215
      • 11.6.2 State modeling technique = 217
      • 11.6.3 Stimuli / response modeling technique = 219
      • 11.6.4 Recommended rules for the finite state behavior model = 220
      • 11.7 ACTIVITY MODELING = 222
      • 11.8 MODELING GUIDE = 226
      • 11.9 SUMMARY = 228
      • Ch 12 - THE SPECIFICATION PROCESS = 231
      • 12.1 SPECIFICATION COMPONENTS = 232
      • 12.2 SPECIFICATION PROCESS DESCRIPTION = 233
      • 12.3 ENVIRONMENT ANALYSIS AND MODELING = 235
      • 12.3.1 Modeling each entity = 235
      • 12.3.2 Functional environment description = 238
      • 12.4 DELIMITATION OF SYSTEM INPUTS AND OUTPUTS = 240
      • 12.5 EXAMPLE 1 : CENTRIFUGE SPEED CONTROL = 240
      • 12.6 FUNCTIONAL SPECIFICATIONS = 242
      • 12.6.1 Nature of functional specifications = 242
      • 12.6.2 Approaches for producing a functional specification = 243
      • 12.6.3 Functional specification method = 249
      • 12.6.4 Examples = 251
      • 12.7 OPERATIONAL SPECIFICATIONS = 252
      • 12.8 TECHNOLOGICAL SPECIFICATIONS = 253
      • 12.9 INSTALLATION AND OPERATING PROCEDURES = 256
      • 12.10 EXAMPLE 2 : WIRE-GUIDED TROLLEY AUTOMATION = 257
      • 12.10.1 Modeling the environment = 257
      • 12.10.2 System specifications = 259
      • 12.11 SPECIFICATION VERIFICATION AND VALIDATION = 262
      • 12.11.1 The participants = 261
      • 12.11.2 Scheduling work and reviews = 262
      • 12.12 SPECIFICATION CHARACTERISTICS = 263
      • 12.13 SUMMARY = 264
      • REFERENCES PART 3 = 265
      • Part 4 : FUNCTIONAL DESIGN
      • Ch 13 - THE FUNCTIONAL MODEL = 271
      • 13.1 FUNCTIONAL MODEL COMPONENTS = 271
      • 13.2 THE FUNCTIONAL STRUCTURE MODEL = 273
      • 13.2.1 Graphical representation = 273
      • 13.2.2 FS coherence and understandability = 275
      • 13.2.3 Interpretation of an FS = 276
      • 13.2.4 Refinement and abstraction of an FS = 279
      • 13.2.5 Maximum decomposition : elementary functions or actions = 280
      • 13.2.6 Behavior rules for an elementary function = 281
      • 13.2.7 Functional structure properties = 284
      • 13.3 ELEMENTARY FUNCTION SPECIFICATION = 285
      • 13.3.1 Specification objectives = 285
      • 13.3.2 Description languages choke = 286
      • 13.3.3 The description model = 287
      • 13.3.4 Model interpretation = 292
      • 13.4 DATA SPECIFICATION = 293
      • 13.4.1 Data specification objectives = 293
      • 13.4.2 Description model = 294
      • 13.4.3 Data categories : structures = 295
      • 13.4.4 Data decomposition : minimization and standardization = 297
      • 13.4.5 Use of data = 298
      • 13.5 GLOBAL FUNCTIONAL MODEL PROPERTIES = 299
      • 13.6 SUMMARY = 301
      • Ch 14 - DESIGN PRINCIPLES = 303
      • 14.1 SUBJECT-ORIENTED DESIGN = 304
      • 14.2 TECHNOLOGY INDEPENDENT DESIGN = 305
      • 14.2.1 Interface functions with the physical environment = 306
      • 14.2.2 Man-machine dialog functions = 307
      • 14.2.3 Geographic distribution = 307
      • 14.2.4 Maintenance, operating safety = 309
      • 14.2.5 Importance of specification categories = 309
      • 14.3 MINIMUM COMPLEXITY AND INDEPENDENCE = 310
      • 14.3.1 Orthogonality or function coherence = 310
      • 14.3.2 Reducing couplings = 311
      • 14.4 SOLUTION DEDUCTION PROCEDURE = 311
      • 14.4.1 Analysis rather than intuition = 311
      • 14.4.2 Data-oriented approach rather than function-oriented approach = 312
      • 14.4.3 Refinement rather than abstraction = 313
      • 14.5 VERTICAL OR HORIZONTAL DECOMPOSITION = 314
      • 14.6 SOLUTION TEMPLATE MODELS = 315
      • 14.7 SUMMARY = 317
      • Ch 15 - THE FUNCTIONAL DESIGN PROCESS = 319
      • 15.1 OVERVIEW OF THE DESIGN PROCESS = 320
      • 15.2 INPUT AND OUTPUT DOCUMENTS FOR THE DESIGN STEP = 322
      • 15.2.1 Specification document = 322
      • 15.2.2 Design document = 322
      • 15.3 FUNCTIONAL INPUT AND OUTPUT DELIMITATION = 323
      • 15.3.1 Process = 323
      • 15.3.2 Example 1 : Centrifuge speed control system = 324
      • 15.3.3 Example 2 : Automation with a wire-guided trolley = 326
      • 15.4 SEARCH FOR AN INITIAL FUNCTIONAL DECOMPOSITION = 328
      • 15.4.1 Importance of the first functional decomposition = 328
      • 15.4.2 Decomposition process = 329
      • 15.4.3 Example 1 : centrifuge speed control system = 331
      • 15.4.4 Example 2 : automation with a wine-guided trolley = 332
      • 15.5 FUNCTIONAL REFINEMENT = 333
      • 15.5.1 Refinement stop criterion = 334
      • 15.5.2 Refinement process = 334
      • 15.5.3 Example 1 : centrifuge speed control system = 334
      • 15.5.4 Example 2 : Automation with a wire-guided trolley = 335
      • 15.6 BEHAVIOR OF ELEMENTARY FUNCTIONS = 337
      • 15.6.1 Method of obtaining an algorithmic description = 337
      • 15.6.2 Example 1 : centrifuge speed control system = 339
      • 15.6.3 Example 2 : automation with a wine-guided trolley = 341
      • 15.7 DATA DESCRIPTION = 343
      • 15.7.1 Data description method = 343
      • 15.7.2 Illustration by an example = 344
      • 15.8 SOLUTION EVALUATION CRITERIA = 347
      • 15.8.1 Coupling analysis = 347
      • 15.8.2 Coherence analysis = 347
      • 15.8.3 Complexity analysis = 348
      • 15.8.4 Solution understandability = 348
      • 15.9 DOCUMENTATION = 349
      • 15.10 SUMMARY = 349
      • Ch 16 - TEMPLATE MODELS FOR DESIGN = 351
      • 16.1 TEMPLATE MODELS ROLE AND BENEFIT = 352
      • 16.2 CONTROLLER / PROCESS MODEL = 352
      • 16.2.1 Principle = 352
      • 16.2.2 The model = 353
      • 16.2.3 The method = 354
      • 16.2.4 Example = 354
      • 16.3 SUPERVISION / CONTROL MODEL = 356
      • 16.3.1 Principle = 356
      • 16.3.2 The model = 357
      • 16.3.3 The method = 358
      • 16.3.4 Examples = 358
      • 16.4 CLIENT / SERVER MODEL = 359
      • 16.4.1 Principle = 359
      • 16.4.2 The model = 359
      • 16.4.3 The method = 360
      • 16.4.4 Example : message transmission through a serial link = 361
      • 16.5 INTERACTIVITY MODEL = 362
      • 16.5.1 Principle = 362
      • 16.5.2 The model = 363
      • 16.5.3 The method = 365
      • 16.5.4 Example = 365
      • 16.5.5 Generalization of the model for a multi-window environment = 367
      • 16.6 SUMMARY = 367
      • REFERENCES PART 4 = 369
      • Part 5 : IMPLEMENTATION SPECIFICATION
      • Ch 17 - THE EXECUTIVE MODEL = 373
      • 17.1 EXECUTIVE MODEL CHARACTERISTICS = 373
      • 17.1.1 The executive model and is constituents = 374
      • 17.1.2 Meaning of elements and relations = 375
      • 17.2 THE EXECUTIVE MODEL = 377
      • 17.2.1 Graphical representation = 377
      • 17.2.2 Interpretation of an ES = 379
      • 17.2.3 Executive structure refinement and abstraction = 380
      • 17.3 SPECIFICATION OF COMPONENTS FOR THE IMPLEMENTATION = 381
      • 17.3.1 Processor specification = 382
      • 17.3.2 Memory specification = 383
      • 17.3.3 Communication node specification = 383
      • 17.4 PROPERTIES OF THE EXECUTIVE MODEL = 383
      • 17.5 SUMMARY = 384
      • Ch 18 - THE INTEGRATION MODEL = 387
      • 18.1 THE INTEGRATION MODEL AND ITS COMPONENTS = 387
      • 18.2 THE ALLOCATION MODEL = 388
      • 18.2.1 Correspondence between elements in the two structures = 389
      • 18.2.2 Allocation constraints = 390
      • 18.3 THE SOFTWARE IMPLEMENTATION MODEL FOR EACH PROCESSOR = 393
      • 18.3.1 Task implementation model = 393
      • 18.3.2 Implementation of each task = 396
      • 18.3.3 Specification of each element = 396
      • 18.4 SOME RULES FOR DEDUCING A SOFTWARE IMPLEMENTATION = 397
      • 18.4.1 Function → Task correspondence = 397
      • 18.4.2 Translation of relations by variable sharing = 397
      • 18.4.3 Translation of synchronizations by event = 398
      • 18.4.4 Translation for message transfers = 399
      • 18.5 IMPLEMENTATION WITH OR WITHOUT A REAL-TIME EXECUTIVE = 401
      • 18.5.1 Implementation without real-time executive = 402
      • 18.5.2 Implementation with a real-time executive = 403
      • 18.5.3 Software implementation technique selection criteria = 405
      • 18.6 INTEGRATION MODEL CHARACTERISTICS = 406
      • 18.7 SUMMARY = 407
      • Ch 19 - THE IMPLEMENTATION SPECIFICATION PROCESS = 409
      • 19.1 OBJECTIVES TO BE ACHIEVED = 410
      • 19.1.1 Hardware specifications = 410
      • 19.1.2 Timing constraints = 411
      • 19.1.3 Reducing development costs = 411
      • 19.1.4 Reducing the organizational part = 412
      • 19.1.5 Quality rules = 413
      • 19.1.6 Contradictory objectives = 413
      • 19.2 PRESENTATION OF THE IMPLEMENTATION PROCESS = 414
      • 19.3 INTRODUCTING GEOGRAPHIC DISTRIBUTION CONSTRAINTS = 415
      • 19.4 INTRODUCTING INTERFACES = 418
      • 19.4.1 Template model for introducing interfaces = 418
      • 19.4.2 Introducing physical interfaces = 419
      • 19.4.3 Introducing man-machine interfaces = 421
      • 19.4.4 Example 1 : centrifuge speed control system = 422
      • 19.4.5 Example 2 : automation with a wire-guided trolley = 427
      • 19.5 CONSTRAINTS FOR AN EXECUTIVE STRUCTURE = 429
      • 19.5.1 Evaluation of timing constraints = 430
      • 19.5.2 Techniques for deducing an executive structure = 436
      • 19.6 DETERMINATION OF THE EXECUTIVE STRUCTURE = 437
      • 19.6.1 Choice of the hardware / software distribution = 437
      • 19.6.2 Example l : Centrifuge speed control system = 438
      • 19.6.3 Example 2 : automation with a wire-guided trolley = 439
      • 19.7 SOFTWARE IMPLEMENTATION DIAGRAM FOR EACH PROCESSOR = 441
      • 19.7.1 Translating a temporal dependence between two actions = 441
      • 19.7.2 Example l : Centrifuge speed control system = 442
      • 19.7.3 Example 2 : a wine-guided trolley automation = 444
      • 19.7.4 Implementation of an action sequence = 445
      • 19.7.5 Implementation of a looped action sequence = 445
      • 19.7.6 Implementation of several action sequences = 446
      • 19.7.7 Port capacity = 446
      • 19.7.8 Using the services of a processor = 447
      • 19.7.9 Module implementation = 448
      • 19.8 IMPLEMENTATION OF DATA = 449
      • 19.8.1 Data Implementation criteria = 449
      • 19.8.2 Implementation for structured data = 451
      • 19.8.3 Implementation for collections and relations = 451
      • 19.9 HARDWARE IMPLEMENTATION SPECIFICATION = 452
      • 19.9.1 Example l : Centrifuge speed control system = 453
      • 19.9.2 Example 2 : automation with a wire-guided trolley = 453
      • 19.9.3 Coupling between processors = 454
      • 19.10 SOLUTION DOCUMENTATION AND CHARACTERISTICS = 456
      • 19.11 SUMMARY = 457
      • REFERENCES PART 5 = 459
      • Part 6 : IMPLEMENTATION
      • Ch 20 - THE IMPLEMENTATION PROCESS = 463
      • 20.1 IMPLEMENTATION OBJECTIVE = 463
      • 20.1.1 Implementation step characterization = 464
      • 20.1.2 Variety of implementation methods and too1s = 465
      • 20.1.3 Time involved in the implementation step = 467
      • 20.2 IMPLEMENTATION STEPS = 468
      • 20.3 SPECIFICATION VERIFICATION AND ACCEPTANCE = 469
      • 20.4 HARDWARE IMPLEMENTATION = 470
      • 20.4.1 Process = 470
      • 20.4.2 The tools = 471
      • 20.4.3 Rules to be respected = 471
      • 20.5 SOFTWARE IMPLEMENTATION = 472
      • 20.5.1 Process = 472
      • 20.5.2 The tools = 472
      • 20.5.3 Rules to be respected = 473
      • 20.5.4 Error processing = 474
      • 20.6 INTEGRATION AND TEST = 475
      • 20.7 SOURCES OF ERRORS = 476
      • 20.8 REFINEMENT DURING IMPLEMENTATION = 477
      • 20.8.1 Hardware implementation refinement = 477
      • 20.8.2 Software implementation refinement = 478
      • 20.9 ADVANTAGE OF REUSE = 479
      • 20.10 SUMMARY = 479
      • Ch 21 - HARDWARE IMPLEMENTATION TECHNIQUES = 481
      • 21.1 IMPLEMENTATION SEARCH METHOD = 481
      • 21.2 IMPLEMENTATION TECHNIQUES = 482
      • 21.2.1 Implementation with existing components = 482
      • 21.2.2 Development of specific components = 483
      • 21.3 VERIFICATION AND VALIDATION OF AN IMPLEMENTATION = 485
      • 21.3.1 Functional test = 485
      • 21.3.2 Manufacturing test = 486
      • 21.4 REUSABILITY FOR HARDWARE = 487
      • 21.5 TEMPLATE MODELS FOR IMPLEMENTATION = 488
      • 21.6 THE MOORE'S MACHINE MODEL = 489
      • 21.6.1 The principle = 489
      • 21.6.2 The model = 490
      • 21.6.3 Method = 491
      • 21.7 THE CONTROL / EXECUTION MODEL = 493
      • 21.7.1 Principle = 493
      • 21.7.2 Model = 494
      • 21.7.3 Method = 497
      • 21.8 SUMMARY = 498
      • Ch 22 - SOFTWARE IMPLEMENTATION TECHNIQUES = 501
      • 22.1 FUNCTIONALITY LEVELS AND PROCEDURES = 502
      • 22.1.1 Functionality levels = 502
      • 22.1.2 Implementation processes = 503
      • 22.2 REUSABILITY FOR SOFTWARE = 505
      • 22.3 DEVELOPMENT PRINCIPLES = 506
      • 22.3.1 Qualities = 507
      • 22.3.2 Characteristics = 507
      • 22.3.3 Principles = 507
      • 22.4 TECHNIQUES FOR INDUSTRIAL DATA PROCESSING APPLICATIONS = 508
      • 22.5 DIRECT IMPLEMENTATION = 510
      • 22.6 USE OF A REAL-TIME EXECUTIVE = 510
      • 22.7 USE OF THE ADA LANGUAGE = 512
      • 22.7.1 The rendez-vous mechanism = 512
      • 22.7.2 Implementation of functional model relations = 513
      • 22.7.3 Interrupts and exceptions = 514
      • 22.8 USE OF THE OCCAM LANGUAGE AND THE TRANSPUTER = 516
      • 22.8.1 The exchange mechanism by channel = 516
      • 22.8.2 Implementing the functional model relations = 518
      • 22.9 SERVICES FOR THE FUNCTIONAL MODEL = 520
      • 22.10 OBJECT-ORIENTED IMPLEMENTATION = 522
      • 22.10.1 Object categories = 523
      • 22.10.2 MCSE and object-oriented design = 524
      • 22.10.3 MCSE for object identification = 525
      • 22.10.4 Structuring with object programming = 529
      • 22.11 SUMMARY = 530
      • REFERENCES PART 6 = 533
      • Part 7 : PROJECT MANAGEMENT
      • Ch 23 - THE PROJECT MANAGEMENT PROCESS = 539
      • 23.1 PRESENTATION OF THE PROBLEM = 540
      • 23.1.1 Modeling a development step = 540
      • 23.1.2 Entropy types = 541
      • 23.1.3 Causes of entropy = 542
      • 23.2 MANAGEMENT ORGANIZATION = 545
      • 23.3 PLANNING = 546
      • 23.3.1 Objectives = 546
      • 23.3.2 Principles = 547
      • 23.4 PLANNING TECHNIQUES = 547
      • 23.5 ORGANIZATION = 549
      • 23.6 STAFFING = 550
      • 23.7 PROJECT DIRECTING = 550
      • 23.8 CONTROL = 551
      • Ch 24 - PROJECT PLANNING AND COST = 553
      • 24.1 EXECUTION CONSTRAINTS FOR EACH STEP = 554
      • 24.1.1 Specification step = 554
      • 24.1.2 Design step = 555
      • 24.1.3 Implementation specification step = 556
      • 24.1.4 Implementation step = 557
      • 24.2 TOTAL PROJECT DURATION = 558
      • 24.3 SCHEDULE OPTIMIZATION = 559
      • 24.4 METHOD OR NO METHOD = 560
      • 24.5 PROJECT COST ESTIMATE = 561
      • Ch 25 - PROJECT VERIFICATION AND VALIDATION = 563
      • 25.1 TERMINOLOGY = 563
      • 25.2 OBJECTIVES = 564
      • 25.3 ERROR TYPES = 565
      • 25.4 NATURE OF VERIFICATIONS = 566
      • 25.5 DESIGN METHODS = 568
      • 25.5.1 Design review technique = 568
      • 25.5.2 Simulation / modeling as evaluation tool = 569
      • 25.6 IMPLEMENTATION PHASE METHODS = 569
      • 25.6.1 Static analysis = 570
      • 25.6.2 Dynamic analysis = 570
      • 25.6.3 Test procedure = 570
      • 25.7 INTEGRATION TECHNIQUES = 571
      • 25.7.1 Assembly by phase = 571
      • 25.7.2 Incremental assembly = 571
      • 25.7.3 Objective oriented tests = 572
      • 25.7.4 Comments on these procedures = 573
      • 25.8 TEST ENVIRONMENT = 573
      • 25.9 AUTOMATIC TESTS = 573
      • 25.10 TEST PLANNING = 574
      • 25.11 TEST SPECIFICATION GUIDE = 575
      • 25.12 GUIDE FOR A TEST DOCUMENT = 576
      • 25.12.1 General information = 576
      • 25.12.2 Plan = 576
      • 25.12.3 Test specification = 577
      • 25.12.4 Test evaluation = 577
      • 25.12.5 Description of tests = 577
      • Ch 26 - MAINTENANCE = 579
      • 26.1 MAINTENANCE TYPES = 580
      • 26.2 CAUSES OF MAINTENANCE = 580
      • 26.2.1 Quality of the developed product = 581
      • 26.2.2 Documentation = 582
      • 26.2.3 Users = 582
      • 26.2.4 Personnel = 582
      • 26.3 MAINTENANCE PROCEDURES = 583
      • 26.3.1 Alternative : maintenance / new design = 584
      • 26.3.2 Change control method = 584
      • 26.4 SOLUTIONS FOR IMPROVING MAINTENANCE = 585
      • 26.5 MAINTENANCE TOOLS = 586
      • 26.6 MAINTENANCE OF MAINTENANCE = 586
      • 26.6.1 Objective and activities = 586
      • 26.6.2 Maintenance rules = 587
      • 26.6.3 Team management = 587
      • Ch 27 - PROJECT DOCUMENTATION = 589
      • 27.1 FUNCTIONAL JUSTIFICATION = 590
      • 27.2 DOCUMENT STRUCTURE = 591
      • 27.2.1 Document hierarchy = 591
      • 27.2.2 Preliminary documents = 592
      • 27.2.3 Control documents = 592
      • 27.2.4 Specification, design, implementation and test documents = 594
      • 27.2.5 Manuals = 595
      • 27.2.6 Maintenance document = 596
      • 27.3 DOCUMENTATION PLANNING = 596
      • 27.4 DOCUMENTATION PROCEDURES = 597
      • 27.4.1 Problems and causes = 597
      • 27.4.2 Documentation quality levels = 598
      • 27.4.3 Procedures = 598
      • 27.5 DOCUMENT PRODUCTION GUIDE = 600
      • 27.5.1 Faults in a document = 600
      • 27.5.2 Writing principles = 601
      • 27.5.3 Writing user manuals = 602
      • Ch 28 - QUALITY MANAGEMENT = 603
      • 28.1 TERMINOLOGY = 604
      • 28.2 PRINCIPLE FOR OBTAINING QUALITY = 605
      • 28.3 QUALITY CRITERIA = 605
      • 28.4 QUALITY FACTORS OR ATTRIBUTES = 607
      • 28.5 QUALITY MEASUREMENT = 607
      • 28.6 METHOD = 608
      • 28.7 QUALITY VERIFICATION = 609
      • REFERENCES PART 7 = 611
      • Part 8 : CONCLUSION AND PERSPECTIVES
      • Ch 29 - METHODOLOGY CONTRIBUTION = 615
      • 29.1 THE DESIGNER'S TOOL BOX = 615
      • 29.2 FIELDS OF USE = 616
      • 29.3 PROJECTOR ORGANIZATION = 616
      • 29.4 DISTRIBUTION OF COMPETENCES = 617
      • 29.5 DEVELOPMENT GUIDE = 618
      • 29.6 PROJECT DOCUMENTATION = 620
      • 29.7 DIFFICULT ASPECTS OF DESIGN = 621
      • 29.8 LONG LIFE OF THE METHODOLOGY = 622
      • Ch 30 - REQUIREMENTS FOR A COMPUTER-AIDED SYSTEM ENGINEERING TOOL = 623
      • 30.1 OBJECTIVES = 624
      • 30.2 NEEDED FUNCTIONALITIES = 625
      • 30.2.1 Description = 625
      • 30.2.2 Documentation = 626
      • 30.2.3 Verification, validation = 626
      • 30.2.4 Production = 627
      • 30.2.5 Project and version management = 629
      • 30.2.6 Project management = 629
      • 30.3 SYNTHESIS OF FUNCTIONALITIES = 630
      • 30.4 TOOL STRUCTURE AND CHARACTERISTICS = 630
      • 30.5 TOOL ANALYSIS GUIDE = 632
      • Ch 31 - REALITIES AND PERSPECTIVES = 635
      • 31.1 THE DESIGNER'S ABILITY = 636
      • 31.2 THE ORGANIZATION RESPONSIBILITIES = 637
      • 31.3 LONG-TERM PERSPECTIVES = 637
      • REFERENCES PART 8 = 641
      • INDEX = 643
      더보기

      분석정보

      View

      상세정보조회

      0

      Usage

      원문다운로드

      0

      대출신청

      0

      복사신청

      0

      EDDS신청

      0

      동일 주제 내 활용도 TOP

      더보기

      이 자료와 함께 이용한 RISS 자료

      나만을 위한 추천자료

      해외이동버튼