software testing verification validation topic website selling pet accessories

 Nguyen Nhu Ngoc  Huynh Nguyen Bao Han  Le Van Anh Duy  Nguyen Huu Linh  Do Duc Binh  Phan Tuan Phong

CONTENTS

II High Level Requirement 4

III Security Requirement 5

IV Use Case Specification 5

4.10 View Order Detail 8

4.11 Generate purchase invoice 9

5.7 Software Quality Attributes 10

VI Web Integration Overview 11

6.1 Web Integration Benefits 12

a Lower cost 12

b Non-intrusive 12

c Faster development 12

d Faster overall integrations 12

e Lower skill requirements 13

f Potentially lower risk 13

I Introduction

1.1 Purpose

 Learn the theory of system analysis and design using UML  Apply knowledge of system analysis and design in practice  Build real projects

 The management interface is friendly, simple and easy to use.

1.2 Scope

From the urgent needs of customers and the current situation of pet accessories business websites on the Internet, the topic "Building a pet accessories business website" vs.

- Website displays beautiful products, attracting users

-Build a website with content including text, images, links, etc to provide necessary needs for users

- Support customers in the fastest way when receiving contact requests - Manage product items, website configuration

- Manage sales statistics, product orders, number of products sold - Application of MVC model to building websites

- Application of Laravel Framework to build websites

1.3 Glossary

API - Application Programming Interface HTML - Hypertext Markup Language LDAP - Lightweight Directory Access Protocol

1.4 Overview

The remaining section of this document provide a general description including characteristic of the users of this product, the product’s hardware, and functional and non-functional requirements of the product.

II High Level Requirement - Easy login:

o Target users: System users

o This use case allows users to log into the system and perform the functions available in the system.

o Money Status: User is not logged in.

o Background condition: User is redirected to the homepage o Steps to do:

1 User accesses login page 2 User enters username, password 3 Click the login button

4 Information check system

5.Cem valid information, go back to home page, then you will be redirected to login page again

Using the purchase case: + Target users: Customers.

This use case allows customers to search for items to purchase + Steps:

1 Sign in 2 Search 3 Select product 4 Order and pay Using the command to manage records:

+ User object: administrator

+ This use case allows admin members to view, edit and change the order status that the customer has selected.

+ Steps: 1 Sign in

2 Click Admin Page

3 View, edit, delete, update order status III Security Requirement

The system is implemented after through checking is done and if

The implementation process begins with preparing a plan for the implementation of the system According to this plan, the activities are to be carried

out, discussions made regarding the equipment, recourses and the additional

equipment that has to be acquired to implement the new system The most important thing in the implementation stage is, gaining the users confidence that

the system will work effectively The system can be implemented only after the

testing is done This method also offers the greatest security since the existing

system can take over if the errors are found or inability to handle

deleted without proper authorization There are two dimensions for the protection of data in the data base The logged user can only perform the operations.

This ensures that the confidentiality of the data is maintained, second, the data

must be protected from accidental or intentional corruption or destruction The

security features are considered while developing the system, so as to avoid the

errors and omissions that may lead to serious problems The system may have

to face the unwanted events called threats A threat to a computer system is

any events that adversely affect the one or more assets or resources, which make

up the system An event can be any of the following:

 There are many methods for handling a threat  Avoid it by altering the design.

 Department of Computer Science 8

 Christ College(Autonomous) Petz-Online Pet Shop  Threat retention.

 Threat reduction that is the frequency of occurrence of a threat is reduced.

The security measures of a computer system should be specified at an early

stage in the design of the system During the system operation each user should

understand the procedures required to keep the system secure There are many possible threats to the security and integrity of

In this project the data security, data validation checking methods are applied using a password authentication All the data, which is entered by the administrator, will be validated.

IV Use Case Specification

4.1 Registration

Use Case Registration

Description The use case begins when the actor indicates the intent to register to the system It ends when the actor is a register or cancels registration.

Pre-Condition The login exists

Post-Condition The actor register successfully

system It ends when the actor is log in or cancels login Pre-Condition The login exists

Post-Condition The actor logs in successfully

4.3 Administration/User Logout

Use Case Login

Actor Administrator/User

Description The use case begins when the actor indicates the intent to logout to the system It ends when the actor is log in or cancels login Pre-Condition The logout exists

Post-Condition The actor logout successfully

4.4 Manage cart

Use Case Manage cart

Description The use case begins when the actor indicates the intent to add items into the cart It ends when the actor enters the next Pre-Condition 1-The Category record exists for editing/view.

2-The actor is logged in.

Post-Condition The Cart record is added or updated.

4.5 View Products

Use Case View Products

Description The use case begins when the actor indicates to view the products It ends when the actor is close to the application Pre-Condition The login exists

Post-Condition The actor view product successfully

4.6 Place Order

Use Case Place Order

Description The use case begins when the actor indicates the intent to confirm the purchase of his selected items

Pre-Condition 1-The product record exists for editing/view 2-The actor is logged in.

Post-Condition The Cart record is added or updated.

4.7 Manage Categories

Use Case Manage Categories Actor Administrator

Description The use case begins when the actor indicates the intent to view, update, add or delete Categories record It ends when the actor closes the Category form.

Pre-Condition 1-The Categories record exists for editing/view 2-The actor is logged in

Post-Condition The Categories record is added, deleted or updated.

4.8 Manage Customer

Use Case Manage Customer Actor Administrator

Description The use case begins when the actor indicates the intent to view, update add or delete Customer’s record It ends when the actor closes the Customer form…

