Software Requirements and Analysis Report: Case Study and Analysis

This report presents a comprehensive analysis of software requirements, focusing on a case study involving a school's transition to an automated system. It begins with an introduction outlining the report's structure and objectives. The discussion section details the case study, highlighting the school's desire to automate various tasks, including student records, faculty management, and financial transactions. The report identifies key pain points, such as process inefficiencies, productivity concerns, and security vulnerabilities. A domain analysis is conducted to understand the system's variables and data. The problem statement focuses on the critical need for robust data security measures. The report includes visual aids like a Fishbone diagram, context diagram, and class diagram to illustrate the system's components. A vision statement is provided, and the report concludes by summarizing the key findings and emphasizing the importance of data security. References to relevant literature are also included to support the analysis and findings.

Running head: SOFTWARE REQUIREMENTS AND ANALYSIS
Software Requirements and Analysis
Name of the Student
Name of the University
Author Note

1
SOFTWARE REQUIREMENTS AND ANALYSIS
Table of Contents
Introduction......................................................................................................................................2
Discussion........................................................................................................................................2
Case Study...................................................................................................................................2
Pain points...................................................................................................................................2
Domain analysis...........................................................................................................................3
Problem statement.......................................................................................................................3
Conclusion.......................................................................................................................................3
References........................................................................................................................................4

2
SOFTWARE REQUIREMENTS AND ANALYSIS
Introduction
A case study will be discussed in the report and with respect to that pain points, domain
analysis and problem statement will be discussed.
Discussion
Case Study
A Remarkable school used to execute all of its task be it storing details of its students,
keeping track of all the records of the students regarding their results, class, section, attendance
etc., keeping the tracks of the faculties, staffs who are working in that particular school. Now it
has been decided by the school to execute all of the above mentioned tasks in a computer driven
manner or in an automated manner (Wiegers and Beatty 2013). This includes the details of the
students like the enrolment number of the students, the details of the teachers and the staff. The
students will also be assessed automatically in a computer driven manner. The information
regarding the payment of the school fees of the students will be executed in an automated way.
In addition to it, the information regarding the issuing of the results, certificates as well as
degrees as well as records of the student like whether they have passed in their classes or not will
also be executed in a computer driven manner (Achimugu et al. 2014). The expectations of the
school is to have a new software so that all the tasks could be used by them in automated way.
The requirements needed for the execution of the tasks should be analyzed which in turn should
be actionable, can be documented, testable, measurable, related to the context and traceable
(Galvis Carreño and Winbladh 2013). An information system will be designed which will
contain computer hardware and software, databases etc.

3
SOFTWARE REQUIREMENTS AND ANALYSIS
Problem statement
The main problem is data security methods. Due to high increase in the probability of
hacking and loss of sensitive information, strong data security methods are needed to keep the
information of the school safe and secure.
Pain points
The pain points in this context are as follows:
 Process and functionality pain point: At times there are issues regarding the process and
the proper functioning of the automated which leads to a pain point.
 Pain point related to productivity: At times there are some issues regarding the
productivity of the results after storing the information regarding the details.
 Pain point related to security: There is high chance of the security of such kinds of
systems getting vulnerable and prone to hacking as well as modification also.
 Pain points related to up gradation of technology: The automated system should always
remain updated. This keeps the automated systems less prone to the risk to an advanced
level.
 Pain point related to application security: Higher levels of tools and personnel are
required for testing the drawbacks of the information security.
 Pain points related to external attacks and third party supplier: Appropriate steps needs to
be taken for this along secured external groups.
Domain analysis
Domain analysis is used for analyzing the software systems which are related to the
project for finding the variable parts that are similar. It mainly focuses on the identification of the

4
SOFTWARE REQUIREMENTS AND ANALYSIS
data and information (StClair and StClair 2015). The software used for the construction of the
automated system of the school is an efficient software which operates accurately for the
execution of all the processes and works in effectively.
Fishbone diagram
Figure: Fishbone diagram

5
SOFTWARE REQUIREMENTS AND ANALYSIS
Context diagram
Figure: Context Level Diagram

6
SOFTWARE REQUIREMENTS AND ANALYSIS
Class diagram
Figure: Class Diagram
Vision Statement
The vision is to execute and develop software that will execute all the tasks of the school
like keeping track of the records of the students regarding their result, attendance, performance
etc. in an automated manner. The details about faculties as well as staffs will also be contained in

7
SOFTWARE REQUIREMENTS AND ANALYSIS
the computer driven system. The various activities of the school like the payment details of the
student, payment details of the staff will be shown in the computer driven system.
Conclusion
The case study has been discussed along with the pain points, domain analysis and problem
statement which states that the strong methods of data security is needed for the successful
execution of the software (Zhang et al. 2014). In this way a school can implement all its manual
tasks in an automated manner.

8
SOFTWARE REQUIREMENTS AND ANALYSIS
References
Wiegers, K. and Beatty, J., 2013. Software requirements. Pearson Education.
Achimugu, P., Selamat, A., Ibrahim, R. and Mahrin, M.N.R., 2014. A systematic literature
review of software requirements prioritization research. Information and software technology,
56(6), pp.568-585.
Galvis Carreño, L.V. and Winbladh, K., 2013, May. Analysis of user comments: an approach for
software requirements evolution. In Proceedings of the 2013 International Conference on
Software Engineering (pp. 582-591). IEEE Press.
StClair, W.G. and StClair, S.A., LDRA Tech Inc, 2015. Automated management of software
requirements verification. U.S. Patent 8,949,770.
Zhang, H., Li, J., Zhu, L., Jeffery, R., Liu, Y., Wang, Q. and Li, M., 2014. Investigating
dependencies in software requirements for change propagation analysis. Information and
Software Technology, 56(1), pp.40-53.