Proof of Concept Mobile Application Scoping Document

for Te Whare Wananga o Awanuiarangi

Prepared by: Date Approved: Version: Status:

Jackie Wharewera 0.1 DRAFT

Page 1 of 24

Document Information Project: Document Title: Location: Department: Owner:

Proof of Concept Mobile Application Development POC_Mobile_App_scoping Documentv0.1 Main Campus, 127 McAlister Street, Whakatane Information Technology Services Jackie Wharewera

Version History Date Ver. Description of Changes Author(s)

12 July 2010

0.1

Draft

Jackie Wharewera

Signoff for the Current Version Name Title Signature

Koro Wikeepa Humphrey Wikeepa Len Hetet Jackie Wharewera/Rajwinder Kaur

Provost Chief Information Officer Brand Manager Developers

Page 2 of 24

1 Introduction
1.1 Purpose

The purpose of this document is to scope a proof of concept [POC] to develop a mobile application that will enable access to online learning resources. e.g via iPhone, tablets, smart devices etc. In developing a proof of concept mobile application, our approach will be to: Allow teachers to access and collaborate and share relevant learning resources with their students. Students will be able to access teachers/lecturers, online learning resources anytime, anywhere, using any internet accessible devices. Supports teachers and students to share knowledge and discovery with groups/followers Inform the organisation of any changing business needs and IT non-functional operational requirements that may be impacted positively or negatively through lessons learnt from this POC will pilot the School of Iwi development programmes to validate and develop user requirements.

1.2

Key performance indicators

An effective proof of concept will be persuasive. It will: Demonstrate the business opportunity/problem to all stakeholders Provide sufficient detail to allow lower level component design Align to technology standards (is cost effective) and business strategy Meet some or all IT non-functional requirements Meet some of all of the functional requirements Align to the investment logic map key strategic outcomes.

1.3

Audience

The audience for this document includes: Information Technology Services to gain a detailed understanding of the project that allows the development to progress based on user requirements from a key stakeholder. Online Learning Board to give approval to progress the proof of concept to completion.

1.4

Architectural goals and constraints

1.4.1 Project Dependencies The success of the mobile application development is reliant on a number of other current or planned solutions and initiatives. These are summarised below Dependency an understanding of user needs from school of iwi development. Description To get an understanding of user needs and requirements for the development of the mobile app. Impact If we do not understand the user requirements, we will waste time developing an application that is irrelevant to the user and does not meet their needs. If we do not receive the required content within appropriate timeframes the success and Page 3 of 24

Agreeing the Systems SQL databases that will feed the content within the mobile

The application requires accurate content to make it functional

applications

Testing solution with at least 20 students/staff who have some form of smartphone/mobile device

getting students who have appropriate devices to test the solution

learning outcomes of the application may not be truly realised. Fail to gain the true value of lessons learnt.

1.4.2 Risks and Assumptions Risks and assumptions for the project are detailed below Risks May notWon't be able to deliver all of the required functionality Description TWWoA may not have the internal capacity to support and develop the desired or best suited solution. Investing too much time scoping out and documenting the needs of the project. Not investing enough time into understanding the full scope of the project and documenting findings. Impact Will get a poor product and in turn not realise the true value/benefits.. 1. Investing too much time scoping out and documenting the project needs and so may delay the go live date of application. 2. Not investing enough time understanding the full scope of the project and documenting the findings may affect the quality of the final solution and the ability of the solution to meet the needs of stakeholders. This may cause the go live date to be extended.

Time spent on development of a Detailed Design Document

Time factors

It may require more time to complete the development project than allocated or projected in the planning phase.

Assumptions Access to resources

Description The resources will be made available to complete the development of the application as detailed in this document.

IT support capacity

TWWoA has some of the technological capacity to internally develop and support the proof of concept, however, it would be beneficial to obtain some external mobile app developer resource who have experience in working in this space.

Impact If the resources are not made available the scope of the development may have to be downgraded or the go live POC date may have to be pushed back or the functionality of the application be downgraded. Any degradation in service may affect the ability for staff to complete their work related tasks effectively.

Page 4 of 24

1.4.3 Compliance TWWoA is required to comply with the Public Records Act; as such the development project and processes related to managing and maintaining the content provided by application will be default of accessing existing mission critical databases, comply with the Public Records Act.

1.5

Privacy Impact Assessment

The content and documents provided by the application will be publically available to the Wananga staff/students within the test group through the Wanangas enterprise federated identity management solution. The application is intended for staff/student use only during the proof of concept.

2
2.1

Business view
Overview

The Wananga has a strong desire to improve its online learning delivery, especially among its other wananga contemporaries and also as an international leader in indigenous research methodologies and pedagogy.. To this end, the development of a mobile application solution should be commissioned to provide ubiquitous access for staff and students to relevant expert subject content or persons associated with their paper or programme course material and information. Technology hardware and additional features are changing at such a rapid pace that some staff/students are unable to keep up with the changes. In some instances, students are not computer literate enough to advance as quickly as their peers who are technology savvy and very computer literate.

2.2 Drivers
Key drivers and objectives for the development of the mobile application are: Drivers / Objectives Improve staff and student experience to access relevant authorised online learning resources attached to a course or programme of study underway. Support international learners access to relevant online learning content, subject matter experts, subject matter material and information. Description Develop a mobile application framework that can integrate and leverage access to relevant learning resources aligned to a students study/programme or course.

Interested parties and stakeholders have access to accurate content.

Page 5 of 24

2.3

Scope and Context

2.3.1 In Scope The Business Scope for the project: Scope Includes Development of a mobile application framework using C# and C++ along with Xcode to support parameter driven functionality. Uses Single sign-on capability Proof of Concept user requirements extracted from School of Iwi Development Provision of test environment to support the proof of concept and the test users Use of Wananga new website CSS style sheets to provide Look and Feel design. Proof of concept will run for one month, with the intent of capturing lessons learnt.

2.3.2 Out of Scope Scope Excludes Design concepts will need be included from the POC to develop the final mobile application Developing any learning resources specific to the needs of the mobile application. Improving business processes during the proof of concept.

2.3.3 Business Context View Business Context View of the mobile device application identifies four key high-level communities of users: Student user group (internal to New Zealand) International student user group (external to New Zealand) 3 xs SIDs staff initially IT Developer

2.4

Functional requirements

2.4.1 High Level Functional Requirements A summary of the high level functional requirements is provided in Architectural Decision Register A.1 and Appendix B.1 of this document. 2.4.2 Detailed Functional Requirements A summary of the detailed requirements is provided in Architectural Decision Register A.2 and Appendix B.2 of this document.

2.5

Non-Functional requirements

A summary of the non-functional requirements is provided in Architectural Decision Register A.3 and Appendix B.3. Page 6 of 24

3 Conceptual view
The conceptual view provides further detail against the in-scope requirements.

3.1

Business solution overview

The Wananga employs a number of enterprise technology solutions to support the organisations Operational and Academic deliverables. There are 7 key mission critical solutions to support the organisation and they are; 1. 2. 3. 4. 5. 6. ARTENA Student Management solution. Great Plains - Financial Management and Reporting System Frontier Soft Payroll and HR System CRM 2007 runs Student enquiries, Help Desk Services, Operation/Building facilities eWananga Online student learning solution which includes Website and intranet. Network This supports VOIP, ultrafast broadband, virtual networks, Video Conferencing via KAREN bridge, thin-client technology and enterprise wifi network. 7. Virtualised Infrastructure ADFS, Virtual Servers, Citrix, Comvault Backup.

None of Tthe first 5 solutions do not integrate seamlessly and cleanly with one another. All information can be shared manually with each solution if need be. Manual processes are prone to high risk of misinterpretation and or duplication/triplication of data across a number of repositories, ultimately loosing the value of a "single source of truth".. eWananga is fast becoming the dominant solution for delivering online education to distance learners. At this stage none of the solutions are integrated enough to unify and present information on a user centric basis. For example if a user accesses the Wananga systems from one of its three sites or main campus the users authenticated login should be sufficient enough to present a students information relevant to their study programme. Included in that presentation, could be a widget that allows the student to see their current marks based on assignments finished to date, covering that academic year only, their ratio of class attendance vs online study, number of readings that are completed according to their course requirements and so on, etc. It is expected the mobile application will overtime provide effective access through the Wanangas ADFS to information and supporting materials relating to relevant authenticated users and can be appropriately presented. Key services may include: Content from eWananga including, text, images, documents, RSS feeds and video. End-user services there are three categories of end user service to consider: o Content dissemination services to enable users to access information provided by SQL structured databases inside the Wananga infratsructure. o Registration services to enable users to register and pay for educational/additional resources outside of the Wananga to support their learning achievement. o Document storage services provision of cloud storage capability within the Wananga cloud services.

Page 7 of 24

4 Physical View
4.1 Deployment overview

The mobile application will be deployed via a download link through the Wananga main website made available to relevant authorised and authenticated test group users. 4.1.1 Authorisation / Security This section describes how the mobile application will access data with user pass through authentication. Challenge How will user authorisation be controlled? Solution description User authorisation/authentication via federated login technology allowing only relevant content to be passed to relevant authenticated authorised user. Products / technology Active Directory Federated Services login using [FTIM] Front-End Technology Identity Management] solution.

What aspects of the design ensure the protection and privacy of data and content presented by the mobile application What aspects of the solution will retain security and data integrity.

How will sensitive data, content and documents be protected?

Through the use of ADFS and FTIM

Presentation of data is confined to the boundaries of the Wananga Portal Solution Design.

ADFS, FTIM, Zoning of Network, Server Infrastructure and Restriction policies enforced via Sophos Security network tool.

4.1.2 Data / information All content and data presented by the mobile application will be available to authenticated authorised internal and external users. 4.1.3 Storage, backup and archive The Wananga backs up all its data using Comvault version 9.0, sited at the Bay of Plenty Regional Council datacentre at Toroa Street, Whakatane

5 Operational View
5.1 Disaster recovery/ failover

The mobile application does not need data recovery as it is a window dressing into the backend enterprise data repository solutions. Thereforer, the mobile application has dependency on the main backend infrastructure DR/failover processes.

Page 8 of 24

5.2

Volume/ growth

As part of the proof of concept it will be beneficial to see how much content the application can present all at once and until the user experience is performance or quality content control, degraded

Page 9 of 24

Page 10 of 24

Appendix A Architectural Decision Register

A.1
ID

AD-001 Method of user authentication delivery

AD-00 Mobile Application development Method of user authentication delivery Which is the best mechanism to deliver information up to the mobile application? Currently all relevant information sits within a number of repositories? That is, Active Directory [AD]/ADFS hosts the users name and password to get access to authorised areas of the Wanangas information systems. eWananga hosts a copy of the AD users name and possibly a separate and different password from the main AD password. Access to CRM information is based on ADFS capability. Access to Office365 resources is based on AD/ADFS authorisation. Library users use AD/ADFS to access their data.data Make eWananga point to ADFS for student authorisation into eWananga data, however, all learning resources would need to be flagged as relevant only to that user and so the user is unable to access anything but what they are authorised to access. The ability to improve the student or staff experience in accessing data through a single sign on process and thereby creating the appearance of a single source of truth. Deploy different and separate platform to create a unified authenticated view of information and data to user. Build a fit for purpose solution that presents the correct data. The mobile application supports those users and learners who are unable to attend classed physically but still want to access all relevant learning resources and maintain a standard of learning achievement.

Topic Subject Area Design Decision Issue or Problem Statement

Assumptions Motivation Alternatives Decision Justification

Page 11 of 24

A.2

AD-002 Compatibility functionality

ID Topic Subject Area Design Decision Issue or Problem Statement Assumptions

AD-002 Mobile Application development Compatibility functionality. i.e Tablets, iPhones, Smart phones/Devices etc The application needs to work on any device using IOS6, Windows8, Android. The solution may need additional backend functional parameter features to allow the application to run on any device using any of the above OSs. Users will want a simple and easy experience where they dont have to worry about the technology causing problems, so they can focus on their learning achievements. Also, users can upload their assignments through this application and placed in relevant repository within the cloud. Give the user confidence Comply with legal requirements Provide transparency and accountability Align with TWWoA Quality investment principles Cost vs. Benefit

Motivation

Alternatives Decision Justification

Back to a web browser on a computer but requires more back end development at an infrastructure level. Develop backend using C## and C+ with Xcode and HTML5 to maximise the best possible outcome. The mobile application supports those users and learners who are unable to attend classed physically but still want to access all relevant learning resources and maintain a standard of learning achievement.

Page 12 of 24

A.3

AD-003 Device Recognition Capability

ID Topic Subject Area Design Decision Issue or Problem Statement Assumptions Motivation

AD-003 Mobile Application development Device Recognition capability The device needs to recognise when peers from the same course, including lecturer are online and can be connected to. The device needs to recognise when peers from the same course, including lecturer are online and can be connected to making use of the devices, camera for video, content presentation between each participant, instant chat, adjust for bandwidth experience and provide notification if and when connection speeds degrade and removing video while retaining audio and content presentation. The solution must make use of the power of the programming language to access the relevant header files that support this capability. Cost vs. Benefit Ease of use Support user requirements

Alternatives Decision Justification

Manual Development tools will provide this capability. i.e. C##, C+ and Xcode, HTML5 Cost and effectiveness Effectiveness of the solution Ease of use Ability to easily and quickly integrate maximising the use of the Wananga 10Gb backbone and KAREN 1GB network.

Page 13 of 24

A.4

AD-004 Integration with existing mobile applications

ID Topic Subject Area Design Decision Issue or Problem Statement Assumptions Motivation Alternatives Decision Justification

AD-004 Mobile Application development Integration with Social media tools, google earth and reputable established reliable mobile device applications. Does the application need to present these tools built within the framework of the solution as part of the overall solution This functionality operates in the same way a portal operates. Essentially allowing the users single student logon could also bring through their facebook, twitter and or other updates into this solution. Users today are across multiple sets of information at any one time. Users will want to post information to their respective sites. Cost vs. Benefit, ease of use for the student None Not urgent for this part of the proof of concept. Good user centric experience.

Appendix B Requirements Traceability Matrix

B.1

High Level Functional Requirements

The following table describes how the intended application will support the high level functional requirements. Ref. Name Managing learning Content HLFR 1.1 Accessing relevant content HLFR 1.2 Users content Description The mobile application must enable authorised users to access relevant content assigned to their appropriate approved course. Users can post documents, notes, quick videos of themselves, Supporting Component1 eWananga repository, ADFS, FTIM Xcode, HTML5, ADFS, FTIM

Page 14 of 24

Ref. HLFR 1.3

Name Delete content

HLFR 1.4

Search for content

Description presentations and or relevant material with ease. The application must enable authorised users to delete content from their own repository however, shared resources cannot be deleted. Users should be able to search for information within their own relevant portal learning space Notification of new information pushed to the users The application must provide a mechanism for distributing or accessing news items to users that are posted to the Wanangas main website or intranet and considered relevant for the user to read. The application must provide a mechanism for a calendaring function. The solution should use the Wananga Exchange calendar as the single source of truth. The application will provide authorised users with a way in which they can highlight key information. The application must enable administrators and users to create notices and blog entries within the website, this must allow for other website users to view the notices and blog entries. The creator must have the ability to edit and delete their notice. The application will support the delivery of video content.

Supporting Component1 eWananga repository, Office365 online, HTML5, Xcode, ADFS, FTIM eWananga repository, HTML5, Xcode, Office365, ADFS, FTIM eWananga repository, HTML5. Xcode, Office365, ADFS, FTIM eWananga repository, Wananga CRM website, Office365, Xcode, HTML5, Pikimaira, ADFS, FTIM eWananga repository, Wananga Exchange, Xcode, HTML5, ADFS, FTIM eWananga repository, Wananga Exchange, Xcode, HTML5, ADFS, FTIM eWananga repository, Wananga Exchange, Wananga CRM website, Office365, Xcode, HTML5, Pikimaira, ADFS, FTIM eWananga repository, KAREN bridge, Wananga CRM website, Office365, Xcode, HTML5, Pikimaira, ADFS, FTIM eWananga repository, Wananga CRM website, Office365, Xcode, HTML5, Pikimaira, ADFS, FTIM, eWananga repository, Wananga CRM website, Office365, Xcode, HTML5, Pikimaira, ADFS, FTIM, eWananga repository, Wananga CRM website, Office365, Xcode, HTML5, Pikimaira, ADFS, FTIM,

