Task
Background:
Your project is cu
ently in the building phase, and your team is in charge of it. The fourth set of
deliverables requires your team to apply more extensive modeling of the essential user stories
to guarantee that the development team completely understands and captures the user's
demands during the sprint. This is often done in the backlog grooming stage of an agile sprint
when it is relevant to the team. It is possible to do this ahead of time for initiatives that will
enefit from BDUF or BRUF.
This collection of deliverables will be limited to the two main user stories in your application. In
practice, you will choose all user stories that can benefit from further in-depth research and
generate use case na
atives, sequence and/or state diagrams as needed to assist the team.
Deliverable 4 requires you to choose two key user stories and create fully clothed use case
na
atives for those user stories. After that, you'll draw System Sequence Diagrams for the two
use cases and a Design Sequence Diagram for the principal use case. You will also draw a
state diagram for the most active class in the major use case. Following these deepe
investigations, you will be able to edit your class diagram to reflect the features depicted in the
state and sequence diagrams.
My Task:
1) Use Case Na
atives (genesis)
a) Create use case na
atives for the 2 highest priority user stories in the application
Use Case Section Comment
Story As the user of the platform, I want my data to be protected, transactions to be secure, & have full transparency about where my money will be through
egular security updates from the platform in order to have confidence in using the platform for my personal projects.
Use Case Title Use case 1: Security
Story owner Malon
Story Creator Team 19
Revision and Interests Version 1
Stakeholders and intrests Malon, TA
Scope,Context, and
Background
This task specifically falls under a specific task in security when creating the sight there should not be aleak of information.
Dependencies Assumes:
● Robust security protocols: The platform must have robust security protocols in place to protect user data and transactions. This may
include measures such as encryption, firewalls, intrusion detection, and prevention systems, and regular security audits.
● Transparency: The platform must provide clear and transparent information about how user data is being used, where their money is going,
and how transactions are being processed. This includes providing users with access to real-time updates on their transactions and
alances.
● Regular security updates: The platform must provide regular security updates to ensure that their security protocols are up-to-date and
effective against emerging threats.
● User education: Users must be educated about how to protect their own data and avoid common security pitfalls, such as phishing scams o
insecure passwords.
● Trustworthiness: The platform must establish a reputation as a trustworthy and reliable service provider, which can be built through
transparent communication, prompt resolution of issues, and a track record of keeping user data safe and secure.
Actor Role(s) Lender and Bowers for money
Precondition(s) To fulfill the user's request for data protection, transaction security, and transparency, the platform must have a secure and reliable infrastructure with
obust security protocols, such as encryption and multi-factor authentication. Additionally, a clear and transparent privacy policy outlining how user data
is collected, stored, and protected, along with a system for providing regular security updates and a dedicated team of security experts, is necessary.
Lastly, there must be a process in place for responding to security incidents and resolving any issues that may arise promptly and effectively.
Success Guarantee Ensure secure transactions, and provide transparency about where user money is going can be guaranteed by implementing robust security protocols,
egular updates, and having a dedicated team of security experts. This should be complemented with clear and transparent privacy policies and use
education to avoid security pitfalls. A process for responding to security incidents and resolving issues in a timely and effective manner is essential, as is
establishing a reputation as a trustworthy and reliable service provider. Ultimately, success would be providing a secure, reliable, and transparent platform
that users can trust with their personal data and projects.
Minimal Guarantee To guarantee protection of user data and secure transactions with transparency, the platform should have robust security protocols, provide regula
security updates, and have a clear privacy policy that outlines data collection and protection.
Triggers Users may have concerns about privacy and security, transparency, and trust when using online platforms dealing with personal data and financial
transactions. Past security
eaches and general skepticism about such platforms may lead to these concerns, and users may want to know how thei
personal data is being used. They may also wo
y about potential financial loss if their data or transactions are compromised, especially for personal
projects with financial impacts. Legal or regulatory obligations may also require users to use platforms that meet specific security and transparency
standards for compliance.
Main Scenario
1. Implement strong security measures, such as encryption and multi-factor authentication, to protect user data and prevent unauthorized
access.
2. Provide regular security updates and patches to address any vulnerabilities that may arise, ensuring the platform is up-to-date with the
latest security technologies.
3. A clear and transparent privacy policy that outlines how user data is collected, stored, and used, as well as how it is protected.
4. Educate users on how to protect their own data and avoid common security pitfalls, such as phishing scams or insecure passwords.
5. The platform should have a process in place for responding to security incidents and resolving any issues that may arise in a timely and
effective manner.
6. Establish a reputation as a trustworthy and reliable service provider through transparent communication, prompt resolution of issues, and a
track record of keeping user data safe and secure.
Alternative Scenarios o
Extensions
1. Enhanced transparency:
a. The user may want more detailed information about where their money is going, such as the specific fees or charges
associated with each transaction.
2. Personalized security options:
a. The user may want the ability to customize their security options, such as setting their own password complexity
equirements or choosing which types of notifications they receive regarding their account activity.
3. Integration with other security tools:
a. The user may want the platform to integrate with other security tools, such as antivirus software or firewalls, to provide an
additional layer of protection.
4. Support for multiple cu
encies:
a. The user may want the platform to support multiple cu
encies, so they can easily manage their finances across different
countries or regions.
5. Seamless user experience:
a. The user may want a platform that provides a seamless user experience, with intuitive interfaces and fast response times, to
ensure they can easily and efficiently manage their personal projects.
6. Strong customer support:
a. The user may want a platform that offers strong customer support, with fast response times and knowledgeable
epresentatives, to ensure any issues or concerns can be addressed quickly and effectively.
Acceptance Criteria Minimum:
● All user data and transactions must be encrypted both at rest and in transit using industry-standard encryption protocols.
● The platform must provide multi-factor authentication options, such as SMS or email-based one-time passwords or biometric login, to
ensure the security of user accounts.
● The platform must provide regular security updates, including vulnerability assessments and software patches, to protect user data and
transactions from potential security threats.
Should Have:
● The platform must provide detailed information about all fees and charges associated with each transaction, including any cu
ency
conversion fees or processing fees.
● The platform must allow users to customize their security options, such as setting their own password complexity requirements o
choosing which types of notifications they receive regarding their account activity.
● The platform must provide integration with other security tools, such as antivirus software or firewalls, to provide an additional layer of
protection for user data and transactions.
● The platform must support multiple cu
encies to allow users to manage their finances across different countries or regions.
● The platform must provide a seamless user experience with intuitive interfaces and fast response times to ensure users can easily and
efficiently manage their personal projects.
Nice to Have:
● The platform must have a dedicated and knowledgeable customer support team, with fast response times and multiple communication
channels, to address any issues or concerns that users may have regarding their data or transactions.
● The platform must provide a clear and detailed explanation of how user data is collected, used, and shared, including any third-party
vendors that have access to user data.
● The platform must have an intuitive and user-friendly interface, with fast response times and minimal downtime, to ensure a seamless use
experience.
● The platform must support multiple cu
encies, with clear and accurate conversion rates, to allow users to easily manage their finances
across different countries or regions.
Test case 1. Open the platform and login to the user account.
2. Navigate to the user profile and check if all personal data is encrypted both at rest and in transit using industry-standard encryption
protocols.
3. Attempt to perform a transaction and verify that multi-factor authentication options, such as SMS or email-based one-time passwords o
iometric login, are available to ensure the security of user accounts.
4. Verify that the platform provides regular security updates, including vulnerability assessments and software patches, to protect user data
and transactions from potential security threats.
5. Check if the platform provides a clear and detailed explanation of how user data is collected, used, and shared, including any third-party
vendors that have access to user data.
6. Verify that the platform provides detailed information about all fees and charges associated with each transaction, including any cu
ency
conversion fees or processing fees.
7. Attempt to customize the security options, such as setting the password complexity requirements or choosing which types of notifications
to receive regarding account activity.
8. Verify that the platform integrates with other security tools, such as antivirus software or firewalls, to provide an additional layer of
protection for user data and transactions.
9. Check if the platform supports multiple cu
encies and if the conversion rates are clear and accurate.
10. Verify that the platform provides a seamless user experience with intuitive interfaces and fast response times to ensure users can easily and
efficiently manage their personal projects.
11. Contact customer support and verify that the team is dedicated and knowledgeable, with fast response times and multiple communication
channels, to address any issues or concerns that users may have regarding their data or transactions.
12. Check if the platform provides a clear and detailed explanation of how user data is collected, used, and shared, including any third-party
vendors that have access to user data.
13. Verify that the platform has an intuitive and user-friendly interface, with fast response times and minimal downtime, to ensure a seamless
user experience.
14. Attempt to use the platform in different countries or regions and verify that it supports multiple cu
encies to allow users to easily manage
their finances across different countries or regions.
Exclusion/Out-of-Scope Items The article lists several types of testing that are not directly related to security and transparency of the platform, such as performance testing,
compatibility testing, integration testing with third-party services, regulatory compliance testing, backup and disaster recovery testing, scalability testing,
user interface testing, and marketing testing.
Assumptions The user expects the platform to protect their personal data and ensure secure transactions. They want transparency about where their money goes and
expect regular security updates to maintain the platform's security. The user seeks confidence in using the platform for their personal projects, suggesting
they plan to use it regularly.
Non-Functional Requiements The non-functional requirements for the platform include secure systems and protocols with regular updates, transparency about money flow and use
data practices, high performance and scalability, an intuitive and user-friendly interface, backup and disaster recovery processes, and compliance with
egulatory frameworks like GDPR and HIPAA.
Stroy Details, Open issues, and
Conversation
This story details the user's requirements for data protection, secure transactions, and transparency in using the platform for personal projects. However,
open issues remain about how to achieve these requirements, such as specific measures for data protection and compliance with regulatory frameworks.
The development team needs to have conversations with stakeholders and establish a clear plan for security updates and compliance to meet the user's
expectations. Regular revisits and documentation of these conversations and plans are necessary to ensure the platform meets the user's needs.
Reference and Attachment To be determined
Use Case Section Comments
Story As a lender, I want there to be a credit-rating system from third-party credit agencies in order to make an informed decision regarding whether or not
the bo
ower is trustworthy.
Use Case Title Use Case 2: Credit Rating System
Story Owner Mahloan
Story Creator Team 19
Revision and Approvals Version 1, Initial Draft
Stakeholders and Interests Professor Vroomen & Vidyasri Ravi
Scope, Context, and Background Having a third-party credit rating agency provide ratings of bo
owers: It is often the case that there will be an individual who will bo
ow a large sum
of money but not have the financial backing to pay the money back. This can cause losses for both the bo
ower and lender and result in a loss of
credibility for the bo
ower. In order to avoid this, it is important that bo
owers share their credit score/credit rating in order to provide some scope of
credibility for their ability to