Chapter 3 System Design

3.1 NTRODUCTION TO SYSTEM DESIGN:

Systems design is the process of defining the architecture, components,
modules, interfaces, and data for a system to satisfy specified requirements.
Systems design could be seen as the application of systems theory to product
development. There is some overlap with the disciplines of systems analysis,
systems architecture and systems engineering. Until the 2990s, systems design
had a crucial and respected role in the data processing industry. In the 2990s,
standardization of hardware and software resulted in the ability to build modular
systems. The increasing importance of software running on generic platforms has
enhanced the discipline of software engineering.
3.2 PROPOSED SYSTEM:
3.2.1 Automated:

After studying the problems and drawbacks of the existing system, it is

better to suggest a new computerized system. Well, computerization is a very
technical job and requires a comprehensive study of the system, so that analyst
can understand whole system, its weakness and drawbacks. Computer information
provided should be highly accurate and reliable because management has to take
decisions pending on this information. Furthermore, in some circumstances this
information is required immediately and should be served in-time. This is why,
corporate and multi-national organizations are switching over to computer based
information system.

3.2.2 Phases of the Proposed System:

From the study of the existing system, it becomes clear that some sort of
method would be needed to organize, plan and convert the manual system into
computerized system. The system life cycle, from the study of the existing system
to the implementation of the proposed system included the following steps:

1- Preliminary investigation

Digital Newspaper Portal 14

Chapter 3 System Design

2- Analysis
3- Design
4- Development
 Preliminary investigation

This phase deals with the determination of problem. It starts with the simple
question that may be of any type to grasp the understanding of the existing
system. So going through this phase following steps have been followed.

 The Impetus for Change

In this step, those reasons are studied for which new system is needed to
replace the old system or to revise the old system.

 True Nature of the Problem

In this step symptoms and the actual problems are differentiated. This will
help us to identify the problem.

 Scope of the Problem

The specific are in which the problem lies is defined in this step.

3.2.3 Analysis Phase:

The analysis phase is primarily concerned with studying and

understanding the Existing system. Before designing and implementing a new
computerized system, a thorough understanding of existing system is required.
Several steps are involved in analysis phase which are listed below.

3.2.4 Understanding the Existing system:

In this step, the existing system is clearly understood, that is, what I
actually going on the system. What functionality it is performing, where are the
problems and drawbacks, how we can remove them, where are the chances of
enhancements and whether they need extra time or money or just extra effort and
and whether they need extra time or money or just extra effort and how we can

Digital Newspaper Portal 15

Chapter 3 System Design

enhancements and whether they need extra time or money or just extra effort and
etc.

 User involvement:

A study of the most successfully developed projects show that the users of
the system played an active role towards the system development. The user’s
knowledge of the system is needed for a new and better system.

3.2.5 Data Gathering

The most difficult task in analysis phase is data gathering and analyzing
the data. Some common data gathering techniques are:
 Interviews
 Sampling
 Written material
 Questionnaire
 Observations
Well, I used almost all the above mentioned techniques to have a clear
understanding of the existing system because I was well aware of the importance
of this phase.

3.2.6 System Requirements:

The purpose of gathering and analyzing the data is to establish the system
requirements because the design of the new system will be based upon these
system requirements.

3.2.7 Design Phase:

The design phase is an important phase of the system development life

cycle. This phase is the most time consuming part of the project. It is common
saying that nothing is more difficult than designing a new system from scratch.
The designing phase comes after the comprehensive study of the existing system.
If the system analyst won’t give adequate attention or concentration while system

Digital Newspaper Portal 16

Chapter 3 System Design

If the system analyst won’t give adequate attention or concentration while

designing, the new system might not be able to fulfill all the demands or
requirements of the user. The system design phase is divide into parts:

 Preliminary Design:

It is particularly important that what the computer system or software will

have an outlook or interface for its users. That is, it should be easy to use, and
provide options in such a manner that the user can quickly understand and can
perform its required job. Therefore the most critical and creative aspect of
development is the design of user-interface, while the preliminary design of the
software structure invoices that how the system will provide functions to its users.

 Detailed Design:

In the detail design, the actual contents of each module in the preliminary
design are planned. Designing each module is much like writing a short program.
I used ER Diagram and Unified Modeling Language for designing the details of
the system.

3.2.8 Development Phase:

A very important issue in building a software system is deciding that what