Communication HLFR 2.1 Deliver content HLFR 2.2 News

HLFR 2.3

Calendar

HLFR 2.4 HLFR 2.5

Key Messages ,features and highlights Notice board / Blog

HLFR 2.6

Video

HLFR 2.7

Library of documents

HLFR 2.8

Search for content and cut and paste/capture for content contribution Gather Information HLFR 3.1 Gather user information

The application will enable documents/files to be stored in a library and can be published on the website. E.g. Word, Excel, PDFs, images and text files. The application must enable users to search for web content entering a search query and having a list of relevant results presented to select from. The application must provide a mechanism for a gathering user information i.e. web based form. This information must be stored in a secure user database.

Page 15 of 24

B.2

Detailed Functional Requirements

The following table describes how the solution components will support the high level functional requirements. Ref. Name Create and Edit Content CON01 Create social media content CON02 Edit social media content CON03 Select Authoring Template Description The application will enable authorised users to create content from authoring templates for publication into a student portal. The application will enable authorised users to edit their social media content. The application will enable users to author content. Supporting Component eWananga repository, Wananga CRM website, Office365, Xcode, HTML5, Pikimaira, ADFS, FTIM, eWananga repository, Wananga CRM website, Office365, Xcode, HTML5, Pikimaira, ADFS, FTIM, eWananga repository, Wananga CRM website, Office365, Xcode, HTML5, Pikimaira, ADFS, FTIM,

Approve Content APP01 Submit for approval

APP02

Approval decision

The application will enable content authors to submit their content for publication approval by their content owner who is responsible for the accuracy and quality of the content. The application will enable a way in which authorised users can approve or reject content which has been submitted for approval. Approved content will move to an APPROVED state. Rejected content will move to the DRAFT or REJECTED state. The application will email the content author of content which has been approved or rejected. The application will enable content authors to submit their content for publication approval by their content owner who is responsible for the accuracy and quality of the content. The application will enable a way in which authorised users can approve or reject content which has been submitted for approval. Approved content will move to an APPROVED state. Rejected content will move to the DRAFT or REJECTED state.

APP03 APP01

Approval notification Submit for approval

APP02

Approval decision

Actioning Published Content ACT01 Expiry date ACT02 Auto expire Content

The application will enable authorised users to specify an Expiry date for content when it is in DRAFT state. The solution will remove the content published on the website Page 16 of 24

Ref.

Name

ACT03

Manually expire content

ACT04

View expired content

ACT05 ACT6

Edit Expiry date Version control

ACT7

Update published content

Description when the Expiry date has passed. (i.e. remove the content from the website but remain stored in the backend solution). The solution will enable authorised users to manually expire content. (i.e. remove the content from the website but remain stored in the backend solution). The solution will enable authorised users to view expired content from within the backend solution to align with the Public Records Act 2005. The solution will enable authorised users to edit the Expiry date of content when it is in PUBLISHED state. The solution will manage version control for edited, published and updated content. Example: a new version is to be created when published content is updated. The solution will allow for a version of published content to be edited, and will manage the replacement of the published content with the edited content. The solution needs to: Expire the original content; Version control the updated content; and Ensure that links to the edited page remain working as they did to the expired page.

Supporting Component

Delete Content DEL01 Delete content Publish Content PUB01 Instant publication Types of Content TYPE01 General content TYPE02 Policies and guidelines

The application will enable authorised users to delete content. The application will allow for the instant publication of content. The application will enable the publication of text, images and documents onto the website. The application will enable the publication of policies and guidelines relating to TWWoA conferences. This will be moderately static content. The application will enable news articles to be published on the Website. The application will enable hyperlinks to be included in content published. The conference portal website will enable documents to be stored in a document library which can be accessed by all Page 17 of 24

