Professional Documents
Culture Documents
Ideas
Design brief: Developing relational database management system for a
client.
The purpose of developing ideas is to develop our ideas.In inquiring and
analyzing we gathered information.here we need to develop those
information.
Aspect
Requirements
Aesthetics (Consider
appearance, style, color,
shape/form, texture, pattern,
finish, layout)
Accessibility(where it will be
available-Online, in the form
of poster, website etc)
safely
Manufacturing (What
resources are available? Are
Product Design
Ms word tables
Designing tables
Tables:
DFD/ERD
Database:issue
Field type
Data type
Size
relation
regno
varchar
50
Foreign key
Data time
Accno
varchar
50
Not null
Name
varchar
50
Not null
course
varchar
50
Not null
Not null
Author
varchar
50
Not null
volumn
varchar
50
Not null
Edition
varchar
50
null
Data Type
Size
Relation
Accno
Varchar
50
Primary key
Author
Varchar
50
Not null
Title
Varchar
50
Not null
Publication
Varchar
50
Not null
Edition
Varchar
50
Not null
No_of_copies
int
Volumn
Varchar
50
Not null
Date_pur
Varchar
50
Not null
Not null
Price
Decimal
(18,2)
Not null
Not null
Status
Varchar(50)
50
Field
Data
Name
Type
S
i
Relatio
Varch
Not
ar
null
Varch
Primar
ar
y key
Name
Regno
Date_of_is
Dateti
Not
sue
me
null
Varch
Not
ar
null
Addresss
Date_of_re
Dateti
Not
turn
me
null
Varch
Not
ar
null
Varch
Foreig
ar
n key
Course
Accno
No
Va
rc
nul
ha
Gender
r
E-R Diagram
Entity Relationship Diagram is used in modern database software engineering to
illustrate logical structure of database. It is a relational schema database modeling
method used to
Model a system and approach. This approach commonly used in database design. The
diagram created using this method is called ER-diagram.
The ER-diagram depicts the various relationships among entities, considering each object
as entity. Entity is represented as rectangle shape and relationship represented as
diamond shape. It depicts the relationship between data object. The ER-diagram is the
notation that is used to conduct the data modeling activity.
Entity: Entity is the things which we want to store information. It is an elementary basic
building block of storing information about business process. An entity represents an
object defined within the information system about which you want to store information.
Entities are distinct things in the enterprise.
Relationship: A relationship is normal connection or association between entities used
to relate two or more entities with some common attributes or meaningful interaction
between the object.
Attributes: Attributes are the properties of the entities and relationship descriptor of the
entity. Attributes are elementary pieces of information attached to an entity.
Structure of a database:
The database consists of following functional components.
Module Decomposition:
Student details:
In this form the users have to enter the details about the student like
name, regno, courseetc. If the proper details are not entered at the
same time error message will be displayed and record will not be stored
And if the entered register number is already exist then the details cant
be stored and error message will be displayed.
Delete student details:
In this case admin can delete individual student details by entering his
register number .If the Register no is not entered at same time message
will be displayed and record will not be storedAnd if the entered number
is already deleted then it will be giving the message.
Book issue:
In this form the Liberian can issue the books to the student. If the books
are already distributed to students then Liberian cant issue those
particular books.
Book return:
Here the user must return the book on given date Otherwise fine will be
calculated
Calculate fine:
In this case we can maintain the late fine of library member who return
the issued book after the due date
Prioritize the best possible design idea for the solution from the
above list and reason is why it is better than the other ideas.
Justify:
6 because i didnt gave a good information.
..
..
..
..