Detailed Report on Functional and Non-Functional Requirements Analysis

This software engineering report provides a detailed analysis of functional and non-functional requirements for a railway crossing system, including stakeholder identification and operational scenarios. Functional requirements encompass system login, user ID generation, signal transmission for bar operation, train status tracking, alert generation for schedule changes, downtime recording, communication with the Railway Control Centre (RCC), control of lights and bells, automated report generation, user account management, and incident reporting. Non-functional requirements emphasize system availability, performance, usability, reliability, maintainability, and security. The report also identifies key stakeholders such as library owners, managers, readers, suppliers, and operational staff, outlining scenarios like visitor registration, book borrowing and returns, overdue penalties, stock management, and reservation processes. Desklib offers this and many other solved assignments for students.

qwertyuiopasdfghjklzxcvbnmqw
ertyuiopasdfghjklzxcvbnmqwert
yuiopasdfghjklzxcvbnmqwertyui
opasdfghjklzxcvbnmqwertyuiop
asdfghjklzxcvbnmqwertyuiopasd
fghjklzxcvbnmqwertyuiopasdfgh
jklzxcvbnmqwertyuiopasdfghjkl
zxcvbnmqwertyuiopasdfghjklzxc
vbnmqwertyuiopasdfghjklzxcvb
nmqwertyuiopasdfghjklzxcvbnm
qwertyuiopasdfghjklzxcvbnmqw
ertyuiopasdfghjklzxcvbnmqwert
yuiopasdfghjklzxcvbnmqwertyui
opasdfghjklzxcvbnmqwertyuiop
asdfghjklzxcvbnmqwertyuiopasd
fghjklzxcvbnmqwertyuiopasdfgh
jklzxcvbnmrtyuiopasdfghjklzxcv
Introduction to Software Engineering
2/21/2018

Introduction to Software Engineering
Table of Contents
Answer 1...............................................................................................................................................2
Functional Requirements...................................................................................................................2
Non-Functional Requirements...........................................................................................................2
Answer 2...............................................................................................................................................3
List of Stakeholders...........................................................................................................................3
Scenarios of Working........................................................................................................................3
References.............................................................................................................................................4

Introduction to Software Engineering
Answer 1
Functional Requirements
 Ability to allow the system operators to authentically login to the software.
 Ability to generate user id for a new user.
 Ability to send and receive signals for lowering or rising of the bar on the crossing.
 Ability of the system to maintain the history and live status of the trains for
functioning of the crossing.
 Ability to generate alerts in case of change in schedule of a train.
 Ability to keep a record of the downtime in case of a system failure.
 Ability to communicate with the Railway Control Centre (RCC) through the software
for receiving instructions.
 Ability to control the lights and bell at the time change in the position of the bar or
while the bar is kept at the lowered position (Silmon and Roberts, 2010).
 Automated preparation and extraction of the operational reports on hourly, daily,
weekly, monthly, or customized basis.
 Ability to allow the users to manage their accounts and to the administrator to make
changes to the user privileges.
 Ability to report system incidents to the support and assistance team.
Non-Functional Requirements
 The system must always be available so that the railway crossing can be operated and
managed at any hour of the day.
 The system must showcase good performance through fast response and throughput
time (Mahmoud and Williams, 2016).
 The system must be usable by including all the functional specifications and must be
easy to use.
 Reliability of the system shall be present by displaying only valid information to the
users.
 System shall be easy to maintain and shall also be secure.

Introduction to Software Engineering
Answer 2
List of Stakeholders
Stakeholder Description
Library Owner(s) The sponsors, owners, and decision-makers
Library Manager The stakeholder responsible for managing the library operations
Readers/Visitors The end-users reading or borrowing a book from the library
Owners/Representatives
of Other Libraries
Library owners borrowing/lending the books and journals
Suppliers Supplier network for obtaining and adding books, papers,
records, and journals in the library (Walley, 2013)
Operational Staff Execution of accounting, customer management, cataloguing,
and circulation activities
Scenarios of Working
 A visitor registers himself/herself to read or borrow book(s) from the library by
providing demographic and contact details along with an identity proof.
 The visitor reads the desired book, paper, record, or journal and does not borrow
anything. The duration and material read is noted and maintained in the register.
 The visitor returns the book(s) borrowed on time and pays the applicable charges and
is provided with an invoice (Kumar et al., 2014).
 The visitor does not return the book on time and is imposed with penalties.
 The requested book by a visitor is available in the stock and is provided for specified
number of days.
 The book requested is not available in the record and the request for the same is sent
to the supplier. The visitor is notified about the availability as soon as the book is
back in the stock.
 The visitor reserves a book for desired dates and the information is noted down.
 The inventories, stocks, and accounts are updated in the register on a monthly basis
for each of the book, paper, journal, or record and are cross-checked for error
resolution.

Introduction to Software Engineering
References
Kumar, P., Singh, R., Kumar, R. and Singh, V. (2014). Mini Project on Library Management
System. [online] Available at:
http://dspace.cusat.ac.in/jspui/bitstream/123456789/8218/1/library%20management
%20system.pdf [Accessed 20 Feb. 2018].
Mahmoud, A. and Williams, G. (2016). Detecting, classifying, and tracing non-functional
software requirements. Requirements Engineering, 21(3), pp.357-381.
Silmon, J. and Roberts, C. (2010). Using functional analysis to determine the requirements
for changes to critical systems: Railway level crossing case study. Reliability Engineering &
System Safety, 95(3), pp.216-225.
Walley, P. (2013). Stakeholder management: the sociodynamic approach. International
Journal of Managing Projects in Business, 6(3), pp.485-504.