Process Model For The Jewellery Store Information Technology Essay
Completing an assignment successfully is a hard task for a student. First time I have completed a System Analysis And Design assignment. I have been great pleasure for completing this assignment. I have gathered sufficient knowledge and experience when preparing this assignment. But my teacher Mr. singh made this easy for me. During discussions on assignment he explained everything step-by-step. It’s a pleasure to acknowledge him for his contribution. I thank him for his encouragement, patience, and support.
I am also grateful to the teachers who taught me the other subjects. Knowledge I acquired from them was very useful for this assignment.
I am privileged to work with my friendly and helpful classmates. I got many useful tips and ideas from them. They deserve my heartiest thanks.
I thank London college of business & computing and its Management for the effort to provide the best education possible. Finally I am grateful to my family members for their support and encouragement to me.
Surely, all credits goes to the Almighty Allah.
Table Of Content
Task 1…………………………………………………………………Page 5
Introduction/Context Diagram……………………………………….Page 6
Data Flow Diagram……………………………………………………………Page 7
Conclusion………………………………………………………………………..Page 9
Task 2…………………………………………………………………Page 10
Conclusion/ Entity Relationship Diagram …….………………Page 11
Attribute…………………………………………………………………………Page 12
Introduction……………………………………………………………………Page 13
Task 3………………………………………………………………Page 14
Introduction / Entity Life History…………………………Page 15
Task 4………………………………………………………………Page16
Introduction/Normalisation…………………………………Page 17
Optimisation/Data dictionary………………………………..Page 21
Conclusion………………………………………………………………Page 25
Task5…………………………………………………………………Page26
Introduction……………………………………………………………Page 27
Task 6 ………………………………………………………………Page 31
Report……………………………………………………………………Page32
TASK ONE
Question of task one:
Create a process model for the jewellery store system comprising:
a) A Context Diagram of the jewellery store system.
b) A statement of the aims and objectives of the jewellery store system.
c) A Data Flow Diagram for the jewellery store system including:
• Process descriptions
• Dataflow descriptions
• Data store contents
• External entity definitions
Introduction:
In this task I have to create a process model of the jewellery store system comprising a context diagram, a statement of the aims and objectives of the jewellery store system and a data flow diagram for the store.
a) Context diagram:
The context diagram of the jewellery store will describe the whole activities and functionality of the system. This diagram has given below:
Figure: Context diagram of the jewellery store
b) Aims and objectives of the jewellery store system:
The overall aim is to provide a computerised and convenient means of running all the activities the jewellery store is engaged in.
The aims and objectives of the system include the following;
To provide a computerised means for member registrations.
The system should provide a central database for search jewellery item.
A process to Organise for customer able to search by category.
The system should provide for an easy means to keep record all item.
A process for provide for an easy means to keep record number sold, money received.
c) Data Flow Diagram:
Data flow diagram shows that how the system specifically works with their staff and external entities. It also shows how the data stores in the database.
The data flow diagram with the process description, data flow description, data store contents and external entities definitions have given below:
Figure: Data Flow Diagram of jewellery store
Conclusion:
To finish this task I got help from my subject teacher and my friends. I also got some help from System Analysis and Design book. After finishing this task now I am able to go to the next task of the assignment.
TASK TWO
Question of task two:
Create a data model detailing the data structure required to support the information and process requirements of the jewellery store system including:
• An Entity Relationship Diagram for the system.
• Entity descriptions for all entities in the diagram.
• Appropriate attributes for all entities including primary and foreign keys.
• Relationships detailing optionality and degree of relationships between entities.
Introduction:
In task two I have instructed to create a data model detailing the data structure required to support the information and process requirements of the jewellery store system including ERD, entity descriptions, and appropriate attribute for all entities with detailing relationships optionality, and degree of relationships between entities.
Entity Relationship Diagram:
The entities of the jewellery store are:
Jewellery Info
Category Info
Stock Info
Sales Info
Sales Invoice
Sales Order Info
Invoice Outward
Customer Info
Staff Info
Category Info
Stock Info
Sales Order Info
Sales Info
Customer Info
Sales Invoice
Staff Info
Jewellery Info
Invoice Outward
Figure: E-R-D of jewellery store
Attribute:
Attributes of the entities are given below:
____________ = Primary Key
* = Foreign Key
Jewellery Info:
ID
Item_Name
Weight
Unti_Price
Category_ID *
Category Info:
Category_ID
Category_Name
Stock Info:
Jwellery_ID
Quantity
Customer Info:
ID
Name
Address
Contact_Number
Staff Info:
ID
Name
Address
Contact_Number
Designation
Sales Info:
Jewellery_ID *
Sales _Invoice_No *
Unit_Price
Quantity
Total_Price
Commission
Net_Price
Sales Invoice Info:
Sales_Invoice_No
Date
Time
Sub_Total
Grand_Total
Staff_ID *
Sales Order Info:
Invoice_Outward_No *
Jewellery_ID *
Unit_Price
Quantity
Total_Price
Commission
Net_Price
Invoice_Outward_Info:
Invoice_Outward_No
Date
Time
Sub_Total
Grand_Total
Customer_ID *
Staff_ID *
Conclusion:
To finish this task I got help from my subject teacher and my friends. I also got some help from System Analysis and Design book. After finishing this task now I am able to go to the next task of the assignment.
TASK THREE
Question of task three:
Create an Entity Life History for a jewellery item.
Introduction:
In this task I have to create an Entity Life History for a jewellery item.
Entity Life History:
Entity life history describes the lifetime of an entity from creation to deletion. The ELH for a jewellery item are given below:
Figure: Entity Life History of a Jewellery Item
TASK FOUR
Question of task four:
Create a database design for the jewellery store system including:
• A set of fully normalized tables showing the normalization process for each.
• Data Dictionary entries for all items included in the database design.
Introduction:
In this task I have to design a database for the jewellery store system including a set of fully normalized tables showing the normalization process for each and data dictionary entries for all items included in the database design.
Normalisation:
Gathering data:
Jewellery_ID
Item_Name
Weight
Unti_Price
Category_ID
Category_Name
Stock_Quantity
Customer_ID
Customer_Name
Customer_Address
Customer_Contact_Number
Staff_ID
Staff_Name
Staff_Address
Staff_Contact_Number
Staff_Designation
Sales _Invoice_No
S_Date
S_Time
Sales_Grand_Total
Invoice_Outward_No
O_Date
O_Time
Order_Grand_Total
Unit_Price
Sales_Quantity
S_Total_Price
S_Commission S_Net_Price
Order_Quantity
O_Total_Price
O_Commission
O_Net_Price
Choosing a key:
Jewellery_ID
Convert to First Normal Form (Remove repeating group of data):
JEWELLERY
Jewellery_ID (PK)
Item_Name
Weight
Unti_Price
Category_ID
Category_Name
Stock_Quantity
Customer_ID
Customer_Name
Customer_Address
Customer_Contact_Number
Staff_ID
Staff_Name
Staff_Address
Staff_Contact_Number
Staff_Designation
Sales _Invoice_No
S_Date
S_Time
Sales_Grand_Total
Invoice_Outward_No
O_Date
O_Time
Order_Grand_Total
SALES INFO
Jewellery_ID (PK)
Sales _Invoice_No (PK)
Unit_Price
Sales_Quantity
S_Total_Price
S_Commission S_Net_Price
SALES ORDER INFO
Jewellery_ID (PK)
Invoice_Outward_No (PK)
Unit_Price
Order_Quantity
O_Total_Price
O_Commission
O_Net_Price
Convert to Second Normal Form (Remove partial key dependency):
JEWELLERY
Jewellery_ID (PK)
Item_Name
Weight
Unti_Price
Category_ID
Category_Name
Stock_Quantity
Customer_ID
Customer_Name
Customer_Address
Customer_Contact_Number
Staff_ID
Staff_Name
Staff_Address
Staff_Contact_Number
Staff_Designation
SALES INFO
Jewellery_ID (PK)
Sales _Invoice_No (PK)
Unit_Price
Sales_Quantity
S_Total_Price
S_Commission S_Net_Price
SALES INVOICE
Sales _Invoice_No (PK)
S_Date
S_Time
Sales_Grand_Total
Staff_ID
SALES ORDER INFO
Jewellery_ID (PK)
Invoice_Outward_No (PK)
Unit_Price
Order_Quantity
O_Total_Price
O_Commission
O_Net_Price
INVOICE OUTWARD
Invoice_Outward_No
O_Date
O_Time
Order_Grand_Total
Staff_ID
Customer_ID
Convert to third Normal Form (Remove non key dependency):
JEWELLERY
Jewellery_ID (PK)
Item_Name
Weight
Unti_Price
Category_ID (FK)
CATEGORY
Category_ID (PK)
Category_Name
STOCK INFO
Jewellery_ID (PK)
Stock_Quantity
CUSTOMER INFO
Customer_ID (PK)
Customer_Name
Customer_Address
Customer_Contact_Number
STAFF INFO
Staff_ID (PK)
Staff_Name
Staff_Address
Staff_Contact_Number
Staff_Designation
SALES INFO
PK Jewellery_ID (FK)
Sales _Invoice_No (FK)
Unit_Price
Sales_Quantity
S_Total_Price
S_Commission S_Net_Price
SALES INVOICE
Sales _Invoice_No (PK)
S_Date
S_Time
Sales_Grand_Total
Staff_ID (FK)
SALES ORDER INFO
Jewellery_ID (PK)
Invoice_Outward_No (PK)
Unit_Price
Order_Quantity
O_Total_Price
O_Commission
O_Net_Price
INVOICE OUTWARD
Invoice_Outward_No
O_Date
O_Time
Order_Grand_Total
Staff_ID (FK)
Customer_ID (FK)
Optimisation:
Category Info
Stock Info
Sales Order Info
Sales Info
Customer Info
Sales Invoice
Staff Info
Jewellery Info
Invoice Outward
Data Dictionary:
Table name: Jewellery_Info
Serial No
Attributes
Field size
Data type
Key Definition
Validation range
Validation rule
01
Jewellery_ID
10
Number
Primary key
————–
Not null, unique
02
Item_Name
30
Text
————–
————–
Null, duplicate
03
Weight
35
Text
————–
————–
Null, duplicate
04
Unit_Price
15
Number
————–
————–
Null, duplicate
05
Category_ID
10
Number
Foreign key
————–
Null, duplicate
Table name: Category_Info
Serial No
Attributes
Field size
Data type
Key Definition
Validation range
Validation rule
01
Category_ID
10
Number
Primary key
————–
Not null, unique
02
Category_Name
30
Text
————–
————–
Null, duplicate
Table name: Stock_Info
Serial No
Attributes
Field size
Data type
Key Definition
Validation range
Validation rule
01
Jewellery_ID
10
Number
Primary key
————–
Not null, unique
02
Quantity
10
Number
————–
————–
Null, duplicate
Table name: Customer_Info
Serial No
Attributes
Field size
Data type
Key Definition
Validation range
Validation rule
01
ID
10
Number
Primary key
————-
Not null, unique
02
Name
30
Text
————-
————-
Not null, duplicate
03
Address
8
Text
————-
————-
Not null, duplicate
04
Contact_Number
10
Number
————-
————-
Not null, duplicate
Table name: Staff_Info
Serial No
Attributes
Field size
Data type
Key Definition
Validation range
Validation rule
01
ID
10
Number
Primary key
————–
Not null, unique
02
Name
30
Number
————-
————–
————–
03
Address
25
Text
————-
————-
————-
04
Contact_Number
15
Number
————-
————-
————-
05
Designation
15
Text
————-
————-
————-
Table name: Sales_Info
Serial No
Attributes
Field size
Data type
Key Definition
Validation range
Validation rule
01
Sales_Invoice_No
10
Number
Primary key
————-
Not null, unique
02
Jewellery_ID
10
Number
Primary key
————-
Not null, unique
03
Unit_Price
15
Currency
————-
————-
Not null, duplicate
04
Quantity
10
Number
————-
————-
Not null, duplicate
05
Total_Price
06
Commission
5
Currency
————-
————-
Not null, duplicate
07
Net_Price
10
Currency
————-
————-
Not null, duplicate
Table name: Sales_Invoice_Info
Serial No
Attributes
Field size
Data type
Key Definition
Validation range
Validation rule
01
Sales_Invoice_No
10
Number
Primary key
————-
Not null, unique
02
S_Date
10
Date/time
————-
2000-2020
Not null, duplicate
03
S_Time
Date/time
————-
————-
Not null
04
Sales_Grand_Total
8
Currency
————-
————-
————-
05
Staff_ID
10
Currency
Foreign key
————-
————-
Table name: Sales_Order_Info
Serial No
Attributes
Field size
Data type
Key Definition
Validation range
Validation rule
01
Invoice_Outward_No
10
Number
Primary key
————-
Not null, unique
02
Jewellery_ID
10
Number
Primary key
————-
Not null, unique
03
Unit_Price
15
Currency
04
Quantity
10
Number
————
————-
————-
05
Total_Price
10
Currency
————
————-
————-
06
Commission
5
Currency
————
————-
————-
07
Net_Price
10
Currency
————
————-
————-
Table name: Invoice_Outward_Info
Serial No
Attributes
Field size
Data type
Key Definition
Validation range
Validation rule
01
Invoice_Outward_No
10
Number
Primary key
————-
Not null, unique
02
S_Date
10
Date/time
————-
2000-2020
Not null, duplicate
03
S_Time
Date/time
————-
————-
Not null
04
Sales_Grand_Total
8
Currency
————-
————-
————-
05
Staff_ID
10
Number
Foreign key
————-
————-
06
Customer_ID
10
Number
Foreign key
————-
————-
Conclusion:
To finish this task I got help from my subject teacher and my friends. I also got some help from System Analysis and Design book. After finishing this task now I am able to go to the next task of the assignment.
TASK FIVE
Question of task five:
Create a prototype user interface for the jewellery store system including, as a minimum, the following functions:
• Searching for an item of jewellery.
• Processing the purchase of an item of jewellery.
• Adding a new item of jewellery to the system.
Print screenshots of the user interface for the functions above. Where necessary, describe where validation rules are applied and the reasons for this.
Introduction:
Searching for a jewellery item:
Processing the purchase of an item of jewellery.
Adding a new item of jewellery to the system.
TASK SIX
It was my first System Analysis And Design assignment. I have done this assignment by so hard work. I have tried my best to do all the tasks. There may have a lot of mistakes. It is understandable that as a 2nd year (IADCS) student our range of knowledge is limited. I Work with this limited knowledge. But the way of assignment I have learnt here help me on the real life. I am grateful to NCC for providing me such kind of assignment. I shall always try to implement this knowledge
Order Now