TYPE03 TYPE04 TYPE05

News Hyperlinks Library of documents

Ref. TYPE06

Name Downloadable files

Description users. The application will allow content to be published and downloadable by website users for the following file types: Microsoft Word, Microsoft PowerPoint, Microsoft Excel, Adobe PDF, jpeg. The solution will enable viewing of multimedia files within the website. The solution must be able to store and present content in the following forms: Flash video Flash audio MPEG-4 formats Windows Media Player format mp3 files

Supporting Component

TYPE07

Multimedia

Event Timetables EVNT01 Listing of events EVNT02 EVNT03 Events View calendar

The application will enable authorised users to create, edit and delete calendars. The application will enable authorised users to create, edit and delete events to be listed on calendars The application will enable website users to view calendar listings, and select a calendar entry which will then display the full event details. The application will enable all users to access their main data repository easily The application will enable users to navigate and view content within relevant systems. The solution will enable content users to view multi-media files (i.e. video streaming) and be able to control their viewing/listening of multimedia files by being able to play, pause, stop, fast forward, and rewind the media. The solution will enable content to be printed as a printer friendly version. ie. strips out non-essential visual content (eg. navigation menus) and also add information for the page title, URL, and page number of total pages (e.g. page 5 of 10)

Browsing and Using Content USEIT01 Accessing website USEIT02 USEIT03 Navigate and view content Multimedia viewing

USEIT04

Printer friendly version

Page 18 of 24

Ref.

Name

Description This requirement is not required for the homepage. The conference portal website will enable website users to perform a simple search on published content. The solution will display the following information about content that is returned in the search results The solution will enable users to select an item from the search results and be presented with that content.

Supporting Component

Content Search SRC01 Simple content search SRC02 SRC03 Search results View search result

User Responses RESP01 Enter feedback

The solution will enable users to enter text into fields specifically created to accept feedback. Noticeboard / Comments board / Blog Function NBCBBF01 Create notice / blog / The conference portal website will enable website users to comments create notices and messages on a 'noticeboard' which can then be viewed by other users. NBCBBF02 Edit/delete notice / blog / The conference portal website will enable notices published on comments the notice board to be edited or deleted by its creator. NBCBBF03 View notice / blog / The conference portal website will list all active notices. comments NBCBBF04 Expire notice / blog / The solution will expire notices (i.e. not flagged as active or comments displaying on noticeboard unless viewing all notices) once the notices Expiry Date has passed. Homepage HP01 Homepage design The solution will incorporate the functionality listed in this table onto the Website homepage, with the given Homepage presence number to determine the level of prominence on the homepage. Where 1 is the highest presence and 3 is the lowest. HP02 Logo / title / name The solution will place the TWWoA logo, Website name and title on the homepage. The TWWoA logo will be a hyperlink to the homepage. This item will also have a permanent presence on all website pages. Homepage presence: 1. The solution will display primary navigation options which users can select from the homepage and then follow the site Page 19 of 24

HP03

Primary Navigation

Ref.

Name

Description navigation structure to find areas of interest. This item will also have a permanent presence on all website pages. Homepage presence: 1. The solution will enable users to search for web content from the homepage. This item will also have a permanent presence on all website pages. Homepage presence: 1. The solution will allow for informational banners to deliver key messages.

Supporting Component

HP04

Content Search

HP05

Informational Banners

Homepage presence: 2 Web Content Management Workflow Processes WFW01 Maintain workflows The solution will enable authorised users to create, edit and delete system workflows which will apply to authoring templates. WFW02 Deletion and change check The solution will ensure that workflows cannot be deleted or edited if it will affect content that is currently using that workflow. E.g. if content is awaiting approval in one workflow, and there is an attempt to alter that workflow to remove the approval process, the system will not allow this change and will inform the user of why. The solution will be able to send emails to content authors or content owners at specific steps within a workflow. The solution will inform users of any content workflow which is awaiting their action. E.g. content owners need to be notified within the system if content is awaiting their approval. The solution will enable a quick publish workflow to be used which will not require approval before publishing. The solution will enable approval workflows to be used where content will require approval before it can be published. The solution will report on the top visited content, and least Page 20 of 24

