Software Requirement Engineering

Project: Electronic Store System Submitted To: Sir Muhammad Waseem

Submitted By: Jamal Ahmad Fasial Aziz Reg No: 906 FBAS/BSSE/F09/B Reg No: 911FBAS/BSSE/F09/B

Malik Murad Ali Reg No: 952FBAS/BSSE/F09/B

Due Date: May 21, 2012

Declaration
We hereby declare that this Software, neither as a whole nor as a part there of has been copied out from any source. It is further declared that we have developed this Software entirely on the basis of our personal efforts made under the sincere guidance of our teacher. No portion of the work presented in this report has been submitted in support of any application for any other degree or qualification of this or any other university or institute of learning.

Jamal Ahmad
906/FBAS/BSSE/f09

Fasial Aziz
911/FBAS/BSSE/f09

Malik Murad Ali

952/FBAS/BSSE/f09

ii

E STORE

E Store Vision Document

Version <1.0>

iii

Revision History
Table 1: Revision History

Date 12 May,2012

Version 1

Description Vision Document

Author Murad,Jamal,Faisal

iv

Table of Contents
1. Introduction ............................................................................................................................. 1 1.1 1.2 1.3 1.4 1.5 2. Purpose ............................................................................................................................. 1 Scope ................................................................................................................................ 1 Definitions, Acronyms, and Abbreviations ...................................................................... 1 References ........................................................................................................................ 1 Overview .......................................................................................................................... 1

Positioning ............................................................................................................................... 1 2.1 2.2 Business Opportunity ....................................................................................................... 1 Problem Statement ........................................................................................................... 2

3.

Stakeholder and User Descriptions.......................................................................................... 2 3.1 3.2 3.3 3.4 Stakeholder Summary ...................................................................................................... 2 User Summary .................................................................................................................. 3 User Environment ............................................................................................................ 4 User Profiles ..................................................................................................................... 4 System Administrator ............................................................................................. 4

3.4.1

3.4.2 Customer .......................................................................................................................... 5 3.4.3 Store Owner...................................................................................................................... 5 3.5 4. Key Stakeholder or User Needs ....................................................................................... 6

Product Overview .................................................................................................................... 6 4.1 4.2 Product perspective .......................................................................................................... 6 Summary of Capabilities .................................................................................................. 6 Customer Support System ....................................................................................... 6

Table 4-1 4.3 5.

Assumptions and dependency .......................................................................................... 7

Product Features ...................................................................................................................... 7 5.1 5.2 5.3 5.4 5.5 5.6 User friendly:.................................................................................................................... 7 Error Free system: ............................................................................................................ 7 Easy to learn: .................................................................................................................... 7 No Headache of working: ................................................................................................ 7 Record Keeping: ............................................................................................................... 7 Data Handling: ................................................................................................................. 7
v

6. 7.

Constraints ............................................................................................................................... 8 Introduction ............................................................................................................................. 9 7.1 7.2 7.3 7.4 7.5 Purpose ............................................................................................................................. 9 Scope ................................................................................................................................ 9 Definition, acronyms and abbreviations........................................................................... 9 References ........................................................................................................................ 9 Overview .......................................................................................................................... 9

8.

Overall description ................................................................................................................ 10 8.1 8.2 8.3 8.4 8.5 8.6 8.7 Product perspective ........................................................................................................ 10 Hardware Interfaces ....................................................................................................... 10 Communication interfaces.............................................................................................. 10 Operations ...................................................................................................................... 10 Site adaption requirements ............................................................................................. 10 Constraints...................................................................................................................... 10 Assumptions and dependencies ...................................................................................... 10

9.

Functional Requirements: ...................................................................................................... 11 9.1 9.2 9.3 9.4 Customer Module ........................................................................................................... 11 Store Owner Module ...................................................................................................... 11 Administrator Module .................................................................................................... 11 Web User ........................................................................................................................ 11 Non Functional Requirements ........................................................................................... 12

10.

10.1 Efficiency ....................................................................................................................... 12 10.2 Time Factor .................................................................................................................... 12 10.3 Reliability ....................................................................................................................... 12 10.4 User Interface and Human Factors ................................................................................. 12 10.5 Documentation ............................................................................................................... 12 11. Use Case Diagram.............................................................................................................. 13

11.1 Customer Use Case Diagram ......................................................................................... 13 11.2 Administrator Use Case Diagram .................................................................................. 13 11.3 Store Owner Use Case Diagram..................................................................................... 14 11.4 Web User Use Case Diagram ......................................................................................... 14
vi

12.

Use Cases ............................................................................Error! Bookmark not defined.

12.1 Login ...............................................................................Error! Bookmark not defined. 12.2 Logout ............................................................................................................................ 16 12.3 Create User ..................................................................................................................... 17 12.4 Add Categories ............................................................................................................... 18 12.5 Update Categories .......................................................................................................... 19 12.6 Add Product.................................................................................................................... 20 12.7 Update Product ............................................................................................................... 21 12.8 Search Product................................................................................................................ 22 12.9 View Product .................................................................................................................. 23 12.10 12.11 12.12 12.13 12.14 12.15 12.16 12.17 12.18 12.19 12.20 12.21 13. 14. View Contact Us ......................................................................................................... 24 Place Order ................................................................................................................. 25 Add To Cart ................................................................................................................ 26 View Cart .................................................................................................................... 27 View Shopping History .............................................................................................. 28 View Orders ................................................................................................................ 29 View Profile ................................................................................................................ 30 Update Profile ............................................................................................................. 31 View Account ............................................................................................................. 32 Manage Account ......................................................................................................... 33 Confirm Order ............................................................................................................ 34 View Sold Product ...................................................................................................... 35

