Chemist Service Group Information Systems Development

Verified

Added on  2023/06/04

|15
|2239
|248
AI Summary
This domain analysis covers the requirements gathering, domain analysis, behavioural modelling, structural and dynamic modelling for Chemist Service Group Information Systems Development. It includes the owner's view for the system, users of the system, domain definitions and scope, use case summary for product sales and inventory management subsystems, use case template for a use case relating to a customer ordering, class diagram for the product sale subsystem, and sequence diagram for the process of a customer selecting products.

Contribute Materials

Your contribution can guide someone’s learning journey. Share your documents today.
Document Page
1Domain Analysis
Chemist Service Group Information Systems Development
CHEMIST SERVICE GROUP INFORMATION SYSTEMS DEVELOPMENT
By (Student names)
[Course Name]
[Lecture Name]
[University Name]
[City where the university is located]
[Date]

Secure Best Marks with AI Grader

Need help grading? Try our AI Grader for instant feedback on your assignments.
Document Page
2Domain Analysis
Chemist Service Group Information Systems Development
Contents
1 Requirements Gathering...........................................................................................................3
1.1 Owner’s view for the system.............................................................................................3
1.2 Users of the system...........................................................................................................4
1.2.1 Business users............................................................................................................4
1.2.2 IS users.......................................................................................................................4
2 Domain Analysis.....................................................................................................................4
2.1 Domain definitions and scope...........................................................................................4
2.2 Identify the domain concepts............................................................................................5
3 Behavioural Modelling............................................................................................................6
3.1 Stakeholders of the whole system.....................................................................................6
3.2 Use case summary for product sales and Inventory Management subsystems................7
3.3 Use case template for a use case relating to a customer ordering.....................................8
3.4 Use case diagram for the Product sale subsystem.............................................................8
3.5 Activity diagram for the Product sale...............................................................................9
4 Structural and Dynamic Modelling.......................................................................................11
4.1 Classes for the product sales and Inventory Management subsystems..........................11
4.2 Class diagram for the product sale subsystem................................................................11
4.3 Sequence diagram for the process of a customer selecting products..............................12
5 Reference...............................................................................................................................14
Document Page
3Domain Analysis
Chemist Service Group Information Systems Development
1 Requirements Gathering
1.1 Owner’s view for the system
The owner’s views are the high-level processes and they represent the various businesses factors
for successful business transactions. These business functions involves the processes that are
related in one way or another and they are able to support the various businesses processes which
can be split into smaller processes that perform some specific tasks (Wixom, 2016).
Assumptions made:
i. Various branches have sales stores.
ii. There is one manager managing each sales store.
iii. Every sales manager can access the local sales store inventory database.
iv. Every manager can get the sales store’s product balances.
v. Every sales store manager is able to place products order from the main central stores.
vi. Every sales store manager is able to update the local store database for any new
received stock.
The following are the proposed system owner views.
i. System should allow creation of users accounts online.
ii. System should allow the store managers checking the balance of the store products.
iii. System should allow the ordering of new stock from the central warehouse by the
store managers.
iv. System should allow the updating of the new products stock delivered from the
central warehouse.
v. System should allow the online ordering of the products by the customers.
vi. System should allow the customers to do the online payments of the ordered products.
vii. System should allow the managers to view customer’s behaviours and the various
products performances.
viii. System should allow the store managers to add new introduced products.
ix. System should enable the managers and marketers to make product’s promotion.
x. The system should enable the customers to register for membership in order to get
promotions and discounts as loyal customers.
Document Page
4Domain Analysis
Chemist Service Group Information Systems Development
1.2 Users of the system
The proposed system will be having various users and these will be either business or the
information system users as discussed below.
1.2.1 Business users
The following are the business system users.
i. Products Supplier.
ii. Store Managers.
iii. Customers.
iv. Store employees.
v. Store sales persons.
vi. Promotions team.
vii. Marketing team.
1.2.2 IS users
Below are the information system users.
i. Information technology professions.
ii. Systems developers.
iii. System programmers.
iv. System analysts.
v. System architects.
vi. Database developers.
vii. Payment service providers.
2 Domain Analysis
2.1 Domain definitions and scope
Chemist Services
Domain Definitions & Scope
Domain Scope Outline
User’s
registrations
The system users including the customers and the managers registration is
done to provide the unique username and password that will be used to
access the system.

Secure Best Marks with AI Grader

