Report on PLADAT: Placement Dating Application.

Contents

Methodology 3

Discussion 3

Conclusion 4

An appendix containing all of UML models 5

An appendix containing (SRS). 11

An appendix containing wireframe 12

Methodology:

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. Using them, the class diagrams have been designed. In order to design the Class diagram, a proper set of the user database had to be decided and the flow of the app was decided initially. After deciding the target users, I developed the required attributes and methods of the classes. To create the System Requirement Specification Document, the overall project objective was taken care of. The purpose of the app and its users play an important role in writing the SRS.

Discussion:

It was difficult to sort the user database as placements take place in all the organisations. So the user database is a big chunk of data which gets difficult to manage if put all at once. So I decided to take up stream wise the data and then add them into the app. For example – the Engineering students are registered first and so on. The SRS document helped to understand the purpose and the scope of the project in depth because before documenting any Requirement document a thorough research is mandatory with clear defined goals.

Conclusion:

The class diagram of the PLADAT describes the structure of the application, their attributes and methods. It also describes the relationships among the objects. The main class of the PLADAT application are the Users, Company and Placements. Most of the activity revolves around them.

The appropriate design and management has been placed with the processing and determination of 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 Class Diagrams.

An appendix containing all of UML models

APPENDIX – I : Class Diagram of PLADAT

Classes of PLADAT – PLacement Dating App Class Diagram:

Placements Class : Manage all the operations of Placements Job Class : Manage all the operations of Job

Company Class : Manage all the operations of Company College Class : Manage all the operations of College

User Class : Manage all the operations of Users i.e Students

Permission Class : The admin manages the permissions of all the operations. Qualification Class : Students database is stored here with all the necessary details

Classes and their attributes of PLADAT – PLacement Dating App Class Diagram:

Placements Attributes : placement_id, placement_qualification, placement_type, placement_description

Job Attributes : job_id, job_name, job_profile, job_salary, job_vacancy

Company Attributes : company_id, company_name, comapny_type, company_description, company_location

College Attributes : college_id, college_name, college_description, college_location User Attributes : User_id, User_name, user_dob, user_role

Permission Attributes: permission_id, permission_title, permission_description Placement Attributes: placement_id, placement_qualification, placement_type, placement_description.

Qualification Attributes:qualification_id,qualification_type, qualification_description.

Classes and their methods of PLADAT – PLacement Dating App Class Diagram:

Placements Methods : addPlacements(), editPlacements(), searchPlacements(), deletePlacements() Job Methods : addJob(), editJob(), searchJob(), deleteJob()

Company Methods : addCompany(), editCompany(), searchCompany(), deleteCompany() College Methods : addCollege(), editCollege(), searchCollege(), deleteCollege()

User Methods : addUser(), editUser(), searchUser(), deleteUser()

Permission Methods: addPermission(), editPermission(), searchPermission(), deletePermission() Qualification Attributes: addQualification(), editQualification(), searchQualification(), deleteQualification()

APPENDIX – I : I * Diagram of PLADAT

APPENDIX – II : System Requirement Specification

SoftwareRequirements

Specification

for

PLADAT – Placement Datingfor Students

Version 1.0approved

Prepared by<author>

<organization>

<date created>

Table of Contents

Table of Contents ii

Revision History ii

1. Introduction 1
   1. Purpose 1
   2. Document Conventions 1
   3. Intended Audience and Reading Suggestions 1
   4. Project Scope 1
   5. References 1
2. Overall Description 2
   1. Product Perspective 2
   2. Product Features 2
   3. User Classes and Characteristics 2
   4. Operating Environment 2
   5. Design and Implementation Constraints 2
   6. User Documentation 2
   7. Assumptions and Dependencies 3
3. System Features 3
   1. System Feature 1 3
   2. System Feature 2 (and so on) 4
4. External Interface Requirements 4
   1. User Interfaces 4
   2. Hardware Interfaces 4
   3. Software Interfaces 4
   4. Communications Interfaces 4
5. Other Nonfunctional Requirements 5
   1. Performance Requirements 5
   2. Safety Requirements 5
   3. Security Requirements 5
   4. Software Quality Attributes 5
6. Other Requirements 5

Appendix A: Glossary 5

Appendix B: Analysis Models 6

Appendix C: Issues List 6

Revision History

Name	Date	Reason For Changes	Version

1. Introduction

1. Purpose

