Please enable JavaScript.

Coggle requires JavaScript to display documents.

lo1 - Coggle Diagram

- - - - tasks processesm
      - task dependencies
      - workflow
      - milestones
      - resources needed
  - - - dates along the top
      - tasks down the left and blocks to represnet the time allocated to each task
        milestones and diamonds
        concurrent dependent tasks
    - - show nodes and subnodes as well as concurrent and dependent tasjs and can shiow task sequences
        dependent tasjs
        concurrent tasks
        can show ritical apath
    - - nodes subnodes branches
  - - - adv
        
        can show estimated time schedule
        
        tasks are shown againsgt a time schedule
        
        comments can be added
        
        resources for each task can be sown
      - dis advctask
        
        an be considred to simple for complect prokect
        
        task time is estimated so may be unrealistic
        
        not easy to identify critical path
        
        dependencies can be difficult to identify at start of the project
    - - adv
        
        can show slack time so resources can be reallocated
        
        enables timescales to be planned
        
        tasjscan be scheduled as dependent or concurrnet
      - disadv
        
        can become confusing
        
        needs skill and knowledge to vreate
        
        can be limited ijn large and complex projects
    - - adv
        
        information can be quickly understood e
        
        emerging trends and patterns can be quickly spotted
        
        non specialist can uderstand the data being used
      - disadv
        
        not appropriate for large anc omplex projects
    - - adv
        
        can be useful for simple projects with a small number of tasks and decisions
        
        no specialst project planninh knowledge neede dto undersyand the flow chatty
      - disadv
        
        does not show time allocated
        
        doesnt show concurrent tasks cos theyre shown in a sequence
    - - adv
        
        easy to add ideas tasks at any time
        
        can provide focus on the tasks and the lineks between them
        
        shows dependent tasks d
      - dis
        
        no time schedule
        
        can be hard for others to undersyand
        
        no concurrent tasks
    - - adv
        
        provide focus on the tasks to be completed and no tasks to be missed out
      - dis
        
        shpuldnt be used for large projects
- - - - gather user requirements and constraints from client, define success criteria and objectives, consider legislation implications, create feasability report and complete phase review
    - - timescale
      - budget
      - security requirements and legislation implications
      - hardware and software that software that should be used during the development of the final product
      - the hardware/software that should be used during the development of the final project
  - - - the product will need to be tested during creatiion and after ut has been complete. Initial tets plans are created
  - - - longest phase in the project
      - project manager use the project plans to monitor the project- project must be kept on track so the product is delivered to client on time - this is the time constraint
- - - - real time changes can be made and project plans can be shared electronically
        project plans can include allocated resoucres
        reports can be generated eg to show resources needed for each tasks
    - - some project management software is very expensive
      - possibilit that a simple project can become very complicated and alsocan be time consuming to set up a project
      - may neeed some knowl,edge training or experience to use the siftware
- - - - user requirements
        
        define what the client wants the product to achieeve
        
        are created between the client and the project manager
        
        can be general or specific
      - user constraintgs
        
        are given to the project manager by the client
        
        are restrictions that must be adhered during the creation of the prodyct
        
        main constraints
        
        time budget hardware and software
    - - feasability report
        
        answers the questions asked uring the initiation stage amd can also include proposed solutions for the client
        considers the client defined constraits and the requirements that have been said
      - legislation implications
        
        depends on the type of products being created and the assets being used, may need to be revisisted during the project to check the legislation nasnt been updated
  - - - feasabuility report
      - legislatiion implications
    - - project plan
        
        is created by the project manager
        
        forms the basis for the completion of the proect
        
        includes tasks resources needed milestones contingency time and workflow and end date
      - test plan
        
        during the planning phase will be related to checking the user requirements are being met
        
        could be used in the execution phase
      - constraints lusr
        
        created frm the client defined constraints provided in the initiation phase
        
        provides detailed infomration about each of the constraints
        
        constantly referred to during project life cycle
        
        referred to during phase reviews to make sure all the constraints are being met
  - - - deliverable product
        
        the product is created and tested bugs or errors found must be corrected
        retests are carried out to ensure that the product works as intended and meets the defined client or user requirements
      - test results
        
        tests are carried out both during the creation and when its completed
        
        the results will be recorded to make sure that the product works as intended
  - - - test results
      - deliverable product
    - - release of deliverable prodyct
        
        prodyct is fully checked against the constraints list and defined requirements
        
        product is installed on the clients computer system and checked again to make sure that it is working as intended
        when the projec team is happy, the product is released to the cliient
      - user documentation
        
        created before the product is released to the client
        
        type of user documentation will depend on the type of product
        
        eg
        
        guide showing user how to use the product or an installation guide which can be used in teh future if the product needs to be reinstalled
  - - - consider the feasability report
      - decide if the project is to carry on
      - if omissions in information are found, teh stage is repeated
    - - consider the project plan, test plan and the constraints list
      - check tehres no omissions in the documents
      - project pkan test pkan and constraints listchecked and agreed by the client
    - - consider the completed product
      - review the product against the test results, user requirements and constraints list
      - resolve issues and omissions
    - - consider all aspects of the project
      - measure against success criteria and objectives
      - review deviations from original plans
      - assess the maintainability of the product including furtehr development of system in the future use of emerging tech and adapting to a changed environemnt
- - - - if its found that theyre not being met then changes must be made to the project
  - - - target audience the colours or donts to be used the hardwarre platform which the product is going to be installed on the software to be ysed inputs and outputs etc
  - - - health and safety act compiter misuse act dpa freedom of informaion act and copyright designs act
    - - logical protection methods
        
        firewalls, encryption access rights username and passwords
      - phyiscal protection methods
        
        locking rooms that computer equipment is located in
        
        bolting computers to desks and using device locks and clowin blinds at windows
    - - steps taken to reduce the impacy of setbacks or problems
        
        eg
        
        regular meetings iwth team to identify problems
        
        building in contingency time to project plans
    - - the importance of and purpose of setting objectives
        
        objectives are set by the project manager and the client
        
        they are the baseis on which the product is baseed
        
        teh final deliverable prodyct is measured againsg these
        
        reviewed during phase reviews to ensure theyre being met
        
        if correct objectives are set
        
        the product will fully meet the client defined requirements
        
        nothing will be left out, so the product can be used as soon as its ready
        
        product will be delivered in agreed tiemscale
        
        setting objectives focuses attention and action
- - - - how the phases link to eachother
    - - the reoeating of a phase - each repitition of a phase where ammendments are made is cakked an iteratuin, the results of each iteration are used as the starting point for the next