Senior Project

Title: System Soft Solution System

Prepared By: Mohamad M Khalifeh

Contents
Chapter One Introduction.....................................3
Stage 0-Feasibility Study.............................5
Stage 1-Investigation..................................6
Stage 2-Business System Option.................7
Stage 3-Requirement Specification..............8
Stage 4-Technical system Option...............10
Stage 5-Logical Design..............................11
Stage 6-Physical Design............................12
Chapter 2 Time Management.............................13
PERT 13

Chapter One
Initiating and planning is the major outcomes of any business
system that have been created earlier, nor new system that requires
to be created, there are several approaches that the analyst in
general can follow in order to accomplish organization needs and
wants want.
I will focus on the waterfall approach that we can take advantage for
implementing a business system that consists of the following
steps:1) The development of feasibility study, that determine whether
the project economically, technologically, and organizationally
feasible.
2) Finding the requirements of the system, this usually done by
interviewing, questionnaire, and observation of existing
system.
3) Train the end users of how to become familiar in operating the
new systems in term of hardware and software experiences,
and how would they use it.

Structural System Analysis and Design

The most three important techniques are:
1) Logical data modeling: is the process that comes with
identifying, modeling, and documenting the requirements of
the business needs (Prototype) of the system that have been
designed. The data are separated into entities (record
information) and their relationship between them.
2) Data Flow: is the process that comes with identifying,
modeling, and documenting how data moves around
information system, that being transformed from one form to
another, and stores in area such as (Database).It could be
sent to external source such as top management if exists, and
finally the data flow by routing the information inside the
network.
3) Entity behavior modeling is the process that comes with
identifying, modeling, and documenting the events that
effects each entity and the sequence by which event occur.

I will separate the phases into Stages in Structural System and

Design Approach in order to be easier for you to understanding how
analyst used (SSADA) in planning, improving and initiating a
business system.

 Stage 0
Structural System and Design include the following stages:
Feasibility Study
Note that if the project is small the feasibility may not
necessary, but if large there are main four areas to take into
consideration in these questions:
1) Is the project technically possible?
2) Financial, can the business afford it in term of money?
3) Organizational, can the organization work and compatible with
existing practice?
4) Ethically and socially it is acceptable?
After studying these question and answering them we can
save them into formal document (it should be formal) to be in
the safe side and giving constructions and detail if any
rejection and we should give reasons.
There must be some form of investigation the goals and
implementation of the project.

 Stage 1
Investigation of the current environment, as we know the new
system may different in though, task, and objective from the
old system. Because the base data would be change a little
very little from the previous system there must be problem
identification in order to build up the new solution. At this
stage we should understand the forms of current system by:
1. Interviewing employees.
2. Circulatory questionnaire.
3. Observation.
4. The existing documents to understand the system at a
starting phase.
This serves many purposes such as:
o Users catalog of current system, describing the user's
interaction with the system and how they interact.
o Current environment (ERD) and Logical data structure
o Data Flow diagram (DFD) further redundancy removed if
needed
o Leveled the DFD for current logical system
o Full data dictionary between data store(Database) and
entity
o The Model diagram of (DFD) is the current physical
model that shows the old system how is implemented.

 Stage 2
Business System option
This is brainstorming session, in which the analyst after
interviewing the current system, he must decide on overall
design of the new system solution that the
organization/Company or institution could implement it. To do
this, he/she, should see the outputs of the previous stage and
develop two or three new business options, which is later on
represented to the user.
The options should be considered with the following:
o The automation degree of the system
o The boundary between the system and user
o The distribution (how many offices will use it, if
centralized or across several)
o Cost/Benefit
o Impact of the new system. It is necessary that the
option documented, with a logical data structures, and
the level 1 data flow diagram. Then the user and analyst
chose a single business option.
The output of this stage is the single selected of business
option, with all the outputs of the feasibility stage.

 Stage 3
Requirements Specification
Full logical specification which includes what the system will
do with free of errors, ambiguity, and inconsistency after the
brainstorming to produce the new (DFD, ELH, ERD, etc) DFD
is shown in the figure 0.0 depending on the software system
that being used.
Figure 0.0 Sales
DFD Exampleprocess

Suppliers

Accountin
g record

Command Management

Inventory

Information
System

This Figure shows a sales system processes that consist of

Five offices sharing information about (sales records,
accounting records, inventory replacement, suppliers, and the
Management information system) future planning process of
activities.
Entity Life History (ELH) for another example in bank account
history activities shown in figure 0.1 below,
Figure 0.1
Entity Life History

Account
open

Bank
Account

Account
life

Account
Close

Account
deleted

Transactio
n

Deposit
Fund

Withdraw
Funds

Make
direct
Payment

Cached

First the user enters the customer's account, selecting one

option depending on customers order, and makes neither the
8

transaction nor it can be a machine such as ATM where the

customer enters the data.
ERD Example would be the relationships between the tables in
a system such as:

This is an example an insurance company which may operate