A description of all the functions and the constraints of the Project – PLADAT – Placement Dating System is provided in this Software Requirement Specification (SRS). This application is developed for students and college placement cell to ensure a smooth and hassle-free placement drive in the college.

This app will maintain a database of the students as well as the company. The students database will consist of all their records starting with their academic details. The company database will consist of company profiles , the eligibility criteria for the placements of that particular company, job descriptions and job openings at the company and also the package they are providing for the particular job profile.

1. Document Conventions

Heading : Font Size: 18 pt

Font Style : Bold Font:

Sub Heading : Font Size : 12pt

Font Style: Bold Font: Arial

Content: Font Size : 11pt

Font: Arial

1. Intended Audience and Reading Suggestions

As the name of the app itself suggests that the App is for Placement Co-ordinators of the Colleges and Companies as well. Along with them, Students are the major chunk of users of this app. Placing all the information together will help the HR. of company to make efficient choices of employees and students can understand or at-least get a glimpse of how the company is. The notifications will keep the students up to date with the new job openings around them or according to their choices.

1. Project Scope

The proposed system is designed to store all the academic and personal details of all the students registered and who are looking out for a job. This will also store the details of company which includes company profiles , the eligibility criteria for the placements of that particular company, job descriptions and job openings at the company and also the package they are providing for the particular job profile.

The notification feature of the app will ensure that the company as well as the student will be up to date with all the necessary information.

1. References

<List any other documents or Web addresses to which this SRS refers. These may include user interface style guides, contracts, standards, system requirements specifications, use case documents, or a vision and scope document. Provide enough information so that the reader could access a copy of each reference, including title, author, version number, date, and source or location.>

2. Overall Description

1. Product Perspective

This app will make the placement procedure hassle-free by maintaining the huge database of the students as well as the companies. This in turn will save the time and efforts and everything will be available with single click.

1. Product Features

The notification feature of the app will ensure that the company as well as the student will be up to date with all the necessary information.

1. User Classes and Characteristics

Major User Classes for the proposed system and their characteristics will be:

1. Student
   • Needs to Sign-up compulsorily
   • Needs to provide all the personal as well academic details so as to be eligible for the placement process.
   • They can chose their choice of company and be updated about them.

2. Administrator
   • Administrator will check the application when the students submit it and approve it.
   • Administrator will also check the application of the companies and then grant access to student profiles to them.
   • Updating the whole database regularly
   • Updating and setting notifications to the companies as well the students.

3. Company
   • Needs to sign-up compulsorily
   • Needs to fill up all the details with respect to the job profiles for which they are looking the candidate for.
   • Once the admin approves, the company can look out for a candidate and notify him/her to send in the resume.
   • Company will also be given access to students required personal and academic details.

1. Operating Environment

<Describe the environment in which the software will operate, including the hardware platform, operating system and versions, and any other software components or applications with which it must peacefully coexist.>

1. Design and Implementation Constraints

<Describe any items or issues that will limit the options available to the developers. These might include: corporate or regulatory policies; hardware limitations (timing requirements, memory requirements); interfaces to other applications; specific technologies, tools, and databases to be used; parallel operations; language requirements; communications protocols; security considerations; design conventions or programming standards (for example, if the customer’s organization will be responsible for maintaining the delivered software).>

1. User Documentation

<List the user documentation components (such as user manuals, on-line help, and tutorials) that will be delivered along with the software. Identify any known user documentation delivery formats or standards.>

1. Assumptions and Dependencies

<List any assumed factors (as opposed to known facts) that could affect the requirements stated in the SRS. These could include third-party or commercial components that you plan to use, issues around the development or operating environment, or constraints. The project could be affected if these assumptions are incorrect, are not shared, or change. Also identify any dependencies the project has on external factors, such as software components that you intend to reuse from another project, unless they are already documented elsewhere (for example, in the vision and scope document or the project plan).>

3. System Features

<This template illustrates organizing the functional requirements for the product by system features, the major services provided by the product. You may prefer to organize this section by use case, mode of operation, user class, object class, functional hierarchy, or combinations of these, whatever makes the most logical sense for your product.>

1. System Feature 1

<Don’t really say “System Feature 1.” State the feature name in just a few words.>

1. Description and Priority

<Provide a short description of the feature and indicate whether it is of High, Medium, or Low priority. You could also include specific priority component ratings, such as benefit, penalty, cost, and risk (each rated on a relative scale from a low of 1 to a high of 9).>

