University Library System Formal Specification Report: ITECH7410

This report details the development of a library management system using software engineering methodologies, with a focus on Z notation for formal specification. The report outlines the system's functionality, including book management, borrower management, and reservation features. It describes the agile methodology, including requirement gathering, design, and prototyping phases. Non-trivial predicate statements and Data Flow Diagrams (DFDs) are provided to illustrate the system's design. The report concludes by emphasizing the importance of critical analysis, risk management, and the use of Z notation in system development, along with a bibliography of relevant sources. This assignment demonstrates the student's ability to apply software engineering principles to design and specify a complex system.

SOFTWARE
ENGINEERING
METHODOLOGIES
Name of the Student
Name of the University

INTRODUCTION
• The presentation is based on developing a library management system. Z
notation is used for defining and completing the functionality of the
system. Z notation is used as simple mathematical notation for describing
the software that is developed. A detailed description of the software
development methodology is used for the completion of the software
development. Non Trival predictable statement is used and compared
with library management.

SOFTWARE DEVELOPMENT
METHODOLOGIES
• There are different strategy used for the development of a predictive or
adaptive software development life cycle. Agile methodology is
considered for the development of software and it includes a number of
steps such as:
• Requirement gathering
• Design Approach
• Requirement Specification
• Design
• Prototype

REQUIREMENT GATHERING
• It is used for collection of information by interrogating users and identify
the reason to create each of the interface.
• Readymade prototype can be shown to customer for gathering evaluative
information that he might require.
• Useful questionnaire can be provided to the user to gather information
regarding the targeted system environment.

DESIGN APPROACH
• It is used for deciding the approach that is needed to be applied for taking
information as an input from the client and start development of user
interface. This phase is about the input and output device that is needed
to be used by the interface, technology used for creating the interface
and the software/hardware tools.

REQUIREMENT SPECIFICATION
• The view of the user is gathered about the development of library
management system and the logical design of the database is prepared.
The data is needed to be displayed is identified for designing the
interface and in the phase the information is also validated for providing
service. The phase provides description about the initial requirement in
agile software development lifecycle.

DESIGN
• This phase is used for the representation of information and the elements
in a proper manner such that the client can find all the information. This
phase is similar with the architectural design and detailed design. For
designing the requirement is evaluated and proceeded with the further
steps.

PROTOTYPE
• It is used for creating a prototype for testing the idea of the designer and
aligning it with the customer’s requirement. The prototype is needed to
be evaluated for deciding the field of prototype. The prototypes are not
fictional and their look and feel is needed to be checked with their
interface and virtual device. The prototype act as a simple structure with
minimum codes.

DEPLOYMENT
• It is used for deployment of complete project for the business
organization or for the client side for the management of functionality.
This phase is the last phase of software development and comes after
complete development.

FUNCTIONALITY OF SCHEMA
• It should only deal with books and no other products
• It must allow addition of new books
• It must have the functionality to add borrowers
• It must have functionality to delete book and borrower
• It must have functionality to buy a book or lend from borrower
• It must have facility of returning book
• The borrower can be able to enquire about book or for book reservation
• A facility for reserving book must be present
• Facility for canceling reservation should be there

NON TRIVIAL PREDICATE
STATEMENT
Book ID⇒ ID, Name, Price, pages
Librarian→ Id, Name, Address, Email, phone Number
Student ∃ ⇔ Student Id, Name, Address, Email, Phone Number
Reservation ∃⇒ Id, type, payment, Student Id

DFD

CONCLUSION
• The details of software development methodology and Z notation is
presented for the completion of library management system. Some DFD
are provided for demonstrating the compete details about the system.
The development of the system helps in increasing the critical analysis
skill and also help in improving the risk management, development
approach. Z notation is used for defining the system.

BIBLIOGRAPHY
• Al-Brashdi, A., Butler, M., & Rezazadeh, A. (2018). Incremental database design using UML-B and Event-B. arXiv preprint
arXiv:1805.05514.
• Anwar, M. W., Rashid, M., Azam, F., Kashif, M., & Butt, W. H. (2019). A model-driven framework for design and verification
of embedded systems through SystemVerilog. Design Automation for Embedded Systems, 23(3-4), 179-223.
• Bosu, A., Iqbal, A., Shahriyar, R., & Chakraborty, P. (2019). Understanding the motivations, challenges and needs of
Blockchain software developers: a survey. Empirical Software Engineering, 24(4), 2636-2673.
• Grant, E. S. (2016, October). Requirements engineering for safety critical systems: An approach for avionic systems.
In 2016 2nd IEEE International Conference on Computer and Communications (ICCC) (pp. 991-995). IEEE.
• Mutarraf, U., Barkaoui, K., Li, Z., Wu, N., & Qu, T. (2018). Transformation of Business Process Model and Notation models
onto Petri nets and their analysis. Advances in Mechanical Engineering, 10(12), 1687814018808170.
• Pickin, S., Sánchez, C., Yelmo, J. C., Gil, J. J., & Rodríguez, E. (2016). Introducing formal notations in the development of
object-based distributed. Formal Methods for Open Object-based Distributed Systems, 1, 79.
• Ríos, J. R. M., Ordóñez, M. P. Z., Tapia, J. A. H., & Moreno, A. S. G. (2016). Analysis Methodologies Web Application
Development. International Journal of Applied Engineering Research, 11(16), 9070-9078.
• Taveter, K., & Norta, A. (2017, November). Agile Software Engineering Methodology for Information Systems’ Integration
Projects. In International Conference on Future Data and Security Engineering (pp. 215-230). Springer, Cham.