Requirment

profileTala
myproject.docx

Contents Table

I. Project Concept ………………………………………...………………………………….…4

1. Executive Summary……………………………………………………………………...4

1. Background………...…………………………………………………………………….4

1. Challenges…...…………………………………………………………………………..4

1. Solution…………………………………………………………………………………..5

II. Business Case………………………………………...………………………………………5

1. Executive Summary…………………………………………………..………………….5

1. Aim of the project………………………………………………………………………..5

1. Background………………………………………...…………………………………….6

1. Key assumptions and constraints………………………………………………………...6

1. Cost-Benefit Analysis…………………………………………………………………....6

1. Revenue projections………………………………………………………………….6

1. Cost Analysis………………………………………………………………………...6

1. Evaluation………...………………………………………………………………….6

1. Sensitivity analysis…………………………………………………………………..7

1. Risk assessment………………………………………………………………………….7

1. Conclusion...……………………………………………………………………………..7

III. Project Charter

IV. Project Plan

1. Executive Summary………………………………………………………………………

1. Background………………………………………………………………………………

1. Objectives………………………………………………………………………………..

1. Project Team……………………………………………………………………………..

1. Scope of Activities……………………………………………………………………….

1. Project Schedule………………………………………………………………………….

1. Project Costs………………………………………………………………………………

1. Costs by Function and Phase……………………………………………………………..

1. Risk Assessment………………………………………………………………………….

1. Assumptions………………………………………………………………………………

1. Summary………………………………………………………………………………….

V. Project Requirements

I.PROJECT CONCEPT:

1. Executive Summary:

Recently, a disconnected network is used by the university that is accessed by the faculty and the students through various Bowie cards. Students and faculty use separate cards to access computing resources. This project is about a single card identification system that will not only reduce extra costs incurred by the university but it will also offer more ease and security to the students, staff and faculty.

2. Background:

Network system is implemented by the university that is composed of disconnect and separate systems and it requires the students and staff to reach various resources through different cards. It means that they access various computing sites and data through different identification cards. Students and faculty both have duties and rights to use these resources. Students include both the graduates and undergraduates, faculty includes full time and visiting professors and the staff which includes the administration and subordinates. They can access this data by keeping in view the security policy of the university. However, the university management has to implement a single ID card system across the university to enhance security of data and ease for the teachers and the students. Because with a current system, they are facing different issues. These issues include the use of separate ID cards, discrete network and absence of real time communication. There is a need for an appropriate solution to issues that originate in response to this project.

3. Challenges:

Preliminary demographics indicate that there is a need for a more reliable and unified identification system in the university. However, the establishment of a single card identification system requires a consolidated platform. The consolidated platform will include registration of fingerprints of the students, staff and teachers, an identification system and a block chain database. This block chain database will not need a centralized manager. It will be developed through the use of block chain technology. In fact, features of block chain technology will be added to this database. Block chain database will be directly distributed across the borders of the university (Anadiotis, 2017). The activities across block chain database will have their separate evidence of approval and therefore they will not need a unified administrator. These activities will be supported through different nodes and the block chain will act as a unanimous procedure to make sure that the nodes are synchronized. The information about every student, staff member and teacher needs to be preserved in this database (Crosby, Pattanayak. and Verma. 2015). By establishing the database, problems of real time communication will be resolved as it will improve the efficiency of data retrieval and management. It will also reduce the extra costs that are incurred by the university because faculty, staff and students will be able to access data from a single shared network which recently occurs in a redundant manner. Moreover, through a shared database all stakeholders will be able to access required information through a remote computing source.

4. Solution:

It is proposed that a single card identification system should be created for addressing the problems that are faced by the management, faculty and students while accessing data from different resources. This centralized identification system will include all of the above components. And for this purpose, block chain technology will be implemented. This block chain technology uses a shared database which is inhabited with digital records that need to be encrypted (Crosby, Pattanayak and Verma. 2015). It will be free of cost for the university. And it is expected that this project will take total of three months to be accomplished.

II. BUSINESS CASE:

1. Executive Summary:

This business case is about implementation of a block chain database for the establishment of a single card identification system through block chain technology. The cost benefit analysis of this project indicates that it will prove quite beneficial for the university.

1. Aim of the project:

This project aims to resolve the issues caused by a decentralized system of identification and enhance the authorization of identity and access at the university (Williams and Sawyer, 2005).

1. Background:

Faculty, students and the staff are using multiple cards to get an access to different computing resources at the university. They are facing the problems of real time communication. So, a project of a centralized identification system has been proposed to the university that will not only assist the university in minimizing extra costs but it will also enhance the flow of data across a centralized database.

1. Key assumptions and constraints:

1. Division of Information Technology (DIT) will provide Team D one on-site meeting weekly as well as be available to address questions and concerns for the duration of the project

1. Team D will update DIT on the timeline and project progress on a weekly basis

1. Team D maybe lacking in some critical technical skills. The team will take some time to learn the necessary skills required to develop the application prototype

1. Team D will ensure the team knows how develop a Blockchain Solution

1. Cost-Benefit Analysis:

1. Revenue projections:

It is estimated that the extra costs that are incurred as a result of downloading and data retrieval in case of a disconnected network and multiple card identification system will be reduced by 20 percent. It will tend to impact the total revenues of the university in a progressive manner (John and Ndujuiba. 2013).

1. Cost Analysis:

This block chain technology will be free of cost for the university because a database containing the attributes of block chain technology will be created for a centralized identification system.

1. Evaluation:

Net present value method was used to evaluate this project. NPV value for the project was positive and that indicates a profitable return on the project.

1. Sensitivity analysis:

Sensitivity analysis was done to determine break even costs of the project. It indicated that by increasing the investment to 40% in an identification system at university, the total costs can be minimized to 20 percent (Weichun, 2013).

1. Risk assessment:

1. Privacy & Confidentiality: Student information cannot be accessed by just anyone without their consent.

1. Security threats to the system and network: There is a threat to the system, which may come from hacking either internally or externally and from malware or viruses.

1. Conclusion:

This project will be advantageous for the university in many ways. It will not only minimize costs but also improve data access of students, staff and teachers through a unified card. However, it may face technical issues that can be resolved through trained personnel with relevant expertise.

III. Project Charter

IV. Project Plan

1. Executive Summary

This document constitutes and serves as the Project Plan for the Centralized College Solution (CCS) project being developed by Team D. The report describes the background and objectives for the project and describes the strategy behind the project management structure proposed by Team D. The primary focus of this document is to provide written confirmation to the customer that there is a fully manageable plan for the successful deliverance of this project.

The Work Breakdown Structure (WBS), shown in Figure 2, illustrates three levels of details: project’s phases, tasks, and subtasks. The project schedule also identifies the critical paths and milestones, which must be met to achieve the target project completion date of December 7, 2017.

The Centralized College Solution project life span commences Tuesday, September 19, 2017 and concludes Thursday, December 7, 2017 equaling to a total of three months and nine days of project life. The project’s calculated cost total to $10,000. The Project risks will be high during Phase 3, the Execution Phase. High risks will dissipate at the conclusion of Phase 3 and through effective Risk Management and Mitigation.

1. Background

The BSU DIT has identified a needed change in the manner in which data is transferred between department network systems. Currently BSU’s network consists of separate and disconnected systems. Transferring data between systems occurs via a batch transfer.  Providing redundant information is necessary since the systems do not communicate with each other in real-time.  The DIT envisions a network that is capable, efficient, and improves productivity.

The reasoning for the Centralized College Solution Project is to save time and improve productivity by embracing an emerging technology. The Centralized College Solution is designed to allow various departments at Bowie State University to verify students, faculty and staff without having to send out emails from one department to another. Typically, a department like the library is on standby until the Bowie card office replies with verifying the student’s identity.

The project plan consists of the managing quality, performance, risks, costs and time. Each of these factors will be managed by the project manager and delivered to the customer on Thursday, December 7, 2017. The project solution is free to implement, with the exception of $10,000 towards project team member hours worked. The stakeholders identified will have direct and indirect implications to the overall project’s success and therefore are listed below:

1. Project Owner

1. Project Manager

1. Project Team

1. Professor

1. Government (Laws and Regulations)

1. BSU Departments (Department of Information Technology (DIT), Bulldog Card Office, Library)

1. Objectives

The overall objective of this Project Plan is to describe how Team D will successfully complete the design of the BSU blockchain network on behalf of DIT. The Centralized College Solution project will be completed on December 7, 2017, at a total cost of $10,000.

The intention of the owners (BSU DIT) is to create a project solution with following criteria:

1. A system that communicates in real-time with various University departments

1. Ability to verify student, faculty, or staff identity or status on campus at any given time

1. Use blockchain technology to access information and verify student, faculty and staff credentials

1. A system that is secure

1. Eliminates the need to provide redundant information to BSU departments

1. Enhances the ability and effectiveness of employees to perform their jobs

1. Facilitates information sharing and coordination between University departments

The major deliverables from the project include the following:

1. Status Report #1

1. Project Concept/Business Case Development

1. Project Plan

1. Status Report #2

1. Requirements Definition

1. Status Report #3

1. Lessons Learned

1. Final Project Report

1. Blockchain Solution

1. Project Team

The project team consists of four team members. Each team member will be assigned key responsibilities that they will be expected to fulfill. Team members’ communications, performance of responsibilities and adherence to the project’s guidelines will be essential to the success of this project.

Figure 1: Project Team

Team Member’s key responsibilities are as follows:

1. Project Manager (PM)

Responsibilities include:

1. Coordination and communication with project Sponsor, Professor, Project Stakeholders, and Project Team Members

1. Providing direction and guidance to other team members

1. Maintaining the overall project plan (schedule, cost, and resources)

1. Coordinating and producing all project documentation

1. Business Analyst (BA)

Responsibilities include:

1. Requirement Gathering and Analysis

1. Interpretation of BSU business requirements

1. Represents Project Stakeholders throughout the project

1. Translate technical issues revealed by the Project Team into business language

1. Developer

Responsibilities include:

1. Coordination of all activities related to design and coding for the project

1. Change Control with respect to design and coding

1. Evaluate, assess and recommend software and hardware solutions

1. Coordinate with business analyst for requirements

1. Develop and deliver BSU modules

1. Develop user interfaces

1. Quality Assurance (QA)

Responsibilities include:

1. Defining test cases and prioritizing testing activities.

1. Updating Project Manager about the progress of the testing activities

1. Execute all test cases, determine the severity and priority of each defect and report defects

1. Responsible for the overall quality control of College Centralized Solution

1. Scope of Activities

The WBS for the Centralized College Solution is contained in a Microsoft Project file and is shown in Figure 2. The plan contains forty eight tasks that are divided into four phases and covers a period of three months. The activities are divided into three levels: phase, task, and subtasks. The WBS will serve as a tool to help get a synopsis of interrelationships between tasks.

1. Phase 1: Initiation – Key activities include the development of the Project Concept/Business Case and the Project Charter.

1. Phase 2: Planning – Key activities include development of the Project Plan and implementation strategies.

1. Phase 3: Execution – Key activities include development of the Blockchain solution, Staff training, Blockchain system testing, and Production deployment

1. Phase 4: Closure Phase – Key activities include distribution of Lessons Learned and establishing a System Maintenance Team.

1. Project Schedule

The CCS project will commence on Tuesday, September 19, 2017 and concludes Thursday, December 7, 2017 equaling to a total of three months and nine days of project life. The project schedule identifies the critical paths and milestones, which must be met to achieve the target project completion date.

Table 1: Critical Milestones

Milestone

Date

Key Stakeholder

Key Trigger Event(s)

Phase 1: Initiation Phase

Approval of Project Charter

September 24, 2017

Project Manager

Creation of project team

Completion of Phase 1 and Approval to Move Forward

October 2, 2017

Project Manager

Project Creation and Phase 2 start

Phase 2: Planning Phase

Define system requirements

October 9, 2017

Project Manager

Collect Customer requirements

Secure Software Vendors

October 16, 2017

Project Manager

Customer requirements

Approval to move Forward

Secure signatures for approval to proceed to Phase 3

October 18, 2017

Project Manager

Project execution and Phase 3

Phase 3: Execution

Develop Blockchain Solution

November 1, 2017

System Developer

Building out system for benchmarking

Release to Development Environment

November 14, 2017

System Developer

Develop Complete

Test Blockchain Solution in Development Environment

November 15, 2017

Quality Assurance

Quality and validation for project continuance

Release to Production Environment

November 21, 2017

System Developer

Successful Development Environment Testing

Test Blockchain in Production Environment

November 22, 2017

Quality Assurance

Quality and validation for project continuance

Blockchain Deployment Complete

November 19, 2017

System Developer

Project Solution delivery and Phase 4

Phase 4: Closure

Closure Phase Complete

December 5, 2017

Project Manager

Project Owner and contractual obligation

Table 2: Noncritical Milestones

Milestone

Date

Key Stakeholder

Key Trigger Event(s)

Phase 1: Initiation Phase

Project Concept/Business Case Development

September 20, 2017

Project Manager

Project Initiation

