2/8/25

MOIS320101 Fall 2024

MGMT Info Systems and Database
Semester Project Briefing

Prof Galal H. Galal-Edeen

Professor of Information Systems Engineering,
Department of Management

[DRAFTv9]

• The Semester Project requires working towards the realization of the

chosen/assigned database project.
• The project has a lot of communicational aspects including report
writing and a presentation.
• The deliverables of the project are used as milestones in the project
life-cycle.
• Most deliverables are preliminary or part project reports/presentations
• Preferably students should use MS-Word to write their reports.
• Each group will select a project from those listed in the slides after.
• A brief project description is given for each (example) project, which
you need to expand & express in a diagrammatic form.
• Your goal is to design and build an appropriate database.
Introduction • The project descriptions are intentionally short and simple so that
you can provide your own assumptions for the mini-world of the
project. State any assumptions you make very clearly.
• It also gives you the experience of going through a “requirements
analysis” exercise. You are required to do a (limited) amount of research
of similar systems or those you might be familiar with, to serve as sources
of requirements. Group discussions and simulations would also be a good
source of useful database and reporting requirements. Group meetings and
discussions should be logged (with dates).
• The projects are also fairly close to real-world business enterprises.
• Hence, most of us are likely to have some idea of how these run and
the kind of information they would need to generate. See the note on using
Generative AI to generate requirements ideas.
2

1
 2/8/25

• Phase 1
• Group names
• Working project title & preliminary Purpose/ Scope Statement.
Deliverables • Preliminary context diagram (one type of DFDs).
• Phase 2
• Project description & Scope. This is an initial, but reasonably well-thought out and
refined, a one-page description of your project. Provide enough details about the scope of
your project. A revised context-diagrams may be added. A rough idea of scope is that an
acceptable project is likely to yield 5-10 or so relations (tables) in the final design.
• Proposed Functions. What reporting functions should the system have to satisfy its user
requirements? these could include main (at least 3 each) queries for all user types
• Entity-Relationship Diagram. Provide a complete data base design for your project
using the Entity-Relationship Model.
• Detailed business process descriptions. Provide a model of the main business processes
that your model should support (check BPMN if you have forgotten this!).
• Phase 3
• Relational Design. Provide a complete relational design for your project (the final
conceptual model mapped onto the target DB relations). Include designs for your user
views and reports as well.
• Database Implementation. Implement your database design with sample data and a
suitable user interface. Be ready to demonstrate how your system satisfies the user
reporting needs.
• In Phase 3 submission, you can upgrade the work you’ve done for the previous 2 phases.

Phase 1: Group Names, Scope and Context

Diagram

Describe Team Draw

Choose a working title List the names and e-mail A context diagram of the
and give an overall textual addresses of a max of 5 proposed system (note
description of purpose of members per group. that this is not final and
the system. Your can be upgraded in later
proposed system should phases).
serve the Manager plus at
least two types of users.

2
 2/8/25

Phase 2: Database Requirements and

Conceptual Design

Describe Explain Provide Draw Suggest

Describe the Explain why a Provide a Conceptual Suggest queries for
application, its database is needed description of the Database design: all user levels (at
detailed users and for this application system including: draw an Entity- least 3 for each).
expected output. and the benefits 1- the required Relationship
and drawbacks of functions Diagram for the
having a database application. Be sure
system. 2- Basic data to indicate the
entities and their assumptions and
attributes constraints of the
3- Relationships ER diagram.
linking the various
entities.

Phase 3: Database Design and Implementation

1. Implement and populate the tables in the RDBMS you choose.

2. Decide on the queries the users need.
3. Develop the queries and build an interface for them.
4. The queries should not be repetitive & must support the selected reports.
5. Develop the needed forms, and reports.
6. Provide sample runs on the implemented functionalities.
7. Be ready to provide a soft copy of all database files, forms, reports, etc. along with
snapshots and a simple manual to run the DB application.

3
 2/8/25

Phase 3 & Final Report

• The final report should incorporate changes suggested in phase 1 (e.g.,
adding certain queries, correcting problems in the ER design, etc.), plus
Phase 2.
• It should properly integrate all the pieces you’ve done in both phases.
• You are expected to provide scenarios about how managers (could be one or
more types) would use the database to generate reports.
• Be sure to submit electronic copies of all your project files together with the
report (MSWord) file to be uploaded to Canvas.
• Observe good document management discipline: Name your file properly,
indicating version number! All pages should be numbered!
• The final prototype maybe presented to a jury of the course instructor and
one of the Tas, alternatively, the groups maybe asked to record short videos
of the same.

