0% found this document useful (0 votes)
50 views

Systems Integration-1st

This document outlines requirements for a library book management software system. It includes requirements for managing books, members, and loans. Key requirements include adding, editing, deleting, and searching for books, members, and loans. Non-functional requirements focus on the system being secure, maintainable, efficient and easy to use. The document also includes sample questions to interview librarians and users to understand needs and timelines for the project.

Uploaded by

Hasan Ahmad
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
50 views

Systems Integration-1st

This document outlines requirements for a library book management software system. It includes requirements for managing books, members, and loans. Key requirements include adding, editing, deleting, and searching for books, members, and loans. Non-functional requirements focus on the system being secure, maintainable, efficient and easy to use. The document also includes sample questions to interview librarians and users to understand needs and timelines for the project.

Uploaded by

Hasan Ahmad
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
You are on page 1/ 14

CE719 Assignment

Library Book Management

Contents
Part A...........................................................................................................................................................3
Who are you going to interview and why?..............................................................................................3
What are the questions?.........................................................................................................................3
Part B...........................................................................................................................................................5
Requirement 1.........................................................................................................................................5
Requirement 2.........................................................................................................................................6
Requirement 3.........................................................................................................................................6
Requirement 4.........................................................................................................................................6
Requirement 5.........................................................................................................................................7
Requirement 6.........................................................................................................................................7
Requirement 7.........................................................................................................................................7
Requirement 8.........................................................................................................................................8
Requirement 9.........................................................................................................................................8
Requirement 10.......................................................................................................................................8
Requirement 11.......................................................................................................................................9
Requirement 12.......................................................................................................................................9
Requirement 13.......................................................................................................................................9
Requirement 14.....................................................................................................................................10
Requirement 15.....................................................................................................................................10
Part C.........................................................................................................................................................10
Book Table.............................................................................................................................................10
Author Table..........................................................................................................................................10
Publisher Table......................................................................................................................................10
Member Table.......................................................................................................................................11
Loan Table.............................................................................................................................................11
Part D.....................................................................................................................................................11
References.................................................................................................................................................13

Part A
Who are you going to interview and why?

I am going to question to the librarians and general users of this software

What are the questions?

1. At the conclusion of the development phase, what do you anticipate the application will
be capable of doing?

If we know the answer to this question, it will be much easier for us to avoid having any
unrealistic expectations.

2. Where do you stand in terms of the timeline for this project?

Every software development project is required to meet certain time constraints, milestones, or
deadlines. Customers could be required to fulfill commitments to investors, and the schedule
might be contingent on the strategic development strategy, marketing efforts, or significant
events of the firm. Developers are able to build a clear and realistic plan for development,
define priorities, and allocate resources in the most effective manner when they are aware of
the time restrictions. This enables them to achieve the deadline that has been set.

3. What Essential Information Do I Require Regarding the Software Development


Method?

The motivation of these questions is when developing bespoke software, it is essential to get as
much knowledge as possible about the software development process. This approach is
essentially the process model, the rules connected with development, and the creation of the
systems meant to execute the software. It also involves the development of the systems. The
interviewing of support personnel and members of your intended audience is one example of a
step that needs to be taken with this method. Other examples of steps that should be
performed with this method include propositions for improved performance with the software
development process, plans related to the development, setup, and usage of the software
solutions, and so on.

4. Which Kinds of Technologies Will Be Employed in This Process?


You will draw from a number of different technological areas while developing bespoke
software. When deciding between various types of technologies, the aspects of the software's
programming code, the maintenance that will be necessary to keep the program up to date,
and the possibility of the development of bespoke software in the future are the most
important considerations to give careful thought to.

5. Which Functionalities Are on Your Priority List to Be Implemented in the Near


Future?

This issue must be considered carefully in order to arrive at the best architectural conclusions.
After all, you may be able to envisage your product in a few years' time and know what features
you will need to integrate at that point. You will be able to create a fantastic evolution plan for
your product if you take everything into consideration.

6. What are the Prerequisites for the Data Storage Process?

Any individual must acquire data, store it, or analyses it while they are working. Before
beginning the process of development, you must have the answers to the following questions:
what sort of data it will be, what storage rules will apply to it, how it will be processed, and, if
required, how it will be removed. With this information, you'll be able to choose the database
storage option that's best for your needs.
Part B

That only one person at a time can take out a loan, but that member may borrow either one
book or many books under one loan, creating a one-to-one connection or a one-to-many
relationship, respectively. There is a one to one connection between the book and the publisher
since only one book will be published by that publisher; yet, there is a one to many links
between the book and the author because only one book will have one or more writers.

Requirement 1

Requirement: B1 List all the books in the system Users: Librarian


Functional Requirement:

List all the books in the system

Non-functional Requirement:

Maintainable
Requirement 2

Requirement: B2 Add a book to the system Users: Librarian


Functional Requirement:

Add a book to the system

Non-functional Requirement:

System should be secure

Requirement 3

Requirement: B3 Edit a book in the system Users: Librarian


Functional Requirement:

Edit a book in the system

Non-functional Requirement:

System must allow the system to do that easily

Requirement 4

Requirement: B4 Delete a book from the system Users: Librarian


Functional Requirement:

Delete a book from the system


Non-functional Requirement:

Secure

Requirement 5

Requirement: B5 Search a book in the system by title, Users: Librarian


author, or publisher
Functional Requirement:

Search a book in the system by title, author, or publisher

Non-functional Requirement:

Maintainable

Requirement 6

Requirement: M1 List all the members in the system Users: Member


Functional Requirement:

List all the members in the system


Non-functional Requirement:

Maintainable

Requirement 7

Requirement: M2 Add a member to the system Users: Member


Functional Requirement:

Add a member to the system


Non-functional Requirement:

Efficient
Requirement 8

Requirement: M3 Edit a member in the system Users: Librarian


Functional Requirement:

Edit a member in the system

Non-functional Requirement:

Easy to use

Requirement 9

Requirement: M4 Delete a member from the system. Users: Member


Functional Requirement:

Delete a member from the system.

Non-functional Requirement:

Easy to use

Requirement 10

Requirement: M5 Search members in the system by Users: Member


name
Functional Requirement:

Search members in the system by name

Non-functional Requirement:
Easy to use

Requirement 11

Requirement: L1 List all the loans in the system. Users: Librarian


Functional Requirement:

List all the loans in the system.

Non-functional Requirement:

Easy to use

Requirement 12

Requirement: L2 Check out a book Users: Librarian


Functional Requirement:

Check out a book


Non-functional Requirement:

Easy to use

Requirement 13

Requirement: L3 Extend a loan for a book Users: Librarian


Functional Requirement:

L3 Extend a loan for a book


Non-functional Requirement:

Easy to use
Requirement 14

Requirement: L4 Search for a loan in the system by Users: Librarian


member id or book id
Functional Requirement:

Search for a loan in the system by member id or book id


Non-functional Requirement:

Easy to use

Requirement 15

Requirement: L5 Mark loan as returned. Users: Librarian


Functional Requirement:

Mark loan as returned.


Non-functional Requirement:

Easy to use

Part C

Book Table

Book_ID(PK), Author_id(FK), title, year, year of publication, status, registration date

Author Table

Author_id, authorFirstName, authorLastName, publisher_id(FK)

Publisher Table

Publisher_id, PublisherName, Publisher_address


Member Table

Member_id, memberFirstName, memberLastName, contactNumber, address, emailed

Loan Table

Loan_id, member_id, book_Id(FK), loanDate, expectedReturnDate

Part D

4 6.7 16
1 1.7 4
2 3.3 8
2 3.3 8
4 6.7 16
P1 P2 P3
7.5 6 20
1.25 1 3.3
3.75 3 10
3.75 3 10
7.5 6 20
TA1 TA2 TA3
5 6 3.75
1.7 2 1.25
3.3 4 2.5
3.3 4 2.5
5 6 3.75

1 1 1 1 1 1 1 1 1 1 2 2
Tasks 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1

Design book
module SD1

Program book
module P2

Document book
module TA3

Design author
module SD2

Program author
module P1

Document author
module TA1
Design Publisher
module SD1
Program
Publisher module P1

Document
Publisher module TA1

Design member
module SD2

Program member
module P3

Document
member module TA3

Design loan
module SD1

Program loan
module P2

Document loan
module TA1

References

1. Baxter, P., & Jack, S. (2008). Qualitative case study methodology: Study design and
implementation for novice researchers. Qualitative Report, 13(4), 544-559.
2. Boar, B. H. (2002). The art of strategic planning for information technology (2nd ed.).
John Wiley & Sons. Carr, N. G. (2003). IT Doesn’t Matter. Harvard Business Review,
81(15), 41-49
3. Chen, D. Q., Mocker, M., Preston, D. S., & Teubner, A. (2010). Information Systems
Strategy: Reconceptualization, Measurement, and Implications. MS Quarterly, 34(2),
233-259.
4. Cordella, A., & Iannacci, F. (2011). Information systems and organizations. United
Kingdom: University of London Press.
5. Doan, A., & McCann, R. (2003). Building Data Integration Systems: A Mass Collaboration
Approach. 18th International Joint Conference on Artificial Intelligence (IJCAI)
6. Gan, X. (2006). Software Performance Testing. ACM Computing Classification System, 1-
9.
7. Gebauer, J., & Lee, F. (2008). Enterprise system flexibility and implementation strategies
– Aligning theory with evidence from case study. Journal Information Systems
Management archive, 25(1), 71-82. http://dx.doi.org/10.1080/10580530701777198

You might also like

pFad - Phonifier reborn

Pfad - The Proxy pFad of © 2024 Garber Painting. All rights reserved.

Note: This service is not intended for secure transactions such as banking, social media, email, or purchasing. Use at your own risk. We assume no liability whatsoever for broken pages.


Alternative Proxies:

Alternative Proxy

pFad Proxy

pFad v3 Proxy

pFad v4 Proxy