Вы находитесь на странице: 1из 2

UGANDA MARTYRS UNIVERSITY

NYAMITANGA CAMPUS

BACHELORS OF SCIENCE IN INFORMATION


TECHNOLOGY
PROGRAM: WKD

NAME: HABARUGIRA HYPAX

REG NO: 2017-B072-70007

COURSE UNIT: SYSTESMS ANALYSIS AND DESIGN

Question
1. Why is it that most systems analysts/software developers rarely follow the systems development
life cycle?

1. System Development Life Cycle (SDLC) is a conceptual model which includes policies and
procedures for developing or altering systems throughout their life cycles. SDLC is used by
analysts to develop an information system (Tutorialspoint.com).
An effective System Development Life Cycle (SDLC) should result in a high quality system that
meets customer expectations, reaches completion within time and cost evaluations, and works
effectively and efficiently in the current and planned Information Technology infrastructure.
SDLC includes the following activities, requirements, design, implementation, testing,
deployment, operations, and maintenance. The following are the phases of Systems development
Life Cycle.

However, most systems analysts rarely follow the Systems Development Life Cycle because of
some of the reasons and these include;

Adjusting scope during the life cycle can end/terminate a project hence most systems analysts
rarely follow this model.

It is difficult to measure progress within stages especially when at the designing stage.
High amounts of risk and uncertainty may be generated.
Some working functionality can be developed quickly and early in the life cycle systems analysts
do not need to follow this model since they already have what they are planning to develop.
More resources may be required, which may be expensive for small organizations hence some
stages may be ignored by systems analysts so as to cut the costs.

System architecture or design issues may arise because not all requirements are gathered in the
beginning of the entire life cycle.

Not suitable for smaller projects hence systems analysts designing systems for small organizations
rarely follow this model.

Large number of intermediate stages require excessive documentation which may be tiresome for
systems analysts hence ignoring some the stages of this model.

Once an application is in the testing stage, it is difficult to go back and change a functionality. Can
turn out to be very expensive if requirements are misunderstood hence some systems analysts
rarely follow this model so as to reduce misunderstandings of the system.