3.  Analysis- separation of a substance into parts for
study and interpretation; detailed examination.
 substance- business system
 Parts – various subsystem
 we are defining systems analysis as that part of the
process of systems development that begins with the
feasibility study and ends with the production of
target document.

4.  A systems analyst will be required to perform a
number of different tasks in carrying out the analysis
phase of a development project.
 5 areas have been identified into which these
tasks can be grouped.

7. B model
 Waterfall
 V model
 Spiral model

8.  Traditional
approach
Analysis requirement
Specify requirement
Produce high level design

10.  Modeling
 Partitioning
 iteration

11.  Planning the approach
 Asking questions and collecting data
 Recording the information
 Interpreting the information collected
 Specifying the requirement

12.  “failure to prepare is to prepare to fail”.
 What type of information is required?
 What are the constraints on the investigation?
 What are the potential problems that may make the
task more difficult?

13.  As part of the planning process, analysts must
ensure that:
 They understand the objectives and terms of
reference agreed with the client;
 They are aware of constraints that affect the
analysis process;
 They plan the research, initial contact and
other tasks to be completed during the
investigation and manage time appropriately.

14.  Who initiated the project?
 What is their role in the organisation?
 What are their objectives for the project?
 What are the company objectives?

15.  The stated objectives of the client will usually
be recorded in the terms of reference.
 Defines SCOPE Of system.
System boundary.
Constraints.
Objectives.
Permission.
End product.

16.  Ifno written terms of reference exist, the
analysis team would be well advised to prepare
a draft based on their understanding and
present it to the client for agreement.

19.  Gather information
 face-to-face contact with the client.
 Focus on confidentiality, integrity, respect and
confidence-building.
 Recognise expertise in the users and welcome their
input.
 Have as a key objective the need to build the client‟s
confidence.
 Keep everybody informed. This includes client contacts
and project staff.
 Be discreet and diplomatic.
 Double-check any information gathered.

20.  Effective
use of time.
List objectives and set priorities.
Make a daily „to do‟ list.
Handle paper only once.
Set and keep deadlines.
Always carry a notebook .
Do it now .

21.  Small- scale system analysis.
 Analysts should concentrate on providing the answers
to four key questions:
 How much? The cost of the new system.
 What? The objectives of the new system.
 When? The delivery timescale.
 How? The means and procedures used to produce the
new system.

22.  The feasibility study report has to address three
levels of feasibility:
 Technical feasibility.
 Business feasibility.
 Functional feasibility

24.  Background
Terms of reference.
Reasons for the study.
 The current situation
Overview of current situation.
Problems and requirements identified.

25.  Proposed solution
Technical implications.
Operational implications.
Cost implications.
 Cost– benefit analysis
 Recommendations