Class Diagram .................................................................................................................... 36 Sequence Diagram ............................................................................................................. 37

14.1 Login .............................................................................................................................. 37 14.2 Logout ............................................................................................................................ 37 14.3 View Shopping History .................................................................................................. 38 14.4 View Product .................................................................................................................. 38 14.5 Manage Account ............................................................................................................ 39 14.6 Manage Categories ......................................................................................................... 40 14.7 Manage Product.............................................................................................................. 41
vii

14.8 Manage Profile ............................................................................................................... 42 14.9 Confirm Order ................................................................................................................ 43 14.10 14.11 14.12 14.13 15. View Account ............................................................................................................. 43 View Sold Product ...................................................................................................... 44 View Profile ................................................................................................................ 44 View Contact Us ......................................................................................................... 45

ACTIVITY DIAGRAM..................................................................................................... 45

15.1 AddProductInfo .............................................................................................................. 45 15.2 Login .............................................................................................................................. 46 15.3 Search Product................................................................................................................ 46 15.4 Signup............................................................................................................................. 47 15.5 Update Customer Profile ................................................................................................ 47 16. 8 Questions......................................................................................................................... 48

16.1 Q#1 ................................................................................................................................. 48 16.2 Q 2 .................................................................................................................................. 49 16.3 Q 3 .................................................................................................................................. 49 16.4 Q4 ................................................................................................................................... 49 16.5 Q5 ................................................................................................................................... 49 16.6 Q6 ................................................................................................................................... 49 16.7 Q7 ................................................................................................................................... 50 16.8 Q8 ................................................................................................................................... 50

viii

Figure of Contents Figure 1 Customer Use Case Diagram.......................................................................................... 13 Figure 2 Administrator Use Case Diagram ................................................................................... 13 Figure 3 Store Owner Use Case Diagram ..................................................................................... 14 Figure 4 Web User Use Case Diagram ......................................................................................... 14 Figure 5 Class Diagram ................................................................................................................ 36 Figure 6 Login Sequence Diagram ............................................................................................... 37 Figure 7 Logout............................................................................................................................. 37 Figure 8 View Shopping History .................................................................................................. 38 Figure 9 View Product .................................................................................................................. 38 Figure 10 Manage Account ........................................................................................................... 39 Figure 11 Manage Categories ....................................................................................................... 40 Figure 12 Manage Product ............................................................................................................ 41 Figure 13 Manage Profile ............................................................................................................. 42 Figure 14 Confirm Order .............................................................................................................. 43 Figure 15 View Account ............................................................................................................... 43 Figure 16 View Sold Product ........................................................................................................ 44 Figure 17 View Profile.................................................................................................................. 44 Figure 18 View Contact Us........................................................................................................... 45 Figure 19AddProductInfo ............................................................................................................. 45 Figure 20 Login............................................................................................................................. 46 Figure 21 Search Product .............................................................................................................. 46 Figure 22 Signup ........................................................................................................................... 47 Figure 23 Update Customer Profile .............................................................................................. 47

ix

Vision Document
1. Introduction
The Purpose of this is to provide the users with the facility of shopping online. User can purchase product and complete system is set to record all the transactions and the system can save complete History of records for their costumers for future referenced. 1.1 Purpose The purpose of this document is to make a costumer reliable. It saves time. Through this costumer can make an account and can easily access and book their orders online. It focuses on the capabilities and functionalities needed by the stakeholders and the target users. The details of how the system fulfills these needs are detailed in the use-case and supplementary specifications. Scope The Scope of the system covers the customer, administrator and store owner .customer through this system can purchase products online .store owner through this website can register their products over the internet through online. Administrator handles all these activities like online shopping, registration.

1.2

1.3 1.4

Definitions, Acronyms, and Abbreviations E Store- Electronic store References www.google.com.pk Different Case studies / Projects from Central Library Overview This vision document describes in brief need for this product and how it will fulfills the needs. It describes the stakeholders associated with the product, the user for which the product is developed, the targeted users and their profiles, the environment of the users and the environment of the system in which the product will be used. The document then gives an overview of the features and a capability of the E-Store. It gives the brief summary of capabilities of the product. It also enlists the major features that is intended to be included in the product. In brief this document tries to cover all aspect of the E-Store and gives a clear vision about how the final product will be.

1.5

2.
2.1

Positioning
Business Opportunity The computerize system for Store will act as a website provides an efficient, easy to use system with any-time access for the customers. It will improve the market shares in stock

E-Store

exchange. It will also increase the number of customers. Due to this system there will be more employment and less building cost. 2.2 Problem Statement The problem of Searching is difficult of old products. No proper system backup is available. No proper record is maintained in registers. Maximum sale products are not known. Difficult for shopkeeper to learn all product names and its prices and amount of remaining items. Affects the impact of which is Wastage of time. Due the manual record keeping of sales and entries of products a lot of time is consumed. It is difficult to perform different activities, process sales, especially lack of resources which results in wastage of time. All Entries of a Shop will be recorded, Maintain Inventory Record, Sale Purchase Records, Sold History, Maximum Item Sold List, Complete System Backup, Generate Reports, Remaining item list etc.

