05 FINALSRS 040 Removed 1
05 FINALSRS 040 Removed 1
05 FINALSRS 040 Removed 1
Note: Our software is based on Linear Sequential Model. The Linear Sequential
Model: (Water Fall Model):
The Linear Sequential Model suggests a systematic, sequential approach to
Software development that begins at the system level and progresses through
analysis, design, coding, testing, and maintenance.
All projects follow a lifecycle model (SDLC). The most widely used SDLC
model in Online Banking Transaction Application.
Requireme
nt
Desig
Coding
Integration
&
Maintena8n
Fig.1 Incremental Model
➢ Design
Software design is actually a multi-step process that focuses on four distinct
attributes of a program: data structure, software architecture, interfaces
representation and procedural detail. The design process translates requirements
into a representation of the software that can be accessed for quality before
coding begins.
➢ Code generation
Code-generation phase translates the design into a machine-readable form.
➢ Testing
Once code has been generated, program testing begins. The testing process
focuses on the logical internals of the software, ensuring that all statements have
been tested, and on the functional externals; that is, conducting tests to uncover
errors and ensure that defined input will produce actual results that agree with
required results.
➢ Maintenance
Software maintenance applies to following phases in the existing
program
➢ Change in software due to errors.
➢ Change in software because the software must be adapted to accommodate
changes in its external environment.
➢ Change in software when the customer requires functional or performance
enhancements.
Here's a sample risk list to get you started (Try to be realistic; "The world might
end tomorrow" is a little off target for this particular exercise):
➢ This project could distract key resources within the company, causing the
rest of the business to suffer.
➢ We will be placed on the same level as our major competitor, a company
that already does most of its business online. (Yes, this is a risk as well as a
benefit!)
➢ Our customers may not want to change the way they do business with us,
so the cost of an e-commerce project may not generate profits. Increasing the
number of products we offer by using a Web site will create warehousing and
distribution issues.
➢ Effectiveness:
The analysis and design phase are quite effective. The user can run any function
at any time without any failure. We have used the latest technology and more
reliable technological framework so called .NET framework 3.5
➢ Efficiency :
The Efficiency of the proposed application is quite reliable. User can perform
any type of query related for searching the various facilities in web inventory
management system. User will find the application very user-friendly and self-
guided.
➢ Confidentiality:
The login name & password are quite secure and much confidential.
➢ Integrity:
The user input process and the output process are quite perfect i.e. the user gets
what he queries. The application is quite secure from hacking and prevents
itself from poor authority granting procedure.
➢ Reliability:
We ensure that each and every information is quite perfect and reliable. So user
can trust on them.
2.3 Estimation
Effort estimation consists in predict how many hours of work and how many
workers are needed to develop a project. The effort invested in a software project
is probably one of the most important and most analyzed variables in recent years
in the process of project management. The determination of the value of this
variable when initiating software projects allows us to plan adequately any
forthcoming activities. As far as estimation and prediction is concerned there is
still a number of unsolved problems and errors. To obtain good results it is
essential to take into consideration any previous projects. Estimating the effort
with a high grade of reliability is a problem which has not yet been solved.
Several methods have been used to analyze data, but the reference technique has
always been the classic regression method. Therefore, it becomes necessary to
use some other techniques that search in the space of non linear relationship.
Some works in the field have built up models (through equations) according to
the size, which is the factor that affects the cost (effort) of the project, the most.
The equation that relates size and effort can be adjusted due to different
environmental factors such as productivity, tools, complexity of the product and
other ones. The equations are usually adjusted by the analyst to fit the real data.
There are basically two types of users who will use the system as per the
requirement. The Users are as follows:
Admin :
Admin has all final authority they maintain shop’s items list ,user
list,member list, all
System Requirements:-
➢ Operating System: - Windows Vista, Windows XP, etc...
➢ Processor: - 400 MHz Processor
➢ RAM: - 1 GB (Minimum);
➢ Hard Disk: - Up to 500 MB of available space required
➢ Display: - 800 x 600, 256 colors (Minimum); 1024 x 768 high color, 32-bit
➢ Platform: - .Net framework 4.0
➢ Front End: - Microsoft Visual Studio 2010
➢ Back Hand: - SQL Server 2008(Management Studio).
➢ Development Tools used (documentation):- Microsoft Excel, PDF-Adobe
Reader
➢ The time which has been spent by the customer in manual shopping can
save
➢ The time which has been spent by the customer in manual shopping can
equates to multiple number of shopping. As customer can sit at home and
browse in a fraction of seconds.
➢ Thus we need to change to a system like “Online Shopping “.
➢ The current business methods can very well be incorporated into the proposed
system. The proposed system has more chance of being accepted by the
intended users.
➢ The system will work when it is developed and installed and there are no
major barriers to its implementation within the organization. This accounts
for the operational feasibility of the proposed system.
4.5 Requirement Validation:
➢ Username and Password validation that is compulsory to enter within
system (Not for visitor).
➢ Phone No must be Numeric and length is of maximum 12 ( Cell no, or lane
line) Digit.
➢ Name must be character not in digit.
➢ Pin code No. is of at least 6 digits.
➢ The field denoted by (*) is compulsory.
➢ Most of the data are enter from the master table so it also reduces the
chances of mismatch data, so no multiple entries.
➢ The time should be entered in the valid format. (MM-DD-YYYY)
CHAPTER 5:SYSTEM DESIGN
1. Use-Case Diagram
2. Sequence Diagram
3. Activity Diagram
4. State Diagram
6. Class Diagram
Conformation order
Report
Activity diagram :
• Data flow
• Process
• Source or Destination
• Data Store
A data flow diagram may be used to represent a system or software at any level
of abstraction. In fact, DFDs may be partitioned into levels that represent
increasing information flow and functional detail. Therefore, the DFD provides
a mechanism for functional modeling as well as information flow modeling. A
level 0 DFD, also called a fundamental system model or a context model,
represents the entire software element as a single bubble with input and output
data indicated by incoming and outgoing arrows, respectively.
A level 1 DFD might contain five to six bubbles with interconnecting arrows.
Each of the processes represented at level 1 is a subfunction of the overall system
depicted in the context model.
Payment Conformation
Validation Cust Info
Bank Courier
2 Customer info
Customer log in info Cust_trans
Log in
Admin log in info
module
Authentication
Authentication
Order info 3
Order info Admin
Order Cust_info
Order info
Order_trans Processing
Cust_trans
Payment
Payment Detail Payment Detail Cust_trans
Bank module
Order_info
Courier
Item_master
6
Update
Update
Updates
Update
Stock_trans
Customer info 7
Cust_trans
Report Reports
Item info
Item_master Generating
Module
Request for report
Order info
Order_trans
Admin
8
discount detail Updates
Store discount info Of Discount detail
Discount
Fig.15 Reg.page
Fig.16.Verification code
6.5 verification code Receive
Fig.19.Product details
6.8 My cart
Fig.20 My cart
6.9 Shipping address
Table testing
7.2 Testing Phase:
➢ Functionality Testing: The application must be tested to ensure that it meets all the
functional requirements specified in the SRS document.
➢ Performance Testing: The application must be tested to ensure that it performs well
under normal and peak load conditions.
➢ User Acceptance Testing: The application must be tested by the end-users to ensure
that it meets their expectations and requirements.
➢ Regression Testing: The application must be tested after every change or update to
ensure that it still works correctly and does not introduce any new defects.
➢ Error Handling Testing: The application must be tested to ensure that it handles
errors and exceptions gracefully and provides clear error messages to users.
➢ Accessibility Testing: The application must be tested to ensure that it meets the
accessibility requirements and can be used by users with disabilities.
➢ Test Scope: Define the scope of testing, including what parts of the application will
be tested and what will not be tested.
➢ Test Objectives: Define the objectives of testing, including what you are trying to
achieve and what problems you are trying to identify.
➢ Test Strategy: Define the overall testing strategy, including what testing
methodologies will be used, what types of testing will be performed, and what testing
tools and resources will be required.
➢ Test Environment: Define the test environment, including the hardware, software,
and network configurations required for testing.
➢ Test Schedule: Define the testing schedule, including when testing will start and
end, and how long each testing phase will last.
➢ Test Deliverables: Define the test deliverables, including what documents and
reports will be produced as part of the testing process.
➢ Test Cases: Develop test cases that cover all the functional requirements of your
application. Each test case should include a description of the test scenario, input
data, expected output, and the actual result.
➢ Test Execution: Execute the test cases and record the results. If there are any defects
found during testing, they should be reported and tracked until they are resolved.
➢ Test Reporting: Generate test reports that summarize the testing activities and
provide insights into the application's quality and performance.
Unit testing:
➢ Testing if user is not able to place an order with invalid or incomplete information.
➢ Testing if user is not able to submit a review with invalid or incomplete information.
➢ Testing if seller is not able to add a product with invalid or incomplete information.
Integration Testing:
➢ Testing if the user login module is properly integrated with the order module.
➢ Testing if the user registration module is properly integrated with the add to cart
module.
➢ Testing if the payment module is properly integrated with the order module.
➢ Testing if the product search module is properly integrated with the add to cart
module.
➢ Testing if the review module is properly integrated with the product search module.
➢ Testing if the banner image module is properly integrated with the home page
module.
➢ Testing if the seller module is properly integrated with the product search module.
➢ Testing if the seller module is properly integrated with the payment module.
➢ Testing if the seller module is properly integrated with the order module.
➢ Testing if the seller module is properly integrated with the banner image module.
➢ Testing if the search by location module is properly integrated with the product
search module.
System Testing:
➢ Testing if the application is able to handle a large number of products and users.
➢ Testing if the application is able to handle various types of products such as physical
goods, digital goods, and services.
➢ Testing if the application is able to handle various types of orders such as bulk orders,
customized orders, and urgent orders.
➢ Testing if the application is able to handle various types of users such as registered
users, guest users, and sellers.
➢ Testing if the application is able to handle different types of devices such as mobile
devices, tablets, and desktops.
CHAPTER 8: CONCLUSION AND FUTURE WORK
➢ At the end of analysis, we concluded that our project contains actors like admin,
customer their roles are managing data of each customer order, complaints, plans
details , report generate.
➢ Our developed system is also not an exception in this case, having mentioned the
limitation. At one time only one page can be accessed.More load on the system
sometimes affects the performance of the system.
FUTURE ENHANCEMENT
• Chatting functionality
➢ BOOKS
➢ WEBSITES
➢ Payment Gateway:
➢ A payment gateway is a service that facilitates the transfer of funds between a
customer and a seller in an online transaction. Payment gateways securely process
credit card or other electronic payments.
➢ Shopping Cart:
➢ A virtual cart or basket that stores the items a customer has selected to purchase on
an ecommerce website or app.
Company Address :
SERVICE OFFERINGS:
➢ Application Development & maintenance.
➢ Web Development
➢ Migration and Re-Engineering.
➢ Software as a Service(SaaS)
➢ Enterprise Solution.
➢ Product Development and Support.
➢ Multimedia Services.
➢ Search Engine Optimization
ABOUT COLLEGE
The College is spread over 25 acres of land and is a part of Ganpat Vidyanagar
Campus. It has six ultra-modern buildings of architectural splendor, class rooms,
tutorial rooms, seminar halls, offices, drawing hall, workshop, library, well
equipped departmental laboratories and several computer laboratories with internet
connectivity through 1 Gbps Fiber link, satellite link education center with two-way
audio and one-way video link. The superior infrastructure of the Institute is
conducive for learning, research, and training.