Laboratory file
on
SOFTWARE ENGINEERING AND METHODOLOGY
School of Engineering and Technology
Department of Computer Science and Engineering
Subject code – CSP 357
SUBMITTED BY: SUBMITTED TO:
Name : Yash Manav Mr. Ashish Jain
Roll No: 2301010997
Sharda University
Greater Noida, Uttar Pradesh
LIST OF EXPERIMENTS
COURSE DATE
S.NO. EXPERIMENT NAME OUTCOME
1 Design requirement analysis and develop Software Requirement
Specification Sheet (SRS) for indikart e-commerce
platform in IEEE standard. CO1
Draw the user‘s view analysis for the suggested system: Use case
2 diagram, Activity Diagram and State chart Diagram. CO2
Draw the structural view diagram for the system: Class
3 diagram, object diagram and Sequence diagram. CO2
Perform Unit testing of calculator program using Junit testing
4 framework. CO3
Perform Integration testing of calculator program using
5 Junit testing framework. CO3
Design Test Case for Inventory Management System based on
6 System Specification. CO4
Design Test cases and perform manual testing of login module
7 of FlipKart (as an example). CO5
VALUE ADDED EXPERIMENTS
EXPERIMENT NAME OUTCOME
Experiment: 01
Aim: Design requirement analysis and develop Software Requirement Specification Sheet (SRS) for
IndieKart- E-commerce platform for local handicrafts in IEEE standard.
1. Introduction
1.1 Purpose
This SRS outlines the functional and non-functional requirements for IndieKart, an e-commerce
platform aimed at promoting and selling locally made handicrafts. The document is intended for
developers, testers, project managers, and stakeholders involved in the design, development, and
deployment of the system.
1.2 Scope
IndieKart allows local artisans to showcase their products and reach wider markets. The system includes
modules for user registration, product browsing, cart management, checkout process, event discovery,
wishlist features, and order tracking. The final product will be a responsive web application.
1.3 Definitions, Acronyms, and Abbreviations
UI: User Interface
DBMS: Database Management System
SKU: Stock Keeping Unit
COD: Cash on Delivery
SRS: Software Requirement Specification
2. Overall Description
2.1 Product Perspective
IndieKart is a standalone e-commerce platform focused on the Indian handicrafts market. It may
integrate with third-party payment gateways and shipping services.
2.2 Product Functions
User Registration & Login
Browse and search products
Add to Cart and Wishlist
Secure Checkout with multiple payment options
Order Management and Confirmation
Admin panel for managing products and orders
Event listing for workshops and fairs
2.3 User Classes and Characteristics
Customer: General users with basic tech knowledge
Artisan/Seller: Skilled craftspeople; need simple product upload system
Admin: Technical users managing the platform
2.4 Operating Environment
Frontend: HTML5, CSS3, JavaScript
Browser: Chrome, Firefox, Safari
OS: Windows, Linux, Android
2.5 Design and Implementation Constraints
Use of open-source technologies
Mobile responsiveness required
Compliance with standard web security practices
2.6 Assumptions and Dependencies
Users have stable internet connection
3. Specific Requirements
3.1 External Interfaces
3.1.1 User Interfaces
Responsive UI with navigation bar, product cards, filters
Admin dashboard with tabs for Products, Orders, Users
3.1.2 Hardware Interfaces
None specific; runs on user’s web browser
3.1.3 Software Interfaces
Firebase / MongoDB for DB
Payment APIs (Razorpay/Paytm)
Optional: Email API for notifications
3.2 Functional Requirements
FR1: The system shall allow users to register and log in
FR2: Users shall be able to browse and search products
FR3: Products shall be filterable by category, price, or popularity
3.3 Performance Requirements
Page load time < 2 seconds
Handle 100+ concurrent users
Real-time cart updates
3.4 Design Constraints
Use Firebase or Node.js for backend
Frontend must use vanilla JS or a framework like Angular
3.5 Quality Attributes
Usability: Simple and intuitive design
Reliability: 99% uptime
Security: Encrypted login, secure payment
Maintainability: Modular architecture
Scalability: Future integration of Android/iOS apps
3.6 Documentation Requirements
User Manual
Developer Guide
Admin Control Documentation
3.7 Security Requirements
User authentication with session management
Encrypted payment and personal data
Role-based access control
3.8 Legal and Compliance Requirements
Must comply with Indian e-commerce policies
Result: The SRS for IndieKart has been successfully developed following the IEEE 830-1998 standard.
It clearly outlines the system’s scope, functional and non-functional requirements, and external
interfaces. The document provides a solid foundation for designing, developing, and testing the e-
commerce platform. It ensures better communication among stakeholders and supports structured
development with defined performance, security, and usability goals
Functional Requirements :
1. User Authentication and Session Management
o Sessions would expire too quickly and often while filling forms, leading to user
frustration.
2. Train Search and Seat Availability
o The displayed availability was often not in real-time, causing booking errors or failed
transactions.
3. Ticket Booking Workflow
o The booking process was unnecessarily long and required too many steps without
guidance.
4. Payment Integration
o Payments would frequently fail due to poor integration with banks and gateways.
Non-Functional Requirements :
1. Performance and Scalability
o The system would crash or hang during high traffic times like Tatkal bookings.
2. Usability and User Experience (UX)
o The interface was cluttered, confusing, and not user-friendly, especially for first-time
users.
3. Reliability and Fault Tolerance
o If a payment failed, there was no smooth retry mechanism or Instant refund confirmation.
4. Mobile and Accessibility Support
o The site wasn’t responsive or accessible for differently-abled users or mobile phone
users.