a successful solution would be

Table 2: Problem Statement

3.
3.1

Stakeholder and User Descriptions

Stakeholder Summary Name System Analyst Description This is a stakeholder that works with the stakeholders to gather their requirements. Responsibilities Leads and coordinates requirements elicitation and use-case modeling by outlining the system's functionality. For example, identifying what actors exist and what use cases they require when interacting with the system.

E-Store

Requirements Specifier.

This is a stakeholder that works with the Analysts to correctly translate needs into requirements to be used for design

Specifies the details of one or more parts of the system's functionality by describing one or the aspects of the requirements, this will include functional and non-functional requirements. Responsible for the software architecture, which includes the key technical decisions that constrain the overall design and implements the project. Ensures that the system is going to be maintainable and the architectural solution supports the functional and nonfunctional requirements Plans, manages and allocates resources, shapes, priorities, coordinates instructions with customers and users, and keeps the project team focused. Also establishes a set of practices that ensures the integrity and quality of project artifact.

Software Architect

This is a stakeholder that is primary leading the system development

Project Manager

This is a stakeholder that is primary for leading the system development.

3.2

User Summary Name System Administra tor Description This person manages the system such as manage account, manage customer as well as manage reports. Responsibilities System admin manages the functionality of EStore such as manage customers, Stakeholde r Self

E-Store

manage account, addition and deletion of news & events, generate reports. Customer They have limited access to create the account, place order, search product, and manage their profile. Customer can only place order, search product, mange profile, view product. They dont have any access to basic functionalities of the system. Store owner can manage profile, confirm order, manage product and manage store etc. Self

Store Owner

This person manage

manage

product,

Self

Profile, manage store, confirm order etc.

3.3

User Environment This system will run on World Wide Web (www). All the users have remote access through internet. The system will be required to run at least moderately well on the following types of system. Internet Explorer Internet Connection Complete System User Profiles

3.4

3.4.1 System Administrator Representative Description Type Responsibilities Administrator A private individual that maintains the system or setup the system and other activities etc. This user is highly technical back ground. This user customizes the system according to user requirements and manages the all activities such as manage account, manage customer as well as manage reports etc. This person also provides

E-Store

help in the system trouble shooting. Success Criteria Involvement When the user of the system is satisfied or system admin customize the system according to the user's requirements. Highly involved in the project during the requirements elicitation and implementation phase.

3.4.2 Customer Representative Description

Customer An individual that uses the system to manage his profile, place order, search product, view product and check status against his/her request. Must be familiar with the system and required some technical background. Customer can place order, search product, mange profile, view product. Successfully manage his tasks and profile May be involved in the project during the request elicitation.

Type Responsibilities Success Criteria Involvement

Comments/Issues Comments and suggestions from the friends or relatives will be welcomed.

3.4.3 Store Owner Representative Description

Store Owner A private individual that maintains the system or setup the system and other activities etc Must be familiar with the system and required some technical background. Store owner can manage profile, confirm order, manage product and manage store etc. When the user of the system is satisfied. Highly involved in the project during the requirements elicitation and implementation phase

Type Responsibilities

Success Criteria Involvement

E-Store

3.5

Key Stakeholder or User Needs Priority Need Broadcast messages High

Concerns

Current Solution

Proposed Solutions Send message through email

Fast deliver None message to all recipients Easily to understand the system and easily to navigate None

Easy to Use

High

Simple user interface according to user need .

Secure access

High

None

Encoding scheme used for storing the personal information.

4.

Product Overview
This section provides a high level view of the product capabilities, interfaces to other applications, and system configurations. This section usually consists of three subsections, as follows: Product perspective Product functions Assumptions and dependencies

4.1

Product perspective The E Store will act as website, and it is independent and totally self contained. It will help to order product, manage product. It also helps to manage users own profile. There is an efficient mechanism for searching the desired products. There is also ability to manage news and events.

4.2

Summary of Capabilities Table 4-1 Customer Benefit Easy management to store information. Customer Support System Supporting Features Easy to keep information up _to _date.

E-Store

Quick response of information of required product.

Availability of related information of product on remote locations.

The burden on staff is decrease.

Due to E Store the management of the product and sales is easy and fast. User's Information Management.

Keeping Records of Users 4.3

Assumptions and dependency No hardware and software dependencies accept a good internet connection and generic up to date web browser

5.
5.1

Product Features
User friendly: The proposed system is the user friendly because it is easy to operate the system. A user feels not a signal difficulty to operate it. Error Free system: The proposed system is free of error as we examined the test it several times. Easy to learn: It is very easy to learn less effort and training is required to operate the system. It is more efficient. No Headache of working: The proposed system is user friendly and requires not high class qualification: So it is easy in handling. Record Keeping: The proposed system has to increase efficiency of the system of record keeping method.

5.2

5.3

5.4

5.5

5.6

Data Handling: In the manual system one hand to performed all the data entries and processing by means of pen and pencil. So there was a great chance of mistake which affects the overall system badly. The proposed system performed all the data handling process with more effectiveness and reliability.It proved the validity check for input data. Their checks were. necessary for preventing the data from errors.

E-Store

6.

Constraints
The system should enforce user authentication security and guaranty timestamps reliability quality ranges.

E-Store

SRS Section 7. Introduction

7.1 Purpose The purpose of this document is to describe the requirement specifications for an Electronic Store. The intended audience of this document includes the prospective developers of the tool and the technical assessment personnel of the client organization. 7.2 Scope The software system to be produced is a Electronic Store. This will be referred to as E Store through this document. The Electronic Store will allow user working within a defined Field to perform various activities, such as manage accounts, manage customers, manage reports, place order, search product etc . The E Store could be used in any remote environment to keep the database of products, records of sales, user and other related activities. The goals are manifolds depending on the users of the system. 7.3 Definition, acronyms and abbreviations E Store: Electronic Store. Activity: Nature of what is being done. SRS: Software requirements specification. 7.4 References For the better understanding of project overview help from www.knowledgetree.org 7.5 Overview The rest of this document contains an overall description of the E Store and the specific requirement for the system.

E-Store

8.

Overall description

8.1 Product perspective The E Store will act as website, and it is independent and totally self contained. It will help to order product, manage product. It also helps to manage users own profile. There is an efficient mechanism for searching the desired products. There is also ability to manage news and events. 8.2 Hardware Interfaces All components must be able to execute on a personal computer. 8.3 Communication interfaces User must communicate with the application with a server running over a TCP/IP connection. The server and the database components should be located on the same host. 8.4 Operations No specific formation must be required to use the tool. The server module must be installed and maintained with no interaction with existing software and should not require any specific technical skill from a network administrator. Back up operations must be defined. Recovery operations must be specified in case of network failure, user machine failure or a database failure. 8.5 Site adaption requirements No specific site adaption should be required. 8.6 Constraints The system should enforce user authentication security and guaranty timestamps reliability. 8.7 Assumptions and dependencies No specific assumption or dependencies.

E-Store

10

9.
9.1

Functional Requirements:
Customer Module Login Logout Place Order Search Product Manage Profile View Shopping History View Product Manage Cart Store Owner Module Login Logout Manage Product View Sold Product Confirm Order View Contact Us View Order Manage Profile View Account Administrator Module Login Logout Create User Manage Account Manage Customer Manage Product Manage Categories Manage Payment View Reports Web User View Product View Categories View Contact Us Search Product

9.2

9.3

9.4

E-Store

11

10. Non Functional Requirements

10.1 Efficiency Efficiency is defined as the economic utilization of available resources for achieving a desired objective, so that proposed system is more efficient than the existing one. It utilizes minimal human and financial resources, and still its output is far better in terms of time and appearance and error free. Time Factor Reports and queries can be produced quickly, thus reducing a lot of extra time used in manual generation of reports. Reliability The new system will be more reliable than the manual system, due to its accurate, secure and time decision making. User Interface and Human Factors Biological training should be required for user, every user who can use software with a little bit of computer literacy. Graphical user interface should be quiet interactive and should also be very simple. Documentation Documentation regarding the features and working of software, complete manual about the use of software in order to achieve the maximum efficiency should be provided with the product document.

10.2

10.3

10.4

10.5

E-Store

12

11. Use Case Diagram

11.1 Customer Use Case Diagram
uc Customer UCD

Login

Lagout Place Order

Search Product

Mange Profile Customer

View Shopping History View Product Manage Cart

Figure 1 Customer Use Case Diagram

11.2

Administrator Use Case Diagram

Figure 2 Administrator Use Case Diagram

E-Store

13

11.3

Store Owner Use Case Diagram

Figure 3 Store Owner Use Case Diagram

11.4

Web User Use Case Diagram

Figure 4 Web User Use Case Diagram

E-Store

14

Test Cases for Changing Password

Actor: User Purpose: To successfully change the password. Description: It first authenticates the user and then allowed to change password. Pre-Condition: User is currently logged into the system, and have the correct permissions to access the appropriate information. Post-Condition: Connection to server establishes, and user logs in successfully. Primary Scenario Actor Action 1. User enters user name and password and click on ok button. System Response 2. i) The system will connect to Database and check the user name and password against their. ii) The system will display the application window to user. Alternative Scenarios and Extensions Actors Actions 1a. User enters invalid login information (user name, password) and click on submit button. Alternative System Response 2a i) Connection to database is not established. ii) Login information is incorrect, indicate error.

E-Store

15

11.5 Logout
Actor: Administrator, Customer, Store Owner Purpose: To Logout from the system. Description: Every user is required to logout after using the system . Pre-Condition: User must be login. Post-Condition: User successfully logout from application. Primary Scenario Actor Action 1. The user must login. 3. The user navigates to logout user form from main menu. Alternative Scenarios and Extensions Actors Actions 1a. The user enters invalid login information. Alternative System Response 2a. Illegal user is restricted. 3a. Users can not logout. System Response 2. The Administrator, Customer, Store Owner are authenticated and administrators form is displayed.

E-Store

16

11.6 Create User

Actor: Administrator, Customer, Store Owner Purpose: To create new user accounts. Description: We need different user for handling the system. Therefore we need to create different user having different access levels according to their role. Pre-Condition: Authorized user must be logged in. Post-Condition: User is created successfully. Primary Scenario Actor Action 1. The user (Administrator, Customer, and Store Owner) must login. 3. The user navigates to create user form from main menu. 5. The administrator enters the profile Information of the new user. Alternative Scenarios and Extensions Actors Actions 1a. The administrator enters invalid login information. Alternative System Response 2a. Illegal user is restricted. 6a. Invalid and incomplete information will not be saved. System Response 2. The User is authenticated and user form is displayed. 4. Create User Form is displayed. 6. The provided information is validated and saved and confirmation message is displayed.

