This document outlines the functional requirements for the Premmani website. The purpose of the site is to provide information about drums, culture, and music. It will allow users to browse drum types, view shopping cart information, and see videos, photos, and information about drum sounds and institutions offering drum courses. The site will use LAMPP (Linux, Apache, MySQL, PHP) and be compatible with multiple browsers and resolutions. It requires a server with Linux, Lampp, MySQL, 5GB storage minimum and client browsers like Firefox.
This document discusses web servers. It provides an overview of web clients and web servers, and describes how web servers handle static and dynamic content. The document outlines the typical architecture of a two-tier or three-tier client-server system for delivering web pages. It also discusses the GET and POST request methods, phases of request handling, popular web servers like Apache and IIS, and factors to consider when selecting a web server.
Non-functional requirements describe how a system will operate rather than what it will do. They include qualities like usability, reliability, performance, and supportability. Usability measures how easy a system is to use, learn, and adapt to user needs. Reliability refers to the likelihood of failures and is measured by metrics like mean time between failures. Performance requirements specify the system's efficiency and response times. Supportability involves how easily a system can be maintained, internationalized, and adapted to changes.
See enhanced version of this (https://www.slideshare.net/ujjwaltrivedi/prd-template-for-product-managers). A sample product requirement document draft for mobile apps. It can also be used for quick wireframing and estimates of any kind of software. It should generally be a useful tool for business analysts, product managers, pre sales consultants. It is modern, complete and agile.
Not all the WEB APIs are RESTful, some are just plain RPC.
REST is an architecture style.
The video attached to these slides.
https://www.youtube.com/watch?v=M28aBbtdWj4
The document provides functional specifications and requirements for phases 2 through 4 of the Openhealth.in web site project. It outlines the goals, audience, phases, tools, hardware and software specifications, information architecture, site design, and application layer specifications for the project. The target user is between 10-70 years old and a novice web user. The site will be developed using current web technologies and a MySQL database. It will have simple navigation focused on key content areas and be accessible across different browsers and connections.
The document provides functional specifications and requirements for phases 2 through 4 of the Openhealth.in web site project. It outlines the goals, audience, phases, and tools to be used. The site will use a content management system to allow staff to easily edit and upload content. It will have a simple navigation structure and meet technical requirements for speed and compatibility. Detailed specifications are provided for the hardware, information architecture, site design, application layers, and use cases.
The document provides functional specifications and requirements for phases 2 through 4 of the Openhealth.in web site project. It outlines the goals, audience, phases, tools, hardware and software specifications, information architecture, site design, and application layer specifications for the project. The target user is between 10-70 years old and a novice web user. The site will be developed using current web technologies and a MySQL database. It will have simple navigation and emphasize updated content to educate visitors about pollution issues in India.
The document provides functional specifications and requirements for phases 2 through 4 of the Openhealth.in web site project. It outlines the goals, audience, phases, tools, hardware and software specifications, information architecture, site design, and application layer specifications for the project. The target user is between 10-70 years old and a novice web user. The site will be developed using current web technologies and a MySQL database. It will have simple navigation and emphasize updated content to educate visitors about pollution issues in India.
This document discusses web servers. It provides an overview of web clients and web servers, and describes how web servers handle static and dynamic content. The document outlines the typical architecture of a two-tier or three-tier client-server system for delivering web pages. It also discusses the GET and POST request methods, phases of request handling, popular web servers like Apache and IIS, and factors to consider when selecting a web server.
Non-functional requirements describe how a system will operate rather than what it will do. They include qualities like usability, reliability, performance, and supportability. Usability measures how easy a system is to use, learn, and adapt to user needs. Reliability refers to the likelihood of failures and is measured by metrics like mean time between failures. Performance requirements specify the system's efficiency and response times. Supportability involves how easily a system can be maintained, internationalized, and adapted to changes.
See enhanced version of this (https://www.slideshare.net/ujjwaltrivedi/prd-template-for-product-managers). A sample product requirement document draft for mobile apps. It can also be used for quick wireframing and estimates of any kind of software. It should generally be a useful tool for business analysts, product managers, pre sales consultants. It is modern, complete and agile.
Not all the WEB APIs are RESTful, some are just plain RPC.
REST is an architecture style.
The video attached to these slides.
https://www.youtube.com/watch?v=M28aBbtdWj4
The document provides functional specifications and requirements for phases 2 through 4 of the Openhealth.in web site project. It outlines the goals, audience, phases, tools, hardware and software specifications, information architecture, site design, and application layer specifications for the project. The target user is between 10-70 years old and a novice web user. The site will be developed using current web technologies and a MySQL database. It will have simple navigation focused on key content areas and be accessible across different browsers and connections.
The document provides functional specifications and requirements for phases 2 through 4 of the Openhealth.in web site project. It outlines the goals, audience, phases, and tools to be used. The site will use a content management system to allow staff to easily edit and upload content. It will have a simple navigation structure and meet technical requirements for speed and compatibility. Detailed specifications are provided for the hardware, information architecture, site design, application layers, and use cases.
The document provides functional specifications and requirements for phases 2 through 4 of the Openhealth.in web site project. It outlines the goals, audience, phases, tools, hardware and software specifications, information architecture, site design, and application layer specifications for the project. The target user is between 10-70 years old and a novice web user. The site will be developed using current web technologies and a MySQL database. It will have simple navigation and emphasize updated content to educate visitors about pollution issues in India.
The document provides functional specifications and requirements for phases 2 through 4 of the Openhealth.in web site project. It outlines the goals, audience, phases, tools, hardware and software specifications, information architecture, site design, and application layer specifications for the project. The target user is between 10-70 years old and a novice web user. The site will be developed using current web technologies and a MySQL database. It will have simple navigation and emphasize updated content to educate visitors about pollution issues in India.
The document provides functional specifications and requirements for phases 2 through 4 of the Openhealth.in web site project. It outlines the goals, audience, phases, and tools to be used. The site will use a content management system to allow staff to easily edit and upload content. It will have a simple navigation structure and emphasize updated content. Hardware requirements, information architecture, site design guidelines, and application layer specifications are also defined. Finally, use cases and workflow diagrams demonstrate how the different components and features will function.
The document provides functional specifications and requirements for phases 2 through 4 of the Openhealth.in web site project. It outlines the goals, audience, phases, and tools to be used. The site will use a content management system to allow staff to easily edit and upload content. It will have a simple navigation structure and meet technical requirements for speed and compatibility. Detailed specifications are provided for the hardware, information architecture, site design, application layers, and use cases.
The document provides functional specifications and requirements for phases 2 through 4 of the Openhealth.in web site project. It outlines the goals, audience, phases, and tools to be used. The site will use a content management system to allow staff to easily edit and upload content. It will have a simple navigation structure and meet technical requirements for speed and compatibility. Detailed specifications are provided for the hardware, software, information architecture, site design, application layers, and use cases.
The document provides functional specifications and requirements for phases 2 through 4 of the Openhealth.in web site project. It outlines the goals, audience, phases, and tools to be used. The site will use a content management system to allow staff to easily edit and upload content. It will have a MySQL database and be developed using the latest Web 2.0 technologies. Wireframes and use cases are provided to illustrate typical workflows for administrators, authors and public site users.
The document provides functional specifications and requirements for phases 2 through 4 of the Openhealth.in web site project. It outlines the goals, audience, phases, tools, hardware and software specifications, information architecture, site design, and application layer specifications for the project. The target user is between 10-70 years old and a novice web user. The site will be developed using current web technologies and a MySQL database. It will have simple navigation focused on key content areas and be accessible across different browsers and connections.
The document provides functional specifications and requirements for phases 2 through 4 of the Openhealth.in web site project. It outlines the goals, audience, phases, tools, hardware and software specifications, information architecture, site design, and application layer specifications for the project. The target user is between 10-70 years old and a novice web user. The site will be developed using current web technologies and a MySQL database. It will have simple navigation and emphasize updated content to educate visitors about pollution issues in India.
The document provides functional specifications and requirements for phases 2 through 4 of the Openhealth.in web site project. It outlines the goals, audience, phases, and tools to be used. The site will use a content management system to allow staff to easily edit and upload content. It will have a MySQL database and be developed using the latest Web 2.0 technologies. Wireframes and use cases are provided to illustrate typical workflows for administrators, authors and public site users.
The document provides functional specifications and requirements for phases 2 through 4 of the Openhealth.in web site project. It outlines the goals, audience, phases, tools, hardware and software specifications, information architecture, site design, and application layer specifications for the project. The target user is between 10-70 years old and a novice web user. The site will be developed using current web technologies and a MySQL database. It will have simple navigation focused on key content areas and be accessible across different browsers and connections.
The document provides functional specifications and requirements for phases 2 through 4 of the Openhealth.in web site project. It outlines the goals, audience, phases, and tools to be used. The site will use a content management system to allow staff to easily edit and upload content. It will have a simple navigation structure and meet technical requirements for speed and compatibility. Detailed specifications are provided for the hardware, software, information architecture, site design, application layers, and use cases.
This document outlines the course content for an introduction to web technology course. The course covers basic web terminology, HTML, CSS, and web hosting. It is divided into 4 units:
1) Basic web concepts including the internet, browsers, servers, domains and URLs
2) An introduction to HTML5 including page structure, tags, and multimedia
3) An introduction to CSS including style sheets, selectors, properties and layouts
4) Web publishing and hosting including the need for hosting, different hosting options, and steps to host a website.
The document provides a software requirements specification for an online job portal being developed by Avachromians. It outlines the purpose, scope, and overall functions of the system. The system will allow job seekers to search and apply for jobs listed by employers. It will also give employers the ability to list available positions and view applicant resumes. The document defines requirements through use case descriptions and diagrams to illustrate how the different users will interact with the system.
This document provides an overview of a major seminar on knowledge discovery from web logs. It discusses how analyzing vast amounts of web site traversal data stored in web logs can reveal useful knowledge about user behavior that can be applied to improve web service performance. Specific techniques covered include mining web logs to build path profiles that predict future page visits, using these predictions to prefetch web documents for faster loading, and clustering web pages to create more intuitive user interfaces. The document lists several applications of web log mining and its advantages.
The document provides an overview of a final report on developing a voice browser. It describes the purpose of creating a voice-based web browser to make online information accessible to users without reading/writing abilities. It outlines the scope, technologies used like HTML, Java, speech recognition and synthesis. It also includes UML diagrams like use case, class, and sequence diagrams modeling the voice browser system and interactions between users, administrator and system components.
This document provides an overview of browser architecture and website structure. It defines a browser as software that sends requests to servers to locate and display web content such as websites, pages, images, audio and video. The rendering engine processes resources, creates a DOM tree, renders the tree, performs layout and painting to display requested content. Website structure involves analyzing content and audience, organizing navigation, content and design, developing pages and layout, implementing interaction and maintenance like marketing and optimization.
This document provides an overview and introduction to installing and administering a web server. It discusses hosting options, hardware requirements, operating system choices, web server software options like Apache and IIS, networking basics, DNS, and more. The course will teach students how to install and configure the Apache web server to deliver dynamic web content on a UNIX system through lectures, demonstrations and hands-on exercises.
This document discusses web servers, including what they are, common features, differences between kernel-mode and user-mode servers, popular server software like Apache, IIS, Nginx, Google Web Server, and Resin. It also covers topics like path translation, load limits, overloads, and the market shares of different server products.
The document provides an overview of a voice based web browser software requirement specification. It includes sections on introduction and purpose, overall description, specific requirements, and diagrams. The introduction describes allowing access to the web through voice for users unable to read, write or access the internet normally. The overall description outlines product functions, constraints, use cases, classes, sequences, activities, and architecture. It provides details on the voice browser's operation and interactions between users, administrators and the system.
This document provides an overview of a module on web authoring and social media. It outlines the aims, structure, assessments, and ground rules of the module. It also covers topics that will be taught, including the history and characteristics of the internet, internet terminology, connecting to the internet, internet addressing, the domain name system, common web terms, server-client models, web browsers, search engines, and the benefits of the internet.
This document discusses the course Web Engineering. It outlines the grading policy for the course which includes a final exam worth 40% and midterm worth 25%. It also discusses some key topics in web engineering including RSS, protocols and ports, and the difference between static and dynamic websites. Finally, it covers various attributes and quality factors of web applications such as usability, functionality, reliability, and extensibility. The inventor of the World Wide Web is identified as Sir Tim Berners-Lee.
This document discusses the grading policy, topics, and attributes of a Web Engineering course. The grading is based 40% on a final exam, 25% on a midterm, and the rest on assignments, class tests, attendance, and a presentation. Topics covered include RSS, protocols and ports, differences between static and dynamic websites, and web technologies. Key attributes of web applications are discussed such as being network intensive, content driven, requiring continuous evolution and immediacy, prioritizing security and aesthetics. Various categories and quality attributes of web applications are also outlined.
The document discusses COBOL data structures and how to define group items, elementary items, and move data between them. It also covers accepting and displaying data using COBOL verbs like MOVE, DISPLAY, and ACCEPT.
The document introduces the new mainframe and its capabilities. It outlines that mainframes are used by large organizations to host commercial databases and applications requiring high security and availability. Mainframes can process large volumes of different workloads concurrently. Typical mainframe roles include system programmers, operators, developers and administrators. Common operating systems are z/OS, z/VM, VSE, and Linux for zSeries.
The document provides functional specifications and requirements for phases 2 through 4 of the Openhealth.in web site project. It outlines the goals, audience, phases, and tools to be used. The site will use a content management system to allow staff to easily edit and upload content. It will have a simple navigation structure and emphasize updated content. Hardware requirements, information architecture, site design guidelines, and application layer specifications are also defined. Finally, use cases and workflow diagrams demonstrate how the different components and features will function.
The document provides functional specifications and requirements for phases 2 through 4 of the Openhealth.in web site project. It outlines the goals, audience, phases, and tools to be used. The site will use a content management system to allow staff to easily edit and upload content. It will have a simple navigation structure and meet technical requirements for speed and compatibility. Detailed specifications are provided for the hardware, information architecture, site design, application layers, and use cases.
The document provides functional specifications and requirements for phases 2 through 4 of the Openhealth.in web site project. It outlines the goals, audience, phases, and tools to be used. The site will use a content management system to allow staff to easily edit and upload content. It will have a simple navigation structure and meet technical requirements for speed and compatibility. Detailed specifications are provided for the hardware, software, information architecture, site design, application layers, and use cases.
The document provides functional specifications and requirements for phases 2 through 4 of the Openhealth.in web site project. It outlines the goals, audience, phases, and tools to be used. The site will use a content management system to allow staff to easily edit and upload content. It will have a MySQL database and be developed using the latest Web 2.0 technologies. Wireframes and use cases are provided to illustrate typical workflows for administrators, authors and public site users.
The document provides functional specifications and requirements for phases 2 through 4 of the Openhealth.in web site project. It outlines the goals, audience, phases, tools, hardware and software specifications, information architecture, site design, and application layer specifications for the project. The target user is between 10-70 years old and a novice web user. The site will be developed using current web technologies and a MySQL database. It will have simple navigation focused on key content areas and be accessible across different browsers and connections.
The document provides functional specifications and requirements for phases 2 through 4 of the Openhealth.in web site project. It outlines the goals, audience, phases, tools, hardware and software specifications, information architecture, site design, and application layer specifications for the project. The target user is between 10-70 years old and a novice web user. The site will be developed using current web technologies and a MySQL database. It will have simple navigation and emphasize updated content to educate visitors about pollution issues in India.
The document provides functional specifications and requirements for phases 2 through 4 of the Openhealth.in web site project. It outlines the goals, audience, phases, and tools to be used. The site will use a content management system to allow staff to easily edit and upload content. It will have a MySQL database and be developed using the latest Web 2.0 technologies. Wireframes and use cases are provided to illustrate typical workflows for administrators, authors and public site users.
The document provides functional specifications and requirements for phases 2 through 4 of the Openhealth.in web site project. It outlines the goals, audience, phases, tools, hardware and software specifications, information architecture, site design, and application layer specifications for the project. The target user is between 10-70 years old and a novice web user. The site will be developed using current web technologies and a MySQL database. It will have simple navigation focused on key content areas and be accessible across different browsers and connections.
The document provides functional specifications and requirements for phases 2 through 4 of the Openhealth.in web site project. It outlines the goals, audience, phases, and tools to be used. The site will use a content management system to allow staff to easily edit and upload content. It will have a simple navigation structure and meet technical requirements for speed and compatibility. Detailed specifications are provided for the hardware, software, information architecture, site design, application layers, and use cases.
This document outlines the course content for an introduction to web technology course. The course covers basic web terminology, HTML, CSS, and web hosting. It is divided into 4 units:
1) Basic web concepts including the internet, browsers, servers, domains and URLs
2) An introduction to HTML5 including page structure, tags, and multimedia
3) An introduction to CSS including style sheets, selectors, properties and layouts
4) Web publishing and hosting including the need for hosting, different hosting options, and steps to host a website.
The document provides a software requirements specification for an online job portal being developed by Avachromians. It outlines the purpose, scope, and overall functions of the system. The system will allow job seekers to search and apply for jobs listed by employers. It will also give employers the ability to list available positions and view applicant resumes. The document defines requirements through use case descriptions and diagrams to illustrate how the different users will interact with the system.
This document provides an overview of a major seminar on knowledge discovery from web logs. It discusses how analyzing vast amounts of web site traversal data stored in web logs can reveal useful knowledge about user behavior that can be applied to improve web service performance. Specific techniques covered include mining web logs to build path profiles that predict future page visits, using these predictions to prefetch web documents for faster loading, and clustering web pages to create more intuitive user interfaces. The document lists several applications of web log mining and its advantages.
The document provides an overview of a final report on developing a voice browser. It describes the purpose of creating a voice-based web browser to make online information accessible to users without reading/writing abilities. It outlines the scope, technologies used like HTML, Java, speech recognition and synthesis. It also includes UML diagrams like use case, class, and sequence diagrams modeling the voice browser system and interactions between users, administrator and system components.
This document provides an overview of browser architecture and website structure. It defines a browser as software that sends requests to servers to locate and display web content such as websites, pages, images, audio and video. The rendering engine processes resources, creates a DOM tree, renders the tree, performs layout and painting to display requested content. Website structure involves analyzing content and audience, organizing navigation, content and design, developing pages and layout, implementing interaction and maintenance like marketing and optimization.
This document provides an overview and introduction to installing and administering a web server. It discusses hosting options, hardware requirements, operating system choices, web server software options like Apache and IIS, networking basics, DNS, and more. The course will teach students how to install and configure the Apache web server to deliver dynamic web content on a UNIX system through lectures, demonstrations and hands-on exercises.
This document discusses web servers, including what they are, common features, differences between kernel-mode and user-mode servers, popular server software like Apache, IIS, Nginx, Google Web Server, and Resin. It also covers topics like path translation, load limits, overloads, and the market shares of different server products.
The document provides an overview of a voice based web browser software requirement specification. It includes sections on introduction and purpose, overall description, specific requirements, and diagrams. The introduction describes allowing access to the web through voice for users unable to read, write or access the internet normally. The overall description outlines product functions, constraints, use cases, classes, sequences, activities, and architecture. It provides details on the voice browser's operation and interactions between users, administrators and the system.
This document provides an overview of a module on web authoring and social media. It outlines the aims, structure, assessments, and ground rules of the module. It also covers topics that will be taught, including the history and characteristics of the internet, internet terminology, connecting to the internet, internet addressing, the domain name system, common web terms, server-client models, web browsers, search engines, and the benefits of the internet.
This document discusses the course Web Engineering. It outlines the grading policy for the course which includes a final exam worth 40% and midterm worth 25%. It also discusses some key topics in web engineering including RSS, protocols and ports, and the difference between static and dynamic websites. Finally, it covers various attributes and quality factors of web applications such as usability, functionality, reliability, and extensibility. The inventor of the World Wide Web is identified as Sir Tim Berners-Lee.
This document discusses the grading policy, topics, and attributes of a Web Engineering course. The grading is based 40% on a final exam, 25% on a midterm, and the rest on assignments, class tests, attendance, and a presentation. Topics covered include RSS, protocols and ports, differences between static and dynamic websites, and web technologies. Key attributes of web applications are discussed such as being network intensive, content driven, requiring continuous evolution and immediacy, prioritizing security and aesthetics. Various categories and quality attributes of web applications are also outlined.
The document discusses COBOL data structures and how to define group items, elementary items, and move data between them. It also covers accepting and displaying data using COBOL verbs like MOVE, DISPLAY, and ACCEPT.
The document introduces the new mainframe and its capabilities. It outlines that mainframes are used by large organizations to host commercial databases and applications requiring high security and availability. Mainframes can process large volumes of different workloads concurrently. Typical mainframe roles include system programmers, operators, developers and administrators. Common operating systems are z/OS, z/VM, VSE, and Linux for zSeries.
The document provides an example JCL used to run a COBOL program. It includes:
1) A JOB statement that identifies the job name, programmer, class, and priority.
2) A STEP statement specifying the COBOL program "COBPROG" to execute.
3) DD statements defining the input and output files for the COBOL program.
The document then explains each part of the JCL and how it will execute the COBOL program on the MVS operating system.
This chapter discusses Job Control Language (JCL) and the Display and Search Facility (SDSF) in 3 sentences: It introduces JCL, which uses statements like JOB, EXEC, and DD to describe programs, inputs, and outputs for execution on the mainframe. It also explains how to check job outputs using SDSF, which allows viewing and searching system logs, monitoring jobs, and controlling job execution order and output printing. Key topics covered include basic JCL coding, procedures, concatenation, continuation, and using SDSF to view job status and outputs.
The document outlines a 4-phase methodology for developing a website about drums called Premmani's Drums. The discovery phase involved gathering existing drum information and identifying problems like a lack of awareness and access to information. The design phase developed solutions like sections on drum types, learning institutions, and famous local drummers. The developing phase used open-source technology and WordPress. The deployment phase launched the site at http://premmani.com/.
This document discusses various sections on a website called Premmani including a home page header and footer, categories on Tamilnadu culture and music, information on drums for shopping and training, and government musical institutions.
WordPress is a free, open-source content management system that allows users to build and manage dynamic websites and blogs. It provides templates called themes that control the visual design and layout of pages. Users can create and edit pages and blog posts called articles directly from their web browser using an easy-to-use control panel. Plugins extend WordPress functionality by adding features like search engine optimization tools. Reasons for using WordPress include the ability to easily update and customize the look and feel of a site using themes, to frequently publish and receive comments on blog posts, and to leverage additional features for search engine optimization and social media.
Ajax allows web pages to be updated asynchronously by exchanging data in the background without interfering with the display and functioning of the page. It uses a combination of technologies like HTML, CSS, JavaScript, XML, and XSLT along with the XMLHttpRequest object. This allows parts of a page or even whole sections to be updated without reloading, improving interactivity and reducing bandwidth usage. However, dynamically updated content also poses challenges for bookmarking, back button usage, and search engine crawling. Developers must also address security concerns and learn new testing and coding methods for Ajax applications.
PHP is a widely used server-side scripting language that was designed for web development to produce dynamic web pages. PHP frameworks streamline the development of web applications written in PHP by providing basic structures that help promote rapid application development. The general idea behind how a PHP framework works is referred to as the Model-View-Controller pattern, where the model refers to the data, view refers to the presentation layer, and controller refers to the application logic. PHP frameworks should be used when working on projects with tight deadlines or substantial amounts of coding to speed up the development process and make the job less tedious.
A framework provides the structure for building a program, including what can be built and how parts interrelate. It includes actual programs, programming interfaces, and tools. Common examples are resource description, internet business, sender policy, and Zachman frameworks. Frameworks are categorized by programming language such as Perl, PHP, Java, Python, Ruby, ColdFusion, and Asp.Net.
Frames allow dividing a webpage into multiple sections or frames, with each frame displaying a separate HTML document. Frames are commonly used to keep navigation menus or branding visible on the page while allowing the main content area to change. Some key uses of frames include a branding frame to identify the site, a navigational frame with hyperlinks, and a content frame for the primary webpage material. Frames provide advantages like keeping headers and menus visible as a user scrolls or loads new pages.
Web 2.0 refers to second-generation websites that allow users to interact and collaborate to control and share content online. It differs from Web 1.0, which featured static, publisher-controlled websites, by enabling multiple users to publish, edit, and shape website content. Key features of Web 2.0 include social networking, wikis, blogs, podcasts, and mashups, which combine data from multiple online sources. The philosophy of Web 2.0 promotes an "architecture of participation" where users contribute to ongoing website development and progress through social networking and sharing.
1. PREMMANI WEBSITE
FUNCTIONAL REQUIREMENT SPECIFICATIONS
Team
Group 4
Team Members
Shiva Prasad.K
Vinoth Kumar
Project Leader
Mr. Karthick Kumar
Prepared by
K.shiva prasad
1
First Planet , Chennai, 2010.
2. PREMMANI WEBSITE
FUNCTIONAL REQUIREMENT SPECIFICATIONS
Table of Contents
1)Introduction
1.1) Purpose
1.2) Scope
1.3) Definations, Abbreviations and Acronym
1.4) References
1.5) Technologies
2) Overview of Functional Requirements
2.1) Server side Requirements
2.2) Client_Side Requirements
3) Specific Requirements
3.1) External interface Requirements
3.2) Detail Description Functional Requirements
3.3) Performance and Requirements
2
First Planet , Chennai, 2010.
3. PREMMANI WEBSITE
FUNCTIONAL REQUIREMENT SPECIFICATIONS
1.Introduction
1.1.Purpose
Premmani's personal site has to provide the information about the
drums,culture and music.It provides the drum related information where you get
it,how it is related with culture,it provides lessons to learn and information about the
institutions.
1.2.Scope
•Registered his /her secured account through premmani drummers site
•He/She can browse the different drum types available through the site.
•Providing shopping cart information for drums where we get it.
•Providing the latest information’s about drums and music.
•Providing the popular videos and photo gallery of events held recently.
•Providing the information about traditional culture in Tamil.
•Providing the various types drums sounds which is related to music and culture.
•Providing the information about the government and aided institutions which
was offered the drums course.
•Visitors can give feedback,leave the comments dynamically and more contact
personally.
•Administrators or managers can able to check out list of items,product
information and so on.
3
First Planet , Chennai, 2010.
4. PREMMANI WEBSITE
FUNCTIONAL REQUIREMENT SPECIFICATIONS
1.3. Definitions, Abbreviations and Acronyms
•PHP : Stands for "Hypertext Preprocessor." A server side scripting language used
normally on Unix-based systems. It is similar to other scripting languages, but was designed
specifically for the purposes of server side scripting on web pages, so it is often has simpler
expressions for more commonly used applications.
•MySql : This is a database which is commonly used with web pages. It can allow
viewers to look up specific information from a large quantity of data stored in the database
•HTTP: Hypertext Transfer Protocol is a transaction oriented client/server protocol
between web browser & a Web Server
•HTTPS: Secure Hypertext Transfer Protocol is a HTTP over SSL (secure socket layer)
• HTML: Hypertext Markup Language is a markup language used to design static web
pages
• LAMPP:Linux Apache ,MySql ,PHP. Perl, an inter-operable group of open- source
computer programs.
• CSS: Cascading Style Sheets (CSS) is a style sheet language used to describe the
presentation of a document written in a markup language. Its most common application is to
style web pages written in HTML and XHTML, but the language can be applied to any kind
of XML document, including SVG and XUL.
•Word press: Word Press is an open source blog publishing application powered by
PHP and Myself which can also be used for content management system It has many
features including a plugin architecture and a template's system.
•Content Management System : A content management system (CMS) is a collection
of procedures used to manage work flow in a collaborative environment. These procedures
can be manual or computer-based. The procedures are designed to:
4
First Planet , Chennai, 2010.
5. PREMMANI WEBSITE
FUNCTIONAL REQUIREMENT SPECIFICATIONS
• Allow for a large number of people to contribute to and share stored data
• Control access to data, based on user roles. User roles define what information each user can view or edit
• Aid in easy storage and retrieval of data
• Reduce repetitive duplicate input
• Improve the ease of report writing
• Improve communication between users
1.4.References
• Wordpress with Lampp server configuration tool from wikepedia
• Php and MySql Courseware provided by W3Schools containing various tutorials
1.5.Technologies
•Web 2.0: Open Source Technology
•Lampp : Apache server for Linux system
•MySql : Database
• Php : Pre Processor Hypertext for dynamic web pages
•Word press plug-ins: word press plug-ins for effective look
2. Overview of Functional Requirements:
This web site requires the following abilities
2.1 Server-side Requirements:
5
First Planet , Chennai, 2010.
6. PREMMANI WEBSITE
FUNCTIONAL REQUIREMENT SPECIFICATIONS
Operating System : Linux or Ubuntu
Web Server : Lampp Server
Database : MySql
Minimum Space : 5GB(including Minimum
database)
2.2 Client-side Requirements :
Operating System : Linux or Ubuntu
Browser : Mozila firebox
The web site provides easy links for easy navigation(browse) in the site. A visitor with
minimum knowledge of web browsing/surfing can access the site very easily. An online
help documentation will be provide to help the users and visitors in using the facilities.
3.Specific Requirements
3.1 External Interface Requirements:
6
First Planet , Chennai, 2010.
7. PREMMANI WEBSITE
FUNCTIONAL REQUIREMENT SPECIFICATIONS
Since the project is completely web-based, users will interface with the
website using a mouse and keyboard. They will navigate the site by clicking on hyperlinks
and get directed to other pages.
3.2 Detail description of Functional Requirement.
Website Resolution compatibility.
Adjust-ability: Auto Adjustable
Minimum resolution: 800 x 600
Best Viewed in 1024 x 768.
Browser: Mozilla fire box or Internet Explorer
3.3 Performance Requirements:
The Web-administration that the site is running on is outside of our control,so we
can not affect the number of users the server can handle or response time. Each page in the
site needs to load in a reasonable amount of time. We should implement latest web
techniques like caching to speed up the loading of dynamic pages. This will also improve
on the number of simultaneous users,as connections are freed faster.
7
First Planet , Chennai, 2010.