tailieunhanh - System Analysis, Design, and Development Concepts, Principles, and Practices phần 5

Nguyên tắc 22,2 Mỗi khả năng hoạt động đòi hỏi phải có một kích hoạt bên ngoài gợi ý hoặc một sự kích thích để bắt đầu xử lý dựa trên kết quả của nó. Nguyên tắc 22,3 Mỗi khả năng hoạt động, như một hệ thống tích hợp, bao gồm ba giai đoạn tuần tự dựa trên hành động: 1. Pre-nhiệm vụ giai đoạn khởi tạo | Simpo PDF Merge and Split Unre gtisieroncPVeriSiontìr SptW Figure Requirements Hierarchy Tree Illustrating Conflicting Requirements Author s Note The hierarchy shown is best described as ideal meaning all requirements are properly aligned to higher level requirements. For discussion purposes we will restrict the simplicity of this diagram to generic requirements. Requirements are derived from and must be traceable to measures of effectiveness MOEs measures of suitability MOSs and measures of performance MOPs at the system and mission levels. Referral For more information about MOEs MOS and MOPs refer to the Operational Utility Suitability and Effectiveness Practices discussion in Chapter 34. The system s mission represents the highest level requirement in Figure . The mission is scoped bounded and described by three high-level capability requirements R1 R2 and R3. When a single requirement such as R12 R32 and R33 effectively ends the chain the term leaf requirement is sometimes used. Guidepost From this basic understanding of a theoretical capability requirement hierarchy we are now ready to investigate common problems with specification requirements. COMMON PROBLEMS WITH SPECIFICATION REQUIREMENTS Specifications often have imperfections and are unintentionally released with a number of errors defects and deficiencies. To illustrate these conditions let s identify a series of undesirable conditions that commonly plague specifications. We noted earlier that some people develop specifications as random sets of thoughts or wish lists organized to a standard outline structure. Specifications of this type typically evolve from informal to formal brainstorming sessions. Requirements captured during the session are published for review. During the session reviewers lobby other reviewers to support additions of their respective desires to the structure. Ssbrn PO 2M er RteredeVersion - http Author