Quality Assurance and Quality Analysis of Boutique Management
Software Quality Assurance
Group No. SQA_7
Asad Mehmood B-18854
M. Junaid Khan B-19224
Ammar Ayub B-19226
Rimsha Saleem B-18827
Prof. Masroor Hussain
Table of Contents
1 Table of Contents. 2
1. Introduction to Topic. 3
2. Introduction to
Organization or concept: 3
2.1. Features of the project 3
3. Previous and Current
3.1. Previous Issue. 4
3.2. Current Issue. 4
3.3. Security Issue. 5
3.4. Graphical user interphase issues. 5
4. How and Why related to
the topic to organization: 6
4.1. How to do: 6
5. What is relevance / role
of SQA in solution problem.. 7
6. How Problem Solved. 8
6.1. Security Issue. 8
6.2. Graphical user
7.1. Conclusions. 9
7.2. Recommendations. 9
1. Introduction to Topic.
This is basically
the “Boutique Management system”, this project is made on Asp.net (MVC). This
is Portal type application and its data is saved on SQL database server. Basically
we analyze its quality and assurance whether it is secure or not and it has been
made according to any standard or not.
2. Introduction to Organization
has been developed on asp.net MVC and my sql.
This is basically web base portal, this application is made for designer
and boutique owner who want to publish their design. The boutique owner make
their profiles as single web page they upload their design on their profile
pages and also they give phone, location and contact info. Customers come to
see their design when they like any design they contact with boutique they give
order and give their measurements. The online boutique system also helps our
customers to find out their stitched clothes and how much time is required for
stitching. When the clothes are stitched the boutique owner notify the customer
through phone or e-mail, customer collect the dress after notification. The
application also helps the boutique owner to watch which clothes are stitched
and how much are pending that tailor is stitching which clothes if some clothes
are stitched and delivered the system have also recorded them and its payment.
The main objective for developing this project is to manage all orders and
track the record of the measurements and further boutique details.
2.1. Features of the project
the searching facilities based on various factors. Such as Boutique, Customer,
Boutique Management also manage the Orders details online for Designs details,
Products details, Boutique.
tracks all the information of Designer, Orders, and Designs.
the information of Designer
the information and description of the Boutique, Customer
increase efficiency of managing the Boutique, Designer
deals with monitoring the information and transactions of Designs.
the information of Boutique
adding and updating of Records is improved which results in proper resource
management of Boutique data.
the information of Designs
of all records of Products.
Previous and Current Issue
3.1. Previous Issue
The old manual system
was suffering from a series of drawbacks. Since whole of the system was to be
maintained with hands the process of keeping, maintaining and retrieving the
information was very tedious and lengthy. The records were never used to be in
a systematic order. There used to be lots of difficulties in associating any
particular transaction with a particular context. If any information was to be
found it was required to go through the different registers, documents there
would never exist anything like report generation. There would always be
unnecessary consumption of time while entering records and retrieving records.
One more problem was that it was very difficult to find errors while entering
the records. Once the records were entered t was very difficult to update these
behind it is that there is lot of information to be maintained and have to be
kept in mind while running the business .For this reason we have provided
features Present system is partially automated (computerized), actually
existing system is quite Laborious as one has to enter same information at
three different places
In the existing
system the exams are done only manually but in proposed system we have to
computerize the exams using this application.
of security of data.
large volume of work.
direct role for the higher officials
the fields take invalid values.
form for Boutique, Designer, Orders accept blank value fields
is no validations and check for avoiding errors in data
of all the reproduced error
3.3. Security Issue
To develop applications without any
thought of security until the application is fully developed. This is the
typical “let’s throw it over the wall to the IT security team” scenario.
The problem with this scenario is that any security problems identified just
before deployment will cause either the development team or the IT security
team big headaches. Either the product is going to be deployed with security
holes or the application is going to be delayed, because it needs more cycles
through the SDLC to remediate the security risk.
No security as data can be misplaced or damaged; lastly,
it was not offers a user friendly work environment.
A mistake in
software that can be directly used by a hacker to gain access to a system or
owner’s data is not secured because there is no security barriers in the
Flaws, faults, bugs,
and other errors in software implementation, code, design, or architecture that
if left unaddressed could result in systems and networks being to attack.
user interphase issues
User Interface Design is concerned
with the dialogue between a user and the computer. It is concerned with
everything from starting the system or logging into the system to the
eventually presentation of desired inputs and outputs. The overall flow of
screens and messages is called a dialogue.
following steps are various guidelines for User Interface Design:
system user should always be aware of what to do next.
screen should be formatted so that various types of information,
instructions and messages always appear in the same general display
instructions or information should be displayed long enough to allow the
system user to read them.
display attributes sparingly.
values for fields and answers to be entered by the user should be
should not be allowed to proceed without correcting an error.
system user should never get an operating system message or fatal error.
4. How and Why related to the topic to organization:
The aim of
proposed system is to develop a system of improved facilities. The proposed
system can overcome all the limitations of the existing system. The system
provides proper security and reduces the manual work.
control of the higher officials.
manual data entry.
time needed for the various processing.
friendliness and interactive.
· Minimum time required.
4.1. How to do:
the first step, we will select the test factors and rank them. The selected
test factors such as reliability, maintainability, portability, will be placed
in the matrix according to their ranks.
step is for identifying the phases of the development process. The phase should
be recorded in the matrix.
third step is that identifying the business risks of the software deliverables.
The risks will be ranked into three ranks such as high, medium and low.
5. What is relevance / role of SQA in solution problem
assurance (SQA) is a critical part of software development it includes software
testing and it is a team consists on software testers and SQA engineers.
5.2. SQA help us to
find solution and solve problems which are occurred in organizations or in the
fields such as Boutique, Customer, Products are validated and does not
take invalid values
for Boutique, Designer, Orders cannot accept blank value fields
errors in data
amount of input
of all the modules/forms in the system.
of the test cases.
of the possible test data with all the validation checks.
testing done manually.
of all the reproduced errors.
done for the errors found during testing.
the test result scripts after rectification of the errors.
of the entire module/forms.
for user input.
of the Coding standards to be maintained during coding.
the module with all the possible test data.
the functionality involving all type of calculations.
standard in the source files.
The system user should always be aware of
what to do next.
The screen should be formatted so that
various types of information, instructions and messages always appear in
the same general display area.
Message, instructions or information
should be displayed long enough to allow the system user to read them.
Use display attributes sparingly.
Default values for fields and answers to
be entered by the user should be specified.
A user should not be allowed to proceed
without correcting an error.
The system user should never get an
operating system message or fatal error.
How Problem Solved
6.1. Security Issue
We are using the International Software Testing Standard ISO/IEC/IEEE 29119-2 for security issue.
aim of ISO/IEC/IEEE 29119-2 is to define a generic process model for software
testing that can be used within any software development life cycle testing.
The model specifies test processes that can be used to, manage and implement
software testing in any organization, project or testing activity.
We are using
the Test Planning process.
First of all we
are understanding the context we which implemented, In the project we check the
black whole and loop.
Graphical user Interface
should be very simple in the form of icons or buttons through them the user can
easily understand that his desired task or action can be done by these icons
and buttons. There should be a sequence of actions in the form of menu where
all the desired action of the user can be easily done. The fonts and buttons used will be intended to be very fast and easy
to load on web pages. The pages will be kept light in space so that it won’t take
a long time for the page.
A description of the background and context of the project and its
relation to work already done in the area. We define the problem on which we
are working in the project. We included features and operations in detail,
including screen layouts. We designed user interface and security issues
related to system. Finally the system is implemented and tested according to
test cases. We understand the problem domain and produce a model of the system,
which describes operations that can be performed on the system.
We recommend that if Boutique Management System does more work for
its Features and accessibilities
it can competitively beat Other Boutique Management system. Organization any
kind now a days just see how their product is more efficient and user Friendly
and user also see that which product either it was software base or not is user
friend and efficient for him.
So providing best features
and use friendly term can give an opportunity to grow up his customers and make
a name in software industry.
You—————– : )