Scribd
Upload
36 views3 pages

Assignment 1

Uploaded by

abhinavsharma349063
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
36 views3 pages

Assignment 1

Uploaded by

abhinavsharma349063
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
You are on page 1/ 3

Amity University, Noida

Assignment #1

Case Study 1: E-commerce Platform Development

Scenario: A company wanted to create an online shopping platform to expand its retail business.
SDLC Methodology: Agile

1. Requirement Analysis:

o Conducted user interviews to determine platform features like product search, cart
functionality, and secure payments.

o Stakeholder input gathered through workshops.

2. System Design:

o Created wireframes and prototypes for the UI/UX.

o Designed a modular architecture with separate services for inventory, payments, and
user authentication.

3. Implementation:

o Development sprints delivered features incrementally.

o Continuous feedback integrated into subsequent iterations.

4. Testing:

o Unit, integration, and performance tests conducted to ensure system reliability.

o User acceptance testing (UAT) carried out with a focus group.

5. Deployment:

o Gradual roll-out with a beta phase for selected users.

o Monitoring tools implemented to track real-time performance.

6. Maintenance:

o Regular updates for bug fixes and feature improvements.

o Customer feedback channels monitored for enhancements.

Outcome: Increased sales by 30% within the first quarter of deployment.

Case Study 2: Bank Loan Processing System

Scenario: A bank needed an automated system to streamline loan application and approval
processes.
SDLC Methodology: Waterfall
1. Requirement Analysis:

o Documented the exact needs for processing, document verification, and risk
assessment.

o Compliance requirements for financial regulations identified.

2. System Design:

o Detailed blueprints for data flow and database structure created.

o Specifications fixed to ensure no scope creep.

3. Implementation:

o Each module (e.g., application intake, risk evaluation) was coded sequentially.

o Used Java and SQL for development.

4. Testing:

o Extensive testing after implementation of each phase.

o Regression tests ensured older functions weren’t affected by new additions.

5. Deployment:

o System rolled out in a phased manner across different branches.

o Training sessions provided for employees.

6. Maintenance:

o Periodic updates for regulatory changes.

o Customer service portal enhanced for self-service options.

Outcome: Loan processing time reduced from 5 days to 2 days.

Case Study 3: Healthcare Mobile App

Scenario: A startup aimed to develop a mobile app for appointment scheduling and telemedicine
consultations.
SDLC Methodology: V-Model (Verification and Validation)

1. Requirement Analysis:

o Key requirements were HIPAA compliance, secure video calls, and a calendar for
appointments.

2. System Design:

o High-level design for core functions.

o Detailed specifications created for APIs, UI, and security mechanisms.

3. Implementation:
o Development carried out in tandem with verification of design documents.

o Swift (iOS) and Kotlin (Android) used for mobile development.

4. Testing:

o Validation tests run parallel to development.

o Focus on security testing and ensuring compliance with health data regulations.

5. Deployment:

o App launched on Google Play and Apple Store.

o Feedback collected for minor patches.

6. Maintenance:

o Continuous improvement based on reviews.

o AI-based triaging feature added in an update.

Outcome: Achieved 50,000 downloads in the first month with a 4.8-star rating.

1. What is Agile methodology, and how is it different from traditional methodologies like
Waterfall?
2. What are the core principles of Agile as defined in the Agile Manifesto?
3. What are the key benefits of using Agile for software development?
4. What are the challenges organizations face when transitioning to Agile?
5. Can Agile be used for non-software projects? Provide examples.
6. How does Agile scale in large organizations (e.g., SAFe, LeSS, Disciplined
Agile)?
7. How can Agile be integrated with DevOps practices?
8. What are some metrics used to measure Agile success?
9. How does Agile manage technical debt?
10. What are the common pitfalls teams face when adopting Agile, and how can
they be addressed?

You might also like