System Analysis and Design Name of the University Author

SYSTEM ANALYSIS AND DESIGN SYSTEM ANALYSIS AND DESIGN System Analysis and Design Name of the Student Name of the University Author Note Introduction: 2 Methodologies: 2 Chosen Methodology: 3 Requirement Gathering: 4 Requirements for the System: 4 Functional Requirement: 4 Non-Functional Requirement: 5 Requirement Modelling: 6 Conclusion: 7 References: 8 Introduction: Information Technology solutions are very much essential for business processes. The IT solution organization is currently facing some problems regarding their business process, and for that, they

Running head: SYSTEM ANALYSIS AND DESIGN
System Analysis and Design
Name of the Student
Name of the University
Author Note

1SYSTEM ANALYSIS AND DESIGN
Table of Contents
Introduction:...............................................................................................................................2
Methodologies:...........................................................................................................................2
Chosen Methodology:................................................................................................................3
Requirement Gathering:.............................................................................................................4
Requirements for the System:....................................................................................................4
Functional Requirement:........................................................................................................4
Non-Functional Requirement:................................................................................................5
Requirement Modelling:............................................................................................................6
Conclusion:................................................................................................................................7
References:.................................................................................................................................8

2SYSTEM ANALYSIS AND DESIGN
Introduction:
Information Technology solutions are very much essential for business processes. In this
paper, the case study of the IT solutions organizations has been selected for describing the
importance of IT in business. The IT solution organization is currently facing some problems
regarding their business process, and for that, they are implementing a system which can
directly take the service requests from the user. Also, this system will be able to track the
status of each request. To develop this system the approach of the SDLC is chosen here. Thus
the predictive and adaptive approach of the SDLC will be described briefly. Further, the
functional and non-functional requirement system will be evaluated in brief.
Methodologies:
To develop the desired system, approach of the Software Development Life Cycle is
chosen here. The System Development Life Cycle is the process which is used for creating,
planning, testing and deploying an information system. The SDLC consists of several ranges
of hardware and software (Bhuvaneswari and Prabaharan 2013). The developed system by
using the SDLC can be consists of hardware, software or can consist both. The main six stage
of the SDLC is the design, analysis, development and testing, documentation, implementation
and evaluation. While considering the approaches of the SDLC, it consists two approaches
which are the adaptive approach and the predictive approach.
The adaptive approach to the SDLC is used for the projects which are not understood
properly and having a high amount of risk (Highsmith 2013). This approach is more iterative,
and it helps the project team to adapt changing requirement of the project. Also, this approach
is very much transparent to the others (Öztürk 2016). The limitation of the adaptive SDLC
that it requires extensive involvement of the user which slows the entire process of the SDLC.

3SYSTEM ANALYSIS AND DESIGN
The predictive approach of the SDLC considers that the planning of the project
development is done in advance and the desired information system can be installed
according to the development plan (Usman et al. 2014). The adaptive approach to the SDLC
is very much useful in the cases when the requirement of the user is not understood properly.
The main limitation of the predictive SDLC approach is that the developed system can be
only used after the last stage of software development. Thus the testing and reviewing the
system is not possible during the development stage of the system.
Chosen Methodology:
The main aim of the IT solution organization is to develop a system which can
directly take service request from the users and can track each of this request. For developing
this type of management system, the waterfall model of the SDLC can be chosen in this case.
The main reason behind choosing the waterfall model of SDLC approach is that it is very
much helpful to develop the framework for planning and controlling the information system
(Alshamrani and Bahattab 2015). In this case, the proposed information system is the
management of the customer’s requests. To develop this type of user request processing
system each developer in the development team needs to work different phases of the
software development process. The waterfall model is actually a linear system development
model, and the flexibility of working in different phase is achieved because of this linear
system. Thus the waterfall model of the SDLC is chosen of the IT solutions organization
(Mishra and Dubey 2013). Also, the main phases of the waterfall model are the system
planning, system design, system analysis and the system implementation which are essential
for developing the request management of the customers and tracking those requests.

