






















Study with the several resources on Docsity
Earn points by helping other students or get them with a premium plan
Prepare for your exams
Study with the several resources on Docsity
Earn points to download
Earn points by helping other students or get them with a premium plan
The software requirements specification for pos_connect provides technical details on the performance, specifications, and functional requirements of the pos_connect system. It outlines the user interfaces, including the web ui and local ui, as well as the hardware, software, and communications interfaces. The product functions, user classes and characteristics, design and implementation constraints, and various functional requirements related to inventory management, web store creation and editing, transaction processing, and syncing between the local pos and the online system. It also includes information on the reporting and gui requirements, as well as the interactions between the web ui and the users. The document serves as a comprehensive guide for the development and implementation of the pos_connect system.
Typology: Exams
1 / 30
This page cannot be seen from the preview
Don't miss anything!























Page 1
Page 2
Table of Contents
1.1 Purpose 1.2 Document Conventions 1.3 Intended Audience and Reading Suggestions 1.4 Product Scope
2.1 Product Perspective 2.2 Product Functions 2.3 User Classes and Characteristics 2.4 Operating Environment 2.5 Design and Implementation Constraints 2.6 Assumptions and Dependencies
3.1 User Interfaces 3.1.1 Web UI 3.1.2 Local UI 3.2 Hardware Interfaces 3.3 Software Interfaces 3.4 Communications Interfaces
4.1 Client Account 4.2 Windows Service 4.3 Web Store 4.4 Online Inventory 4.5 Editable Product Information 4.6 Web Cart 4.7 Online Sales 4.8 Payment Processing 4.9 Shipping and Label Information 4.10Conflict Resolution 4.11Information Reporting 4.12Inventory Management 4.13Syncing 4.14POS Interaction 4.15 Web UI Requirements
5.1 Performance Requirements 5.2 Safety and Security Requirements 5.3 Software Quality Attributes 5.4 Business Rules
Page 4
a client’s existing Point of Sales (POS) system to create, update, and maintain an online store. POS_Connect establishes a connection between a local POS and a remote web service. The remote web service in turn establishes and hosts a web store for a given client. POS_Connect maintains and updates both local POS and online databases, while also facilitating online transactions for a given client.
All requirements in the document must have a priority level of 1, 2, or 3. Priority level 1 specifies that the requirement is essential. Priority level 2 specifies that the requirement may be included in the end but is not necessary to product functionality. Priority level 3 specifies extra features of the product that may be included after all level 1 and 2 requirements are adequately completed.
This document is intended for use by current and future development teams and outside project advisers and stakeholders who are associated with POS_Connect. This document contains technical information regarding the performance, specifications, and functional requirements (prioritized via the system outlined in Section 1.2) of POS_Connect. This Document also outlines the User Interfaces of POS_Connect.
POS_Connect is designed to run on a private web server utilizing Wordpress, Multisite, PHP, and existing databases, so as to host, maintain and secure individual client’s web stores and account information. POS_Connect also includes a Windows based client side service which automates interactions between the client’s local POS and the POS_Connect server.
POS_Connect is a self contained, standalone product. POS_Connect is mainly targeted toward small, pre established businesses, as the purpose is to integrate into and improve upon already existing local POS systems. It also creates a client editable web store focusing on a simple user interface with little to no required technical background.
Page 7
database.
Assumptions: ● Clients are expected to be store owners themselves. ● Clients are expected to already have Intuit POS set up.
Dependencies ● Wordpress and associated E Commerce and Multisite plug ins
3.1.1 Web UI As of version 1.0 all POS Connect online services, including the main page where account verification and client download take place and the web stores where clients can list products and customers can buy them are all Wordpress website pages. This section shows the user interface with the POS Connect system annotated with requirement numbers associated with particular UI components.
The POS Connect main page is shown below. The current page should be displayed on the navigation in a different color than the other links. When a user clicks on the “Home” link, they are taken to the home page. When the user clicks on the “Downloads” link, they should be taken to the downloads page. If a user wishes to search the POS Connect site, they can use the search boxes on the right side of the page to do so.
Page 8
Figure 1: POS Connect main page
The POS Connect download page is shown below. The navigation and search boxes follow the same specifications as outlined in the previous section. The page has a download link located directly below the title. Any additional information is below the download link. Clicking on the link initiates a download of the installer for the client.
Figure 2: POS Connect download page
Page 10
Figure 4: Products listing page
The next screenshot shows a product detail page. Navigation and other features on this page function the same was as outlined for an individual web store. A user can also add the item in question to their cart from this page by clicking the “Add To Cart” button.
Figure 5: Product detail page
Page 11
The following screenshot shows the login page for administration of an individual store. The username and password are to be entered into the appropriate boxes, then a user logs in by clicking on the “Log In” button.
Figure 6: Login page for administration of individual store
The following screenshot shows the WordPress dashboard for a particular store. The user can select a normal WordPress option if they wish, or the Products navigation item to list their products managed by POS Connect. Clicking on this link should take the user to the product administration page.
Figure 7: WordPress dashboard for a particular store, “products” link listed on dashboard
The following screenshot shows the product administration page. Clicking on a link at the top of the table sorts the table by that field. Clicking again sorts it descending. Clicking on a product title takes the user to the product edit page. Hovering over the title shows additional options to be
Page 13
The following screenshot also shows the product edit page. The price and sale price can be edited on the right side of the page, below the visible portion on the above screenshot.
Figure 10: Price edit page
The following screenshot shows a store’s checkout page. Cart items are listed here. Quantities of items can be edited from this page, and products can be removed altogether. To proceed to an available payment service, a user enters the required information in section 15. and clicks the “Next” button to be redirected to the proper payment authorization site.
Page 14
Figure 11: Checkout page
3.1.2 Local UI
The following screen shots are related to REQ 2.1, the Windows Service installer.
Double clicking on the POS_setup installer POS_Setup Setup wizard is prompted.
Figure 12: POS_setup Installer
Page 16
Figure 14:
The Next button displays a dialog box which asks for the users confirmation.
Figure 15:
Clicking on the Next button initiates the POS_setup installation.
Page 17
Figure 16: Once the installation is over the user is asked to click on the Close button to exit.
Figure 17:
Page 19
Figure 20:
Selecting the repair radio button and then clicking on Finish displays a dialog box stating that the service already exists.
Figure 21
Selecting the remove radio button and clicking on finish starts the uninstallation.
Page 20
Figure 22:
Once the service has been uninstalled a dialog box showing that the service has been successfully removed is shown. Clicking on Close exits the installer.
Figure 23: