RPM Customs E-Commerce Web Application Technical Document Specification

This technical document outlines the specifications for the RPM Customs E-Commerce Web Application, including its purpose, scope, and requirements for site navigation, content management, reporting, and search optimization. The document also includes assumptions and constraints, as well as information on the developer and version history.

Running head: ICT 1
Assessment one
Part A: Website Technical Document Specification
Section One: Introduction
Client: RPM CUSTOMS
Project Name RPM CUSTOMS E-COMMERCE WEB APPLICATION
Developer (developer firm’s name here)
Addressing Email
Include your address here
Phone Number
Postal address – Code
City
Date 18/06/2018
Document
Author
(insert your name here)
Section Two: Document Tracking
This section describes the evolution of the application by giving version descriptions. Each
version comes with some added functionalities.
Version Editor Date Description
1.0 Developing firm 06/17/2018 Building the web
application from
scratch.
Section Three: System Description

ICT 2
a) Purpose
The purpose of this project is to develop an e-commerce web application platform from
which the firm will directly sell its products to its clients.
b) Scope
The project will have a products’ catalogue- photos and datasheets and an online ordering
module.
c) Background information
RPM Customs is a distributor dealing with high performance automotive parts and
accessories that are primarily used for racing in the market and is known for its quality
and high performance products.
Section Four: Assumptions and Constraints
[Contractual/project level assumptions and constraints]
Assumptions
Requirement
ID
DESCRIPTION
Constraints
Requirement
ID
Requirement definition

ICT 3
Section Five: Website Requirements
a) Site Navigation and Organization
Menu System- as the primary navigation method of the site will be displayed on each page. A
hierarchical menu content divided into related functional areas based on the current Organization
site map.
Each section will have a main page where visitors can navigate to the sub items under the
sections, but still be able to get back to any of the other main section home pages. Full site
search, with administrator control.
b) Automated Content Management
The web site content must easily be able to manage dynamically by non-technical department
staff in as simple a method as possible, and who have basic IT knowledge. The technical staff
will add, change and delete site content without manipulating any HTML or scripting code.
Personnel should be able to access designated templates and easily update information in pre-
designed formats, including the use of databases to hold and change dynamic information.
Documents in Word, Excel, PDF, and other formats. Most documents will age and lose
relevancy over time, and need to be routinely updated or removed
c) Website Reporting

ICT 4
A quality web site reporting system that provides types and features of management reports,
including traffic counts, origin or domain names sources of visitors, or other useful information
regarding the website is required.
d) Search Optimization
The title of each page should be unique to each page and not be longer than 70 characters.2.Each
content author must have the ability to customize the META-DESCRIPTION and META-
KEYWORDS in the CMS
All page URLs, especially dynamically generated ones, must have friendly URL aliases so that
they are picked up by search engines.4.The CMS must employ semantic HTML (h1, h2, p, etc.)
The CMS should allow the content author to specify ALT text for all images
Web Application Elements
Section/requirement webpage Requirement definition
Web Hosting and Security Configurations
Requirement ID Description

ICT 5
Requirement ID Description
-The End-