tool I should use. Different tools or languages or packages are suitable for
different kinds of systems. The tools selection can also be dependent upon the
user choice sometimes. In the development phase, mainly following task are
accomplished:

 Development of the computer programs

 Testing of the computer programs with all kinds of dummy data
 Testing of the computer programs with real data
 I performed all of above listed procedures to guarantee the authenticity
of this newly build system for its readily usage by the organization. its
readily usage by the organization.

Digital Newspaper Portal 17

Chapter 3 System Design

3.2.9 Implementation:

In preliminary investigation analyst studied the objectives for the new

system, so analyst hold implement the proposed system in such a way that it
should fulfill all requirements of organization. Implementation is the process of
converting the new system. Conversion to the new system must be planned
carefully. Data files must be prepared to be used by the new system. Personnel
who will use or interact with the system must be trained. All conversion related
activities must be scheduled and coordinated properly. When the new system has
been converted, it is usually evaluated by some neutral party. The evaluator is
probably is another analyst, either from the same organization or from an
independent consulting firm. And for course, system is evaluated by the user
themselves, who are the key evaluators. This final development activity is
followed by the maintenance, an ongoing process to improve the system.
3.3 OBJECTIVES OF THE PROPOSED SYSTEM:
The most important objective that newly built computer system should meet
that it should satisfy all the requirements as specified by the user or analyst. The
main objectives of the proposed system are given below:

 Reliability

The system is more reliable than the manual system.

 Efficiency
The proposed system should be efficient and faster.

 Data Security:

It refers to protection form any accidental loss or destruction of data. The data
required for decision making is very important and valuable. Therefore, the
reliability of the system may be secured by maintain a proper system of user
privileges so that only the authorized users can login to the system.

 Time Factor:

Digital Newspaper Portal 18

Chapter 3 System Design

Time factor is an important factor in decision-making. The higher authorities

require quick response for their quires because decisions are based upon this
data analysis so efficient and quick retrieval of data is vital. The proposed
computerized system is too fast than the old manual system.

 User Friendly:

The system should be as much user friendly as possible so that the user can be
easily trained to work on the new system without using a lot of time. The
system should be so much easy to learn that existing staff can easily be adapted
to the new system without the need for hiring a new specialized computer-
trained staff.

 Improving Accuracy:

The purposed system provides accurate and error free results. It ensures error
free efficiency and accuracy.

 Minimizing the Redundancy:

The proposed system has no redundancy. It means that files and data is so
designed and arranged that minimizes data duplications thus cutting
maintenance overhead. My proposed computerized system to replace the
previous manual one meets all the goals toward the development of an
effective and successful information system.

 Report Generation:

Since report generation is the main purpose of the database project so the
purposed system will produce the large number of necessary reports that
provide great deals of information to the customers relating to his or her
transactions. It has helps the user to get the updated and timely information so
that user can get the maximum result from minimum of effort. This will make
the project according to the user requirements. . It has helps the user to get the
updated and timely information so that user can get the maximum result from
minimum of effort.
Digital Newspaper Portal 19
Chapter 3 System Design

3.4 FUNCTIONS OF THE PROPOSED SYSTEM:

The functions that the system will perform are given below:
1. User firstly get registered.
2. Then User get logged.
3. Verify Details from administrator.
4. Then user will get logged in.
5. Select desired news categories from drop down menus.
6. Admin can modify all details about user and himself.
3.5 INTRODUCTION:
3.5.1 Digital Newspaper Portal:

Digital Newspaper Portal is a web based project in

PHP/MySQL/Html/CSS which is used specially for online news. Here password
security check is especially for admin. User can register himself, send mail to
admin about confirmation, and after login select desired news categories and can
read news.

3.5.2 Modules:

 Registration

In this module the user can register himself and after the registration he
can be the login user of the site, The main advantage of this module is
that the customer who is not register with us, he cannot access If he
wanted to access first of all he have to register.

 Login:

After registration you can login to read news.

 Register user:

In this module user can register his/her which he has about the website.
And then he also can check posts and news.

Digital Newspaper Portal 20

Chapter 3 System Design

 Update post:
In this module admin update and add the post of complaint which is under
process.
 Edit post:
In this module admin and user can review the post of complaint which is
under process.
 Add new post:
This is the module of file adding, in this module admin enters a new file
of post and office to the system record which has for the user.
 Delete post:
In this module admin delete a post and office file to the system
record which has complaint of the user.
3.6 UNIFIED MODELING LANGUAGE (UML):
The Unified Modeling Language (UML) is a general-purpose,
developmental, modeling language in the field of software engineering that is
intended to provide a standard way to visualize the design of a system. UML was
originally motivated by the desire to standardize the disparate notational systems
and approaches to software design developed by Grady Booch, Ivar Jacobson and
James Rum Baugh at Rational Software in 2994–95, with further development led
by them through 2996.

3.6.1 Visual Modeling Using UML:

Visual Modeling is a way of thinking about problems using models

organized around real-world ideas. Models reduce the amount of time it takes to
learn and it improves safety, performance, and consistency and reduces errors. It
communicates effectively with process, maps, charts and diagrams of all types. .
UML allows people to develop several different types of visual diagrams that
represent various aspects of the system. Pace star for UML supports the
development of the. Models reduce the amount of time it takes to learn and it
improves safety, performance, and consistency and reduces errors. It
communicates effectively with process, maps, charts and diagrams of all types
medium of choice for developing large scale distributed object applications.

Digital Newspaper Portal 21

Chapter 3 System Design

The unified Modeling Language (UML) offers standard semantics and notations
for describing object structure and behavior and has emerged as the design
medium of choice for developing large scale distributed object applications. UML
allows people to develop several different types of visual diagrams that represent
various aspects of the system. Pace star for UML supports the development of the
majority of these models as follows:
1. Use Case Diagram
2. ER Diagram
3. Activity Diagram
Object oriented approach is used in this project design are as follows.
3.7 USE CASES:
It shows the interaction between use cases, which represent the system
functionality, and actors, which represents the people or system, which provide or
receive information from the system. This shows the overall functionality of the
system. One, who interested in the system as a whole can view these diagrams
and understand what the system is supposed to accomplish.

3.7.1 When to Use: Use Cases Diagrams:

Use cases are used in almost every project. These are helpful in exposing
requirements and planning the project. During the initial stage of a project most
use cases should be defined, but as the project continues more might become
visible. A use case describes event sequences for an actor to use the system. It is a
narrative description of the process. A use case is normally actor or event based.
An actor will begin a process or an event will happen that the system must
respond to.

3.7.2 Elements of a Use Case Diagram:

 Boundary - System boundary can be a computer system, organization

boundary, or department boundary. The system functions and factory may
change depending on the system boundary location. . An actor may perform
an event to start the system.

Digital Newspaper Portal 22

Chapter 3 System Design

 Actors - An external entity (person or machine) that interacts with or uses the
system.
 Sequence of events description - This describes a high level process of what
an actor will do with a system. An actor may perform an event to start the
system. This description does not represent individual steps in the process but
represents the high level process itself.

1. Define the system boundary.

2. Identify actors.
The actor must be able to walk away happy.

3.7.3 Use Case Categorization:

This describes the importance of the function to the system.

 Primary - These functions are required and are common main processes.
 Secondary - These functions are secondary to the system or rarely occur.
Don't need these functions in this iteration. This type of use case is rarely
done.

3.7.4 Use Case Description Level (Abstraction)

 Essential - A general description of the business process. Do not include

technology information. Use the 200 year rule where the information would
be understood 200 years in the past and the future.
 Real - Design oriented, shows reports, examples. Uses technological
descriptions. Real use cases are undesirable during analysis and should only
be used during analysis for specific reasons. Real use cases are handy for
requirements gathering. Normally high level essential use cases and
expanded essential use cases are done during the analysis phase of a project.
A high level real use case is rarely done and an expanded real use case is
done during the design phase only if necessary. A high level real use case is
rarely done and an expanded real use case is . Real use cases are undesirable
during analysis and should only be used during analysis for specific reasons.

Digital Newspaper Portal 23

Chapter 3 System Design

Use case detail level

 High Level - Brief with no detail
 Expanded - More detailed with information about every step in the process.
Don't describe how the system responds.

General guidelines:

When writing use cases, consider:

 Audience
 Purpose
 Iteration

(Figure 3-1: Use Case Diagram in User View)

Digital Newspaper Portal 24

Chapter 3 System Design

(Figure 3-2: Use Case Diagram in Case of Admin)

Data Flow Diagram:

A data flow diagram (DFD) is a graphical representation of the "flow" of

