Great Deal! Get Instant $10 FREE in Account on First Order + 10% Cashback on Every Order Order Now

This is the third part of the assignment. You did the first two parts. Our topic is Face Detection Using Python. The teacher gave an example for the homework.

1 answer below »



Purpose


To experience developing an organized system from scratch. To experience working with a group to develop a full organizing system including the use of taxonomies and/or controlled vocabularies as well as encoding of metadata.


Description


You will need to work with a group for this project. Please identify two to three individuals with whom you can work on this project. You will need to share your collaborative document with me.


Develop an organizing system to organize material on a website for a resource collection of your choice. Here are a few resource schemas you may consider using:



  1. Recipe [https://schema.org/RecipeLinks to an external site.

    ]

  2. Music Recording [https://schema.org/MusicRecordingLinks to an external site.

    ]

  3. Drug [https://schema.org/DrugLinks to an external site.

    ]

  4. Video Game [https://schema.org/VideoGameLinks to an external site.

    ]

  5. Vehicle [https://schema.org/VehicleLinks to an external site.

    ]

  6. Dublin Core (General Purpose) [https://www.dublincore.org/specifications/dublin-core/dcmi-terms/Links to an external site.

    ]


Alternatively, you may choose your own topic and use the Dublin Core Schema and Omeka to set up your organized system. Your organizing system should include the selection of appropriate elements from the schema, the development of a basic taxonomy, and the selection or development of appropriate controlled vocabularies for names of persons and organizations (even when not specifically required in the schema), as well as appropriate controlled vocabulary formatting, for dates, languages and identifiers where required or recommended by the schema.


Your completed project should include:



  • a front page listing the members of the group

  • a discussion of the design decisions you must make for this system to be efficient and effective.


You will develop a demo to show how your system would work in practice. While your demonstration does not need to be a fully working website or model, you should include a working faceted taxonomy and metadata encodings corresponding to at least three (3) of your created metadata records. You may use paper mockups or slides to demonstrate how the system would work.


You may use an existing digital library tool such as Omeka, code a demo yourself in HTML, use a website builder, or create a slide presentation/video showing how your system would work.


Your project must include the following:


1) a page discussing design decisions [This should include answering the questions posed herehttps://berkeley.pressbooks.pub/tdo4p/chapter/design-decisions-in-organizing-systems-introduction/Links to an external site.

]


2) a minimum of 10 metadata records for your selected resources formatted according to the example shown in the table below (your metadata record should use a minimum of 8 elements/properties) [skill learned in Assignment 3]:







































































Metadata Element

Value

Content/Vocabulary Standard for Formatting


dc.title



The Discipline of Organizing: 4thProfessional Edition






dc.creator



Glushko, Robert J.



LCNAF




dc.subject



Information organization.



LCSH




dc.description



This textbook takes a multi-disciplinary approach to the field of information organization.






dc.publisher



Glushko, Robert J.






dc.contributor








dc.date



XXXXXXXXXX



W3CDTF




dc.type



Text



DCMI-Type




dc.format



application/pdf



IMT




dc.identifier



XXXXXXXXXX






dc.source



https://berkeley.pressbooks.pub/tdo4p/






dc.language



en



ISO 639-2




NB. Since you will be using schema.org your property/element names will not be the same as shown in the table, since that uses Dublin Core


3) validated metadata encoding in rdf/xml or json for three (3) of your metadata records [See Week 11 Module]


4) the identification and use of established controlled vocabularies for names of persons and organizations (Seehttps://en.wikipedia.org/wiki/Authority_controlLinks to an external site.

) and for all elements where a content standard is recommended or required for a property by the schema eg. language, date. [See Week 5 module]


5) the set of interactions you will enable on your site (these can be built into the system or you can demonstrate how you would like it to work) [Seehttps://berkeley.pressbooks.pub/tdo4p/chapter/designing-resource-based-interactions/Links to an external site.

],


5) a hierarchical taxonomy that will support organization of your resources and at least three facets to enable filtering of the search results. [skill learned in Assignment 4 and Week 10 module]


6) demo/overview of how your website would look with enabled taxonomy and results displayed


NOTE:


It is recommended that you work with at least one other person on this project. Because it is very important to experience issues involving lack of consensus for taxonomy or controlled vocabulary development during this project. A student who would prefer to work alone must reach out to me for agreement first and must also write an additional short paper which will compare their system to a similar system for a similar experience.



Submission Components:



  1. Submit a single pdf document or presentation which combines these elements of your organized system. You may present the document as slides (with or without voice) as you desire.Do not use Prezi or any similar tool.


    1. one page discussing design decisions


    2. 10 metadata records


    3. 3 validated encoded metadata records (rdf/xml, json)


    4. mock ups of interactions showing how they are enabled


    5. full faceted taxonomy that organizes resources and supports search and browse


    6. demo/overview of how your website would look with enabled taxonomy and results displayed


    7. final page providing summary of the work done, decisions made, challenges, disagreements and resolutions, and any final thoughts. (Include a link to your collaborative document on this final page, be sure permissions are set appropriately for me to view this document)




  2. Students who are working alone should add an additional document, 400 words, comparing their system to an existing system on a similar topic/with a similar function. If you work in a group, you will have the chance to discuss issues of compromise and consensus that a solo project will miss. Comparing your system to an existing system will still allow you to experience and discuss some of these issues.


Group Sign Up


Group membership is a self enroll, you will not be randomly assigned. Do the following:



  • Please identify the Final Project Group Sets and self-sign up with one of the available groups. Instructions for self-sign up may be foundat this linkLinks to an external site.

    . (If you choose to work alone, please contact me for permission and so that I might set up Canvas to accept your work.)

  • Create a collaborative document (Microsoft Word or Google Docs) in which you will all be working and share that file with me.

  • Please use one page of the collaborative document to outline tasks and how you will be dividing those tasks between group members.

  • Please add a notation if a group member fails to complete their assigned and agreed on tasks.







Rubric





Final Project Rubric




























































Final Project Rubric

Criteria Ratings Pts




This criterion is linked to a Learning Outcome

Discussion of Design Decisions
Project has one page with a discussion of design decisions.


















2pts

Full Marks

Design decisions include all the organizing questions along with appropriate answers and considerations for each.








1pts

Partial Marks

Some elements of design decisions were not discussed or more thorough discussion is needed in elements mentioned.








0pts

No Marks

No discussion of design decisions present or discussion is lacking to the point where meaningful assessment is impossible.






2pts






This criterion is linked to a Learning Outcome

Metadata Records
Project includes the required amount of metadata records


















3
to >2.0
pts

Full Marks

10 or more metadata records provided








2
to >0.0
pts

Partial Marks

Less than 10 metadata records provided.








0pts

No Marks

No sample records provided.






3pts






This criterion is linked to a Learning Outcome

Schema
Appropriate schema applied to records


















2pts

Full Marks

Excellent use of chosen metadata schema.








1pts

Partial Marks

Some issues with your schema (not a schema, schema not well described, schema not well implemented)








0pts

No Marks

No schema used.






2pts






This criterion is linked to a Learning Outcome

Controlled Vocabulary
Excellent selection and use of controlled vocabulary for value and formatting of schema properties.


















2pts

Full Marks

Excellent description of controlled vocabulary and correct application to properties shown across the organizing system.








1pts

Partial Marks

Reasonable description of selection and use of vocabularies however some properties that should have used a controlled vocabulary do not or formatting rules for the content standard are ignored or not applied correctly.








0pts

No Marks

No controlled vocabulary used or no explanation of why it was chosen or how applied.






2pts






This criterion is linked to a Learning Outcome

Encoded Records
Project includes the required amount of metadata records


















3
to >2.0
pts

Full Marks

3 or more encoded metadata records in json or xml








2
to >0.0
pts

Partial Marks

Less than 3 encoded records or serious problems noted - such as invalid xml or json








0pts

No Marks

No encoded metadata records submitted.






3pts






This criterion is linked to a Learning Outcome

Taxonomy
Taxonomy Design and Diagram


















3
to >2.0
pts

Full Marks

Full faceted taxonomy that organizes resources and supports search and browse, excellent taxonomy diagram and identification of taxonomy levels, categories and facets.








2
to >0.0
pts

Partial Marks

Good start. However, your taxonomy diagram needed more layers/ no facets mentioned which would help to refine search supported by the taxonomy/ diagram is confusing and hard to follow








0pts

No Marks

No taxonomy presented.






3pts






This criterion is linked to a Learning Outcome

Demo System with Interactions
Demo/Wireframe demonstrating interactions.


















4
to >3.0
pts

Full Marks

Excellent Demo. Demo is interactive or clearly provides sufficient evidence through screenshots/images to indicate how interactions would take place. [Example: search, sort, filter, rate, comment, popular, etc]








3
to >0.0
pts

Partial Marks

Good demo. Demo provides a good description of how the system would work but could be enhanced with additional screenshots or explanations.








0pts

No Marks

No demo/wireframe provided.






4pts






This criterion is linked to a Learning Outcome

Final Summary Report Page
Report describing the system (including this page and first page, as well as others in document should be 800 words).
If you worked alone, there should be an individual 400 page report comparing your system to another system.


















5
to >3.0
pts

Full Marks

Excellent report which describes the process of designing your system and implementing the demo system.








3
to >0.0
pts

Partial Marks

Good report which describes the process of designing your system, however more detail would be invaluable.








0pts

No Marks

Report Missing






5pts






This criterion is linked to a Learning Outcome

Formatting
Appropriate style used (APA, MLA). Name of authors listed and references included. Grammar and Spelling appropriate.


















1pts

Full Marks

Format follows standard style guidelines, author names and references supplied. Correct grammar and spelling used. Excellent writing and communication of concepts.








0.5pts

Partial Marks

Some issues with style, grammar, or spelling.








