POC Mobile App Scoping Documentv0.1

8/13/2019 POC Mobile App Scoping Documentv0.1

1/24


2/24

Document Information

Project: Proof of Concept Mobile Application Development

Document Title: POC_Mobile_App_scoping Documentv0.1

Location: Main Campus, 127 McAlister Street, Whakatane

Department: Information Technology Services

Owner: Jackie Wharewera

Version History

Date Ver. Descript ion of Changes Author(s)

12 July 2010 0.1 Draft Jackie Wharewera

Signoff for the Current Version

Name Title Signature

Koro Wikeepa Provost

Humphrey Wikeepa Chief Information Officer

Len Hetet Brand Manager

JackieWharewera/RajwinderKaur

Developers


3/24

1 Introduction

1.1 Purpose

The purpose of this document is to scope a proof of concept [POC] to develop a mobile applicationthat 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 operationalrequirements that may be impacted positively or negatively through lessons learnt from thisPOC

will pilot the School of Iwi development programmes to validate and develop userrequirements.

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 allowsthe 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


4/24

applications learning outcomes of theapplication may not be truly

realised.Testing solution with at least 20students/staff who have someform of smartphone/mobiledevice

getting students who haveappropriate devices to test thesolution

Fail to gain the true value oflessons learnt.

1.4.2 Risks and Assumptions

Risks and assumptions for the project are detailed below -

Risks Description Impact

May notWon'tbe able to deliverall of the required functionality

TWWoA may not have theinternal capacity to support anddevelop the desired or bestsuited solution.

Will get a poor productand inturn not realise the truevalue/benefits..

Time spent on development of aDetailed Design Document

Investing too much time scopingout and documenting the needsof the project.

Not investing enough time intounderstanding the full scope ofthe project and documentingfindings.

1. Investing too much timescoping out and documentingthe project needs and so maydelay the go live date ofapplication.

2. Not investing enough timeunderstanding the full scope ofthe project and documenting thefindings may affect the quality ofthe final solution and the abilityof the solution to meet theneeds of stakeholders.

Time factors It may require more time tocomplete the developmentproject than allocated orprojected in the planning phase.

This may cause the go live dateto be extended.

Assumptions Descript ion ImpactAccess to resources The resources will be made

available to complete thedevelopment of the applicationas detailed in this document.

If the resources are not madeavailable the scope of thedevelopment may have to bedowngraded or the go livePOCdate may have to be pushedback or the functionality of the


5/24

1.4.3 Compliance

TWWoA is required to comply with the Public Records Act; as such the development project andprocesses related to managing and maintaining the content provided by application will be default ofaccessing 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 Wanangastaff/students within the test group through the Wanangas enterprise federated identity managementsolution. The application is intended for staff/student use only during the proof of concept.

2 Business view

2.1 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 methodologiesand pedagogy..

To this end, the development of a mobile application solution should be commissioned to provideubiquitous access for staff and students to relevant expert subject content or persons associated withtheir 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 peerswho are technology savvy and very computer literate.

2.2 Drivers

Key drivers and objectives for the development of the mobile application are:

Drivers / Objectives Descripti onImprove staff and student experienceto access relevant authorised onlinelearning resources attached to acourse or programme of studyunderway.

Develop a mobile application framework that can integrateand leverage access to relevant learning resources alignedto a students study/programme or course.

Support international learners access Interested parties and stakeholders have access to accurate


6/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 parameterdriven 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 conceptswill 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 ofusers:

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 Funct ional Requirements

A summary of the high level functional requirements is provided in Architectural Decision Register A 1


7/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 organisationsOperational and Academic deliverables.

There are 7 key mission critical solutions to support the organisation and they are;