A database system for a pharmacy.

A database system for a spare parts/ car service
shop.

DB Project A tourist excursion booking system.

A family database system

Ideas (feel Ma's kitchen

free to
A supermarket CRM
A system for event organisation.

suggest Educational course support

Museum or Gallery Gift Shop System.
your own) A DB for an application to save food.
A DB to receive reports of road traffic violations.
A system for receiving and distributing clothes
donations 8

4
 2/8/25

A Database
System for a
pharmacy
• Design a database system for managing the activities
of a pharmacy.
• You may for instance track information about
medications, patients, other products on sale, prices,
discounts and promotions, etc., ..etc.
• Show how this database will be used by at least two
different types of users (like pharmacist, manager,
suppliers).
• For example, the pharmacist may be able to update
the stock database whereas a supplier might be able
to check if an item is running low or selling fast to
decide whether to re-stock.
• Managers can generate reports about sales (possibly
grouped by weekdays, months etc.), returns and
exchanges, the the average sales by shift, etc..
• Show how this database will be used by at least 2
different types of users (buyers and sales staff) other
than the Manager.
9
This Photo by Unknown Author is licensed under CC BY-SA

A Database System for a

vehicle spare parts and/ or
servicing

• Design a database system for an organization that

sells vehicle spare parts and/ or vehicle servicing.
• This database could be used to keep track of stocks,
orders, clients, special offers and promotions.
• Vehicle keepers may register their contact details
and vehicle types so that the correct parts can be
ordered for them.
• It is important that the management gets reports of
items that are about to be sold out so that more can
be ordered on time.
• Show how this database will be used by at least 2
different types of users (buyers and sales staff)
other than the Manager.

10
This Photo by Unknown Author is licensed under CC BY-SA This Photo by Unknown Author is licensed under CC BY-NC

10

5
 2/8/25

A Tourist
excursions
bookings system

• Design a database system for an application that helps

independent tourists book excursions arranged by
expert individuals or tourist agencies.
• This database will record details of the offering agent
(individual or a company), and the tours/ excursions
they offer.
• The prices and the exact details may be changed from
time to time.
• Tourists can write reviews and award stars.
• Show how this database will be used by at least 2
different types of users (guest and landlord) other than
the Manager.
This Photo by Unknown Author is licensed under CC BY-SA-NC 11
This Photo by Unknown Author is licensed under CC BY-SA

11

A Family Database System

• Design a database system for an application that supports
families in tracking their important data about health,
education and various utilities and suppliers (the scope need
not include family accounts)., but you are free to decide!)
• Think about what data is typically needed by an average family
within an Egyptian context.
• This database may be used to keep track of preferred suppliers/
outlets for certain items. Also, the tracking of service providers
(dry cleaning, appliance repairs, etc.)
• One possible thing to track is various shopping lists (per
member and per store).
• Show how this database will be used by at least 2 different
types of users (family members and the head of the family who
would have different privileges and/ or functions).
12

This Photo by Unknown Author is licensed under CC BY-SA-NC This Photo by Unknown Author is licensed under CC BY-SA-NC This Photo by Unknown Author is licensed under CC BY-SA-NC

12

6
 2/8/25

Ma’s kitchen with online

food reservation and
delivery.
• Design a database system to support a family that
has an extra “cooking” capacity, and who wish to
use it to generate extra income.
• The system should support an application that can
be used with many families.
• The system should record details of families, the
meals they offer, as well as delivery companies or
agents.
• Meal buyers should also be recorded, as well as
their past meal reservations and purchases.
Buyers should also be able to rate meals and
kitchens.
• Show how this database will be used by at least 2
different types of users (kitchens and buyers)
other than the System Administrators.
13
This Photo by Unknown Author is licensed under CC BY-SA

13

A Database System to Support a

local supermarket CRM

• Design a database system for an application that supports

