Scribd
Upload
8 views

Assignment - 8

Uploaded by

bsse2380220
Copyright
© © All Rights Reserved
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
8 views

Assignment - 8

Uploaded by

bsse2380220
Copyright
© © All Rights Reserved
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
You are on page 1/ 4

Name: Abdul Rafay

Registration Number: 2380220


Program: BSSE 3-D

Assignment
Summary of Lecture: 8
 Requirements engineering defines what a project needs to accomplish so everyone
understands it clearly.
 Key steps in requirements engineering:
 Gather requirements: Talk to users, project managers, and others to understand their
needs.
 Review requirements: Ensure they make sense, aren't repetitive, and resolve any conflicts.
- Check feasibility: Confirm that requirements can be met within time, budget, and
resource limits.
- Clarify and trace requirements: Make sure each one is easy to understand and
linked to its requester.
- Prioritize requirements: Decide what is essential and what can wait, using methods
like the Moscow method (must-have, should-have, could-have, won’t-have).
- Build a prototype: Create a sample version of the software to gather feedback.
- Seek approval: Get everyone’s agreement on requirements before starting work.
 Requirements should be clear, flexible, realistic, and help avoid wasted time and money.
 The goal is to keep everyone informed and aligned to complete the project successfully.
Case Study: Mobile Banking
App
Introduction
The bank requires a mobile application to enable customers to manage their accounts and perform
transactions conveniently from their smartphones. The app should be available on both iOS and
Android platforms to cater to all customers.

Goals & Objectives


The goal of this project is to define the requirements for a secure, user-friendly mobile banking app
that allows customers to:

 Access account information and transaction history.


 Transfer funds, pay bills, and manage payments.
 Receive notifications and alerts for account activity.
 Ensure secure access with strong authentication.

By identifying all stakeholders and gathering both functional and non-functional requirements, this
project aims to deliver a reliable, secure, and efficient app that meets customer needs and banking
standards.

Requirement Specification
1. Functional Requirements:
 Authentication: Secure login, possibly with biometrics (e.g., fingerprint, face ID).
 Account Management: View account balance, transaction history, and account
details.
 Transactions: Transfer funds, pay bills, and schedule payments.
 Notifications: Receive alerts for transactions, low balance, and security events.
 Customer Support: In-app customer support and query handling.

2. Non-Functional Requirements:
 Security: Data encryption, multi-factor authentication, compliance with banking
regulations.
 Performance: Fast loading times, optimized for both iOS and Android.
 Availability: Available 24/7 with minimal downtime.
 Scalability: Able to handle increasing users and transaction loads.
 Usability: Simple, intuitive design that works well on various screen sizes.

3. Use Case Diagrams:


 Diagram(s) depicting key interactions like account login, fund transfer, and
notification setup.
Process to Follow
1. Elicitation
 Identify stakeholders (bank staff, IT teams, customers).
 Conduct interviews and surveys to understand customer needs and preferences.
 Use observation and document analysis to gather detailed requirements.
2. Analysis:
 Prioritize requirements based on customer and business needs.
 Perform dependency mapping to identify how different features rely on each other.
 Conduct a feasibility study to evaluate technical, financial, and time constraints.
 Use tools such as Data Flow Diagrams (DFD) and Entity-Relationship Diagrams (ERD)
to visualize requirements.
3. Design and Validation:
 Requirement Review: Check if all requirements are clear, feasible, and aligned with
objectives.
 Prototyping: Develop a basic prototype to test core features and get feedback from
stakeholders.
 Test Case Design: Create test cases to verify that each function meets the
specifications.
 Verification: Confirm non-functional requirements are met for performance,
security, and usability.

Change Management
 Implement version control to manage changes throughout development.
 Set up a change control process for handling feature updates and new requirements.
 Maintain a traceability matrix to track changes and their impacts on the project.
Outcome
Following this process, the bank will get a clear and detailed list of requirements to help develop a
secure, reliable, and easy-to-use mobile banking app. This app will allow customers to manage their
accounts easily, while keeping their information safe and meeting banking standards.

You might also like