buy & sell 3.docx
TRANSCRIPT
-
7/30/2019 Buy & Sell 3.Docx
1/29
11
Model Used:
Iterative Model
An iterative lifecycle model does not attempt to start with a full specification of
requirements. Instead, development begins by specifying and implementing just part of the
software, which can then be reviewed in order to identify further requirements. This process
is then repeated, producing a new version of the software for each cycle of the model.
Consider an iterative lifecycle model which consists of repeating the following four phases
in sequence:
ARequirements phase, in which the requirements for the software are gathered and
analyzed. Iteration should eventually result in a requirements phase that produces a
complete and final specification of requirements. - ADesign phase, in which a
software solution to meet the requirements is designed. This may be a new design, or an
extension of an earlier design.
- AnImplementation and Testphase, when the software is coded, integrated and tested.- AReview phase, in which the software is evaluated, the current requirements are
reviewed, and changes and additions to requirements proposed. For each cycle of the
model, a decision has to be made as to whether the softwareproduced by the cycle will be
discarded, or kept as a starting point for the next cycle (sometimes referred to as
incremental prototyping). Eventually a point will be reached where the requirements are
complete and the software can be delivered, or it becomes impossible to enhance the
software as required, and a fresh start has to be made.
The iterative lifecycle model can be likened to producing software by successive
-
7/30/2019 Buy & Sell 3.Docx
2/29
15
The Java Platform consists of several programs, each of which provides a distinct portion
of its overall capabilities. For example, the Java compiler, which converts Java source code
into Java bytecode (an intermediate language for the Java Virtual Machine (JVM)), is
provided as part of the Java Development Kit (JDK). The sophisticated Java Runtime
Environment (JRE), complementing the JVM with a just-in-time (JIT) compiler, converts
intermediate bytecode into native machine code on the fly. Also supplied are extensive
libraries (pre-compiled into Java bytecode) containing reusable code, as well as numerous
ways for Java applications to be deployed, including being embedded in a web page as an
applet. There are several other components, some available only in certain editions.
The essential components in the platform are the Java language compiler, the libraries, and
the runtime environment in which Java intermediate bytecode "executes" according to the
rules laid out in the virtual machine specification.
-
7/30/2019 Buy & Sell 3.Docx
3/29
52
Screen Shots:-
Admin Login:-
Admin Home:-
-
7/30/2019 Buy & Sell 3.Docx
4/29
53
Admin View Items:-
Admin View Items:-
-
7/30/2019 Buy & Sell 3.Docx
5/29
54
Admin Book Display:-
More Info:-
-
7/30/2019 Buy & Sell 3.Docx
6/29
55
Manage Users:-
View Orders:-
-
7/30/2019 Buy & Sell 3.Docx
7/29
56
View Feedback:-
Home Page:-
-
7/30/2019 Buy & Sell 3.Docx
8/29
57
Home Page After Login:-
Register Page:-
-
7/30/2019 Buy & Sell 3.Docx
9/29
58
View Desktops :-
-
7/30/2019 Buy & Sell 3.Docx
10/29
59
Information Page:-
Cart:-
-
7/30/2019 Buy & Sell 3.Docx
11/29
60
Cart2:-
Check Out:-
-
7/30/2019 Buy & Sell 3.Docx
12/29
61
Card Details:-
Pay Confirmation:-
-
7/30/2019 Buy & Sell 3.Docx
13/29
140
Screen Shots:-Admin Login:-
Admin Home:-
-
7/30/2019 Buy & Sell 3.Docx
14/29
141
Admin View Items:-
Admin View Items:-
-
7/30/2019 Buy & Sell 3.Docx
15/29
142
Admin Book Display:-
More Info:-
-
7/30/2019 Buy & Sell 3.Docx
16/29
143
Manage Users:-
View Orders:-
-
7/30/2019 Buy & Sell 3.Docx
17/29
144
View Feedback:-
-
7/30/2019 Buy & Sell 3.Docx
18/29
145
Home Page:-
-
7/30/2019 Buy & Sell 3.Docx
19/29
146
Home Page After Login:-
-
7/30/2019 Buy & Sell 3.Docx
20/29
147
Register Page:-
-
7/30/2019 Buy & Sell 3.Docx
21/29
148
View Desktops :-
-
7/30/2019 Buy & Sell 3.Docx
22/29
149
Information Page:-
-
7/30/2019 Buy & Sell 3.Docx
23/29
150
Cart:-
-
7/30/2019 Buy & Sell 3.Docx
24/29
151
Cart2:-
-
7/30/2019 Buy & Sell 3.Docx
25/29
152
Check Out:-
-
7/30/2019 Buy & Sell 3.Docx
26/29
153
Card Details:-
Pay Confirmation:-
-
7/30/2019 Buy & Sell 3.Docx
27/29
154
Chapter 4
TESTING & MAINTENANCE
4.1 INTRODUCTION
The Process of analyzing a s/w item to detect the differences between existing and required
conditions (i.e. Bugs) and to evaluate the features of the s/w items is called the Testing. The
process of analyzing a program with the intent of finding errors is called the testing.
During testing, the program to be tested is executed with a set of test cases, and the output of
the program for the test cases is evaluated to determine if the program is performing as
expected. From this it is clear that testing is used to find out errors rather than to tell the
exact nature of error. Also, the success of the testing process clearly depends upon the testcases used.
Testing is a complex process. In order to make the process simpler, the testing activities are
broken into smaller activities. Due to this, for a project, incremental testing is generally
performed. In incremental testing process, the system is broken into set of subsystems and
these subsystems are tested separately before integrating them to form the system for system
testing.
4.2 TESTING THE SYSTEM
The quality of a product or item can be achieved by ensuring that the product meets the
requirements by planning and conducting the following tests at various stages.
Unit Tests at unit level, conducted by development team, to verify individual standalone
units.
Integration Tests after two or more product units are integrated conducted by development
team to test the interface between the integrated units.
Functional Test prior to the release to validation manager, designed and conducted by the
team independent of designers and coders, to ensure the functionality provided against the
customer requirement specifications.
Acceptance Tests prior to the release to validation manger, conducted by the development
team, if any supplied by the customer.
Validation Tests prior to customer, conducted by the validation team to validate the productagainst the customer requirement specifications and the user documentation.
-
7/30/2019 Buy & Sell 3.Docx
28/29
155
4.3 TEST CASES
Case 1) The first test case was performed by Mr. Amit Gupta. He performed testing on the
form of Nibiru Solution Buy & Sell online login page. He checked that if the project is able
to login by the admin and also check the validation who was performed by Amit Gupta to
validate the user and their password. Following is the test he performed:-
Before validation login test case
After validation login test case
-
7/30/2019 Buy & Sell 3.Docx
29/29
Case 2) The second test case was performed by Mr. Nishant Gupta. He wants to test that
whether the check-in or check-out which was issued for the product by the company, is
saved or not in the database. Also perform the configuration the structs. Following test he
performed:-
Check in & Check out
Payment details
Case 3) The third case was performed by Mr Piyush Arora. He wanted to test that if the
project can show the summary of pay from a particular date till the current date. He
performed the following test:-