E-Store

17

11.7 Add Categories

Actor: Administrator Purpose: Add a new Category Description: Administrator is concerns with expanding business and in this context he expands a new category to system. Pre-Condition: Authorized user must be logged in. Post-Condition: Category Added successfully. Primary Scenario Actor Action 1. User opens the Categories information form. 3. User clicks add button to add new categories. 5. User enters the required attributes about new categories. System Response 2. The system will display the Categories information form. 4. The system will clear all the required fields. 6. Generates next product ID. i) Validity of information is checked on the basis of duplication and criteria mentioned. ii) Displays message of successfully added Categories.

Alternative Scenarios and Extensions Actors Actions 1a. User enters all the required information about Categories. Alternative System Response 6a i). Entered information is incorrect indicates an error.

E-Store

18

11.8

Update Categories
Actor: Administrator Purpose: Update the Category. Description: Administrator is concern with updating their Categories properties. Pre-Condition: Category must be added in the system. Post-Condition: Category update successfully. Primary Scenario Actor Action 1. The user must be logged first. 3. The user can enter, update or delete records according to their access level. System Response 2. The authentication of user is done and based on the role of the user specific form will be displayed to the user. 4. The data will be saved by the system successfully and the respective message is shown to the user.

Alternative Scenarios and Extensions Actors Actions 1a. The user enters invalid login information. 3a. The user enter invalid data. Alternative System Response 2a. Illegal user is restricted. 4a. Invalid data is not saved and meaningful message will displayed to the user.

E-Store

19

11.9

Add Product
Actor: Administrator, Store Owner Purpose: Add a new product.

Description: Administrator and store owner are concerned with expanding business and in this context they can put new product to the system. Pre-Condition: Authorized user must be logged in. Post-Condition: Product added successfully. Primary Scenario Actor Action 1. User opens the product information form. 3. User clicks add button to add new product. 5. User enters the required attributes about new product. System Response 2. The system will display the product information form. 4. The system will clear all the required fields. 6. Generates next product ID. i) Validity of information is checked on the basis of duplication and criteria mentioned. ii) Displays message of successfully added product.

Alternative Scenarios and Extensions Actors Actions 1a. User enters all the required information about product. Alternative System Response 6a i). Entered information is incorrect indicates an error.

E-Store

20

11.10 Update Product

Actor: Administrator, Store Owner Purpose: Update the product. Description: Administrator and store owner are concerned with updating there products. They can add properties like name pictures etc. Pre-Condition: Product must be added in the system. Post-Condition: Product update successfully. Primary Scenario Actor Action 1. The user must be logged first. 3. The user can enter, update or delete records according to their access level. System Response 2. The authentication of user is done and based on the role of the user specific form will be displayed to the user. 4. The data will be saved by the system successfully and the respective message is shown to the user.

Alternative Scenarios and Extensions Actors Actions 1a. The user enters invalid login information. 3a. The user enter invalid data. Alternative System Response 2a. Illegal user is restricted. 4a. Invalid data is not saved and meaningful message will displayed to the user.

E-Store

21

11.11 Search Product

Actor: Customer, Web User, Store Owner Purpose: Search or view product. Description: Customer, Web User and Store Owner want to search product which he want to see or purchase that product. Pre-Condition: Authorized user must be logged in. Post-Condition: Product is in the website or not. Primary Scenario Actor Action 1. The user must be login in to the system first. 3. The user can view records of the product. System Response 2. The authentication of user is done and based on the role of the user specific form will be displayed to the user. 4. The data will be shown by the system successfully and the respective data is shown to the user.

Alternative Scenarios and Extensions Actors Actions 1a. The user enters invalid login information. Alternative System Response 2a. Illegal user is restricted.

E-Store

22

11.12 View Product

Actor: Customer, Store owner, Web User. Purpose: View a product. Description: Customer, Store owner and Web User are concern to view new product and their Description. Pre-Condition: Authorized user must be logged in. Post-Condition: Order is placed successfully. Primary Scenario Actor Action 1. User opens the product information form. System Response 2. The system will display the product information form. 3. The system will clear all the required fields. i) Validity of information is checked on the basis of duplication and criteria mentioned. Alternative Scenarios and Extensions Actors Actions 1a. User enters all the required information about product. Alternative System Response 2a. Entered information is incorrect indicates an error.

E-Store

23

11.13 View Contact Us

Actor: Customer, Web User, Store Owner Purpose: view about us. Description: Customer, Web User and Store Owner see the contact information about us. Pre-Condition: Authorized user must be logged in. Post-Condition: Contact information added successfully. Primary Scenario Actor Action 1. The user must open the website. 3. The user can view all messages. System Response 2. The authentication of user is done and based on the role of the user specific form will be displayed to the user. 4. The data will be shown by the system successfully and the respective data is shown to the user.

Alternative Scenarios and Extensions Actors Actions 1a. The user enters invalid irrelevant information. Alternative System Response 2a. Illegal user is restricted.

E-Store

24

11.14 Place Order