Need help grading? Try our AI Grader for instant feedback on your assignments.
Document Page
5Domain Analysis
Chemist Service Group Information Systems Development
User’s logins The system users enter the usernames and passwords in order to perform
some transactions.
Manager’s
product balance
check-up
The store-manager requires login the system to get the balance left for the
various products.
.
Manager’s
product
ordering
The store-manager places order for some products whose balance is very
low that the minimum balance.
Manager’s new
product stock
updating
The store-manager gets the products from the central warehouse and updates
the new products balance in the system.
Manager’s
customer’s
behaviors
analysis
The store-manager login the system in order to analyze the behaviors of
customers and the most selling and least selling product.
Customer’s
memberships
registrations
The customers who are regular buyers are able to register as members which
allows them to benefit from the promotions and discounts.
Customer’s
products
ordering
The customer login the system then orders the required products after
selecting and adding them to the shopping-cart.
Customers
credit-card
payments
The customer does the payments for the items selected using the credit card.
2.2 Identify the domain concepts
Chemist services
Document Page
6Domain Analysis
Chemist Service Group Information Systems Development
Domain Dictionary
Name Type Description
Register on website-
system
processes The system users provide the usernames and
passwords on the website registration forms.
Log-in website-system Objects The system users provides the registered usernames
and passwords in order to sign in the system
Check inventory’s
products balances.
Functions The store managers login to check the products
balances in the system inventory.
Place Order for new
products
Roles Store managers access the system through login and
place order for the more products from the central
warehouse.
Updating products
received
functions, The store manager then updates the received products
in the system.
Booking the products. Roles The customer accesses the system through login and
books some products which are added in shopping-
cart.
Paying for the product business
rules
The customer pays for the ordered products which
are added in the shopping cart.
Registering customer’s
membership
Processes The frequent customers register for membership and
thus they get discounts and offers.
Analyzing customer’s
behavior.
Roles The managers login the system to get the behaviors
of the customers in the buying patterns and the thus
are able to make good decisions.
Introducing new products Processes The store managers login the system to insert the new
products details for the customers accessibility.
Adding the classified
product
objects The store managers login the system to add classified
products like baby, health products.
Document Page
7Domain Analysis
Chemist Service Group Information Systems Development
3 Behavioural Modelling
3.1 Stakeholders of the whole system
The proposed system will be used by various users who include the following:
Chemist Services
Stakeholders & Actors
Name Description
Customers The customers login system to do booking or ordering and
making payments for products.
Store-managers. The manager login system for orders placement and updating
the new ordered products in the system.
Store-employees. The employees in the stores login to update the details of the
products sold to the customers.
Central warehouse managers. Warehouse manager login the system to identify any order
placed from the sales stores to deliver the ordered products.
Technical supports team. The technical-team offers support to the customers or staffs
on how to use system or offer maintenance.
System’s analysts The analysts analyze the requirements that need to be
implemented into the proposed system.
System’s programmer. The programming team to do the code part to implement the
system requirements features.
System’s designer. The designing team designs the system interfaces and
databases to be used in the system implementations.
Payment-platform vendors. These are service providers who offer the third party
platform for products payment.
(Singh,2016).
3.2 Use case summary for product sales and Inventory Management
subsystems Chemist Services

Paraphrase This Document

