You and your group will be assessed in three ways. First, your group-mates will give you a grade based on your performance in the group. Second, you will provide documentation about your submission. Finally, your group’s virtual network itself forms part of your submission. Your network must be up and running on the due date and remain so for at least one month after the due date. During the marking period, you should monitor your IFN641 network email addresses for requests from your CEO and the markers.
Note that, although some of the requirements will be fulfilled through your practicals, many of the requirements go beyond what is done in the practicals. It is your responsibility to gather the required information in order to meet these requirements.
3 System Requirements
On your virtual environment, you must set up a network with the following requirements:
The network must be split into two sub-networks. One network for a demilitarised zone (for servers) and one network for internal hosts (user desktops etc.). You must have a separate router for each network.
The internal network must have at least two desktop workstations (simulated in VMs) for users, one of which should be the CEO’s machine. The CEO’s machine must have Firefox and Sylpheed installed.
The CEO should be able to operate their desktop externally (i.e. from other IFN641 networks) using one of VNC or RDP (1 mark)
• Users are able to access external websites from other IFN641 groups (1 mark)
• Internal Routing uses OSPF (1 mark)
• External Routing uses BGP (1 mark)
DNS is set up with your delegated domain name, and a name server is running on your network for this delegated domain name and answers requests from the IFN641 network. (1 mark)
DHCP should be set up for user workstations. The workstations should acquire their IP addresses via DHCP (1 mark)
A network file system for users to store and share company documents, with shares mounted automatically on boot on the user desktops (1 mark)
Email is working externally to other IFN641 groups and internally within your network, with the following email accounts/aliases set up (1 mark)
– firstname.lastname@example.org for each member of your group
– email@example.com which is a group reaching all the members of your group
– postmaster or hostmaster aliases, set up as required by the relevant RFCs
• Email can be sent/received with a webmail interface (1 mark)
• A web server is set up, hosting a website using PHP and MySQL is accessible, with
– Public content describing the company's products or services. The team is to develop a fictional product or service for the company to provide. This must be available from other IFN641 networks
– Internal content including the names and contact email addresses of the members of the team. This must not be accessible from external IFN641 networks, but must be accessible from user desktops.
– The web server should allow the CEO to create their own PHP pages accessible while they are on sales trips. (2 marks)
• An internal employee wiki or forum or blog is set up, with sufficient access controls to allow
– Private wiki or forum or blog pages, with read/edit access for your team members and the CEO
– Public wiki or forum or blog pages, where anyone can contribute. This is mainly for customer feedback. (1 mark)
All servers must be accessible using ssh from your group’s network. At least one machine must be accessible via ssh externally. (1 mark)
In each item, for full marks your solution must work correctly and completely implement the required functionality.
You must have separate virtual machines for each router, each user desktop, email, web server, DNS, and NFS. DHCP may be installed on an appropriate router VM or on its own VM.
4 Documentation Requirements
You are expected to have documented your progress and meetings and configurations, etc. Your documentation needs to contain/address:
• Organisational structure, how have you broken your group into smaller teams
• List of all team members and their responsibilities
List of all team meetings (starting week 4), when they occurred, action items arising and if those action items were actually completed
• System and Network Design describing detailed reasoning for design choices.
Documentation on how the network and each service is built and configured. Consider this your disaster recovery documentation, it does not need to be a tutorial on how to create a service but does need to contain enough information that a reasonably competent systems administrator could recreate a working service using your documentation. (2 marks)
Details of testing and use cases for all of the services and evidence (screenshots) of whether those services passed that testing. Please note that fabricating evidence is seen very unfavourably and may result in grade penalties. (2 marks)
User documentation for the CEO to access the IT systems and to create web pages. This should be usable by someone with only basic knowledge and cover the following tasks: (1 mark)
– Log into the CEO’s desktop from outside the network. You may assume that they are already connected to the IFN641 network. For example they may be connected to another group’s network.
– Upload web content, including php scripts, to the company web server
– Fetch and send email using Sylpheed with SMTP/IMAP, and via a webmail interface.
– Edit/add items to the company blog/wiki/forum
• Evidence of bug and issue tracking. (1 mark)
Additionally, you must provide
The CEO’s login details. These should work for all services that the CEO has access to, and should have root privileges via sudo on all servers.
For full marks in each item, your documentation must be complete, correct, well presented and easy to understand.
Please note the that plagiarism is consider academic misconduct. Copy/pasting from websites or other material is not acceptible. All documentation must be your own.
5 Peer Assessment
You will be provided with a Peer Assessment Reflection Word document to provide a reflection and peer assessment mark with justification for each team member. In the Peer Assessment Reflection document, you should award a mark out of 10 for each team member. Each student should submit the assessment of his or her peers via Blackboard Grade Centre. (5 marks)
If a team member does not participate or participates significantly less than other team members, a percentage penalty will be applied to that team member’s group component marks.
6 Process and Procedure Requirements
You are expected to meet at least weekly during the unit practical session. Your team meetings should have some formal structure and if action items are issued to individual team members then this should be recorded and indicated if it had been completed (see above documentation requirements)
You are also expected to follow an established IT change management process. The exact process you use will be a group decision and should reflect the breakdown of the group into teams and individual team members. Adherence to this process is a key requirement of the unit.
Total marks: 30