1. ARTENA Student Management solution.2. Great Plains- Financial Management and Reporting System3. Frontier Soft Payroll and HR System4. CRM 2007 runs Student enquiries, Help Desk Services, Operation/Building facilities5. eWananga Online student learning solution which includes Website and intranet.6. 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 informationcan be shared manually with each solution if need be. Manual processes are prone to high risk ofmisinterpretation and or duplication/triplication of data across a number of repositories, ultimatelyloosing 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 usercentric basis. For example if a user accesses the Wananga systems from one of its three sites ormain campus the users authenticated login should be sufficient enough to present a studentsinformation relevant to their study programme. Included in that presentation, could be a widget thatallows the student to see their current marks based on assignments finished to date, covering thatacademic year only, their ratio of class attendance vs online study, number of readings thatarecompleted according to their course requirements and so on, etc.

It is expected the mobile application will overtime provide effective access through the WanangasADFS to information and supporting materials relating to relevant authenticated users and can beappropriately presented. Key services may include:

Content from eWananga including, text, images, documents, RSS feeds and video.

E d i th th t i f d i t id


8/24

4 Physical View

4.1 Deployment overview

The mobile application will be deployed via a download link through the Wananga main website madeavailable 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 throughauthentication.

Challenge Solution description Products / technology

How will user authorisation becontrolled?

User authorisation/authenticationvia federated login technologyallowing only relevant content to bepassed to relevant authenticatedauthorised user.

Active DirectoryFederated Services loginusing [FTIM] Front-EndTechnology IdentityManagement] solution.

What aspects of the design ensurethe protection and privacy of dataand content presented by themobile application

How will sensitive data, content anddocuments be protected?

Through the use ofADFS and FTIM

What aspects of the solution willretain security and data integrity.

Presentation of data is confined tothe boundaries of the WanangaPortal Solution Design.

ADFS, FTIM, Zoning ofNetwork, ServerInfrastructure andRestriction policies

enforced via SophosSecurity network tool.

4.1.2 Data / information

All content and data presented by the mobile application will be available to authenticated authorisedinternal 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 RegionalCouncil datacentre at Toroa Street, Whakatane


9/24

5.2 Volume/ growth

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


10/24


11/24

Page 11of 24

Appendix A Architectural Decis ion Register

A.1 AD-001 Method of user authenticat ion delivery

ID AD-00

Topic Mobile Application development

Subject Area Method of user authentication delivery

Design Decision Which is the best mechanism to deliver information up to the mobile application?

Issue or ProblemStatement

Currently all relevant information sits within a number of repositories? That is, Active Directory [AD]/ADFS hosts the users name and passwordto get access to authorised areas of the Wanangas information systems. eWananga hosts a copy of the AD users name and possibly aseparate and different password from the main AD password. Access to CRM information is based on ADFS capability. Access to Office365resources is based on AD/ADFS authorisation. Library users use AD/ADFS to access their data.data

Assumptions Make eWananga point to ADFS for student authorisation into eWananga data, however, all learning resources would need to be flagged asrelevant only to that user and so the user is unable to access anything but what they are authorised to access.

Motivation 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.

Al ternat ives Deploy different and separate platform to create a unified authenticated view of information and data to user.

Decision Build a fit for purpose solution that presents the correct data.

Justification The mobile application supports those users and learners who are unable to attend classed physically but still want to access allrelevant learning resources and maintain a standard of learning achievement.


12/24

Page 12of 24

A.2 AD-002 Compatibi lity funct ionali ty

ID AD-002


Subject Area Compatibility functionality. i.e Tablets, iPhones, Smart phones/Devices etc

Design Decision The application needs to work on any device using IOS6, Windows8, Android.

Issue or Problem

Statement

The solution may need additional backend functional parameter features to allow the application to run on any device using any of the above

OSs.

Assumptions Users will want a simple and easy experience where they dont have to worry about the technology causing problems, so they can focus ontheir learning achievements. Also, users can upload their assignments through this application and placed in relevant repository within thecloud.

Motivation Give the user confidence

Comply with legal requirements

Provide transparency and accountability

Align with TWWoA Quality investment principles

Cost vs. Benefit

Al ternat ives Back to a web browser on a computer but requires more back end development at an infrastructure level.

Decision Develop backend using C## and C+ with Xcode and HTML5 to maximise the best possible outcome.

Justification The mobile application supports those users and learners who are unable to attend classed physically but still want to access allrelevant learning resources and maintain a standard of learning achievement.


13/24

Page 13of 24

A.3 AD-003 Device Recognit ion Capabil ity

ID AD-003


Subject Area Device Recognition capability

Design Decision The device needs to recognise when peers from the same course, including lecturer are online and can be connected to.Issue or ProblemStatement

The device needs to recognise when peers from the same course, including lecturer are online and can be connected to making use of thedevices, camera for video, content presentation between each participant, instant chat, adjust for bandwidth experience and providenotification if and when connection speeds degrade and removing video while retaining audio and content presentation.

Assumptions The solution must make use of the power of the programming language to access the relevant header files that support this capability.

Motivation Cost vs. Benefit

Ease of use

Support user requirements

Al ternat ives Manual

Decision Development tools will provide this capability. i.e. C##, C+ and Xcode, HTML5

Justification 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.


14/24

Page 14of 24

A.4 AD-004 Integration wi th exis ting mobi le applicat ions

ID AD-004


Subject Area Integration with Social media tools, google earth and reputable established reliable mobile device applications.

Design Decision Does the application need to present these tools built within the framework of the solution as part of the overall solution

Issue or ProblemStatement

This functionality operates in the same way a portal operates. Essentially allowing the users single student logon could also bring through theirfacebook, twitter and or other updates into this solution.

Assumptions Users today are across multiple sets of information at any one time. Users will want to post information to their respective sites.

Motivation Cost vs. Benefit, ease of use for the student

Al ternat ives None

Decision Not urgent for this part of the proof of concept.

Justification Good user centric experience.

Appendix B Requirements Traceabil it y Matrix

B.1 High Level Functional Requirements

The following table describes how the intended application will support the high level functional requirements.

Ref. Name Descript ion Support ing Component1

Managing learning Content

HLFR 1.1 Accessing relevant content The mobile application must enable authorised users to accessrelevant content assigned to their appropriate approved course.

eWananga repository, ADFS, FTIM

HLFR 1.2 Users content Users can post documents, notes, quick videos of themselves, Xcode, HTML5, ADFS, FTIM


15/24


16/24

Page 16of 24

B.2 Detailed Functional Requirements

The following table describes how the solution components will support the high level functional requirements.

Ref. Name Descript ion Support ing Component

Create and Edit Content

CON01 Create social mediacontent

The application will enable authorised users to create contentfrom authoring templates for publication into a student portal.

eWananga repository, Wananga CRM website,Office365, Xcode, HTML5, Pikimaira, ADFS, FTIM,

CON02 Edit social media content The application will enable authorised users to edit their socialmedia content.

eWananga repository, Wananga CRM website,Office365, Xcode, HTML5, Pikimaira, ADFS, FTIM,

CON03 Select Authoring Template The application will enable users to author content. eWananga repository, Wananga CRM website,Office365, Xcode, HTML5, Pikimaira, ADFS, FTIM,

Approve ContentAPP01 Submit for approval The application will enable content authors to submit their

content for publication approval by their content owner who isresponsible for the accuracy and quality of the content.

APP02 Approval decision The application will enable a way in which authorised users canapprove or reject content which has been submitted forapproval.

Approved content will move to an APPROVED state.

Rejected content will move to the DRAFT or REJECTED state.

APP03 Approval notification The application will email the content author of content whichhas been approved or rejected.

APP01 Submit for approval The application will enable content authors to submit theircontent for publication approval by their content owner who isresponsible for the accuracy and quality of the content.

APP02 Approval decision The application will enable a way in which authorised users can

approve or reject content which has been submitted forapproval.

Approved content will move to an APPROVED state.

Rejected content will move to the DRAFT or REJECTED state.

Actioning Published Content

ACT01 Expiry date The application will enable authorised users to specify anExpiry datefor content when it is in DRAFT state.

ACT02 Auto expire Content The solution will remove the content published on the website


17/24

Page 17of 24


when the Expiry datehas passed. (i.e. remove the contentfrom the website but remain stored in the backend solution).

ACT03 Manually expire content The solution will enable authorised users to manually expirecontent. (i.e. remove the content from the website but remainstored in the backend solution).

ACT04 View expired content The solution will enable authorised users to view expiredcontent from within the backend solution to align with the PublicRecords Act 2005.

ACT05 Edit Expiry date The solution will enable authorised users to edit the Expiry dateof content when it is in PUBLISHED state.

ACT6 Version control The solution will manage version control for edited, publishedand updated content. Example: a new version is to be createdwhen published content is updated.

ACT7 Update published content The solution will allow for a version of published content to beedited, and will manage the replacement of the publishedcontent 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 didto the expired page.

Delete Content

DEL01 Delete content The application will enable authorised users to delete content.

Publish Content

PUB01 Instant publication The application will allow for the instant publication of content.

Types o f Content

TYPE01 General content The application will enable the publication of text, images and

documents onto the website.TYPE02 Policies and guidelines The application will enable the publication of policies and

guidelines relating to TWWoA conferences. This will bemoderately static content.

TYPE03 News The application will enable news articles to be published on theWebsite.

TYPE04 Hyperlinks The application will enable hyperlinks to be included in contentpublished.

TYPE05 Library of documents The conference portal website will enable documents to bestored in a document library which can be accessed by all


18/24

Page 18of 24


users.

TYPE06 Downloadable files The application will allow content to be published anddownloadable by website users for the following file types:

Microsoft Word, Microsoft PowerPoint, Microsoft Excel,

Adobe PDF, jpeg.

TYPE07 Multimedia The solution will enable viewing of multimedia files within thewebsite. The solution must be able to store and present contentin the following forms:

Flash video

Flash audio

MPEG-4 formats

Windows Media Player format

mp3 files

Event Timetables

EVNT01 Listing of events The application will enable authorised users to create, edit anddelete calendars.

EVNT02 Events The application will enable authorised users to create, edit anddelete events to be listed on calendars

EVNT03 View calendar The application will enable website users to view calendarlistings, and select a calendar entry which will then display thefull event details.

Browsing and Using Content

USEIT01 Accessing website The application will enable all users to access their main datarepository easily

USEIT02 Navigate and view content The application will enable users to navigate and view content

within relevant systems.USEIT03 Multimedia viewing The solution will enable content users to view multi-media files

(i.e. video streaming) and be able to control theirviewing/listening of multimedia files by being able to play,pause, stop, fast forward, and rewind the media.

USEIT04 Printer friendly version The solution will enable content to be printed as a printerfriendly 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)


19/24

Page 19of 24


This requirement is not required for the homepage.

Content Search

SRC01 Simple content search The conference portal website will enable website users toperform a simple search on published content.

SRC02 Search results The solution will display the following information about contentthat is returned in the search results

SRC03 View search result The solution will enable users to select an item from the searchresults and be presented with that content.

User Responses

RESP01 Enter feedback The solution will enable users to enter text into fields specificallycreated to accept feedback.

Noticeboard / Comments board / Blog FunctionNBCBBF01 Create notice / blog /comments

The conference portal website will enable website users tocreate notices and messages on a 'noticeboard' which can thenbe viewed by other users.

NBCBBF02 Edit/delete notice / blog /comments

The conference portal website will enable notices published onthe notice board to be edited or deleted by its creator.

NBCBBF03 View notice / blog /comments

The conference portal website will list all active notices.

NBCBBF04 Expire notice / blog /

comments

The solution will expire notices (i.e. not flagged as active or

displaying on noticeboard unless viewing all notices) once thenotices Expiry Datehas passed.

Homepage

