IA2- Technical Proposal

Get Started. It's Free
or sign up with your email address
IA2- Technical Proposal by Mind Map: IA2- Technical Proposal

1. User Problem

1.1. Mr Grey

1.1.1. Relief Coordinator Role

1.1.1.1. Requirements

1.1.1.1.1. Manage & Contact Relief Teachers

1.1.1.1.2. Full Access to the New Web Application

1.1.1.1.3. Check Teacher's Relief Work is Entered

1.1.1.1.4. Allocate & Enter Relief Teachers to Relief Work

1.1.1.1.5. Facility to Print Hard Copies of the Relief Work for his Records

1.1.1.1.6. Run Database Queries to aid System Management

1.1.2. 20 years of teaching experience

1.2. Ms Scarlet

1.2.1. Biology Teacher

1.2.2. Requirements

1.2.2.1. Enter her relief work when absent

1.2.2.2. Add, Update and View relief work

1.2.2.3. Alerted in Advance when cover work has been allocated

1.2.2.4. See clearly any relief work she needs to cover

1.2.3. 2 Years of teaching experience

1.3. Mr Green

1.3.1. Senior Humanities Teacher

1.3.2. Requirements

1.3.2.1. Access to new system

1.3.2.2. Not listed as a supply teacher on .CSV file

1.3.2.3. Guidance on using the system

1.4. Ms Beige

1.4.1. Degree in Data Science

1.4.2. Leading Data Administrator

1.4.2.1. Requirements

1.4.2.1.1. Facility to add and deactivate teachers from system

1.4.2.1.2. Generate and run ad-hoc queries

1.4.2.1.3. Full access to web application and database

2. Criteria

2.1. Prescribed Criteria

2.1.1. Communicating

2.1.1.1. Make Decisions & Fluent Use of

2.1.1.1.1. Written & visual features to communicate about a solution

2.1.1.1.2. Language for a technical audience

2.1.1.1.3. Grammatically Accurate language structures

2.1.1.1.4. Referencing & project conventions

2.1.2. Analysing

2.1.2.1. Analyse

2.1.2.1.1. Low-fidelity Prototype

2.1.2.1.2. Problem & Information related to technical proposal

2.1.2.1.3. Personal, Social and Economic Impacts

2.1.2.2. Determine

2.1.2.2.1. User Interface

2.1.2.2.2. Data

2.1.2.2.3. Programmed & Solution Requirements

2.1.3. Retrieving & Comprehending

2.1.3.1. Recognise & Describe

2.1.3.1.1. Programming Elements

2.1.3.1.2. User Interface Components

2.1.3.1.3. Useability Principles

2.1.3.2. Symbolise & Explain

2.1.3.2.1. Programming Information & Ideas

2.1.3.2.2. Data Structures

2.1.3.2.3. Interrelationships between user experience & data of the digital protoype

2.1.4. Synthesising & Evaluating

2.1.4.1. Coherent & Logical Synthesis of

2.1.4.1.1. Relevant Information

2.1.4.1.2. Ideas to Determine

2.1.4.2. Purposeful

2.1.4.2.1. Efficient User Interface

2.1.4.2.2. Programmed Components

2.2. Self-Determined Criteria

2.2.1. Accurate Code

2.2.2. A working low-fidelity program

2.2.3. Ensuring all information is relevant & insightful

3. Developer Problem

3.1. User Interface

3.1.1. Useability Principles

3.1.1.1. Accessibility

3.1.1.2. Effectiveness

3.1.1.3. Safety

3.1.1.4. Utility

3.1.1.5. Learnability

3.1.2. Login Screen for Users

3.1.3. SMS & Email Capability

3.1.3.1. For the registered teachers who have relief

3.1.4. Registration Screen

3.1.4.1. Only appropriate administrators can have access

3.2. Coding Environment

3.2.1. HTML for web application

3.2.2. Python Language

3.2.3. CSS for style

3.2.4. SQL for queries

3.2.5. Code for SMS and email

3.3. Data Environment

3.3.1. 1 Database

3.3.1.1. 2 Tables

3.3.1.1.1. One with the relief work

3.3.1.1.2. One with all the teachers

3.3.2. Protection of personal information

3.3.2.1. Encryption

3.3.2.2. Data

3.3.2.2.1. Full name

3.3.2.2.2. Mobile Number

3.3.2.2.3. Email Address

4. Client Problem