>| The Process | p. 21 |
| A Case Study | p. 21 |
| Project Blastoff | p. 22 |
| Trawling for Requirements | p. 24 |
| Prototyping the Requirements | p. 25 |
| Scenarios | p. 25 |
| Writing the Requirements | p. 26 |
| The Quality Gateway | p. 28 |
| Reusing Requirements | p. 29 |
| Reviewing the Specification | p. 29 |
| Iterative and Incremental Processes | p. 30 |
| Requirements Retrospective | p. 31 |
| Your Own Requirements Process | p. 31 |
| In Conclusion | p. 33 |
| Project Blastoff | p. 35 |
| Agility Guide | p. 38 |
| IceBreaker | p. 38 |
| Scope, Stakeholders, Goals | p. 40 |
| Setting the Scope | p. 40 |
| Domains of Interest | p. 42 |
| First-Cut Work Context | p. 44 |
| Stakeholders | p. 45 |
| The Client | p. 47 |
| The Customer | p. 48 |
| The Users: Get to Know Them | p. 49 |
| Other Stakeholders | p. 51 |
| Consultants | p. 52 |
| Management | p. 52 |
| Subject Matter Experts | p. 52 |
| Core Team | p. 52 |
| Inspectors | p. 53 |
| Market Forces | p. 53 |
| Legal | p. 53 |
| Negative Stakeholders | p. 53 |
| Industry Standard Setters | p. 53 |
| Public Opinion | p. 53 |
| Government | p. 53 |
| Special-Interest Groups | p. 54 |
| Technical Experts | p. 54 |
| Cultural Interests | p. 54 |
| Adjacent Systems | p. 54 |
| Finding the Stakeholders | p. 54 |
| Goals: What Do You Want to Achieve? | p. 55 |
| Keeping Track of the Purpose | p. 59 |
| Requirements Constraints | p. 60 |
| Solution Constraints | p. 60 |
| Project Constraints | p. 61 |
| Naming Conventions and Definitions | p. 61 |
| How Much Is This Going to Cost? | p. 62 |
| Risks | p. 63 |
| To Go or Not to Go | p. 64 |
| Blastoff Alternatives | p. 65 |
| Summary | p. 65 |
| Event-Driven Use Cases | p. 67 |
| Agility Guide | p. 67 |
| Understanding the Work | p. 67 |
| Use Cases and Their Scope | p. 69 |
| The Work | p. 70 |
| The Context of the Work | p. 70 |
| The Outside World | p. 72 |
| Business Events | p. 73 |
| Time-Triggered Business Events | p. 74 |
| Why Business Events and Business Use Cases Are a Good Idea | p. 75 |
| Finding the Business Events | p. 76 |
| Business Use Cases | p. 78 |
| The Role of Adjacent Systems | p. 79 |
| Active Adjacent Systems | p. 80 |
| Autonomous Adjacent Systems | p. 83 |
| Cooperative Adjacent Systems | p. 85 |
| Business Use Cases and Product Use Cases | p. 86 |
| Actors | p. 89 |
| Summary | p. 90 |
| Trawling for Requirements | p. 93 |
| Agility Guide | p. 93 |
| Responsibility | p. 94 |
| The Requirements Analyst | p. 94 |
| Trawling and Business Use Cases | p. 96 |
| The Role of the Current Situation | p. 98 |
| Apprenticing | p. 101 |
| Observing Structures and Patterns | p. 103 |
| Interviewing the Stakeholders | p. 104 |
| Asking the Right Questions | p. 106 |
| Getting to the Essence of the Work | p. 107 |
| Solving the Right Problem | p. 109 |
| Innovative Products | p. 110 |
| Business Use Case Workshops | p. 113 |
| Outcome | p. 114 |
| Scenarios | p. 115 |
| Business Rules | p. 115 |
| Creativity Workshops | p. 116 |
| Brainstorming | p. 117 |
| Personas | p. 119 |
| Mind Maps | p. 122 |
| Wallpaper | p. 124 |
| Video and Photographs | p. 124 |
| Wikis, Blogs, and Discussion Forums | p. 125 |
| Document Archeology | p. 126 |
| Some Other Requirements-Gathering Techniques | p. 128 |
| Family Therapy | p. 128 |
| Soft Systems and Viewpoints | p. 129 |
| Determining What the Product Should Be | p. 129 |
| The True Origin of the Business Event | p. 131 |
| Does Technology Matter? | p. 131 |
| Choosing the Best Trawling Technique | p. 132 |
| Summary | p. 134 |
| Scenarios and Requirements | p. 135 |
| Agility Guide | p. 135 |
| Scenarios | p. 136 |
| Normal Case Scenarios | p. 140 |
| Diagramming the Scenario | p. 142 |
| Alternative Cases | p. 144 |
| Exception Cases | p. 145 |
| What If? Scenarios | p. 146 |
| Misuse Cases and Negative Scenarios | p. 147 |
| Scenario Template | p. 148 |
| Product Use Case Scenarios | p. 150 |
| Summary | p. 152 |
| Functional Requirements | p. 155 |
| Agility Guide | p. 155 |
| Functional Requirements | p. 157 |
| Finding the Functional Requirements | p. 157 |
| Level of Detail or Granularity | p. 160 |
| Exceptions and Alternatives | p. 161 |
| Avoiding Ambiguity | p. 162 |
| Technological Requirements | p. 164 |
| Requirements, Not Solutions | p. 165 |
| Grouping Requirements | p. 166 |
| Alternatives to Functional Requirements | p. 167 |
| Summary | p. 169 |
| Nonfunctional Requirements | p. 171 |
| Agility Guide | p. 172 |
| Nonfunctional Requirements | p. 173 |
| Use Cases and Nonfunctional Requirements | p. 174 |
| The Nonfunctional Requirements | p. 174 |
| Look and Feel Requirements: Type 10 | p. 176 |
| Usability and Humanity Requirements: Type 11 | p. 178 |
| Performance Requirements: Type 12 | p. 182 |
| Operational and Environmental Requirements: Type 13 | p. 184 |
| Maintainability and Support Requirements: Type 14 | p. 186 |
| Security Requirements: Type 15 | p. 187 |
| Confidentiality | p. 187 |
| Availability | p. 188 |
| Integrity | p. 188 |
| Auditing | p. 189 |
| ... And No More | p. 189 |
| Cultural and Political Requirements: Type 16 | p. 190 |
| Legal Requirements: Type 17 | p. 192 |
| Sarbanes-Oxley Act | p. 194 |
| Other Legal Obligations | p. 194 |
| Standards | p. 194 |
| Finding the Nonfunctional Requirements | p. 195 |
| Blogging the Requirements | p. 195 |
| Use Cases | p. 195 |
| The Template | p. 197 |
| Prototypes and Nonfunctional Requirements | p. 197 |
| The Client | p. 198 |
| Don't Write a Solution | p. 199 |
| Summary | p. 201 |
| Fit Criteria | p. 203 |
| Agility Guide | p. 203 |
| Why Does Fit Need a Criterion? | p. 204 |
| Scale of Measurement | p. 206 |
| Rationale | p. 206 |
| Fit Criteria for Nonfunctional Requirements | p. 208 |
| Product Failure? | p. 209 |
| Subjective Tests | p. 210 |
| Look and Feel Requirements | p. 211 |
| Usability and Humanity Requirements | p. 212 |
| Performance Requirements | p. 213 |
| Operational Requirements | p. 214 |
| Maintainability Requirements | p. 215 |
| Security Requirements | p. 215 |
| Cultural and Political Requirements | p. 216 |
| Legal Requirements | p. 216 |
| Fit Criteria for Functional Requirements | p. 217 |
| Test Cases | p. 218 |
| Use Cases and Fit Criteria | p. 218 |
| Fit Criterion for Project Purpose | p. 219 |
| Fit Criteria for Solution Constraints | p. 219 |
| Summary | p. 220 |
| Writing the Requirements | p. 223 |
| Agility Guide | p. 223 |
| Turning Potential Requirements into Written Requirements | p. 225 |
| Knowledge Versus Specification | p. 225 |
| The Volere Requirements Specification Template | p. 227 |
| The Purpose of the Project | p. 229 |
| The User Business or Background of the Project Effort | p. 229 |
| Goals of the Project | p. 230 |
| The Client, the Customer, and Other Stakeholders | p. 232 |
| The Client | p. 232 |
| The Customer | p. 233 |
| Other Stakeholders | p. 233 |
| Users of the Product | p. 233 |
| Mandated Constraints | p. 234 |
| Solution Constraints | p. 235 |
| Implementation Environment of the Current System | p. 235 |
| Partner or Collaborative Applications | p. 236 |
| Off-the-Shelf Software | p. 236 |
| Anticipated Workplace Environment | p. 236 |
| Schedule Constraints | p. 236 |
| Budget Constraints | p. 237 |
| Naming Conventions and Definitions | p. 237 |
| Definitions of All Terms, Including Acronyms, Used in the Project | p. 237 |
| Data Dictionary for Any Included Models | p. 238 |
| Relevant Facts and Assumptions | p. 238 |
| Facts | p. 238 |
| Assumptions | p. 239 |
| The Scope of the Work | p. 240 |
| Work Partitioning | p. 240 |
| The Scope of the Product | p. 241 |
| Product Boundary | p. 241 |
| Product Use Case List | p. 241 |
| Individual Product Use Cases | p. 241 |
| The Shell | p. 241 |
| Snow Cards | p. 242 |
| Automated Requirements Tools | p. 243 |
| The Atomic Requirements | p. 243 |
| Requirement Number | p. 244 |
| Requirement Type | p. 244 |
| Event/Use Case Number | p. 244 |
| Description | p. 245 |
| Rationale | p. 245 |
| Originator | p. 245 |
| Fit Criterion | p. 245 |
| Customer Satisfaction and Customer Dissatisfaction | p. 246 |
| Priority | p. 247 |
| Conflicts | p. 247 |
| Supporting Materials | p. 248 |
| History | p. 248 |
| Writing the Specification | p. 248 |
| Functional Requirements | p. 249 |
| Description | p. 250 |
| Nonfunctional Requirements | p. 251 |
| Project Issues | p. 252 |
| Open Issues | p. 252 |
| Off-the-Shelf Solutions | p. 253 |
| New Problems | p. 254 |
| Tasks | p. 254 |
| Migration to the New Product | p. 254 |
| Risks | p. 254 |
| Costs | p. 255 |
| User Documentation and Training | p. 256 |
| Waiting Room | p. 256 |
| Ideas for Solutions | p. 257 |
| Summary | p. 257 |
| The Quality Gateway | p. 259 |
| Agility Guide | p. 260 |
| Requirements Quality | p. 261 |
| Using the Quality Gateway | p. 262 |
| Testing Completeness | p. 263 |
| Are There Any Missing Components? | p. 264 |
| Meaningful to All Stakeholders? | p. 265 |
| Testing Traceability | p. 265 |
| Consistent Terminology | p. 267 |
| Relevant to Purpose? | p. 268 |
| Testing the Fit Criterion | p. 270 |
| Viable within Constraints? | p. 272 |
| Requirement or Solution? | p. 273 |
| Customer Value | p. 274 |
| Gold Plating | p. 275 |
| Requirements Creep | p. 276 |
| Requirements Leakage | p. 278 |
| Implementing the Quality Gateway | p. 279 |
| Alternative Quality Gateways | p. 280 |
| Summary | p. 281 |
| Prototyping the Requirements | p. 283 |
| Agility Guide | p. 285 |
| Prototypes and Reality | p. 286 |
| Low-Fidelity Prototypes | p. 288 |
| High-Fidelity Prototypes | p. 292 |
| Storyboards | p. 294 |
| Object Life History | p. 296 |
| The Prototyping Loop | p. 297 |
| Design and Build | p. 298 |
| Testing in the User Environment | p. 299 |
| Analyzing the Results | p. 300 |
| Summary | p. 301 |
| Reusing Requirements | p. 303 |
| What Is Reusing Requirements? | p. 303 |
| Sources of Reusable Requirements | p. 306 |
| Requirements Patterns | p. 307 |
| Christopher Alexander's Patterns | p. 308 |
| A Business Event Pattern | p. 309 |
| Context of Event Response | p. 310 |
| Processing for Event Response | p. 311 |
| Data for Event Response | p. 312 |
| Forming Patterns by Abstracting | p. 313 |
| Patterns for Specific Domains | p. 314 |
| Patterns Across Domains | p. 315 |
| Domain Analysis | p. 317 |
| Trends in Reuse | p. 318 |
| Reuse and Objects | p. 318 |
| Reuse Is Now a Job? | p. 318 |
| Summary | p. 319 |
| Reviewing the Specification | p. 321 |
| Agility Guide | p. 322 |
| Reviewing the Specification | p. 323 |
| Inspections | p. 323 |
| Find Missing Requirements | p. 324 |
| Have All Business Use Cases Been Discovered? | p. 325 |
| Define the Scope | p. 326 |
| Identify Business Events and Non-Events | p. 326 |
| Model the Business Use Case | p. 328 |
| Define the Business Data | p. 328 |
| CRUD Check | p. 330 |
| Check for Custodial Processes | p. 331 |
| Repeat Until Done | p. 331 |
| Customer Value | p. 332 |
| Prioritizing the Requirements | p. 333 |
| Prioritization Factors | p. 333 |
| When to Prioritize | p. 334 |
| Requirement Priority Grading | p. 335 |
| Prioritization Spreadsheet | p. 335 |
| Conflicting Requirements | p. 337 |
| Ambiguous Specifications | p. 339 |
| Risk Analysis | p. 340 |
| Project Drivers | p. 340 |
| Project Constraints | p. 341 |
| Functional Requirements | p. 341 |
| Measure the Required Effort | p. 342 |
| Summary | p. 342 |
| Whither Requirements? | p. 345 |
| Adapting the Process | p. 345 |
| What About Requirements Tools? | p. 347 |
| Mapping Tools to Purpose | p. 348 |
| Publishing the Requirements | p. 350 |
| Contractual Document | p. 351 |
| Management Summary | p. 351 |
| Marketing Summary | p. 352 |
| User Review | p. 352 |
| Reviewing the Specification | p. 353 |
| Requirements Traceability | p. 353 |
| Tracing a Business Event | p. 353 |
| Dealing with Change | p. 357 |
| Changes in the World | p. 358 |
| Requirements Feedback | p. 358 |
| Requirements Retrospective | p. 360 |
| What to Look For | p. 360 |
| Running the Retrospective | p. 360 |
| Retrospective Report | p. 362 |
| Your Notebook | p. 363 |
| The End | p. 363 |
| Volere Requirements Process Model | p. 365 |
| The Volere Requirements Process Model | p. 365 |
| Making This Work for You | p. 366 |
| Finding More Information | p. 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 Specification | p. 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 Model | p. 437 |
| Volere Requirements Specification Template | p. 451 |
| Contents | p. 451 |
| Project Drivers | p. 451 |
| Project Constraints | p. 451 |
| Functional Requirements | p. 451 |
| Nonfunctional Requirements | p. 451 |
| Project Issues | p. 452 |
| Preamble | p. 452 |
| Volere | p. 452 |
| Requirements Types | p. 453 |
| Testing Requirements | p. 453 |
| Requirements Shell | p. 454 |
| The Purpose of the Project | p. 454 |
| The User Business or Background of the Project Effort | p. 454 |
| Goals of the Project | p. 455 |
| The Client, the Customer, and Other Stakeholders | p. 456 |
| The Client | p. 456 |
| The Customer | p. 456 |
| Other Stakeholders | p. 457 |
| Users of the Product | p. 457 |
| The Hands-On Users of the Product | p. 457 |
| Priorities Assigned to Users | p. 458 |
| User Participation | p. 459 |
| Maintenance Users and Service Technicians | p. 459 |
| Mandated Constraints | p. 460 |
| Solution Constraints | p. 460 |
| Implementation Environment of the Current System | p. 461 |
| Partner or Collaborative Applications | p. 462 |
| Off-the-Shelf Software | p. 462 |
| Anticipated Workplace Environment | p. 463 |
| Schedule Constraints | p. 464 |
| Budget Constraints | p. 465 |
| Naming Conventions and Definitions | p. 465 |
| Definitions of All Terms, Including Acronyms, Used in the Project | p. 465 |
| Data Dictionary for Any Included Models | p. 466 |
| Relevant Facts and Assumptions | p. 467 |
| Facts | p. 467 |
| Assumptions | p. 467 |
| The Scope of the Work | p. 468 |
| The Current Situation | p. 468 |
| The Context of the Work | p. 469 |
| Work Partitioning | p. 470 |
| The Scope of the Product | p. 472 |
| Product Boundary | p. 472 |
| Product Use Case List | p. 472 |
| Individual Product Use Cases | p. 473 |
| Functional and Data Requirements | p. 473 |
| Functional Requirements | p. 473 |
| Data Requirements | p. 475 |
| Look and Feel Requirements | p. 476 |
| Appearance Requirements | p. 476 |
| Style Requirements | p. 476 |
| Usability and Humanity Requirements | p. 477 |
| Ease of Use Requirements | p. 477 |
| Personalization and Internationalization Requirements | p. 479 |
| Learning Requirements | p. 479 |
| Understandability and Politeness Requirements | p. 480 |
| Accessibility Requirements | p. 481 |
| Performance Requirements | p. 482 |
| Speed and Latency Requirements | p. 482 |
| Safety-Critical Requirements | p. 483 |
| Precision or Accuracy Requirements | p. 484 |
| Reliability and Availability Requirements | p. 484 |
| Robustness or Fault-Tolerance Requirements | p. 485 |
| Capacity Requirements | p. 485 |
| Scalability or Extensibility Requirements | p. 486 |
| Longevity Requirements | p. 486 |
| Operational and Environmental Requirements | p. 487 |
| Expected Physical Environment | p. 487 |
| Requirements for Interfacing with Adjacent Systems | p. 487 |
| Productization Requirements | p. 488 |
| Release Requirements | p. 489 |
| Maintainability and Support Requirements | p. 489 |
| Maintenance Requirements | p. 489 |
| Supportability Requirements | p. 490 |
| Adaptability Requirements | p. 490 |
| Security Requirements | p. 491 |
| Access Requirements | p. 491 |
| Integrity Requirements | p. 492 |
| Privacy Requirements | p. 492 |
| Audit Requirements | p. 493 |
| Immunity Requirements | p. 493 |
| Cultural and Political Requirements | p. 494 |
| Cultural Requirements | p. 494 |
| Political Requirements | p. 494 |
| Legal Requirements | p. 495 |
| Compliance Requirements | p. 495 |
| Standards Requirements | p. 496 |
| Open Issues | p. 496 |
| Off-the-Shelf Solutions | p. 497 |
| Ready-Made Products | p. 497 |
| Reusable Components | p. 497 |
| Products That Can Be Copied | p. 498 |
| New Problems | p. 498 |
| Effects on the Current Environment | p. 498 |
| Effects on the Installed Systems | p. 499 |
| Potential User Problems | p. 499 |
| Limitations in the Anticipated Implementation Environment That May Inhibit the New Product | p. 499 |
| Follow-Up Problems | p. 500 |
| Tasks | p. 500 |
| Project Planning | p. 500 |
| Planning of the Development Phases | p. 501 |
| Migration to the New Product | p. 501 |
| Requirements for Migration to the New Product | p. 501 |
| Data That Has to Be Modified or Translated for the New System | p. 502 |
| Risks | p. 502 |
| Costs | p. 503 |
| User Documentation and Training | p. 504 |
| User Documentation Requirements | p. 504 |
| Training Requirements | p. 505 |
| Waiting Room | p. 505 |
| Ideas for Solutions | p. 506 |
Function Point Counti
 |