1. Stimulus/Response Sequences

<List the sequences of user actions and system responses that stimulate the behavior defined for this feature. These will correspond to the dialog elements associated with use cases.>

2.1.3 Functional Requirements

<Itemize the detailed functional requirements associated with this feature. These are the software capabilities that must be present in order for the user to carry out the services provided by the feature, or to execute the use case. Include how the product should respond to anticipated error conditions or invalid inputs.

Requirements should be concise, complete, unambiguous, verifiable, and necessary. Use “TBD” as a placeholder to indicate when necessary information is not yet available.>

<Each requirement should be uniquely identified with a sequence number or a meaningful tag of some kind.>

REQ-1:

REQ-2:

1. System Feature 2 (and so on)

4. External Interface Requirements

1. User Interfaces

<Describe the logical characteristics of each interface between the software product and the users. This may include sample screen images, any GUI standards or product family style guides that are to be followed, screen layout constraints, standard buttons and functions (e.g., help) that will appear on every screen, keyboard shortcuts, error message display standards, and so on.

Define the software components for which a user interface is needed. Details of the user interface design should be documented in a separate user interface specification.>

1. Hardware Interfaces

<Describe the logical and physical characteristics of each interface between the software product and the hardware components of the system. This may include the supported device types, the nature of the data and control interactions between the software and the hardware, and communication protocols to be used.>

1. Software Interfaces

<Describe the connections between this product and other specific software components (name and version), including databases, operating systems, tools, libraries, and integrated commercial components. Identify the data items or messages coming into the system and going out and describe the purpose of each. Describe the services needed and the nature of communications. Refer to documents that describe detailed application programming interface protocols. Identify data that will be shared across software components. If the data sharing mechanism must be implemented in a specific way (for example, use of a global data area in a multitasking operating system), specify this as an implementation constraint.>

1. Communications Interfaces

<Describe the requirements associated with any communications functions required by this product, including e-mail, web browser, network server communications protocols, electronic forms, and so on. Define any pertinent message formatting. Identify any communication standards that will be used, such as FTP or HTTP. Specify any communication security or encryption issues, data transfer rates, and synchronization mechanisms.>

5. Other Nonfunctional Requirements

1. Performance Requirements

<If there are performance requirements for the product under various circumstances, state them here and explain their rationale, to help the developers understand the intent and make suitable design choices. Specify the timing relationships for real time systems. Make such requirements as specific as possible. You may need to state performance requirements for individual functional requirements or features.>

1. Safety Requirements

<Specify those requirements that are concerned with possible loss, damage, or harm that could result from the use of the product. Define any safeguards or actions that must be taken, as well as actions that must be prevented. Refer to any external policies or regulations that state safety issues that affect the product’s design or use. Define any safety certifications that must be satisfied.>

1. Security Requirements

<Specify any requirements regarding security or privacy issues surrounding use of the product or protection of the data used or created by the product. Define any user identity authentication requirements. Refer to any external policies or regulations containing security issues that affect the product. Define any security or privacy certifications that must be satisfied.>

1. Software Quality Attributes

<Specify any additional quality characteristics for the product that will be important to either the customers or the developers. Some to consider are: adaptability, availability, correctness, flexibility, interoperability, maintainability, portability, reliability, reusability, robustness, testability, and usability. Write these to be specific, quantitative, and verifiable when possible. At the least, clarify the relative preferences for various attributes, such as ease of use over ease of learning.>

6. Other Requirements

<Define any other requirements not covered elsewhere in the SRS. This might include database requirements, internationalization requirements, legal requirements, reuse objectives for the project, and so on. Add any new sections that are pertinent to the project.>

Appendix A: Glossary

<Define all the terms necessary to properly interpret the SRS, including acronyms and abbreviations. You may wish to build a separate glossary that spans multiple projects or the entire organization, and just include terms specific to a single project in each SRS.>

Appendix B: Analysis Models

<Optionally, include any pertinent analysis models, such as data flow diagrams, class diagrams, state-transition diagrams, or entity-relationship diagrams.>

Appendix C: Issues List

< This is a dynamic list of the open requirements issues that remain to be resolved, including TBDs, pending decisions, information that is needed, conflicts awaiting resolution, and the like.>

APPENDIX – III: Wireframe

The post development of a logical system for PlaDat appeared first on My Assignment Online.