You are on page 1of 16

Developing Ideas

By- Chinmayee Channuri 7A


Design brief: Developing relational database management system
for a client.
In my Stage 1, I completed my analysis report and found out
information from my client by asking questions (Primary
research) This way I found out my clients expecting requirements in the DBMS and I
clarified my doubts too. As I did whatever I expected in Stage 1, i progressed onto Stage 2.
In Stage 2, we are making a Entity Relationship Diagram which shows the first look of my
Database Management System which I will be making for my client.
The Database must use information that I gathered at criteria A to meet the requirements of the
client.
The Database needs to contain an Tables, relationship, reports, query,forms because our
purpose of the unit is to create RDBMS.
The Database is for the client so I need to use simple tables. A primary goal of database design
is to decide what tables to create.
This product is perfectly safe because its just a Database it doesnt harm anyone.
The product should be size just good to see.
Function of this Database is to maintain data.

Selection and implementation of such a system can be a complex process so,look here at the
main factors to consider when making your decision, to help you with the whole process.
Aspect

Requirements
Usability

user-friendly the system will be for all


those members of staff required to use
it. In some organisations those may
include Marketing professionals, the
IT department, Database Developers
and others. Look at the suitability
from everyones perspective, and
consider if you can set different levels
of permission for different teams or
personnel.
Many systems offer drag-and-drop
execution, which makes for an
intuitive working methodology.
Importantly, however the system

works, make sure it is usable for your


whole team.
Visualisation & Reporting

Review the ease of visually analysing


and displaying results for any queries
you run on your data, while making
selections and deciding segments.
Also, check how the software displays
campaign results if you feed this
information back into the database.
You should look for visual displays
that will help you show selections and
results to colleagues (likely other
teams or managers/directors) in a way
that they will be able to understand
quickly and easily.

Customer (Who it is for?


What is the target users age,
gender, socio-economic
background?)
Function (What it must do?
What is its purpose? Where
will the product be stored?
How easily can it be
used/maintained?)

Confirm that the modules available in


the data analysis software meet your
business requirements. The
functionality or modules you should be
looking for include:
Extract and filter data

Insight and analysis


Segmentation and modelling
Automation
Forecasting strategy
Results visualisation
Campaign planning and ROI
management.
Support & Development

Think about the support service the


software company offers for its
solution. Is this available during the
hours you are likely to need support?
Is the support offered by email, phone,
other?
Ensure there is a development plan for
the selected software so that you can
be confident it will grow with
emerging technologies. Make sure you
will receive upgrades to the most
recent version and that you will be
supported for as long as you use that
software.
Tools: MS Access

Security (What safety factors


need to be incorporated into
the design?)

Security of your data is an essential


aspect of any database
implementation. Business-sensitive
data and any personal information you
hold must be stored securely to adhere

to regulations and to protect it from


loss or theft.
It is important to consider both the
physical risk to data (e.g. the risk
from fire, theft, etc.) and the risks
from hacking, or from unintentional
corruption of data through human
error. Any system you implement must
address the issue of keeping your data
secure.
Scalability

Ensure that the system has the


capacity to grow with your data and
your business. Remember you are
likely to be adding to the data all the
time, so even though your requirement
may not be huge right now, this can
grow very quickly if you are gathering
and updating your data regularly as
planned. Essentiallycan it easily
manage millions of rows of data?

Updates

The two most important factors


regarding updates to the database are
frequency and automation.
Do you need data to be live and
constantly in sync with your other
systems, or would daily or even
weekly updates to the database be
sufficient? Consider that in order to

automate the update process, you will


typically need a consistent data
source, i.e. the field types, and the files
supplied each time must be the same.
You should consider how often source
data is likely to change, if you are ever
going to import additional data and if
so how your chosen software will deal
with this.
Cost and Suitability

Whilst cost is obviously a factor in any


business expenditure, it is wise to
ensure that as far as possible your
decision is based on the software being
fit for purpose.
It could be a costly mistake to take on
a system that you then invest

time in building, only to find too late


that it is not advanced enough for
your needs. Equally there is no need to
opt for the most expensive software
available, if you are unlikely to need
much of the functionality it offers.

List a range of feasible design ideas for the solutions based on the data collected
Design idea development

Strategies and techniques to communicate and develop ideas:


Technique/Strategy

Product Design

Google Docs tables

Designing tables

Smart draw tool, creately

DFD/ERD

Business Management System database design


This page contains information of Business Management System database design. The database in
turn is further described in detail giving all the fields used with the data types, constraints
available, primary key and foreign key.
What is a database management system :
Database design is used to manage large of information. The database is a collection of
information and is systematically stored in tables in the form of rows and columns. The table in the
database has unique name that identifies its contents. In this database we describe the entire 4
table available in the software, which are used to store all the records.
2. Data types and its description:
Fields in database table have a data type used in database table are explained below.

1. Integer: one optional sign character (+ or -) followed by at least one digit (0-9).
Leading and trailing blanks are ignored. No other character is allowed.

2. Varchar: It is used to store alpha numeric characters. In this data type we can set
the maximum number of characters up to 8000 ranges by defaults SQL server will
set the size to 50 characters range.
3. Data/time: Data/time data type is used for representing date or time.
Table name- Invoices

Field name

Data type

Size

Relation

Customer name
Sales person
Quantity
Amount

Table name- Account receivable

Field name
Account receivable
Date
Customer name

Data type

Size

Relation

Amount

Table name- Customers (Relationship to Invoices)


Field name

Data type

Size

Relation

Customer name
Address
City
State

Table name- Salespeople (Relationship to Invoices)


Field name
Salesperson
Name
DOB
Hire date

Data type

Size

Relation

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 entit
MY ER DIAGRAM NEXT PAGE

...

Structure of a database:
The database consists of following functional components.
Functional component 1: Sales Person Details
Functional component 2: Customer Description
Functional component 3: Invoice Details
Functional component 4: Amount Receivable

Module Decomposition:
Customer DetailsThis form contains every detail about the customer my client has.
Invoice Details-

This form contains the details about my clients account.

Salesperson Description-

This form contains details about my clients workforce and their details.

Amount Details-

This form contains details about my clients and his amount receivable every month.

Selecting and justifying the chosen design:


I think this chosen design apts for all the ideas I have in my brain about my DBMS because
these are the topics which are very important to my client and his office. So, probably this
would be helpful for him because after all, this is SERVICE!
Presenting the chosen design
Reason: I chose this design because I think it is not complicated but it is also creative. It is very
organized and this is the reason I chose this design!

Write the steps you will follow to create your solution. Include the materials,
drawing/diagrams/target diagram/cycle diagram and the technology you will use

1. OPEN MS Access for creating the DBMS


2. While creating the DBMS, I should include the details from this document as well as use
the ER Diagram as the base for my DBMS
3. After the Creation of my DBMS, Review and Check for any mishappenings, mistakes or
unknown problems because of any virus or any problem based on technology
4. Save & Share and Present the DBMS to my Client
5. Lastly, Present to my Peers and Teachers & post on my E-JOURNAL on
www.mydesignjournal-chinmayeechannuri.weebly.com

Understanding of Developing Ideas

Justify:
I would rate myself an 8 because I am happy with my results on this document as well as my
progress on my e- journal too.

You might also like