Download Placement Management System and more Study Guides, Projects, Research Computer Science in PDF only on Docsity!
P a g e | 1
A Project Report On
SUBMITTED BY
Under the Guidance of
Submitted in
Partial fulfilment of the requirement for the award of
MASTER OF COMPUTER APPLICATION
At
NM INSTITUTE OF ENGINEERING & TECHNOLOGY
(A Constituent college of Biju Patnaik University of Technology)
Bhubaneswar - 751019
BATCH- 2022 - 2024
**> REGD.NO-
REGD.NO- REGD.NO- REGD.NO-**
Asst. Prof. JITENDRA SAHU
CHINMAYA SARANGI SWADHIN KUMAR PRADHAN > REGD.NO- TUSHAR KUMAR SAMAL ABINASH SAMAL SUSHANTA KU. BARIK
PLACEMENT-MANAGEMENT-SYSTEM
HIMANSU SH. SAHOO > REGD.NO-
Table of Contents
- Introduction CHAPTERS PAGE NO.
- System Analysis/ Requirement Analysis
- System Design and Architecture
- Project Modules
- Implementation Details
- Feasibility Study
- Testing
- Snap-Shots
- Conclusion
- 10.Future Enhancements
- 11.References
2. System Analysis/ Requirement Analysis
It is a process of collecting and interpreting facts, identifying the problems, and decomposition of a system into its components. System analysis is conducted for the purpose of studying a system or its parts in order to identify its objectives. It is a problem-solving technique that improves the system and ensures that all the components of the system work efficiently to accomplish their purpose. Analysis specifies what the system should do. Taking the user requirements into consideration an understanding of the system requirements can be comprehended. The System Should Have the Following Features Bundled: Database support Reports Report with version chat control Flexibility Menu bar Dropdown menu Software And Hardware Selections: Hardware Selection: In this we need a personal computer, a floppy Disk and printers are required for this project. These requirements are to be met by the system. Hence the project is technically feasible. Software Selection: This project requires a language which supports a personal computer on client/server development environment. Microsoft SQL server is required as backend and PHP as front- end tool.
2.1 System Requirements Specification (SRS) (also known as a Software Requirements Specification) is a document or set of documentation that describes the features and behaviour of a system or software application. It includes a variety of elements that attempts to define the intended functionality required by the customer to satisfy their different users. Main Elements Depending on the methodology employed (agile vs waterfall) the level of formality and detail in the SRS will vary, but in general an SRS should include a description of the functional requirements, system requirements, technical requirements, constraints, assumptions and acceptance criteria. Each of these is described in more detail below: Business Drivers Business Model Functional and System Requirements Business and System Use Cases Technical Requirements System Qualities Constraints and Assumptions Acceptance Criteria
2.2.1. Technical Feasibility
This assessment focuses on the technical resources available to the organization. It helps organizations determine whether the technical resources meet capacity and whether the technical team is capable of converting the ideas into working systems. Technical feasibility also involves the evaluation of the hardware, software, and other technical requirements of the proposed system. As an exaggerated example, an organization wouldn’t want to try to put Star Trek’s transporters in their building—currently; this project is not technically feasible.
2.2.2. Economic Feasibility
This assessment typically involves a cost/ benefits analysis of the project, helping organizations determine the viability, cost, and benefits associated with a project before financial resources are allocated. It also serves as an independent project assessment and enhances project credibility— helping decision-makers determine the positive economic benefits to the organization that the proposed project will provide.
2.2.3. Legal Feasibility
This assessment investigates whether any aspect of the proposed project conflicts with legal requirements like zoning laws, data protection acts or social media laws. Let’s say an organization wants to construct a new office building in a specific location. A feasibility study might reveal the organization’s ideal location isn’t zoned for that type of business. That organization has just saved considerable time and effort by learning that their project was not feasible right from the beginning.
2.2.4. Operational Feasibility
This assessment involves undertaking a study to analyse and determine whether and how well the organization’s needs can be met by completing the project. Operational feasibility studies also examine how a project plan satisfies the requirements identified in the requirements analysis phase of system development.
2.2.5. Scheduling Feasibility
This assessment is the most important for project success; after all, a project will fail if not completed on time. In scheduling feasibility, an organization estimates how much time the project will take to complete. 2.3. System Specification: 2.3.1 Hardware Specification: - Pentium4 1.4GHZ or above 512MB RAM 20GB Free Hard disk space Standard colour monitor NIC or Modem (for remote sources) 2.3.2 Software Specification: - Operating System: windows NT/windows XP//2000/2007/2008/ Language: PHP (version 5.6 or 7.x) Server Technology: web server (XAMPP) Client-side Technology: HTML, AJAX, jQuery, JavaScript IDE: Edit plus Back End: My SQL
system immediately prompts the user and the user has to again key in the data and the system will accept the data only if the data is correct. Validations have been included where necessary. The system is designed to be a user friendly one. In other words the system has been designed to communicate effectively with the user. The system has been designed with popup menus.
USER INTERFACE DESIGN:
It is essential to consult the system users and discuss their needs while designing the user interface.
USER INITIATED INTERFACES:
In user-initiated interface, the user is in charge and controls the progress of the user/computer dialogue. User initiated interfaces fall into two approximate classes:
- Command driven interfaces: In this type of interface the user inputs commands or queries which are interpreted by the computer.
- Forms oriented interface: The user calls up an image of the form to his/her screen and fills in the form. The forms-oriented interface is chosen because it is the choice.
COMPUTER INITIATED INTERFACES:
In the computer-initiated interfaces the computer guides the progress of the user/computer dialogue The following computer-initiated interfaces were used:
- The menu system for the user is presented with a list of alternatives and the user chooses one of alternatives.
- Questions – answer type dialog system where the computer asks question and takes action based on the basis of the users replay.
ERROR MESSAGE DESIGN:
The design of error message is an important part of the user interface design. As user is bound to commit some errors or other mistakes, while designing a system the system should be designed to be helpful by providing the user with information regarding the error he/she has committed. This application must be able to produce output at different modules for different inputs.
PERFORMANCE REQUIREMENTS:
Performance is measured in terms of reports generated weekly and monthly. Requirement specification plays an important part in the analysis of a system. Only when the requirement specifications are properly given, it is possible to design a system, which will fit into required environment. It rests largely in the part of the users of the existing system to give the requirement specifications because they are the people who finally use the system. This is because the requirements have to be known during the initial stages so that the system can be designed according to those requirements. It is very difficult to change the system once it has been designed and on the other hand, designing a system, which does not cater to the requirements of the user, is of no use. The requirement specification for any system can be broadly stated as given below: The system should be able to interface with the existing system. The system should be accurate. The system should be better than the existing system. The existing system is completely dependent on the faculties to perform all the duties.
CHAPTER- 4
4. Project Modules
CHAPTER- 5
5.1 Implementation Details
5.1.1. Development Environment Setup
Install XAMPP: It provides PHP, MySQL, and Apache server. Configure Apache: Set up virtual hosts for local development. Configure PHP: Adjust settings in php.ini for error reporting and extensions. Configure MySQL: Set up user accounts and permissions in my.cnf.
5.1.2. Database Design and Creation
Design Schema: Create an Entity-Relationship Diagram (ERD) for the database. Create Database: Use MySQL commands to create a database. Create Tables: Define tables with appropriate data types and constraints.
Insert Data: Populate tables with initial data if necessary.
5.1.3. Back-End Development
Set Up Project Structure: Organize PHP scripts in a logical directory structure. Database Connection: Write a PHP script to connect to the MySQL database. CRUD Operations: Implement functions to create, read, update, and delete records. User Authentication: Develop login and registration system with session management.
5.1.4. Front-End Development
Design UI: Create wireframes and design the user interface. HTML/CSS: Write markup and styles for the web pages.
JavaScript: Add interactivity and validate forms on the client side.
It is responsible for data encryption and decryption of sensitive data before they are transmitted over common channels. It is also responsible for data compression. Data compression is done at the source to reduce the number of bits to be transmitted. It reduces the storage space and increases the file transfer rate. It is particularly useful for transmission of large multimedia files.
THE BUSINESS LOGIC LAYER: -
The business logic layer is where you tackle the problems your program was created to solve. In the logic layer, classes decide what information they need in order to solve their assigned problems, request that information from the accessor layer, manipulate that information as required, and return the ultimate results to the presentation layer for formatting. The business logic layer in this application does the spherical geometry—the Great Circle calculation itself. The calculation program, calcGreatCircle.php, uses an algorithm that assumes the Earth is perfectly spherical, which it isn't. The calculation is not the point here, so if you're thinking about using this application as a serious navigation tool, think again.
THE DATA STORAGE LAYER AND ACCESS LAYER: -
A data access layer ( DAL ) in computer software is a layer of a computer program which provides simplified access to data stored in persistent storage of some kind, such as an entity- relational database. This acronym is prevalently used in Microsoft environments. For example, the DAL might return a reference to an object (in terms of object-oriented programming) complete with its attributes instead of a row of fields from a database table. This allows the client (or user) modules to be created with a higher level of abstraction. This kind of model could be implemented by creating a class of data access methods that directly reference a corresponding set of databases stored procedures. Another implementation could potentially retrieve or write records to or from a file system. The DAL hides this complexity of the underlying data store from the external world. For example, instead of using commands such as insert , delete , and update to access a specific table in a database, a class and a few stored procedures could be created in the database. The procedures would be called from a method inside the class, which would return an object containing the requested values. Or, the insert, delete and update commands could be executed within simple functions like register user or login user stored within the data access layer. Also, business logic methods from an application can be mapped to the Data Access Layer. So, for example, instead of making a query into a database to fetch all users from several tables, the application can call a single method from a DAL which abstracts those database calls. Applications using a data access layer can be either database server dependent or independent. If the data access layer supports multiple database types, the application becomes able to use whatever databases the DAL can talk to. In either circumstance, having a data access layer provides a centralized location for all calls into the database, and thus makes it easier to port the application to other database systems (assuming that 100% of the database interaction is done in the DAL for a given application). Object-Relational Mapping tools provide data layers in this fashion, following the Active Record or Data Mapper patterns. The ORM/active-record model is popular with web frameworks.
5.2.1.3 THE 3 - TIER ARCHITECTURE
A 3 Tier Architecture in DBMS is the most popular client server architecture in DBMS in which the development and maintenance of functional processes, logic, data access, data storage, and user interface is done independently as separate modules. Three Tier architecture contains a presentation layer, an application layer, and a database server. 3 - Tier database Architecture design is an extension of the 2-tier client-server architecture. A 3- tier architecture has the following layers:
- Presentation layer (your PC, Tablet, Mobile, etc.)
- Application layer (server)
- Database Server
5.4.1 WEB SERVERS
Web server contains only web or servlet container. It can be used for servlet, jsp, struts, jsf etc. It can't be used for EJB. It is a computer where the web content can be stored. In general web server can be used to host the web sites but there also used some other web servers also such as FTP, email, storage, gaming etc. Examples of Web Servers are: Apache Tomcat and Resin.