a local-scale supermarket's CRM (Customer Relationship
Management)/ or a loyalty program system.
• This database may be used to keep track of customers,
special offers and periodical communications (like a
monthly newsletter).
• Customers who register would benefit from things like
electronic receipts, special offers and discounts, points
that can be used against purchases, etc. li
• Registered customers would be sent satisfaction surveys
from time to time to help improve their experiences.
• Show how this database will be used by at least 2
different types of users (customers, product group
managers) in addition to the store manager.

14
This Photo by Unknown Author is licensed under CC BY-SA This Photo by Unknown Author is licensed under CC BY-SA

14

7
 2/8/25

A Database System
to Support Event
Organization

• Design a database system for an application that supports a business in organizing events, such
as product launches, fairs and exhibitions.
• This database may be used to keep track of participants, sponsors, caterers, venues, etc.
• It should enable using the attendees’ data to launch other promotional offers and campaigns. It
should also provide for post-event evaluations and comments.
• Patrons would be sent satisfaction surveys from time to time to help improve their experiences.
• Show how this database will be used by at least 2 different types of users (attendees, sponsors)
in addition to the event manager.

15

15

Educational
Course Support
• Design a database system for an application that
supports students in posting queries and
receiving answers about courses of study that
they are taking.
• This database may be used to keep track of
course names, topics, and tutors available and
questions posted.
• The data base should also keep track of
Resources and materials per topic.
• Registered students would be sent satisfaction
surveys from time to time to help improve the
system.
• Show how this database will be used by at least
2 different types of users (students, tutors) in
addition to the the system administrator.

This Photo by Unknown Author is licensed under CC BY This Photo by Unknown Author is licensed under CC BY

16

8
 2/8/25

A Database System for the Gift

Shop of a
Museum or Art Gallery

• With opening of the Grand Egyptian Museum eminent!

• Design a database system for managing the activities of the
gift shops of that museum.
• You may for instance track information about the items on
sale, prices, discounts and promotions, special marketing
campaigns, etc., ..etc.
• Show how this database will be used by at least two
different types of users (like sales staff, suppliers), in
addition to the Store Management.
• For example, an employee may be able to update the stock
database whereas a supplier might be able to check if an
item is running low or selling fast to decide whether to re-
stock.
• Managers can generate reports about sales (possibly
grouped by weekdays, etc.), returns, the the average sales
by employee, etc..

17

17

A Database System for an

Application to
Save Food from Going to Waste
• Design a database system for a mobile application that aims to save over-
stocked food items.
• This database may be used to keep track of outlets that are willing to sell
over-stocked food (sandwiches, bakery. items, platters, etc.) at a greatly
reduced prices. Usually, the offer has a maximum time limit to be collected.
• Customers must register prior to use the application to record their food
preferences or constraints, as well as their payment method(s).
• Show how this database will be used by at least 2 different types of users
(buyers and sellers) other than the Manager.
• For example: At a Beano’s branch that closes at midnight, the manager finds
at 10:00 PM that he still has too many Danish pastries unsold, decides to offer
a number for sale at 30% of the original price to be collected before the
closing time. A customer sees the offer, purchases the desired number (which
has to be equal or less than the units available), then goes to the branch to
collect. Shops may also assemble “surprise bags” with an assortment of items.
è Check: Too Good to Go app

18

18

9
 2/8/25

A Database System for receiving and

recording road traffic violations video
footage and pictures