data through an information system, modelling its process aspects. A DFD is
often used as a preliminary step to create an overview of the system, which can
later be elaborated. DFDs can also be used for the visualization of data
processing. A DFD shows what kind of information will be input to and output
from the system, where the data will come from and go to, and where the data
will be stored. It does not show information about the timing of process or
information about whether processes will operate in sequence.

Digital Newspaper Portal 25

Chapter 3 System Design

(Figure 3-3: Data Flow Diagram)

Sequence Diagram:

A Sequence diagram is an interaction diagram that shows how objects operate

with one another and in what order. It is a construct of a Message Sequence Chart.
A sequence diagram shows object interactions arranged in time sequence. It
depicts the objects and classes involved in the scenario and the sequence of
messages exchanged between the objects needed to carry out the functionality of

Digital Newspaper Portal 26

Chapter 3 System Design

the scenario. Sequence diagrams are typically associated with use case
realizations in the Logical View of the system under development. Sequence
diagrams are sometimes called event diagrams or event scenarios. A sequence
diagram shows, as parallel vertical lines (lifelines), different processes or objects
that live simultaneously, and, as horizontal arrows, the messages exchanged
between them, in the order in which they occur. This allows the specification of
simple runtime scenarios in a graphical manner.

(Figure 3-4: Sequence Diagram)

Activity Diagrams:

Activity diagrams are graphical representations of workflows of step wise

activities and actions with support for choice, iteration and concurrency. In the
Unified Modeling Language, activity diagrams are intended to model both
computational and organizational processes (i.e. workflows). Activity diagrams

Digital Newspaper Portal 27

Chapter 3 System Design

show the overall flow of control. Activity diagrams are constructed from a limited
number of shapes, connected with arrows. Arrows run from the start towards the
end and represent the order in which activities happen. Activity diagrams may be
regarded as a form of flowchart. Typical flowchart techniques lack constructs for
expressing concurrency. However, the join and split symbols in activity diagrams
only resolve this for simple cases; the meaning of the model is not clear when
they are arbitrarily combined with decisions or loops. The pages that are
following show some important sequence diagrams relating to the system.

(Figure 3-5: Activity Diagram)

ERD Diagram:
In software engineering, an entity–relationship model (ER model) is a data
model for describing the data or information aspects of a business domain or its
process requirements, in an abstract way that lends itself to ultimately being.
Entity relationship modeling was developed by Peter Chen and published in a be

Digital Newspaper Portal 28

Chapter 3 System Design

implemented in a database such as a relational database. The main components of

ER models are entities (things) and the relationships that can exist among them.
Entity relationship modeling was developed by Peter Chen and published in a
2976 paper. However, variants of the idea existed previously, and have been
devised subsequently such as super type and subtype data entities and
commonality relationships.
An ER model is typically implemented as a database. In the case of a relational
database, which stores data in tables, every row of each table represents one
instance of an entity. Some data fields in these tables point to indexes in other
tables; such pointers represent the relationships.

(Figure 3-6: ERD Diagram)

Digital Newspaper Portal 29

Chapter 3 System Design

3.8 WHAT IS DATABASE?

A database is a tool for collecting and organizing information. Databases can
store information about people, products, orders, or anything else. Many
databases start as a list in a word-processing program or spreadsheet. As the list
grows bigger, redundancies and inconsistencies begin to appear in the data. The
data becomes hard to understand in list form, and there are limited ways of
searching or pulling subsets of data out for review. Once these problems start to
appear, it's a good idea to transfer the data to a database created by a database
management system (DBMS), such as Access 2013.A computerized database is a
container of objects. One database can contain more than one table. For example,
an inventory tracking system that uses three tables is not three databases, but one
database that contains three tables. Unless it has been specifically designed to use
a computerized database is a container of objects. As the list grows bigger,
redundancies and inconsistencies begin to appear in the data. One database can
contain more than one table. For example, an inventory tracking system that uses
three tables is not three databases, but one database that contains three tables.
Unless it has been specifically designed to use data or code from another source,
an Access database stores its tables in a single file, along with other objects, such
as forms, reports, macros, and modules. Databases created in the Access 2007
format (which is also used by Access 2013 and Access 2010) have the file
extension .accdb, and databases created in earlier Access formats have the file
extension .mdb. You can use Access 2013, Access 2010, or Access 2007 to create
files in earlier file formats (for example, Access 2000 and Access 2002-2003).
Using Access, you can:
 Add new data to a database, such as a new item in an inventory
 Edit existing data in the database, such as changing the current location of
