Loading repository data…
adambruzac / repository
Brief: Design, implement and test a stand-alone University Human Resources system using objectoriented principles in Java and accessed using a graphical user interface. Design should include use cases and a class diagram while testing should include black box and white box testing Here are the specific requirements: Assume the new Northampton Metropolitan University would like a system for their human resources department to keep track of lecturing staff who work in various departments through a graphical user interface. The system also allows a department secretary to view the details of all the lecturers in his/her department. Human resources staff access the system through a single user name and password. Likewise, department secretaries access the system through a different user name and password which is stored with each department (see below). The new Northampton Metropolitan University will be made up departments which, in turn, will be made up of lecturers. The human resources department need to keep track of each department and their associated staff. Each department has a name (e.g Physics, Chemistry etc), type of department (e.g Science, Arts, Engineering etc) and a web address. For each department we also store a user name and password to allow a department secretary to log in to view the lecturers in his/her department. Each department is made up of lecturers. The new University has the following 3 distinct types of lecturers: 1. Full-time Lecturers – each full-time lecturer has a staff identification number, name, address, phone number, email address, the date they started and their salary 2. Part-time Lecturers – each full-time lecturer has a staff identification number, name, address, phone number, email address, the date they started and their hourly rate. 3. Contract Lecturers – each full-time lecturer has a staff identification number, name, address, phone number, email address, the date they started, salary and the date their contract will finish Minimum System Requirements (for grades upto D-): The system must, using a GUI, allow human resource staff to do the following: 1. Log onto the system with a user name and password 2. Exit the system 3. Add a new department 4. Change details of a department 5. Delete a department 6. Add a new lecturer of any type (full-time, part-time or contract) and allocate them to a department 7. Change details of a lecturer 8. Delete a lecturer The system must, using a GUI, also allow departmental secretaries to do the following: 9. Log onto the system with a user name and password that is stored with each department 10. Exit the system 11. Show details of the full-time lecturers 12. Show details of all the part-time lecturers 13. Show details of all the contract lecturers 14. Query a specific lecturer’s details including what type of lecturer they are (full-time, part-time or contract) by their staff identification number 15. Show details of all the details of all the lecturers (including their type) in their department Additional System Requirements (for grades C to A+): 16. Exit the system and write all objects to file so they can be reloaded when the system is run again 17. An intuitive GUI 18. Appropriate exception handling 19. Use the Model View Controller 20. Use of Collections Note that object serialisation must be used and no marks to be given for use databases and SQL queries.
Brief: Design, implement and test a stand-alone University Human Resources system using objectoriented principles in Java and accessed using a graphical user interface. Design should include use cases and a class diagram while testing should include black box and white box testing Here are the specific requirements: Assume the new Northampton Metropolitan University would like a system for their human resources department to keep track of lecturing staff who work in various departments through a graphical user interface. The system also allows a department secretary to view the details of all the lecturers in his/her department. Human resources staff access the system through a single user name and password. Likewise, department secretaries access the system through a different user name and password which is stored with each department (see below). The new Northampton Metropolitan University will be made up departments which, in turn, will be made up of lecturers. The human resources department need to keep track of each department and their associated staff. Each department has a name (e.g Physics, Chemistry etc), type of department (e.g Science, Arts, Engineering etc) and a web address. For each department we also store a user name and password to allow a department secretary to log in to view the lecturers in his/her department. Each department is made up of lecturers. The new University has the following 3 distinct types of lecturers:
Selected from shared topics, language and repository description—not editorial ratings.
EricLego /
Client-server countdown protocol project: client sends integer n n; server replies with countdown n n to 1. Implement iterative and concurrent connection-oriented versions in Java using a three-tier design. Submit code, brief report, and output screenshots.
ahmedmaged3k1 /
This repository contains S.O.L.I.D principles brief explanation and example of each principle and its benefits, Also contains famous antipatterns to avoid while coding, Atlast it, contains an explanation, benefits, drawbacks, UML diagram, and implementation in java for multiple design patterns with different types as (Creational , Behavioral , Structural ). Each topic is represented in a branch with it name .
sekharpasem /
Problem Statement :- Indian Government wants you to create a Java solution for managing the voting on motions once debate has concluded in the parliament. The system you create must accept votes (For or Against) on a specified motion and determine whether motion is pass or fail. Conditions :- 1. No votes can be accepted upon a motion until it is opened for voting. 2. When a motion is closed for voting, a result is returned that describes whether the motion passed or failed The number of votes for and against The time that voting opened and closed 3. A motion cannot be closed for voting less than 15 minutes after it was opened. 4. No voter can vote more than once on the same motion. 5. The maximum votes that can be received on a motion is 51. 6. If voting is a tie, then an attempt to close the motion for voting will cause it to enter a special "tied" state. 7. In the "tied" state, the speaker of the parliament is the only person allowed to vote. Once the speaker votes, the motion is automatically closed. 8. The speaker is not allowed to vote except when voting has entered the "tied" state. 9. If the speaker is not available to vote, then voting can be forced to the closed state which causes the motion to fail. Implementation Details :- 1. Expose a rest api to start a new motion. Only speaker should have access to start a new motion. 2. Expose a rest api to accept vote of a user (For or Against). 2. Expose a rest api to get the current state of a motion at any time (Not Started, In progress, Completed, Tied, Void). 3. Expose a rest api to get the results of a motion (The number of votes for and against, and the time that voting opened and closed). 4. Write unit test cases to validate the above conditions. Note :- The solution will be evaluated on following parameters. Object Oriented Design aspects of the solution. Overall coding practices. Working code covering the above conditions. You must include a brief explanation of your design, restrictions and assumptions in a README file.
vaishvik12 /
### Brief Description The Project Management System is a Java-based application designed for managing educational course-related data. It features key entities including Course, Faculty, Batch, and Student, each represented by POJOs. Implementation classes handle CRUD operations, guided by defined interfaces.
AhmedSleeem /
this repo contains a brief implementation of GoF design patterns with a brief explanation using java
AlifTalha /
This repository contains a Java project that [briefly explain the project purpose or functionality]. Java, as a versatile and widely-used programming language, is designed to have minimal implementation dependencies, making it an excellent choice for building cross-platform applications.