4SYSTEM ANALYSIS AND DESIGN
Requirement Gathering:
To develop the proposed system successfully, it is very much essential to find the
requirements needed for the system. For finding the requirement of the system a set of
common question was thrown to every technical member of the organization. Also, a
personal interview is taken of the CEO and the managers of the organization. The group of
questions was mainly focused on the current problems of the organization which is faced by
them. From the answers, it has been assessed that the majority of the peoples were having the
problem with managing the clients as recently a large number of new clients has been joined
with the organization recently. Also, another problem stated by them was tracking of the
service. In many cases, the technical staffs need to handle the customers multiple time for
fixing the problem. In such of the cases, it becomes very much essential to track the record of
the service progress.
From the interview of the CEO and the managers, the actual functionality of the
system has been assessed. Also, the budget for the proposed system is a very much crucial
requirement (Meredith et al. 2016). From the interview of the CEO and the managers, the
total budget of the project has been assessed. Thus planning can be taken according to the
total budget of the system.
Requirements for the System:
The requirement of the system can be divided into two parts. The first part is the
functional requirement and the second part is the non-functional requirement.
Functional Requirement:
The main functional requirement of the proposed system follows:
 Taking problem definition from the clients and passing on to the technical team.
 Managing the client’s record.

5SYSTEM ANALYSIS AND DESIGN
 Processing the service request of the client in real time.
 Tracking the progress report of each problem separately and the assigned technicians
to the problem.
Non-Functional Requirement:
The non-functional requirement of the systems are:
 Secure access to the customer’s data.
 Availability of the system 24*7.
 Flexible architecture for future modification (Basak, Bhunia and Ray 2015) or the
improvement in the existing system.
 The resource utilization by the system must be optimized.

6SYSTEM ANALYSIS AND DESIGN
Requirement Modelling:
(Figure 1: Activity Diagram of the System)
(Source: Created by the Author)

7SYSTEM ANALYSIS AND DESIGN
Conclusion:
Form the above discussion it can be concluded that the Software Development Life
Cycle is very much important for the software development processes. In this paper, the
problems of the IT solutions organization has been assessed. Form the analysis it has been
assessed that the organization was facing problems regarding response to the clients as their
business was expanded in recent time. Also, they were facing problem regarding the tracking
of the service status. Thus the organization opted to develop a system which can mitigate this
issues and for development of this system waterfall model of the SDLC has been used in this
case. Further, the functional and non-functional system has been discussed in this paper.

8SYSTEM ANALYSIS AND DESIGN
References:
Alshamrani, A. and Bahattab, A., 2015. A comparison between three SDLC models waterfall
model, spiral model, and Incremental/Iterative model. International Journal of Computer
Science Issues (IJCSI), 12(1), p.106.
Basak, A., Bhunia, S. and Ray, S., 2015, November. A flexible architecture for systematic
implementation of SoC security policies. In Proceedings of the IEEE/ACM International
Conference on Computer-Aided Design (pp. 536-543). IEEE Press.
Bhuvaneswari, T. and Prabaharan, S., 2013. A survey on software development life cycle
models. Journal of Computer Science and Information Technology, Vol2 (5), pp.263-265.
Highsmith, J.R., 2013. Adaptive software development: a collaborative approach to
managing complex systems. Addison-Wesley.
Meredith, J.R., Shafer, S.M., Mantel Jr, S.J. and Sutton, M.M., 2016. Project management in
practice. Wiley Global Education.
Mishra, A. and Dubey, D., 2013. A comparative study of different software development life
cycle models in different scenarios. International Journal, 1(5), pp.64-69.
Öztürk, V., 2016. Flexible and Adaptive Life Cycle Framework for Software
Development. JSW, 11(9), pp.943-951.
Usman, M., Mendes, E., Weidt, F. and Britto, R., 2014, September. Effort estimation in agile
software development: a systematic literature review. In Proceedings of the 10th
International Conference on Predictive Models in Software Engineering (pp. 82-91). ACM.