CS319 Module 5-3 Data Prioritization

docx

School

Southern New Hampshire University *

*We aren’t endorsed by this school

Course

319

Subject

Computer Science

Date

Feb 20, 2024

Type

docx

Pages

4

Uploaded by UltraCamelMaster345

Report
Raphael Tolentino CS-319 Prof. Tirell 26 Nov 23 Milestone: Data Priorities 1. Evaluate the data requirements for borrowers. Using the CS 319 CSV Tutorial, linked in this module’s resources, download data from the Kiva Data Snapshots page. What data does the borrower want to access locally? Borrowers want to access data concerning their loan status, amount, payment plan, and PII information. What data fields from the CSV file will be most applicable? From the loans.csv, this would be columns F-G for the loan amount, and loan status, column AG for how often they would pay, and columns A, B, and M for PII information such as Loan ID, Loan Name, and the purpose of the loan. What type of interface is possible with the limited resources of an embedded system? Given the limitations of an embedded system, a text based approach might accomplish all of the users’ needs. Who will the different users of the system be? What will each user need to be able to do? The primary users of this system would be the borrowers. They would need to be able to view details about their loans, track their repayment progress, and possibly request new loans. What are the design requirements for the system?
The system should be easy to navigate for an international audience. Additionally, it should provide concise and accurate information on the users’ loan(s) and repayment schedule. Lastly, it should have a secure layer to safeguard bank information and other PII related items. 2. Assess specific borrower stories to refine their data needs. After reviewing some of the borrowers’ information, the description provides plenty of information to get a picture of our users’ needs and stories. 1) Vangie – borrowed to support her family in the Philippines. Uses the money for capital for her buy-and-sell charcoal business which supports and feeds her family. 2) Bibi – borrowed money to support her 16-yr old daughter’s educational expenses such as coaching and exam fees. 3) Riya – from Cambodia; aged 51, married and with three children; borrowed money to use for house repair and maintenance. 4) Rosemarie – from Philippines; aged 40 with three children; borrowed money to use as capital for her farm in the Philippines to buy feeds, piglets, and other supplies to raise her pigs. 5) Aigul – from Kyrgyzstan; aged 27 with one son, borrowed money to purchase another purebred cattle for her already successful farm. It is evident from these user stories that borrowers intend on using the borrowed money as capital to continue running their business and ensuring they have a way of supporting their families. Additionally, the users all come from different age groups, and locations, therefore the user design needs to be simple to be understood and navigated by different technical savviness and skill. Moreover, we also need to present information that can communicate across different
cultures. Our priority will then be simplicity and should be easy to navigate using any mobile devices, primarily flip-phones. In conclusion, reviewing these user stories has highlighted the importance of gathering user stories, requirements, and potentially feedback to cater to their wants and needs. Particularly in this case where we have to cater to the limitation of integrated devices such as flip-phones. 3. Recommend borrower data priorities for UI/UX development: Based on our research, the most important information to display would be the columns in loans.csv F-G, A, B, and M. These columns provide funded loan amount, loan requested, loan id, loan name, and loan purpose respectively. This information needs to be presented in a simple text-based format to accommodate any and all mobile devices currently use internationally. 4. Evaluate the data requirements for lenders: What data does the lender want to access? Lender would want to access the loans they have funded, the total amount of each loan, the repayment schedule, the loan IDs and loan names, and the reason for each loan. What data fields from the CSV file will be most applicable to the lender’s needs? In loans.csv, the same columns that are relevant to borrowers will also be relevant to lenders with the addition of the currency conversion and the country of origin to track accommodation exchanges and default statistics by country. What type of interface is possible with the available resources? Given that we’re not limited to integrated devices such as flip-phones and we have access to cloud-based technology, more complex interfaces that allow lenders to track the overall health of all loans by using graphs and charts would be ideal. Who will the different users of the system be? What will each user need to be able to do?
Your preview ends here
Eager to read complete document? Join bartleby learn and gain access to the full version
  • Access to all documents
  • Unlimited textbook solutions
  • 24/7 expert homework help
The primary users would be the lenders and they would need to track all information about the loans they’ve signed; information such as total funded, loan IDs, and repayment schedule and amounts. What are the design requirements for the system? The system should be easy to navigate and visually pleasing. Additionally, it needs to accommodate future scaling to handle increasing amounts of data. Lastly, it needs to be secure for data transmittal over international standards.

Related Documents

Module 3-2 Pseudocode.docx
CS 230 Project Software Design - Tolentino Project 2.docx
CS 305 Module Two Coding Assignment - Tolentino.docx
CS 305 Module Two Written Assignment Tolentino.docx
Module 4-2 Pseudocode.docx
CS319 Module 2 - Interview and Personas.docx
CS 305 Project Two Practices for Secure Software Report - Tolentino.pdf
Color, Sounds, and Motion.docx
Guided Practice - Network Security.docx
Tenhagen_7-2_Activity.docx
Project Phase 3_ VLANs and IoT.docx
Project - Connecting to the Internet (1).docx
Recommended textbooks for you
Text book image
Database Systems: Design, Implementation, & Manag...
Computer Science
ISBN:9781305627482
Author:Carlos Coronel, Steven Morris
Publisher:Cengage Learning
Text book image
Oracle 12c: SQL
Computer Science
ISBN:9781305251038
Author:Joan Casteel
Publisher:Cengage Learning
Text book image
Np Ms Office 365/Excel 2016 I Ntermed
Computer Science
ISBN:9781337508841
Author:Carey
Publisher:Cengage
Text book image
MIS
Computer Science
ISBN:9781337681919
Author:BIDGOLI
Publisher:Cengage
Text book image
Database Systems: Design, Implementation, & Manag...
Computer Science
ISBN:9781285196145
Author:Steven, Steven Morris, Carlos Coronel, Carlos, Coronel, Carlos; Morris, Carlos Coronel and Steven Morris, Carlos Coronel; Steven Morris, Steven Morris; Carlos Coronel
Publisher:Cengage Learning
Text book image
CMPTR
Computer Science
ISBN:9781337681872
Author:PINARD
Publisher:Cengage
SEE MORE TEXTBOOKS
Recommended textbooks for you
Text book image
Database Systems: Design, Implementation, & Manag...
Computer Science
ISBN:9781305627482
Author:Carlos Coronel, Steven Morris
Publisher:Cengage Learning
Text book image
Oracle 12c: SQL
Computer Science
ISBN:9781305251038
Author:Joan Casteel
Publisher:Cengage Learning
Text book image
Np Ms Office 365/Excel 2016 I Ntermed
Computer Science
ISBN:9781337508841
Author:Carey
Publisher:Cengage
Text book image
MIS
Computer Science
ISBN:9781337681919
Author:BIDGOLI
Publisher:Cengage
Text book image
Database Systems: Design, Implementation, & Manag...
Computer Science
ISBN:9781285196145
Author:Steven, Steven Morris, Carlos Coronel, Carlos, Coronel, Carlos; Morris, Carlos Coronel and Steven Morris, Carlos Coronel; Steven Morris, Steven Morris; Carlos Coronel
Publisher:Cengage Learning
Text book image
CMPTR
Computer Science
ISBN:9781337681872
Author:PINARD
Publisher:Cengage
SEE MORE TEXTBOOKS