Professional Documents
Culture Documents
Analysis and Design Systems: Analysis Stage Detailed Study
Analysis and Design Systems: Analysis Stage Detailed Study
Analysis and Design Systems: Analysis Stage Detailed Study
Lecture 5
Analysis stage
Detailed study
Dr.Abdualmajed Alkhulaidi
Associate professor at Sana’a University
Doctor of Philosophy in Software
Engineering
Operations specification
Of course, we can all tell which carrier a friend of ours is using just by •
knowing his or her mobile phone number. However, we do not recognize
the logic on which this knowledge operates.
There are several techniques used to analyze and document the logic of •
decisions that occur in operations, including:
• English language,
• structural decisions
• decision tables
• decision trees.
The analyst must be able to recognize the logic and structural decisions •
that occur in the business, and must also know how to differentiate
between these structural and semi-structural decisions.
Structured decisions: are those that deal with recurring routine problems •
and have a known routine procedure that can be applied at any time
whenever the same problem recurs.
- Unstructured decisions: they deal with new and non-recurring problems, •
and therefore there is no clear path or decisive way for them to take
decisions regarding them.
Objectives of production process
specifications
• Reduce process ambiguity: This objective will force
the analyst to identify the details of the process
implementation.
• Obtaining an accurate description of what has been
done and done: This description will usually be later
placed in a file of specifications and given to the
programmer.
• Validate the design of the system and ensure that the
process actually receives all the input data streams
needed to produce the output streams and also
ensures that all the input and output streams are
represented on the data flow diagram.
Cases that do not require
description
There are many cases in which a specification of operations is not created,
because sometimes the process is too simple or relies on pre-existing
computer code. Such cases should then be noted in the process description,
and no further design is required.
-Operations representing physical input or output: reading and writing.
- These operations usually need simple logic. Regular data entry validations.
For complex editing data entry validations, a process specification must be
created.
- Operations that use pre-written code. These processes are then usually
included in the system as subprograms or dependencies. Subprograms are
computer programs that are written, tested, and stored on a computer
system. These subprograms usually perform a general system function, such
as validating a date or check number. These general-purpose subprograms are
written and documented only once but form a series of building blocks that
can be used in many data flow diagrams. As for the functions, they are similar
to the subprograms, but the difference between them is in the way the code
is written for each of them.
data specification format
- Process number: which must match the process ID shown on
the data flow diagram.
Process name: which must also match the name written on the
process code in the data flow diagram.
- A brief description of what the process does.
- A list of the data flows entering the process.
-Data flows out of the process.
- Determine the type of operation: is it batch, on-line, or -
manual.
-If the process uses prewritten code, give the name of the -
child or child program that contains the code.
-A description of the logic of the process that explains policies
and business rules in the language of everyday life rather than in
the pseudo-code language of computer languages. Business
rules are procedures or perhaps a set of conditions and formulas
that a company follows in order to carry out its work.
-If there is not enough space on the form to write a full
description of the process in Structured English, or if there is a
decision table or tree illustrating the logic of the process, give
the name of the table or tree in the form.
- List all the unresolved issues, all the missing parts of the
process logic and any other issues related to that, as these issues
form the basis for the questions that will be asked in the appeals
interviews.
Structured English
-When process logic includes formulas or repetitions or when
structural decisions are uncomplicated, it is appropriate to use
Structured English for decision-process analysis.
- As its name indicates, Structured English is based on
• Structural logic: we mean instructions that are organized into
overlapping and modest procedures into groups.
• Simple English like: add , multiply , move.
- The verbal problem can be expressed in Structured English by
placing decision rules in the required sequence and using the IF-
THEN-ELSE instructions within it. Structured English can be more
complex if blocks of operations overlap with other blocks of
instructions.
Structured English
• Structured English:
-Strings of Imperative Sentences.
- Decisions.
-Cycles or Repeat.
Decision Table جداول القرارات
N N N N N N N N Y Y Y Y Y Y Y Y أن يكون مستوى المادة أكبر من مستوى الطالب
N N N N Y Y Y Y N N N N Y Y Y Y أن يكون مستوى المادة مسا ٍو أو أصغر من مستوى الطالب
N N Y Y N N Y Y N N Y Y N N Y Y أن ال يقل عدد الساعات المسجلة للطالب بعد الحذف عن 12ساعة.
N Y N Y N Y N Y N Y N Y N Y N Y أن يكون عدد الساعات المسجلة للطالب بعد الحذف أقل من 12
ساعة.
x x أحذف المادة
N N Y Y Y أن يكون مستوى المادة أكبر من مستوى الطالب
Y Y N N N أن يكون مستوى المادة مسا ٍو أو أصغر من مستوى الطالب
N Y N N Y أن ال يقل عدد الساعات المسجلة للطالب بعد الحذف عن 12ساعة.
Y N N Y N أن يكون عدد الساعات المسجلة للطالب بعد الحذف أقل من 12
ساعة.
x x أحذف المادة