Retail Configuration And Order System For Luminscape

Our System Capabilities

XYZ is an Australia based organization that provides financial services to its customer. The data and information that the organization works into belongs to the category of sensitive and critical information. There are numerous security risks and attacks that have taken place in the past due to the violation of the access controls and the insider threats and attacks. Due to the increased frequency of such attacks, the customer engagement and the level of customer satisfaction has begun to drop.

System Capabilities

It has been proposed that a biometric information system is designed for the organization which would capture the users and their identities using the iris and fingerprint based recognition. The users that would succeed in the attempt will only be provided the access to the organizational applications. The system will overcome the security attacks as only the authorized users will be allowed the access. Also, a real-time log of the users accessing each of the application and associated activities will be maintained by the system for tracking purposes. The user activities will also be mapped with the set of best practices and standards to ensure that quality of operations is maintained.

Business Benefits & Advantages 

• The security risks and attacks that are currently taking place in the organization causing damage to the information and data sets will come to a stop.
• The customer engagement and trust will improve as the customers will be able to be assured that their information is in the safe hands.
• With the use of the latest security measures and information systems in the organization, it will be able to gain a competitive advantage.
• The market shares and the revenues earned by the organization will improve as the customer base will expand.
• The employees of the organization will understand that any of the malicious practices will result in adverse actions and will enable them to follow best practices and standards.

Quantify Project Approval factors

Estimated Time for the Project 

The estimated time for the project has been calculated to be 112 days. The starting date of the project will be 19^th September 2017 and it will end on 21^st February 2018. There will be a number of activities that will be carried out in the project. All of these activities have been described in the table below along with their sub-activities. The time that has been allocated to each of these activities has been in accordance with the effort that will be required. It has been made sure that there is no over-lapping of the resources during the project activities. The project will be carried out in four broad phases and there will be activities carried out in each phase.

Task ID	Task Name	Duration	Start	Finish	Predecessors
1	Biometric Information System	112 days	Tue 9/19/17	Wed 2/21/18
1.1	Initiation and Project Planning	15 days	Tue 9/19/17	Mon 10/9/17
1.1.1	Technical, Operational and Economical Feasibility Analysis	3 days	Tue 9/19/17	Thu 9/21/17
1.1.2	Project Estimation – Scope, Cost and Schedule	6 days	Fri 9/22/17	Fri 9/29/17	3
1.1.3	Risk Identification, Assessment and Evaluation	2 days	Mon 10/2/17	Tue 10/3/17	4
1.1.4	Team selection and allocation	2 days	Wed 10/4/17	Thu 10/5/17	5
1.1.5	Communication Guidelines	2 days	Fri 10/6/17	Mon 10/9/17	6
1.1.6	Milestone One: Project Plan	0 days	Mon 10/9/17	Mon 10/9/17	7
1.2	Execution of the Project	56 days	Tue 10/10/17	Tue 12/26/17
1.2.1	Interfaces and UI design for Information System	12 days	Tue 10/10/17	Wed 10/25/17	7
1.2.2	Wireframes and UI elements	6 days	Thu 10/26/17	Thu 11/2/17	10
1.2.3	Creation of Source Code	30 days	Fri 11/3/17	Thu 12/14/17	11
1.2.4	Syncing with database and analytical tools	5 days	Fri 12/15/17	Thu 12/21/17	12
1.2.5	Unit testing of the system	2 days	Fri 12/22/17	Mon 12/25/17	13
1.2.6	Release of source code	1 day	Tue 12/26/17	Tue 12/26/17	14
1.2.7	Milestone Two: Source Code	0 days	Tue 12/26/17	Tue 12/26/17	15
1.3	Testing and Implementation	23 days	Wed 12/27/17	Fri 1/26/18
1.3.1	Testing Processes	9 days	Wed 12/27/17	Mon 1/8/18	16
1.3.2	Reporting of the defects	1 day	Tue 1/9/18	Tue 1/9/18	18
1.3.3	Change Management	5 days	Wed 1/10/18	Tue 1/16/18	19
1.3.4	Reviews and Inspection	5 days	Wed 1/17/18	Tue 1/23/18	20
1.3.5	Integration of the sub-systems	3 days	Wed 1/24/18	Fri 1/26/18	21
1.3.6	Milestone Three: Defect Report	0 days	Fri 1/26/18	Fri 1/26/18	22
1.4	Project Closure	18 days	Mon 1/29/18	Wed 2/21/18
1.4.1	System Documentation	10 days	Mon 1/29/18	Fri 2/9/18	22
1.4.2	Deliverables and Sign Offs	3 days	Mon 2/12/18	Wed 2/14/18	25
1.4.3	Closure Report Preparation	5 days	Thu 2/15/18	Wed 2/21/18	26
1.4.4	Milestone Four: Closure Report	0 days	Wed 2/21/18	Wed 2/21/18	27

