R012 revision

R012 revision

1. Legislation

   • DATA PROTECTION ACT
     • Passed by UK Parliament to stop any abuse of your personal data. First created in 1984 but updated in 1998. 8 main principles
     • All data must be used lawfully and fairly processed.
     • All personal data must be obtained for specific use and cannot be used for anything else
     • Personal data must not be excessive and needs to be relevant and adequate.
     • All personal Data must be accurate and up-to-date.
     • Data must not be kept for any longer than it needs to be.
     • Data must be processed in line with our rights
     • Data must be held securely
     • All Personal Data must not be transferred across countries outside of the European Economic Area unless the country had similar data protection laws.
   • COMPUTER MISUSE ACT
     • Passed to stop any purposeful attacks or theft of data against you. Founded in 1990 Offences include: hacking, data misuse and unauthorised transfer or copying. Copying and distributing copyrighted software, music and film. Email and chat room abuses.Pornography  Identity and financial abuses Viruses. 
     • OFFENCE 1 - Unauthorised access to someone's computer
       • Logging onto someone's account without permission. Could either have a hefty fine or 6 months in prison.  Example:  Gary Mckinnon – broke into the Pentagon's computer systems back in 2008
     • OFFENCE 2- Unauthorised access to someone's computer with intention to commit a crime
       • Logging onto someone's computer to do bad things. You could have a hefty fine or up to 5 years in prison.  
     • OFFENCE 3- Unauthorised modification to someone's computer material
       • Logging on to someone's computer without their permission and changing a document. You could have either a hefty fine or up to 5 years in prison.
     • OFFENCE 3a/4- making, supplying or obtaining that could be used in Computer Misuse Act

2. Project Planning

   • SMART
     • Specific
       • For you to achieve your project goals, it's best to be as specific as possible
       • Who is going to be involved?
       • What do you want to accomplish?
       • WHen is it going to start? and happen?
       • Where is this going to happen?
       • Why do you need to do this?
       • What things are you going to need
     • Measureable
       • Create criteria that you can use to measure the success of a goal.
     • Achievable
       • Identify the most important goals and what it will take to achieve them
     • Realistic
       • You should be willing and able to work towards a particular goal
     • Time-bound
       • Create a time-frame to achieve the goal
   • Phases
     • Initiation
       • Inputs
         • User Requirements
           • The user requirements form part of the input to the initiation phase. The user requirements define what the client wants the product to achieve
             • The requirements may be generic such as:  ● keeping records about suppliers  ● producing reports about the most popular products  ● the website must have ten linked webpages.  When the product is being created during the execution phase, these generic requirements will be used by the development team who will use their skills to create a product which meets the requirements.  It is important to remember that a client may not have the specialist skills needed to clearly define the requirements for a product, and they are not really bothered how the requirement is met as long as it is.  The client will liaise with the project manager to discuss the user requirements of the product. 
         • User Constraints
           • These are given to the project manager by the client and form part of the input to the initiation phase. The constraints are restrictions which the project manager must stick to during the project life cycle.
             • There are four constraints:  ● timescale: the start and end date for the project. The end date is when the deliverable product is released to the client.  ● budget: the amount of money that can be spent during the project. If the project is planned in enough detail then the budget should not be exceeded. There are, however, always exceptions to this.  ● hardware: the hardware that the client wants the deliverable product to be installed or run on. The hardware to be used during the creation of the product may also be defined by the client.  ● software: the software that the client wants the deliverable product to use to run on. The software to be used during the creation of the product may also be defined by the client. 
       • outputs
         • Feasibility report
           • The feasibility report includes the answers to all the questions that are asked during the initiation phase
             • The report can also include different solutions for the client. The client can then select the solution they would like to be created. The feasibility study will also consider the constraints and requirements which have been provided by the client. These need to be realistic if the project is to go ahead. If any of the requirements or constraints are not realistic, then the project manager can liaise with the client to create new requirements and constraints
         • Legislation implications
           • The legislation implications will need to be considered at the start of the project.
             • The legislation implications also  form part of the input for the planning phase.
     • planning
       • User requirements- inputs

3. Planning Tools

   • GANTT Chart
     • A GANTT chart is used for Project Management. It was developed in 1917 by Henry L. Gantt 
   • PERT Chart
     • A PERT chart is a Network Analysis Chart. It stands for Program Evaluation, Review Technique.  It shows the start and end date of a project. It was first used by the US Navy in 1950's. Each section of a PERT chart is called a PERT event. It marks the start of completion of one or more activities. There are also predecessor events, which occur immediately before some successor event, which naturally occurs afterwards. STRUCTURE: Task label at the top left earliest start at the top middle Earliest finish top right task time bottom left  latest start bottom middle latest finish bottom right  the task in the centre
   • Mindmap
     • Invented by Tony Buzan.  Used to visualise organised information.  .