0% found this document useful (0 votes)
13 views3 pages

? SDA Assignment 2

Uploaded by

raozeeshanhafiz
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
13 views3 pages

? SDA Assignment 2

Uploaded by

raozeeshanhafiz
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd

🌂 SDA Assignment 2 – Umbrella Activities for BMS

👥 Group Members:

 Khuzaima Saqib – SE231009


 M. Furqan Shaukat – SE231026
 Rao Miran – SE231031

1. Project Tracking and Control

We monitored our project's progress in four main phases:

 Requirement Gathering
 Development & Testing
 Pilot Launch
 Final Deployment

✅ We ensured tasks stayed on schedule using our project timeline.


✅ Progress was tracked using simple checklists and weekly status updates.

2. Risk Management

Some key risks we identified and how we planned for them:

 🔐 Security Breaches → Used encryption and multi-factor authentication (MFA).


 💸 Budget Overrun → We adjusted features and planned for phased rollout.
 🛑 System Downtime → Ensured 99.9% uptime and had cloud hosting via Microsoft
Azure.

3. Software Quality Assurance

We focused on non-functional requirements like:

 📈 Performance – Fast responses under 2 seconds


 🔁 Reliability – 99.9% uptime
 🔒 Security – Password encryption
We also tested functionalities like login, signup, deposits, withdrawals, and transaction
views.
4. Formal Technical Reviews

At the end of each phase, we:

 ✅ Reviewed use case and activity diagrams


 ✅ Double-checked that all functional and non-functional requirements were met
 ✅ Ensured our design matched user needs (like mobile/online access)

5. Measurement

We used simple metrics to measure progress and performance:

 Response Time – under 2 seconds per action


 👤 User Load Handling – up to 1000 users at once
 ✅ Completion Tracking – % of modules developed and tested

6. Software Configuration Management

We:

 📂 Managed our files and code using version control (e.g., Git)
 💻 Kept backups and recorded each update/change
 🧱 Organized our project folder with separate areas for frontend, backend, and database
code

7. Work Product Preparation and Production

We created:

 📄 Feasibility Report
 📐 Use Case and Activity Diagrams
 📜 Requirement Documents (Functional + Non-Functional)
 📦 Modules for account handling, login, transaction history, etc.

8. Reusability Management
We ensured parts of our system can be reused:

 ♻️Login System can be used for other banking or e-commerce apps


 🔧 Transaction Management Module can be adapted for finance systems
 🧱 Modular codebase supports easy reuse and extension

You might also like