Pre-Condition 1-The Customer’s record exists for editing/delete 2-The actor is logged in

Post-Condition The Customer’s record is added or updated.

4.9 Manage Product

Use Case Manage Product Actor Administrator

Description The use case begins when the actor indicates the intent to add, update, delete or view item is a record Categories can be searched.

It ends when the actor closes the form Pre-Condition 1-The Item’s record exists for editing/view.

2-The actor is logged in.

Post-Condition The item’s record is added or updated.

4.10 View Order Detail

Use Case View Order Detail

Description The use case begins when the actor indicates the intent to view orders detail of customers.

Pre-Condition 1-The order record exists for editing/view 2-The actor is logged in.

Post-Condition The actor dispatch or cancel the customer record.

4.11 Generate purchase invoice

Use Case View Order Detail

Description System receives payment confirmation from user

System sends credit card information and amount to be charged to the Payment module

Payment module sends purchase confirmation to the system System creates an invoice for the user consisting to the ProducItems,

total cost, date of purchase ,and shipping address details Pre-Condition 1-The order record exists for editing/view.

2-The actor is logged in.

Post-Condition The item’s record is added or updated.

V Other Requirements

5.1 Functional Requirements

 Users should be able to create ad hoc chat groups comprising sets of users and send private messages to other users.

 Users should be able to have text chats that they can break into threads  Chats should be able to be archived indefinitely so users can reference past

 Users should be able to upload files to chats for reference  External Interface Requirements

5.2 User Interfaces

 Front-end software: React Native  Back-end software: NET Core  Database software: MySQL

 LDAP connection: Authentication in an enterprise environment

 The application should load and be usable within 3 seconds.

 The application should update the interface on interaction within 2 seconds  The database should be normalized to prevent redundant data and improve

 The database should be distributed to prevent outages.

5.5 Safety Requirements

 Databases should use sharding to be redundant to prevent loss of data  Backups of the databases should be done hourly and be kept for one week.

5.6 Security Requirements

 Any keys used for the REST API should be stored securely  Only the REST API should be able to connect to the databases  Databases should be behind a firewall.

5.7 Software Quality Attributes

 Availability: Because this application is critical to business communication, we will have a goal of four nines(99.99%) availability.

 Correctness: The application should never allow anyone to read messages or discussions not intended for that person.

 Maintainability: The application should use continuous integration so that features and bug fixes can be deployed quickly without downtime.

 Usability: The interface should be easy to learn without a tutorial and allow users to accomplish their goals without errors.

VI Integration

6.1 Web Integration Overview

Web Integration is a unique and innovative approach to the challenges of integrating and service- enabling existing browser-accessible applications Web Integration can be done quickly, iteratively, at low cost and with relatively modest skill requirements In addition, because it uses the presentation layer as its API, it is by nature non-intrusive.

The key factor with Web Integration is that most production applications already have an HTML- based interface that provides access to both functionality and data Most newly developed web applications even expose logic that has been written into the presentation layer itself.

Although this web interface was intended for end users, Web Integration can turn the browser into a well-defined programmatic interface that exposes the full functionality and data of the application.

As the figure above shows, a Web Integration Server accesses the presentation layer of an application through the browser interface This server can then make one or more of the following access points available: a web service, a modified browser interface, or an API into the application’s logic and data.

Using Web Integration, other applications would have the capability to access the full functionality and data of the application, as if the application had been developed to provide an open interface By accessing the application through the user interface, the power and functionality of these applications can be re-utilized in sophisticated integration solutions, such as:

 Enterprise Portals - content and functionality of existing web-enabled

applications can be used in an enterprise portal.

 Composite Applications - functionality from any existing application

can be combined to create a new application that automates business processes

 Web Services - any web-enabled application can be turned into a web service

 Data Collection - data available via any web-enabled application can

be aggregated and moved to a new system, such as a content management system.

 Market Intelligence - information from competitors, media

providers, government databases, etc., can be collected on a regular, scheduled basis for market intelligence purposes.

 Automation - in general, Web Integration is exceptional for

programmatically automating normal operator tasks requiring the flow of information between web-enabled applications.

6.2 Web Integration Benefits

Web Integration has a number of important benefits compared to the other more traditional integration approaches:

a. Lower cost

Using Web Integration, the effort required becomes much less expensive compared to traditional integration There are numerous reasons, including lower skills for developers, no change to existing applications, and no infrastructure changes to network.

b. Non-intrusive

Web Integration is done non-intrusively, thereby lowering the risk and impact of the entire integration project Because there are no architectural changes required, it is often easier to justify cross-enterprise projects This benefit extends even further to those external applications where the user interface is the only available option for integration.

c. Faster development

Since the browser interface is well understood by both the end user and the programmer, application design becomes much easier and less prone to error.

d. Faster overall integrations

Even complex Web Integration projects can be completed in weeks rather than months Companies can gain competitive advantages by leveraging their existing enterprise applications more quickly than their competitors.

e. Lower skill requirements

A traditional integration project requires highly skilled development staff In depth knowledge of the applications and application integration techniques is required With Web Integration technologies, development personnel with basic programming experience and web application knowledge can do a superior job The need for high-skilled, expensive programmers can be obviated.

f. Potentially lower risk

Web Integration allows for shorter and more cost-effective implementation cycles The initial integration can often be up and running quickly and further integration can be accomplished once results from the initial integrations have been proven This allows companies to try out new business opportunities at lower risk than using traditional methods.