Actor: Customer. Purpose: Order of product to be purchased. Description: After purchasing the product the customer confirms the order Pre-Condition: Authorized user must be logged in. Post-Condition: Order is placed successfully. Primary Scenario Actor Action 1. User opens the order information form. 3. User clicks add button to add new order. 5. User enters the required attributes about new order. System Response 2. The system will display the order information form. 4. The system will clear all the required fields. 6. Generates next order ID. i) Validity of information is checked on the basis of duplication and criteria mentioned. ii) Displays message of successfully added order.

Alternative Scenarios and Extensions Actors Actions 1a. User enters all the required information about Order. Alternative System Response 2a. Entered information is incorrect indicates an error.

E-Store

25

11.15 Add To Cart

Actor: Customer. Purpose: Add product to cart/ purchasing product. Description: Customer is adding the product into his cart which product he want to purchase. Pre-Condition: Authorized user must be logged in. Post-Condition: Product added to cart successfully. Primary Scenario Actor Action 1. User opens the Product information form. 3. User clicks add button to add to cart. System Response 2. The system will display the product information form. 4. Add product into cart. i) Validity of information is checked on the basis of duplication and criteria mentioned. ii) Displays message of successfully added product.

Alternative Scenarios and Extensions Actors Actions 1a. User enters all the required information about product. Alternative System Response 2a. Entered information is incorrect indicates an error.

E-Store

26

11.16 View Cart

Actor: Customer Purpose: view the product in the Shopping Cart. Description: Customer can view the product that he wants to purchase. Pre-Condition: Authorized user must be logged in. Post-Condition: Content of cart is shown. Primary Scenario Actor Action 1. The user must be logged in. 3. The user can view records according to their required purchase products in the cart. System Response 2. The authentication of user is done and based on the role of the user specific form will be displayed to the user. 4. The data will be shown by the system successfully and the respective data is shown to the user.

Alternative Scenarios and Extensions Actors Actions 1a. The user enters invalid irrelevant information. Alternative System Response 2a. Illegal user is restricted.

E-Store

27

11.17 View Shopping History

Actor: Customer Purpose: view shopping history of user. Description: Customer can see all his previous shopping products in the content form. Pre-Condition: Authorized user must be logged in. Post-Condition: Content of all previous record is shown. Primary Scenario Actor Action 1. This use case begins when the user will open the site and logged in. 3. User will enter the required information. 5. Then the user can view his order history that what product he has purchased and the total amount spent on those products. Alternative Scenarios and Extensions Actors Actions 1a. User will not provide appropriate information. Alternative System Response 2a.System will show alert and will ask user to reenter the information to login. System Response 2. System will ask user to enter user id and password. 4. System will login the user successfully.

E-Store

28

11.18 View Orders

Actor: Store Owner Purpose: view the orders. Description: Store owner can view all the latest or pervious placed orders by customer and he can take action on these orders. Pre-Condition: Authorized user must be logged in. Post-Condition: shows all the orders placed by the customer. Primary Scenario Actor Action 1. The user must be login in. 3. The user can view records according to their required purchase products in the cart. System Response 2. The authentication of user is done and based on the role of the user specific form will be displayed to the user. 4. The data will be shown by the system successfully and the respective data is shown to the user.

Alternative Scenarios and Extensions Actors Actions 1a. The user enters invalid irrelevant information. Alternative System Response 2a. Illegal user is restricted.

E-Store

29

11.19 View Profile

Actor: Store Owner, Customer Purpose: view personal information. Description: Store owner and Customer can see the personal information. Pre-Condition: Authorized user must be logged in. Post-Condition: personal information added successfully. Primary Scenario Actor Action 1. The user must be login in. 3. The user can view profile that is added by the customer. System Response 2. The authentication of user is done and based on the role of the user specific form will be displayed to the user. 4. The data will be shown by the system successfully and the respective data is shown to the user.

Alternative Scenarios and Extensions Actors Actions 1a. The user enters invalid irrelevant information. Alternative System Response 2a. Illegal user is restricted.

E-Store

30

11.20 Update Profile

Actor: Store Owner, Customer Purpose: Update the Profile. Description: Store owner and Customer are concern with updating profiles properties like name contact no etc. Pre-Condition: Profile must be added in the system. Post-Condition: Profile updated successfully. Primary Scenario Actor Action 1. The user must be login in. 3. The user can enter, update or delete records according to their access level. System Response 2. The authentication of user is done and based on the role of the user specific form will be displayed to the user. 4. The data will be saved by the system successfully and the respective message is shown to the user.

Alternative Scenarios and Extensions Actors Actions 1a. The user enters invalid login information. 3a. The user enter invalid data. Alternative System Response 2a. Illegal user is restricted. 4a. Invalid data is not saved and meaningful message will be displayed to the user.

E-Store

31

11.21 View Account

Actor: Store Owner, Administrator Purpose: view the Account. Description: Store owner and Administrator can view all the latest or pervious account information. Pre-Condition: Authorized user must be logged in. Post-Condition: Show all the account information. Primary Scenario Actor Action 1. The user must be login in. 3. The user can view records according to their required purchase products in the cart. System Response 2. The authentication of user is done and based on the role of the user specific form will be displayed to the user. 4. The data will be shown by the system successfully and the respective data is shown to the user.

Alternative Scenarios and Extensions Actors Actions 1a. The user enters invalid irrelevant information. Alternative System Response 2a. Illegal user is restricted.

E-Store

32

11.22 Manage Account

