Traditional and Agile Systems Analysis Methodologies

This document discusses the traditional and agile systems analysis methodologies. It covers the principles of traditional system development life cycle models and the feasibility study for a system. It also explores the analysis of a system using a suitable methodology and the system design according to user requirements and system requirements.

qwertyuiopasdfghjklzxcvbnmqw
ertyuiopasdfghjklzxcvbnmqwert
yuiopasdfghjklzxcvbnmqwertyui
opasdfghjklzxcvbnmqwertyuiopa
sdfghjklzxcvbnmqwertyuiopasdf
ghjklzxcvbnmqwertyuiopasdfghj
klzxcvbnmqwertyuiopasdfghjklz
xcvbnmqwertyuiopasdfghjklzxcv
bnmqwertyuiopasdfghjklzxcvbn
mqwertyuiopasdfghjklzxcvbnmq
wertyuiopasdfghjklzxcvbnmqwer
tyuiopasdfghjklzxcvbnmqwertyui
opasdfghjklzxcvbnmqwertyuiopa
sdfghjklzxcvbnmqwertyuiopasdf
ghjklzxcvbnmqwertyuiopasdfghj
klzxcvbnmqwertyuiopasdfghjklz
xcvbnmrtyuiopasdfghjklzxcvbnm
qwertyuiopasdfghjklzxcvbnmqw
System Analysis and Design
Database
5/25/2019

Contents
TRADITIONAL AND AGILE SYSTEMS ANALYSIS METHODOLOGIES.........................................................3
TRADITIONAL SYSTEMS ANALYSIS METHODOLOGY...........................................................................3
Principles of Traditional System Development Life Cycle Models.................................................4
AGILE METHODOLOGY......................................................................................................................6
Principles of Agile Methodology Models.......................................................................................7
Comparison & Contrast Between Traditional and Agile Systems....................................................12
FEASIBILITY STUDY FOR A SYSTEM FOR A BUSINESS-RELATED PROBLEM...........................................13
Elements of a Business Case........................................................................................................13
Desirability, Viability and Feasibility of Systems..........................................................................13
Investigation Techniques to Use......................................................................................................14
Criteria to Consider for a Business Case:.........................................................................................14
Vision...........................................................................................................................................14
Goals............................................................................................................................................14
Cost-Benefit Analysis...................................................................................................................15
Benefit.........................................................................................................................................15
Legal............................................................................................................................................15
Economic Considerations............................................................................................................15
Technical Considerations.............................................................................................................16
Operational Considerations.........................................................................................................16
Timeframes Considerations.........................................................................................................16
Organizational Considerations.....................................................................................................17
Security Considerations...............................................................................................................17
Evaluation of Relevance of Feasibility Criteria.................................................................................17
ANALYSIS OF SYSTEM USING SUITABLE METHODOLOGY....................................................................17
Identifying User Requirements........................................................................................................18
User 1 - Management..................................................................................................................18
Requirements...............................................................................................................................18
User 2 – Customer.......................................................................................................................18
User 3 – Supplier..........................................................................................................................19
Identifying System Requirements....................................................................................................19
Functional Requirements.............................................................................................................19
Non-Functional Requirements.....................................................................................................19

Management Requirements........................................................................................................19
Customer Requirements..............................................................................................................20
Supplier Requirements................................................................................................................20
Identifying Constraints.....................................................................................................................20
Roles and Responsibilities............................................................................................................20
Sign off conditions Documentation and Determination..................................................................21
Documentation and Determination.............................................................................................21
Options to the Clint, Nina................................................................................................................22
Criteria to Use to Determine the Suitability of Methodology to Analyse the System......................22
Effectiveness of the analysis in the context of the methodology....................................................23
SYSTEM DESIGN ACCORDING TO USER REQUIREMENTS AND SYSTEM REQUIREMETNS.....................24
Project Plan and Design...................................................................................................................24
Project flow:................................................................................................................................25
Project Flow and Objectives........................................................................................................25
System Design and Document.........................................................................................................26
Interface Design...........................................................................................................................26
Database Design..........................................................................................................................40
Design Documentation....................................................................................................................41
Effectiveness of the System Design with Selected Methodology....................................................41
REFERENCES........................................................................................................................................42
TRADITIONAL AND AGILE SYSTEMS ANALYSIS
METHODOLOGIES
TRADITIONAL SYSTEMS ANALYSIS METHODOLOGY
The traditional software development life cycle has been almost obsolete i
The typical traditional systems lifecycle has become oldest method for information systems
building. However, the same has been in use even today in the projects, medium to larger
complex systems.

Principles of Traditional System Development Life Cycle Models
Waterfall
It is a formal approach considered to build a system, systems development dividing into
formal stages taken sequentially. Here sequentially refers to completing all the activities at
one stage, prior to beginning of the following stage. It shows formal and clear division of
labour in between information systems specialists and end users. This model emphasizes
paperwork with detailed formal specifications generating and accumulating several
documents in the system project course.
Once the system gets installed and enters into production, a formal post implementation audit
takes place with technical specialists and users to determine whether the original objectives
are met and how is it done, along with the exploration of the need for modifications or
revisions. Then the system would be fine tuned in terms of meeting the requirements,
correcting the errors, improvement