SYSTEM AND DESIGN 5

System Analysis and Design Unit 5

Sikkim Manipal University Page No. 95

Unit 5 The Systems Development Life Cycle

Structure: 5.1 Introduction

Objectives

5.2 System Development Life Cycle

Feasibility

Analysis

Design

Testing

Implementation

Maintenance

5.3 Requirements Determination

Requirements specification

Steps to determine requirements

5.4 Feasibility Analysis

Steps in feasibility analysis

Types of feasibility

Final specification

5.5 Hardware and Software Study

5.6 Role of Systems Analyst

5.7 Attributes of a Systems Analyst

5.8 Tools Used in System Analysis

Onsite observation

Interviews

Questionnaires

5.9 Summary

5.10 Glossary

5.11 Terminal Questions

5.12 Answers

5.13 References

5.1 Introduction

To understand system development, it is important to know that every

system has a life cycle, similar to a living system. The life cycle is a

systematic composition of several phases of system development one after



the other. The analyst must move on from one phase to another

systematically, solving key problems and attaining results in each phase.

In the previous unit, you learned the concept of system architecture

construct. You also studied the system entity relationships and guiding

principles followed in architecture of systems.

To continue further, you will now learn about the systems development life

cycle in this unit. Here, you will study various phases of systems

development life cycle such as feasibility, analysis, planning, design,

implementation, testing, and maintenance. Also, you will find out the use of

hardware and software study in the development process. You will also

study the role and attributes of systems analyst, and finally, the tools used in

system analysis.

Objectives:

After studying this unit, you should be able to:

evaluate the phases of system development life cycle

discuss requirements determination and requirements specification

explain the concept of feasibility analysis

discuss final specifications

discuss hardware and software study

recognise the role of systems analyst and attributes of a systems analyst

tools used in system analysis

5.2 System Development Life Cycle

System development is quite a challenging and difficult task. In developing a

big integrated system, like MIS, a lot of people are involved and several

months or even years are devoted for completion. But, a small autonomous

application, like payroll, can be generated in a number of weeks or months

by a single or only a few programmers. For these kinds of small systems,

system development activities may be performed perfectly without

appropriate documentation. But, for big systems, these activities must be

performed unambiguously with appropriate preparation and documentation.

In both small and large systems, system development rotates about a life

cycle that starts with the identification of users' requirements and

recognising their difficulties. Such a life cycle including numerous phases is

known as System Development Life Cycle (SDLC).

Ankit PrajapatiHighlight



System development starts with the finding of user requirements, followed

by a series of activities which are executed step by step. The fundamental

phases that are needed for developing a system are displayed in figure 5.1.

Figure 5.1: Various Phases of SDLC

Now let us study these phases in detail.

5.2.1 Feasibility

The systems development cycle begins with the identification of

organisations objective and the nature and scope of the problem under

study. Based on the outcomes of the initial investigation, the inspection is

extended to a comprehensive feasibility study. A feasibility study is defined

as a test of a system proposal in accordance with its function ability effect

on the organisation, capability to fulfil needs of users, and effective

utilisation of resources.

The feasibility study includes three main questions:

What are the users verifiable needs and how does a system fulfil them?

What resources are obtainable for specified systems? Is the trouble

worth solving?






What is the probable effect of the system on the organisation? How

does it fit inside the organisations master plan?

All these questions must be solved with care. They focus on examination

and assessment of the problem, recognition and explanation of systems,

specification of performance and the cost of every system, and final choice

of the finest system.

The aim of a feasibility study is not just to solve the problem but also to

achieve a sense of its scope. In the study, the problem definition is sorted

out and identified and the facets of the problem to be incorporated in the

system are established. Therefore, costs and benefits are predicted with

complete accuracy at this phase.

The outcome of the feasibility study is considered as formal proposal.

This is a formal document specifying the nature and possibility of the

suggested solution. The proposal summarises what is identified and what is

going to be performed.

You will study the concept of feasibility analysis in detail (such as steps

included in feasibility analysis and types of feasibility) later in the unit.

5.2.2 Analysis

The next phase is known as Analysis. It can be considered as a

comprehensive study of numerous operations accomplished by the system

and their association inside and outside of the system. It also involves

