간편결제, 신용카드 청구할인
인터파크 롯데카드 5% (65,550원)
(최대할인 10만원 / 전월실적 40만원)
북피니언 롯데카드 30% (48,300원)
(최대할인 3만원 / 3만원 이상 결제)
NH쇼핑&인터파크카드 20% (55,200원)
(최대할인 4만원 / 2만원 이상 결제)
Close

Mastering the Requirements Process [양장]

소득공제

2013년 9월 9일 이후 누적수치입니다.

공유하기
정가

69,000원

  • 69,000원

    2,070P (3%적립)

할인혜택
적립혜택
  • S-Point 적립은 마이페이지에서 직접 구매확정하신 경우만 적립 됩니다.
추가혜택
배송정보
  • 5/14(화) 이내 발송 예정  (서울시 강남구 삼성로 512)
  • 무료배송
주문수량
감소 증가
Mastering the Requirements Process

69,000원

절판으로 구매가 중지됩니다.
위로

  • 이벤트/기획전

  • 연관도서

  • 상품권

AD

이상품의 분류

목차

Preface to the Second Editionp. xxi
Foreword to the First Editionp. xxiii
Acknowledgmentsp. xxiv
What Are Requirements?p. 1
Requirements Gathering and Systems Modelingp. 3
Agile Software Developmentp. 4
Why Do I Need Requirements?p. 8
What Is a Requirement?p. 9
Functional Requirementsp. 9
Nonfunctional Requirementsp. 10
Constraintsp. 10
Evolution of Requirementsp. 11
The Templatep. 11
The Shellp. 14
The Volere Requirements Processp. 15
The Requirements Processp. 17
Agility Guidep. 19
Requirements Process in Contextp. 20
The Processp. 21
A Case Studyp. 21
Project Blastoffp. 22
Trawling for Requirementsp. 24
Prototyping the Requirementsp. 25
Scenariosp. 25
Writing the Requirementsp. 26
The Quality Gatewayp. 28
Reusing Requirementsp. 29
Reviewing the Specificationp. 29
Iterative and Incremental Processesp. 30
Requirements Retrospectivep. 31
Your Own Requirements Processp. 31
In Conclusionp. 33
Project Blastoffp. 35
Agility Guidep. 38
IceBreakerp. 38
Scope, Stakeholders, Goalsp. 40
Setting the Scopep. 40
Domains of Interestp. 42
First-Cut Work Contextp. 44
Stakeholdersp. 45
The Clientp. 47
The Customerp. 48
The Users: Get to Know Themp. 49
Other Stakeholdersp. 51
Consultantsp. 52
Managementp. 52
Subject Matter Expertsp. 52
Core Teamp. 52
Inspectorsp. 53
Market Forcesp. 53
Legalp. 53
Negative Stakeholdersp. 53
Industry Standard Settersp. 53
Public Opinionp. 53
Governmentp. 53
Special-Interest Groupsp. 54
Technical Expertsp. 54
Cultural Interestsp. 54
Adjacent Systemsp. 54
Finding the Stakeholdersp. 54
Goals: What Do You Want to Achieve?p. 55
Keeping Track of the Purposep. 59
Requirements Constraintsp. 60
Solution Constraintsp. 60
Project Constraintsp. 61
Naming Conventions and Definitionsp. 61
How Much Is This Going to Cost?p. 62
Risksp. 63
To Go or Not to Gop. 64
Blastoff Alternativesp. 65
Summaryp. 65
Event-Driven Use Casesp. 67
Agility Guidep. 67
Understanding the Workp. 67
Use Cases and Their Scopep. 69
The Workp. 70
The Context of the Workp. 70
The Outside Worldp. 72
Business Eventsp. 73
Time-Triggered Business Eventsp. 74
Why Business Events and Business Use Cases Are a Good Ideap. 75
Finding the Business Eventsp. 76
Business Use Casesp. 78
The Role of Adjacent Systemsp. 79
Active Adjacent Systemsp. 80
Autonomous Adjacent Systemsp. 83
Cooperative Adjacent Systemsp. 85
Business Use Cases and Product Use Casesp. 86
Actorsp. 89
Summaryp. 90
Trawling for Requirementsp. 93
Agility Guidep. 93
Responsibilityp. 94
The Requirements Analystp. 94
Trawling and Business Use Casesp. 96
The Role of the Current Situationp. 98
Apprenticingp. 101
Observing Structures and Patternsp. 103
Interviewing the Stakeholdersp. 104
Asking the Right Questionsp. 106
Getting to the Essence of the Workp. 107
Solving the Right Problemp. 109
Innovative Productsp. 110
Business Use Case Workshopsp. 113
Outcomep. 114
Scenariosp. 115
Business Rulesp. 115
Creativity Workshopsp. 116
Brainstormingp. 117
Personasp. 119
Mind Mapsp. 122
Wallpaperp. 124
Video and Photographsp. 124
Wikis, Blogs, and Discussion Forumsp. 125
Document Archeologyp. 126
Some Other Requirements-Gathering Techniquesp. 128
Family Therapyp. 128
Soft Systems and Viewpointsp. 129
Determining What the Product Should Bep. 129
The True Origin of the Business Eventp. 131
Does Technology Matter?p. 131
Choosing the Best Trawling Techniquep. 132
Summaryp. 134
Scenarios and Requirementsp. 135
Agility Guidep. 135
Scenariosp. 136
Normal Case Scenariosp. 140
Diagramming the Scenariop. 142
Alternative Casesp. 144
Exception Casesp. 145
What If? Scenariosp. 146
Misuse Cases and Negative Scenariosp. 147
Scenario Templatep. 148
Product Use Case Scenariosp. 150
Summaryp. 152
Functional Requirementsp. 155
Agility Guidep. 155
Functional Requirementsp. 157
Finding the Functional Requirementsp. 157
Level of Detail or Granularityp. 160
Exceptions and Alternativesp. 161
Avoiding Ambiguityp. 162
Technological Requirementsp. 164
Requirements, Not Solutionsp. 165
Grouping Requirementsp. 166
Alternatives to Functional Requirementsp. 167
Summaryp. 169
Nonfunctional Requirementsp. 171
Agility Guidep. 172
Nonfunctional Requirementsp. 173
Use Cases and Nonfunctional Requirementsp. 174
The Nonfunctional Requirementsp. 174
Look and Feel Requirements: Type 10p. 176
Usability and Humanity Requirements: Type 11p. 178
Performance Requirements: Type 12p. 182
Operational and Environmental Requirements: Type 13p. 184
Maintainability and Support Requirements: Type 14p. 186
Security Requirements: Type 15p. 187
Confidentialityp. 187
Availabilityp. 188
Integrityp. 188
Auditingp. 189
... And No Morep. 189
Cultural and Political Requirements: Type 16p. 190
Legal Requirements: Type 17p. 192
Sarbanes-Oxley Actp. 194
Other Legal Obligationsp. 194
Standardsp. 194
Finding the Nonfunctional Requirementsp. 195
Blogging the Requirementsp. 195
Use Casesp. 195
The Templatep. 197
Prototypes and Nonfunctional Requirementsp. 197
The Clientp. 198
Don't Write a Solutionp. 199
Summaryp. 201
Fit Criteriap. 203
Agility Guidep. 203
Why Does Fit Need a Criterion?p. 204
Scale of Measurementp. 206
Rationalep. 206
Fit Criteria for Nonfunctional Requirementsp. 208
Product Failure?p. 209
Subjective Testsp. 210
Look and Feel Requirementsp. 211
Usability and Humanity Requirementsp. 212
Performance Requirementsp. 213
Operational Requirementsp. 214
Maintainability Requirementsp. 215
Security Requirementsp. 215
Cultural and Political Requirementsp. 216
Legal Requirementsp. 216
Fit Criteria for Functional Requirementsp. 217
Test Casesp. 218
Use Cases and Fit Criteriap. 218
Fit Criterion for Project Purposep. 219
Fit Criteria for Solution Constraintsp. 219
Summaryp. 220
Writing the Requirementsp. 223
Agility Guidep. 223
Turning Potential Requirements into Written Requirementsp. 225
Knowledge Versus Specificationp. 225
The Volere Requirements Specification Templatep. 227
The Purpose of the Projectp. 229
The User Business or Background of the Project Effortp. 229
Goals of the Projectp. 230
The Client, the Customer, and Other Stakeholdersp. 232
The Clientp. 232
The Customerp. 233
Other Stakeholdersp. 233
Users of the Productp. 233
Mandated Constraintsp. 234
Solution Constraintsp. 235
Implementation Environment of the Current Systemp. 235
Partner or Collaborative Applicationsp. 236
Off-the-Shelf Softwarep. 236
Anticipated Workplace Environmentp. 236
Schedule Constraintsp. 236
Budget Constraintsp. 237
Naming Conventions and Definitionsp. 237
Definitions of All Terms, Including Acronyms, Used in the Projectp. 237
Data Dictionary for Any Included Modelsp. 238
Relevant Facts and Assumptionsp. 238
Factsp. 238
Assumptionsp. 239
The Scope of the Workp. 240
Work Partitioningp. 240
The Scope of the Productp. 241
Product Boundaryp. 241
Product Use Case Listp. 241
Individual Product Use Casesp. 241
The Shellp. 241
Snow Cardsp. 242
Automated Requirements Toolsp. 243
The Atomic Requirementsp. 243
Requirement Numberp. 244
Requirement Typep. 244
Event/Use Case Numberp. 244
Descriptionp. 245
Rationalep. 245
Originatorp. 245
Fit Criterionp. 245
Customer Satisfaction and Customer Dissatisfactionp. 246
Priorityp. 247
Conflictsp. 247
Supporting Materialsp. 248
Historyp. 248
Writing the Specificationp. 248
Functional Requirementsp. 249
Descriptionp. 250
Nonfunctional Requirementsp. 251
Project Issuesp. 252
Open Issuesp. 252
Off-the-Shelf Solutionsp. 253
New Problemsp. 254
Tasksp. 254
Migration to the New Productp. 254
Risksp. 254
Costsp. 255
User Documentation and Trainingp. 256
Waiting Roomp. 256
Ideas for Solutionsp. 257
Summaryp. 257
The Quality Gatewayp. 259
Agility Guidep. 260
Requirements Qualityp. 261
Using the Quality Gatewayp. 262
Testing Completenessp. 263
Are There Any Missing Components?p. 264
Meaningful to All Stakeholders?p. 265
Testing Traceabilityp. 265
Consistent Terminologyp. 267
Relevant to Purpose?p. 268
Testing the Fit Criterionp. 270
Viable within Constraints?p. 272
Requirement or Solution?p. 273
Customer Valuep. 274
Gold Platingp. 275
Requirements Creepp. 276
Requirements Leakagep. 278
Implementing the Quality Gatewayp. 279
Alternative Quality Gatewaysp. 280
Summaryp. 281
Prototyping the Requirementsp. 283
Agility Guidep. 285
Prototypes and Realityp. 286
Low-Fidelity Prototypesp. 288
High-Fidelity Prototypesp. 292
Storyboardsp. 294
Object Life Historyp. 296
The Prototyping Loopp. 297
Design and Buildp. 298
Testing in the User Environmentp. 299
Analyzing the Resultsp. 300
Summaryp. 301
Reusing Requirementsp. 303
What Is Reusing Requirements?p. 303
Sources of Reusable Requirementsp. 306
Requirements Patternsp. 307
Christopher Alexander's Patternsp. 308
A Business Event Patternp. 309
Context of Event Responsep. 310
Processing for Event Responsep. 311
Data for Event Responsep. 312
Forming Patterns by Abstractingp. 313
Patterns for Specific Domainsp. 314
Patterns Across Domainsp. 315
Domain Analysisp. 317
Trends in Reusep. 318
Reuse and Objectsp. 318
Reuse Is Now a Job?p. 318
Summaryp. 319
Reviewing the Specificationp. 321
Agility Guidep. 322
Reviewing the Specificationp. 323
Inspectionsp. 323
Find Missing Requirementsp. 324
Have All Business Use Cases Been Discovered?p. 325
Define the Scopep. 326
Identify Business Events and Non-Eventsp. 326
Model the Business Use Casep. 328
Define the Business Datap. 328
CRUD Checkp. 330
Check for Custodial Processesp. 331
Repeat Until Donep. 331
Customer Valuep. 332
Prioritizing the Requirementsp. 333
Prioritization Factorsp. 333
When to Prioritizep. 334
Requirement Priority Gradingp. 335
Prioritization Spreadsheetp. 335
Conflicting Requirementsp. 337
Ambiguous Specificationsp. 339
Risk Analysisp. 340
Project Driversp. 340
Project Constraintsp. 341
Functional Requirementsp. 341
Measure the Required Effortp. 342
Summaryp. 342
Whither Requirements?p. 345
Adapting the Processp. 345
What About Requirements Tools?p. 347
Mapping Tools to Purposep. 348
Publishing the Requirementsp. 350
Contractual Documentp. 351
Management Summaryp. 351
Marketing Summaryp. 352
User Reviewp. 352
Reviewing the Specificationp. 353
Requirements Traceabilityp. 353
Tracing a Business Eventp. 353
Dealing with Changep. 357
Changes in the Worldp. 358
Requirements Feedbackp. 358
Requirements Retrospectivep. 360
What to Look Forp. 360
Running the Retrospectivep. 360
Retrospective Reportp. 362
Your Notebookp. 363
The Endp. 363
Volere Requirements Process Modelp. 365
The Volere Requirements Process Modelp. 365
Making This Work for Youp. 366
Finding More Informationp. 367
Define Blastoff Objectives (Process Notes 1.1.1)p. 371
Plan Physical Arrangements (Process Notes 1.1.2)p. 371
Communicate with Participants (Process Notes 1.1.3)p. 372
Determine Project Purpose (Process Notes 1.2.1)p. 374
Determine the Work Context (Process Notes 1.2.2)p. 374
Do First-Cut Risk Analysis (Process Notes 1.2.3)p. 375
Identify the Stakeholders (Process Notes 1.2.4)p. 376
Partition the Context (Process Notes 1.2.5)p. 377
Consider Non-Events (Process Notes 1.2.6)p. 377
Determine Business Terminology (Process Notes 1.2.7)p. 377
Define Project Constraints (Process Notes 1.2.8)p. 378
Identify Domains of Interest (Process Notes 1.2.9)p. 378
Write Blastoff Report (Process Notes 1.3.1)p. 380
Review Blastoff Results (Process Notes 1.3.2)p. 380
Hold Follow-Up Blastoff (Process Notes 1.3.3)p. 381
Make Initial Estimate (Process Notes 1.3.4)p. 382
Review Current Situation (Process Notes 2.1.1)p. 385
Apprentice with the User (Process Notes 2.1.2)p. 385
Determine Essential Requirements (Process Notes 2.1.3)p. 386
Brainstorm the Requirements (Process Notes 2.1.4)p. 386
Interview the Users (Process Notes 2.1.5)p. 387
Do Document Archaeology (Process Notes 2.1.6)p. 388
Make Requirements Video (Process Notes 2.1.7)p. 389
Run Use Case Workshop (Process Notes 2.1.8)p. 389
Build Event Models (Process Notes 2.1.9)p. 390
Build Scenario Models (Process Notes 2.1.10)p. 391
Run Creativity Workshop (Process Notes 2.1.11)p. 391
Study the Adjacent Systems (Process Notes 2.2.1)p. 393
Define Use Case Boundary (Process Notes 2.2.2)p. 393
Gather Business Event Knowledge (Process Notes 2.3.1)p. 395
Choose Appropriate Trawling Techniques (Process Notes 2.3.2)p. 395
Ask Clarification Questions (Process Notes 2.4)p. 396
Identify Potential Requirements (Process Notes 3.1)p. 399
Identify Functional Requirements (Process Notes 3.2)p. 399
Identify Composite Requirements (Process Notes 3.3)p. 400
Formalize Requirement (Process Notes 3.4)p. 400
Formalize System Constraints (Process Notes 3.5)p. 400
Identify Nonfunctional Requirements (Process Notes 3.6)p. 401
Write Functional Fit Criteria (Process Notes 3.7)p. 401
Write Nonfunctional Fit Criteria (Process Notes 3.8)p. 402
Define Customer Value (Process Notes 3.9)p. 402
Identify Dependencies and Conflicts (Process Notes 3.10)p. 403
Review Requirement Fit Criteria (Process Notes 4.1)p. 405
Review Requirement Relevance (Process Notes 4.2)p. 406
Review Requirement Viability (Process Notes 4.3)p. 406
Identify Gold-Plated Requirements (Process Notes 4.4)p. 406
Review Requirement Completeness (Process Notes 4.5)p. 406
Plan the Prototype (Process Notes 5.1)p. 408
Build Low-Fidelity Prototype (Process Notes 5.2.1)p. 410
Build High-Fidelity Prototype (Process Notes 5.2.2)p. 410
Test High-Fidelity Prototype with Users (Process Notes 5.3.1)p. 413
Test Low-Fidelity Prototype with Users (Process Notes 5.3.2)p. 413
Identify New and Changed Requirements (Process Notes 5.3.3)p. 414
Evaluate Prototyping Effort (Process Notes 5.3.4)p. 414
Conduct Private Individual Reviews (Process Notes 6.1.1)p. 417
Conduct Separate Meetings with Groups (Process Notes 6.1.2)p. 417
Facilitator Reviews Facts (Process Notes 6.1.3)p. 417
Hold Retrospective Review Meeting (Process Notes 6.2.1)p. 420
Produce Retrospective Report (Process Notes 6.2.2)p. 420
Retrospective Report on Requirements Specificationp. 420
Identify Filtration Criteria (Process Notes 6.3.1)p. 423
Select Relevant Requirement Types (Process Notes 6.3.2)p. 423
Add New Filtration Criteria (Process Notes 6.3.3)p. 423
Identify Missing Requirements (Process Notes 7.1.1)p. 427
Identify Customer Value Ratings (Process Notes 7.1.2)p. 427
Identify Requirement Interaction (Process Notes 7.1.3)p. 428
Identify Prototyping Opportunity (Process Notes 7.1.4)p. 428
Find Missing Custodial Requirements (Process Notes 7.1.5)p. 429
Look for Likely Risks (Process Notes 7.2.1)p. 431
Quantify Each Risk (Process Notes 7.2.2)p. 431
Identify Estimation Input (Process Notes 7.3.1)p. 434
Estimate Effort for Events (Process Notes 7.3.2)p. 434
Estimate Requirements Effort (Process Notes 7.3.3)p. 435
Design Form of Specification (Process Notes 7.4.1)p. 437
Assemble the Specification (Process Notes 7.4.2)p. 437
Dictionary of Terms Used in the Requirements Process Modelp. 437
Volere Requirements Specification Templatep. 451
Contentsp. 451
Project Driversp. 451
Project Constraintsp. 451
Functional Requirementsp. 451
Nonfunctional Requirementsp. 451
Project Issuesp. 452
Preamblep. 452
Volerep. 452
Requirements Typesp. 453
Testing Requirementsp. 453
Requirements Shellp. 454
The Purpose of the Projectp. 454
The User Business or Background of the Project Effortp. 454
Goals of the Projectp. 455
The Client, the Customer, and Other Stakeholdersp. 456
The Clientp. 456
The Customerp. 456
Other Stakeholdersp. 457
Users of the Productp. 457
The Hands-On Users of the Productp. 457
Priorities Assigned to Usersp. 458
User Participationp. 459
Maintenance Users and Service Techniciansp. 459
Mandated Constraintsp. 460
Solution Constraintsp. 460
Implementation Environment of the Current Systemp. 461
Partner or Collaborative Applicationsp. 462
Off-the-Shelf Softwarep. 462
Anticipated Workplace Environmentp. 463
Schedule Constraintsp. 464
Budget Constraintsp. 465
Naming Conventions and Definitionsp. 465
Definitions of All Terms, Including Acronyms, Used in the Projectp. 465
Data Dictionary for Any Included Modelsp. 466
Relevant Facts and Assumptionsp. 467
Factsp. 467
Assumptionsp. 467
The Scope of the Workp. 468
The Current Situationp. 468
The Context of the Workp. 469
Work Partitioningp. 470
The Scope of the Productp. 472
Product Boundaryp. 472
Product Use Case Listp. 472
Individual Product Use Casesp. 473
Functional and Data Requirementsp. 473
Functional Requirementsp. 473
Data Requirementsp. 475
Look and Feel Requirementsp. 476
Appearance Requirementsp. 476
Style Requirementsp. 476
Usability and Humanity Requirementsp. 477
Ease of Use Requirementsp. 477
Personalization and Internationalization Requirementsp. 479
Learning Requirementsp. 479
Understandability and Politeness Requirementsp. 480
Accessibility Requirementsp. 481
Performance Requirementsp. 482
Speed and Latency Requirementsp. 482
Safety-Critical Requirementsp. 483
Precision or Accuracy Requirementsp. 484
Reliability and Availability Requirementsp. 484
Robustness or Fault-Tolerance Requirementsp. 485
Capacity Requirementsp. 485
Scalability or Extensibility Requirementsp. 486
Longevity Requirementsp. 486
Operational and Environmental Requirementsp. 487
Expected Physical Environmentp. 487
Requirements for Interfacing with Adjacent Systemsp. 487
Productization Requirementsp. 488
Release Requirementsp. 489
Maintainability and Support Requirementsp. 489
Maintenance Requirementsp. 489
Supportability Requirementsp. 490
Adaptability Requirementsp. 490
Security Requirementsp. 491
Access Requirementsp. 491
Integrity Requirementsp. 492
Privacy Requirementsp. 492
Audit Requirementsp. 493
Immunity Requirementsp. 493
Cultural and Political Requirementsp. 494
Cultural Requirementsp. 494
Political Requirementsp. 494
Legal Requirementsp. 495
Compliance Requirementsp. 495
Standards Requirementsp. 496
Open Issuesp. 496
Off-the-Shelf Solutionsp. 497
Ready-Made Productsp. 497
Reusable Componentsp. 497
Products That Can Be Copiedp. 498
New Problemsp. 498
Effects on the Current Environmentp. 498
Effects on the Installed Systemsp. 499
Potential User Problemsp. 499
Limitations in the Anticipated Implementation Environment That May Inhibit the New Productp. 499
Follow-Up Problemsp. 500
Tasksp. 500
Project Planningp. 500
Planning of the Development Phasesp. 501
Migration to the New Productp. 501
Requirements for Migration to the New Productp. 501
Data That Has to Be Modified or Translated for the New Systemp. 502
Risksp. 502
Costsp. 503
User Documentation and Trainingp. 504
User Documentation Requirementsp. 504
Training Requirementsp. 505
Waiting Roomp. 505
Ideas for Solutionsp. 506
Function Point Counti

