Types of Requirements

By -
Customer Requirements
Statements of fact and assumptions that define the expectations of the system in terms of mission objectives, environment, constraints, and measures of effectiveness and suitability (MOE/MOS). The customers are those that perform the eight primary functions of systems engineering, with special emphasis on the operator as the key customer. Operational requirements will define the basic need and, at a minimum, answer the questions posed in the following listing:
  • Operational distribution or deployment: Where will the system be used?
  • Mission profile or scenario: How will the system accomplish its mission objective?
  • Performance and related parameters: What are the critical system parameters to accomplish the mission?
  • Utilization environments: How are the various system components to be used?
  • Effectiveness requirements: How effective or efficient must the system be in performing its mission?
  • Operational life cycle: How long will the system be in use by the user?
  • Environment: What environments will the system be expected to operate in an effective manner?
Architectural Requirements
Architectural requirements explain what has to be done by identifying the necessary system architecture (structure + behavior) of a system.
Structural Requirements
Structural requirements explain what has to be done by identifying the necessary structure of a system.
Behavioral Requirements
Behavioral requirements explain what has to be done by identifying the necessary behavior of a system.
Functional Requirements
Functional requirements explain what has to be done by identifying the necessary task, action or activity that must be accomplished. Functional requirements analysis will be used as the toplevel functions for functional analysis.
Non-functional Requirements
Non-functional requirements are requirements that specify criteria that can be used to judge the operation of a system, rather than specific behaviors.
Performance Requirements
The extent to which a mission or function must be executed; generally measured in terms of quantity, quality, coverage, timeliness or readiness. During requirements analysis, performance (how well does it have to be done) requirements will be interactively developed across all identified functions based on system life cycle factors; and characterized in terms of the degree of certainty in their estimate, the degree of criticality to system success, and their relationship to other requirements.
Design Requirements
The “build to,” “code to,” and “buy to” requirements for products and “how to execute” requirements for processes expressed in technical data packages and technical manuals.
Derived Requirements
Requirements that are implied or transformed from higher-level requirement. For example, a requirement for long range or high speed may result in a design requirement for low weight.
Allocated Requirements
A requirement that is established by dividing or otherwise allocating a high-level requirement into multiple lower-level requirements. Example: A 100-pound item that consists of two subsystems might result in weight requirements of 70 pounds and 30 pounds for the two lower-level items.
Well-known requirements categorization models include FURPS and FURPS+, developed at Hewlett-Packar

Comments

Post a Comment

Popular posts from this blog

Progress 4GL interview questions for QAD technology

By -
1.        What is “No-undo” in the variable declaration? 2.        What are the different .pf parameters 3.        What are the different types of  locks in progress? Explain with example. If a record is locked Exclusively, can a shared lock be provided over the same? 4.        What are different type of procedures in progress? Can internal procedure call other internal procedure? If yes how? If no why no? Can external procedure call internal procedures? 5.        How is array defined in progress? What is the limit of extent for progress? Can we create 2 dimensional / multi dimensional arrays in progress / How? If no then how can we achieve the same? 6.        What are browses? 7.        What are queries? 8.        Can we call excel application from progress? How? 9.        What is the difference between can-find and find? 10.     What are the different types of triggers available in progress? Name few database level triggers. 11.     What are the different type
Read more

QAD interview questions for SE and Eb2 version

By -
1.       What is the difference between WO close and WO accounting close. 2.       What are the different types of transaction types in mfg-pro 3.       What is tag count when it is used 4.       Explain the purchase cycle 5.       What is the difference between the WO module and Repetitive  module. 6.       Explain the Payment cycle 7.       Explain the Sales Cycle 8.       What is a schedule order 9.       Explain GTM why and where it can be used 10.   How can u ensure that the supplier is given a schedule on a particular day of the week say only on Monday. 11.   What is MRP .What are the different types of MRP 12.   Can the  status of the the material can be changed 13.   What are financial transactions passed when you do voucher and payments. 14.   What are the transaction  passed when the payment is made 15.   The financial transaction passed when the sales  order is  updated. 16.   What are the primary input for MRP explain  in details 17.   Expl
Read more

Use of API in QAD EE

By -
/*Sample API Program to create currency in QAD EE*/ {us/mf/mfdtitle.i} {us/bbi/gplabel.i} {us/wb/wbrp01.i}         {us/gl/glsec.i} {us/gp/gpuid.i} {proxy/bcurrencydef.i } /* ======== FOR API ========= */ DEFINE VARIABLE viReturn                     AS INTEGER     NO-UNDO. DEFINE VARIABLE ilReturnDataset              AS LOGICAL     NO-UNDO. DEFINE VARIABLE ilPartialUpdate              AS LOGICAL     NO-UNDO. DEFINE VARIABLE icPartialUpdateExceptionList AS CHARACTER   NO-UNDO. DEFINE VARIABLE ocPrimaryKey                 AS CHARACTER   NO-UNDO. DEFINE VARIABLE ocRowid                      AS CHARACTER   NO-UNDO. DEFINE VARIABLE oiDraftInstance              AS INTEGER     NO-UNDO. DEFINE VARIABLE ocPrimaryKeyName             AS CHARACTER   NO-UNDO. DEFINE VARIABLE vho                          AS HANDLE. DEFINE VARIABLE oiReturnStatus               AS INTEGER     NO-UNDO. empty temp-table tCurrency. for first RoundingMethod no-lock where RoundingMethodCode = "
Read more