Development Costs for the Project 

Type of Cost	0	1
Cost of tools – One time	$12,160
Design Costs		$4,200
Development Costs		$11,760
Program Total Costs By Year	$12,160	$15,960

Operational Costs for the Project 

Type of Cost	1
Cost of Resources	$15,470
Maintenance and Support	$2,870
Testing Processes Cost	$3,540
Program Total Costs By Year	$21,880

Project Benefits

Benefit Sources	0
Reduction in operational processes	$15,670
Enhancement of security	$12,300
Tangible Benefits	$9,870
Intangible Benefits	$5,780
Total Benefits Per Year	$43,620

Risk Analysis

Name of the risk	Brief Description	Risk Impact	Probability of the Risk	Treatment Process
Strategic Risks	There may be inadequate design and implementation of the project strategies and methodologies	High	Low	Risk avoidance shall be done by assessing the requirements carefully along with enhanced planning
Management Risks	The skills of the Project Manager may not be adequate as per the project requirements (Berg, 2016)	High	Low	Risk avoidance by selecting the manager as per the project factors and requirements

Feasibility Analysis

The project will be feasible from the organizational point of view since all of the risks that have been identified have a low probability. It will be possible to avoid the risks by following adequate measures (Dey, 2016).

Risk Analysis

Name of the risk	Brief Description	Risk Impact	Probability of the Risk	Treatment Process
Technical Fault	The technical tools being used in the project may suffer from a severe fault	Medium-High	Medium	Risk mitigation by keeping the alternative of every tool ready to be used
Integration and Compatibility Risks	The problems of incompatibility of the tools and technologies with the final system (Grimes, 2016)	High	Medium	Risk avoidance by carrying out a compatibility and integration analysis in advance (Microsoft, 2016)

The project will be feasible from the technical point of view as it will be possible to apply the adequate controls on the risks that have been identified (Bateman, 2016).

Risk Analysis

Name of the risk	Brief Description	Risk Impact	Probability of the Risk	Treatment Process
Efficiency and Productivity Risks	The increased number of resources may lead to enhanced conflicts and disputes which may bring down the levels of efficiency and productivity	High	Low	The project management must avoid the risks by enhanced monitoring and control along with effective communication during the project
Resource Scarcity	The resources may quit the organization in abundant numbers	High	Low	The project management must avoid the risks by enhanced monitoring and control along with effective communication during the project (Scu, 2016)

There shall be a daily meeting organization by the Project Manager so that the communication processes carried out in the project are effective in nature (Sychrava, 2016). As per the resource feasibility, the project would be feasible since the risks can be avoided and controlled (Bause, 2016).

Name of the risk	Brief Description	Risk Impact	Probability of the Risk	Treatment Process
Schedule Overrun	The project team may not be able to meet the deadlines of the project due to increased changes and conflicts (Trendmicro, 2016)	High	Low	Risk avoidance and mitigation by following proper estimation and revision of the schedule in case the same is caused

The project would be feasible as per the schedule feasibility since the avoidance of the risk will be possible (Kim, 2015). The management must make sure that the schedule and the other estimated values are maintained by frequent monitoring and control.  

