System Analysis and Design: Evaluation of SDLC Models and Feasibility Report Components

Table of Contents
1. Task 1................................................................................................................................................2
1.1 Evaluation of various systems lifecycle models.............................................................2
1.2 Discussion about the significance of software development life cycle in
investigation of developing system...............................................................................................7
2. Task 2................................................................................................................................................7
2.1 Discussion on the components of a feasibility report...................................................7
2.2 Investigating the effects of various feasibility criteria towards developing system
9
3. Task 1..............................................................................................................................................11
3.1 Introduction............................................................................................................................11
3.1.1 Aim...................................................................................................................................11
3.1.2 Project Scope.................................................................................................................11
3.1.3 Abbreviations, Acronyms and Definitions..............................................................12
3.1.4 Overview of the Project...............................................................................................12
3.2 Overall Description of Proposed System........................................................................12
3.2.1 General Description about Project...........................................................................12
3.2.2 Hardware Interfaces.....................................................................................................12
3.2.3 Software Interfaces.......................................................................................................12
3.2.4 Product capabilities......................................................................................................13
3.3 ERD..........................................................................................................................................14
3.3.1 Context Level DFD........................................................................................................14
3.3.2 Data flow Diagram.........................................................................................................15
3.4 System Specific Requirements.........................................................................................19
3.4.1 External Interfaces of Proposed System.................................................................19
3.4.2 Software Interfaces.......................................................................................................19
3.4.3 Hardware Interfaces.....................................................................................................19
3.4.4 User Interfaces...............................................................................................................19
3.4.5 Functional Requirements............................................................................................19
3.4.6 Non-functional Requirements....................................................................................21
3.4.7 Evaluation of User System Requirements through Verification and Validation
Process 21
1

References.............................................................................................................................................22
1. Task 1
1.1 Evaluation of various systems lifecycle models
To design and develop customized software product, SDLC methodology is applied for
build structure, plan design and control the entire software development process (Writer, 2018).
It makes the software product as a standardized. Basically there are 6 software development life
cycle models presented. Among them choosing the best one is not an easy task. We have to
compare all the SDLC models and analyze their advantages and disadvantages (iqbal, 2018).
Waterfall Model
In SDLC models, it is a very simple methodology to process. It follows easy classic life
cycle phases. Another name of this models is 'Linear-sequential' life cycle model. There are 6
phases in Waterfall model (Architects, 2018). Each phase of actions should be carried out
completely before entering into next phase. The verification and validation process can be done
by review team at the end of each phases of model. It helps to check that the project is on right
track. The following figure shows that the steps involved in this model (Hayakawa and
Matsukura, 2010).
Pros:
1. Simplicity; It is easy to understand by developer
2

2. Each phases of product is developed separately because they are independent each
other.
3. This models suits for small project which carried out with clear requirements.
Cons:
1. As each phases work independently, the error or no output can be obtained when
integrating them together. So high level of risk is involved in this model.
2. It does not suitable for big projects.
Iterative model
Another name of iterative model is 'Multi waterfall model' life cycle (Testing Excellence,
2018). Cycles are spitted into small. These cycles are managed iteratively. At the end of each
iteration process, a working on a series of phases will be carried out. So on each end of cycle, a
working output software can be obtained as a result. The figure of iterative model is given below
(Verma, 2018).
Pros:
1. When the life cycle is being processed, the output or working software can be obtained
at earlier.
2. Testing the developed product and debugging is easier. Because occurrence of small
iterations.
Cons:
1. As this iterative model is very rigid, it is too difficult to overlap.
3

2. Before starting the development process, all requirements are not collected properly so
that it led to architectural problem at end of each iteration cycle.
Spiral Model
It is more similar to the above mentioned spiral model except risk analysis (Software
Testing Material, 2018). It is an important place in SDLC. The steps involved in the spiral model
is given below (Testing Excellence SDLC, 2018).
To use the software product by various type of users, system requirements are defined
in depth-detail and this is for identifying the aspects of the system.
The most important step in this development model is preliminary design. It helps to
make a cost effective strategies to work on a project. In this stage, the new system is
developed. It represents the characteristics of final output as it is a scaled down system.
 The strength, weakness and risk involved in the system can be evaluated easily.
 Functional and non-functional requirements are defined for new prototype.
 planning and designing of newly developing prototype can be started
 For the developing project, testing process will be carried out
4

Pros
1. The spiral model is very efficient for critical and big sized project
2. At earlier of lifecycle, the working or output software is developed
3. It helps to analyze the high level of risks.
Cons:
1. The cost of model installation is very high rather than others
2. It is not recommended for small projects.
3. The success of project is based on the risk taken on analysis phase only. So an expertise is
required for analyzing the high level of risk.
Prototype Model
5