20201216-Task1
20201216-Task1
Q1- Write a problem statement that explains the problem that the project aims to study and solve.
The software project I selected for this is a mobile application to manage a library to make it easy for
users to find, borrow, reserve books and also receive notifications for the return dates, and it can also be
used by librarians to manage books
Problem Statement: Libraries can have a lot of problems in managing book inventories, tracking book
loans, return dates for books using the old and traditional methods only because it tends to be inefficient
when the library grows and that could impact the library service the app im trying to build will provide
solutions to all the listed problems and a user-friendly interface to make it easy for libraries to manage
the library
The software development methodology I think is best for this software is agile
Q3- Justify Your Choice:
For a mobile library app, it doesn’t require a lot of complex functionality, moderate complexity with
essential features like borrowing books, managing loans, sending notifications
- Team Size:
it can be done with small to medium team due to the project being not that complex to implement and
allowing for updates and improvements or changes
- Timeline:
I choose Agile for being and adaptive and iterative process that suits best with the project, it
enables the app to be managed and developed easier and allow core functionalities to be
launched as fast as possible with updates and everything needed
2- Key Features:
Agile makes it easy to add changes and allows for continues improvements and adapt to
new functionalities and features
Agile supports the addition of features as library needs such as implementing Qr code
scanning to easy access to the library or pay for books
- User-Centric Approach:
Agile being an approach that user feedback is essential for it makes it the best method for
the library project it ensures the app meets both the librarian and user needs
- Waterfall:
The limitations of waterfall model compared to agile is that waterfall is sequential and requires a lot of
documentations to every step so it makes it hard to adapt to user requirements changes once the
project in the development phase for a library app choosing waterfall will make it hard to develop and
solve the issues that libraries face. it limits flexibility and adaptability because waterfall requires each
step to be fully documented
- Spiral:
The issue with spiral is while it allows for iterative development it is more suited for large and complex
projects because it focuses a lot on risk management and prototyping, this makes it less efficient for a
moderate complexity like a library app
Resources: