RSS System Requirements Specification1

K-NOW (Connected Knowledge) Document ID: Q-CK Version: 1.
0
SRS
System Requirements Specification (SYS) Version Date:
28/07/2003
System Requirements Specification (SRS)
K-NOW
Version 1.0.0
Produced for:
Connected Knowledge.
PO Box 98
Ashington
Northumberland
United Kingdom
NE63 8XN
Confidential © Connected Knowledge Ltd. 1

K-NOW (Connected Knowledge) Document ID: Q-CK Version: 1.0
SRS
28/07/2003
Revision History
Date Versio Description Author
n

SRS
28/07/2003
Table of Contents
System Requirements Specification (SRS)............................................................................1-1
K-NOW..................................................................................................................................1-1
Version 1.0.0..........................................................................................................................1-1
1 Miniworld for K-NOW....................................................................................................1-5
1.1.1 Glossary............................................................................................................1-5
1.1.2 Stages of the Project.......................................................................................1-6
1.1.3 Structure of the Website.................................................................................1-6
1.1.4 High Level User Defined Functions of the Website...................................1-6
1.1.5 Mid level User Defined Function of the Website........................................1-7
1.1.5.1.1.1.....................................................................The Registration Process
1-7
1.1.5.1.1.2................................................................................The Billing Process
1-8
1.1.5.1.1.3........................................................................The Broadcast Process
1-8
1.1.5.1.1.4........................................................................The Diagnostic Process
1-8
1.1.5.1.1.5...........................................................................The Planning Process
1-8
1.1.5.1.1.6.....................................................................The Assessment Process
1-9
1.1.6 Reporting Function of the Website...............................................................1-9
1.1.7 Advertising Function of the Website.............................................................1-9
1.1.8 Management Function of the Website.........................................................1-9
1.2 OBJECTIVES OF THE WEBSITE...................................................................................1-9
2 Introduction....................................................................................................................2-12
2.1 SPECIFICATION DEFINITION.....................................................................................2-12
2.2 SPECIFICATION OBJECTIVES....................................................................................2-12
2.3 INTENDED AUDIENCES............................................................................................2-12
2.4 REFERENCES............................................................................................................2-13
2.5 SPECIFICATION OVERVIEW......................................................................................2-14
3 K-NOW System Overview............................................................................................3-15

SRS
28/07/2003
3.1 DEFINITION..............................................................................................................3-15
3.2 BUSINESS GOAL.......................................................................................................3-15
3.3 BUSINESS OBJECTIVES.............................................................................................3-15
3.3.1 Knowledge User Business Benefits............................................................3-15
3.3.2 Product and Service Advertisers Business Benefits................................3-16
3.3.3 Event Advertiser Business benefits............................................................3-16
3.3.4 Knowledge Manager Business Benefits....................................................3-16
3.4 CONTEXT OF THE CONTENT AND KNOWLEDGE MANAGEMENT SYSTEM................3-17
3.4.1 External Hardware.........................................................................................3-18
3.4.2 External Roles................................................................................................3-18
3.4.3 External Software..........................................................................................3-19
3.4.4 External Systems...........................................................................................3-19
3.5 K-NOW CAPABILITIES............................................................................................3-19
3.5.1 Summary of System Capabilities................................................................3-19
3.5.1.1 Employee Capabilities............................................................................3-19
3.5.1.2 Users Capabilities...................................................................................3-20
3.5.1.3 Other Capabilities....................................................................................3-23
4 Functional Requirements...............................................................................................4-24
4.1 Summary Use Case Diagrams.................................................................................4-24
Table of Figures
Figure 1: K-NOW Context Diagram..........................................................................4-3
Figure 2: Employee Summary Use Case Diagram...................................................5-3
Figure 3: User Summary Use Case Diagram...........................................................5-3
Figure 4: System manager Use Case Diagram........................................................6-3
Figure 5: General Knowledge user Use Case Diagram...........................................6-3
Figure 6: Event-Specific Knowledge user Use Case Diagram.................................6-3
Figure 7: Direct Sale Knowledge user Use Case Diagram.......................................6-3
Figure 8: Security Officer Use Case Diagram...........................................................6-3
Figure 9: Advertiser Use Case Diagram...................................................................6-3
Figure 10: User Use Case Diagram.............................Error! Bookmark not defined.

SRS
28/07/2003
Figure 11: User Support Agent Use Case Diagram..................................................6-3

SRS
28/07/2003
1 Miniworld for K-NOW
1.1.1 Glossary
 A Service Package is the level of service available to a user

 An Information Package is a combination of briefings, insights and
programmes
 A Briefing is a two to three page document in formatted text, PDF, or HTML
with graphics, video and sound files that provides a summary of information
on a particular topic
 An insight is a fifteen to forty page document in formatted text or HTML with,
graphics video and sound files that provides an in-depth analysis on a
particular topic
 A programme is a training programme on a particular topic which contains
text of HTML, with graphics OHP slides, case studies, video, sound files and
assessment materials
 A learning object (LO) is an insight, briefing or programme
 An individual user is an individual or entity that registers to use a service
package.
 A corporate user is an individual or entity with access privileges to use a
service package
 A system manager is an individual who analyses and manages the system
 Page Scanner - Scans a web page for keywords.
 RDF Resource Description Framework
 RSS - Really Simple Syndication. This is an XML file format that makes
sharing new articles fairly simple.
 RSS feed - an RSS file that contains links to news articles.
 RSS aggregator -A news aggregator is a software application or remotely
hosted service that collects syndicated content from disparate sources and
provides a single consolidated view. These applications can also be
commonly referred to as a feed reader, feed aggregator or simply just an
aggregator
 URL - Uniform Resource Locator. The address of a file on the internet.
 Web Scanner - Searches the internet for articles.
 XML - eXtensible Markup Language. This is a markup language that is used
for structured documents.
 XML Parser - a tool to break up an XML file into usable parts.


SRS
28/07/2003
1.1.2 Stages of the Project
The project will be completed in X stages.
 Evaluation of Web spider technology

 Evaluation of RSS and RDF systems
 The coding and testing of the RSS aggregator
 The database design
 The creation of the registration system
 The coding for the website.
 The coding for the billing system
 The coding of the content for the website
1.1.3 Structure of the Website
This website is organized into sections. Each section has a unique name, a unique
number, and a particular function.
Some functions within a section have sub-functions
This website will be used by users who will be based at several locations
Different types of user will use the functions of this website in different ways, with
different levels of access, and different service packages.
1.1.4 High Level User Defined Functions of the Website
The first function of this website is to allow users to download an RSS aggregator
which will integrate with Microsoft Outlook and allow users to subscribe to RSS
feeds on training topics.
The second function of the website is to provide a series of RSS feeds with XML
content headlines linking to Briefings, Insights and Programmes within the site
SRS
28/07/2003
The third function of this website is to record and diagnose user needs on the basis
of RSS content accessed.
The fourth function of this website is to provide a mechanism for planning the use of
information products by individuals , teams and organisations
.
The fifth function of this website is to customise RSS headlines to include context
sensitive information such as user, team and organisational headings
The sixth function of the website is to offer an RSS news service with easily
updateable news stories that link to information packages
The seventh function of the website is to offer a registration system for users
The eighth function of the website is to offer a billing and transaction management
system for the website
The ninth function of the website is to attach optional advertising messages to the
RSS content accessed
1.1.5 Mid level User Defined Function of the Website
Within these functions, there are several processes.
The first of these is a registration process
The second is a billing process
The third is a broadcast process, which allows the user to find information on
performance related topics at an individual, team and organisational level
The fourth of these is an autodiscovery process, which allows the system to access
learning objects at an individual, team and organisational level
The fifth of these is a diagnostic process, which allows the system manager to
gather information on development needs at an individual, team and organisational
level.

SRS
28/07/2003
The sixth of these is an assessment process, which allows the users and system
manager to determine the effectiveness of information packages and service
packages
1.1.5.1.1.1The Registration Process
The registration process will elicit location and tracking information from individual
users and tracking information from corporate users
1.1.5.1.1.2The Billing Process
Billing details, such as billing info (essential for checks) and credit card info (valid
only for credit card payment), are stored in a billing profile.
 Billing Info comprises the details such as first and second names, company
name, phone, e-mail and address you provided at the sign up aside from
contact info. This is where the admin mails bills if the user has chosen to
pay by cheque.
 Credit Card Info comprises the number, name and expiration date of user's
credit card.
Both Billing and Credit Card Info can be different for each billing profile.
Billing details are not editable, users can only create a new billing profile. They
cannot delete a billing profile.
When users sign up as a pay user, a new billing profile is created. For trial users, no
billing profile is created. The system, however, keeps track of all trial user's
purchases and includes them into the user's bills available in Online Invoice.
1.1.5.1.1.3 The Broadcast Process
The broadcast process identifies and returns briefings, insights or programmes on

the basis of XML based headlines. Some “Headlines” . will be customised according
to the user name
1.1.5.1.1.4The Diagnostic Process

SRS
28/07/2003
The diagnostic process gathers user information on processes and resources at an

individual, team and organisational level through web based questionnaires and web
based structured interview techniques.
This process identifies learning objects accessed by the user
1.1.5.1.1.5The Planning Process
The planning process gathers user information on processes and resources at an

individual, team or organisational through web based questionnaires and web based
structured interview techniques
1.1.5.1.1.6The Assessment Process

TBD
1.1.6 Reporting Function of the Website
For each user we track usage of each function
For each user we track personal or organizational details
We also track information packages used by each user
We also track service packages used by each user for billing purposes
We also track results of diagnostics
User administrators should be able to access records of defined users and user
groups
1.1.7 Advertising Function of the Website
As well as user defined and reporting functions of the website, we also need to
attach advertising materials to the information packages delivered in response to
user needs
We track the delivery of advertising attachments to information packages

SRS
28/07/2003
We offer an anonymous interface whereby advertisers can compare customer

databases with our user databases to determine advertising effectiveness.
1.1.8 Management Function of the Website
The database that underpins the website will offer an easy to use control panel with
an intuitive interface that can be monitored and adapted by relatively unskilled
administrators
1.2 Objectives of the Website
The User objectives for the RSS system are to:

 Help them identify key business and management solutions in the form
of LOs at an individual, team and organisational level
 Develop customised training and information solutions,using LOs for
each of these problems, ensuring relevance.
 Ensure that the customisation of these solutions provides information
at different levels for different user needs
 Help them identify key business and management opportunities at an
individual, team and organisational level
 Develop customised training and information solutions to assist them in
taking advantage of each of these opportunities, ensuring relevance.
 Close the gap between obtaining and using information in business
and organisations by customising the information to specific problems and
opportunities.
 Make information and training more convenient by allowing them to
access information:
o Anytime (i.e., 24 hours a day and 7 days a week).
o Anywhere that the Knowledge Users have access to the Internet (e.g., at
home, at work, and while travelling).
 Implement effective feedback systems to ensure content is updated
and or replaced frequently ensuring currency of content.
The User Manager objectives for the RSS system are to:
 Identify and track the changing roles of staff within the organisation or
across organisational boundaries.

SRS
28/07/2003
 Enable them to align staff development goals and targets with

organisational, business unit and team goals and targets.
 Enable them to plan and manage quick response to shifting
organisational challenges
The Advertiser objectives for the RSS system are to:

 Minimize the costs of marketing by reducing the costs of market
research, advertising, channel management, etc.
 Maximize income by matching advertising and products and services
to the needs and desires of users as soon as those needs and desires
become apparent
 Act as a central clearing house for training and information
programmes
 Attract delegates to events through this central clearing function
The Knowledge Analyst objectives for the RSS system are to:
 Provide them with a large customer base of staff, managers and
owners from whom they can collate data on management problems and
effective solutions.
 Enable them to easily gather information on the problems faced by
potential Users.
 Enable them to identify and predict problems faced in particular User
segments

SRS
28/07/2003
2 Introduction
This section introduces the system requirements specification (SRS) for the K-NOW
(RSS system) system to its readers.
2.1 Specification Definition
This specification documents the system-level requirements for the RSS system .
2.2 Specification Objectives
The objectives of this specification of the RSS system are to:

 Provide a system overview of the RSS system including definition,
goals, objectives, context, and major capabilities.
 To formally specify its associated:
 Functional requirements.
 Data requirements.
 Quality requirements.
 Constraints.
2.3 Intended Audiences
The intended audiences of stakeholders for this specification of the RSS system
include:
Connected Knowledge Employees:
 Managers
 Directors, who must approve it.
 System Managers, who will perform system management functions using
the RSS system.
 Security Officers, who will respond to potential security violations of the
RSS system.
 User Support Agents, who will provide a human interface for the RSS
system to the users.
The K-NOW Project Team:
 Project Managers

SRS
28/07/2003
 Architects, whose overall architecture must meet the requirements

specified in this SRS.
 Designers, whose design must meet the requirements specified in this
SRS.
 Hardware Engineers, whose hardware components must implement the
requirements specified in this SRS.
 Programmers, whose software components must implement the
requirements specified in this SRS.
 Quality Engineers, who must ensure the quality of its quality requirements.
 Testers, who must ensure that the requirements are validatable and
whose tests must validate the requirements.
 Usability Engineers, who must ensure that the user interfaces fulfil the
usability requirements.
Users, who are any private individuals or organisations that make use of content
held in the RSS system:
 Knowledge Users, who will use the RSS system to identify problems and
solutions to management and business problems. Also to plan career
development or meet day to day organisational challenges.
 Corporate Knowledge Users who will use the RSS system to identify
problems and solutions to management and business problems. Also to
plan career development or meet day to day organisational challenges
 Knowledge User Managers, who will use the RSS system to performance
manage at an individual, team and organisational level
 Seller Advertisers, who will use the RSS system to bring their products
and services to the attention of other users
 Event Advertisers, who will use the RSS system marketplace to bring their
events to the attention of Knowledge users

2.4 References
This specification references or complies with the following documents:

RSS system Project Documents:
 RSS system Application Vision Statement, which documents the business
goals to be achieved by the requirements specified in this specification
 RSS system Glossary, which defines the business and technical terms
used in this specification.

SRS
28/07/2003
 RSS system Release Plan, which documents the scheduled incremental

release of the RSS system in terms of the requirements specified in this
requirements specification.
OPEN Process Framework (OPF) Conventions:
 Use Case Modeling Guidelines, which documents the guidelines used to
develop the use case model specifying the functional requirements in this
specification.
 System Requirements Specification Content and Format Standard, which
specifies the content and format of this specification.
 System Requirements Specification Inspection Checklist, which is used
during the inspection of this specification.
 System Requirements Specification Template, which provides the
skeleton of this specification.
2.5 Specification Overview
This specification is organized into the following sections:

 Introduction, which introduces the specification for the RSS system to
its readers.
 System Overview, which provides a brief, high level description of the
RSS system including its definition, business goals, business objectives,
context, and capabilities.
 Functional Requirements, which specifies the functional system
requirements in terms of a use case model consisting of each external’s use
cases and use case paths.
 Data Requirements, which specifies the system data requirements in
terms of required data components.
 Quality Requirements, which specifies the required system quality
factors.
 Constraints, which documents required architecture, design, and
implementation constraints on the RSS system.
 Appendices, which define ancillary information including future
envisioned enhancements, open issues, TBDs, and assumptions.

SRS
28/07/2003
3 K-NOW System Overview
This section provides a high level description of the K-NOW (RSS system) system
including its definition, primary business goal, business objectives, context, and
capabilities.
3.1 Definition
The K-NOW (RSS system) system will be a global Web-based content and
knowledge marketplace that delivers customised packages of information at different
levels of complexity in response to user requests. It will also attach advertising
material to these packages, and offer the capacity to sell goods and services
through an interface TBD. It will also identify business, organisation and
management problems and opportunities on the basis of the users profiles in
accessing packages.
3.2 Business Goal
The business goal of the K-NOW (RSS system) system is to
Take advantage of RDF and Really Simple Syndication (RSS), XML, the Internet
and World Wide Web to radically improve the way in which information, training and
education is delivered to individuals and organisations.
Take advantage of the Internet and World Wide Web to radically improve the way in
which events information is delivered to individuals and organisations
3.3 Business Objectives
The business objectives of the RSS system are to provide the following business
benefits to its Users, Sellers/Advertisers, and Managers.
3.3.1 Knowledge User Business Benefits
The Knowledge User objectives for the RSS system are to:
 Help them identify key business and management problems at an

SRS
28/07/2003
 Develop customised training and information solutions for each of

these problems, ensuring relevance.
 Help them identify key business and management opportunities at an
 Develop customised training and information solutions to assist them in
taking advantage of each of these opportunities, ensuring relevance.
 Close the gap between obtaining and using information in business
and organisations by customising the information to specific problems and
opportunities.
 Make information and training more convenient by allowing them to
access information:
 Anytime (i.e., 24 hours a day and 7 days a week).
 Anywhere that the Knowledge Users have access to the Internet (e.g.,
at home, at work, and while travelling).
 Implement effective feedback systems to ensure content is updated
and or replaced frequently ensuring currency of content.
3.3.2 Product and Service Advertisers Business Benefits
The Product and Service Advertiser objectives for the RSS system are to:
 Minimize the costs of events and marketing by reducing the costs of
market research, advertising, channel management, etc.
 Maximize income by matching advertising to the needs and desires of
users as soon as those needs and desires become apparent
3.3.3 Event Advertiser Business benefits
The Event Advertiser Business Benefits for the RSS system are to:
 Match training and other informational events with the needs of RSS system
knowledge users
3.3.4 Knowledge Manager Business Benefits
The Knowledge User Manager objectives for the RSS system are to:

SRS
28/07/2003
 Provide them with a large customer base of staff, managers and

owners.
 Enable them to easily gather information on the problems faced by
potential Users.
 Enable them to identify and predict problems faced in particular User
segments
3.4 Context of the RSS System
This subsection documents the context of the RSS system in terms of the significant
externals with which it interacts. As illustrated in the following context diagram, the
K-NOW (RSS system) interfaces with several external actors and systems:
 Individuals and organisations can act as users in either the user or
advertiser role.
 System managers, security officers and user support agents are
employees who work for Connected Knowledge. Managers perform their
system management duties using the RSS system. Security Officers handle
security violations of the RSS system. User support agents provide user
support for the RSS system.
 The RSS system authorizes credit card purchases of items via the
authorization processor gateway.
Figure 1: K-NOW Context Diagram

SRS
28/07/2003
3.4.1 External Hardware

The RSS system interacts, either directly or indirectly, with the following significant
external hardware:
Client Hardware:
Employee Workstations, which are the personal computers used by employees to

perform their tasks.
User Client, which are the personal computers, personal digital assistants (PDAs),
and smart phones used by users to communicate with each other and with the
RSS system over the Internet.
Networks:
Internet, which is the global network used for communication among
employees, users, and the RSS system.
Local Area Network, which is the RSS systemC-internal local area
network used for communication among employees and the RSS
system.
Leased Phone Line, a dedicated telephone line connecting the RSS
system to the authorization processor gateway.
3.4.2 External Roles

client roles:
Employees, who are any actors who works for CK:

SRS
28/07/2003
System Managers, who are any CK employees who perform system

management functions using the RSS system.
Security Officers, who are any CK employees who respond to potential security
violations of the RSS system.
User Support Agents, who are any CK employees who provide human support
to the RSS system users.
Users, who are any individuals or organisations that buy information services in
the RSS system or advertise goods or services in the RSS system:
Knowledge Users, who are any users who use the RSS system to plan,
diagnose, or search for information within the RSS system.
User Managers, who are the managers of user accounts within the
organisations using the RSS system
Advertisers, who is any users who use the RSS system to advertise products or
services.
3.4.3 External Software
client software:
 Browser, which is the software tool that runs on employee and user
personal computers that allow them to communicate over the networks with
the RSS system.
3.4.4 External Systems
external systems:
 Authorization Processor Gateway, which is the server system that
provides a common interface to the numerous processors of credit card
payment authorizations.

SRS
28/07/2003
3.5 K-NOW Capabilities

This subsection provides a high-level overview of major capabilities of the RSS
system. Note that this subsection provides useful information for understanding the
following requirements, but does not contain specific testable requirements.
3.5.1 Summary of System Capabilities

3.5.1.1 Employee Capabilities
The RSS system will provide the following capabilities to employees:
 System Managers. The RSS system will enable System Managers

to:
Generate financial reports.
Update billing information and billing cycle .
Update the fee schedule.
Update user restrictions
Update news stories and links to RSS system content
Update content
Monitor user activity.
Monitor advertising activity
Interface with advertisers events data to provide feedback on

advertising effectiveness
 Knowledge Analysts. The RSS system will enable knowledge

analysts to:
Record user usage patterns.

SRS
28/07/2003
Interpret user usage patterns
Record user problem statement patterns
Identify the relationship between diagnostic results and user

information packages
Identify the relationship between diagnostic results and target results
Identify the relationship between diagnostic results and user problem

statement patterns
Identify the relationship between functional and process based

diagnostics
Identify the relationships between organisational, team and individual

diagnostics
 Security Officers. The RSS system will
Notify security officers of security violations.
Enable security officers to generate security violation reports.
 User Support Agents. The RSS system will enable user support
agents to:
Handle user inquiries.
Sanction users who violate the user agreement.
3.5.1.2 Users Capabilities
The RSS system will provide the following capabilities to users:

 Knowledge Users. The RSS system will enable Knowledge Users to:
Read user agreement

SRS
28/07/2003
Register
Read general information and user guidelines.
Register and maintain a user account:
Review and manage their user information (e.g., contact information,

credit card information).
Review and manage their account history (e.g., listings, transactions,

fee payments).
Review and annotate their individual feedback history.
Accept the RSS system privacy policy and user agreement.
Pay registration fees by credit card.
Receive confirmation of registration
Register for notification of new services
Read user guidelines
Access Help system
Plan career development (TBD)
Plan competence development (TBD)
Register feedback with regard to information characteristics including

 Relevance
 Timeliness
 Completeness
 Accuracy

SRS
28/07/2003
 Validity
 Usability.
Email other Knowledge Users, CK User Support Staff and Mentors
Take part in online chat with other Knowledge Users, CK User Support
Staff and Mentors.
Read news which links to RSS system information packages
Set up and use Web log software. (TBD)
Identify key performance targets at an organisational level
Identify key performance targets at a team level
Identify performance key targets at an individual level
Monitor all targets
 Corporate Knowledge Users
 Corporate Knowledge Users (CKUs) will employ the same services as

Knowledge users except for payment arrangements. CKUs will be
exempted from individual payment and instead be offered a prepaid
account

 Advertisers. The RSS system will enable advertisers to:
Register
Read advertiser guidelines.
Register and maintain a advertiser account:

SRS
28/07/2003
Review and manage their advertiser information (e.g., contact

information, credit card information).
Review and manage their account history (e.g., listings, transactions,

fee payments).
Accept the RSS system privacy policy and user agreement.
Pay registration fees by credit card.
Register advertising on information packages which Knowledge Users

receive.
Match ongoing and recent events with Knowledge User data .
Review their account status.
Make inquiries regarding account.

.
3.5.1.3 Other Capabilities

 Authorization Processor Gateway. The RSS system will use the
authorization processor gateway to:
Request authorisation of credit card payments via a dedicated leased

telephone line.

SRS
28/07/2003
4 Functional Requirements
This section of the SRS specifies the functional requirements of the RSS system in
terms of use cases and their associated use case paths. The use case model is
primarily organized in terms of the externals that benefit from the use cases.
4.1 Summary Use Case Diagrams
The following use case diagrams summarize the functional requirements for the
RSS system:
 Employee Summary Use Case Diagram
 User Summary Use Case Diagram
Figure 2: Employee Summary Use Case Diagram
Figure 3: User Summary Use Case Diagram

SRS
28/07/2003

RSS System Requirements Specification1

Загружено:

Сведения о документе

Исходное описание:

Авторское право

Доступные форматы

Поделиться этим документом

Поделиться или встроить документ

Параметры публикации

Этот документ был вам полезен?

Это неприемлемый материал?

Авторское право:

Доступные форматы

RSS System Requirements Specification1

Загружено:

Авторское право:

Доступные форматы

K-NOW (Connected Knowledge) Document ID: Q-CK Version: 1.

System Requirements Specification (SRS)

Confidential © Connected Knowledge Ltd. 1

Confidential © Connected Knowledge Ltd. 2

Confidential © Connected Knowledge Ltd. 3

Confidential © Connected Knowledge Ltd. 4

Figure 11: User Support Agent Use Case Diagram..................................................6-3

Confidential © Connected Knowledge Ltd. 5

1 Miniworld for K-NOW

 A Service Package is the level of service available to a user

Confidential © Connected Knowledge Ltd. 6

1.1.2 Stages of the Project

The project will be completed in X stages.

 Evaluation of Web spider technology

 The coding and testing of the RSS aggregator

 The database design

 The creation of the registration system

 The coding for the website.

 The coding for the billing system

 The coding of the content for the website

1.1.3 Structure of the Website

Some functions within a section have sub-functions

1.1.4 High Level User Defined Functions of the Website

1.1.5 Mid level User Defined Function of the Website

Within these functions, there are several processes.

The first of these is a registration process

The second is a billing process

Confidential © Connected Knowledge Ltd. 8

1.1.5.1.1.1The Registration Process

1.1.5.1.1.2The Billing Process

1.1.5.1.1.3 The Broadcast Process

The broadcast process identifies and returns briefings, insights or programmes on

1.1.5.1.1.4The Diagnostic Process

Confidential © Connected Knowledge Ltd. 9

The diagnostic process gathers user information on processes and resources at an

This process identifies learning objects accessed by the user

1.1.5.1.1.5The Planning Process

The planning process gathers user information on processes and resources at an

1.1.5.1.1.6The Assessment Process

1.1.6 Reporting Function of the Website

For each user we track usage of each function

For each user we track personal or organizational details

We also track information packages used by each user

We also track results of diagnostics

1.1.7 Advertising Function of the Website

We track the delivery of advertising attachments to information packages

Confidential © Connected Knowledge Ltd. 10

We offer an anonymous interface whereby advertisers can compare customer

1.1.8 Management Function of the Website

1.2 Objectives of the Website

The User objectives for the RSS system are to:

Confidential © Connected Knowledge Ltd. 11

 Enable them to align staff development goals and targets with

The Advertiser objectives for the RSS system are to:

Confidential © Connected Knowledge Ltd. 12

2.1 Specification Definition

2.2 Specification Objectives

The objectives of this specification of the RSS system are to:

2.3 Intended Audiences

Confidential © Connected Knowledge Ltd. 13

 Architects, whose overall architecture must meet the requirements

This specification references or complies with the following documents:

Confidential © Connected Knowledge Ltd. 14