Actor: Administrator Purpose: Manage the Account. Description: Administrator can manage all the accounts like add or delete payment that will pay by particular store owner. Pre-Condition: Authorized user must be logged in. Post-Condition: Show all the account information. Primary Scenario Actor Action 1. The user must be login in. 3. Administrator can manage all the accounts like add or delete payment that will pay by particular store owner. System Response 2. The authentication of user is done and based on the role of the user specific form will be displayed to the user. 4. The data will be shown by the system successfully and the respective data is shown to the user.

Alternative Scenarios and Extensions Actors Actions 1a. The user enters invalid irrelevant information. Alternative System Response 2a. Illegal user is restricted.

E-Store

33

11.23 Confirm Order

Actor: Store Owner. Purpose: Order of product that purchase. Description: After purchasing the product the Store Owner confirms that this order is confirmed. Pre-Condition: Authorized user must be logged in. Post-Condition: Order is placed successfully. Primary Scenario Actor Action 1. User opens the confirm order form. 3. User clicks add button to confirm order. System Response 2. The system will display the order information form. 4. The system will clear all the required fields. 5. Generates next order ID. i) Validity of information is checked on the basis of duplication and criteria mentioned. ii) Displays message of successfully confirm order.

Alternative Scenarios and Extensions Actors Actions 1a. User enters all the required information about Order. Alternative System Response 2a. Entered information is incorrect indicates an error.

E-Store

34

11.24 View Sold Product

Actor: Store Owner, Administrator. Purpose: View sold product. Description: Administrator and Store Owner is concern to view sold product. Pre-Condition: Authorized user must be logged in. Post-Condition: Product sold successfully. Primary Scenario Actor Action 1. User opens the Sold product information form. System Response 2. The system will display the Sold product information form 3. The system will clear all the required fields. i) Validity of information is checked on the basis of duplication and criteria mentioned. Alternative Scenarios and Extensions Actors Actions 1a. User enters all the required information about product. Alternative System Response 3a i). Sold product information is incorrect indicates an error.

E-Store

35

12. Class Diagram

class E-Store ManageOrders + + OrderID: int OrderName: int 0..* confirm_order() : void view_order() : void manage Order 1 Manages StoreOw ner address: int mob_no: int Name: int Owner_id: int password: int 1 have 1 Customer Web address: int Cust_id: int mob_no: int Name: int password: int

Manage Category + + + + CategoryID: int CategoryName: int add() : void delete() : void Search() : void Update_category() : void 1..* Manage Payment + + PaymentID: int PaymentType: int 1..* Add_Payment() : void Delete_payment() : void Has Manges Manage Product + + + Prod_id: int Prod_Name: int Prod_Type: int Add_Prod() : void Search_Prod() : void update_Prod() : void

1..* Profile + + + ProfileID: int ProfileOwner: int ProfileType: string Search_Profile() : void Update_Profile() : void View_Profile() : void 1..*

Has manages

Person address: int mob_no: int Authenticate name: String + password: int + UserID: int 1

Authentication password: String username: String signIn() : void signOut() : void

Has Manages 1..* 1..* 1..* -

Administrator address: int Admin_id: int mob_no: int Name: int passwod: int

1 1..* + + + Account accountID: int accountOwner: int accountType: String add_account() : void search_account() : void view_account() : void

Figure 5 Class Diagram

E-Store

36

13.
13.1

Sequence Diagram
Login

Figure 6 Login Sequence Diagram

13.2

Logout

Figure 7 Logout

E-Store

37

13.3

View Shopping History

Figure 8 View Shopping History

13.4

View Product

Figure 9 View Product

E-Store

38

13.5

Manage Account
sd Use Case View obj: Weborm Administrator Obj: Business Obj: DataAccess

OnClickUpdateAccount()

UpdateAccountData()

ExectueUpdateQuery()

ExecuteUpdateQuerySuccessfully()

OnClickInsertAccount()

InsertAccountData()

ExecuteInsetQuery()

ExecuteInsertQuerySucessfully()

OnClickDeleteAccount()

DeleteAccountData()

ExecuteDeleteQuery()

ExecuteDeleteQuerySucessfully()

Figure 10 Manage Account

E-Store

39

13.6

Manage Categories
sd Use Case View obj: Weborm Administrator Obj: Business Obj: DataAccess

OnClickUpdateCategories()

UpdateCategoriesData()

ExectueUpdateQuery()

ExecuteUpdateQuerySuccessfully()

OnClickInsertCategories()

InsertCategoriestData()

ExecuteInsetQuery()

ExecuteInsertQuerySucessfully()

OnClickDeleteCategories()

DeleteCategoriesData()

ExecuteDeleteData()

ExecuteDeleteQuerySucessfully()

Figure 11 Manage Categories

E-Store

40

13.7

Manage Product
sd Use Case View obj: Weborm StoreOwner Obj: Business Obj: DataAccess

OnClickUpdateProduct()

UpdateProductData()

ExectueUpdateQuery()

ExecuteUpdateQuerySuccessfully()

OnClickInsertProduct()

InsertProductData() ExecuteInsetQuery()

ExecuteInsertQuerySucessfully()

OnClickDeleteProduct()

DeleteProductData()

ExecuteDeleteData()

ExecuteDeleteQuerySucessfully()

Figure 12 Manage Product

E-Store

41

13.8

Manage Profile
sd Use Case View obj: Weborm StoreOwner Obj: Business Obj: DataAccess