understanding the nature of the information and functions of the software

that is required for the system. The main question is: what to do to solve the

problem?

One facet of analysis is specifying the limitations of the system and

identifying whether or not a system should take into account other related

systems. During analysis, data is gathered on accessible files and

transactions managed by the existing system.

It needs special skills and understanding by the analyst of the subjects

being interviewed. Prejudice of the analyst in data gathering and its

interpretation can be a problem. Training, experience and common sense

are needed for compilation of the information required to perform analysis.

After completing the analysis, the analyst has a clear understanding of what

is to be performed.













After the systems analyst has decided that the requested system is feasible

and the management has permitted to carry on the development procedure,

then SDLC goes into its next phase of requirements determination and

prepares a Software Requirements Specification (SRS) document. Once the

SRS Document is prepared, the analyst moves on to the design phase

where the total cost of the system is estimated.

You will study in detail the concept of requirements determination and

requirements specification later in the unit.

5.2.3 Design

The next phase that comes after analysis is system design. After completion

of Software Requirements Specification (SRS) document in analysis phase,

the analyst makes a plan to handle the software project. System planning is

considered as the most essential part of the design phase.

System planning involves the total cost estimation of developing the system

together with the estimation of total time period needed. A project team is

finalised with complete staff needed for each phase. Now, the analyst

decides how the problem can be solved. Therefore, in the systems design

phase, we shift from the logical to the physical aspects of the life cycle.

System design is considered as the most inventive and challenging phase of

the system life cycle. The term design portrays a final system and a method

by which it is developed. It points to the technical specifications (similar to

the engineers proposals) that will be applied in executing the system. It also

involves the building of programs and program testing. The steps taken in

system design are shown in figure 5.2.














Figure 5.2: Steps in System Design

First, the system analyst finds out how the output is to be generated and in

what kind of format. The samples of the output (and input) are also

available. The next step is to design input data and master files (database)

to fulfil the needs of the projected output. The operational (processing)

phase is managed via program construction and testing, involving a list of

the programs required to fulfil the systems goals and to complete the

documentation.

Finally, details associated with validation of the system and a prediction of

the impact of the system on the client and the organisation are documented

and assessed by management as a step toward implementation.

1

Detailed System

Documentation

Output

Design

Cost

Justification and

System Design

Input

Design

Design

Submitted to

Management

for Approval File

Design

Form

Analysis

Design

Accepted?

Abandon

Project

No

Yes

Test

Programs

Go to

implementation

Output

Design



The concluding report previous to the implementation phase involves

procedural flowcharts, record outlines, and a functional plan for executing

the system. Information on personnel, money, hardware, amenities and their

predictable cost must also be available. Now, predictable costs must be

close to decided costs of implementation.

In some companies, separate groups of programmers perform the

programming while other companies employ analyst programmers who

perform analysis and design in addition to code programs.

Here, we are assuming that analysis and programming are carried out by

two different persons. There are some functions that the analyst must carry

out while programs are being written. In design phase, safety and auditing

measures must also be developed.

5.2.4 Testing

Testing is considered as the most crucial phase of SDLC. In this phase, the

analyst test the whole system with different methods to make sure that the

system is error free. Though, the programmers test their programs in design

phase, but this kind of testing is usually not systematised and is without

using test data.

In testing phase, the testing is performed in methodical and organised

manner so as to make sure the consistency of the system and to make it

error-free. The main goal of testing is to discover all probable errors that can

take place at some stage in implementation of the system.

In case of final testing, user acceptance is tested, and then comes the turn

for user training testing. Based on the nature of the system, you may need

extensive user training. Conversion generally occurs at around the same

time the user is being trained or later.

System testing verifies the readiness and correctness of the system to

access, update, and extract data from new files. Once the programs

become available, test data are read into the computer and processed

against the file(s) offered for testing. The program(s) then run with live

data. Or else, a diagnostic process is used to find and correct errors in the

program.

In most programs, we perform a parallel run where the new system runs

parallelly with the old systems. This method, however expensive, offers












added assurance against errors in the system and also provides the users

chance to have experience via operation in some cases.

Practically, parallel processing is not possible. For example, it is not

possible to execute two parallel online point-to-sale (POS) systems for a

