Let's start a new assignment project together, Get Exclusive Free Assistance Now!

Need Help? Call Us :

Place Order

PlaDat: Placement Dating for Students

Mar 13,23

Question:

Background:

Problem Statement 2

Title – PlaDat: Placement Dating for Students*

 

Project Abstract

This project will create a matching service to connect placement students with potential employers. Using a “dating” service metaphor, the site will allow employers to post details of placements available and students to apply for placements.

This project will create a database-driven mobile-friendly website to encourage employers and students to engage in year-long paid industrial placements as part of an honours degree programme.

Project Description

Placements with employers play a valuable role in the learning journey for software engineering and computing students. Placement students are paid a salary and benefit from support and mentoring towards working on live production projects. Different terminology is used in different countries. Placements are sometimes called “paid internships” or “work experience.”

Placements can benefit employers by:

  • Helping existing staff members develop their mentoring and management skills
  • Providing an improved recruitment pipeline for graduate vacancies
  • Giving extra resources to projects and helping to offer imaginative new ideas
  • Supporting partnership building with Universities

Placements with employers play a valuable role in the learning journey for software engineering and computing students. Placement students are paid a modest salary but benefit from support and mentoring towards working on live production projects. Placement students gain first-hand experience of working on commercial projects. The daily interactions with practitioners help students gain valuable professional and technical skills.

Project Scope

The project comprises three main elements: placement descriptions, student capabilities and a matching algorithm. Users (employers and students) will need to be able register with the site and store details of placements and capabilities. Some persistent storage will be required to retain placement details, student capabilities, and user credentials.

