Web Content Management System
Web Content Management System
Index
1. Preface 4
2. Acknowledgement 5
3. Project Profile 6
4. Project Planning 7
5. System Analysis 8
6. Abstract 9
7. Project Summary 10
8. User Requirement 11
9. Software Specification 12
10. Feasibility Study 13
11. Tools and Technology 15
12. Database Infomation 26
13. E-R-Diagram 29
14. Database Information 31
15. Screen Shots 36
16. Testing 57
17. Future Enhancement 60
18. Reference and Bibliography 61
PREFACE
To prepare a project as well as project report as a separate subject in 5nd
semester B.Sc.IT project is to be prepared on a particular subject after study it
well.
It was felt that it is important and very instructive not only to learn the
principles of software engineering but also apply them to a software
development project so that all aspects of development can be clearly seen on
a project.
By preparing this report I have understood the need of practical training in the
education field. It is easier to work with computerized system the manual
system. It saves time, effort and space and also increases the efficiency by
creating interest.
ACKNOWLEDGEMENT
Most successful feats involve efforts of many people. This Project is no
exception. It ismy pleasure to take this opportunity to thank all those who helped me
directly or indirectly indevelopment of the project.
We are also thankful to our Parents, Friends and Others for their opinions
andsupport in the system.The project has given us immense knowledge to use in our
future ventures and manymoments to cherish.
Your faithfully :-
Shah Keval
PROJECT PROFILE
TITLE :- STMB.COM
DIV :- F4 [B.Sc(it)5-th]
PROJECT ID :- BIT13F433
Project Planning
Description Estimated Days Date
From To
SYSTEM STUDY 15 29-06-2013 14-07-2013
GATHERING
System Analysis
Since years, there have been many people carrying out businesses on the
Internet. Growth of such community has very rapid since last few years.
follow a per-defined path or strategy to earn money from the net. One such
strategy is to create, marketing and manage a website with attracts huge
masses of people. Such websites, with lots of traffic can yield into lots of
revenue.
Today people get fast edited photographic while staying at home just require
internet no more requirement, So it „very easy way you can get whatever they
want in their image it and also will save time and some other cost so better
way is online.
Abstract
• Usability: The interface should use term and concept, which are drawn from the
previous experience of the user who will make most of the system.
• Efficiency: The system must provide easy and fast access without consuming time
and resources. This system is efficient then other manual techniques.
ProjectSummary
This site only create some of the information for every services. To
show Services user has to create an account. Those who does not have
an account, Once the user has created account, only he can view the
main part of the website.
Admin side:-
Admin delete the records in the database which can be retrieved and
used whenever needed and all the validation are performed during the
entry of the data. Thus it ensures that the user cannot enter any wrong
data which would cause problem later.
User side:-
This site allows the user to access all the services available. To show
services, user must create an account in this website. It also includes
the concept to enter transaction reports and to maintain user records
very easily.
User Requirement
When the user wants to see the page in the project then user have to Click on
that particular page on which link is there then that only that page Will be
opened.
In these way the is related with the system. Here the so in these
way by Clicking on the link user can see any page what he wants.
As designers, we all want our products to be easy to use, but it‟s quite tricky to
define precisely what that means. It is difficult because ease of use is a
subjective experience, different for each individual user.
Software Specification
SystemRequirement
SoftwareRequirement
HardwareRequirement
FEASIBILITY ANALYSIS
FEASIBILITY STUDY :-
TYPES :-
There are three type of feasibility analysis:
1. Technical Feasibility
2. Operational Feasibility
3. Economical
Feasibility
1. Technical feasibility:
2. Operational Feasibility:
It is the measure of that our project solves the problems of the user or
not.it is also a measure of how user feels about our project.Whether the right
information is provided at the right time to the users and all operations done
by software solves the problem of user or not.
Economical Feasibility:
It is measure of effectiveness of a
the cost into project or and benefits.
solution. COST-BENEFIT
called It analysis .To Thus
account find itthis is
we oftenwhether
ask
financestakes costs
are available for implementing the proposed solution. In our
project we have used php and mysql their costs are low .so; we can say very
that our project is cost effective.
Information required to develop the application is gathered with the help of internet
access. Various websites involving CMS has been viewed and the detail study of features
and working of them is carried out. Some of the CMS based websites like
WWW.joomla.org, www.wordpress.com and such others were reffered for the functionalities
they provide. Even the tutorials related to the technologies used in the development process
have been studied.
Software Design
Software Design is actually a multi-step process that focuses on four distinct
attributes of program; data structure, software
architecture, interface
representations, and procedural details. The design process translates
requirements into a representation of the software that can be assessed for
quality before code
generation begins based upon the functional specifications taking up design,
developing, and concluding with the acceptance testing.
Software Development
The design must be translated into a machine-readable form. The code
generation step performs this task. If design is performed in a detailed manner,
code generation can be accomplished mechanistically.
Maintenance
It includes providing of post implementation support.
WaterFall Model:
• Simplest Model is the Waterfall model, which states that the phases are
organized in linear order. It is a well-known technique of top down design
and structured programming.
• With the water fall model, the sequence of activities performed in a
software development process is:
Requirement Analysis
Planning
Designing
Implementing
Testing
•
In a Typical model, the project begins with feasibility study analysis. On
successful completion of testing, the system is installed. After this, the regular
operation and maintenance of the system take place. When the phases are
completed, there should be product produced by that phase. The earlier output of
phase is called work product and is usually in the form of documents like the
requirement documents, design documents and for coding phase output is code.
One cannot jump between various phases of waterfall model. It is strictly to be
followed in a step by step manner
.
Hardware Requirements :
Internet Modem,
Intel P4 processor,
512 MB RAM
20 GB harddisk
Software Requirements:
Front-end:
PHP
Back-end:
MySQL
PLATFORM SPECIFICATION
It is the language your web browser can understands. The basics of HTML
are fairly simple to learn. Just by knowing the basic tags, you can design and entire
website. A “tag” is a coded command used to indicate how part of a web page
should be display.
About Javascript
About PHP
• PHP is the most superior technology. Other technologies PERL, Python, Tcl,
VB script, ASP are older and inferior technologies. Even Java/JSP is inferior to
PHP.
• Open Source
ABOUT APACHE
Apache 1.3
Apache 1.3 has been ported to a great variety of Unix platforms
and is the
most widely deployed Web server
on the Internet.
• Windows support :-
• Modular :-
Apache 2.0
Apache 2.0 is the latest and greatest version of the Apache server. The
architecture contains significant improvements over the 1.3 series. The following
are some of them.
• Protocol Module :-
• Portable :-
DATABASE TABLES
DATABASE
Admin
Advertisement
Cms
Magazine
Moment
News
Our Pillars
Sub-Sections
Users
E-R DIAGRAM
An entity-relationship diagram is a data modeling technique that creates a
graphical representation of the entities, and the relationships between entities,
within an information system.
An Entity Relationship Diagram (ERD) is a visual representation of different
data
using conventions that describe how these data are related to each other. For
example, the elements writer, novel, and consumer may be described using ER
diagrams this way:
While able to describe just about any system, ER diagrams are most often
associated with complex databases that are used in software engineering and IT
networks. In particular, ER diagrams are frequently used during the design
stage
of a development process in order to identify different system elements and
their
relationships with each other. For example, an inventory software used in a
retail
shop will have a database that monitors elements such as purchases, item, item
type, item source and item price.
A relationship is how the data is shared between entities. There are three types
of
relationships between entities
1.) One to One:-
One instance of an entity (A) is associated with one other instance of
another entity (B). For example, in a database of employees, each employee
name
(A) is associated with only one social security number (B).
2.) One to Many:-
One instance of an entity (A) is associated with zero, one or many instances of
another entity (B), but for one instance of entity B there is only one instance of
entity A. For example, for a company with all employees working in one
building,
the building name (A) is associated with many different employees (B), but
those
employees all share the same singular association with entity A.
3.) Many to Many :-
One instance of an entity (A) is associated with one, zero or many instances of
another entity (B), and one instance of entity B is associated with one, zero or
many instances of entity A. For example, for a company in which all of its
employees work on multiple projects, each instance of an employee (A) is
associated with many instances of a project (B), and at the same time, each
instance of a project (B) has multiple employees (A) associated with it.
One of the tools of the structure analysis is the Date Flow Diagrams. A
DFD is a graphical representation of the system. The Data Flow Diagram
is used by the system analyst to explain the flow of the data in the system.
A DFD uses some elements as its building blocks. The following is a
brief description of these elements:
External entity
User
CMS
Site View
2. Level 1 :
User
Logged In ? No Login.php
Yes
3. Level 2 : (Dashboard)
Dashboard
User Moderate
User()
4. Level 2 : (Magazine)
User
(Logged in)
Magazine
Table Magazine
User User
(Logged in) (Logged in)
View Our
View News Add News Add
Pillars
User User
(Logged in) (Logged in)
Users Moments
Tabel moments
Tabel USERS
9. Level 2 : (Advertisement)
User
( L og ged in)
A d v e r ti s e m e n t
View
Add
A d v e e r ti s e m e n t
Ta b l e
a d v e r ti s e m e n t
User Side:
User
About
Contact
Our Pillars
Video
Gallery
Photo
Gallery Other
Latest News Chamkara Sanstha
Gnati
Bandhu
3. CMS
4. Magazine
5. News
6. Our Pillars
7. User
8. Moments
9. Advertisement
CLIENT SIDE:-
1. Home Page
2 . About
3. Our Pillars
4. Photo Gallery
5. Latest News
6. Gnati Bandhu
7. Chamkara
8. Other Sanstha
9. Video Gallery
10. Contact
12. Register
•
This section discusses the testing strategy, methodology and types of tests that the
product must pass in order to pass quality assurance and customer acceptance. A
detailed test plan will be created as part of the implementation phase.
•
Following are the various levels of testing adopted during system development:
Unit Testing:
Unit Testing refers to tests that verify the functionality of a specific section of
code, usually at the function level.
Integration Testing:
Integration Testing in any type of software testing that seeks to verify the
interfaces between components against a software design. Software components may
be integrated in an iterative way or all together. It works to expose defects
in the interfaces and interaction between integrated components (modules)
System Testing:
System Testing tests a completely integrated system to verify that it meets its
requirements.
Acceptance Testing :
Acceptance Testing is the system testing performed by the customer to determine whether
or not the accept the delivery of the product
TESTING SCHEDULE:-
Testing has been done for each procedure back-to-back so that errors and
missions can be found as early as possible.
Once the system has been developed fully testing procedure is followed on
other machines, which differs in configuration.
TEST METHODS:-
STATISTICAL TESTING:-
Statistical Testing is used to test the program‟s performance and reliability and
to check how it works under operational conditions. Tests are designed to
reflect the actual user inputs and their frequency.
The stages involved in the static analysis for this system are follows:
Control flow analysis
Data use analysis
Interface
analysis
DEFECT
TESTING:-
Black-box Testing:-
White-box Testing:-
Structural Testing:-
Path testing has been exercised i.e. every independent execution path through
component or program has been tested. If every independent path is executed
then all statements in the components must have been executed at least once.
After the individual modules were tested out, the integration procedure is done to
create a complete system. This integration process involves building the system a
testing the resultant system for problems that arise from component interactions
FUTURE EXPANSION
This “CMS based Web Tool” is initially developed with the idea to
implement and work with the basic features of CMS in an application.
With this, a user can develop a small-scale simple website very easily
and quickly.
Bibliography
Books :
FutureCMSArchitecture
eBooks
Websites :
o
www.joomla.com
o
www.wordpress.com
o
www.contegro.com
o
www.google.com
o
www.htmldrive.net