Stock Management System for Confectionery Items

Design Document
Version 1.0

Student ID: MC150401757

Group Id: S1902DE9EC (MC150401757)

Supervisor Name: Muhammad Tahir Jan

 Revision History

Date Version Description Author

(dd/mm/yyyy)

07/07/2019 1.0 Stock Management System for KASHIF KHAN

Confectionery Items for Pharmacy
design document includes ERD,
Class Diagram, Database Diagram,
Sequence Diagram, User interface
and Test Case

i
 Table of Contents

1. Introduction of Design Document..................................................................................................1

1.1 The SDD usually contains the following information:...........................................................1
2. Entity Relationship Diagram (ERD)..............................................................................................2
3. Activity Diagrams (Member).........................................................................................................3
4. Sequence Diagrams........................................................................................................................4
6 Class Diagram................................................................................................................................6
7. Interface Design.............................................................................................................................7
7.1 Splash Screen..........................................................................................................................7
7.2 Login.......................................................................................................................................8
7.4 Delete User..............................................................................................................................8
7.5 Employee................................................................................................................................9
8. Test Cases.....................................................................................................................................10

ii
1. Introduction of Design Document
A software design description (software design document or SDD) is a written description
of a software product, that a software designer writes in order to give a software development
team overall guidance to the architecture of the software project. An SDD usually
accompanies an architecture diagram with pointers to detailed feature specifications of
smaller pieces of the design. Practically, the description is required to coordinate a large team
under a single vision, needs to be a stable reference, and outline all parts of the software and
how they will work.

1.1 The SDD usually contains the following information:

1. The data design describes structures that reside within the software. Attributes and
relationships between data objects dictate the choice of data structures.
2. The architecture design uses information flowing characteristics, and maps them into the
program structure. The transformation mapping method is applied to exhibit distinct
boundaries between incoming and outgoing data. The data flow diagrams allocate control
input, processing and output along three separate modules.
3. The interface design describes internal and external program interfaces, as well as the design
of human interface. Internal and external interface designs are based on the information
obtained from the analysis model.
4. The procedural design describes structured programming concepts using graphical, tabular
and textual notations. These design mediums enable the designer to represent procedural
detail that facilitates translation to code. This blueprint for implementation forms the basis
for all subsequent software engineering work.

1
2. Entity Relationship Diagram (ERD)

Customer

Suppliers Sa
le
S
al Store
e

Purchas
e

Product

H
as

A
dd

Employee Product Type

2
3. Activity Diagrams (Member)

3
4. Sequence Diagrams

Inventory MS

4
5. Architecture Design Diagram

5
6 Class Diagram

6
7. Interface Design
User Interface (UI) Design focuses on anticipating what users might need to do and ensuring that
the interface has elements that are easy to access, understand, and use to facilitate those actions.
UI brings together concepts from interaction design, visual design, and information architecture.

7.1 Splash Screen

Figure: 7.1 Splash

7
7.2 Login

Figure 7.2 Login

7.4 Delete User

Figure 7.4 Delete User

8
7.5 Employee

Figure 7.5 Employee

9
8. Test Cases
Login Test Case
Test Case Title Login
Use Case Id 01
Description: Test case for user login.

Post Conditions:
1. Verify that the login screen is having option to enter username and password with
submit button and option of forgot password
2. Verify that user is able to login with valid username and password
3. Verify that user is not able to login with invalid username and password
4. Verify that validation message gets displayed in case user leaves username or password
field as blank
5. Verify that validation message is displayed in case user exceeds the character limit of
the user name and password fields
6. Verify that there is reset button to clear the field's text
7. Verify that the password is in encrypted form when entered
8. Verify that there is limit on the total number of unsuccessful attempts
9. For security point of view, in case of in correct credentials user is displayed the message
like "incorrect username or password" instead of exact message pointing at the field that
is incorrect. As message like "incorrect username" will aid hacker in bruteforcing the
fields one by one
10. Verify if the password can be copy-pasted or not
Test Result: Pass

Tested By: KASHIF KHAN

10
Change Password Test Case

Use Case Title User Change Password

Use Case Id Use Case 02
Description: User of the system attempts to Change Password.
Post Conditions:
1. Open the Application2. Click on the Change.
2. Password link3.
3. Check whether the Change password Page is loaded.
4. Check whether there are 3text fields for Old Password, New Password and Re-type
new password
Test Result: Pass

Tested By: KASHIF KHAN

Test Case Title Add Employee Record

Use Case Id Use Case 03
Description: Administrator of the system attempts to add new record of employee.
1. Check the behavior of form by not filling up any data into the form.
2. Check the by not filling up the required fields.
3. Check the behavior of form by adding random data in the text field.
4. Check the by not filling up the full name text field but by filling up rest of the other
fields.
5. Check the behavior of form by filling other text fields except address text fields.
6. Check the form by filling other text fields except phone number text field.
7. Check the form by filling other text fields except email text field.

Testing Full Name Field

1. Check the Full name text field without Prefix.

2. Check the Full name text field without adding First name.
3. Check the Full name text field without adding Last name.

Testing Address Field

1. Check if all the text fields in the address field are mandatory or not.

11
 2. Check the city text field by adding numbers into it.
3. Check the city text field by adding no data.
4. Check the state text field by adding no data.
5. Check the state text field by adding numbers into it.

Testing Email Field

1. Check the Email text field that has Email address without @ symbol.
2. Check the Email text field that has random string instead of real email.
3. Check the Email text field that has @ symbol written in words.
4. Check the Email text field that has missing dot in the email address.
5. Check the Email text field as “name@gmail”
6. Check the Email text field as “@gmail”
7. Check the Email text field as “[email protected]”
8. Check the Email text field as “[email protected]”

9. Check the Email text field as “name.. @gmail.com”

Test Result: Pass

Tested By: KASHIF KHAN

Test Case Title Delete Record

Test Case Id Use Case 04
Description: Test case for record deletion
Test Scenario
1. You check the buttons are enabled.
2. Check the buttons when its enabled and when its disabled
3. After click the button, page responding or not.
4. When u have click the delete button, record should be deleted.
Test Result: Pass

Tested By: KASHIF KHAN

12
Test Case Title Update Record
Test Case Id 05
Description: Test cases for record Updation.

Test Case Scenario

1. Modify value should be updated when u have click this button.
2. After updation user view updated values.
Test Cases Result: Pass

Tester Name: KASHIF KHAN

13