• Design a database system that enables various road users to upload video footage or pictures
of drivers who violate traffic safety (e.g. jumping a red light, driving in the opposite direction
of indicated travel direction, swerving without due care and attention, etc..
• This database would record details of the materials and who submitted them, with a “trust-
score” for each user who submits materials.
• A rating would be given to each item before submitting to the police authority with view of
prosecution.
• Show how this database will be used by at least 2 different types of users (user and rater)
other than the director of the system.
• For example: whilst you are driving, your dash cam records another vehicle descending a
slip road that should be only used in the opposite direction to join the motorway, you press on
the ”protect” button to keep that recording, later you upload that video to the web site.
è Check: Dash cams

19

19

A Database System for an Application

to for Collecting and Distributing
Clothes Donations

• Design a database system for an application that aims to help

people donate and those deserving to collect donations (you
decide what type!).
• This database may be used to keep track of donors, items
that they donate and people who need them.
• People who would like to give donations are registered.
Those in need are not registered but logged as individual
cases with descriptions of the items they need. must register
prior to use the application to record their food
• Show how this database will be used by at least 2 different
types of users (donors and those who receive donations)
other than the Manager.
• For example: you have a winter coat bag that you don’t need,
but a student in a nearby university needs, so you both log
the offer and the need, and the system matches them up for
collection (collection terms like area, cost, etc. will be
recorded)..

20

20

10
 2/8/25

Innovate!
• YOU can innovate in this project, through observation, field research,
analysis, model building, brainstorming, etc..
• Think of this project as an innovating entrepreneur!
• Keep a logbook or diary of your team meetings and your personal
work. You may be asked to attach a “group logbook” as an appendix
to your Final Report.

21

21

Form Groups & email to TA

• fagr.abdelrazek@aucegypt.edu
• Tell her of your group members (with full details) and the working/
general title of the chosen project (you can choose a more specific
title later).

22

11
 2/8/25

Use of Generative AI
• You may use a generative AI tool (such as ChatGPT, Gemini, etc.) to get ideas for possible
requirements for your chosen system, but:
• You must declare clearly –in an appendix- that you did, stating:
• Which Gen AI tool you used (name it and provide its URL)
• Specify all the exact prompts you used.
• The dates you used the Gen AI tool.
• The responses of the tool.
• If you use a Gen AI tool, you are required to write a short statement of your thoughts
and reflections on how useful the use of the Gen AI tool was to you!
• Please also see the section in the Syllabus document on “AI Tools Use Policy” and
observe its requirements.

23

Use visual models!!

• Context diagram to establish

scope & main users.
• ERD’s, with the needed symbols
and other info.
• Used one of: Lucidchart, Visual
Paradigm, Visio (least preferred),
etc. to help you with drawing
professional-looking models that
can also be easy to modify and
update.

24

12
 2/8/25

Data Flow Diagrams (DFDs)

• A useful tool for visualing the information flow around and within the
information system.
• This is a useful quick tutorial (there are many online):
https://youtu.be/6VGTvgaJllM?si=E0DfcxpxoBaSwlRY
• You can use Lucidchart to construct DFDs, as well as many other types
of system-related diagrams.
• Your MOIS2101 textbook should contain a chapter on using DFDs.

25

Creating the Context Diagram

• Include in Phase 1 documentation.
• The highest level in a data flow diagram
• Contains only one process, representing the entire system
• The process is given the number 0.
• All entities external to the system/ process, as well as major data
flows to and from External Entities are shown.

26

13
 2/8/25

Basic Rules
• The data flow diagram must have one process
• Must not be any freestanding objects
• A process must have both an input and output data flow
• A data store must be connected to at least one process
• External entities should not be connected to one another

27

The Context Diagram (very useful for

scope determination)
• Note: arrows indicate data flows (data structures being transferred), so labels can
be only nouns or noun phrases! (External) Entities are the squares outside the
boundaries of the system and could be other systems or people. (watch:
https://youtu.be/6VGTvgaJllM?si=CKlqbnZIkW9fmBmv)

Source: Kroenke & Boyle (2017)

28

14
 2/8/25

Card-based (lo-fi) prototypes (you can show some such

interface mock-ups for features that you would like to
implement in future)

• Index cards (3 X 5 inches)

• Each card represents one screen or part of screen
• Often used in website/ application development

See Rogers et al., (2011) Ch. 11 29

29

Examples of using wireframes to model the user interactions (optional to the project)

The doctor identifies herself to The doctor receives a patient The doctor can view the
the system. This info can be and finds his file in the database, patient’s medical history in a
stored on the phone. or registers a new patient to the patient’s summary and charts of
system. the blood pressure and glucose
level.

69
30

15
 2/8/25

©Prof. Dr. G. H. Galal-Edeen 31

31

Projects
• 1) Pharmacy CRM.
• A museum gift shop • 2) Vehicle spare parts and/ or servicing.
• Saving over-supplied food • 3) Electric accessories shop.
• Spare room booking • 4) A doctor’s clinic appointments and follow up
system.
• Charity donations & distribution
• 5) Tourist excursions bookings.
• Disaster response system
• 6) Personal media streaming and blogs (with
• Campus food ordering subscriptions for targeting announcements).
• Personal medical records • 7) Ma’s kitchen with online food reservation and
delivery.
• 8) A family’s database.
• 9) A supermarket CRM.
• 10) Education course support.
• 11) A restaurant/ café review and customer
comments system (see Foursquare for example).

32

16