BN209 Software Engineering Proof Reading Services

BN209 Software Engineering Proof Reading Services

1.Project overview

This section provides an overview about the project

1.Definitions & Acronyms

 Definition and acronyms used for these projects are as follows:

2.Referenced document or notes

3.Project name

Alibaba online shopping website

4.Project Introduction

Purpose of this project is to create a website that could enable the company to attain a competitive value in the e-commerce sector. The website will be designed satisfying consumer and market requirements. This report will focus on the software requirements of the users that will access the website. The entire functional and nonfunctional requirement will be discussed. The context diagram, ERD diagram, DFD diagram will be included in the SRS document. An MS access database will be designed to store the all the required data on the website.

5.Project goals

The main aim of this project is to design and implement an online shopping website ‘Alibaba’ to reach for more customers in the market. The goal of this project is to target the market in order to increase productivity and revenue for the products. The goals of the project are:

Specific:  The goal of the website that we can track per day unique customer or visitor to the website (community.optimizely, 2015).

Measurable:This goal of the Alibaba website is quantitativeinstead of qualitative. Through the website, we can track the progress chart of the website.

Actionable: The goal of this projectto take such actions which can help to reach achievements.

Timely and Time-bound

The main goal of this website that we can achieve our goal on due time and date i.e. deadline shouldn’t be missed (roborr, 2017).

6.Targeted audience

The following target audience can be in an

Investors: The investors are those which invest money in the organization. The organization can increase the business if an investor invests the money in the company. All Financial issue is solved and company can purchase more and more product and expand the business.

Suppliers: Suppliers are those who supply the products. As the demand of the customer increases the company increases the suppliers. If delivery of the customer will not be on time then the customer will be satisfied.

Customer:The customers are those who visit the website and purchase the products. The main goal of the website to reach more and more customer.

Whole sellers: The Alibaba website mainly sells the products to the whole seller. So the online shopping organization mainly earns more profit from the whole seller compare to retails. So whole sellers are the main target audience of the proposed online shopping organization.

Manufactures:Manufactures are those who manufacture the products. So the target of the company manufactures the different types of the products so that customer can find every type of products on one website it will increase the customer.

7.Project Objective

The system which is going to be developed has the following objective:

Website:A website is to be developed for online shopping which will be delivered to the users through online. The objective of developing the online website is to attract more and more audience towards the organization. The graphics used should be proper and simple. The image should be clear.

Reduce loading time of the website:The website must be very low bandwidth so that website takes little time to load the website. If a website takes more time to load their customer may leave the website.

Database

To store all the data related to the customer, admin, staff personal details, and product details needed a secure server. So MySQL server is needed to store all the information.

Security/Privacy

The proposed system must fulfill all the security and privacy issues. The data stored in the system should be secured so that unauthorized person can’t use the data.

Testing

Testing is very important to test whether all the functionality of the website is working properly or not. Our objective is to perform black box testing and white box testing.

8.Support

Once the online shopping website has been implemented and deployed to the client, the client may request any support and maintenance then it will be charged extra cost as an additional requirement because it is not part of the scope.

9.Stakeholders

A stakeholdermay be any person, organization who involves the activity of the organization. A stockholder can be affected or can affect the objectives, goals, and policies of a Company or organization (Businessdictionary, 2017).

For the Alibaba online shopping website the stakeholder may be:

Customer:  Customer is the end user of the Alibaba website. Customers are those who visit the website and purchase the products. Customer may register on the website, he can search the products, add to cart the products and purchase products. The customer can also give feedback about products. The customer can chat online for any queries.

Administrator:Theadministrator is those who manage the overall organization. They have high authority to take a decision about Alibaba online shopping organization. He will decide which products to be sell, new offers, stock details about products and take other organization related decision.

Staff:Staff is the person who works in the organization.  Staff may be an accountant, manager, suppliers and all other people who work for the organization.

Development Team:

The development team is those who design and implement the website. They develop the system in the module and each module is tested and after all, modules are combined and then again the whole system is tested.

Accountant:Accountant is those who manage all the account details. All the product payment details, salary details are managed by the accountant.

Suppliers:  Suppliers are those who supply the productorderedby the customer. The administrator asks the supplier to deliver new products. Suppliers can also give feedback on the website and can chat online if have any query.

10.System context

The Alibaba online website will be hosted online. A backend database server is needed to store all the data. The deployment of the proposed system has been described in Appendix C.

11.Acceptance criteria

The acceptance criteria of the projects have been fulfilling after completing the user and system acceptance testing. The developed system will be accepted by the client due to fulfilling the following requirement:

1.The login system of the website is working properly and then after the successful login, the correct page is opened according to the user's role.

2.The products are successfully added to the shipping cart which is being stored in the backend Mysql database.

3.The payment gateway system is working properly.

4.All the WebPages are linked properly and all other functions are working properly.

12.Evaluating Success

To evaluate the success of the project the following factors should succeed:

1.acceptance criteria’s success

2.functional,unit and integration testing

3. client’s feedback

4.Customer feedback

2. General Description

2.1. Product Functions

The proposed system has the many functions which reduce the maintenance cost and will reduce the labour efforts to maintain the system. The main functions of the system are as follows:

1.Display tests:the website will be provided with login webpage. If invalid username and password are entered then a Message box will be displayed which shown “the entered username and password is incorrect. Please try again.”

2.Record data: when the user selects a product and add to cart then these details will be recorded in the database.

3.Surveys:user can visit the website and can survey about the different products, he can know what is in trend nowadays. He can save order history. The user can manage his profile and save products for later purchasing.

4.Administration area: the administrator allows the user to register, login into the system. The administrator has user controls, has authority to create and manage user, manage products.

5.Download Data: user can download the payment receipt if he made any purchasing, may download images etc.

2.2. User characteristics

There can be three types of the users of the proposed website:

1.Administrators:the administrators are those who take all high authorities decision for the organization. Administrators add and update the products. The categories of the products and vendors are administrated by the administrators.

2.Sellers:the products are added to the database by the seller. The stored products in the database will be visible to the end user. The seller manager the products store by them.

3.Customers/ end user:customer/ end user are those who visit and purchase the products.

2.3. Technical assumptions and dependencies

1.With the use of normal quality images and theme, it is assumed that the loading time will be minimum and performance will be good.

2.With the design of the login system, it is assumed that the proposed system will provide security and privacy.

3.With the testing, the plan will be useful for maintaining the proposed online shopping website without the need of the external parties.

4.A prototype will be provided to the client so that all the requirement of the project can be collected before developing the website.

2.4. Product Outlook

2.4.1. User Interfacing

2.4.1.1.Use cases

The use case diagram is also referred to as behavioral diagram which includes all the actions that a system must perform. The use case diagram is shown below in Appendix D. 

Use Case 1-Administrator Login

Procedure            

1.The user opens the login webpage of the website

2.The user enters the username and password in the login field.

3.If the entered username and password is correct then the system will open the main page of the administrator.

4.After the successful login, the administrator will perform all the administrator related operations.

Exceptions

The userhas entered the incorrect login name and password. If the user enters incorrect login details he has to again try again.

Database requirement

The admin table from the table will be accessed. the username, password and role column will be read from the database.

Use Case 2 - Admin

Actor:Admin

Procedure

1.Use case must be performed

2.After the successful login, there will be multiple options related to the manager user, manage products. If admin selects “manage user” then admin will able to create a new user and may control user activities.

Exceptions

If the user login as a user, not an admin then the system will display the normal operation related to the user, not administrators.

Database requirement

The admin table from the table will be accessed. the username, password and role column will be read from the database.

Use Case 3 - User login

Actor:  End-user

Procedure

1.The user opens the customer login page of the website

2.The user enters the username and password that they create at the time of the registration.