WFW03 WFW04

Email notification Content awaiting action

WFW05 WFW06

Quick publish workflow Approval workflow

Analytic Reports AN.REP01 Top and least visited

Ref.

Name content

Description visited content within a given date period. The number of top visited and least visited content will be able to be specified within a given date range. The solution will report on unique users to a given piece of content within a given date range. The solution will be able to report on the most commonly used search terms entered, being able to specify the top N number of search terms to report on. The solution will report on search terms that were queried but produced no results The solution will report on the totals of pages views per visit. The solution will provide a report on navigation patterns of how users navigate to access content The solution will report on peak traffic times (by day of week and time) of when content has been viewed within a given date range. E.g. give a report over the last 2 weeks. The solution will provide traffic comparisons for content specified time periods (e.g. weekly, monthly and yearly) and provide traffic statistics for individual pieces of content and user activity. The solution will report on the following information of users accessing the website within a given timeframe: based on location they are viewing the content from Browsers type and version accessing via Operating system

Supporting Component

AN.REP02 AN.REP03

Report unique visits Top search terms

AN.REP04 AN.REP05 AN.REP06 AN.REP07

Failed search terms Page views per visit Navigation patterns Peak traffic times

AN.REP08

Comparisons of traffic

AN.REP09

User location

AN.REP10

Last viewed date

Screen resolution The solution will be able to report on content that was last viewed within a given date range. Such a report will assist in finding out if the content needs to be placed in a different place on the website and not easily found The solution will report on any broken:

Content Management Report CM.REP07 Broken links

Page 21 of 24

Ref.

Name

Description hyperlinks on the website links to an anchor within content

Supporting Component

Other Functional Requirements OTH01 Superuser

The solution will enable authorised users (well use the term superuser) to have access to perform all functions and activities within the application.

B.3

Non-Functional Requirements

The following table describes how the solution components will support the non-functional requirements. Ref. Usability US.1 Name Consistency Description The conference portal website will have a new look and feel that will be applied to it, eventually the parent TWWoA website will have the same branding and look and feel applied to it, therefore it will maintain consistency of the TWWoA branding guidelines. The conference portal website will ensure that users have a clear sense of where they are within the conference website. The conference portal website will ensure that users can go back through the pages viewed in that website session in the reverse order. The website needs to be viewed by all stakeholders and users. The solution must allow for compatibility across all browsers where possible. At the time of writing this document, the major browsers that we are considering are: For Windows: Internet Explorer 0.7, 0.8 , 0.9, Firefox 2.0, 3.0, Google Chrome 0.4 For Mac: Safari 4, Firefox 2.0, 3.0, Google Chrome 0.4 The solution will have a new theme created, it will align with Page 22 of 24 Architectural Impact

US.2 US.3

Site location Back and forward

US.4

Browsers

US.5

Theme

Ref. US.6

Name NZ government web standards

Description branding guidelines that are currently being developed The solution will align with the NZ Government Web Standards 2.0 (published March 2009) where possible.

Architectural Impact

Availability AV.1 Availability - planned AV.2 AV.3 Back up processes Maintenance windows

The conference portal website is expected to be available 97% of an average 7.5 hour working day Backups of the website will be performed at least once a day. The solution will provide for a maintenance window of up to 2 hours each week outside of employee working hours on the same day (day of week to be confirmed). The solution will support x concurrent website users with the ability to scale as necessary. The solution will support the initial number of x backend users with the ability to scale as necessary. Joomla will ensure that the website administrators and backend users are authenticated. Joomla will ensure that the website administrators and backend users are authorised. Joomla will enable all users for the website to view all content.

Scalability SCA.1 SCA.2 Security SCR.1 SCR.2 SCR.3

Website User numbers Backend user numbers

Authentication Authorisation

Viewing of content in the Infrastructure Solution Recoverability RCV.1 Recoverability

The solution will recover to an operational level after service failure (e.g. unplanned outage) as per the website requirements.

Page 23 of 24

Page 24 of 24