Reference no: EM133297883
Assignment - Library book management system
In this assignment, you will go through the software development life cycle and practice some key activities of designing a library book management system. The book management system is a web application to support a local library in managing inventory and loaning books.
The assignment consists of four parts:
• In Part A of the assignment, you will organise the interviews.
• In Part B, you will draw the entity-relationship diagram and write requirement specifications for many functions.
• In Part C, you will design the database for the system.
• In Part D, you will practice planning and draw the Gantt chart for the project.
Part A: Organise the interviewAssuming the library currently using an out-of-date Dynix system. And they are knee to update their infrastructure to a modern web-based system developed by Essex Bespoke Software Ltd. As a team leader, you are in charge of designing the interview process. Due to time constrain, you can only choose two groups of people to conduct the interviews. For each group, you need to prepare four questions (The people you can interview are not restricted to the library staff).
1. Who are you going to interview and why?
2. What are the questions you are going to ask them and what are your motivations for those questions?
Part B: System analysis
After the interviews, five modules are identified (book, author, publisher, member and loan). For requirement specification, you team is in charge of three modules (book, member and loan). The functions required for those modules are listed below:
• Book module:
- B1. List all the books in the system.
- B2. Add a book to the system.
- B3. Edit a book in the system.
- B4. Delete a book from the system.
- B5. Search a book in the system by title, author, or publisher
• Member module:
- M1. List all the members in the system.
- M2. Add a member to the system.
- M3. Edit a member in the system.
- M4. Delete a member from the system.
- M5. Search members in the system by name.
• Loan module:
- L1. List all the loans in the system.
- L2. Check out a book.
- L3. Extend a loan for a book.
- L4. Search for a loan in the system by member id or book id.
- L5. Mark loan as returned.
1. Suppose each of the modules corresponds to an entity in the entity relationship diagrams. You are required to draw the entity-relationship diagrams for the system (with all five modules).
To simplify the drawing, you can replace the one-to-many symbol (e.g. on page 23 of the lecture slides 7) with the arrows, e.g. Department → Course means one department may have multiple courses.
2. You need to write the functional and non-functional requirements foreach of the 15 functions and the potential users for those functions.
Part C: System design
After the analysis, for system design, you are required to design the database for the system. Suppose each of the five modules (book, author, publisher, member and loan) corresponds to a table in a relational database. You are required to design the tables.
1. How are you going to design the fields (consider using foreign keys when appropriate) of those tables?
Part D: Project management
Now assuming you are the project manager who is in charge of scheduling. For each of the five modules, they are three tasks (Design, Programming and Documentation). You have three system designers, three programmers and three technical authors in your team to help you with the tasks. Based on the experiences from previous project, the effect time and work rate are estimated. The effect times (days) required to complete the tasks can be found in Table 1. And the work rate and availability for all the members in your team are shown in Table 2
|
Module
|
Design
|
Programming
|
Documentation
|
|
Book
|
4
|
6
|
3
|
|
Author
|
1
|
1
|
1
|
|
Publisher
|
2
|
3
|
2
|
|
Member
|
2
|
3
|
2
|
|
Loan
|
4
|
6
|
3
|
Table 1: The effect time needed for each of the tasks.
|
Task
|
Team Member
|
Work rate
|
Availability
|
|
Design
|
System designer 1 (SD1)
|
100%
|
100%
|
|
System designer 2 (SD2)
|
150%
|
40%
|
|
System designer 3 (SD3)
|
50%
|
50%
|
|
Programming
|
Programmer 1 (P1)
|
200%
|
40%
|
|
Programmer 2 (P2)
|
100%
|
100%
|
|
Programmer 3 (P3)
|
50%
|
60%
|
|
Documentation
|
Technical author 1 (TA1)
|
100%
|
60%
|
|
Technical author 2 (TA2)
|
50%
|
100%
|
|
Technical author 3 (TA3)
|
200%
|
40%
|
Table 2: The work rate and availability of all the members of the team.
Question 1. Compute the elapsed time for all the team members on all the related tasks that could assign to them. e.g. for SD1, five tasks can be potentially assigned to him/her (design book, author, publisher, member and loan modules).
Question 2. How do you want to assign the tasks to your team members to minimise the overall time for completing the project. Draw your schedules using a Gantt chart.
Attachment:- Library book management system.rar