msaad

1.B.4-Requirements Elicitation activities (discuss with natural language)

• Identifying actors
  (type of actor that use system in all cases-normal and abnormal-)
  
• Identifying scenarios
  (different scenario with different actor –is specific scenario with specific
  

  
  Actor-)
  

• Identifying use cases (define use case and its actor)
  
• Identifying relationship among actors and use cases (relation
  use case and its actor)
  
• Identifying initial analysis objects (object that need in this use case)
  
• Identifying non-functional requirements (type of used in cases object’s)
  

1.B.4.0-Identifying actors

Questions to ask

Which user group is supported by the system to perform their work? – Customer of system. (Owner of car)

Which user groups execute the system’s main functions? - Who execute function (Driver of car)

Which user groups perform secondary functions (e.g. maintenance and administration)?

(Mechanical man) (Service station - in fuel system)

With what external hardware or software systems the system will interact? -Type of external environment that effect in system design.

1.B.4.1-Types of Scenarios

A concrete, focused, informal description of a single feature of the system used by a single actor.

Usually uses during the software lifecycle:

Requirements Elicitation: As-is scenario (Current) used in re-engineering

, visionary scenario (in future) used in Greenfield engineering, reengineering

Client Acceptance Test: Evaluation scenario. (System that will produce)

System Deployment: Training scenario. (Simulate action to train it)

How to find the scenarios?

Ask client discussion question don’t ask (yes, no) question?

Ask yourself or the client the following questions:

    What are the primary tasks that the system needs to perform? - System function

    What data will the actor create, store, change, remove or add in the system?

    What external changes does the system need to know about? - By which actor

    What changes or events will the actor of the system need to be informed about?

However, don’t rely on questionnaires alone.

Insist on task observation
if the system already exists (interface engineering or reengineering)

مثال كشاف النور: عند كل عنوان يكتب بعض الملاحظات التى تساعده فى العمل – صغيرة ولاكن مهمة - مثل (كلب فى الحديقة – متواجدين بع الساعة 11).

• Ask to speak to the end user, not just to the software contractor
  
• Expect resistance and try to overcome it.