*This project specification is taken (and updated) from the Student Contest on Software Engineering Projects (https://conf.researchr.org/home/icse-2021/score-2021#Project-Proposals) at the 43rd International Conference on Software Engineering.

Assignment 1: Modeling Requirements

Important note

  1. You are required to read problem statement work on it as per instructions provided below.

Doing the Assignment

This assignment has following steps. They are listed as below:

  • Use requirements elicitation techniques to analyse information and features provided in the selected problem statement. You are also allowed to collect any additional information/additional innovative feature(s) you may need to refine the requirements.
  • Develop models of key aspects of the problem. Your models must include:
    1. The required functionality of the proposed system (using UML Use Case Diagrams AND UML Sequence Diagrams).
    2. The dynamic behaviour of relevant objects in the application domain of the proposed system (using UML Activity Diagrams AND State Diagrams).
  • Drawings must be clear and legible. You can use open source modeling tools of your choice like ArgoUML, Star UML etc to draw your models – Strictly, do not draw models/diagrams by hand.
  • Clearly list any assumptions you might make in completing this assignment at appropriate places.

Written requirements of the assignment:

You must hand in a report (in .WORD format and contain all relevant graphics) that should contain the following:

  • You should hand in a report of your work, not exceeding three (2) pages (not counting references, appendices, figures or tables etc). The report itself is intended just to give an overview of what you did, and the rationale for any choices you made (e.g. about what to model and how to model it; the requirements elicitation techniques used to further refine the requirements, discuss any interesting lessons learned during the elicitation and modeling process etc).
  • An appendix containing all of your analysis models. Make sure you provide enough commentary with the models for the reader to understand what each model is of, and how to understand them.
  • Any further appendices you feel are relevant

Assignments will be judged on the basis of visual appearance, grammatical correctness and quality of writing, as well as their contents. Please make sure that the text of your report is well-structured, using paragraphs, full sentences, and other features of a well-written presentation. The report must not consist of itemized lists of points. Text font size should be either 10 or 12 points.

Lectures notes:

  • https://www.youtube.com/watch?v=zid-MVo7M-E
  • https://www.youtube.com/watch?v=UI6lqHOVHic

Answer:

Introduction

PLADAT: PLACEMENT DATING FOR STUDENTS

 

Table of Contents

Introduction. 3

Required Functionality and Proposed Systems. 3

Dynamic Behaviour of Relevant Objects. 6

Summary. 9

References. 10

Appendices. 11

 

Introduction

This report has been associated designing and development of a logical system for PlaDat, a placement dating structure. The application of the proper information systems designing concepts and the application of various UML logic systems have been done through structural assessment and communication for the structures and their analytics. The valid operation of systems and their considerations have been directed through software engineering and computing system structures. The direction has been related with the consideration of placement dating structure of operations and management. The respective and relevant perspective has been directed through the systems designing.

Required Functionality and Proposed Systems

In this particular application, the consideration of the valid functional requirements has been directed through proper consideration (Babar et al. 2020). The identification has been related with proper direction and justification. The valid identifiers have been stated below:

  • Account Registration and Login
  • Posting of jobs (Employers)
  • Browsing for Jobs (Students)
  • Interview Request (Students)
  • Student Assessment (Employers)
  • Interview Confirmation
  • Payment Processing (Employers)

UML Use Case

Figure 1: Use Case Design (Student)

[Refer to Appendix 1]

Figure 2: Use Case Design (Employer)

[Refer to Appendix 1]

In this particular consideration two specific diagrams have been provided for the tasks done by student actors and the tasks done by the employer actors.

UML Sequence

Figure 3: System Sequence Design (Student)

[Refer to Appendix 2]

Figure 4: System Sequence Design (Employer)

[Refer to Appendix 2]

In this particular consideration two specific diagrams have been provided for the tasks done by student actors and the tasks done by the employer actors.

Dynamic Behaviour of Relevant Objects

In this particular consideration, the approaches of the specific strategic of operation have been related and made relevant through the conceptual presentation of the logic behind operation. The appropriate activities have been thoroughly setup through the directional logic. The assessment has been related with proper application and consideration for the directive logic (Jetlund, Onstein & Huang, 2019). The direction has been considered with the help of directive development and qualification for the specifics. The direction and logic has been stated with the consideration and management of the applications and their specific approaches. The determination and has been related through proper approach and specification.

UML Activity

Figure 5: Activity Diagram (Student)

[Refer to Appendix 3]

Figure 6: Activity Diagram (Employer)

[Refer to Appendix 3]

In this particular consideration two specific diagrams have been provided for the activities form the students as well as from the employers.

UML State Transition

Figure 7: State Transition Diagram (Student)

[Refer to Appendix 4]

Figure 8: State Transition Diagram (Employer)

[Refer to Appendix 4]

In this particular consideration two specific diagrams have been provided for the states of operation form the students as well as from the employers.

Summary

The development and application of the design for this required placement dating software system has been related with proper consideration and use of respective UML logics and designs. The appropriate designing and management has been placed with the processing and determination for the directives and their logical structure of specification. This report contains relevant specific documentation on the directive designing and management of the necessary logical structure with the help of proper Unified Modelling Language under consideration. The direction has been made relevant with the use of valid type of UML logic systems through development of functionalities and their dynamic nature for objective specification and management.

 

References

Babar, M., Khattak, A., Arif, F., & Tariq, M. (2020). An Improved Framework for Modelling Data Warehouse Systems Using UML Profile. The International Arab Journal of Information Technology17(4), 562-571. https://www.academia.edu/download/63794903/1576720200701-47989-1e1phyk.pdf

Jetlund, K., Onstein, E., & Huang, L. (2019). Adapted Rules for UML Modelling of Geospatial Information for Model-Driven Implementation as OWL Ontologies. ISPRS International Journal of Geo-Information8(9), 365. https://www.mdpi.com/2220-9964/8/9/365/pdf

Pourali, P. (2020). A User-Centric Approach to Improve the Quality of UML-like Modelling Tools and Reduce the Efforts of Modelling. https://uwspace.uwaterloo.ca/bitstream/handle/10012/15595/Pourali_Parsa.pdf?sequence=3

Vu, T., Probst, C., Nielsen, A., Bai, H., Buckley, C., Meier, P., … & Purshouse, R. (2020). A software architecture for mechanism-based social systems modelling in agent-based simulation models. Journal of Artificial Societies and Social Simulation. http://eprints.whiterose.ac.uk/159213/8/1.pdf

Winiarski, T., Węgierek, M., Seredyński, D., Dudek, W., Banachowicz, K., & Zieliński, C. (2020). EARL—Embodied Agent-Based Robot Control Systems Modelling Language. Electronics9(2), 379. https://www.mdpi.com/2079-9292/9/2/379/htm

 

Appendices

Appendix 1: Use Cases

Use case 1: The procedure begins with student trying to register into the placement dating system. The system admin is associated with creating the user account on behalf of the students. The next step of procedure is to log into the application. It is here that the student can present and project their capabilities with information and Curriculum Vitae upload feature. The students then start browsing into the tasks and choose one or more through request for interview. The admin then consults with the employer on behalf of the student and then forwards the date of interview once confirmed. The students could also be provided with an option to choose their suitable date. The direction is associated with issuing of the specific slip for confirmation, although it can be kept optional.

Use case 2: The procedure begins with employer trying to register into the placement dating system. The system admin is associated with creating the user account on behalf of the employer. The next step of procedure is to log into the application. The employers then start placement of jobs (Pourali, 2020). The details for the placement and previously stated date of interview can also be provided for a proper consideration and assessment when the students apply. The admin then collects various interview requests from students and forwards the requests. The fixing of the interview is then done form the employer side. The confirmed student data including the CV is provided to the employer by the system. The direction is associated with issuing of the specific slip for confirmation, although it can be kept optional.

Appendix 2: Sequences

Sequence 1: The sequence structure for the system has been done through student considerations. The application has been directed with the help of three interfaces. The registration interface has all the familiar prospects of creation and use of student account. The Browsing interface is associated with checking for suitable jobs. The final Interface begins when the interview request has been sent. The admin forwards the request and the system goes into a waiting state. Once the confirmation for interview is received by admin, it is forwarded to student with the help of a proper confirmation slip.

Sequence 2: The sequence structure for the system has been done through employer considerations. The application has been directed with the help of three interfaces. The registration interface has all the familiar prospects of creation and use of employer account. The posting and assessment interface is associated with placement of specification for suitable jobs and assessment of the student sending the interview requests. The final Interface begins when the student assessment has been done. The admin forwards the interview confirmation to the student and the system goes into a waiting state for payment. Once the payment is done by the employer, the service charge is processed and the admin forwards thee receipt for payment.

Appendix 3: Activities

Activity 1: In this approach, the initial activity of the student is to register. The system goes through a conditional logic and then places the old user for a login. The system then directed to a parallel aspect of operations. Students can either book service through application of jobs or get a proper assessment of the previously sent interview requests. The interview requests go through another conditional statement (Vu et al. 2020). If the interview is confirmed, then the system initiates the appointment confirmation activity. In this type of activity and use of conditional statements, all negative outcomes are subject to reversal of the flow to the previous activity.

Activity 1: In this approach, the initial activity of the employer is to register. The system goes through a conditional logic and then places the old user for a login. The system then directed to a parallel aspect of operations. Employers can either book service through posting of jobs or get a proper assessment of the previously received interview requests and approach the system for the interview confirmation activity. The interview confirmation goes through another conditional statement. If the interview is confirmed, then the system initiates the appointment confirmation activity. In this type of activity and use of conditional statements, all negative outcomes are subject to reversal of the flow to the previous activity.

Appendix 4: States

State 1: This structure is much similar to the concept of activities and their dynamic nature of application. The state machine approach initiates when the student applies for a job. The process goes into idle state and the machine acquires the respective data. The parallel procedure begins after this state. The new applicants can check for the eligibility for specific interview (Winiarski et al. 2020). The old applicants can directly check the Approval of previously sent interview requests. The direction is related with the proper assessment and analysis for a direct approach and development of the systems through a conditional state of forwarding the new interview requests. The system stays in idle state until the confirmation is done.

State 2: The state machine approach initiates when the employer processes for a job advertisement. The process goes into idle state and the machine acquires the respective data. The parallel procedure begins after this state. The employers can check all the new job interview requests. The old interview requests can be associated with a confirmation after state after the assessment by student. The direction is related with the proper assessment and analysis for a direct approach and development of the systems through a conditional state of assessment of students. The system stays in idle state until the eligibility is evaluated.

0 responses on "PlaDat: Placement Dating for Students"

Leave a Message

Your email address will not be published. Required fields are marked *