ICT
 
home search Contact
Lmarsden is a non-profit information site

Week 15: Data-driven problems, programming and solutions

Class Task and Information

  • Lesson 01:
      • Unit 3 - IA1 Exploration


      • Understand the application of performance standards to evidence presented


    • FIA3: Folio
      • Well done on the submission of your FIA3. This was a big and time consuming project that required you to bring all the learning you have done over the last 2 years into one project.
      • The size and complexities of this assignment varies with your programming skills and understanding.
      • Do not stop your programming now!!! it is time to build upon your success and keep your brain cells working and applying all the hard work your have been doing.
      • My suggestion to keep yourself active as a programmer is to set yourself a programming task each week. If you would like something for the next couple of weeks, learn bootstrap.
      • Bootstrap 5 Crash Course | Website Build & Deploy


    • Today’s task - Setting the benchmark and understanding performance standards
    • Class discussion on their findings using Cold Calling - no phone a friend - no interruptions.


    • Writing a letter to yourself
      • You will be given a piece of paper and an envelope
      • Address the envelope to yourself
      • Write a message and a reminder to future you! This will be given to you when you start IA1.
      • Remember starting the course strong will ensure you finish strong.




      • Website Landing Page



      • Hamburger Menu (not responsive from collapse)



      • What advantage does the App have over the Web site
        • applying systems thinking that identifies
          • - system boundaries
          • - properties of elements
          • - inputs and outputs
          • - user interface
          • - system controls
      • Create a table with the following 2 categories and 4 columns:
      • Web Site Application
        Advantage Disadvantage Advantage Disadvantage
               
               



  • Lesson 02:
      • system boundaries
      • User Interface Requirements


        • Students are to return envelopes - Future you will appreciate the advice and reminder
        • Students need to complete the table about What advantage does the App have over the Web site?



    • applying systems thinking that identifies
      • - system boundaries
        • The scope defines the boundaries of the system (or problem) that is being addressed.
        • A scope includes:
          • Problem statement: The problem statement is an overall descriptive statement about what needs to be solved. It includes a justification for the project (explains why is it being undertaken in the first place).
          • Objective: These are the overall project goals that will meet the needs of your customers. They is in described in terms of the product or service that will exist at the end of the project. The developer needs to understand the objectives because it gives a basis for any decision making in the future. It also allows the developer to evaluate the most recent status of the project against the original objectives which had already been set.
          • Deliverables: The deliverables are the objects are that need to be produced. It may also describe the key features and what client needs are being met though them.
          • Constraints and Limitations: What are the barriers or things that must be adhered to. These are the requirement specifications for the project. These are summarized and typically involve a technical description. The requirements also have descriptions which are functional so that the project participants can implement them. These might include such things as the platforms the projects is being developed for and the programming languages involved.
          • Time line: How long the project will run for and any specific milestones or checkpoints along the way.



      • - properties of elements
        • covering needs for specific fonts, text sizes etc
        • Position and scale, animation and trigger effects

      • - inputs and outputs
        • How the user enters information. This can be done though keyboards, virtual keyboards, voice narration, gesture. Tapping, shaking, sliding, toggling etc

      • - user interface
        • What the user can see and interact with. depending on the device and its IoT options, this will vary from device to device. Some UI result in visual outputs and inputs, audible outputs and inputs, haptic outputs and inputs.

      • - system controls
        • Events and processing that drive outcomes that is encompassing of all elements.
        • Science of control, defines two basic control mechanisms:
          • Negative feedback, maintaining system state against set objectives or levels.
          • Positive feedback, forced growth or contraction to new levels.




    • User Interface Requirements
      • User interface requirements can be sorted into three categories:
        • 1. Operational Details – Things that apply to the user interface as a whole. For example, who needs it, when and where it is needed.

        • 2. Component details – Things that apply to a portion of the thing based on a meaningful grouping of fields or list of records. For example, areas specific selection criteria, sorting criteria, pagination rules.

        • 3. Individual Element Details – Things that apply to a data item being presented – either its source or its derivation. Each textual label of a field, column or area. For UIs involving input fields – validation criteria and any business rules. For each UI action item (e.g. a button), a description of the action to be carried out.



    • Technical Issues that can influence the User Interface requirements
      • Hardware issues that can influence the user interface include, but are not limited to:
        • The physical size of the interface the user sees (the screen size)
        • The colours that can be displayed by the device
        • The physical means of input and output available to the system (Human computer interactions)
        • The amount of bandwidth that is available to a user

       

      • Software issues can also be influential. These can include:
        • What language or software is being used to develop the system and what capabilities does it have
        • What operating systems are users using
        • Is any additional software required


    • Website Landing Page
      • Students are to take the A3 Landing page of Uber East. This Landing page is concidered the second time you have accessed the site (cookies and server information remember you!!!)


      • Task01: Annotate the page layout
        • Start by Identify Divisions and areas that you believe the website is using.
        • Look at the nesting of the page and the element areas.
        • Add the HTML5 Semantic tags that are ovious

        • Uber Eats Order Page



  • Lesson 03:
      • Recognise and compare different file formats and data structures appropriate to the context
      • Analyse how data sources could be combined
      • Explore the impacts of missing data, different join conditions, data duplication and inconsistency
      • Develop a data flow diagram showing how data sources can be combined to create a solution dataset

      • Note in this section you are looking at:
        • data, programming and user-interface relationships
        • data sources
        • programming features communicated by algorithms
        • data structures
        • programming features
        • potential algorithmic implementations
        • programming requirements
        • required data
        • data structures of the proposed solution



      • User Interface Requirements and Designs
      • Data requirements and programming structures


    • Task 01: Identify the Input, Output and Event Triggers / Call to Actions
      • Using another copy of the document, annotate the appropriate information
      • Use a set colour for each of the elements: Input, Output, Call To Action.

        Uber Eats Order Page


    • Task 02: Identify the different Elements of data used
      • Make a list of all the different types of data and fields used to construct and make this dynamic web page. Pro-Tip: Make a Data Dictionary for the page (it will not be normalisd)

        Uber Eats Order Page



      Task 03:Write out the Functional and non-functional requirements of the Uber Eats Web Site.



    • Functional requirements: Functional requirements define the specific behaviours, responses, information, rules, or operations of a solution. They outline
      • What functions or functionality the solution will support
      • What specific users will do or experience while being a part of or using the solution
      • What information or data will be managed
      • Under what circumstances the behaviours and responses happen (or not) in order to ensure the required results and outcome

    • Non-functional requirements specify the manner or the environment in which a solution is intended to operate. They define standards for
      • Usability: How easy the solution must be to understand or figure out
      • Reliability: To what extent users can rely on the solution to be accessible and work when needed
      • Performance: How quickly and efficiently the solution works and how it responds to commands and requests for action
      • Security: The level of protection the system and its data are expected to have in place
      • Design: The visual elements expected from the solution
      • Accessibility: The support that must be provided for users with disabilities, including hearing or vision loss, typically in compliance with relevant regulations.
      • Documentation: The type and extent of written documentation expected or needed
      • Information capacity: Requirements for the amount of data or media to be stored, including the expected growth of the information over time
      • Information architecture: Any needs for the arrangement or organization of the information in the solution
      • Anything else: Whatever else the stakeholders decide is required of the solution





  • Lesson 04:
      • evaluate the improved user interfaces and heuristic reviews against
        • useability principles including accessibility, effectiveness, safety, utility and learnability
        • elements and principles of visual communication.


      • Students are to scaffold and write in dot points their evaluation of Uber Eats


    • Task - Scaffold solution to:
      • evaluate the user interfaces and heuristic reviews of Uber Eats Web Site against
        • useability principles including accessibility, effectiveness, safety, utility and learnability
        • elements and principles of visual communication.


Readings / Homework
  • Submit all work into myFlinders as evidence of your learning.

 

 

 

 

Focus Point

 

 

Information