Phase 2: Planning Phase

Develop Project Plan

October 3, 2017

Project Manager

Project Planning

Phase 4: Closure

Create Blockchain System Maintenance Team

December 4, 2017

Project Manager

Project Closure

Figure 2: Project Schedule and Work Breakdown Structure

1. Project Costs

The project costs for completion are estimated at $10,000. The project solution is free to implement, with the exception of $10,000 towards project team member hours worked.

Figure 3: Total Cost by Project Function

1. Costs by Function and Phase

Costs by project function and by phase are illustrated in Figures 3 and 4. Majority of the cost will take place in Phase 3. The project team will spend more time working on Phase 3. The construction and execution of the blockchain solution will occur during this Phase.

Figure 4: Costs by Project Phase

1. Risk Assessment

1. Privacy & Confidentiality: Student information cannot be accessed by just anyone without their consent. Any staff accessing the info must have the authority to do so.

1. Security threats to the system and network: There is a threat to the system, which may come from hacking either internally or externally and from malware or viruses.

1. Scheduling Conflicts: Team members have different schedules and cannot all be available at the same times.

1. Blockchain Technology Skills: Team members may lack experience with blockchain technology.

1. Assumptions

The project plan is founded on the following key assumptions:

1. Division of Information Technology (DIT) will provide Team D one on-site meeting weekly as well as be available to address questions and concerns for the duration of the project

1. Team D will update DIT on the timeline and project progress on a weekly basis

1. Team D maybe lacking in some critical technical skills. The team will take some time to learn the necessary skills required to develop the application prototype

1. Team D will ensure the team knows how develop a Blockchain Solution

1. Team D will provide two staff members for testing

1. Team D will provide two staff members for operations and maintenance

1. Team D will meet the technical requirements

1. Team D will ensure the computer hardware meets the requirements to implement the Blockchain solution

1. Team D will operate within the existing technical infrastructure

1. Team D will provide training and support to users to familiarize them with the application processes and procedures

1. Team D will not provide more than five hours for additional support post Operations without additional costs

1. The time available to develop a working prototype is limited; therefore the team will not be able to develop working prototypes of all the Blockchain modules

1. Summary

Team D has developed a comprehensive Project Plan that will serve as a communication document used for socializing the project’s methodology to the DIT. The Project Plan emphasizes the four phases planned for successfully delivering the solution. The customer’s requirements, time and costs are all inclusive and shall not exceed budget.

The customer is required to authorize this Project Plan, empowering and authorizing the Project Manager to commence working on the next phase of the project. This Project Plan is time sensitive and therefore requires a signature within 10 days to ensure that Team D maintains the Project Plan schedule.

Project Plan Approval Signatures

Name: ______________________________________

Date: ______________________________________

Organization: ______________________________________

Signature: ______________________ Date: ______________

Figure 5: Work Breakdown Structure and Schedule

V. Project Requirements

References:

John. S. N. and Ndujuiba. C. (2013).Design and implementation of a unified e-id card for secure e-voting system (muses)’. International Journal of Computer and Information Technology, 2(6), pp. 2279-0764.

http://citeseerx.ist.psu.edu/viewdoc/download?doi=10.1.1.403.5992&rep=rep1&type=pdf

Weichun. L. V. (2013).Design of campus smart card system’. Proceedings of the 2nd International Symposium on Computer, Communication, Control and Automation. (ISCCCA-13). Atlantis Press, France, pp. 0483-0486.

Williams. R. and Sawyer. S. C. (2005). ‘Using information technology: a practical introduction to computers & communications’. 7th Edition.

Anadiotis, G. (2017). ‘How to use block chain to build a database solution. Retrieved from

http://www.zdnet.com/article/blockchains-in-the-database-world-what-for-and-how/

Crosby. M., Pattanayak. P. and Verma. S. (2015). ‘Block chain Technology’. Berkeley: Sutardja Center for Entrepreneurship & Technology.

Total Cost by Project Function Project Manager Business Analyst Quality Assurance System Developer 42.79 31.23 29.81 32.21 Costs by Project Phase Phase 1: Initiation Phase 2: Planning Phase 3: Execution Phase 4: Closure 17 36 38 7

Project Manager

Cherno Jallow

Quality Assurance

Duaa Altalhi

Business Analyst

Manal Allam

System Developer

Starvon Jones

Team Title�

Company Name �

Company Name Department Name�

Project Manager Cherno Jallow�

Quality Assurance Duaa Altalhi