Afjal Hossain - dspace.daffodilvarsity.edu.bd:8080

This Project entitled “Business Plax: For a Small Business Management Area”, submitted by Afjal Hossain to the Department of Software Engineering, Daffodil International University has been accepted as satisfactory for the partial fulfillment of the requirements for the degree of B.Sc in Software Engineering and approved in respect of its style and content. First of all, I am grateful to Almighty Allah for making me eligible to complete this project. I would like to thank those who helped in my project by their very important suggestions without their passionate participation and input; the project could not be executed successfully.

I take this opportunity to write my sincere thanks to all the faculty members of the Department of Software Engineering for their help and encouragement. We also declare that neither this project nor any part of the project has been submitted elsewhere for the award of any degree. Like any other project, hard work, perseverance, dedication and concentration are essential to complete the project.

There are many reasons to capitalize project development, such as stakeholder requirements to be properly met. If you follow requirements analysis properly then it helps a lot in project development.

Project Overview

Project Objectives

Background

Benefits and Beneficiaries

Goals

Stakeholder

Proposed System Model

Project Schedule

Gantt Chart

Release Plan or Milestone

Functional Requirements

Login for Admin
Setup Category and Product
Party (Customer and Supplier)
Operation (Purchases, Stock and Sales)
Report (Purchases and Sales)

When the admin buys a product he increases the stock availability and when he goes to sell a product he can see the available product stock availability and when the product is sold the product stock automatically decreases.

Data Requirements

Performance Requirements

Speed and Latency Requirements

Precision or Accuracy Requirements

Capacity Requirements

Dependability Requirements

Reliability Requirements
Availability Requirements
Robustness or Fault-Tolerance Requirements
Safety-Critical Requirements

Also, ensure that the system continues properly even if some of its components fail.

Maintainability and Supportability Requirements

Maintenance Requirements
Supportability Requirements
Adaptability Requirements
Scalability or Extensibility Requirements

Our technical expertise, combined with a deep understanding of the built environment, enables us to help a wide range of clients address the impacts of climate change. Ensure that the system easily adapts to new functionalities, interfaces, devices and input types.

Security Requirements

Access Requirements

Integrity Requirements

Privacy Requirements

Usability and Human- Interaction Requirements

Ease of use Requirements
Understandability and Politeness Requirements
Accessibility Requirements
User Documentation Requirements
Training Requirements
Look and Feel Requirements
Appearance Requirements
Style Requirements

The requirements for how easy it should be for people and our system are very easy to use and understand. The gathering of the user who expects and must do it in the system properly is mandatory because this request is given directly by the user. And after completion, the system user can give new requests, then it is also added to the system.

If the user must be trained to use the system properly, then you must train them properly. In our project we don't need this kind of training for users, but a simple guide for them. If your systems look like garbage, then the user may be bored and not go to the next step.

The look and feel requirements are how the system will look and how our system's user interface or graphical user interface will be displayed to the user. Description If there is no optional word in the field that means this field is mandatory for input.

Operational and Environmental Requirements

Release Requirements

Legal Requirements

Use Case Diagram

Login for Admin
Category Setup
Product Setup
Manage Customer
Manage Supplier
Purchase Operation
Stock Operation
Sale Operation
View Purchase Report
Sale Report
Send Message

Prerequisites An administrator must exist in the database before the login can complete successfully Prerequisite An administrator can access the system. 1 The system displays the category screen 2 Admin can add a category and save it 3 View the list of categories. 4 Admin can edit each category 5 Can search specific category 6 Admin can delete each category Alternative Flows Step Branching Action.

4 Admin can edit each product 5 Can search specific product 6 Admin can delete each of the product Alternative Flow Step Branch Action. 2a.1 Mandatory field empty 2a.2 Input misses match 3 Can't see product list 4 Admin can't edit product 5 Search job. Failed End State Unable to add, edit, delete, view and search customer details in the system.

