Computer Engineering Commons^™

Introduction To Atomic Requirements, William L. Honig

William L Honig

An introduction to requirements and the importance of making single atomic requirements statements. Atomic requirements have advantages and improve the requirements process, support requirement verification and validation, enable traceability, support testability of systems, and provide management advantages. Why has there been so little emphasis on atomic requirements?

Requirements Quick Notes, William L. Honig, Shingo Takada

William L Honig

A short introduction to requirements and their role in system development. Includes industry definition of requirements, overview of basic requirements process including numbering of requirements, ties to testing, and traceability. An introduction to requirements quality attributes (correct, unambiguous, etc.) Includes references to requirements process, numbering, and quality papers.

An Example Of Atomic Requirements - Login Screen, William L. Honig

William L Honig

A simple example of what an atomic or individual or singular requirement statement should be. Using the example of the familiar login screen, shows the evolution from a low quality initial attempt at requirements to a complete atomic requirement statement. Introduces the idea of a system glossary to support the atomic requirement.

Requirements Metrics - Definitions Of A Working List Of Possible Metrics For Requirements Quality, William L. Honig

William L Honig

A work in progress to define a metrics set for requirements. Metrics are defined that apply to either the entire requirements set (requirements document as a whole) or individual atomic (or singular, individual) requirements statements. Requirements are identified with standard names and a identification scheme and include both subjective and objective measures. An example metric for the full set of requirements: Rd2 - Requirements Consistency, Is the set of atomic requirements internally consistent, with no contradictions, no duplication between individual requirements? An example of a metric for a single requirement: Ra4 - Requirement Verifiability, How adequately can this requirement be …

Atomic Requirements Quick Notes, William L. Honig, Shingo Takada

William L Honig

Working paper on atomic requirements for systems development and the importance of singular, cohesive, individual requirements statements. Covers possible definitions of atomic requirements, and their characteristics. Atomic requirements improve many parts of the development process from requirements to testing and contracting.

Analyzing Wi­Fi P2p In The Context Of A Hangman Game, William L. Honig

William L Honig

Wi­Fi P2P , which complies with the Wi­Fi Alliance's Wi­Fi Direct™ certification

2 3

program, is a relatively new addition to wireless communications systems. It is now

supported in Android operating system (since version 4.0). In theory, Wi­Fi Direct offers

advantages for ad hoc communications between mobile apps. A key goal of this project

was to evaluate the ability of Wi­Fi P2P for interconnecting mobile apps by using a

common game suitable to mobile screens and devices.

The application allows the user to interconnect two devices using Wi­Fi P2P and

play the classic hangman game. The players search for devices …