TLS Implementation Project Report
VerifiedAdded on  2020/04/07
|16
|1941
|114
AI Summary
This assignment presents a comprehensive project report detailing the implementation of TLS (Transport Layer Security) within HQI. It outlines a five-phase Work Breakdown Structure spanning 108 days. The project is projected to yield a 15% Internal Rate of Return (IRR). The report acknowledges potential changes in business operations and management strategies following TLS adoption, emphasizing the need for a robust change management plan. It also identifies cybersecurity risks associated with increased access points and operational errors, proposing risk management procedures for mitigation.
Contribute Materials
Your contribution can guide someone’s learning journey. Share your
documents today.
High Quality Institute (HQI)
Teaching and Learning System (TLS)
Analysis Report
10/6/2017
Teaching and Learning System (TLS)
Analysis Report
10/6/2017
Secure Best Marks with AI Grader
Need help grading? Try our AI Grader for instant feedback on your assignments.
High Quality Institute (HQI)
Table of Contents
Introduction.................................................................................................................................................3
Aims and Objectives of the Project.........................................................................................................3
Scope of the Report.................................................................................................................................3
Project Requirements...................................................................................................................................3
Functional Requirements.........................................................................................................................3
Non-Functional Requirements.................................................................................................................4
Work Breakdown Structure (WBS).............................................................................................................5
System Analysis..........................................................................................................................................9
Net Present Value....................................................................................................................................9
Payback Period......................................................................................................................................10
Conclusions and Recommendations..........................................................................................................10
References.................................................................................................................................................12
Table of Contents
Introduction.................................................................................................................................................3
Aims and Objectives of the Project.........................................................................................................3
Scope of the Report.................................................................................................................................3
Project Requirements...................................................................................................................................3
Functional Requirements.........................................................................................................................3
Non-Functional Requirements.................................................................................................................4
Work Breakdown Structure (WBS).............................................................................................................5
System Analysis..........................................................................................................................................9
Net Present Value....................................................................................................................................9
Payback Period......................................................................................................................................10
Conclusions and Recommendations..........................................................................................................10
References.................................................................................................................................................12
High Quality Institute (HQI)
Introduction
High Quality Institute (HQI) is an educational firm that provides the students with many
different courses in the field of Information Technology. With the advancement of technology
and increase in the number of students, HQI has decided to implement a new technological
system called Technical and Learning System (TLS). This will comprise of a learning system for
undergraduate and postgraduate courses and there will be many features and functionalities that
will be implemented in the system.
Aims and Objectives of the Project
The primary aim of the project is to provide the students with an advanced and automated
teaching and learning system with improved quality and streamlining of activities.
The project will have the following objectives:
ï‚· Successful design and development of the undergraduate and postgraduate courses and
learning systems.
ï‚· Deployment of these two systems and their integration for the deployment of a teaching
and learning system.
ï‚· Accomplishment of the project tasks and activities with minimal risks and under the
estimated schedule and budget.
Scope of the Report
The report covers the functional and non-functional requirements of the project along with a
Work Breakdown Structure (WBS) supported by the table describing project activities and their
duration. Project budget, poster and recommendations have also been covered in the report.
Project Requirements
Functional Requirements
ï‚· Ability to allow the students, members of the staff and administrative members to
securely login to the system.
ï‚· Ability to view the undergraduate and postgraduate courses that are available with their
details such as duration, fee structure, modules covered etc.
Introduction
High Quality Institute (HQI) is an educational firm that provides the students with many
different courses in the field of Information Technology. With the advancement of technology
and increase in the number of students, HQI has decided to implement a new technological
system called Technical and Learning System (TLS). This will comprise of a learning system for
undergraduate and postgraduate courses and there will be many features and functionalities that
will be implemented in the system.
Aims and Objectives of the Project
The primary aim of the project is to provide the students with an advanced and automated
teaching and learning system with improved quality and streamlining of activities.
The project will have the following objectives:
ï‚· Successful design and development of the undergraduate and postgraduate courses and
learning systems.
ï‚· Deployment of these two systems and their integration for the deployment of a teaching
and learning system.
ï‚· Accomplishment of the project tasks and activities with minimal risks and under the
estimated schedule and budget.
Scope of the Report
The report covers the functional and non-functional requirements of the project along with a
Work Breakdown Structure (WBS) supported by the table describing project activities and their
duration. Project budget, poster and recommendations have also been covered in the report.
Project Requirements
Functional Requirements
ï‚· Ability to allow the students, members of the staff and administrative members to
securely login to the system.
ï‚· Ability to view the undergraduate and postgraduate courses that are available with their
details such as duration, fee structure, modules covered etc.
High Quality Institute (HQI)
ï‚· Assignment of a student to a course along with an advisor.
ï‚· Registration of the students for a particular unit by an associated advisor.
ï‚· Ability to the students to select an alternative advisor if the one assigned to the student is
not available
ï‚· Ability of the system to keep a track of the students along with their courses and units
and the advisors assigned to them (Dabbagh & Lee, 2014).
ï‚· Ability to allow the users to exchange emails between each other securely.
ï‚· Ability to communicate with the other users using a network connection and the chat
functionality installed in the system.
ï‚· Ability to extract reports on the student details, advisor details along with the course
information in a customized manner.
ï‚· Ability to the system to create data backups at regular intervals to maintain information
security and privacy.
Non-Functional Requirements
ï‚· System performance must be maintained so that the users do not face any issues in terms
of the lags or faulty connections.
ï‚· System availability must be included as one of the non-functional requirements so that
the students and the other system users may access the system at any hour and from any
location.
ï‚· System shall be reliable and must present updated and valid information in the reports
that are extracted or the response to any of the actions performed by the users.
ï‚· Usability shall be included as one of the prime system qualities so that functional aspects
listed above are covered and the user experience attained from the system is high (Broy,
2015).
ï‚· Supportability is one of the essential system qualities that must be present and included in
TLS so that the changes in requirements, technologies, users etc. can be handled and
incorporated as and when required.
ï‚· The system must be easy to use and it shall also be easy to maintain. The maintainability
of the system must be non-complex so that the updates can be easily installed.
ï‚· Assignment of a student to a course along with an advisor.
ï‚· Registration of the students for a particular unit by an associated advisor.
ï‚· Ability to the students to select an alternative advisor if the one assigned to the student is
not available
ï‚· Ability of the system to keep a track of the students along with their courses and units
and the advisors assigned to them (Dabbagh & Lee, 2014).
ï‚· Ability to allow the users to exchange emails between each other securely.
ï‚· Ability to communicate with the other users using a network connection and the chat
functionality installed in the system.
ï‚· Ability to extract reports on the student details, advisor details along with the course
information in a customized manner.
ï‚· Ability to the system to create data backups at regular intervals to maintain information
security and privacy.
Non-Functional Requirements
ï‚· System performance must be maintained so that the users do not face any issues in terms
of the lags or faulty connections.
ï‚· System availability must be included as one of the non-functional requirements so that
the students and the other system users may access the system at any hour and from any
location.
ï‚· System shall be reliable and must present updated and valid information in the reports
that are extracted or the response to any of the actions performed by the users.
ï‚· Usability shall be included as one of the prime system qualities so that functional aspects
listed above are covered and the user experience attained from the system is high (Broy,
2015).
ï‚· Supportability is one of the essential system qualities that must be present and included in
TLS so that the changes in requirements, technologies, users etc. can be handled and
incorporated as and when required.
ï‚· The system must be easy to use and it shall also be easy to maintain. The maintainability
of the system must be non-complex so that the updates can be easily installed.
Secure Best Marks with AI Grader
Need help grading? Try our AI Grader for instant feedback on your assignments.
High Quality Institute (HQI)
ï‚· Security is an extremely important and significant non-functional requirement that shall
be present in the TLS so that any of the security risks, threats and attacks are avoided and
prevented.
Work Breakdown Structure (WBS)
WB
S
Task Name Duration Predecessors
1 High Quality Institute - Teaching and Learning System
(TLS)
89 days
1.1 TLS Initiation 5 days
1.1.1 Feasibility Analysis - Operational Aspect 2 days
1.1.2 Feasibility Analysis - Technical Aspect 2 days
1.1.3 Feasibility Analysis - Economical and Environmental
Aspect
2 days
1.1.4 Results compilation and project chartering 4 days
1.1.5 Charter submission and project startup 1 day 3,4,5,6
1.1.6 Milestone One: Project Charter 0 days 7
1.2 TLS Planning 11 days
1.2.1 Scope determination and Management 5 days 8
1.2.2 Project Estimates - Budget, Schedule and Risks 8 days 8
1.2.3 Team planning, allocation and communication 5 days 8
1.2.4 Project approach and methodology 3 days 10,11,12
1.2.5 Milestone Two: Project Plan Document 0 days 13
1.3 TLS Execution 53 days
1.3.1 UI /UX aspects for undergraduate and postgraduate 10 days 14
ï‚· Security is an extremely important and significant non-functional requirement that shall
be present in the TLS so that any of the security risks, threats and attacks are avoided and
prevented.
Work Breakdown Structure (WBS)
WB
S
Task Name Duration Predecessors
1 High Quality Institute - Teaching and Learning System
(TLS)
89 days
1.1 TLS Initiation 5 days
1.1.1 Feasibility Analysis - Operational Aspect 2 days
1.1.2 Feasibility Analysis - Technical Aspect 2 days
1.1.3 Feasibility Analysis - Economical and Environmental
Aspect
2 days
1.1.4 Results compilation and project chartering 4 days
1.1.5 Charter submission and project startup 1 day 3,4,5,6
1.1.6 Milestone One: Project Charter 0 days 7
1.2 TLS Planning 11 days
1.2.1 Scope determination and Management 5 days 8
1.2.2 Project Estimates - Budget, Schedule and Risks 8 days 8
1.2.3 Team planning, allocation and communication 5 days 8
1.2.4 Project approach and methodology 3 days 10,11,12
1.2.5 Milestone Two: Project Plan Document 0 days 13
1.3 TLS Execution 53 days
1.3.1 UI /UX aspects for undergraduate and postgraduate 10 days 14
High Quality Institute (HQI)
systems
1.3.2 Design diagrams and system behavior 6 days 16
1.3.3 System development - Source code 31 days 17
1.3.4 Unit testing of the two sub-systems 5 days 18
1.3.5 Review and release to the test team 1 day 19
1.3.6 Milestone Three: Developed System 0 days 20
1.4 TLS Testing & Implementation 11 days
1.4.1 System Integration 4 days 21
1.4.2 System, Regression, Security and Performance Testing 6 days 21
1.4.3 Implementation and management of changes 5 days 23,24
1.4.4 Milestone Four: Test Report 0 days 25
1.5 Closure - Project Phase 5 9 days
1.5.1 User Trainings 4 days 26
1.5.2 Acceptance and Lessons Learned 2 days 26
1.5.3 System Documentation 7 days 26
1.5.4 Submission of the closure report 2 days 28,29,30
1.5.5 Milestone Five: Closure Report 0 days 31
systems
1.3.2 Design diagrams and system behavior 6 days 16
1.3.3 System development - Source code 31 days 17
1.3.4 Unit testing of the two sub-systems 5 days 18
1.3.5 Review and release to the test team 1 day 19
1.3.6 Milestone Three: Developed System 0 days 20
1.4 TLS Testing & Implementation 11 days
1.4.1 System Integration 4 days 21
1.4.2 System, Regression, Security and Performance Testing 6 days 21
1.4.3 Implementation and management of changes 5 days 23,24
1.4.4 Milestone Four: Test Report 0 days 25
1.5 Closure - Project Phase 5 9 days
1.5.1 User Trainings 4 days 26
1.5.2 Acceptance and Lessons Learned 2 days 26
1.5.3 System Documentation 7 days 26
1.5.4 Submission of the closure report 2 days 28,29,30
1.5.5 Milestone Five: Closure Report 0 days 31
High Quality Institute (HQI)
The Work Breakdown Structure and its supported table displayed above illustrate the project
tasks and activities and the duration that will be required for the accomplishment of every task.
The project will be completed in five phases as displayed in the WBS above. TLS has been kept
at the top most level followed by the five phases and then comes the sub-activities that will be
covered under every phase. The five phases that have been displayed above include initiation,
planning, execution, testing & implementation and closure (Miyahara, 2011).
High Quality Institute -
Teaching and Learning
System (TLS)
TLS Initiation
Feasibility Analysis -
Operational Aspect
Feasibility Analysis -
Technical Aspect
Feasibility Analysis -
Economical and
Environmental Aspect
Results compliation
and project chartering
Charter submission and
project startup
Milestone One: Project
Charter
TLS Planning
Scope determination
and Management
Project Estimates -
Budget, Schedule and
Risks
Team planning,
allocation and
communication
Project approach and
methodology
Milestone Two: Project
Plan Document
TLS Execution
UI /UX aspects for
undergraduate and
postgraduate systems
Design diagrams and
system behavior
System development -
Source code
Unit testing of the two
sub-systems
Review and release to
the test team
Milestone Three:
Developed System
TLS Testing &
Implementation
System Integration
System, Regression,
Security and
Performance Testing
Implementation and
management of
changes
Milestone Four: Test
Report
Closure - Project Phase
5
User Trainings
Acceptance and
Lessons Learned
System Documentation
Submission of the
closure report
Milestone Five: Closure
Report
The Work Breakdown Structure and its supported table displayed above illustrate the project
tasks and activities and the duration that will be required for the accomplishment of every task.
The project will be completed in five phases as displayed in the WBS above. TLS has been kept
at the top most level followed by the five phases and then comes the sub-activities that will be
covered under every phase. The five phases that have been displayed above include initiation,
planning, execution, testing & implementation and closure (Miyahara, 2011).
High Quality Institute -
Teaching and Learning
System (TLS)
TLS Initiation
Feasibility Analysis -
Operational Aspect
Feasibility Analysis -
Technical Aspect
Feasibility Analysis -
Economical and
Environmental Aspect
Results compliation
and project chartering
Charter submission and
project startup
Milestone One: Project
Charter
TLS Planning
Scope determination
and Management
Project Estimates -
Budget, Schedule and
Risks
Team planning,
allocation and
communication
Project approach and
methodology
Milestone Two: Project
Plan Document
TLS Execution
UI /UX aspects for
undergraduate and
postgraduate systems
Design diagrams and
system behavior
System development -
Source code
Unit testing of the two
sub-systems
Review and release to
the test team
Milestone Three:
Developed System
TLS Testing &
Implementation
System Integration
System, Regression,
Security and
Performance Testing
Implementation and
management of
changes
Milestone Four: Test
Report
Closure - Project Phase
5
User Trainings
Acceptance and
Lessons Learned
System Documentation
Submission of the
closure report
Milestone Five: Closure
Report
Paraphrase This Document
Need a fresh take? Get an instant paraphrase of this document with our AI Paraphraser
High Quality Institute (HQI)
The 3-level WBS shows the project activities in a hierarchical manner so that the project tasks
and activities are completed and accomplished with much ease and the determination of project
estimates is also easier (Hans, 2013).
Critical path diagram
The critical tasks are highlighted in yellow color:
Task Name
Results compilation and project chartering
Charter submission and project start-up
Milestone One: Project Charter
Project Estimates - Budget, Schedule and Risks
Project approach and methodology
Milestone Two: Project Plan Document
UI /UX aspects for undergraduate and postgraduate systems
Design diagrams and system behaviour
System development - Source code
Unit testing of the two sub-systems
Review and release to the test team
Milestone Three: Developed System
System, Regression, Security and Performance Testing
Implementation and management of changes
Milestone Four: Test Report
System Documentation
Submission of the closure report
Milestone Five: Closure Report
The 3-level WBS shows the project activities in a hierarchical manner so that the project tasks
and activities are completed and accomplished with much ease and the determination of project
estimates is also easier (Hans, 2013).
Critical path diagram
The critical tasks are highlighted in yellow color:
Task Name
Results compilation and project chartering
Charter submission and project start-up
Milestone One: Project Charter
Project Estimates - Budget, Schedule and Risks
Project approach and methodology
Milestone Two: Project Plan Document
UI /UX aspects for undergraduate and postgraduate systems
Design diagrams and system behaviour
System development - Source code
Unit testing of the two sub-systems
Review and release to the test team
Milestone Three: Developed System
System, Regression, Security and Performance Testing
Implementation and management of changes
Milestone Four: Test Report
System Documentation
Submission of the closure report
Milestone Five: Closure Report
High Quality Institute (HQI)
High Quality Institute (HQI)
Secure Best Marks with AI Grader
Need help grading? Try our AI Grader for instant feedback on your assignments.
High Quality Institute (HQI)
Class diagram
Class diagram
High Quality Institute (HQI)
Poster
Poster
High Quality Institute (HQI)
System Analysis
Net Present Value
The project will involve many costs and there will also be many benefits that will be earned as a
result. On the 5-year return on investment of the project, the net present value and its calculation
has been described below.
Year
0 1 2 3 4 5
Undiscounted
Flows
Costs of TLS -$43,000 -$32,800 -$32,800 -$32,800 -$32,800 -$32,800
Benefits of TLS $0 $45,540 $45,540 $45,540 $45,540 $45,540
Net Cash Flow -$43,000 $12,740 $12,740 $12,740 $12,740 $12,740
Discount Factors
Discount Rate
Applied on the
Project 6.0%
Base Year 0
Year Index 0 1 2 3 4 5
Discount Factor 1.0000 0.9434 0.8900 0.8396 0.7921 0.7473
Discounted Flows
Costs of TLS -$43,000 -$30,943 -$29,192 -$27,540 -$25,981 -$24,510
Benefits of TLS $0 $42,962 $40,530 $38,236 $36,072 $34,030
Net -$43,000 $12,019 $11,339 $10,697 $10,091 $9,520
Cumulative -$43,000 -$30,981 -$19,643 -$8,946 $1,145 $10,666
Net Present Value $10,666
Internal Rate of
Return 15%
System Analysis
Net Present Value
The project will involve many costs and there will also be many benefits that will be earned as a
result. On the 5-year return on investment of the project, the net present value and its calculation
has been described below.
Year
0 1 2 3 4 5
Undiscounted
Flows
Costs of TLS -$43,000 -$32,800 -$32,800 -$32,800 -$32,800 -$32,800
Benefits of TLS $0 $45,540 $45,540 $45,540 $45,540 $45,540
Net Cash Flow -$43,000 $12,740 $12,740 $12,740 $12,740 $12,740
Discount Factors
Discount Rate
Applied on the
Project 6.0%
Base Year 0
Year Index 0 1 2 3 4 5
Discount Factor 1.0000 0.9434 0.8900 0.8396 0.7921 0.7473
Discounted Flows
Costs of TLS -$43,000 -$30,943 -$29,192 -$27,540 -$25,981 -$24,510
Benefits of TLS $0 $42,962 $40,530 $38,236 $36,072 $34,030
Net -$43,000 $12,019 $11,339 $10,697 $10,091 $9,520
Cumulative -$43,000 -$30,981 -$19,643 -$8,946 $1,145 $10,666
Net Present Value $10,666
Internal Rate of
Return 15%
Paraphrase This Document
Need a fresh take? Get an instant paraphrase of this document with our AI Paraphraser
High Quality Institute (HQI)
Payback Period
Conclusions and Recommendations
The project will be completed in five phases as displayed in the WBS section in the report. The
overall duration of the project will be 108 days and the allocation of the schedule has been done
on the basis of the effort that will be required for project completion. The project will earn an
internal rate of return as 15% that shows that there will be considerable benefits that will come
out of the project.
There will be many changes that will be introduced in HQI after the implementation of TLS. The
management and administration must be ready to deal with such changes in terms of migration
of the business activities to the new system, change in the business operations and many more.
There shall be a change management plan that shall be designed in advance for this purpose
(Lindberg, 2013). There may also be many of the risks that may emerge during the project. The
primary category of these risks will be security risks and attacks. These risks may be introduced
due to the increased access points and the operational errors executed by the users leading to
Payback Period
Conclusions and Recommendations
The project will be completed in five phases as displayed in the WBS section in the report. The
overall duration of the project will be 108 days and the allocation of the schedule has been done
on the basis of the effort that will be required for project completion. The project will earn an
internal rate of return as 15% that shows that there will be considerable benefits that will come
out of the project.
There will be many changes that will be introduced in HQI after the implementation of TLS. The
management and administration must be ready to deal with such changes in terms of migration
of the business activities to the new system, change in the business operations and many more.
There shall be a change management plan that shall be designed in advance for this purpose
(Lindberg, 2013). There may also be many of the risks that may emerge during the project. The
primary category of these risks will be security risks and attacks. These risks may be introduced
due to the increased access points and the operational errors executed by the users leading to
High Quality Institute (HQI)
enhancement of the security vulnerabilities. These risks shall be handled by using risk
management procedure with adequate identification and analysis of the risks. The overall project
management must also be efficiently done so that the project goals are met and there are no
major risks involved (Kumar & Gregory, 2013).
enhancement of the security vulnerabilities. These risks shall be handled by using risk
management procedure with adequate identification and analysis of the risks. The overall project
management must also be efficiently done so that the project goals are met and there are no
major risks involved (Kumar & Gregory, 2013).
High Quality Institute (HQI)
References
Broy, M. (2015). Rethinking Nonfunctional Software Requirements. Computer, 48(5), 96-99.
http://dx.doi.org/10.1109/mc.2015.139
Dabbagh, M., & Lee, S. (2014). An Approach for Integrating the Prioritization of Functional and
Nonfunctional Requirements. The Scientific World Journal, 2014, 1-13.
http://dx.doi.org/10.1155/2014/737626
Kumar, M., & Gregory, M. (2013). An exploration of risk management in global industrial
investment. Risk Management, 15(4), 272-300. http://dx.doi.org/10.1057/rm.2013.8
Lindberg, D. (2013). Change Management Tools for Systemic Results. Change Management: An
International Journal, 12(3), 1-6. http://dx.doi.org/10.18848/2327-798x/cgp/v12i03/50736
Miyahara, T. (2011). Scheduling and Management of Information System Implimentation
Prosess: IT Project Management Based on Work Breakdown Structure. Japanese Journal
Of Radiological Technology, 67(4), 393-399. http://dx.doi.org/10.6009/jjrt.67.393
T. Hans, R. (2013). Work Breakdown Structure: A Tool for Software Project Scope Verification.
International Journal Of Software Engineering & Applications, 4(4), 19-25.
http://dx.doi.org/10.5121/ijsea.2013.4402
References
Broy, M. (2015). Rethinking Nonfunctional Software Requirements. Computer, 48(5), 96-99.
http://dx.doi.org/10.1109/mc.2015.139
Dabbagh, M., & Lee, S. (2014). An Approach for Integrating the Prioritization of Functional and
Nonfunctional Requirements. The Scientific World Journal, 2014, 1-13.
http://dx.doi.org/10.1155/2014/737626
Kumar, M., & Gregory, M. (2013). An exploration of risk management in global industrial
investment. Risk Management, 15(4), 272-300. http://dx.doi.org/10.1057/rm.2013.8
Lindberg, D. (2013). Change Management Tools for Systemic Results. Change Management: An
International Journal, 12(3), 1-6. http://dx.doi.org/10.18848/2327-798x/cgp/v12i03/50736
Miyahara, T. (2011). Scheduling and Management of Information System Implimentation
Prosess: IT Project Management Based on Work Breakdown Structure. Japanese Journal
Of Radiological Technology, 67(4), 393-399. http://dx.doi.org/10.6009/jjrt.67.393
T. Hans, R. (2013). Work Breakdown Structure: A Tool for Software Project Scope Verification.
International Journal Of Software Engineering & Applications, 4(4), 19-25.
http://dx.doi.org/10.5121/ijsea.2013.4402
1 out of 16
Related Documents
Your All-in-One AI-Powered Toolkit for Academic Success.
 +13062052269
info@desklib.com
Available 24*7 on WhatsApp / Email
Unlock your academic potential
© 2024  |  Zucol Services PVT LTD  |  All rights reserved.