Chapter 3: - Requirement & Analysis

Problem definition
Identifying current trends in the online auction market, including popular categories of items, pricing
strategies, and competitive platforms.
Gathering information about what features and functionalities users are looking for in an online auction
system, including ease of use, bidding mechanisms, and payment options.

1. Why Auctions is important?

Ans: Auctions play a significant role in everyone's life they connect us to sell their products as well as
to buy a product. They can help seller to sell what they want to sell and you to buy by making highest
amount.

2. What devices can be used to run this project?

Ans: You need Android & Windows devices to run this project.

3. How old does this Website?

Ans: All age groups can use this application.

4. What is the benefit of your website?

Ans: The main benefit for the website is that buyer and seller can sell and buy their product through
online without being going anywhere.

5. Why am I selected this project?

Ans: There is a growing demand for Auctions in our daily life and there is no site for small area seller to
grow their business.

 Overall Problem
The overall problem revolves around designing and implementing an online auction system that facilitates the
buying and selling of items through a digital platform. The goal is to create a user-friendly system that ensures
transparency, security, and efficiency in the auction process. This involves addressing various challenges such as
user management, bidding processes, item listing, and payment handling.
 Sub-Problems
1. User Registration and Authentication

o Definition: Implement a secure user registration and login system that verifies user identities and
manages user profiles.

2. Auction Listing Management

o Definition: Develop a system for sellers to create and manage auction listings, including item
details and auction parameters.

3. Bidding Mechanism

o Definition: Create a dynamic bidding system that allows users to place bids, view current bids,
and receive notifications.

4. Payment Processing

o Definition: Implement a secure payment gateway to facilitate transactions between buyers and
sellers after the auction ends.

5. User Feedback and Rating System

o Definition: Develop a system for users to provide feedback on transactions and rate other users,
fostering trust in the marketplace.

6. Search and Filter Functionality

o Definition: Implement a search and filtering system that allows users to easily find relevant
auctions based on various criteria.

7. Dispute Resolution and Support System

o Definition: Create a support system for users to resolve disputes and report issues related to
auctions.
 Requirements Specification for Online Auction System
In this phase, we will outline the functional and non-functional requirements for the online auction system, as
well as identify the operations and problems of existing systems.

Functional Requirements

1. User Registration and Authentication

o Users must be able to create an account by providing their email, username, and password.

o Users should be able to log in using their credentials.

o Users must have the ability to recover their password if forgotten.

2. User Profile Management

o Users should be able to view and edit their profiles, including personal information and payment
details.

o Users must be able to view their auction history (both bids and listings).

3. Auction Listing Management

o Sellers must be able to create new auction listings by providing item details (title, description,
images, starting price, and auction duration).

o Sellers should be able to edit or remove their listings before the auction starts.

o Sellers must receive notifications for bids placed on their items.

4. Bidding Mechanism

o Users must be able to place bids on active auctions.

o The system should display current highest bids and notify users when they are outbid.

o Users must receive notifications when the auction is about to end.

5. Payment Processing

o The system must allow buyers to securely process payments after winning an auction.

o Buyers and sellers should receive confirmation of successful transactions.

o The system should manage refunds in case of disputes.

6. User Feedback and Rating System

o Users must be able to leave feedback and rate other users after transactions.

o The system should display user ratings and feedback on their profiles.

7. Search and Filter Functionality

o Users must be able to search for auctions by keywords.

o The system should provide filters for categories, price ranges, and auction status.

o Users should be able to sort search results by various criteria (e.g., ending soonest, highest bid).
8. Dispute Resolution and Support System

o Users must be able to submit support tickets for disputes or issues.

o The system should provide an FAQ and help resources.

 Non-Functional Requirements
1. Usability

o The system must be user-friendly, with an intuitive interface.

o The design should be responsive to support various devices (desktop, tablet, mobile).

2. Performance

o The system must manage concurrent users without significant degradation in response times.

o Search functionality should return results within a few seconds.

3. Security

o User data must be encrypted and securely stored.

