This Unit will be assessed by assignment and Presentation.
You are strongly recommended to read “Preparation guidelines of the Coursework Document” before answering your assignment.
ASSIGNMENT
- 1. Objective
This coursework is designed in the form of set questions and design scenario. The tasks are divided into four sections, with section compromising several questions. The coursework should be submitted as one document in a report format.
Assignment Scenario:
You are working as a network server engineer. You have been assigned a new project to design, implement and support the network of a recruitment company which was established in 2014.
The company planning to install 122 client computers, two servers and four network printers, so that they can meet the company requirements. All users should be able to share all the printers, but department within the company will need to share a specific folders assigned to each department.
The company data should be treated on high level of security in terms of confidentiality and availability. So, all users should be controlled and managed by an administrator according to users’ needs and requirements, and all the machines within the network should be up-to-date with the new patches and service pack and latest security patches to avoid any security related issues.
The company as well forecasting an expansion in the foreseeable future and hence you have to put in mind the capability to expand the network when needed (Scalability).
The IT manager of the company decided to use a private IP address Range of 10.20.0.0 /24 to be distributed on all the network devices including the servers, workstation and printers. The network manager specifically asked for the following criteria to be fulfilled for the project (Software availability, Scalability, Maintainability and Technical support)
Task 1
1.1. Identify and evaluate different types of operating systems available in the market, your evaluation and discussion must include the following: [P1.1, P1.3, D1]
- Identify the required network services for the above scenario
- Discuss the available network operating system that can fulfil the requirements.
- Critically compare and justify different network operating system available in the market in terms of (software availability, security, Technical support, etc.).
- Based on your evaluation and justification, recommend a network operating system for the above company
1.2. Business continuity and disaster recovery are crucial for any organisation, discuss the following in relation to disaster recovery: [P1.2, M1]
- What do you understand by the term disaster recovery & Business continuity?
- Explain the benefits of implementing an effective disaster recover strategy?
- Explain different types of backup options and devices?
- Explain different RAID options in relation to availability?
- To achieve M1, you should have made effective judgement including a relevant theories and techniques have been applied and met the deadline to submit the tasks and achieved the unit assessment criteria.
- To achieve D1, you should have made a detailed comparison of many operating system available in the market giving the advantages/disadvantages of such operating systems in view of the requirement given in the scenario based on which you should select the most appropriate operating system justifying your choice by eliminating any disadvantages and rectifying the weakness concentrating on security, maintainability and software availability.
Task 2
2.1. Prepare a detailed plan for the implementation of NOS with the following information: [P2.1, D2]
- Installation: Server hardware specification, (your hardware configuration must be compatible to the Operating System you have chosen)
- Addressing: IP address allocations for all the servers, workstations and printers, including the CLASS and range of IP Address.
- Security: what do you understand by the term password policy, patch management etc..
- Disaster recovery: explain what would you prepare in case of disaster
2.2. Evaluate and justify you plan and users feedback including: [P2.2, M2]
- Evaluation of hardware selection in relation to the scenario requirements i.e. (RAID, Memory, Processors etc…)
- Components: Evaluate network components scalability and Availability
- To achieve M2, you should have made effective judgement including a range of relevant theories and techniques have been applied, a range of sources of information has been used.
- To achieve D2, you should have made a plan by which you have accounted for the unforeseen and accommodated the plan with necessary devices/routines disaster recovery, including alternative approach and critical evaluation procedures and user feedback, demonstrating autonomy and independence
Task 3
3.1. Install your selected NOS including: [P3.1, M3]
- Installation: step by step installation process document (Show the screenshots of the installation process from LAB)
- Services: required services & any specialised configuration
- Naming: Directory services, application of addressing
3.2. Configure and test password security policy, including adding users and groups to meet the given requirement [P3.2, P3.3, D3]
- Security: Setting of administrative rights, setting of password policy etc..
- Network simulated: show how devices can access services and/or other devices using any network simulation.
- Documentation: analyse and document your network against scenario requirements giving some recommendation to enhance the performance and availability.
- To achieve M3, you should have made an appropriate structure to fulfil the requirement of the given question, including a range of methods in presenting the solution using appropriate technical language accurately.
- To achieve D3, you should have applied and effective and creative thinking in unfamiliar contexts including self-evaluation in solving problems, providing alternative methods and/or approach in the solution given.
Task 4
4.1. There are many tools available in the market to monitor the network, identify, select and justify one of the tools to produce a performance baseline report. [P4.1]
4.2. Network operating system should always be monitored against threats, Justify and produce Baseline Security Report, including (Patches & Security updates, NOS vulnerability, Weak password, etc.) for the client network. [P4.2, P4.3, M3]
- To achieve M3, you should have made an appropriate structure to fulfil the requirement of the given question, including a justification in using appropriate tools and a range of methods in presenting the solution using appropriate technical language and tools.
Presentation
As part of the overall assessment of this assignment, you will need to prepare an oral presentation of your individual work. You will use power point presentation or similar presentation package of your choice. The presentation will last 10 – 15 minutes. You will be marked on content, presentation style and clarity of delivery.
Relevant Information
1. Outcome of the Units
Learning outcomes | Assessment criteria for pass to achieve each outcome a learner must demonstrate | Questions Reflecting the Outcome |
LO1 Understand network operating systems principles | 1) evaluate types of NOS and NOS services2) discuss the benefit of disaster recovery and NOS security3) critically compare a selection of current NOS’s in use | Q1.1, Q1.2 |
LO2 Be able to plan the implementation of network operating systems | 1) plan the implementation of a NOS for a required service to meet a given specification2) evaluate the plan and analyse user feedback | Q2.1, Q2.2 |
LO3 Be able to implement network operating systems | 1) implement a NOS service based on a prepared plan2) test the NOS to meet user requirements3) document and analyse test results against expected results | Q3.1, Q3.2 |
LO4 Be able to manage network operating systems | 1) establish and justify a performance baseline2) monitor NOS performance against the baseline3) Justify performance optimisation and update to NOS. | Q4.1, Q4.2 |
Table of Contents
Task 1. 2
Task 2. 3
Task 3. 4
Task 4. 11
Task 1
1.1. Available Network Operating Systems in the market:
- Cisco IOS: Most Cisco Systems routers and network switches employ the Cisco IOS, originally called Internetwork Operating System, which provides a multitasking environment for routing, switching, internetworking and telecommunication functionality. The Cisco IOS provides a command-line interface which operates on a fixed set of multiple-word commands, with the current mode of operation and privilege level of the user determining the available set of commands.
- Junos OS: This operating system is employed in hardware routers by Juniper Networks. It is FreeBSD-based, and provides routing, switching and security functionalities. Junos OS supports a number of networking protocols as well as such features as stateful firewall, NAT, and IPSec.
- MikroTik RouterOS: This NOS is based on the linux kernel and is capable of turning any standard x86-based computer into a network router. It is usually employed on MikroTik’s proprietary hardware, the RouterBOARD series, and implements such features as firewalling, Virtual Private Network (VPN) service and client, wireless access point functions, and bandwidth shaping, among others.
1.2.
- Disaster Recovery and Business Continuity: Whenever a natural or human-made disaster causes critical failure of core technological infrastructure to a company or business, the Disaster Recover and Business Continuity policies come into effect. These policies enable the business to recover core business functionality and continue operating at least its most critical operations. Business continuity thus focuses on ensuring that even in the case of major disruptive events, the business continues to be functional. Disaster recovery is a subset of business continuity and focuses on recovering functionality and technological infrastructure after it is disrupted or destroyed.
- Importance of Disaster Recovery Planning: IT infrastructure has become the very core of almost all businesses, so much so that sudden loss of IT infrastructure and IT services can cause entire companies to shut down and never recover. Therefore, investment in disaster recovery planning helps avoid such a situation.
- RAID options as compared according to Availability: In RAID 0, there is no added redundancy for handling disk failures, thus causing the entire volume to crash in case of a disk failure. In RAID 1, there is mirroring of disks so that there are two physical drives for every logical volume. As long as at least one disk is functional, the volume stays operative. In RAID 2, bit-level striping occurs, but no provisions are available for backup drives. Therefore, if a single drive fails, it may cause system failure. RAID 3 uses bytle-level striping rather than bit-level striping as in RAID 2, but still contains a single point of failure. RAID 4 improves over RAID 2 and RAID 3 by allowing I/O parallelism, but there is still a single point of failure. RAID 5 provides block-level striping with distributed parity, thus allowing the system to stay online as long as only one drive failure occurs. RAID 6 provides double distributed parity and can tolerate two drive failures.
Task 2
2.1.
- Password Policy: The password policy of a system is a set of rules that determine valid password patterns for user passwords. Password policies are generally set in place to promote usage of strong passwords by eliminating usage of weak password patterns. Password policies may be advisory or mandatory.
- Patch Management: Patches are small pieces of software that update an existing software on a computer system, generally providing additional functionality, bug fixes, or other improvements. Patch management is the strategy employed to determine the schedule or plan according to which patches are applied to a system.
2.2.
- The hardware component needed for the system is:
RAM: 256 MB
Processor: i3
Hard disk: 20 GB
- The components used in the system can be connected such that it remains scalable, like routers and switches with many ports.
Object oriented programming
Name of the student:
Name of the University:
Table of Contents
Task 2. 2
2.1 The Use Case diagram of important feature and UI design. 2
2.1.0 Use case diagram.. 2
2.1.1 UI design with the usage and data flow.. 2
2.2 UML Class diagram.. 4
Task 3. 5
3.1 Implementation software design. 5
3.2 The commented code: 7
3.3 The reasons for made any changes. 8
3.4 The Screenshots evidence. 8
Task 4. 15
4.1 Testing and review of OOP solution. 15
4.2 The analysis of test result 19
4.3 Feedback and recommendations. 19
4.4 The on-screen help to assist the users. 20
4.5 The support and maintained of the OOP Solution. 22
Bibliography. 22
Task 2
2.1 The Use Case diagram of important feature and UI design
2.1.1 UI design with the usage and data flow
The underneath client interface is given for upgrade convenience of a client and clear comprehension of this new structure. This structure is appearing in underneath figures.
3.2 The commented code:
Here the programmer use some appropriate comments in some block of coding, which clearly define how the code fetch data from the database and update. Here various type of SQL queries are used for selecting some data, delete, insert and update. This comments are helps the users to understand the function of this lines.
3.3 The reasons for made any changes
In this application, the programmer use Microsoft access to build the database for storing data. Here the main cause of make any change in this application is lack of storage, when this prototype application will be used in a real environment. Therefore if there are any possible option to develop it in RDBMS or BIG DATA structure then it can store huge information and which can manipulate this more efficiently.
3.4 The Screenshots evidence
Screen capture 1:
Task 4
4.1 Testing and review of OOP solution
Review: The OOP arrangement is created in Visual Studio 2012, utilizing C#. Here the an understudy can login into this framework to see their advancement and instructive subtle elements. Here an understudy has some constrained get to, for example, an understudy can’t alter, include or erase a record in their database. A database administrator or staff can sign in with all conceded benefits. They can adjust, include or erase a record furthermore deliver a report for understudies or staffs.
Testing: The testing process is procced by some phases, which are given underneath.
Step 1: Relation test of college database
Step 2: in this section, the programmer going to test the expected result with the current output. Here two types of testing process is applied one is black box testing and white box testing.
White Box Testing: Now the developers achieve the white box testing, they try to identify the bugs in this application. If any exception and code bugs detected then it, remove by appropriate coding methods.
In this application, login section contains the flowing programming codes. Here a Button is used to trigger an event. This event will call the method called Execute Query. In this section the researcher provide this example to find the how a white box testing is performed. Let’s see the underneath coding structure, where the developer uses a MySQL database connection and reader to read the value from the database and validate that the current user. Now the developer uses this login system several times with the test data and until it satisfied the actual outcome.
4.2 The analysis of test result
Step |
Test Steps |
Test Data |
Expected Result |
Actual Result |
Status (Pass/Fail) |
Notes |
1 |
Navigate to login page |
|
User should be able to log in |
User should be able to log in |
|
All page are loaded |
2 |
Provide valid username |
User=0001 |
User is navigated to dashboard with successful login |
User is navigated to dashboard with successful login |
Pass |
Successfully login |
3 |
Provide valid password |
Password: 1234 |
|
|
Pass |
Password accepted |
4 |
Click on Deshboard options |
Click on 1 |
Open the next page successfully |
Open the next page successfully |
pass |
Load successfully |
5 |
Update student infromation |
Enter data Student code: 0008 Name: XYS Status: single Course Code: if any College Code: if any |
Commit successfully |
Commit successfully |
Pass |
Data instserted successfully |
4.3 Feedback and recommendations
Feedback: This framework is intended for proposed a programmed framework that disposes of a manual framework. Here this arrangement helps them to element report era where they can create every data of montage, course, classes and an aggregate number of understudy in school. This framework upgrades the efficiency of observing all data. This data framework store information in MySQL database, this is a connection a database. In this product, the clients can work with a GUI based application. This GUI application upgrades the clients around an unmistakable comprehension of its operations and info information.
Recommendation: In this product the developer utilizes connection database structure to store all data. All things considered, it is ease administration on the off chance that this framework contains tremendous information set then it ought to incorporate Big information base. In this circumstance, the college or school require more costs on Big information usage. In this framework, the client interface might be changed for Big information system then it ought to be executed for good with another structure.
4.4 The on-screen help to assist the users
Here all onscreen help are showing in few steps. Therefore, the users should follow this steps and so on.
4.5 The support and maintained of the OOP Solution
This framework underpins numerous sorts of information for information and yield operation. Here all data are assembled by means of GUI. It bolsters more than 10000 information in this database, and it can be keep running in windows 7, windows 8 and windows 10. The base framework prerequisite for this framework is given beneath:
Bibliography
Bracha, G. and Ungar, D., 2015. OOPSLA 2004: Mirrors: Design Principles for Meta-level Facilities of Object-Oriented Programming Languages.ACM SIGPLAN Notices, 50(8), pp.35-48.
Dai, W., Vyatkin, V. and Christensen, J.H., 2016. Applying IEC 61499 design paradigms: Object-oriented programming, component-based design, and service-oriented architecture. Distributed Control Applications: Guidelines, Design Patterns, and Application Examples with the IEC 61499, 9, p.39.
Dai, W., Vyatkin, V. and Christensen, J.H., 2016. Applying IEC 61499 design paradigms: Object-oriented programming, component-based design, and service-oriented architecture. Distributed Control Applications: Guidelines, Design Patterns, and Application Examples with the IEC 61499, 9, p.39.
Davi, L., Liebchen, C., Sadeghi, A.R., Snow, K.Z. and Monrose, F., 2015. Isomeron: Code Randomization Resilient to (Just-In-Time) Return-Oriented Programming. In NDSS.
Dennis, A., Wixom, B.H. and Tegarden, D., 2015. Systems analysis and design: An object-oriented approach with UML. John Wiley & Sons.
Dhara, K.M., Dharmala, M. and Sharma, C.K., 2015. A Survey Paper on Service Oriented Architecture Approach and Modern Web Services.
Graves, D., 2015. Promoting Computer Science with Video Games: Teaching Object-Oriented Programming through Unity (Doctoral dissertation, California Polytechnic State University San Luis Obispo, CA).
Guo, P. and Shi, X., Intel Corporation, 2015. Type checking for object-oriented programming languages. U.S. Patent 9,009,688.
Holopainen, T., 2016. Object-oriented programming with Unity: Inheritance versus composition.
Holopainen, T., 2016. Object-oriented programming with Unity: Inheritance versus composition.
Myers, A.C., Liskov, B., Loring, M.C., Salvaneschi, G. and Zhang, Y., 2015. Genus: Making Generics Object-Oriented, Expressive, and Lightweight.
Obermeier, M., Braun, S. and Vogel-Heuser, B., 2015. A Model-Driven Approach on Object-Oriented PLC Programming for Manufacturing Systems with Regard to Usability. Industrial Informatics, IEEE Transactions on, 11(3), pp.790-800. Wu, D., Chen, L., Zhou, Y. and Xu, B., 2015. A metrics-based comparative study on object-oriented programming languages.
Schuster, F., Tendyck, T., Liebchen, C., Davi, L., Sadeghi, A.R. and Holz, T., 2015, May. Counterfeit object-oriented programming: On the difficulty of preventing code reuse attacks in C++ applications. In Security and Privacy (SP), 2015 IEEE Symposium on (pp. 745-762). IEEE.
Uysal, M.P., 2015. Evaluation of learning environments for object-oriented programming: measuring cognitive load with a novel measurement technique. Interactive Learning Environments, pp.1-20.
Zhang, Y., Loring, M.C., Salvaneschi, G., Liskov, B. and Myers, A.C., 2015, June. Lightweight, flexible object-oriented generics. In Proceedings of the 36th ACM SIGPLAN Conference on Programming Language Design and Implementation (pp. 436-445). ACM.
Zhang, Y., Loring, M.C., Salvaneschi, G., Liskov, B. and Myers, A.C., 2015. Genus: Making Generics Object-Oriented, Expressive, and Lightweight.