Search, Customize, and Purchase Outdoor Lighting Solutions Online

Establishment of the Project Environment

Information Classification and User Privileges

Information Captured by the System	Brief Description	View/Update the Information – User Privileges
Sensitive Information	It will include the financial details of the clients and employees, such as, their account numbers and passwords	Only the Project Manager will be allowed to view the information and its update rights will not be provided to any of the project resource
Confidential Information	The information on the organization strategies and projects will come under this category (Hoiem, 2013)	View: Project Manager, Project Developer, Implementation Head Update: None
Private Information	The demographic details of the employees and the clients	View: Project Manager, Project Developer, Implementation Head, System Tester Update: Implementation Head
Public Data	The details of the organization such as its profile, main list of customers, mission and vision.	View: The entire project team Update: Project Manager

Tools and Software for Developmental Activities 

• The source code of the information system will be designed in Microsoft Visual Studio with C# as the programming language and .NET as the framework.
• The database used in the project will be MySQL.
• Testing tools such as Bugzilla and TestLink will be required. Test creation and reporting of the defects will be done using these testing tools.
• Project Management and Resource tracking tools
• Big Data analysis tool as Hadoop will be integrated.

Work Environment

There will be three work environments that will be created for the project team members as development environment, testing environment and production environment.

Apart from these, the tools and equipment necessary for the team will be provided to them and the meeting rooms will be equipped with tele-conferencing mediums for effective communication.

Processes and Procedures

The methodology that shall be used for the project development activities would be Agile Methodology for Software Development. There will be multiple iterations called sprints that will be run in order to make sure that the requirements of the system are implemented (Rao, 2011). It is the methodology in which there will be a daily meeting that will take place and will be organized by the Project Manager. In the meeting, the activities for the day will be planned and project progress will be discussed. This methodology will provide the project team members with an ad-hoc approach which will make it easier for them to target the requirements that are to be met. Any of the changes requested by the project client will also be possible to be implemented with ease.

Project Management is another discipline that has a lot of significance in the project success. There are several methodologies that have been defined so that the project management practices may be implemented. The methodology that would be applied in this case will be Project Management Body of Knowledge (PMBOK). In this methodology, the project activities will be carried out and completed in five phases or stages as the initiation stage, planning phase, execution, control and closure. The management activities will be synced with the project development and other tasks so that the risks, conflicts and disputes are avoided and project goals are met (Hewagamage, 2011).

Work/Project Schedule

Work Breakdown Structure (WBS)

The Work Breakdown Structure (WBS) is a tool that shows the project activities in a hierarchical manner. These activities are displayed in the various levels using this tool. In case of the Biometric information system for the organization, there are three levels that have been shown in the WBS. These levels include the packages and sub-packages that showcase the project tasks and activities that will be carried out during the project life cycle. This tool is essential in the projects to determine the work schedule and effort that shall be applied for each of the activities. It is because of the reason that the activities that are shown in WBS can be understood and analyzed to reach up to the highest level which is the end-product.

There will be four broad phases that will be involved in this case, which have been shown at level-1. These phases are further divided in the set of tasks and activities that will be executed.

Gantt chart is a tool that is used in the projects to estimate the project schedule and also understand the resource allocation and cost structure. In this tool, the project activities can be viewed in the form of a timeline. This timeline also shows the activities that are completed and the ones that are pending in the project. The over-lapping of the resources, slack, and the critical path can also be determined using this tool.

Save Customizations and Track Preferred Products

The timeline for the project of biometric information systems has been displayed from the images below. These images have been captured from Microsoft Project which is the software this is commonly used in order to design the Gantt charts. There are also various other activities that can be performed using the Gantt chart, such as correct allocation of the resources to the project activities, correct estimation of the project schedule and the effort that shall be applied and so on.

Functional Requirements