o The payment process must comply with relevant security standards (e.g., PCI-DSS).

4. Scalability

o The system should be able to accommodate a growing number of users and auctions without
requiring significant rework.

5. Reliability

o The system must be available 99.9% of the time, with minimal downtime for maintenance.

Operations of Existing Systems:

 Existing online auction platforms typically allow users to create accounts, list items for auction, place
bids, and process payments.

 Most systems provide basic search and filtering capabilities and have some form of user feedback
mechanisms.

 They often include mobile applications for easier access.

 Problems of Existing Systems:
1. User Experience Issues

o Many existing systems have cluttered interfaces that can overwhelm users.

o Navigation can be unintuitive, making it difficult for users to find auctions or manage their
accounts.

2. Security Vulnerabilities

o Some systems may not adequately protect user data or secure payment transactions, leading to
potential breaches.

o Lack of two-factor authentication for enhanced security.

3. Inefficient Bidding Processes

o Users often experience delays in bid updates, leading to confusion and frustration.

o Some platforms do not notify users promptly when they are outbid.

4. Limited Support and Dispute Resolution

o Existing systems may lack effective support channels, making it difficult for users to resolve
issues.

o Inadequate mechanisms for handling disputes can lead to user dissatisfaction.

5. Poor Scalability

o Many systems struggle to handle a large number of simultaneous users, leading to slow
performance during peak times.

6. Inadequate Mobile Experience

o Some platforms do not provide a mobile-optimized experience, limiting accessibility for users on
smartphones or tablets.
 Planning and Scheduling for Online Auction System
Task Breakdown

To effectively plan and schedule the development of the online auction system, we first break down the project
into smaller, manageable tasks. Here is a high-level list of tasks along with their dependencies:

1. Project Initialization

o Define project scope and requirements.

o Identify stakeholders.

o Assemble the development team.

2. User Registration and Authentication

o Design user registration flow.

o Implement registration feature.

o Implement login/logout functionality.

o Develop password recovery process.

3. User Profile Management

o Design user profile interface.

o Implement profile viewing and editing.

o Develop auction history tracking.

4. Auction Listing Management

o Design auction listing interface.

o Implement item listing creation.

o Develop item editing and removal features.

5. Bidding Mechanism

o Design bidding interface.

o Implement bid placement feature.

o Develop real-time bid updates and notifications.

6. Payment Processing

o Research and select payment gateway.

o Implement payment processing system.

o Develop transaction confirmation and invoice generation.

7. User Feedback and Rating System

o Design feedback submission interface.

o Implement feedback and rating features.

o Develop display system for ratings.

8. Search and Filter Functionality

o Design search interface.

o Implement keyword search and filtering features.

o Develop sorting options for search results.

9. Dispute Resolution and Support System

o Design support ticket submission interface.

o Implement dispute resolution workflow.

o Develop FAQ and help resources.

10. Testing and Quality Assurance

o Develop testing strategy (unit, integration, user acceptance)

o Perform system testing and bug fixing.

o Conduct user acceptance testing.

11. Deployment and Maintenance

o Prepare deployment plan.

o Launch the online auction system.

o Plan for ongoing maintenance and support

 Constraints
 Time Constraints: Each task has specific deadlines; for example, user registration must be completed
before the bidding mechanism can be implemented.

 Resource Constraints: Availability of team members, budget limitations, and technology stack
constraints may affect the scheduling of tasks.

 Quality Constraints: Each task must adhere to quality standards, which may require additional time for
testing and revisions.

 Gantt Chart
A Gantt chart provides a visual representation of the project timeline and the schedule of tasks. Here is a
simplified version of what the Gantt chart for the online auction system might look like:

Task Start Date End Date Duration Dependencies

Project Initialization Week 1 Week 2 2 weeks -

User Registration
Week 3 Week 4 2 weeks Project Initialization
and Authentication

User Profile
Week 5 Week 6 2 weeks User Registration
Management
Auction Listing
Week 7 Week 8 2 weeks User Profile
Management

