1st Step: System Identification

Two questions need to be answered:

 We must identify the:

Purpose of a system? : That determined which tools and technology I have to use.

System boundary: What is inside, what is outside the system and sub system?

Like:
saving account in ATM will be by ATM system or Bank system.


Requirements process consists of two activities:

 Requirements Elicitation:
-User Language-

Definition of the system in terms understood by the customer (”Problem Description”)

 Requirements Analysis: -Developer Language-

Technical specification of the system in terms understood by the developer (”Problem Specification”)

Difficult to get specific and right system processes

So we can do it by dealing with more than categories of user (Customer-Manager- and system user)

with different back ground.

How to make function Model?

Ask user in
scenarios
like examples of what is action and interaction happened to do process x?

But this not all ways to do this process, this is only 1 scenario.

So
we need to have more scenarios that declare relevant and irrelevant

in (system and Function-Use Case-).

Problem Statement Generation: export (problem Statement, Requirements Elicitation).
Problem Statement Document: define system purpose and boundary.الورق المستخدم فى المناقصة
Requirements Elicitation: export Step 4 and written with (user Lang.). مثال: العمارة عاوزها شكله …و الوجهة….
System Specification Model: represent model with (user language) describe user view.

Natural Language can be understood by more mean Like (Boy (No) Girl).
Requirements Analysis: -will going throw it in chapter 5- but we going on between (elicitation and analysis)

According to prosperity or not until we get clear requirement and make
Analysis Model: represent clear and specific model by graphical language UML