Scribd
Upload
25 views

Database Systems!: Requirements Analysis

The document discusses requirements analysis for a database application. It outlines the methodology "Data First" which involves creating an information flow diagram, ER diagram, and relational schema from input documents and tasks. An example project is described involving tracking departments, projects, employees, and dependents. Requirements include assigning employees to departments and projects, and tracking employee hours and supervisor. The document concludes by constructing an information flow diagram from requirements of a case study on an online teams platform.

Uploaded by

hgj
Copyright
© © All Rights Reserved
Available Formats
Download as PDF, TXT or read online on Scribd
25 views

Database Systems!: Requirements Analysis

The document discusses requirements analysis for a database application. It outlines the methodology "Data First" which involves creating an information flow diagram, ER diagram, and relational schema from input documents and tasks. An example project is described involving tracking departments, projects, employees, and dependents. Requirements include assigning employees to departments and projects, and tracking employee hours and supervisor. The document concludes by constructing an information flow diagram from requirements of a case study on an online teams platform.

Uploaded by

hgj
Copyright
© © All Rights Reserved
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 22

Database Systems!

REQUIREMENTS ANALYSIS

Dr. Seema Jehan
Outline!
•  Database Application Development
•  The Software Process
•  Overview of Methodology Data First
•  Examples
Database Application
Development - Assumptions!
•  Business processes are well-designed
•  Documents are known
•  Tasks are known
•  System boundary is known
•  One database schema unifying all views can be designed
•  Problems with the methodology?
•  Problems with the organization?
The Software Process!
•  Business process (re)-design
• Analysis
• Specification
• Design Management

• Implementation
•  Testing
•  Operations
•  Maintenance
Overview of the Methodology-
Data First!

Abstract PHP
Tasks! Code/ Code/
SQL! SQL!

Info Flow
Diagram!
MySQL!
ER Relational
Relational
diagram! Schema!
Platform!

Analysis Specification Design Implementation


Example- Project Description!
•  The project description represents the customer
•  It is assumed that
•  Business process are known
•  Documents are known
•  Tasks are known
•  System boundaries are known
Analysis: Information Flow Diagram!
D2! D3! D4!
D1!

T1!

Database!
T2!

T3!

T4!
tasks!

document! D6!

D5!
Requirement1!
•  The company is organised into departments. Each
department has a unique name, a unique number, and a
particular employee who manages the department.

•  We keep track of the start date when that employee


began managing the department.

•  A department may have several locations.


Requirement2!
•  A department controls a number of projects, each of
which has a unique name, a unique number, and a single
location.
Requirement3!
•  The database will store each employee’s name, social
security number, address, salary, gender and birth date.
An employee is assigned to one department, but may
work on several projects, which are not necessarily
controlled by the same department.

•  It is required to keep track of the current number of hours


per week that an employee works on each project, as well
as the direct supervisor of each employee.
Requirement4!
•  The database will keep track of the dependent’s of each
employee for insurance purposes, including each
dependent’s first name, gender, birthdate, and
relationship to the employee.
Analysis: Information Flow Diagram!
Department’s
Project Edit Form!
Employee’s Information Form!
Registration
form!

Edit
Project!
Register!
Employee!

Register
Database!
Department!

Edit
Dependents'!
Information! Edit
Department’s
information!

Dependents'
Information View
Form! Location!
Case Study- TeamsOnline!
•  Requirement 1:
•  Logging in to TeamsOnline via the login screen.
•  All users are uniquely identified by his or her Email
address.

•  Providing a valid Email address and Password


combination will log the user into the system.

•  Providing invalid login credentials should display an error


message and return the user to the login screen.
Case Study!
•  Requirement 2:
•  Users who are new to TeamsOnline must register first.
•  A register button is provided directly on the login page.

•  Clicking this button displays the new user registration


form

•  After the user clicks the Register button, the systems


should verify that all fields are filled in, the Email address
has already not been registered and the password fields
match.
Case Study!
•  Requirement 3:
•  All TeamsOnline users have a user profile containing
basic information about them.

•  After a new user registers, they should be taken to the


edit profile page.

•  The basic profile properties include: gender, birthdate,


and city.
Case Study!
•  Requirement 4:
•  The profile also contains information about user’s
education.

•  The set of available options are maintained by


TeamsOnline

•  The profile also contains Professional information. The


user will select his or her Employer and the Job title.
Case Study!
•  Requirement 5:
•  There are number of links on the home page screen:
•  View courses
•  Logout
•  View Pending Requests
Case Study!
•  Requirement 6:
•  Clicking ManageTeam will display information about the
team’s members.

•  Requirement 7:
•  Provided Team’s code, user can join any Teams
•  Requirement 8:
•  User has the option to leave any Teams
Case Study!
•  Construct an Information Flow Diagram out of these
requirements:
IFD!
Profile Edit
Form! Profile!
Registration
Form!

Edit View
Login Profile! Profile!
Form!
Register!

Login! View
Teams!
Database!

View/Accept/
Join ! Reject!
Teams! request!
Teams List!

Join Request
Teams! Pending
Requests List!
Summary!
•  We designed an information flow diagram from customer
requirements.

•  The next phase in our database development


methodology is specification.

•  We will look at the input/output documents into the


database and will design ER and EER diagram
representing the specification of the database.

•  In addition, we will also provide specification of tasks


relative to the input/output documents and the database
that we have designed.
References!
•  Chapter 3, Fundamentals of Database systems, Ramez
Elmasri and Shamkant Navathe, 7th Edition, 2016

•  Udacity course on “Fundamentals of Databases” by


Georgia Tech:
•  https://classroom.udacity.com/courses/ud150/

You might also like