4 Admin can edit each customer 5 Can search specific customer 6 Admin can delete each customer Alternative Flow Step Branch Action. Failed End State Unable to add, edit, delete, view and search supplier details in the system. 4 Admin can edit each supplier 5 Can search specific supplier 6 Admin can delete each supplier Alternative Flow Step Branch Action.

Success End Condition Admin Add, edit, delete, view and search purchase details in the system. Failed End Condition Unable to add, edit, delete, view and search purchase details in the system. Success End Requirement Admin Add, edit, delete, view and search sales details in the system.

Failed End State Unable to add, edit, delete, view and search sales details in the system. 4 Admin can edit each of sales operations 5 Can search specific sales operation 6 Admin can delete each of sales. Success End State Visitor can send message into the system Failed End State Unable to send message into the system.

Activity Diagram

Activity Diagram for Login
Activity diagram for Category Setup
Activity diagram for Product Setup
Activity Diagram for Purchase Operation
Activity Diagram for Stock Operation
Activity Diagram for Sale Operation
Activity Diagram for Purchases Report
Activity Diagram for Sale Report
Activity Diagram for Send Message

In the customer module, admin can add new customer and he can also update, delete, search the previous customer after logging into the system. In the Supplier module, the admin can add new customer and he can also update, delete, search the previous customer after logging into the system.

Figure 3.2.2: Activity diagram for Category Setup

Sequence Diagram

Sequence diagram for Login

Sequence diagram for Admin Setup Category

Sequence diagram for Product Setup

Sequence diagram for Manage Customer

Sequence diagram for Manage Supplier

Sequence diagram for Purchase Operation

Sequence diagram for Sales Operation

Sequence diagram for Report (purchase & Sale)

Development tools and Technology

User Interface Technology

Implemented Tools and Platform

Visual Studio, also known as Microsoft Visual Studio and VS, is an integrated development environment for Microsoft Windows. It includes a code editor, debugger, GUI design tool and database schema designer and supports most major revision control systems. Asp.Net MVC is a framework that adds support for the MVC design pattern to Asp.Net.

The main problem when using asp.net in my project is the better performance of asp.net mvc.

Class Diagram

Database Design Diagram

Testing Features

Feature to be tested

Testing Strategy

Test Approach

Testing approach is created by the individual tester based on the module or application, which means his own views or approaches for that module. Black box testing is a testing method that is performed without touching the internal function. This technique aims to eliminate the input data set and reduce the number of redundant test cases by eliminating the test cases that generate the same output.

Each partition has its maximum and minimum values and these maximum and minimum values are the boundary values of a partition. This type of testing, the code is visible to the tester and the tester must have knowledge of the function.

Pass/Fail Criteria

Testing Schedule

Trace Ability Matrix

Testing Environment

Test Cases

Login
Category
Product
Customer
Supplier
Purchase
Stock
Sales
Purchase Report
Sales Report
Send message

Brief description: The administrator enters the category code and name and submits the data and saves it as a unique product category in the database. Brief description: The administrator entered all the information about the product and submitted the data and saved it under a specific product category in the database. Short description: If the admin fills in all the mandatory fields of the customer and submits the data, then the customer is added to the application.

Short description: If the admin fills all the required fields of the Supplier and submits the data, then add the supplier to the application. Brief Description: If the administrator fills all the required fields of Purchase under Supplier and submits the data, then save it to the database. Brief description: When the supplier will purchase the product and the administrator will add it to the system, then the system provides the product purchase stock data from the database.

Brief description: When a product is sold to a customer and the administrator enters the sales information into the system and stores it in the database. Brief Description: When an admin searches for purchase information within the start date and end date, the system displays all the purchase details from the database. Brief Description: When the admin searches for sales data within the start and end date, the system displays all the sales details from the database.

Brief description: Visitor level user can send message to admin without logging into the application.

Application Home Page

Admin Login Page

Admin Home Page