Requirements

Published on May 2016 | Categories: Documents | Downloads: 27 | Comments: 0 | Views: 129
of 3
Download PDF   Embed   Report

Comments

Content

Dears, I have prepared the project's details.

System architecture:
The system is based on SOA and consists of four major components. ● Database (Data-tier). ● Web Service (Middle tier and business logic) that is connected to database ● Web front (for e-commerce and administration) that is connected to web-service. ● POS (for branches) that is connected to web service.

Roles:
All roles must be configurable and editable by super administrators. So, each user can be assigned to any role created by super admins for the authentication purpose. Examples of roles (customers, employees, vendors, etc). Also, a list of authorized system actions must be configurable to be assigned by super admins to roles. For example, employee can edit and add products while customers can only read products. Each action may map to a web page. (e.g. Add new product web page is considered as an action).

Non-functional requirements:
● ● ● ● ● ●

POS system have to be designed for touch screen. POS system have to be configurable for receipt printers. POS system have to be configurable for cash drawer. POS system have to be configurable for barcode reader.. POS system have to be fast in performance. All systems have to be available in multiple languages. (Using resource files resx).

Technical requirements:
● ● ● ● ● ● ● ● ● ●

Code must be written in C#. Web system should be written in ASP.NET. Security module should use membership technology. System must be designed in SOA technology (service oriented architecture). Use Master-Page when design web-pages. Use ASP.NET Themes. Business module can only and ONLY be accessed through web-service (asmx files) Data Module can only be accessed through LINQ-To-SQL. The system should be fully designed well (Layers, tiers, and modules). Each class and module should be documented very well in case another programmer may work on the source code in the future.

Functional requirements:
● ● ● ● ●

Super Admin can create, Delete, update, & read people. Super Admin user can create, Delete, update, & read people roles. Super Admin user can create, Delete, update, & read people role actions. Super Admin can read system errors. Authorized user can create, Delete, update, & read purchase orders.

● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ●

Authorized user can create, Delete, update, & read products. Authorized user can create, Delete, update, & read product variants. Authorized user can create, Delete, update, & read product categories. Authorized user can create, Delete, update, & read product specifications. Authorized user can create, Delete, update, & read products pictures. Authorized user can create, Delete, update, & read Locations (Branches, warehouses). Authorized user can create, Delete, update, & read Applications Settings. Authorized user can create, Delete, update, & read taxes. Read Logs. Authorized user can create, Delete, update, & read Orders. Authorized user can create, Delete, update, & read Order Lines. Authorized user can create, Delete, update, & read Order status. Authorized user can create, Delete, update, & read Payments. Authorized user can create, Delete, update, & read Payment Status. Authorized user can create, Delete, update, & read Payment types. Authorized user can create, Delete, update, & read Shipment Types (for ecommerce). Authorized user can create, Delete, update, & read Shipment Status (for ecommerce). Authorized user can create, Delete, update, & read Receipts. (When order is paid, receipt will be created). Authorized user can create, Delete, update, & read Closed Cash (For POS only). Authorized user can create, Delete, update, & read Product Movements between locations. Authorized user can create, Delete, update, & read customer rewards policy. Authorized user can view reports on inventory stock. Authorized user can view reports on sales trends. Authorized user can view reports on purchase orders. Authorized user can view reports on orders. POS cashier can access to customers information. POS cashier register sold products of anonymous customer. POS cashier register sold products of registered customer. POS cashier search for products within any branch. POS cashier register refunded products of anonymous customer. POS cashier register refunded products of registered customer. Customer can register herself in the system through e-Commerce channel. Customer can update her account in the system through e-commerce channel. Customer can view her orders in the system through e-commerce channel. Customer can order products through the e-commerce channel. Customer can view and search for products through the e-commerce channel. Each customer have reward point based on her payments.

Security requirements:
● ●

All roles must be configurable and editable by super administrators. Each user can be assigned to any role created by super admins for the authentication purpose.

● ● ● ● ● ●

Examples of roles (customers, employees, vendors, etc). A list of authorized system actions must be configurable Authorized system actions can be assigned to roles by super admins. Example of actions, employee can edit and add products while customers can only read products. Each action may map to a functional requirement (e.g. Add new product is considered as an action, while update product is considered as another action). All logins in e-commerce have to use CAPTCHA images.

Audits requirements:


All user actions must be saved in log database table.

Users:
● ● ● ● ●

Employees. Super admins. Customers. POS-Cashier. When you finished read this document, just type: “I READ IT” in your response bid.

Sponsor Documents

Or use your account on DocShare.tips

Hide

Forgot your password?

Or register your new account on DocShare.tips

Hide

Lost your password? Please enter your email address. You will receive a link to create a new password.

Back to log-in

Close