Page 51 - DCAP205_DCAP409_ANALYSIS_AND_DESIGN_OF_INFORMATION_SYSTEMS
P. 51
Mithilesh Kumar Dubey, Lovely Professional University Unit 3: Analysis
Unit 3: Analysis Notes
CONTENTS
Objectives
Introduction
3.1 Preliminary Investigation
3.2 Scope of Study
3.3 Conducting the Investigation
3.4 Testing Project Feasibility
3.5 Handling Infeasible Projects
3.6 Summary
3.7 Keywords
3.8 Review Questions
3.9 Further Readings
Objectives
After studying this unit, you will be able to:
Understand the concept of preliminary investigation
Recognize the scope of study
Discuss the conducting the investigation
Understand the testing project feasibility
Discuss the handling infeasible projects
Introduction
After the feasibility study, the analyst takes the formal acceptance of the proposed system from
the requested department. The next step is to study the current system in detail, so that the
system requirements can be determined. During systems analysis, the analyst obtains actual
specifications of the system by clearly understanding the needs of the users. After analysis, a
document is prepared by the analyst, which is called as Software Requirement Specification
(SRS) document.
Many methods and languages have been developed for requirements analysis. Structured
Analysis and Design Technique (SADT) – simply called as ‘Structured Analysis’ – is the most
commonly used method for analysis. We will discuss this method later. Problem Statement
Language (PSL) and Requirements Statement Language (RSL) are some of the languages developed
for specifying the requirements. PSL is fundamentally the same as the structured analysis, but it
is purely textual whereas structured analysis uses both text and graphics. RSL has been specially
designed for specifying the requirements of real time control systems.
Data collection is an important part of feasibility analysis and systems analysis phase of SDLC.
Many techniques are used for collection of data, which are commonly known as fact finding
techniques.
LOVELY PROFESSIONAL UNIVERSITY 45