an item
 Delete information, perhaps if an item is sold or discarded
 Organize and view the data in different ways
 Share the data with others via reports, e-mail messages, an intranet, or the
Internet.

Digital Newspaper Portal 30

Chapter 3 System Design

3.8.1 Database:

A database is an application that manages data and allows fast storage and
retrieval of that data. A database is a collection of data, which is organized in such
a way that each piece of data is available to those who need it and with minimum
duplication of data. There are different types of database but the most popular is a
relational database that stores data in tables where each row in the table holds the
same sort of information. In the early 1970s, Ted Cod, an IBM researcher devised
12 laws of normalization. These apply to how the data is stored and relations
between different tables.

3.8.2 Advantages of Database:

The most common advantages of database may be as follows.
 Minimal data redundancy
 Consistency of data
 Data integrity
 Sharing of data
 Ease of application development
 Uniform security, privacy and integrity controls
 Reduced program maintenance

 Improved data security

3.8.3 Disadvantages

 Database systems are complex, difficult, and time-consuming to design

 Substantial hardware and software start-up costs
 Damage to database affects virtually all applications programs
 Extensive conversion costs in moving form a file-based system to a database
system
 Initial training required for all programmers and users

 Software startup costs

 Time consume to design

 Damage to applications

Digital Newspaper Portal 31

Chapter 3 System Design

3.9 Normalization:
A relation is in specified normal form if it satisfies the set of requirements
or constraints of that form. The major concept used from the relation data model,
used in the developing the conceptual model in this system, is the normalization
process. Infect normalization process is the process of grouping the data elements.
Its simplest definition will be “The process of converting complex data structure
converting complex data structure converting complex data structure into simple
stable data structure”. Anomalies are the errors or inconsistencies that may result
when a user attempts to update a table that contains the redundant data. There are
types of anomalies are insertion, deletion and the modification. So another
definition of normalizes will be Anomalies are the errors or inconsistencies that
may result when a user attempts to update a table that contains the redundant data.
There are types of anomalies are insertion, deletion and the modification. So
another definition of normalizes will be; Its simplest definition will be “The
process of converting complex data structure into simple stable data structure
“Normalization is the process through which we remove insertion, deletion and
updating of anomalies of the database. “The definition of the three normal forms
is given below.

3.9.1 First Normal Form (1NF)

A relation is in first normal form if every cell a table must contain an

atomic value.

4.9.2 Second Normal Form (2NF)

A relation is in second normal form if it is in first normal form and every

non-key attributes fully functionally dependent on the primary key.

3.9.3 Third Normal Form (3NF)

A relation is in third normal form if and only if it is in second normal form

and no non-key attribute is transitively dependent on the primary key. It is also
stated as “A relation is in third normal form, if it is in second normal form and no
transitive dependencies exist”.

Digital Newspaper Portal 32

Chapter 3 System Design

admin login (id, name, password, email)

users (password, email, name, email, id)

3.10 Database Tables:

A table is a collection of related data held in a structured format within a database.
It consists of columns, and rows. In relational databases and flat file databases, a
table is a set of data elements (values) using a model of vertical columns
(identifiable by name) and horizontal rows, the cell being the unit where a row
and column intersect. A table has a specified number of columns, but can have
any number of rows. Each row is identified by one or more values appearing in a
particular column subset. The columns subset which uniquely identifies a row is
called the primary key. “Table" is another term for "relation"; although there is
the difference in that a table is usually a multistep (bag) of rows where a relation
is a set and does not allow duplicates. Besides the actual data rows, tables
generally have associated.

Digital Newspaper Portal 33

Chapter 3 System Design

3.10.1 Admin Table

(Figure 3-7: Admin Table)

3.10.2 User Table

(Figure 3-8: User Table)

Digital Newspaper Portal 34

Chapter 3 System Design

3.10.3 News Category Table

(Figure 3-9: News Category Table)

3.10.4 Comments Table

(Figure 3-10: Comments Table)

Digital Newspaper Portal 35

Chapter 3 System Design

3.10.5 About us/Contacts us pages Table

(Figure 3-11: Contact/About us Pages Table)

3.10.6 News Subcategory Table

(Figure 3-12: News Subcategory Table)

Digital Newspaper Portal 36

Chapter 3 System Design

3.10.7 News Post Table

(Figure 3-13: News Post Table)

Digital Newspaper Portal 37