3.If the username and password are correct then the system opens the customer’s main webpage.

4.After successful login, the user may perform all the user operations such as search products, buy products etc.

Exception

1.User forgets the password. There will be a button will be available to recover the password. When the user clicks on that button then a new page will be opened to reset the password.

2.User forgets to use the name. There will be a button will be available to recover username.when the user clicks on that button then a new page will be opened to reset the username.

3.The usermay not register on the website.

Database requirement

The admin table from the table will be accessed. The username, password and role column will be read from the database.

Use Case 4- End-user

Actor-End-user

Procedure

1.Use case 3 must be performed.

2.After successfully login the user can search the products, select product, add to cart products in the shipping cart, purchase products.

3.The usermay give feedback on the website.

Exception

The usermay not register into the system.

If the user login as an admin, not the user then the system will display the normal operation related to the administrator, not the user.

Database requirement

The admin table from the table will be accessed. The username, password and role column will be read from the database.

1.Activity diagram

Activity diagram represents the flow from one activity to another activity. an activity can be defined as an operation of the system. The flow between can be sequential or concurrent(Tutorialpoint, 2017).

2.Memory constraints

The proposed system requires a large amount of the memory space as the system is developed of the organization. Up to 100 MB, hard disk space is required to save the text file like HTML, CSS, and JS.  Up to 50 MB, hard disk space is required to store the images of the products. MySQL requires almost 2GB to store all the products details, customer details, order history and all the organization history.

The above is an estimation of the size of the database.

3.Operations

The system will be developed in such a way that it requires minimum maintenance requirement. Only admin may add user and products. The operation of the admin include the organization management, user control, add user, product management. The operation of the staff is the services provider according to their role. The operation of the user visit website and purchase products.

2.4.4 Adaptation / Compatibility Requirements

In future, it is possible that the system will require the adaption which is not part of the scope. The proposed system may be used by other organization. The client requirement is only that the website should be hosted on one server so the compatibility requirement of the system will be motioned by the client and the project will be developed according to this compatibility requirement.

4.User base

The user base of the system may be customer, admin, staff, and supplier. The customer may visit the website and purchase the product.  The administrator will perform all administrator activities. The suppliers will add the product to the database and supply the product to the customer. The staff provides services according to their role in the organization.

5.General design constraints

I have considered the following constraints which may affect the e-commerce website design and development:

Scope:The scope is the major constraints of the proposed e-commerce website. The productivity will be increased and the business will be enhanced. Due to good knowledge and skill of the project team, the website is effective and is increasing productivity.

Time:time of developing this website will be divided into two parts. In the first phase the analysis, planning, prototype development will occur and then this prototype will be delivered to the client so that we can collect feedback before starting the development phase. The second phase includes the design and development of the online shopping website, testing and implementation will be included.

Cost:

As it is an organization project so the development cost is high. The overall cost of the project include the following sources like project team cost, infrastructure cost, graphics/ animation cost, testing and maintenance costing, advertisement cost, outsourcing cost to an external party.

6.Project Feasibility

Economic: Theproposedonline shopping project is Economical feasible. The project is implemented on existing infrastructure.  The benefit of the proposed system is more than developing cost.

Operational: Operational feasibility means after the development and deployment the system is useful or not. Before the developing of the website, all the problem and requirement are documented. The proposed system is operationally feasible and acceptable of any solution to the problem mentioned in the documentation.

Technical: the proposed online shopping is feasible within the current technology’s limits. The system is available within the resource constraints like budget, schedule etc.

Legal / Political: there is no legal or political issue which may affect the proposed online shopping. All the government policies and rules are followed by the proposed system.

Ethical: there is no ethical issue which may affect the proposed online shopping. The proposed system provides security and there are no chances of theft of the data. The proposed system follows all online selling laws.

7.Requirements

Software requirement is expressed as document file which describes what system will do without specifying how the system will do. The software requirement specifies the external behavior of the system, constraints needed for implementation. The requirement document mainly includes:

1.Requirement definition

2.Requirement specification

Software requirements can be divided into two parts:

1. Functional requirements

The functional requirement specifies what the proposed online website should do i.e. the functionality of the website is included in the Functional requirement document.

Authentication:The proposed online shopping system should provide login option for the customer, the admin that is previously created. After successful login, the website should redirect the webpage according to login type.

Add to cart:If a customer wants to buy a product he can add to cart them. From there he can purchase the products or can cancel the products.

Sign in:Customer can sign on the website before using it. After successful login, he can access the website.

Sign out: Customer can sign out after using the website so the unauthorized person can’t use it.

Navigation:   All the links of the website should be properly connected and the user should easily navigate from one webpage to another webpage.

Online chat:The Alibaba website also provides an option for Online Chat. If the user has any query user can chat and ask their query.

Payment gateway:The website should have the payment option like a credit card, debit card, net banking etc.

Social media integration:

Thewebsite should also include the links to the social media like Facebook, YouTube, twitter, linked in that are directly connected to the login page of these social media sites(Reqtest, 2017).

2.Nonfunctionalrequirements

The nonfunctional requirement specifies how the proposed online website will work.

Load time:

Load time of the website should be minimum. As the website is accessed by the widest users so the loading time of the website should be minimum. If loading time will be high then the user may leave the website.

Security: The proposed online website should be secure. The only authorized user should use the website.

Privacy:The identity of all the users should be paramount. There should be no way that anyone can track the other identity.

GUI (Graphical User interface):Graphical user interface should be easy and proper. The images, GUI used for the website should be simple and contrasting colors should be used for text.

3.Automatically generated value Rules

4.Interface requirement

1.User interface

The interface should be user-friendly i.e. user can easily navigate through all pages of the website. Images and theme should be normal quality so that the WebPages take less time to load. The space of the WebPages should be kept light so that webpage doesn’t lake long time load.

2.Mock-upsof the website to be developed

Figure 1 Homepage

Figure 2 products page

Figure 3 special offer page

Figure 4 contact page

3.Hardware interface

Processor: Pentium or  Higher.

Input devices: keyboard, mouse, screen

Output devices: monitor

RAM: 1 GB or higher

4.Software interface

OS (operating system): Windows, Linux etc.

Techniques:HTML, CSS, JS

Database:  MYSQL

Web browser: a web browser that interprets the HTML, CSS, JS code and displays the website on the end user computer system.

5.Communication protocols

TCP/IP: the TCP/IP is used for sending and receiving the emails at client side and server side. An email confirmation is sent to the customer for sending the products to the shipping address.

SQL:the proposed online website will use MYSQL as the backend database and all the query and update operation will be performed on it.

6.Sitemap

Figure 5 Sitemap of the website

5.Hardware requirements

1.Client side

Processor: Pentium or  Higher.

Input devices: keyboard, mouse, screen

Output devices: monitor

RAM:1 GB or higher

2.Server side

UOB-community (or equivalent environment)

6.Software requirements

1.Client side

Web browser: aweb browserthat interprets the HTML, CSS, JS code and displays the website on the end user computer system.

(Operating system):Windows, Linux etc.

2.Server side

Firewallto protect the proposed system from illegal activities

Database:  MYSQL

(Operating system): Windows, Linux etc.

7.Database requirements

The ER diagram and database schema is described below which represent the all the entities and attributes.

1.Entity-Relationship Diagram

Entity-Relationship Diagram i.e. ER diagram represents the relationship between entities of the e-commerce website.

Figure 6 ERD DIAGRAM

2.Entity-Relationship Diagram Notes & Assumptions

Entity-Relationship Diagram i.e. ER diagram represents the relationship between entities of the e-commerce website.

1.Notes

1.The attributes which are the primary key are shown using underline. A primary key uniquely identifies the table.

2.The attributes which are foreign key are shown italic.

