System Analysis and design

College of Computing and Informatics

CS352

Project Report
Deadline: Wednesday 04/23/2025@
23:59
[Total Mark for
this Project is 14]
Student Details:

CRN:

Name(leader): Renad
Abdullah Buhaimed
Name: Norah Saad Alharbi
Name: Norah Omar Alomar
Name:

ID: S220046965
ID: S230004116
ID: S230045867
ID:

Instructions:
•

You must submit two separate copies (one Word file and one PDF file) using the Assignment Template on
Blackboard via the allocated folder. These files must not be in compressed format.

•
•

It is your responsibility to check and make sure that you have uploaded both the correct files.

•
•

Email submission will not be accepted.

•
•

You must use this template, failing which will result in zero mark.

•
•
•

Late submission will result in ZERO mark.

Zero mark will be given if you try to bypass the SafeAssign (e.g., misspell words, remove spaces between
words, hide characters, use different character sets, convert text into image or languages other than English
or any kind of manipulation).
You are advised to make your work clear and well-presented; marks may be reduced for poor presentation.
This includes filling your information on the cover page.
You MUST show all your work, and text must not be converted into an image, unless specified otherwise by
the question.
The work should be your own, copying from students or other resources will result in ZERO mark.
Use Times New Roman font for all your answers.

Restricted – ‫مقيد‬

Pg. 01

Description and Instructions
•

Each group has up to 2-3 students.

•

Each group should choose a topic for an Information system.

•

The chosen topic and students’ names in each group must be sent to the course instructor by April 23, 2025

•

Students must use reputable sources and at least 3 scientific papers in their research.

•

Use the following fonts.
o

Times New Roman font with font size of 12 for paragraphs

o

Times New Roman font with font size of 14 bold for headings

•

The line spacing should be single.

•

Avoid grammatical mistakes.

•

Each group will select a group Leader who will submit the paper via Blackboard.

•

The group leader will submit the MS Word and PDF format both. These files must not be in compressed format.

•

Total Marks = 14

The deliverables of the project should include A report with the following sections:
o

Planning Phase: (5 Marks)

o

Analysis Phase: (5 Marks)

o

Design Phase: (4 Marks)

As a system analyst, you are requested to develop an Information System by performing
the first three phases of SDLC (planning, analysis and design). You need to apply what
you have learned in the class and to participate in the team project work.
•

You have received a System Service Request (SSR) from a client and you need to
apply the planning, analysis and design phases.

•

In this project, the first step is to present the SSR received (select a scenario of your
choice). Then, you need to prepare the main deliverables of the planning phase:
Project Scope Statement (PSS) and the Baseline Project Plan (BPP).
Note that: all sections of these documents should be included (for example the
system description, the feasibility assessment, and the management issues in
the BPP).

•

Restricted – ‫مقيد‬

Finally, you need to start the analysis and designing steps by providing the Data Flow
Diagram (DFD) and the Entity Relation Diagram (ERD) of the Information System to
be developed.

Pg. 01
Deliverables
This project should follow the main steps of the first three phases of the SDLC
(phase 1, 2 and 3). Detailed description should be included in each phase.

Restricted – ‫مقيد‬

Pg. 01

Learning
Outcome(s):

Planning Phase

5 Marks

Under this section, include the following:
CLO3: Recognize
• The System Service Request. (2.5 marks)
different
• The Project Scope Statement. (1 mark)
concepts,
• The Baseline Project Plan. (1.5 marks)
principles, and
software
modelling
1.1 System Service Request (SSR)
techniques.
Customer: Al-Salam Food Store
Summary of the Request:
The creation of a Smart Inventory Management System (SIMS) has been formally requested by
the proprietor of Al-Salam Grocery Store. Inventory is tracked by the store manually using tools
like spreadsheets and paper logs. Significant issues like inaccurate data entry, low stock visibility,
and ineffective replenishment have resulted from this. To provide real-time inventory updates,
low-stock notifications, stock reports, and secure access for managers and employees, the
customer has asked for a contemporary, intelligent, and automated solution.
Business Need:
•
•
•
•

Visibility of stocks in real-time
Restocking alerts that are automated
Easy-to-use system for employees with little training
Monitoring and reporting historical data for planning and analysis.

Expected Benefits:
•
•
•
•

Restricted – ‫مقيد‬