Suzanne Robertson [저]
|
 |
-
전체 0개의 구매후기가 있습니다.
 |
인터파크도서는 고객님의 단순 변심에 의한 교환과 반품에 드는 비용은 고객님이 지불케 됩니다.
단, 상품이나 서비스 자체의 하자로 인한 교환 및 반품은 무료로 반품 됩니다. |
|
|
 교환 및 반품이 가능한 경우 |
 상품을 공급 받은 날로부터 7일이내 가능
공급받으신 상품의 내용이 표시, 광고 내용과 다르거나 다르게 이행된 경우에는 공급받은 날로부터 3개월 이내,
혹은 그사실을 알게 된 날 또는 알 수 있었던 날로부터 30일 이내
상품에 아무런 하자가 없는 경우 소비자의 고객변심에 의한 교환은 상품의 포장상태 등이 전혀 손상되지 않은 경우에 한하여 가능 |
|
|
| 교환 및 반품이 불가능한 경우 |
구매확정 이후(오픈마켓상품에 한함)
고객님의 책임 있는 사유로 상품 등이 멸실 또는 훼손된 경우
(단, 상품의 내용을 확인하기 위하여 포장 등을 훼손한 경우는 제외)
시간이 지남에 따라 재판매가 곤란할 정도로 물품의 가치가 떨어진 경우
포장 개봉되어 상품 가치가 훼손된 경우 |
|
|
| 다배송지의 경우 반품 환불 |
다배송지의 경우 다른 지역의 반품을 동시에 진행할 수 없습니다.
1개 지역의 반품이 완료된 후 다른 지역 반품을 진행할 수 있으므로, 이점 양해해 주시기 바랍니다. |
|
|
| 중고상품의 교환 |
| 중고상품은 제한된 재고 내에서 판매가 이루어지므로, 교환은 불가능합니다. |
|
|
| 오픈마켓 상품의 환불 |
오픈마켓상품에 대한 책임은 원칙적으로 업체에게 있으므로, 교환/반품 접수시 반드시 판매자와 협의 후 반품 접수를 하셔야하며,
반품접수 없이 반송하거나, 우편으로 보낼 경우 상품 확인이 어려워 환불이 불가능할 수 있으니 유의하시기 바랍니다. |
|
|
|
 |