• Ability to make sure that the login functionality is implemented in the system for the users to access it.
• The system shall ask for a login id and password as the first step towards authentication.
• It shall then recognize the user on the basis of iris recognition and the pattern shall be matched with the one present in the database. The access shall be provided in case of a correct match.
• There shall be fingerprint recognition performed as a final check for authentication of the users.
• The system shall monitor the user access for various applications and databases associated with the organization.
• A system log shall be maintained on a real-time basis.
• Data analytics shall be performed on the user activities and the attempts to violate the security.
• The system shall generate the reports on the basis of user activity.

Non-Functional Requirements

• The system shall have amazing performance in terms of the throughput time and the response time which shall be quick. There shall be no lags involved in any of the actions (Chung, 2016).
• The information system must be available at all times so that the security of the organization and its applications is maintained at all times.
• Reliability of the system shall be implemented so that the information that it presents must be valid and accurate at all times.
• The system must be easy to maintain so that any of the updates shall be easily installed in the system without any hurdles (Glinz, 2016).
• The system shall also be scalable in nature. Technology keeps on changing at the rapid rate and the system must be scaled up and down accordingly.
• Usability is one of the most important system qualities that shall be maintained. It must make sure that the system requirements are met and the user experience that is attained is high.  

Stakeholder Analysis

Internal Stakeholders – Operational · Project Team Members – Project Developer, Project Designer, Implementation Head, System Tester, Network Engineer, Finance Officer	Internal Stakeholders – Executive · Project Manager
External Stakeholders – Operational · Business Analyst	External Stakeholders – Executive · Project Sponsor · End-Users · Business Partners

The internal stakeholders that will be associated with the system will include the operational members of the project team. They will carry out the tasks of project execution, testing and implementation. The Project Manager will be an internal stakeholder of the project at the executive level. The Project Manager will be responsible for the project planning, control and closure.

There will be many of the external stakeholders that will be associated with the project as well. The Business Analyst will be an external stakeholder at the operational level. The stakeholder will provide the project team with the set of the guidelines to meet the business requirements for the project. There will also be many of the external stakeholders present and involved at the executive level. The Project Manager will provide the project team with the required funds for the project and the requirements that shall be targeted. The end users and the business partners will provide their feedback on the final product that will be delivered.

The stakeholder groups that are associated with the project shall be provided with the status reports on the project and there shall be a SharePoint location that shall be set up for the same. The project documents and other confidential information shall be updated on this location which shall be accessible only by the project stakeholders and resources. This will make sure that an enhanced communication channel is created and the same is maintained so that project information remains confidential at all times. There shall also be internal and external meetings that shall be carried out so that the project progress and issues are discussed.

Questionnaire for the Operational Stakeholders – Business Analyst 

There are various techniques that may be used to extract information from the stakeholders and associated project entities. These techniques make sure that the maximum information is extracted and is understood by the project team members so that the requirements associated with the project are met. One of such techniques is the questionnaire which includes a set of questions regarding the project and the same are answered by the stakeholders.

The stakeholder group for which the following questionnaire is designed is the Business Analyst that is an external stakeholder at the operational level.

Question No	Question
1	What are the common security risks and attacks that take place in the organization?
2	What are the problems that are faced by the organizations for which the information system has to be designed?
3	What are the information categories that need to be managed and maintained by the system?
4	What are the current codes and policies that are implemented in the organization for the management and efficient storage of the information?
5	What is the frequency of the insider threats and attacks that have taken place in the past?
6	Is there a biometric based system already in use in the organization or this system will be first of its kind?
7	What are the system qualities that the client would be wanting in the final release of the system?
8	Are the employees of the organization allowed to bring their own devices at work or the company provides them with all the necessary equipment?
9	What is the level of technical expertise of the employees in the organization?
10	Are they provided with the trainings and sessions on security and latest practices?
11	What are the other automated systems and tools that are being used in the organization?
12	What kind of network topology is implemented in the organization? What is the network architecture that is used?

Domain class diagram