HP01 Homepage design The solution will incorporate the functionality listed in this tableonto the Website homepage, with the given Homepagepresence number to determine the level of prominence on thehomepage. Where 1 is the highest presence and 3 is thelowest.

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 thehomepage.

This item will also have a permanent presence on all websitepages.

Homepage presence: 1.

HP03 Primary Navigation The solution will display primary navigation options which userscan select from the homepage and then follow the site


20/24

Page 20of 24


navigation structure to find areas of interest.



HP04 Content Search The solution will enable users to search for web content fromthe homepage.



HP05 Informational Banners The solution will allow for informational banners to deliver keymessages.

Homepage presence: 2

Web Content Management Workflow Processes

WFW01 Maintain workflows The solution will enable authorised users to create, edit anddelete system workflows which will apply to authoring templates.

WFW02 Deletion and change check The solution will ensure that workflows cannot be deleted oredited if it will affect content that is currently using that workflow.E.g. if content is awaiting approval in one workflow, and there isan attempt to alter that workflow to remove the approvalprocess, the system will not allow this change and will inform theuser of why.

WFW03 Email notification The solution will be able to send emails to content authors or

content owners at specific steps within a workflow.WFW04 Content awaiting action The solution will inform users of any content workflow which isawaiting their action. E.g. content owners need to be notifiedwithin the system if content is awaiting their approval.

WFW05 Quick publish workflow The solution will enable a quick publish workflow to be usedwhich will not require approval before publishing.

WFW06 Approval workflow The solution will enable approval workflows to be used wherecontent will require approval before it can be published.

Analytic Reports

AN.REP01 Top and least visited The solution will report on the top visited content, and least


21/24


22/24

Page 22of 24


hyperlinks on the website

links to an anchor within content

Other Functional Requirements

OTH01 Superuser The solution will enable authorised users (well use the termsuperuser) to have access to perform all functions and activitieswithin the application.

B.3 Non-Funct ional Requirements

The following table describes how the solution components will support the non-functional requirements.

Ref. Name Descript ion Arch itectu ral Impact

Usability

US.1 Consistency The conference portal website will have a new look and feel thatwill be applied to it, eventually the parent TWWoA website will havethe same branding and look and feel applied to it, therefore it willmaintain consistency of the TWWoA branding guidelines.

US.2 Site location The conference portal website will ensure that users have a clearsense of where they are within the conference website.

US.3 Back and forward The conference portal website will ensure that users can go backthrough the pages viewed in that website session in the reverseorder.

US.4 Browsers The website needs to be viewed by all stakeholders and users. Thesolution must allow for compatibility across all browsers wherepossible. At the time of writing this document, the major browsersthat 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

US.5 Theme The solution will have a new theme created, it will align with


23/24

Page 23of 24

Ref. Name Descript ion Arch itectu ral Impact

branding guidelines that are currently being developed

US.6 NZ government webstandards

The solution will align with the NZ Government Web Standards 2.0(published March 2009) where possible.

Availabili ty

AV.1 Availability - planned The conference portal website is expected to be available 97% ofan average 7.5 hour working day

AV.2 Back up processes Backups of the website will be performed at least once a day.

AV.3 Maintenance windows The solution will provide for a maintenance window of up to 2 hourseach week outside of employee working hours on the same day(day of week to be confirmed).

Scalability

SCA.1 Website User numbers The solution will support x concurrent website users with theability to scale as necessary.

SCA.2 Backend user numbers The solution will support the initial number of x backend users withthe ability to scale as necessary.

Security

SCR.1 Authentication Joomla will ensure that the website administrators and backendusers are authenticated.

SCR.2 Authorisation Joomla will ensure that the website administrators and backendusers are authorised.

SCR.3 Viewing of content in theInfrastructure Solution

Joomla will enable all users for the website to view all content.

Recoverability

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


24/24

POC Mobile App Scoping Documentv0.1

Documents

Transcript of POC Mobile App Scoping Documentv0.1