Minimize inventory mistakes
Keep inventory levels up to date to increase client satisfaction.
Avoid wasting time on manual updates.
Make better decisions by using insights derived from data.

Pg. 01
1.2 Project Scope Statement (PSS)
Project Objective:
To provide Al-Salam Grocery Store with a web-based inventory management system that is
scalable, safe, and responsive so that it can automate alarms, track stock levels, and produce
informative reports.
Scope Includes:
Using CRUD (Create, Read, Update, Delete) activities to track inventory
• Access control by role (admin/staff)
• Alert mechanism for low stock
• reporting on stocks (daily, weekly, monthly)
• Change log for inventory
• Out of Scope:
• POS (point-of-sale) system integration
• Analytics and forecasting powered by AI
Constraints:
• Non-technical employees must be able to use the system easily.
• The system should support basic mobile browser usage.

1.3 Baseline Project Plan (BPP)
System Description: A centralized dashboard for inventory management will be made
available by the system. It will be able to generate custom reports, add new items, update
stock, and get low-stock notifications. Web-based, the interface will require secure logins
for various user roles.
Feasibility Assessment:
Technical Feasibility: The group is qualified in web technologies (Flask, MySQL,
React.js). Cloud-based deployment will be done with Heroku or Render.
Economic Feasibility: Open-source tools will be used in the project. Only optional
domain and hosting fees apply.
Operational Feasibility: Real users will be used to test the system. Staff members will
receive basic training.
Management Issues:
1. Frequent monitoring of progress and weekly stand-ups
2. Risks include technological obstacles, requirements change, and scope creep.
3. GitHub version control and backup

Restricted – ‫مقيد‬

Pg. 01

Learning
Outcome(s):

Analysis Phase

CLO2: Describe
the role of
analysis and
design in software
development.

Under this section, include the following:
•
•

5 Marks

List the functional and nonfunctional business requirements for the
system. (2 mark)
Create the complete DFD (Data Flow Diagram) for your own system.
(3 marks)

2.1 Functional and Nonfunctional Requirements
CLO3: Recognize
different
concepts,
principles, and
software
modelling
techniques.

Functional Requirements:
•
•
•
•
•

Users can safely view the dashboard after logging in.
Admins have control over both users and categories.
Inventory items are viewable, editable, and delectable by users.
Real-time warnings are generated by the system when the stock falls below the threshold.
Inventory reports are produced using filters (date, category, etc.).

Nonfunctional Requirements:
• The system (desktop and mobile) has to be responsive.
• Up to 10,000 inventory items must be handled effectively.
• Should react in two seconds to user input.
• All information needs to be safely kept and regularly backed up.
System availability needs to be at least 99%

Restricted – ‫مقيد‬

Pg. 01
2.2 Data Flow Diagram (DFD)
The Data Flow Diagram (Level 0 and Level 1) includes the following main processes:
Processes:
•
•
•
•

1.0User Management: Manages role assignment, login, and logout.
2.0 Inventory Management: CRUD procedures for goods
3.0 Notification Management: Creates and distributes alerts for low stock.
4.0 Reporting: Generates personalized inventory reports

External Entities:
•
•

Admin
Store Staff

Data Stores:
•
Users
•
Products
•
Categories
•
Logs
•
Alerts
[Insert DFD diagrams here]

Restricted – ‫مقيد‬

Pg. 01

Learning
Outcome(s):

Design Phase

CLO2: Describe
the role of
analysis and
design in software
development.

Under this section, include the following:
•

4 Marks

Use the ERD (Entity Relationship Diagram) to design the database of
the information system. (4 marks)

3.1 Entity Relationship Diagram (ERD)
The ERD includes the following key entities and relationships:
CLO3: Recognize
different
concepts,
principles, and
software
modelling
techniques.

•
•
•
•
•

Users (role, password, username, name, and user_id)
Product_id, name, description, quantity, reorder_level, and category_id are among the
items.
Categories (description, name, and category_id)
Logs for inventory (log_id, product_id, user_id, action, quantity_changed, timestamp)
Alerts: triggered_on, resolved, product_id, and alert_id

Relationships:
• There can be a lot of products in one category.
• Many inventory operations can be carried out by a single user.
• Several warnings can be generated by a single product.
[Insert ERD diagram here

Restricted – ‫مقيد‬

Pg. 01

Restricted – ‫مقيد‬

Pg. 01

Restricted – ‫مقيد‬

Purchase answer to see full
attachment