2.Database assumptions

1.A customer may make multiple orders so the relationship between customer and order details may be one to many.

2.One product can be ordered multiple times so the relationship between order details and products may be many to one.

3.One supplier may provide multiple products details so the relationship between the suppliers and product details may be one to many.

4.The supplierwill have one back up for each product so the relationship between suppliers and back up products may be one to one.

3.Database Schema

Define the logical view of a database is called database schema. It specifies how the data in the database is organized and the relationship between them. The database schema of the database is provided below:

Figure 7 logical view of the database

Customer table

Product_details table

Suppliers table

Backup_products

Order_detail table

8.Extra Quality Requirements

This website is used for each age of the person. All types of products will be available on this website so that user can get each type of products.

9.Training Requirements

The training document will be prepared and provided to the end user so that the end user understand how to access the website the understand the basic web knowledge.

4.Appendixes

1.Appendix A - Context diagram

The context diagram represents the relationship between the System and other external entities(Adams, 2017).

The system is Alibaba online shopping website and the external entities are  Customer, management, supplier and accountant.

Figure 8 context diagram

2.Appendix B – DFD (Level 0)

The DFD (level 0) extends the above context diagram. DFD  represents the flow of the information between processes of the system(Lucidchart, 2017). The DFD for the proposed system is shown below:

Figure 9 DFD (level 0)

3.Appendix C - Deployment Diagram

The  virtual server is shown below on which the website has been hosted :

Figure 10 deployment diagram

4.Appendix D - Use case model

Use case diagram represents the activity of the system between the actors of the system (UML-diagrams, 2017). The use case diagram of the proposed system is shown below:

Figure 11 Use case for customer

Figure 12 customer authentication use case

Figure 13 check out use case

5.Appendix E - Activity diagrams

The activity diagram of the developed system is shown below:

Figure 14 Activity diagram

6.Appendix F – Alibaba online shopping testing

Login testing:

Awaiting survey from admin and Client

Functional testing:

Awaiting survey from Client

Successfully payment testing

Awaiting survey from Client

Appendix G – Auto Generated Emails

The following email will be generated automatically for proposed online shopping website

1.The Shopping Cart Abandonment Email

2.The Order Confirmation Email

3.The Shipping Confirmation Email

4.The Customer Feedback Email

7.Appendix H – Level Progress Diagram

The level progress diagram represents all levels which are included when developing the system. The level progress diagram is shown below:

Figure 15 Level progress diagram

References

7 Goals You Need to Set For Your Website - Rob Orr. (2017). Rob Orr. Retrieved 27 December 2017, from https://roborr.net/website-tips-tools/7-goals-you-need-set-your-website

Adams, C. (2017). Context Diagram Retrieved 27 December 2017, from http://www.modernanalyst.com/Careers/InterviewQuestions/tabid/128/ID/1433/What-is-a-Context-Diagram-and-what-are-the-benefits-of-creating-one.aspx

Functional and non functional requirement(2017). Reqtest. Retrieved 27 December 2017, from https://reqtest.com/requirements-blog/functional-vs-non-functional-requirements/

Ecommerce Goals. (2015). Community.optimizely. Retrieved 27 December 2017, from https://community.optimizely.com/t5/Testing-Ideas-Strategy/Ecommerce-Goals/td-p/10467

UML - Activity Diagrams. (2017). Tutorialspoint. Retrieved 27 December 2017, from https://www.tutorialspoint.com/uml/uml_activity_diagram.htm

UML diagrams.(2017). Uml-diagrams.Retrieved 27 December 2017, from https://www.uml-diagrams.org/use-case-diagrams.html

What comes after those ellipses?. (2017). BusinessDictionary.Retrieved 27 December 2017, from http://www.businessdictionary.com/definition/stakeholder.html

What is a Data Flow Diagram. (2017). Lucidchart. Retrieved 27 December 2017, from https://www.lucidchart.com/pages/data-flow-diagram