770 skills found · Page 15 of 26
cashapp / TrifleSecurity functionality for interoperability/interaction with core services.
iaindooley / TrellinatorTrellinator core functionality and queue management
UncreatedStaff / UncreatedWarfareCore gameplay functionality of Uncreated Warfare Server for Unturned.
musket-ml / Musket CoreCore Functionality of DL Pipelines
mndrix / Atom Emacs Core KeysEmacs key bindings for only core Atom functionality
amanat-2003 / Whatsapp CloneThis WhatsApp clone Flutter project aims to replicate core functionalities of WhatsApp, including chat, group creation, status updates, and contact selection.
mohsengham / MiniloadMySQL Turbo Mode for WooCommerce - Optimize your store with pure MySQL performance, intelligent caching, and blazing-fast search without removing core functionality.
daniel149afonso / MinishellMinishell is a small command-line shell written in C that replicates core functionalities of Unix shells like bash.
KOSASIH / DAFE CoreThe DAFE-Core Git repository is a central hub for the Decentralized Autonomous Financial Ecosystem (DAFE) project. It contains essential code and resources for developing and maintaining the core functionalities of the DAFE platform, including smart contracts, governance mechanisms, and integration tools for various financial services.
AbhisumatK / Numeth Numerical Methods LibraryA fully functional Python package implementing core numerical methods for engineering and applied mathematics. Designed for usability and educational clarity.
devansharora18 / Cpu ControllerCPU Controller for Linux is a straightforward GUI application based on PyQt6, enabling users to toggle individual CPU cores on or off in a Linux system to save battery life. This functionality serves purposes such as power management and troubleshooting.
joulefingers3z / Trading SoftThe project is aimed at developing an intelligent bot for automated cryptocurrency trading, leveraging advanced machine learning (ML) algorithms and feature engineering. The project offers the following core functionalities
rickmanalexander / ADODBDataAccessAPIA heavily object oriented solution that wraps the core functionality of the MS ActiveX Data Objects Library. This is a highly modified version of Mathieu Guindon (@retailcoder)'s code from here: https://github.com/rubberduck-vba/examples/tree/master/SecureADODB. This Library addresses many of the commonly missed caveats like accurately monitoring an object's state using bit-wise checks, spinning up async commands, and and providing the ability to await their results or process other items during execution.
mitulmanish / Java AssignmentsYou are required to implement a basic Java program using Java (SE 5.0 or later). This assignment is designed to help you: 1. Practise your knowledge of class design in Java; 2. Practise the implementation of different kinds of OO constructs in Java; 3. Practise the use of polymorphism; 4. Practise error handling in Java; 5. Develop a reasonable sized application in Java. General Implementation Details All input data should be read from the standard input and all output data should be printed to the standard output. Do not use files at all. If the input is formatted incorrectly, that input should be ignored and an appropriate error message should be displayed. Marks will be allocated to your class design. You are required to modularise classes properly---i.e., to use multiple methods as appropriate. No method should be longer than 50 lines. Marks will be allocated to proper documentation and coding layout and style. Your coding style should be consistent with standard coding conventions . Overall Specification You will build out the system from Assignment 1 to manage multiple users purchasing different types of items, including discounts for multiple items. Items to be Purchased The TechStore has been extended to sell Software as well as Books. Like Books, Software can be sold as a (physical) CD or as an online item (i.e., download). As in Assignment 1, a Book can also be sold as a physical copy or as an ebook. You need to keep track of the physical copies of Books and CDs, and whether or not a title is available as an online item. Books have a title and an author; Software items have a title and a publisher. Each item is individually priced---i.e., the price depends on the title and whether it is a physical copy or ebook/software-download. Purchasing Items A User can buy any number of items (books, software, or a mix), adding one item at a time to their Shopping Cart. However, a User can only purchase up to a total of $100, unless they are a Member—if a non-Member User tries to add an item to their Shopping Cart that takes the total over their maximum then this is blocked. A Member has no limit. Items can be added and removed from a Shopping Cart until Checkout. When an Item is added to the Shopping Cart, the system checks that there are enough copies of it available; if an Item is added or removed from the Shopping Cart, the number of copies available must be updated. Checkout clears the Shopping Cart. Users Users can add Items to their Cart, up to their allowed limit (i.e., their Shopping Cart cannot store a total greater than the limit). A User has an id (must be unique) and password (you do NOT need to make these encrypted or secure), as well as a name and email address. A Member is a special kind of user: a Member has no limit on value they can store in their Cart. Once a User has spent a total of 10% more than their limit in total (this obviously must be over multiple Checkouts), then they are offered to become a Member—this offer is made straight after they Checkout with the items that takes them to 10% over their limit. An Administrator is a User that can perform special functions: add to the number of copies of a (physical) Book or Software CD; change the price of an item; print sales statistics: i.e., number of sales (physical and electronic) of each Item; add a new user—the system must checked that the new id is unique. Other Users do not have these options on their menu. A user must keep track of their previous purchases, grouped by Transaction—a Transaction is the set of items purchased at Checkout time. Users can log in and out—they do not need to Checkout before logging out. However, only one user can be logged in at a time—the system must allow something like “change user”. If a User logs back in, their Shopping Cart holds the same contents as before they logged out. Recommended Items and Discounts Each item can store a list of “if you liked this” recommendations. If a User adds an Item to their Shopping Cart, then the system suggests other titles they may like. Only similar types of things are recommended—i.e., when a Book is added, other Books (not Software) are suggested. At the time when a list of Recommended titles is given, the user has the option to add one of the recommended titles to their Shopping Cart. If a user adds the title, then they receive a discount of 15% off that second title (the first one is still full price); the User can add multiple recommended titles for 15% off each of them. If a Member adds the recommended title, then they get 25% discount off all the recommendations added. Note: when a recommended title is added, its recommendations are also shown, and are discounted if purchased at that time. You are NOT required to handle the special case of updating discounts when a User removes recommendations from their Cart. However, there is a Bonus Mark for this. Sample menus The menu for a standard User (i.e., a Shopper) should include the following options: 1. Add item to shopping cart 2. View shopping cart 3. Remove item from shopping cart 4. Checkout 5. List all items 6. Print previous purchases 7. Logout (change user) 0. Quit The menu for an Administrator should include the following options: 1. List all items (this option can include purchase statistics for each title) 2. Add copies to item 3. Change price of item 4. Add new user 5. Logout (change user) 0. Quit * SAMPLE RUNS and TEST DATA will be posted to Blackboard * Program Development When implementing large programs, especially using object-oriented style, it is highly recommended that you build your program incrementally. This assignment proposes a specific incremental implementation process: this is designed to both help you think about building large programs, and to help ensure good progress! You are not strictly required to follow the structure below, but it will help you manage complexity. Part A (2 marks): Extend Assignment 1 Start by extending your Assignment 1 solution (a sample solution will be made available): 1. Rename your main class to TechStore if necessary; 2. Extend your Book class (if necessary) to contain all data and operations it needs for Assignment 2, and appropriate classes for other types of Items to be sold; 3. Define Exceptions to handle problems/errors; in particular, you must handle invalid menu options or inputs. Part B (1 marks): Class Design Define all the classes and any interfaces needed for the described system. In particular, you should try to encapsulate all the appropriate data and operations that a class needs. This may mean some classes refer to each other (e.g., the way Account refers to Customer). At this point, you may just want to think about the data and operations and just write the definitions, not all the code. Part C (3 marks): Main Program Your main program should be in the TechStore class. (Of course, any class can contain a main(); this is useful for testing that class.) The main program will contain a menu that offers all the required options (these can be different for different Users!). The system will allow a User to login by typing their id and password and will check that these match: if it does not then the menu prints an error; if they do match, then the system prints a welcome message with the user’s name and shows them the appropriate menu. The system must keep a list of all its Users: this list must be efficient to look-up by User id. Week 7 Demo (2 marks): You will be required to demonstrate your main program and design (with only bare functionality) by Week 7 at the latest. You must also submit to the associated WebLearn project by the Week 7 lecture. Part D (4 marks): Implement Core Functionality Implement the core functionality of the TechStore system described above, except for the recommendations, members, and discounts. You should be able to implement the rest of the TechStore functionality described above, and run and test your system. Part E (4 marks): Implement Recommendations , Members, Discounts Implement the functionality of providing recommendations, users becoming and being members, and discounts. Other (4 marks) As always, marks will be awarded for coding style, documentation/comments, code layout and clarity, meaningful error and other messages, proper error handling, choice of data structures and other design decisions. You are encouraged to discuss such issues with your tutors and lab assistants, or with the coding mentors. Bonus (2 marks) Note: There will be no hints or help offered on Bonus tasks. 1 bonus mark for early demonstration of Parts A,B,C in Week 6 1 bonus mark for correctly handling removal of recommended books from Cart—e.g., if a Member removes the first item then the 15/25% should be added back to the price of the recommended title, unless there are multiple recommendations linked to that title. Submission Instructions Full assignment submission will be via Weblearn, by 9AM, Tues April 28, 2015. You can submit your assignment as many times as you want before the due date. Each submission will overwrite any previous submissions. 1. You need to submit a class diagram (in pdf, gif or jpeg format). 2. You are required to submit your .java files weekly via Weblearn. Your progress will be taken into consideration if you need an extension. 3. There will be a separate WebLearn submission for Part A,B,C—you must submit to this before the Week 7 lecture to qualify for the 2 marks for Week 7 demo. 4. You must include a README file. This should describe how to run your program, what extra functionality you implemented, any standard functionality you know does not work, and any problems or assumptions. If the tutors have any problem running your program and the README does not help then you will lose marks. 5. For the code submission, you must include only the source files in your submission (do not submit any *.class files!). As always, your code must run on CSIT machines. 6. You must submit a single ZIP file—use zip/WinZIP to zip your files before submitting---do NOT submit rar or zipx files!! 7. If you use packages, it is your responsibility that these unpack properly into the correct folders and that your program compiles correctly.
payMeQuiz / PayMe ProjectpayMe is a technical solution initiated by some concerned Nigerians aimed to catalyze the innate desire in humans to fairly compete in an intellectual learning exercise. payMe is structured to more than engage users to learn but to incentivize users to be compelled to strive to achieve desired results on set targets. That in fact is the excelling value of payMe over competitions. payMe is originally a web2 play-to-earn (P2E) gaming application upgraded to a hybrid platform by the adoption of the platform's native utility token for incentivizing success among the quizzers. Play-to-earn (P2E) games are online games that guarantee rewards with real-world value to players for completing given task in a contest with other players. It comes with different structure and rewarding system. In the blockchain ecosystem, these rewards can be in the form of in-game assets like crypto tokens, virtual land, as well as the game assets (weapons, tools etc.) and other NFTs. The advent of web3 and its decentralized nature made it possible for players to buy, transfer and sell these in-game assets, outside of the games's traditional platform in exchange for real money. payMe is designed to encourage knowledge development using incentivization of success. payMe serve as cognitive behavioral therapy (CBT) to users who are psychogically affected by the disturbing examination malpractice permitted in the system, with the learn to earn functionality that catalyzes users desire to aspire to be the best in a transparent and meritorious form of testing knowledgeability. The transparent, honest, and undisputed fairness in determination of examinations success, aim also to promote hardwork as valuable asset to success as against luck dependency, in a society that eligizes game-of-chance about competency test. The Service payMe is designed for every interested adult netizen. The service is web-based and a communal crowdfunding scheme. The game is a test of knowledge, interactive quizzing in a multi-choice questions type. payMe™ is designed to play on web browsers enabling desktop and mobile applications. payMe is intentionally created with meritorious rewarding functionality to differ from the original pattern of the gaming industry, which is famously circumscribed by randomly selection of winners in a game of chance that is luck dependent. It is technically structured as an anti-gambling game with superlative uniqueness that distinguished it among competing brands. payMe is an ongoing concern product that will continue to meet users demands that aligns with our believes, principles and goals. The Service's Aim and Objectives The service's core aim is to create economic opportunities using ethical functionalities in a democratized software. Other objectives are: to incentivise intellectual competence. to encourage healthy and fair competition in the field of learning. to promote edifying research habits among scholars using the platform. to provide alternative healthy empowerment platform for gamesters suffering from addiction The Economic Benefit There are so many economic benefits to be derived from the payMe™ product brand. payMe guarantees regular, sustainable fiscal empowerment to users. It is a healthy alternative means of rewarding users’ passion in games. payMe is designed with the ability to enhance valuable learning exercises. Engaging in the contest can help in the reduction of common crimes incidental to youths. The Playing System The console adopts the multiple-choice questions type to create an interactive quizzing format. It offers online learning capabilities that cover extensive information on various academic subjects and soccer (FIFA competitions, leagues, and clubs’ activities). The service features an interactive learning interface and an intuitive time-bound quiz contest amongst participants. The service is deliberately created to differ from the original pattern of the gaming industry, which is luck-dependent, to an intellectual development contest. By this, payMe™ is ethical. Though it entails the use of cash to gain access, however, it guarantees much value for the little Token expended on every entry. payMe™ is designed to play on web browsers enabling desktop and mobile applications. It is playable everywhere with internet access on PC, Laptop, mobile phones, and other devices, if supported. Its technicality and structure make it superlatively unique among competing brands. payMe™ is an ongoing-concerned revolutionary software. The Process payMe™ can be subscribed to online. It entails an initial free membership registration and thereafter funding of a personal wallet with the platform’s native utility asset – the payME Pay Token (payME) Contestants automatically qualify to either make use of the premium entry to the quiz contest or use the payment option. Any of the quiz contests is a set of Ten (10) objective intra-changeable questions. Contestants are expected to provide correct answers to the questions within the swiftest timeframe. Each contestant’s result is displayed after the last question is answered on the contestants’ quiz page and thereafter, updated on the general result page. Weekly participation is limitless for contestants entering as regular quizzers but limited to 10 entries for the premium contestants. Only the best result amongst a Quizzer’s several attempts is registered for the contestant despite when it’s played each week. The first ranked 5% of the weekly contestants based on the most correct answers provided within the swiftest timeframe wins. The Playing Schedule Contests start every Monday at 12 am and end Saturday at 11.59 pm. From 12 am to 11.59 pm every Sunday, results are automatically displayed on the Result Page. The Web Portal Interface and Functions The web/mobile app has interactive interfaces and modules that help Quizzers easily glide through their activities. Some of these modules are described below: a. Wallet: A participant is expected to link his personal blockchain wallet after registration and fund it to enable him gain access to games. Only a decentralized crypto wallet is accepted. b. Quiz: This is 10 revolving questions, each having 4 objectives with 1 possible answer. When entering as a regular quizzer, once the play (ACE or COS) quiz button is clicked, $0.50 worth of payME Token will be debited from the quizzer’s wallet and credited to the platform’s wallet. Next, intra-changeable questions from the Question Bank will be appearing in non sequence routine. Quizzers are expected to provide the correct answers to each of the 10 questions as fast as they could and within 18 seconds. Immediately, after answering the 10th question, the quizzer’s result will display automatically on both the quizzing page and the general result dashboard. c. Tutorial Quiz: As the name implies, this is a free gaming zone created to enable holders of payMe token who may not want to engage in the contest, but want to improve their intellect through quizzing on the platform. However, the user must have payMe token worth $50 USD in his/her personal connected wallet to gain free access at anytime. d. Result Dashboard: this is a general result center for all Contestants. It updates automatically after each game is played during the play period, and according to the most correct answers within the swiftest time frame. That means that if a million quizzers scored 100/100, the system will display their result according to the fastest to answer the entire question using nanoseconds (an SI unit of time equal to one billionth of a second) in computing. So, be rest assured that it is impractical and impossible for 2 Quizzers to tally in the result. This makes payMe unique in the way winners are determined – fastest finger first! Updating of the dashboard however is programmed to freeze once it is 12 am every Sunday to determine the winners by publishing the result of the past week until 12 am on Monday when it continues its routine update. Available Rewards PayMe weekly quiz contest will commence by 12:00AM on Mondays and close by 11:59PM on Saturdays. Results are auto displayed on Sundays. the top most 5% of the participants are declared winners weekly and they are incentivized in ranges of: 1. The topmost 20% of the Winners earn 40% of the total revenue allocation to incentivizing pool in an equal share. 2. While the remaining 80% of the Winners earn 60% of the revenue share on an equal distribution rate. Practically, whatever revenue is generated weekly, 50% is automatically remitted to the incentivizing pool wallet and from there, the topmost 5% of the total participants are rewarded in the following ratio: 40% is equally shared to the topmost 20% while 60% is equally shared to the rest 80% of the winners. Winners claim button would automatically turn green by 12am every Sunday and they can claim their prizes themselves from their dashboard. Every Year, each of the 10 most intelligent Quizzers, drawn from the 52 weeks’ cumulative results of all participants in the ACE Quiz contests are rewarded with a Scholarship Award worth $1000 USDT in payME Token. Criteria is participating in every week of play. Cost of Play Cost of Game $0.50 worth of payME Token per game entry or with a single weekly subscription with payMe token worth $5. NB: The rewards are available for each quizzer's claim from Sunday at 12 am (according to the Nigerian calendar and time).
uttkarshparmar50 / LIBRARY MANAGEMENT SYSTEM L I B R A 1-Project Title “Library Management System (L_I_B_R_A)” The “Library Management System” has been developed to override the problems prevailing in the practicing manual system. This software is supported to eliminate and in some cases reduce the hardship faced by this existing system. Moreover this system is designed for the particular need of the institution to carry out operating in a smooth and effective manner. 2-Domain Library management institutional management non-profitable organization. 3-Problem of Statement In our existing system all the transaction of books are done manually, so taking more time for a transaction like borrowing a book or returning a book and also for searching of member and books. Another major disadvantage is that to preparing the list of book borrowed and the available book in the library will take more time, currently it is doing as a day process for verifying all records. So after conducting he feasibility study we decided to make the manual library management system to be computerised. Proposed system is an automated library management system. Through our software user can add member, edit information, borrow and return books in quick time. Some of the problems being faced in faced in manual system are as follows: • Fast report generation is not possible. • Tracing a book is difficult. • Information about issue/return of the books is not properly maintained. • No central database can be created as information is not available in database. All the manual difficulty in managing the Library have been rectified by implementing computerization. This application is reduced as much as possible to avoid errors while entering the data. It also provides error message while entering invalid data. No, formal knowledge is needed for the user to use this system. Thus by this all it is user-friendly. Library Management System as described above can lead error free, secure, reliable and fast management system. It can assist the user to concentrate on other activities rather to concentrate on the record keeping. Thus it will help organisation in better utilization of resources. So that’s why I can choose this topic to make it simple. is a sub-discipline of issues faced by libraries and library management professionals. Library management encompasses normal managerial tasks, as well as intellectual that focuses on specific freedom and fundraising responsibilities. Issues faced in library management frequently overlap with those faced in managing Title: L_I_B_R_A Page 5 of 16 TMU-CCSIT Version 1. 4-Project Description The software to be produced is on Library Management System. A library card will also be provided to the customers who visit daily. A person can also borrow the book for particular days. All the information will be entered in the system. If the person doesn’t return the due book. Admin has the authority to add, delete or modify the details of the book available to/from the system. He also has the authority to provide username and password for the receptionist. He can also add the details of the book purchased from shops along with the shop name. Project plan Requirement Design Process description implementation STATE DIAGRAM : LIBRARIAN OBJECT Title: L_I_B_R_A Page 6 of 16 TMU-CCSIT Version 1. 4.1-Scope of the Work This project is helpful to track all the book and library information and to rate the maximum number of books, the students wished to allot books. The software will be able to handle all the necessary information related to the library. From a librarian perspective, the Library Management System Project enhanced searchable database for the search books, managing library members, issuing and receiving books . • Search Books, Managing Library Members, Issuing and Receiving Books: An enhanced atomized system is developed to maintain Books, Authors, Issuing and Receiving Books and maintain the history of transaction. • To utilize resources in an efficient manner by increasing their productivity through automation. • It satisfies the user requirement. Title: L_I_B_R_A Page 7 of 16 TMU-CCSIT Version 1. 4.2-Project Modules • Books: This module consist the details of the books available in library and their categories. Title: L_I_B_R_A Page 8 of 16 TMU-CCSIT Version 1. • Member Account details To issue an book from the library, one should have a account in the library. The registration contains all the details about the member like registration number, name, address, contact number etc.. • Book Request: This module is used by the member to request a book from the library. The search can be performed by using name of the book, author name, and subject name. Title: L_I_B_R_A Page 9 of 16 TMU-CCSIT Version 1. • Issue of books: This module is used by the librarian to issue a book based on the request made by the members. • Returning Books: In this module the librarian maintains the details of the books returned by the member, which also includes the fine details, damage book details, lost book details. • History: In this module the member can view the details about the previous issued books, requested books and returned books etc. • Reports: This module includes the details about the issued books, returned books, member reports, fine reports, or any damage to the book or details of the book which are not returned. Title: L_I_B_R_A Page 10 of 16 TMU-CCSIT Version 1. 5-Implementation Methodology In this I am trying to give an Idea of “How I can implement the library management system” . FUNCTIONAL DECOMPOSITION OF LIBRARY MANAGEMENT SYSTEM CLASS DIAGRAM OF LIBRARY MANAGEMENT SYSTEM Title: L_I_B_R_A Page 11 of 16 TMU-CCSIT Version 1. DFD OF LIBRARY MANAGEMENT SYSTEM ER DIAGRAM OF LIBRARY MANAGEMENT SYSYTEM Title: L_I_B_R_A Page 12 of 16 TMU-CCSIT Version 1. DATABASE OF LIBRARY MANAGEMENT SYSTEM Title: L_I_B_R_A Page 13 of 16 TMU-CCSIT Version 1. 6-Technologies to be used 6.1 -Software Platform a) Front-end ----python (3.8) ----tk-inter (GUI) b) Back-end -----sqlite (database) 6.2 -Hardware Platform RAM — 8 GB Hard Disk — not used OS — Mac OS (Mojave-10.14.6) Editor — idle (Available with python package) Processor — 1.8 GHz intel core i5 6.3 -Tools No tool used. 7-Advantages of this Project Our proposed system has the following advantages. User friendly interface Fast access to database Less error More storage capacity Search facility Look and feel environment Quick transaction 8-Future Scope and further enhancement of the Project o In future we can make this application online so that members will be able to search the book from any places as well as can send book request. o Book reading facility can be provided through on-line. o In the area of data security and system security. o Provide more online tips and help. o Implementation of ISBN BAR code reader Title: L_I_B_R_A Page 14 of 16 TMU-CCSIT Version 1. 9-Project Repository Location S# Project Artifacts (softcopy) Location Verified by Project Guide Verified by Lab In-Charge 1. Project Synopsis Report (Final Version) https://s.docworkspace.com/d/AEsSC- 7eqLpR6Z6S_OSdFA Tushar mehrotra Name and Signature 2. Project Progress updates Name and Signature Name and Signature 3. Project Requirement specifications Name and Signature Name and Signature 4. Project Report (Final Version) Name and Signature Name and Signature 5. Test Repository Name and Signature Name and Signature 6. Any other document, give details Name and Signature Name and Signature 10-Team Details Project Name Course Name Student ID Student Name Role Signature LIBRARY MANAGEMENT SYSTEM INDUSTRIAL TRAINING(PYTHON) (ECS 509) TCA1809026 UTTKARSH PARMAR Developer 11-Conclusion “Library Management System” allows the user to store the book details and the customer details. This software package allows storing the details of all the data related to library. The system is strong enough to withstand regressive yearly operations under conditions where the Title: L_I_B_R_A Page 15 of 16 TMU-CCSIT Version 1. database is maintained and cleared over a certain time of span. The implementation of the system in the organization will considerably reduce data entry, time and also provide readily calculated reports. 12-References • Website http://www.wikipedia.com http://www.sololearn.com And also my mentor from Ducat (Noida) • Book Python-basic-handbook ( writer- vivek Krishnamoorthy, jay Parmar, mario pisa pena)
twilio / Twilio Cli CoreCore functionality for the twilio-cli
JuliaApproximation / ApproxFunBase.jlCore functionality of ApproxFun
LaughingLeader-DOS2-Mods / LeaderLibA core library mod used to provide common functionality to other mods.
walmartlabs / Strati FunctionalA lightweight collection of functional classes used to complement core Java.
