Unit 6 Application Design Practice Assignment

Practice Assignment 3 Part A – Training Part B – Designing the application Part C – Client brief

Part C - Brief The client is Mrs Kay and Mr Reid who wants to meet the needs of year 7 pupils who find it difficult to find their way around school. They want something that could help pupils get around school and finding the correct rooms for their lessons. The client wants and application to help users to be able to navigate from one room to another in the school.

Part B – Designing the application You will be required to: gather and document the client’s requirements; identify possible solutions and produce a feasibility study for the client; prepare their designs and present them to the client; negotiate and document any adaptations agreed with the client; develop a prototype; test the prototype and gather feedback from the client/user; analyse the feedback and implement any changes required.

gather and document the client’s requirements; client and user interviews e.g. closed and open questions leading questions observation of tasks analysis of existing documents and systems

gather and document the client’s requirements; what the application should do – brief & investigation data and information collected and used in the existing approach data and information to be collected and used in the new application functions or processing that the application should perform outputs from the application Input Process Output

gather and document the client’s requirements; A requirement for a computer system specifies what you want or desire from a system. Functional requirements - are what you want a system to do – NOT how Non-functional requirements - are restrictions on the types of solutions that will meet the functional requirements. Performance Constraints e.g. The system should be able to hold 1500 student timetables, The system must be able to download & store a max of 5 timetables Development Constraints Time to develop - deadlines Resource - finance & time Design Objective – rank important features by priority http://www.coleyconsulting.co.uk/require.htm

Part B – Designing the application You will be required to: gather and document the client’s requirements; identify possible solutions and produce a feasibility study for the client; prepare their designs and present them to the client; negotiate and document any adaptations agreed with the client; develop a prototype; test the prototype and gather feedback from the client/user; analyse the feedback and implement any changes required.

Technical Feasibility: Will it perform requirements? identify possible solutions and produce a feasibility study for the client; Technical Feasibility: Will it perform requirements? Social Feasibility: Acceptable to people? Economic Feasibility: Cost vs. benefits Legal Issues: Evaluate against legislations e.g. DPA Operational Impact: Functions affect by product Scheduling: Timings to produce Feasibility Study The feasibility study determines if it is possible(or viable) to develop a product. This is conducted after the investigation as the requirements, constraints and limitations are now known and the developer can decide if they are able to produce the project.

identify possible solutions and produce a feasibility study for the client; Technical Feasibility: Will it perform requirements? Social Feasibility: Acceptable to people? Economic Feasibility: Cost vs. benefits Legal Issues: Evaluate against legislations e.g. DPA Operational Impact: Functions affect by product Scheduling: Timings to produce

Part B – Designing the application You will be required to: gather and document the client’s requirements; identify possible solutions and produce a feasibility study for the client; prepare their designs and present them to the client; negotiate and document any adaptations agreed with the client; develop a prototype; test the prototype and gather feedback from the client/user; analyse the feedback and implement any changes required.

prepare their designs and present them to the client; Use diagrams to represent aspects of design These will show what the system will look like, how it will work and who is involved with the application. Functional requirements: identifies all the people involved in the app with interactions Processing and data handling: flowcharts, dataflow diagram, entity relationship diagrams User interface designs: wireframe diagram, graphical mock-up