I need a project solution in business requirements analysis, and I will add to this letter the name of the book, the unsolved project, and an old project from one of the students (just to get an idea about the project. Please send a better solution than a student project) Thank you
Project topic:Blockchain in medical records
book name:Software Requirements, Third Edition
1.1 Description: Our service is based on borrowing and exchanging tools by being in the same narrow geographical area, in universities. The service aims to meet urgent needs in a short and fast time, such as: a university student needs a portable charger for a short period of time. So that the needy user submits his request, specifying what he/she wants and the required time to borrow it. and in the role of other users of the service who are present at the same time, and time to refuse or accept, according to the compatibility of the request. Delivery service may be available by hand or through storage boxes - lockers closing and opening mechanism according to the order number \& you must open the GPS to get your destination. It's so fast and helpful. 1.2 Scope: Our project focuses on all staff and students in Imam Mohammed Ibn Saud Islamic University (IMSIU). Features: Borrowing. Exchanging, Selling. 2. Business Requirements: 2.1 Background: The current situation for students who need stuff is not that simple. They may ask for their needs in WhatsApp groups or so.... so it's not efficient and there is no trust between the taker and the giver. Hence, students cannot find or get what they need. That's why we chose this idea for our project. 2.2 Business Objectives: Upgrade service communication in Imam Mohammed Ibn Saud Islamic University by 25% in the first semester. 2.3 Vision: For students who need to borrow stuff and exchange them "Muhtag" system is an information system that will provide a different services like borrowing, exchanging. selling and renting every stuff you want. This system will save lots of time, promotes the spirit of cooperation, and build trust between people, friendly with the environment. Unlike the current situation our product will save us from all this inefficiency. 3. Stakeholders: - Students: All students in IMSIU. - Employees: All departments in IMSIU. - Department staff: teachers, doctors and professors in IMSIU. 4. Elicitation Techniques: 4.1 similar system We use 2 similar systems: application "' $2"-see Figure 1 in Appendix A to application icon- and website "streetbank" -see the Appendix B 9.1 to move to website-- mrrhaapp it's Saudi community platform for play, pay, borrow staff, new and used. The Street bank is a UK-based network and Website that helps users share items with their neighbors. The purpose of Streetbank is to boost local communities by encouraging people to get to know their neighbors. The requirements extracted of this elicitation Techniques: - Allows delete chat in direct message - Allows edit chat in direct message - Allows cancel order of borrow - appear user location on the map - Show the closest user to you 4.2 Questionnaires The Questionnaires form consists of 6 questions. 5 of them had multiple choices and 1 open question -see the Appendix B 10.2 to read the question- we sent to 100 people, 62 of them replay. 95% of answers were from students and 5% of employees - see the Appendix 10.3 to review the result and see Figure 3,4 and 5 for answers. The requirements extracted of this elicitation Techniques: - Security deposit - Specific time to borrow - Allow lockers to return stuff - All chat and direct message 4.3 Interview The interview consisted of 4 questions with 3 persons. We asked some of the staff in the university campus. And they gave us very pleasing answers. -see Appendix A Table 1 interview questions and answers- The requirements extracted of this elicitation Techniques: - tool on the taker's phone. - direct phone call with both taker and giver. - support all credit cards and debit cards. 5. User requirements: 5.1. Students: - The students want Security deposit - The student wants Specific time to borrow - the students suggest Allow lockers to return stuff - The student suggests enabled chat and direct message 5.2. Employees: - The employees suggested login by user account university - The employees want period deternined for borrower - The employees suggested borrower rating "student, employees..." 5.3. Department staff: - The staff suggested that we build a tracking tool on the taker's phone. - The staff also suggested a direct phone call with both taker and giver. - They suggested that the system should support all credit cards and debit cards, visa Mastercard and etc... 6. Software Requirements: 6.1 Functional Requirements: 6.1.1. The system shall allow users by login with only accounts in university email. 6.1.2. The system must allow users to reset their password by clicking on "I forgot my password" and receiving a link to their verified email address. 6.1.3. The system must support multiple ways for payment for insurance (apple pay, cash, STC pay). 6.1.4. The system must add payment of fees if the borrower is late on returning the stuff. 6.1.5. The system must create a database that contains important information about the borrower (full name, phone number, university ID, and user address). 6.1.6. The system shall determine it period of borrower and return. 6.1.7. The system shows both -the taker and the giver- the time left to give back the item-: 6.1.8. The system shares the basic information about the taker with the giver, such as name, phone number, and University id, and the taker also can have the giver's information. 6.1.9. Every time you use the app you will earn points, and you will have many benefits. The benefits of the points are either:1. You can buy anything for free. 2.you get a 10% discount on any product you want to buy. BUY NOT BORROW 6.1.10. The system saves the history of all orders in the archive. 6.1.11. The system must give benefits when the user shares the app with his/her contacts. 6.1.12. The system shall allow cancel order of borrow. 6.1.13. The system shall allow edit and delete text in direct message. 6.1.14. The system must appear user location on the map. Every order borrow must determine period be specified date and day. 6.1.16. The system supports login to multiple devices. 6.1.17. The system allows the program to be evaluated. 6.1.18. The system shall provide the ability to send notifications: 6.1.19. The system shall support both Arabic and English languages. 6.1.20. The system shall evaluate after the order borrow is completed to taker and giver. 6.1.21. The system shall only work on using Wi-Fi. 6,1.22. The system shall only work on using GPS. 6.1.23. The system must be shown on the map who is closer to the taker. 6.1.24. The system contains a complaint box in case the beneficiary did not return the product he borrowed. 6.1.25. The system contains a search box to facilitate the beneficiary to search for the product he wants to borrow faster. 6.1.26. The system contains a support and assistance box, in which there are general and technical questions and terms of service. 6.1.27. The system includes sending notifications to alert the user that the borrowing deadline is approaching. 6.1.28. The system contains a division of products with each field of its own (electronic device box, stationery box, etc.). 6.2 Non-Functional Requirements: 6.2.1 Safety: 6.2.1.1 The system must provide lockers to return stuff 6.2.2 Performance: 6.2.2.1 The system must send a Verification code within 5 seconds by email or a text 6.2.3 Compatibility: 6.2.3.1 The system must be compatible with iOS and Android devices. 7. Models: 8. References: StarUML 4.1.6 (2021). MKLabs Co,L.td. 9. Appendices A: Fugare 6 ammery 10. Appendices B: 10.1. website streetbank 10.2. Questionnaires form 10.3. Result the questionnaires Table of Contents List of Figures List of Tables 3 1. Introduction: 3 1.1 Description: 4 1.2 Scope: 4 2. Business Requirements: 4 2.1 Background: 4 2.2 Business Objectives: 4 2.3 Vision: 4 3. Stakeholders: 4 4. Elicitation Techniques: 4 4.1 4 4.2. 4 4.3.. .4 5. User requirements: .4 6. Software Requirements: 4 6.1 Functional Requirements: .4 6.2 Non-Functional Requirements: 4 7. Models: 4 References. Appendices. 4 .4 4 List of Figures Figure 1 Figure 2 List of Tables Table 1 : 1. Introduction: 1.1 Description: 1.2 Scope: 2. Business Requirements: 2.1 Background: 2.2 Business Objectives: 2.3 Vision: 3. Stakeholders: 4. Elicitation Techniques: 4.1 4.2 4.3 5. User requirements: 6. Software Requirements: 6.1 Functional Requirements: 6.2 Non-Functional Requirements: 7. Models: References Appendices The Project Details: 1) Work with your group to suggest an idea for a system that you will work on. 2) Describe your idea and identify the scope of the system: you have to give a brief description of your system which is supposed to be designed and then specify its scope. 3) Identify the business requirements of the system: you have to specify the business requirements: background, business objectives and vision statement of the proposed system. 4) Identify the stakeholders of the system: you have to define at least three stakeholders of the system who have interest in the system directly or indirectly and describe them. 5) Use at least 3 Elicitation techniques: state your chosen techniques and describe how you used them. 6) Write all possible user requirements for the three stakeholders: you are supposed to pick three different stakeholders listed above and write all possible user requirements for each one of them. 7) Write your software requirements: after identifying the user requirements, you are supposed to derive all possible software requirements for each user requirements identified above. Classify the requirements to Functional requirements and Non-Functional requirements (you must have at least totally 30 requirements). 8) Provide at least two relevant requirements modelling diagrams. 9) Write a report: that describes the material concerning above 8 points. (You can look at IEEE Standard: ISO/IEC/IEEE 29148:2011 (The document is available in Blackboard). 10) In the cover page of the report, you must write the name of the system and team members' names and their IDs' (Use the General IS department Assignment/Project Template). - Report Formats: The font size is: 12 . The font style: Times New Roman. The font color: black. The alignment: justified. The line spacing: 1.5 lines. Headers: 14, bold, Times New Roman - Sub headers: 12, bold, Times New Roman
