• Skip to main content
  • Skip to header right navigation
  • Skip to site footer

Shaping Software

Enduring Ideas in the Realm of Software

  • About
  • Topics
  • Best Software Engineering Books
  • Lessons in Software
  • Archives
  • JD Meier.com

Requirements

Customer-Connected Engineering Slides

Customer-Connected Engineering Slides (PDF Download)

Customer Connected Engineering (CCE) is a practices we use across our patterns & practices teams for engaging customers throughout the life cycle. We involved customers during the planning, development, and release of our deliverables. This is a draft slide set that shares how we do Customer Connected Engineering inside patterns & practices, including our key practices and guiding principles.

Read moreCustomer-Connected Engineering Slides (PDF Download)

Agile Architecture Method

The Agile Architecture Method is a way to bake quality into the life cycle. It's also an iterative and incremental approach for architecture and design. In its simplest form, it's a way to help you identify potential hot spots against your prioritized scenarios. The hot spots are key engineering decision. The main hot spots are cross-cutting concerns, such as data access, exception management, logging ... etc. and quality attributes, such as security, performance, reliability ... etc.

Read moreAgile Architecture Method

What’s a Scenario

Photo by Wonderlane What’s a scenario?  Not everybody uses the term “scenario” the same way.  In the software industry, there’s three common usages of scenario: The same as a use case. A path through a use case. An instance of a use case. Usually, the most helpful one is “an instance of a use case.”  …

Read moreWhat’s a Scenario

5 Situations for Writing Use Cases

What are five common project situations for writing use cases?  In Writing Effective Use Cases (Agile Software Development Series), Alistair Cockburn identifies five different situations for writing use cases to help you better understand variances between the purposes and approaches. Five Project TypesCockburn identifies the following five particular situations: Eliciting requirements, even if use cases …

Read more5 Situations for Writing Use Cases

User Requirements vs. System Requirements

I’ve often run into debates over whether it’s worth distinguishing between user requirements and system requirements. I would argue that having precision around the perspective helps you make more effective trade-offs, as well as make sure you’re looking through the appropriate lens when you need to. In Scenarios, Stories, Use Cases: Through the Systems Development …

Read moreUser Requirements vs. System Requirements
  • Go to page 1
  • Go to page 2
  • Go to page 3
  • Next