Bidding Mechanism Week 9 Week 10 2 weeks Auction Listing

Payment Processing Week 11 Week 12 2 weeks Bidding Mechanism

User Feedback and

Week 13 Week 14 2 weeks Payment Processing
Rating System
Program Evaluation Review Technique (PERT)
PERT is used to analyse the tasks involved in completing a project. Each task is evaluated based on three-time
estimates:

 Optimistic Time (O): The minimum possible time to complete the task.

 Pessimistic Time (P): The maximum possible time to complete the task.

 Most Likely Time (M): The most realistic time to complete the task.

Using the PERT formula:

Expected Time (E)=O+4M+P / 6

 Example PERT Estimates for Selected Tasks
Task O (weeks) M (weeks) P (weeks) E (weeks)
User
1 2 3 2
Registration
Bidding
2 3 4 3
Mechanism
Payment
2 3 5 3.33
Processing
Testing and
Quality 1 2 4 2.33
Assurance
 Requirements
Hardware Requirements

1. Development Machine (for developers)

o Processor: Intel Core i5 or equivalent (minimum quad-core)

o RAM: 16 GB (minimum)

o Storage:

 SSD with at least 256 GB for faster read/write speeds.

 Additional HDD with at least 1 TB for backups and large data storage.

o Graphics Card: Integrated graphics are acceptable, but a dedicated GPU.

o Display: 1920 x 1080 resolution (minimum) for optimal coding and design experience.

o Input Devices: Standard keyboard and mouse, with optional ergonomic devices for comfort.

2. Server (for hosting the application)

o Processor: Intel Xeon or equivalent, multi-core

o RAM: 32 GB (minimum)

o Storage:

 SSD with at least 512 GB for fast access to databases and application files.

 Additional HDD with at least 2 TB for backups and storage of user data.

o Network Interface: Gigabit Ethernet for reliable and fast internet connectivity.

o Power Supply: Uninterruptible Power Supply (UPS) for backup power during outages.
Software Requirements
1. Operating System

o Development Machine:

 Windows 10/11, macOS, or a Linux distribution (e.g., Ubuntu or CentOS).

o Server:

 Linux distribution (e.g., Ubuntu Server, CentOS, or Debian).

2. Web Server

o Apache for serving the web application.

3. Database Management System

o MySQL or MongoDB for data storage.

4. Programming Languages and Frameworks

o Frontend:

 HTML, CSS, and JavaScript for UI development.

 Frameworks like React, Angular, or Vue.js for building interactive components.

o Backend:

 Node.js, Python (Django/Flask), or PHP for server-side development.

5. Development Tools

o IDE/Text Editor:

 Visual Studio Code, IntelliJ IDEA, or PyCharm.

o Version Control System:

 Git (with GitHub, GitLab, or Bitbucket for repository management).

6. Libraries and Frameworks

o CSS Frameworks:

 Bootstrap or Tailwind CSS for responsive design.

o Authentication Libraries:

 OAuth, JWT, or Passport.js for user authentication and authorization.

7. Monitoring Tools

o Application Performance Monitoring:

 New Relic or Prometheus for performance tracking and monitoring.

 Preliminary Product Description for Online Auction
System
Requirements:

 User Management:

o Registration and authentication processes.

o Profile management including personal information and auction history.

 Auction Management:

o Functionality for sellers to create, edit, and remove auction listings.

o Real-time bidding system allowing users to place bids and receive notifications.

 Payment Processing:

o Secure payment gateway for transactions between buyers and sellers.

o Mechanisms for invoicing and refunds.

 Search and Filter Features:

o Users should be able to search for items and filter results based on various criteria.

 Feedback System:

o Allow users to rate transactions and provide feedback.

 Support and Dispute Resolution:

o A system for submitting support tickets and managing disputes.

 Functions and Operation of the Application/System
1. User Registration and Authentication

o Users can register using email, username, and password.

o Users can log in, log out, and recover their passwords if forgotten.

o Profiles can be edited to update personal information and payment details.

2. Auction Listing Management