Need a fresh take? Get an instant paraphrase of this document with our AI Paraphraser
Document Page
8Domain Analysis
Chemist Service Group Information Systems Development
Use Case Summary
ID Name Description Actors
1 Users Registering in
system
All users of the system must have username
and password registration details to use the
system.
Customer, managers
2 Users sign in
system
The system users must enter username and
passwords and usernames to access the
system functionalities.
Customer, managers
3 Customers ordering
the product
After successful sign in the users select
items and order them by adding them to
shopping-cart.
Customers
4 Customers
receiving the
products
After the customer order the products
online they pay some delivery fees or pick
items from the store.
Customer
6 Checking products
balances.
The manager sign in system in order to
check the products balances.
Store-managers
7 Placing the products
orders.
After the successful login into system the
store manager places order of additional
products from the central warehouse.
Store-managers
8 Receiving products
ordered.
After the warehouse manager getting the
store manager orders he deliver the
products which are received by the store
manager.
Store-managers
9 Updating products
received
The store manager sign in system and make
update of all new products that were
received from the central warehouse.
Store-managers
3.3 Use case template for a use case relating to a customer ordering
Use Case: Customer ordering
Document Page
9Domain Analysis
Users registering in system
PRODUCT SALE SUBSYSTEM USE
CASE DIAGRAM
Chemist Service Group Information Systems Development
ID: 3
Scope: The customer login the system and place order where he add
Items to shopping cart.
Priority: High
Summary: Customers sign in, select products, add to shopping-cart and
use credit card to pay.
Primary Actor: Customers
Supporting Actors: Store-employee who gives or deliver items to the customers
Stakeholders: Customers, store-manager and store-employees
Generalization: -
Include: Adding product to shopping-cart, paying using credit cards.
Extend: -
Precondition: Customers require a product.
Trigger: Customers sign in.
Normal Flow: Customer sign in, add product to shopping-cart and pay for
products through credit card.
Sub-Flows: Customer sign in, add products to shopping-cart and pay using
credit card.
Alternate Flow/ Exceptions: Customer visits the local store and buys the products.
Post-Condition: Customers get the product through delivery or picking from
store.
Non-Behavioral
Requirements:
Customer requires a product.
Open Issues: Customer pick product or pay for delivery.
Source: Customers
Author: Store-managers
Revision & Date 3/10/2018
3.4 Use case diagram for the Product sale subsystem
Document Page
10Domain Analysis
Users sign in system
Customers ordering the product
Customers receiving the products
Customers
Store-manager
Chemist Service Group Information Systems Development
(Laplante, 2013).
3.5 Activity diagram for the Product sale

Secure Best Marks with AI Grader

Need help grading? Try our AI Grader for instant feedback on your assignments.
Document Page
11Domain Analysis
Chemist Service Group Information Systems Development
(Karumanchi, 2012).
Document Page
12Domain Analysis
PRODUCT
Products_id
Product_name
Descriptions
Supplier_name
CUSTOMER
Customer_id
Full_name
Email_address
Telephone _no
SALE
Sale_id
Sales_date
Sales_Amount
Total_cost
Customer_id
Product_id
INVENTORY
Inventory_id
Units_available
Current_date
Product_id
Chemist Service Group Information Systems Development
4 Structural and Dynamic Modelling
4.1 Classes for the product sales and Inventory Management subsystems
Below are the classes in the product sales and inventory
i. Product
ii. Customers
iii. Sale
iv. Inventories
(Goyal, 2011).
4.2 Class diagram for the product sale subsystem
Document Page
13Domain Analysis
PRODUCTS
Product_id int(20)
Product_name varchar(150)
Descriptions varchar(150)
Supplier_name varchar(150)
CUSTOMER
Customer_id int(20)
Full_name varchar(150)
Email_address varchar(150)
Telephone_no int(20)
SALES
Sale_id int(20)
Sales_date Date
Sales_Amount int(20)
Total_cost int(20)
Customer_id int(20)
Product_id int(20)
Chemist Service Group Information Systems Development
(Gupta, 2015)

Paraphrase This Document

Need a fresh take? Get an instant paraphrase of this document with our AI Paraphraser
Document Page
14Domain Analysis
Chemist Service Group Information Systems Development
4.3 Sequence diagram for the process of a customer selecting products.
(Award, 2013)
Document Page
15Domain Analysis
Chemist Service Group Information Systems Development
5 Reference
Award,E.(2013) Systems Analysis and Design .3rd edn.Delhi:Galgotia Publications Pvt Ltd.
Gupta,B.(2015) Power System Analysis and Design.1st edn.New Delhi: S Chand & Company.
Goyal, A. (2011) systems Analysis and Design Paperback .2nd edn.INDIA:Prentice Hall India
Learning Private Limited.
Karumanchi,N.(2012) Peeling Design Patterns: For Beginners and Interviews.5th edn.New
York:CareerMonk Publications.
Laplante,P.(2013) Real-Time Systems Design and Analysis: Tools for the Practitioner.2nd
edn.New Jersey:Wiley.
Singh,B.(2016) Systems Analysis and Design.4th edn.Delhi:New Age International Private
Limited.
Wixom,D.(2016) Systems Analysis and Design.2nd edn. New Jersey: Wiley publishers.
1 out of 15
circle_padding
hide_on_mobile
zoom_out_icon
[object Object]

Your All-in-One AI-Powered Toolkit for Academic Success.

Available 24*7 on WhatsApp / Email

[object Object]