책소개

Written by two internationally acclaimed experts on requirements, this text provides software engineers with the insights, techniques and templates to discover exactly what their customers desire for their systems.

저자소개

Robertson / Robertson [저] 신작알림 SMS신청
생년월일 -

해당작가에 대한 소개가 없습니다.

컴퓨터 분야에서 많은 회원이 구매한 책

    리뷰

    0.0 (총 0건)
    리뷰쓰기

    100자평

    작성시 유의사항

    평점
    0/100자
    등록하기

    100자평

    0.0
    (총 0건)

    판매자정보

    • 인터파크도서에 등록된 오픈마켓 상품은 그 내용과 책임이 모두 판매자에게 있으며, 인터파크도서는 해당 상품과 내용에 대해 책임지지 않습니다.

    상호

    (주)교보문고

    대표자명

    안병현

    사업자등록번호

    102-81-11670

    연락처

    1544-1900

    전자우편주소

    callcenter@kyobobook.co.kr

    통신판매업신고번호

    01-0653

    영업소재지

    서울특별시 종로구 종로 1(종로1가,교보빌딩)

    교환/환불

    반품/교환 방법

    ‘마이페이지 > 취소/반품/교환/환불’ 에서 신청 또는 1:1 문의 게시판 및 고객센터(1577-2555)에서 신청 가능

    반품/교환가능 기간

    변심 반품의 경우 출고완료 후 6일(영업일 기준) 이내까지만 가능
    단, 상품의 결함 및 계약내용과 다를 경우 문제점 발견 후 30일 이내

    반품/교환 비용

    변심 혹은 구매착오로 인한 반품/교환은 반송료 고객 부담
    상품이나 서비스 자체의 하자로 인한 교환/반품은 반송료 판매자 부담

    반품/교환 불가 사유

    ·소비자의 책임 있는 사유로 상품 등이 손실 또는 훼손된 경우
    (단지 확인을 위한 포장 훼손은 제외)

    ·소비자의 사용, 포장 개봉에 의해 상품 등의 가치가 현저히 감소한 경우
    예) 화장품, 식품, 가전제품(악세서리 포함) 등

    ·복제가 가능한 상품 등의 포장을 훼손한 경우
    예) 음반/DVD/비디오, 소프트웨어, 만화책, 잡지, 영상 화보집

    ·시간의 경과에 의해 재판매가 곤란한 정도로 가치가 현저히 감소한 경우

    ·전자상거래 등에서의 소비자보호에 관한 법률이 정하는 소비자 청약철회 제한 내용에 해당되는 경우

    상품 품절

    공급사(출판사) 재고 사정에 의해 품절/지연될 수 있음

    소비자 피해보상
    환불지연에 따른 배상

    ·상품의 불량에 의한 교환, A/S, 환불, 품질보증 및 피해보상 등에 관한 사항은 소비자분쟁해결 기준 (공정거래위원회 고시)에 준하여 처리됨

    ·대금 환불 및 환불지연에 따른 배상금 지급 조건, 절차 등은 전자상거래 등에서의 소비자 보호에 관한 법률에 따라 처리함

    (주)KG이니시스 구매안전서비스서비스 가입사실 확인

    (주)인터파크커머스는 회원님들의 안전거래를 위해 구매금액, 결제수단에 상관없이 (주)인터파크커머스를 통한 모든 거래에 대하여
    (주)KG이니시스가 제공하는 구매안전서비스를 적용하고 있습니다.

    배송안내

    • 교보문고 상품은 택배로 배송되며, 출고완료 1~2일내 상품을 받아 보실 수 있습니다.

    • 출고가능 시간이 서로 다른 상품을 함께 주문할 경우 출고가능 시간이 가장 긴 상품을 기준으로 배송됩니다.

    • 군부대, 교도소 등 특정기관은 우체국 택배만 배송가능합니다.

    • 배송비는 업체 배송비 정책에 따릅니다.

      • - 도서 구매 시 15,000원 이상 무료배송, 15,000원 미만 2,500원 - 상품별 배송비가 있는 경우, 상품별 배송비 정책 적용

    파워링크 광고

    신청하기