Tag: stakeholder expectation

Scope Definition Seminar for INCOSE ChicagoLand Chapter

Scope Definition Seminar for INCOSE ChicagoLand Chapter

On May 11, 2019 we presented our 1-day Scope Definition seminar for the INCOSE ChicagoLand Chapter Spring Seminar offering to their membership.  This was a natural follow on seminar to the Writing Good Requirements seminar we presented at the 2018 Spring Seminar.  Feedback from the attendees indicated the seminar was very well received!  One of […]

Scope Definition Seminar in Chicago

Scope Definition Seminar in Chicago

Hi all, I will be giving a 1-day seminar on scope definition for the ChicagoLand INCOSE Chapter on May 11, 2019 for their Spring Tutorial. Last year I gave our 1-day Writing Good Requirements seminar which was very popular and sold out quickly.  That seminar focused on writing requirements that have the characteristics of well-formed […]

Requirements – What’s the Big Deal????

Requirements – What’s the Big Deal???? ArgonDigital - enterprise automation experts

Note: this is an update to this blog originally published in 2012. Preparing for the future A constant throughout the evolution of systems engineering is an ever-increasing complexity of systems which can be observed in terms of the number of system functions, components, and interfaces and their non-linear interactions and emergent properties. Each of these […]

What is the difference between verification and validation? Part 1

What is the difference between verification and validation? Part 1 ArgonDigital - enterprise automation experts

A question we are often asked is “What is difference between verification and validation?” This two-part blog answers that question.  In part 1 we discuss the basic concepts of verification and validation in terms of the context in which they are used within the system development lifecycle.  In part 2 of the blog, these concepts […]

Baseline Your Scope Before Writing Requirements

Baseline Your Scope Before Writing Requirements ArgonDigital - enterprise automation experts

A major issue that contributes to cancelled projects is a failure to establish a shared vision of the final product at the beginning of the project. The reason for a new product or upgrade must be clearly understood before writing requirements, or divergent requirements will be written and important requirements will be missed. This vision […]

How Do I Know When My Requirements Are Sufficient?

How Do I Know When My Requirements Are Sufficient? ArgonDigital - enterprise automation experts

This question was asked recently on a popular discussion group. Maybe a better question to ask: “How do I know when the requirement set for the system of interest is “done enough” to give to the development team?” Where “done enough” is the point of time in the development process where the cost of potential […]

Agile and Requirement–Driven Product Development

Agile and Requirement–Driven Product Development ArgonDigital - enterprise automation experts

My previous blog described “Requirement-Driven Product Development” (RDPD). One of my readers asked a very important and well-formed question: “Lou, nice article. Are there any specializations to the approach for software systems? Would you say that Scrum process is consistent with RDPD? I expect that everyone agrees that requirements must drive development. The controversy is […]

Requirement–Driven Product Development

Requirement–Driven Product Development ArgonDigital - enterprise automation experts

I think it is safe to say that everyone that leads or is part of a product development project starts out with the intention of delivering a winning product. We define a winning product as a product that delivers what is needed, with the expected quality, within schedule and budget constraints. To deliver winning products, […]

How to Handle Implementation in Customer Requirements

How to Handle Implementation in Customer Requirements ArgonDigital - enterprise automation experts

I was asked the following question from a friend of mine: “I see a propensity to copy requirements from the Customer Specification to various levels of the requirement hierarchy in order to link between a Customer requirement written as implementation in their specification to where it is allocated to in HW/SW.  Is there any guidance […]

Medical Device Development and ArgonDigital

Medical Device Development and ArgonDigital ArgonDigital - enterprise automation experts

We are frequently asked whether or not the training we offer is specifically geared to the medical device industry or if our training is generic.  The short answer – our instructors have extensive experience in providing training for the medical device industry.  We have taught both our standard courses as well as tailored classes for […]

Why are we doing what we are Doing?

Why are we doing what we are Doing? ArgonDigital - enterprise automation experts

A common problem we see on new projects is people jump into writing requirements without first answering the question “Why are we doing what we are doing?”  Many challenged projects (e.g., over budget, behind schedule, not meeting quality standards) can trace their difficulties to the very beginning of the project where there was a failure […]

Going from system concepts to requirements – Part 1

Going from system concepts to requirements – Part 1 ArgonDigital - enterprise automation experts

Note: This is Part 1 of our discussion concerning going from system concepts to requirements.  Part 1 addresses the basic concepts; Going from system concepts to requirements – Part 2 delves more into the “How” to go from system concepts to requirements. As you know, before writing requirements there is a lot of work that […]