Domain class diagram is the diagram that represents the association that exists among the various classes that are involved in the biometric information system. During the design of the system, there are classes and their attributes defined so that it becomes easier for the developers to understand the system behavior. There are five classes that are present in this case viz. login_history, staff, user, iris_pattern and report. The relationship between these classes is represented in the diagram below. The associations that are present between the various classes are represented by the UML notations of multiplicity. The domain class diagram for the biometric information system is represented below.

Social Media Integration

Use case Descriptions

Biometric Information System: Use Cases Summary
Use Case ID	Use Case Name	Description
1	Login to the System	The user would be required to enter the login id and password to access the system.
2	Iris Recognition	The iris pattern of the user will be matched with the one in the system database.
3	Fingerprint Recognition	The fingerprint pattern of the user will be matched with the one in the system database.
4	Data Analysis	The data in terms of user and system activities will be analyzed using the analytical tools.
5	System and Security Logs	The logs will be maintained by the information system on a real-time basis.
6	Report Extraction	The users will be allowed to extract the reports from the system.

Fully Developed Use Case Description

Use Case:	Iris Recognition
ID:	2
Scope:	Access control for the users
Priority:	9/10
Summary:	The biometric information system will carry out recognition of the users on the basis of the iris patterns and the access will be granted only if the match is found.
Primary Actor:	Users, System
Supporting Use Cases	Login to the System, Fingerprint Recognition
Stakeholders:	Project Team Project Sponsor End User
Preconditions	The user has passed the login check by entering a valid id and password.
Trigger:	Successful login authentication
Normal Flow:	User opens the system User enter the login id and password (A1) The match is found in the database and the user moves to the next stage. An iris check is performed by capturing the iris pattern of the user.(A2) The user is granted the access if the match is found.
Alternate Flow/ Exceptions:	A1: Invalid login credentials. System displays an error message. A2: The match to the iris pattern of the user is not found in the database
Post-Condition:	The user shall be granted the access to the system only if the fingerprint recognition is successful.

Use case diagram

Use case diagram is one of the most significant diagrams that have been created to understand the system behavior and activities. There are actors that are illustrated in the diagram and are mapped with their set of activities that they will execute. In the case of biometric information system, there are primarily two actors that are involved, that is, customer and the system. The set of activities that will be performed by the customer include register, login, identify iris, identify fingerprint and extract reports. The system will perform the activities of data analysis, identification of iris and fingerprint and generation of security logs.

Activity diagram

There are various activities that will be carried out and performed by the system. These activities can be extracted from the set of the requirements that are provided to the project team. However, it is always easier to understand and grasp the information from a graphical representation as compared to the theoretical information. It is due to this reason that the activity diagrams were created and the same for the biometric information system is represented below. The flow of the activities in the system has been displayed so that the task of the developers and the implementation team gets easier.

System sequence diagram

There are a number of diagrams that have been invented so as to understand the interaction between the various components in the system. One of such diagrams is the system sequence diagram in which the interaction between the admin and the system has been represented below.  The sequence is showcased with the aid of the message chart and their flow is displayed with the aid of the arrows. In this manner, it makes it possible for the developers and the project team to understand the level of system interaction and the dependency of the components on each other as well.

System Components

There will be cloud models that will be used for the deployment and delivery of the system. It is because of the reason that the company has its operating locations in various areas. The system will be accessible by the users at any location by deploying and delivering it on cloud.

Platform as a Service (PaaS) is the delivery model that will be used in the system for its delivery. This model will provide the required platform, that is, the framework for carrying out system activities. The model has been recommended as it will be cost-effective in nature and will provide the project team with enhanced form of security. Due to the nature of the business requirements and the functional and non-functional requirements of the project, the PaaS model will be apt in this case (Gorelik, 2013).

The deployment of the system will be done by making use of Hybrid model for cloud. There are three models which may be used for the deployment activities, as, private cloud, public cloud and hybrid cloud. The hybrid cloud model is a combination of the public and private cloud models. This model has been recommended as the information categories that will be used in the system will be sensitive, confidential, private and public. The system operations that will be carried out will revolve around these information sets and categories. It will, therefore, be required that the cloud deployment model that is selected is able to meet all of the system requirements.

