About Us


  Process Models

  SE Resources


  Contact us

Breaking News!

A new blog ... visit OnCenter, Roger Pressman's running commentary on the world at large

A new edition ... the 6th edition of Software Engineering is available now

A first novel ... Roger Pressman's first novel is a technothriller -- The Aymara Bridge

A new training curriculum! RSP&A has partnered with QAI to develop a comprehensive Internet-based software engineering curriculum.

A redesigned Web site ... we've done a major redesign and added many new features

Adaptable Process Model
System-Level Requirements Validation

IMPORTANT NOTICE: The complete Adaptable Process Model (APM) is provided for informational purposes and for assessment by potential users. The APM is copyrighted material and may not be downloaded, copied, or extracted for use in actual project work. The full hypertext (html) version of the APM may be licensed for use and customization within your organization. Contact R.S. Pressman & Associates, Inc. for complete licensing information.

System Level Requirements Validation

    Software always exists in a broad system context. Although system requirements may have already been established before a software engineering begins his or her work, it is important to determine that system requirements are complete and consistent. If they are not, "push-back" must occur. That is, the software engineering organization must demand clarification from those who have developed system level requirements. The following check will help you to assess system requirements for completeness and consistency. For this checklist, the more questions that elicit a negative response, the higher the risk that the system model will not provide a solid foundation for software engineering work.

    • Have the business context and justification for the system been properly developed?
    • Has overall feasibility been addressed?
    • Have all stakeholders been identified and polled for agreement?
    • Have the overall function and behavior of the system been defined?
    • Based on existing documentation/information, do you understand the system in the context of each of the views in the system engineering hierarchy?
    • Have system processes been adequately (unambiguously) and consistently defined?
    • Is system output and input adequately defined?
    • Have system-level assumptions, simplifications, limitations, constraints and preferences been explicitly and unambiguously stated?
    • Has simulation been done to demonstrate technological feasibility?
    • Has a data architecture been identified?
    • Has an application (functional) architecture been defined?
    • Has the required technology infrastructure for the system been adequately defined?
    • For business applications: Have ISP and BAA (SEPA, 5/e, p. 253) been performed?
    • Has requirements elicitation been performed at the system level?
    • Has the scope of the system been bounded?
    • Has business and technical feasibility been assessed?
    • Have usage scenarios been created at the system level?
    • Has a requirements management process been established for the system?
    • Has allocation occurred for all system elements?
    • Is the allocation for software reasonable and well-defined?
    • Have appropriate traceability tables been developed?
    • Has a system model (e.g., a Hatley-Pirbhai model) been developed?

      Return to Checklist Table of Contents

Site search! We've added links to a search engine that will enable you to search our entire site for information you need. Enter the appropriate word or phrase below.


Home About us Products Product Models SE Resources Commentary Contact us

Web site and all contents R.S. Pressman & Associates, Inc. 2001 - 2006, All rights reserved.
Free website templates