retail chain. In any case, the old system is phased out after the new system

proves itself reliable.

5.2.5 Implementation

Implementation phase is considered to be less inventive as compared to

system design. It is mainly associated with user training, site preparation,

and file conversion. When the system is connected to workstations and

remote sites, the telecommunication system and tests of the systems

together with the system are also involved in implementation. It comprises

testing and maintenance of the system.

5.2.6 Maintenance

After completing the installation phase and adaptation of user staff to

changes in the system, we carry out assessment and maintenance of the

system. If there is confliction between new information with the design

specifications, modifications have to be made. Hardware also needs

intervallic maintenance to keep in time with design specification. The

significance of maintenance is to keep the new system to latest standards.

User preference, modifications in organisational needs or environmental

factors also require system enhancements. There is a big difference

between maintenance and enhancement. Let us illustrate this with an

example.

An Example: Let us say a bank decides to increase its service charges of

checking accounts from `3.00 to `4.00 for a minimum amount of `100,000; it

is considered as maintenance. But, if the same bank decided to provide a

personal loan on negative balances, it is enhancement. This change needs

assessment, program alterations and future testing.

Now you will study the concept of requirements determination and

requirements specification in the next section.









Self Assessment Questions

1. In _________________ phase, data are gathered on accessible files,

decision points, and transactions managed by the existing system.

2. During testing phase, the testing is not performed in methodical and

ordered manner and does not make it error free. (True/ False)

3. In the stage of _________________, costs and benefits are predicted

with greater correctness.

5.3 Requirements Determination

Requirements determination is the initial sub phase of analysis. In this sub

phase, analysts should gather information on what the system should do

from as many sources as possible. There are some traditional methods to

help collecting system requirements, such as interviewing, survey, directly

observing users, etc.

Requirements Determination phase involves studying of current system in

detail and gathering data so as to discover the requirements of the users.

You can also call this phase as Requirements Analysis. The main goal of

requirements analysis is to recognise 'what' is required from the system.

Throughout this phase, the analyst recognises the comprehensive

requirements of the users.

Figure 5.3: Requirement Analysis Process



Requirements analysis encompasses various tasks that go into finding the

needs to meet for a new or modified product, taking into account all the

possible requirements of the different stakeholders.

The process starts with an activity diagram containing details. During the

requirements analysis process for modelling of process-aware system(A

Process-Aware System is a software system that manages and executes

operational processes involving people, applications, and/or information

sources on the basis of process models), the functional requirements are

raised and specified from process diagrams and then the information is

specified. Eventually, data modelling is executed by following a set of

standard guidelines.

Graphical representation of information offers a very efficient means for

demonstrating information to both users and system developers. Therefore,

the data model provides the details of information to be stored, and is of

primary use when the final product is the generated.

As shown in figure 5.3, requirement method is applied in the requirements

analysis process. The method is an integrated approach to development

that brings forth a balanced solution to meeting the requirements at hand.

System or Requirements analysis phase comprises two sub-phases

Problem Analysis

Requirements Specification

In problem analysis, the analyst recognises the current system for locating

the needs of the proposed new system (at times also known as system).

5.3.1 Requirements specification

Requirements Specification is considered as the activity that the systems

analyst utilises to clearly record and document the needs either during or

after the extraction and guarantee of activities. This activity is most

frequently connected with automated computer aided software engineering

(CASE) technology.

In requirements specifications, the analyst records all the requirements in a

document known as Software Requirements Specifications (SRS)

document. The SRS is authenticated by the users by assessing their

requirements stated in analysis.



Attributes of well written SRS: Various attributes of a well written Software

Requirements Specification are;

Correctness

Unambiguous

Verifiability

Understandable by customers

Consistency

Conciseness

Modifiability

5.3.2 Steps to determine requirements

We follow the following steps to determine the requirements.

Plan/Manage: To prepare for and manage the requirements

Obtain: Collect information from various sources

Understand: Analyse the obtained Information

Validate: Confirm mutual understanding of the requirements

Evaluate: Assess the process


4. The main purpose of _____________ is to recognise the requirements

from the system.

5. The Software Requirements Specifications (SRS) document is

authenticated by the users by assessing their requirements mentioned

in analysis phase. (True/False)

5.4 Feasibility Analysis

Feasibility analysis is the process by which feasibility is measured. It is an

ongoing process done frequently during systems development projects in

order to achieve a creeping commitment (Creeping commitment describes

the involvement of the end user in the systems testing process) from the

user and to continually assess the status of the project. The measurement

of feasibility is known as feasibility study.



Figure 5.4: Feasibility Analysis Workflow

Feasibility study highlights the costs of the project and the time taken to

deliver the project and thus implies whether the project is feasible in terms

of time and costs or not. Figure 5.4 shows a workflow example in feasibility

analysis. Let us now study the steps included in feasibility analysis and

types of feasibility.

5.4.1 Steps in feasibility analysis

Feasibility analysis consists of the following steps:

1. Create a project team and employ a project leader: First of all,

project management group generates different teams for independent

projects. Every project team contains one or more systems analysts

and programmers along with a project leader. The project leader is

accountable for planning and organising the expansion activities of the

system.

2. Begin preliminary investigation: Every project teams systems

analyst begins preliminary investigations via various fact finding

methods.

3. Set up the existing systems flowchart: After the second step, the

analysts arrange the systems flowchart of the existing system. These

charts depict the common functioning of the system in a graphical

manner.



4. Illustrate the deficiencies in the existing system: On learning the

systems flowcharts, the analysts recognise and depict the deficiencies

in the existing system.

5. Determine goals of the proposed system: The main goals of the

projected systems are listed by each analyst and are discussed with

the project leader.

6. Set up the proposed systems flowchart: After identifying the main

goals of the projected system, the analysts make their systems

flowcharts. Systems flowcharts of the projected system are compared

with those of existing system so as to make sure that they fulfil the

goals.

7. Determine the technical feasibility: The current computer systems

(hardware and software) of the associated departments are studied

and their technical specifications are noted. The analysts decide

whether the current systems are enough for the technical requirements

of the projected system or not.

8. Determine the economic feasibility: The analysts establish the costs

and advantages of projected system so as to make sure that the

project is economically feasible.

9. Determine the operational feasibility: Now the analysts recognise

the users of the system and therefore find out the operational feasibility

of the project.

10. Presentation of feasibility analysis: Throughout the feasibility study,

the analysts also continue making the feasibility study report. At the

finish point of feasibility analysis, the feasibility analysis report is

provided to the management together with the oral presentation.

5.4.2 Types of feasibility

The analyst takes into account the three main types of feasibility, analysis

technical, economical and operational feasibility, all of which are

interconnected. Let us discuss these types of feasibility in detail.

1. Technical feasibility: In technical feasibility, the analyst studies the

current systems (hardware and software) of the associated departments

and identifies whether these technical resources are enough for the



projected system or not. If they are not enough, the analyst recommends

the configuration of the systems that are needed.

2. Economic feasibility: Economic feasibility is the most significant study

that identifies the cost and benefits of the projected system and

contrasts with the budget. The cost of the project should not overshadow

the budget. The cost of the project involves the cost of hardware,

software, expansion and implementation.

3. Operational feasibility: When it is established that the project is both

economically as well as technically feasible, the next step is to find out

whether it is operationally feasible or not. In operational feasibility study,

it is identified whether the system will function in the manner that user

requires.

After the feasibility study, we make a document called Feasibility Study

Report. Apart from this report, the analyst also provides the oral

presentation of feasibility study to the management.

5.4.3 Final specification

Final specifications of the proposed system play an important role in

determining the achievements that a system will produce.

Specifications specify what the system would attain.

Specifications made are enhanced for implementation.

Software requirement specification (SRS) is written and provided to the

user and finally an agreement is reached.


6. To fulfil the goals, systems flowcharts of the projected system are not

compared with those of existing system. (True/ False)

7. ___________________ feasibility identifies the cost and advantages of

the projected system and compares with the budget.

5.5 Hardware and Software Study

To implement the proposed system:

You should find out the hardware and software required to

implementation application.



You should first find out the response time, quantity of data to be

processed, frequency of reports etc. and then choose the hardware.

Technical feasibility is associated with the hardware and mechanical

components required so as to produce the proposed system. The software

is also significant and essential for developing system. You cannot

implement the system without any hardware or software.

Thus, the cost of the hardware and software should be involved into the

economic feasibility. You will assign suitable amount of the hardware and

software for implementing the system successfully and competently. The

assessment of the hardware and software will offer the comfort to the user

in determining the budget of the system.

Now, we will discuss the role and attributes of systems analyst, and tools

used in system analysis in the next sections.


8. The hardware and software are not required for implementing the

proposed system. (True/False)

9. The cost of the ____________ and _____________ should be involved

into the economic feasibility.

5.6 Role of Systems Analyst

A systems analyst is the one who carries out a study, determines activities

and goals, and identifies a process to attain the goals of a system. The

functions of the systems analyst involve designing and implementing

systems to go well with organisational requirements. Systems analyst plays

a main role in obtaining business advantage from computer technology. The

analyst is a person with exclusive skills. He utilises these skills to organise

the efforts of different people in an organisation to attain business

objectives.

A systems analyst has a very responsible role in system development. See

figure 5.5 for an example.



Figure 5.5: Various Tasks of a Systems Analyst

Now, let us study various tasks performed by a systems analyst:

(a) The first and possibly the most complicated task of systems analyst is

problem definition. System problems are pretty complex to define. It is

also a fact that problems cannot be solved until they are accurately and

evidently defined.

(b) At first, a systems analyst does not conceptualise how to solve a

particular problem. Analyst must discuss with managers, users and other

data processing users in defining problems and generating solutions. He

makes use of various techniques for data collection to obtain an

accurate explanation of a problem.

(c) By collecting the data related to a problem, the systems analyst

analyses them and device a plan to solve it. He may not have the best

idea of solving a problem but takes the ideas of other people and

process them until a feasible solution is attained.

(d) Systems analysts coordinate the process of developing solutions. Since,

many problems have number of solutions; the systems analyst must

evaluate the merit of such proposed solutions before recommending one

to the management.

(e) Systems analysts are frequently known as planners. A main part of the

systems analyst's task is to build up a plan to fulfil the goals of the

management.



(f) When the plan has been received, systems analyst is accountable for

designing to make the management's goal attainable. Systems design is

a time taking, difficult and a precise job.

(g) Systems must be tested systematically. The systems analyst frequently

coordinates the testing process and assists in checking whether the new

system is fulfilling the standards recognised in the planning stage or not.


10. Systems analyst's main task is to build up a plan to fulfil the

management's goals. (True/False)

11. Systems analysts are frequently known as _____________________.

5.7 Attributes of a Systems Analyst

A Systems analyst must have several skills to efficiently carry out his job.

These can be broadly divided into two categories: technical and

interpersonal skills. Examples of technical skills are project management,

problem solving, dynamic interface, questioning attitude, inquiring mind,

creativity, business function and knowledge of the computer. Interpersonal

skills deal with relationships and the interaction of the analyst with people in

business.

Examples are communication, understanding, teaching and selling. A

systems analyst, to be successful, must possess the following attributes:

Knowledge of people: As a systems analyst works with others very

closely, he or she must know their needs correctly.

Business functions knowledge: A systems analyst must understand

the surroundings in which he functions. Analyst must know the traits of

management and the users and recognise how they respond to him. A

functioning knowledge of accounting and marketing rules are

compulsory, as so many systems are constructed around these two

regions.

Data processing principles knowledge: Most systems nowadays are

based on computers. The systems analyst must be well versed with the

capabilities and limitations of computers.

Capability to communicate: Being a controller, a systems analyst must

interact properly with people of different levels inside an organisation.



Systems analyst must pay attention and listen carefully to what others

say and integrate the feedback of others into the systems development

procedure.

Flexibility: Systems analysts must be flexible in their thoughts as they

frequently have to compromise. Different groups in an organisation have

contradictory needs and most systems are developed after negotiation

and compromise between various groups. The goal of an analyst is to

develop the system that will be best suited for the organisation. This

needs an open mind and flexibility in the thoughts.

An analytical mind: It needs an extraordinary person to observe the

problems facing by an organisation and produce solutions. Systems

analysts frequently find themselves with more data than they can

manage. It needs an analytical mind to choose applicable data and

focus on it in defining problems and developing solutions.

Well educated with quick mind: Systems analysts works with people

at all levels almost in every part of business. They must learn how to

work with all of them and achieve their confidence. Analysts must have

sharp mind to study quickly how people perform their tasks and

generate methods for them to perform it in a better way.


12. It is not necessary for a systems analyst to interact properly with people

at different levels in an organisation. (True/False)

13. Systems analysts generally find themselves with more _____________

than they can manage with.

5.8 Tools Used in System Analysis

On-site observation, interviews and questionnaire are the tools used in

system analysis. Let us study these in detail.

5.8.1 Onsite observation

Onsite Observation is an information gathering tool used in system analysis.

It is the process of identifying and observing people, objects and incidences

to attain information. The role of analyst is that of an information seeker who

has no relation with the system that is being observed. In this role he can

mix openly with the users.



The main goal of onsite observation is to gets as close to the real system

being studied as possible. Thus, it is significant that the analyst should be

well-informed about the common structure and activities of the system. The

questions given below can serve as an instructional guide for onsite

observations:

What type of system is it? What does it do?

Who executes the system? Who are the important people in it?

What is the past of the system? How did it reach to its current level of

development?

Besides its formal function, what type of system is it as compared with

other systems in the organisation? Is it a primary or a secondary

provider to the organisation? Is it quick paced or is it a laid-back system

that reacts slowly to outside emergency?

The analyst follows some rules as an observer. When making observations,

he is more expected to listen than talk and to listen with real interest when

information is communicated. The importance is not on providing advice or

passing moral verdict on what is observed.

Onsite observation in a complex circumstance can be extremely time-

consuming. Suitable sampling procedures must be utilised to determine the

stability.

5.8.2 Interviews

Interview is another tool used in system analysis. The interview is a person-

to-person, inter-personal situation where a person (known the interviewer)

asks a person being interviewed; questions intended to obtain information

regarding a problem part. The interview is the oldest and most frequently

utilised tool for collecting information. It has traits that behavioural and

onsite observations do not contain. It can be utilised for two main purposes:

You can use this tool as an examining tool to recognise relations or

verify information

You can also use this tool to capture information as it occurs.

Validity is not a small problem. Special precautions are taken to get rid of

interview partiality. We presume that more the information is applicable, the

more generously it is provided. Such a supposition stresses the controlled



character of the interview as a relationship freely and readily entered into by

the respondent.

In an interview, as the interviewer and the person interviewed meet face to

face, there is a chance of flexibility in extracting information. The analyst is

also in a situation to examine the subject. On the contrary, the information

acquired via a questionnaire is restricted to the subjects' written responses

to predefined questions.

There are four main benefits of interview.

The flexibility of an interview makes it a better technique for discovering

areas, where not much is identified regarding what questions to ask or

how to invent questions.

It provides a better chance than the questionnaire to assess the validity

of the information collected. The interviewer can observe what subjects

say along with how they say it.

It is an efficient technique for extracting information regarding difficult

subjects and for exploring the sentiments underlying expressed

outlooks.

Many people feel good being interviewed irrespective of the subject.

They typically assist in a study, when all they have to do is speak. On

the contrary, the percentage of returns to a questionnaire is

comparatively low, frequently less than 20 per cent.

The main disadvantage of interviews is an extensive preparation time.

Interviews also take time to carry out, which signifies more time and money.

Thus, whenever a more economic option is available for capturing the

similar information, the interview is usually not used.

5.8.3 Questionnaires

Questionnaire is a tool that has questions to which individuals responds. By

its nature, a questionnaire provides you the following benefits:

It is economical and needs less skill to manage than the interview.

In contrast to the interviews, which normally question one subject at a

time, a questionnaire can be given to a large number of individuals at

the same time.

The standardised language and arrangement of the questions and the

standardised directions for reporting responses guarantee uniformity of



questions. On the contrary, the interview situation is hardly ever

consistent from one interview to the other.

The respondents feel better in the anonymity of a questionnaire as

compared to that of an interview. In an interview, the analyst generally

recognises the user staff by name, job function, or other identification.

By means of questionnaire, respondents provide opinion without fear

that the answer will be associated to their names.

The questionnaire puts less pressure on subjects for instant reactions.

Respondents have time to think and do computations to give more

precise data.

The advantages of self-managed questionnaire surpass the drawbacks,

particularly when cost is a concern. The major drawback is a low percentage

of return. Another drawback is that many people have trouble in articulating

themselves in writing. Due to these drawbacks, interview is perhaps

superior as compared to questionnaire.


14. _____________________ is the procedure of identifying and observing

individuals, objects and incidences to acquire information.

15. A questionnaire cannot be given to a large number of people at the

same time. (True/ False)

5.9 Summary

In case of both small and large systems, system development rotates

about a life cycle that starts with the identification of users' requirements

and recognising their problems. Such a life cycle having numerous

phases is called System Development Life Cycle (SDLC).

A feasibility study is considered as a test of a system proposal in

accordance with its workability effect on the organisation, capability to

fulfil user needs, and efficient use of resources.

In analysis, data is gathered on available files and transactions

managed by the current system.

In system planning, the total cost of generating the software is estimated

together with the total period of the project.



In systems design, we shift from the logical to the physical aspects of

the life cycle.

Implementation phase is mainly related with user training, site

preparation, and file conversion. In testing, whole system is tested with

dissimilar methods to guarantee that the system is error free.

A systems analyst is a one who carries out a study, recognises activities

and goals and determines a process to attain the goals.

5.10 Glossary

Analysis: In analysis, data is gathered on available files, decision

points, and transactions managed by the current system

Feasibility study: A feasibility study is considered as a test of a system

proposal in accordance with its workability effect on the organisation,

capability to fulfil user needs, and efficient use of resources.

Planning: In system planning, the total cost of developing is estimated

together with the total period of the project.

Systems analyst: A systems analyst is one who carries out a study,

recognises activities and goals, and determines a process to attain the

goals.

System Design: In systems design, we shift from the logical to the

physical aspects of the life cycle

Testing: In testing, whole system is tested with different methods to

guarantee that the system is error free.

5.11 Terminal Questions

1. What is feasibility analysis? Discuss the steps used in feasibility

analysis. Also illustrate different types of feasibility.

2. Explain the concept of Planning and Design in system development life

cycle.

3. Illustrate the different tasks carried out by a systems analyst.

4. What are the various attributes of a systems analyst? Illustrate.

5. Make distinction between interviews and questionnaires with examples.



5.12 Answers


1. Analysis

2. False

3. Feasibility

4. Requirements determination

5. True

6. False

7. Economic

8. False

9. Hardware and software

10. True

11. Planners

12. False

13. Data

14. Onsite Observation)

15. False

Terminal Questions

1. A feasibility analysis is considered as a test of a system proposal in

accordance with its workability effect on the organisation, capability to

fulfil user needs, and efficient use of resources. Refer section 5.2.

Steps in Feasibility Analysis involves project team formation, start

Preliminary Investigation, etc. Refer section 5.4.

Various types of feasibility include technical, economical and operational

feasibility. Refer section 5.4.

2. During system planning, the total cost of generating the software is

estimated along with the total period of the project. System design points



to the technical specifications that will be valid in implementing the

system. Refer section5.2.

3. Designing and implementing systems to go well with organisational

requirements are the functions of the systems analyst. He plays a main

role in observing business advantage from computer technology. Refer

section 5.6.

4. Various attributes of systems analyst include Knowledge of people,

Knowledge of Business functions, Knowledge of Data processing

principles, etc. Refer section 5.7.

5. The interview is a person-to-person, interpersonal role condition where

an interviewer asks a person being interviewed; questions intended to

acquire information regarding a problem area. Questionnaire is a term

utilised for approximately any tool that has questions to which individuals

react. Refer section 5.8.

5.13 References

Kenneth, E. Kendall and Julie E. Kendall., Systems Analysis and

Design, 5th Edition, Prentice Hall PTR, 2001

Silver, G. A., and Silver, M. L., System Analysis and Design, Addison-

Wesley Publishing Company, MA, 1989.

Alan, L. Eliason., System Development Analysis, Design and

Development, 1990.

E-References:

www.teach-ict.com

www.http://turguthaspolat.wordpress.com

www.http://www.khuram-shahzad.com

www.gis.geo.uj.edu.pl

Documents

SYSTEM AND DESIGN 5