Business Benefits and Advantages

Hybrid Cloud Model

There are also many of the network topologies and architectures that are available that may be used in this case. However, the one that will be applicable as per the system requirements and factors is the three-tier networking architecture and the topology that shall be used shall be mesh topology for the inter-connection of various components.

User Interface Design Concepts – Best Practices

The primary motive of any system or project is to make sure that the maximum user satisfaction is achieved through the same. It is necessary to include the functional and non-functional requirements due to this reason. It is also equally important to ensure that the user interface that is implemented is visually appealing and is understood by the user.

To make sure that the best design and concepts were implemented in the system, the layout of the information system has been kept simple and consistent all throughout. There is a logo of the company displayed at the top followed by header, body and footer sections. The body section comprises of the menu and the contents. The contents keep on changing from one screen to the other and the rest of the sections are kept the same.

Navigation and the flow that has been implemented in the system are also kept simple. It is made sure that the flow from one screen to the other is smooth and there is not too much scrolling. The use of the screen space is done accurately so that there are no whitespaces and no over-loading of the elements as well (Galitz, 2014).

Consistency is one of the design principles that have been followed in the system which allows the consistency of the layout, text style, color scheme and themes. The users can also customize the color scheme that has been used in the system so that the colors are displayed as per their choice.

There are help and support documents that have been included to assist the users and there is also a link to the support team that has been provided. The users can always contact the team in case they get stuck. The error resolution and management can therefore be done with much ease.

Deploy the Solution

Project Management is a discipline that has a lot of significance in the project success. There are several methodologies that have been defined so that the project management practices may be implemented, such as, PRINCE2, PMBOK, agile management etc. The methodology that has been recommended in this case is Project Management Body of Knowledge (PMBOK). In this methodology, the project activities are carried out and completed in five phases or stages as the initiation stage, planning phase, execution, control and closure.

The management activities are then synced with the project development and other tasks so that the risks, conflicts and disputes are avoided and project goals are met (Rose, 2013). The planning and initiation phases of the project cover the feasibility analysis, project estimation, allocation of roles and communication plan. These activities make sure that the estimation tasks are carried out correctly.

There will be a number of estimations that will be carried out in the project such as scope, schedule, cost etc. There will also be risk identification and assessment that will be done so that the risk areas of the project are identified and the suitable measures are taken so as to avoid and control the risks. An enhanced communication plan will make sure that the internal and external stakeholders are aware about the project progress and any of the issues associated with the project.

The methodology that shall be used for the project development activities would be Agile Methodology for Software Development. There will be multiple iterations called sprints that will be run in order to make sure that the requirements of the system are implemented. It is the methodology in which there will be a daily meeting that will take place and will be organized by the Project Manager. In the meeting, the activities for the day will be planned and project progress will be discussed. This methodology will provide the project team members with an ad-hoc approach which will make it easier for them to target the requirements that are to be met. Any of the changes requested by the project client will also be possible to be implemented with ease (Karaman, 2015).

Testing is one of the most important activities that shall be carried out to make sure that the defects and bugs are not present in the project. The testing activities that shall be covered in this case shall include system testing, integration testing, unit testing, regression testing, performance and security testing. In these processes, the validation and verification of the requirements will be done to make sure that the final release of the project is free from any of the errors or deviations. The management shall also carry out the reviews and inspection so that the project team is always aware of the errors that they may be implementing. These processes will enhance the quality of the system and will also make sure that the client expectations are met.

There will also be closure activities that will be performed in the project which will cover the system documentation, acceptance of deliverables and preparation of the closure report.

References

Bateman, D. (2016). Feasibility Analysis. [online] Available at: https://www.prenhall.com/behindthebook/0132240572/pdf/BarringerCH03.pdf [Accessed 15 Sep. 2017].

Bause, K. (2016). Feasibility Studies in the Product Development Process.

