Cambridge Technical Introductory Diploma in IT

(Unit 6 - LO3)

Be able to generate designs for application solutions

 

Part - - -

Why is it important that a product is being developed following rules, guidelines or the phases of an application development model? Discuss why there should be a structure and rules for a developer to follow when producing a product.

3.1 The use of diagrams to represent aspects of the design of an application

Task 3: Prepare and present designs

(This task should take between 3 and 4.5 hours)

Learning Outcome 1 (part): Understand how applications are designed, is assessed in this task.

Learning Outcome 3: Be able to generate designs for application solutions, is assessed in this task.

Learning Outcome 4: Be able to present application solutions to meet client and user requirements, is assessed in this task.

Your task is to:

  • Describe the design stage of an application development for the application model you have been given or chosen. Provide a series of annotated diagrams that illustrate and describe your proposed application design. These should include diagrams to show the scenarios in which the application will be used with functional requirements, process and data handling and user interface designs.
  • As an extension to the annotated diagrams you should justify your design choices, outlining the advantages and disadvantages of each.
  • Present your proposed design solution to the client. The presentation format must be ‘fit for purpose’ and you should have undertaken appropriate quality checks. It should be sufficiently detailed to enable the client to understand the key features of your proposed solution.
  • Following the meeting, discussion or communication with the client, you should identify clearly the adaptations that the client wanted and what was agreed, with clear statements of the refinements to the solution design and the possible implications. You should make changes to their designs following the client review and negotiations. The changes should be clearly documented.

Annotated diagrams – P3

  • This must provide a series of annotated diagrams that describe the proposed application
    solution. These should include diagrams to show the scenarios in which the application will be used with functional requirements, process and data handling and user interface designs.

Extension to diagrams – D1

  • This should justify your design choices, outlining the advantages and disadvantages of each.

Presentation of proposed design – P4

  • You must present your proposed design solution to the client. The presentation format must be ‘fit for purpose’ and you should have undertaken appropriate quality checks. It should be sufficiently detailed to enable the client to understand the key features of your proposed solution.

Negotiation with client and adapted design solution – M3

  • You should provide evidence of your meeting, discussion, or communication with the client. You should identify clearly the adaptations that the client wanted and what was agreed. You should make changes to your design solution following the client review and negotiations. The changes should be clearly documented, considering any implications.

LO3 Assessment activities

Describe the design stage of an application development for the application model you have been given or chosen.

Provide a series of annotated diagrams that illustrate and describe your proposed application design. These should include diagrams to show the scenarios in which the application will be used with functional requirements, process and data handling and user interface designs.

As an extension to the annotated diagrams you should justify your design choices, outlining the advantages and disadvantages of each.

Present your proposed design solution to the client. The presentation format must be ‘fit for purpose’ and you should have undertaken appropriate quality checks. It should be sufficiently detailed to enable the client to understand the key features of your proposed solution. [You have done this as part of a group]

Following the meeting, discussion or communication with the client, you should identify clearly the adaptations that the client wanted and what was agreed, with clear statements of the refinements to the solution design and the possible implications. You should make changes to their designs following the client review and negotiations. The changes should be clearly documented. [You have done this individually as a recorded meeting with the client - Mr Campling - and now need to write it up in a suitable style. The purpose is to justify your choices, give a suitable reason or resons for each dicision that you have made.]

Report or Presentation – P1
This should be produced for the trainee application designers, describing the design stage in application development for the model you have been given or chosen.

Annotated diagrams – P3
This must provide a series of annotated diagrams that describe the proposed application
solution. These should include diagrams to show the scenarios in which the application will be used with functional requirements, process and data handling and user interface designs.

Extension to diagrams – D1
This should justify your design choices, outlining the advantages and disadvantages of each.

Presentation of proposed design – P4
You must present your proposed design solution to the client. The presentation format must be ‘fit for purpose’ and you should have undertaken appropriate quality checks. It should be sufficiently detailed to enable the client to understand the key features of your proposed solution.

Negotiation with client and adapted design solution – M3
You should provide evidence of your meeting, discussion, or communication with the client. You should identify clearly the adaptations that the client wanted and what was agreed. You should make changes to your design solution following the client review and negotiations. The changes should be clearly documented, considering any implications.

  • Issues to consider.
  • 3.1 The use of diagrams to represent aspects of the design of an application, i.e.:
    • functional requirements (e.g. use case diagrams)
    • processing and data handling (e.g. flowcharts, data flow diagrams, class diagrams, object diagrams, entity relationship diagrams)
    • user interface designs (e.g. wireframe diagrams and graphical mock-ups)
  • 3.2 Standardisation of design, e.g.:
    • standard algorithms or processes
    • modularisation
    • cross-platform standards
    • standard protocols
    • standard interface widgets (appearance of buttons, dropdown menus, hyperlinks)
    • common user interface layouts, icons and labels throughout application
    3.3 Advantages of proposed solution, e.g.:
    • automation
    • operational efficiency
    • cost-effectiveness
    • globalisation
    • improved communication
    • customisation and adaptability
    • increased markets
    • ease of access for customers
    • new marketing opportunities
    • customer or user information
    • real-time information
    • new employment
  • 3.4 Disadvantages of proposed solution, e.g.:
    • financial cost
    • changeover costs and risks
    • training needs
    • lack of job security and job losses
    • security issues
    • privacy issues
    • potential customer concerns
    • loss of personal contact