o Sellers can create auction listings by providing details such as title, description, images,
starting price, and auction duration.

o Users can view active, upcoming, and past auctions.

o Sellers can edit or delete their listings before the auction starts.

3. Bidding Mechanism

o Users can place bids on active auctions.

o The system updates the highest bid in real-time, allowing for competitive bidding.

o Notifications are sent to users when they are outbid or when the auction is about to close.

4. Payment Processing

o The system securely processes payments after a successful bid.

o Users receive confirmation of their transactions via email.

o A refund process is in place for disputes or cancellations.

5. Search and Filter Functionality

o Users can search for items using keywords.

o Filters are available to narrow results by categories, price ranges, and auction status.

o Sorting options allow users to find items based on different criteria (e.g., ending soonest,
highest bid).

6. User Feedback and Rating System

o Users can leave feedback and rate their experience after each transaction.

o Ratings and reviews are displayed on user profiles, promoting trust and accountability.
7. Dispute Resolution and Support System

o Users can submit support tickets for any issues or disputes encountered during the auction
process.

o An FAQ section provides answers to frequent questions.

o Users can access customer support through chat or email for additional assistance.

8. Admin Panel

o Admins can manage users, listings, and oversee transactions.

o Analytics and reporting features help track system usage and performance metrics.
 Conceptual Models for Online Auction System.
1. Use case diagram

A use case diagram is a visual representation of the interactions between users (or "actors") and a system,
illustrating the system's functionality from the users' perspective. In the context of an online auction system, the
use case diagram outlines how different actors interact with the system to perform specific tasks, known as use
cases.
2. Sequence Diagram

A sequence diagram is a type of interaction diagram in UML that shows how objects interact in a particular
scenario of a use case, representing the sequence of messages exchanged between them over time. In this, a
sequence diagram can illustrate how different components interact during specific processes, such as bidding on
an item or creating a new auction.
3. system sequence diagram (SSD)

A system sequence diagram (SSD) is a specific type of sequence diagram that focuses on the interactions
between a system and its external actors for a particular use case. It visually represents how a system responds to
messages from its users and outlines the sequence of events in a specific scenario. In the context of an online
auction system, the system sequence diagram can help clarify the interactions during key processes, such as
placing a bid or creating an auction.
4. Class diagram

A class diagram is a static structure diagram in UML (Unified Modelling Language) that describes the structure
of a system by showing its classes, their attributes, methods, and the relationships between them. In the context
of an online auction system, a class diagram can help visualize the various components of the system, their
attributes, and how they interact with each other.
5. Collaboration diagram

A collaboration diagram (also known as a communication diagram) is a type of UML (Unified Modelling
Language) diagram that shows how objects interact in a particular scenario, focusing on the relationships
between objects and the messages they exchange. Unlike sequence diagrams, which emphasize the timing of
messages, collaboration diagrams highlight the structural organization of the objects involved in the interaction.
6. ER diagram.

An Entity-Relationship (ER) diagram is a visual representation of the entities in a system and the
relationships between them. ER diagrams are commonly used in database design to illustrate the structure of
a database and how data is connected. In the context of an online auction system, an ER diagram helps in
understanding the various entities involved, their attributes, and the relationships among them, guiding the
development of the underlying database.
7. Deployment diagram

A deployment diagram is a type of UML (Unified Modelling Language) diagram that illustrates the
physical deployment of artifacts (software components, hardware devices, etc.) in a system. It represents how
software components are distributed across the hardware and how they communicate with each other. In the
context of an online auction system, a deployment diagram helps visualize the hardware and software
architecture, showing where each component resides and how they interact within the system's environment.
 8. Activity Diagram

An activity diagram is a type of UML (Unified Modelling Language) diagram that represents the flow of control
or data in a system, illustrating the dynamic aspects of the system. It shows the sequence of activities, decisions,
and events that occur in a process. In the context of an online auction system, an activity diagram can help
visualize user interactions, system processes, and workflows involved in various tasks such as placing a bid,
creating an auction, or managing payments.