• A brief "cheat sheet" on requirements writing.

• Applying Use Case analysis with Scenario Sequence Diagrams and their applicability and utility in the Systems Engineering domain.
• 2004

• The Scenario Sequence Diagram modeling technique began as a Use Case elaboration exercise.  In separate work with both Lockheed-Martin and Boeing, we have been successfully using Scenario Sequence Diagrams to model, and document, system behavior and flow the knowledge gained into the traditional requirements and design documents. 
• 2005

• The Operations Concept document is a technical design document derived from the customers Concept of Operations (CONOPS) and developed through Systems Engineering's functional and behavioral decomposition and synthesis into a viable system architecture meeting all project requirements.
• The Operations Concept Document is an architecture-driving document. The three components of system design; HW design, SW implementation and Operations Procedures are all equal elements of the system architecture. The Operations Concept Document defines & drives SW and HW implementation providing the context of system behavior.
• 2004

• The tools industry is on the verge of providing the practicing systems engineer with the ability to efficiently perform systems analysis and manage design products through the integration of graphic UML modeling capabilities with established requirements repositories.  Unfortunately this integration is potentially hampered by an in complete behavior modeling construct in the UML.  This paper discusses the systems engineering need, critiques the UML Activity and Sequence Diagram's shortcomings and proposes a recommendation for evolution of the UML 2.0 to facilitate industry development of an integrated systems engineering tool set, by describing the key attributes of such a tool set.
• 2004