Berg, H. (2016). Risk Management. [online] Available at: https://ww.gnedenko-forum.org/Journal/2010/022010/RTA_2_2010-09.pdf [Accessed 15 Sep. 2017].

Chung, L. (2016). Non-Functional Requirements. [online] Available at: https://www.utdallas.edu/~chung/SYSM6309/NFR-18-4-on-1.pdf [Accessed 15 Sep. 2017].

Dey, P. (2016). Integrated approach to project feasibility analysis: a case study: Impact Assessment and Project Appraisal: Vol 19, No 3. [online] Tandfonline.com. Available at: https://www.tandfonline.com/doi/abs/10.3152/147154601781766989 [Accessed 15 Sep. 2017].

Galitz, W. (2014). The Essential Guide to User Interface Design. [online] Available at: https://ps.fragnel.edu.in/~dipalis/prgdwnl/eguid.pdf [Accessed 15 Sep. 2017].

Glinz, M. (2016). On Non-Functional Requirements. [online] Available at: https://www.ptidej.net/courses/log3410/fall11/Lectures/Article_6.pdf [Accessed 15 Sep. 2017].

Gorelik, E. (2013). Cloud Computing Models. [online] Available at: https://web.mit.edu/smadnick/www/wp/2013-01.pdf [Accessed 15 Sep. 2017].

Grimes, R. (2016). The 5 cloud risks you have to stop ignoring. [online] InfoWorld. Available at: https://www.infoworld.com/article/2614369/security/the-5-cloud-risks-you-have-to-stop-ignoring.html [Accessed 15 Sep. 2017].

Hewagamage, C. (2011). Redesigned Framework and Approach for IT Project Management. [online] Available at: https://www.sersc.org/journals/IJSEIA/vol5_no3_2011/8.pdf [Accessed 15 Sep. 2017].

Hoiem, O. (2013). Guidelines for Classification of Information. [online] Available at: https://services.geant.net/cbp/Knowledge_Base/Security/Documents/gn3-na3-t4-ufs136.pdf [Accessed 15 Sep. 2017].

Karaman, E. (2015). Comparison of project management methodologies: prince 2 versus PMBOK for it projects. [online] Available at: https://www.ijaser.com/articles/vol4issue42015/vol4issue4/JASER4059.pdf [Accessed 15 Sep. 2017].

Kim, D. (2015). A Feasibility Study on the Research Infrastructure Projects for enhancing the ICT Devices Industry Reliability using AHP. [online] Available at: https://www.sersc.org/journals/IJUNESST/vol8_no9/5.pdf [Accessed 15 Sep. 2017].

Microsoft, (2016). Risk Management Process Overview. [online] Technet.microsoft.com. Available at: https://technet.microsoft.com/en-us/library/cc535304.aspx [Accessed 15 Sep. 2017].

Rao, K. (2011). A Study of the Agile Software Development Methods, Applicability and Implications in Industry. [online] Available at: https://www.sersc.org/journals/IJSEIA/vol5_no2_2011/4.pdf [Accessed 15 Sep. 2017].

Rose, K. (2013). A Guide to the Project Management Body of Knowledge (PMBOK® Guide)-Fifth Edition.

Schmeer, K. (2016). Stakeholder Analysis Guidelines. [online] Available at: https://www.who.int/workforcealliance/knowledge/toolkit/33.pdf [Accessed 15 Sep. 2017].

Scu, (2016). The Risk Management Process – Risk Management – SCU. [online] Scu.edu.au. Available at: https://scu.edu.au/risk_management/index.php/8/ [Accessed 15 Sep. 2017].

Sychrava, L. (2016). Some Thoughts on Feasibility Studies. [online] Available at: https://www.bath.ac.uk/e-journals/jtep/pdf/Volume_11_No_3_332-348.pdf [Accessed 15 Sep. 2017].

Trendmicro, (2016). BYOD – Consumerization of IT & Mobility – Trend Micro USA. [online] Trendmicro.com. Available at: https://www.trendmicro.com/us/enterprise/challenges/it-consumerization/ [Accessed 15 Sep. 2017].