OnClickUpdateProfile()

UpdateProfileData()

ExectueUpdateQuery()

ExecuteUpdateQuerySuccessfully()

OnClickInsertProfile()

InsertProfileData() ExecuteInsetQuery()

ExecuteInsertQuerySucessfully()

OnClickDeleteProfile()

DeleteProfileData()

ExecuteDeleteData()

ExecuteDeleteQuerySucessfully()

Figure 13 Manage Profile

E-Store

42

13.9

Confirm Order
sd Confirm Order obj: Webform StoreOwner obj: Business obj: DataAccess

ConfirmOrder()

GetOrderData()

ExecuteSelectQuery()

ExecuteSelectQuerySuccessfully()

Figure 14 Confirm Order

13.10

View Account
sd Confirm Order obj: Webform StoreOwner obj: Business obj: DataAccess

ViewAccountInfo()

GetAccountInfoData()

ExecuteSelectQuery()

ExecuteSelectQuerySuccessfully()

Figure 15 View Account

E-Store

43

13.11

View Sold Product

sd Confirm Order obj: Webform StoreOwner obj: Business obj: DataAccess

ViewSoldProduct()

GetSoldProductData()

ExecuteSelectQuery()

ExecuteSelectQuerySuccessfully()

Figure 16 View Sold Product

13.12

View Profile
sd sd use case v iew obj: Webform StoreOwner obj: Business obj: DataAccess

ViewProfile()

GetProfileData()

ExecuteSelectQuery()

ExecuteSelectQuerySuccessfully()

Figure 17 View Profile

E-Store

44

13.13

View Contact Us
sd sd use case v iew obj: Webform StoreOwner obj: Business obj: DataAccess

ViewContactUs()

GetContactData()

ExecuteSelectQuery()

ExecuteSelectQuerySuccessfully()

Figure 18 View Contact Us

14. ACTIVITY DIAGRAM

14.1 AddProductInfo

Figure 19AddProductInfo

E-Store

45

14.2

Login

Figure 20 Login

14.3

Search Product

Figure 21 Search Product

E-Store

46

14.4

Signup

Figure 22 Signup

14.5

Update Customer Profile

Figure 23 Update Customer Profile

E-Store

47

15.

8 Questions

15.1 Q#1 Prepare a Vision Document and scope document for your project and build a WBS for your project down to level 3.

Work Breakdown Structure

E-Store

48

15.2 Q 2 Identify the stakeholders for the system. Who or what are the relevant sources of requirements for this system? Ans: Stakeholders description is given on page#5 and the point no 3 in Vision Document. 15.3 Q 3 Choose one or more of the requirements elicitation techniques you have studied (Interviewing, brainstorm, workshop, scenarios, reuse, etc.) Which would be suitable for eliciting requirements for your project and explain the reasons why you select/not select a specific technique?
Ans: The Best requirement approach for this system is interviewing for each stakeholder of the

system. Reason to select interviewing approach that this technique provides us complete system need of individual stakeholder requirements. 15.4 Q4 Can you identify any conflicts or unresolved issues? Are there any ambiguous, duplicated or missing requirements? Negotiate to resolve any disagreements. Answer: No 15.5 Q5 Comment on how your requirements elicitation techniques impacted on analysis? Did you have all the information you needed? Was it easy or difficult to retrace and resolve issues? Answer: Requirements elicitation techniques are impact on analysis because if we dont use requirements elicitation techniques then the analysis cant be done so easily. Almost we have all the information we needed by using interviewing elicitation techniques. Thats not easy to retrace and resolve by using other elicitation techniques. Our technique is design to facilitate literal thinking people. Using this technique all the ideas are welcome and nothing is rejected.

15.6 Q6 Document the requirements in a proper way (structured natural language, requirements description language, graphical notation, mathematical specifications, etc.). You may think about using requirements tools to do the task Answer: Requirements are documented in a proper way using the structural language.

E-Store

49

15.7 Q7 Check the requirements document and make a list of items in the specification that require clarification and revision. Answer: We have checked the requirement document in specification that requires clarification and revision. 15.8 Q8 Write a test case for one or more of the requirements. Make a note of any problems. Answer:

Test Cases
Test Case 1. Verification of Login Fields Test Case ID: 01 Test Date: 24-May-2012 Reviewed by : Testing Team leader Test Engineer: Jamal Ahmad Test case version: ver:1.0 Use Case Reference(s) N/A

Objective: Verify that none of the fields remain empty Product/Version/Module Environment: The user is currently using Microsoft Windows XP SP2

Pre-Requisite: User must know the input of login form. Step No. Execution Description Submit a form with a number of fields remaining empty Procedure Result Error message displayed indicting the missed fields

Comments: The test passed successfully Passed o Failed o Not Executed

E-Store

50

Test Case 2. Verify Insert New Product Test Case ID: 02 Test Date: 24-May-2012 Reviewed by : Testing Team leader Test Engineer: Murad Ali Test case version: ver:1.0 Use Case Reference(s) N/A

Objective: To check insert information about a new Product. Product/Version/Module Environment: The user is currently using Microsoft Windows XP SP2

Pre-Requisite: Administrator must be login to the system. Step No. Execution Description Submit a form containing required product information. Procedure Result Product entered Successfully.

Comments: The test passed successfully Passed o Failed o Not Executed

E-Store

51