with four forms, (recording the hospital details, customer
detail, employee details and the government tax detail) which
up to four offices recording.
The product of this stage a complete requirement specification
document which made up of:
o
o
o
o
o
o
o
o

Data Catalog (updated)

Requirement Catalog (Updated)
The processing specification which made of:
User role/ Function Matrix
Function definition
Require logical data model
Entity life Diagram
Effect correspondence diagram

 Stage 4
Technical System Option

This stage is the physical implementation of the new system.

Creating two or three to present to the user from which the final
option is chosen with respect to the following
o
o
o
o
o
o
o

Hardware architecture
Software to use
Cost of implementation
Staffing required
Space of the system/Capacity
Network needed
Human Computed Interface

All of this aspect must be confirmed to any constraints imposed by

business such as valuable money and standardization of hardware
and software.

10

 Stage 5
Logical Design

The logical Data design specifies the main methods of iteration in

term of command structure and menu structure. It the definition
in which the user will interact with the system, analyzing the
events, and inquires about the data. Both of these use the
events, function description and effect correspondence diagram
in stage 3 to determine how to update and the need of secure.

The product of this stage is the logical design which made up of:
Data catalog
Required logical data structure
Logical data structure
Logical process model includes dialogue and model for the
update and inquiry process
o Stress and binding moment
o
o
o
o

11

 Stage 6
Physical Design

This is the final step where all the logical specification of the
system is converted to hardware and software. The physical data
structure is optimized to meet size and performance
requirements.

The Product of this stage is the final complete physical design. In

my point of view the best chosen project design in is the
manufacturer processes as shown in the figure 0.0.

References: some information are available on the internet,

"Wikipedia"

12

Chapter 2
PERT is the collection time duration of any project, specific task
time, and breakdown structure. Its the Technique that uses
optimistic, pessimistic, and realistic time estimated to calculate the
expected time for a particular task.
It helps determining better time estimation when there is
uncertainly as how much times the tasks to be accomplished.
The formula of calculating the Expected time (ET) is = Optimistic +
4 (realistic) + pessimistic. Once we add these values together, it
must be divided by 6. Technique can help us to obtain a better time
estimate when there is some uncertainty as to how much task will
require to be completed.
As expected time (ES) can be calculated, because the expected
completion time should be close to the realistic time, it is typically
weighted four times more than the optimistic (o) and pessimistic(p)
times. Once we add these values together, it must be divided by 6
to determine the ET. This equation is shown in the following formula
ET =

o+4 r + p
6

Where
ET = Expected time for a completion foe an activity
O = Optimistic completion time for an activity
R= Realistic time for an activity
P=Pessimistic time for an activity
For example, suppose that that POV is asking you to do a Sales
Promotion Tracking System (SPTS) before 24 weeks to develop and

13

implement the system The project Manager, Jim Woo after knowing
the deadline of 24 weeks he knows that the next step is to:
1) Gantt Chart
2) Network Diagram

Activity

Activity

ET

Name
Require

collection
Screen

Design
Report

Design
Database

Design
User

5.5

Documenta
6

tion
Programmin

7
8

g
Testing
Installation

1
1

3
1

5
1

3
1

1) Discussion with the Team Management about the SPTS, sales

and development staff.
2) Identify the earliest time which is 24 weeks
3) Gantt Chart and Network Diagram
4) Finding the critical path equal to 22 and slack time
The Project Management Software automates these activities
time.

14

But if we want to calculate them manually the calculation will be

as follow
R= 4
Activity 1) (1+ 5r + 9) /6 = 20/6 = 5
Activity 2) (5 + 6r + 7)/6 = 6
Activity 3) (3 + 6r + 9)/6 = 36/6 = 6
Activity4) (1 + 2r + 3)/6 = 12/6 = 2
Activity5) (3 + 6r + 7)/6 = 34/6 = 5.67 = 6
Activity6) (4 + 5r + 6)/6 =30/6 = 5
Activity 7) (1+ 3r + 5)/6 = 18/6 = 3
Activity 8) (1 +1r + 1)/6 = 6/6 =1
Before the summation, there are Critical activities and non
Critical activities; we must add the whole critical activities
together. In this case the noncritical activity is the fifth activity,
which is the user documentation that will not delay the project. In
addition the Network draw shows the parallels activities below
8

5
4

1
3

15

The Line shows the Critical Path 1 , 2, 3, 4, 6, 7, 8 without the 5

activity so now we can calculate the highest time in activities 2
and 3 which is the same 6 followed by activity 6 + 7 and finally 8
So ET of critical path = ET of activity 1 + ET of activity 2 or 3 +
ET of activity 4 + ET of activity 6 + ET of activity 7 + ET of
activity 8 => 5 + 6 + 2 + 5 + 3 + 1 = 22
Summation of the activity =
1)
2)
3)
4)
5)
6)
7)
8)

Requirements collection
Screen design
Report Design
Database Design
User Documentation
Programming
Testing
Installation

16