0pts

No Marks

Answer is hard to understand due to writing style. The Writing Center (http://www4.uwm.edu/writingcenter/) can provide assistance with writing.






1pts



Answered 13 days After Apr 04, 2024

Solution

Shubham answered on Apr 08 2024
13 Votes
CST8333 Programming Language Research Project – Assignment 3
CST8333
Assignment 3
Student’s Name
Date
Algonquin College
All material prepared for this assignment was produced by the author. Material from all third parties has been cited and referenced.
Table of Contents
Purpose    5
Timeline    5
Status    5
Requirements    5
Traceability Matrix    5
Conceptual Design    5
References    5
Purpose
Face detection in Python is used to identify and locate human faces in images. This has diverse applications that includes security systems, facial recognition and augmented reality [3]. It includes use of computer vision techniques. Python enables development of accurate and efficient face detection algorithms for various real-world applications.
The timeline is visual representation of chronological events for displaying order in which they occu
ed over period. It provides concise overview of historical and project-related developments [3].
Status
Requirements
The face detection project in Python will include functional requirements like accurate face identification, real-time processing and integration with image. Non-functional requirements ensure performance, scalability and user interface responsiveness [1]. This ensures reliable and user-friendly experience for various applications like security systems or facial recognition technology.
Traceability Matrix
Use the traceability matrix to track requirements fulfillment and testing results.
    Requ't Numbe
    Requ't Name
    Category
    Test Criteria
    Expected Result
    Result
    Pass/Fail
    Notes
    TECHNOLOGY REQUIREMENT-001
    Face Detection
    Functionality
    Detect faces in images/video with 90% accuracy
    Faces accurately detected
    Faces detected with X% accuracy (replace X with actual value)
    Check accuracy
    Consider environmental factors, occlusion, lighting
    TECHNOLOGY REQUIREMENT-002
    Face Detection
    Speed
    Detect faces in real-time at 30fps on average hardware
    Achieves 30fps average detection speed
    Achieves Yfps average detection speed (replace Y with actual value)
    Optimize for performance
    Address computational bottlenecks, adjust parameters
    TECHNOLOGY REQUIREMENT-003
    Face Recognition
    Functionality
    Recognize known faces with 80% accuracy
    Co
ectly identifies known faces
    Identifies known faces with Z% accuracy (replace Z with actual value)
    Check accuracy
    Evaluate with different datasets, consider pose variations
    TECHNOLOGY REQUIREMENT-004
    Face Recognition
    Speed
    Recognize faces in real-time at 20fps on average hardware
    Achieves 20fps average recognition speed
    Achieves Wfps average recognition speed (replace W with actual value)
    Optimize for speed
    Explore trade-offs between accuracy and speed
    TECHNOLOGY REQUIREMENT-005
    Facial Feature Extraction
    Functionality
    Extract key facial features (eyes, nose, mouth) with 95% accuracy
    Features accurately extracted
    Features extracted with V% accuracy (replace V with actual value)
    Check accuracy
    Assess robustness to noise, variations
    TECHNOLOGY REQUIREMENT-006
    Facial Feature Extraction
    Speed
    Extract features in real-time at 40fps on average hardware
    Achieves 40fps average feature extraction speed
    Achieves Ufps average feature extraction speed (replace U with actual value)
    Optimize for speed
    Consider feature importance, reduce dimensionality
    BUSINESS REQUIREMENT-001
    User Interface
    Usability
    Intuitive and user-friendly interface for interacting with the system
    Users can easily operate the system
    Users encounter some difficulty with X (indicate specific usability issues)
    Improve usability
    Address UI flaws, refine user interactions
    BUSINESS REQUIREMENT-002
    User Interface
    Responsiveness
    System responds promptly to user interactions
    Interface reacts immediately to user input
    Interface has slight lag with Y actions (indicate specific actions)
    Optimize responsiveness
    Reduce processing loads, improve efficiency
    USER REQUIREMENT-001
    Unit Tests
    Coverage
    Unit tests cover all core functionalities
    All critical functionalities have tests
    Some functionalities lack tests for Z scenarios (indicate specific scenarios)
    Expand test coverage
    Create tests for uncovered scenarios, ensure completeness
    USER REQUIREMENT-002
    Integration Tests
    Integration
    Modules interact seamlessly and produce co
ect results
    System functions integratedly without issues
    Issues arise when integrating X and Y modules (indicate specific modules)
    Debug integration issues
    Identify and resolve communication problems between modules
    NON-FUNCTIONAL REQUIREMENT-001
    Non-Functional Requirements
    Security
    System protects user privacy and data integrity
    Data is secure and user privacy is respected
    Potential vulnerability identified in X area (indicate specific area)
    Address security concerns
    Implement encryption, authentication,...
SOLUTION.PDF

Answer To This Question Is Available To Download

Related Questions & Answers

More Questions »

Looking For Homework Help? Get Help From Best Experts!

Copy and Paste Your Assignment Here