Experiment no: 1

Aim: Requirements Engineering of Web Application for

Content Management System.

Name: Abbasali Springwala
Branch: Computers (Sem 5)
Roll no: 63

Sign:

Grade:









Aim: Requirements Engineering of Web Application for Content Management
System.
Theory:
1. Introduction:
What is content management system? It is nothing but web pages so designed
that it makes easy to update our web content. The WebPages built in php are
connected to MySQL which stores our data or content. Content could be anything
like ----
1. Documents
2. Web sites / web applications
3. Multi-media files (audio, image, video)
4. Postings + Comments ( blogs, forums)
5. Short messages (sms, twitter)
6. Topics (wiki)
7. Correspondence (e-mail, newsletter)
8. Feeds (rss)
9. Individuals (social networking)

1.1 Purpose:
A software application used to upload, edit, and managecontent displayed on a
website. A content management system can perform a variety of different tasks for
a website including regulating when content is displayed, how many times the
content is shown to a specific user, and managing how the content connects or
interacts with other elements of the website.
This software also enables less technicalindividuals to manage content on a
website easily without having an extensive coding background.
Content management is a great way to ensure that your website is always fresh
and filled with great content and it always keeps your presence young.

1.2 Scope:
We can use it to build an enterprise content management system (ECS).Enterprise
Content Management, as a form of content management, combines the capture,
search and networking of documents with digital archiving, document
management and workflow.
More elaborate CMS can perform unique functions (such as archiving, built-in
search engines, and mod rewrites), but basic functionality is still related to easy
creation and editing of web pages.

1.3 Definition:
A Web Content Management System (WCMS) is a software system that provides
website authoring, collaboration, and administration tools designed to allow
users with little knowledge of web programming languages or markup languages
to create and manage website content with relative ease. A robust WCMS
provides the foundation for collaboration, offering users the ability to manage
documents and output for multiple author editing and participation.

1.4 References:
http://www.wymsy.com/
http://tandemserver.org/
http://en.wikipedia.org/wiki/Main_Page
http://websolutions.opentext.com/products_web_content_management.aspx

2. Overall description:
A typical CMS works like this,
A web design layout is designed and developed. Usually this entails a logo/banner
at the top, standard navigation menus across the top, down the left side, and/or at
the foot of the page, and a 'blank' area where content is inserted
This layout format is then converted into a master template for all subsequent
pages. During the process of this conversion, the CMS admin backend is integrated
and tested.
Web content producers are given access and instructions on how to add text and
images to web pages automatically. Most CMS are usually very intuitive and easy
to operate.
Each generated page is saved onto a database, for future editing or deletion.

2.1 Product Perspective:
2.1.1 System interface:
The system interfaces in our project includes the main operating system which is
Windows XP/Windows 7.



2.1.2 User interfaces:
The user interfaces in our project includes web browser (any general purpose),
mouse & keyboard for selecting the items from the categories.

2.1.3 H/W Requirements:
No additional hardware requirements are needed; only basic user interfaces are
enough in our project.

2.1.4 S/W Requirements:
The basic s/w which is needed in our project is the text editor. We are using
notepad++ as our editor in which code is to be written.
The second most important s/w required in our project is wamp server. We are
using internet explorer 7 and wamp sever for the execution of the code.
Backend software used to store data would be mysql.

2.1.5 Communication interfaces:
The basic means of communication in our project is to online communicate with
us i.e. through internet.
We are willing to provide our contact info so that people can contact through us
personally or via telephonic talk.

2.1.6 Memory constraints:
Memory required depends on the amount of content provided by the
organization. No such memory constrains.

2.1.7 Operations:
Staff admin can add users to edit website. Editors with proper rights to maintain
website can login and change the contents of the website. Admin and editors
must login with login id and password to modify the website.
Website visitors can read the content of webpages and navigate through the links.
Visitors cannot modify the WebPages.






2.1.8 Site adaptations requirement:
2.1.8.1 Website requirement:

We require a public area and a staff area. In Public area the website visitors will
read and navigate through the contents of website. Whereas the staff area is for
admin to add users to edit and maintain the website. (CRUD: Create Read Update
Delete)

2.3 User characteristics:
First and foremost quality of a software product from users perspective is that
product must meet all the requirements stated by him in elicitation and
negotiation.
In our project, we mainly focused on
Reliability: Our site doesnt have any defects. Not only this, it shouldn't fail while
execution.
Efficiency: Our sites make effective use of the storage space and execute
command as per desired timing requirements.
Flexibility: Changes are easy to make.
Portability: Our site is portable; user can run our product in any environment with
any browser.
Security: Staff area is separate from public area to avoid the visitors from
hampering the security of website.
Common Vocabulary: Use of common words so that employees of the
organization find easy to maintain the website.
Self-explanatory: Visitors of website can navigate through the links easily in an
intuitive manner.

2.4 Constraints:
The most important thing is to manage constraints and even so bad is to
recognize them.
As we are already given the deadline, we are doing all the tasks as per are decided
schedule.
In order to make the product cost effective, we are using less no. of resources.
We are developing our project in self explanatory manner so that user gets
interacted easily as well as we have made it very interactive.

2.5 Assumptions and dependencies: The unique property of our website is:
Simple database, user or the owner can maintain the content easily without much
technical knowledge and the visitors may find it intuitive or self-explanatory.




















3. Specific Requirements:
3.1 External interface requirements:
3.1.1 User interface:
Our website will be completely functional in the following web browsers:
Microsoft Internet Explorer (IE) 7.0 and IE 8.0 Mozilla Firefox 3.x Google Chrome.
A confirmation message will be displayed to the user prior to any kind of
conformation of membership activity on the website. The confirmation action will
be carried out only if the user confirms the confirmation action.
Each user will have his/her unique username and password.
Help tools are provided for users.

3.2 Software product features:
The basic s/w which is needed in our project is the text editor-notepad.
Notepad is a common text-only (plain text) editor, Notepad supports both left-to-
right and right-to-left based languages, updated version of Notepad with a search
and replace function (Ctrl + H), as well as Ctrl + F for search and similar keyboard
shortcuts. Notepad in our project is used to edit text with markup, such as HTML.
Important software used is Internet Explorer7. It has better security framework,
the user can rearrange tabs by dragging and dropping them as desired.
Internet Explorer supports conditional comments. These are comments that can
be used to show and hide different parts of our code depending upon the
conditions in the comment.

3.3 Performance requirement (Non-functional requirements):
Our web site is designed to increase sales in business.
Our website gives high performance and process to create product information
for the web site, process to sell products from start to finish, process to order
products or materials from supplies.

3.4 Software system attributes (Quality requirements):

Maintainability:
Our website has ability of the system to undergo changes with a degree of ease.

Portability:
Our website has the ability to run under different computing environments. The
environment types can be either hardware or software.

Recoverability:
Our website can recover from any sudden damage.

Security:
Our website has the capability to prevent malicious or accidental actions outside
of the designed usage, and to prevent disclosure or loss of information.



Logical database requirements:
All data will be saved in the database: user accounts and profiles. The database
allows concurrent access and will be kept consistent at all times, requiring a good
database design.



Conclusion: Thus we completed Requirement Engineering for our Content
Management System web application successfully.