| 배송예정일 안내 |
| 인터파크 도서는 모든 상품에 대해 배송완료예정일을 웹사이트에 표시하고 있습니다.
|
| <인터파크 직배송 상품> |
상품은 월~토요일 오전 10시 이전 주문분에 대하여 당일 출고/당일 배송완료를 보장하는 상품입니다. |
상품은 서울지역/평일 주문분은 당일 출고/익일 배송완료를 보장하며,
 서울외지역/평일 주문분의 경우는 오후 6시까지 주문분에 대하여 익일 배송완료를 보장하는 상품입니다.
(단, 월요일은 12시까지 주문에 한함)
|
상품은, 입고예정일(제품출시일)+택배사배송일(1일)에 배송완료를 보장합니다. |
 ~ 
상품은 유통특성상 인터파크에서 재고를 보유하지 않은 상품으로
주문일+기준출고일+택배사배송일(1일)에 배송완료를 보장합니다.(토/공휴일은 배송기간에 포함되지 않습니다.)
※기준출고일:인터파크가 상품을 수급하여 물류창고에서 포장/출고하기까지 소요되는 시간
|
|
| <업체 직접배송/오픈마켓 상품> |
~ 
상품은 업체가 주문을 확인하고, 출고하기까지 걸리는 시간입니다.
주문일+기준출고일+택배사배송일(2일)에 배송완료를 보장합니다.(토/공휴일은 배송기간에 포함되지 않습니다.)
※5일이내 출고가 시작되지 않을시, 오픈마켓 상품은 자동으로 주문이 취소되며, 고객님께 품절보상금을 지급해 드립니다.
|
|
|
|
| 배송비 안내 |
도서(중고도서 포함)만 구매하시면 : 배송비 2,000원 (1만원이상 구매 시 무료배송)
음반/DVD만 구매하시면 : 배송비 1,500원 (2만원이상 구매 시 무료배송)
잡지/만화/기프트만 구매하시면 : 배송비 2,000원 (2만원이상 구매 시 무료배송)
도서와 음반/DVD를 함께 구매하시면 : 배송비 1,500원 1만원이상 구매 시 무료배송)
도서와 잡지/만화/기프트/중고직배송상품을 함께 구매하시면 : 2,000원 (1만원이상 구매 시 무료배송)
업체직접배송상품을 구매시 : 업체별로 상이한 배송비 적용
* 세트상품의 경우 부분취소 시 추가 배송비가 부과될 수 있습니다.
* 북카트에서 배송비없애기 버튼을 클릭하셔서, 동일업체상품을 조금 더 구매하시면, 배송비를 절약하실 수 있습니다.
|
|
|
| 해외배송 안내 |
인터파크도서에서는 국내에서 주문하시거나 해외에서 주문하여 해외로 배송을 원하실 경우 DHL과 특약으로 책정된 요금표에
의해 개인이 이용하는 경우보다 배송요금을 크게 낮추며 DHL(www.dhl.co.kr)로 해외배송 서비스를 제공합니다.
해외배송은 도서/CD/DVD 상품에 한해 서비스하고 있으며, 다른 상품을 북카트에 함께 담으실 경우 해외배송이 불가합니다.
해외주문배송 서비스는 인터파크 도서 회원 가입을 하셔야만 신청 가능합니다. |
|
|
| 알아두세요!!! |
도매상 및 제작사 사정에 따라 품절/절판 등의 사유로 취소될 수 있습니다.
오픈마켓업체의 배송지연시 주문이 자동으로 취소될 수 있습니다.
출고가능 시간이 서로 다른 상품을 함께 주문할 경우 출고가능 시간이 가장 긴 기준으로 배송됩니다.
유통의 특성상 출고기간은 예정보다 앞당겨지거나 늦춰질 수 있습니다.
택배사 배송일인 서울 및 수도권은 1~2일, 지방은 2~3일, 도서, 산간, 군부대는 3일 이상의 시간이 소요됩니다. |
|
|
 |
|
|
|
|
;)
