پاورپوینت کامل DATA GATHERING (REQUIREMENTS) 40 اسلاید در PowerPoint

توجه : این فایل به صورت فایل power point (پاور پوینت) ارائه میگردد

 پاورپوینت کامل DATA GATHERING (REQUIREMENTS) 40 اسلاید در PowerPoint دارای ۴۰ اسلاید می باشد و دارای تنظیمات کامل در PowerPoint می باشد و آماده ارائه یا چاپ است

شما با استفاده ازاین پاورپوینت میتوانید یک ارائه بسیارعالی و با شکوهی داشته باشید و همه حاضرین با اشتیاق به مطالب شما گوش خواهند داد.

لطفا نگران مطالب داخل پاورپوینت نباشید، مطالب داخل اسلاید ها بسیار ساده و قابل درک برای شما می باشد، ما عالی بودن این فایل رو تضمین می کنیم.

توجه : در صورت  مشاهده  بهم ریختگی احتمالی در متون زیر ،دلیل ان کپی کردن این مطالب از داخل فایل می باشد و در فایل اصلی پاورپوینت کامل DATA GATHERING (REQUIREMENTS) 40 اسلاید در PowerPoint،به هیچ وجه بهم ریختگی وجود ندارد

بخشی از مطالب داخلی اسلاید ها

پاورپوینت کامل DATA GATHERING (REQUIREMENTS) 40 اسلاید در PowerPoint

اسلاید ۴: ELICITATION

اسلاید ۵: ELICITATION TECHNIQUESinterviewing group sessions observations scenarios and use cases prototyping

اسلاید ۶: REQ. DEFINITIONThe requirements definition document is a complete listing of everything the customer expects the proposed system to do. It represents an understanding between the customer and developer of what the customer needs or wants, and it is usually written jointly by the customer and developer.

اسلاید ۷: REQ. SPECIFICATIONThe requirements specification restates the requirements definition in terms appropriate for the development of a system design; it is the technical counterpart to the requirements definition document, and it is written by requirements analysts. Sometimes one document may serve both purposes, representing a common understanding among customers, requirements analysts and designers. But often both types of documents are needed, and the need that no information is lost or changed when reinterpreting the definition as a specification is great.

اسلاید ۸: Functional / Non-Functionalfunctional requirements describe fundamental functions of the system non functional requirements (NFRs) describe constraints on the system (e.g. security, reliability, portability, safety, performance) constraints from the application domain (e.g. interface with existing systems in the organization)

اسلاید ۹: CONTENT OF A REQUIREMENTS DOCUMENToutline of the general purpose of the system description of the background and objectives of system development (e.g. if the system is to replace an existing approach) detailed description of characteristics of the proposed system (functional requirements) description of the environment in which the system will operate and requirements for support, security, privacy and any other hardware or software constraints should be addressed (NFR’s)

اسلاید ۱۰: EXAMPLERequirement 4.1.3.1. INITIATE TRACK ON IMAGE. Logical processing shall be done to INITIATE TRACK ON IMAGE. This shall have as input HANDOVER DATA. This shall have as output HOIQ, STATE DATA and IMAGE ID. This logical processing, when appropriate, shall identify a new instance of IMAGE. This logical processing, when appropriate, shall identify the type of entity instance as being IMAGE ON TRACK. NOTE: a request for pulses is made by entering a formal record into the HOIQ which feeds the pulse-send procedures.

اسلاید ۱۱: FORMALALPHA: INITIATE_TRACK_ON_IMAGE. INPUTS: HANDOVER_DATA. OUTPUTS: HOIQ. STATE_DATA, IMAGE_ID. CREATES: IMAGE. SETS:IMAGE_ON TRACK. DESCRIPTION: (4.1.3.1) A REQUEST FOR PULSE IS MADE BY ENTERING A FORMAL RECORD REQUEST INTO THE HOIQ WHICH FEEDS THE PULSE SENDING PROCEDURES.

اسلاید ۱۲: CHARACTERISTIC OF REQUIREMENTSunambiguous complete verifiable consistent modifiable traceable usable (Macaulay 1997)

اسلاید ۱۳: UNAMBIGUOUSRequirements are often written in a natural language where statements can have more than one meaning. Formal requirements languages help reduce ambiguity.

اسلاید ۱۴: COMPLETEThe requirements documents are complete if they include all of the significant requirements, whether relating to functionality, performance, design constraints, attributes or external interfaces and conforms to the company standards.

اسلاید ۱۵: VERIFIABLEAn example of non-verifiable requirements is the product should have a good human interface. An example of a verifiable requirement is the system will respond to a user request within 20 secs of the user pressing the enter key, 80% of the time

اسلاید ۱۶: CONSISTENTThree types of conflict which can occur are: different terms used for the same object: for example, a P45 and a tax form might be used to describe the same form. characteristics of objects conflict: for example, in one part of the requirements document, a red light will indicate a fault, while in another part, a blue light will indicate a fault. logical or temporal faults: for example, A follows B in one part, A and B occur simultaneously in anothe