Download - Resume Bulider Ppt
RESUME BUILDER APPLICATION
OBJECTIVE
• Develop an Intranet Application for automating the process of Resume Writing
•This would be facilitating the employees to make and print their resumes in a proper format.
•It will be facilitating the higher management to search the employees depending upon their skills sets and other attributes.
FEATURES AND SERVICES
LOGIN
EMPLOYEEADMINISTRATOR
View Resume And Print Resume Of Employee In PDF Format.Search for a particular employees according to search criteria.
Enter information into their Resume / Edit Resume.
Print their resume as a PDF Document.
COMONENTS OF RESUME
Biographical Data
Objective
Skill Area
Awards / Certificates
Employment History
Education History
THE RESUME
References
FEASIBILITY STUDY
•The feasibility study is carried out to test whether the proposed System is worth implemented.
• Feasibility study is the test of proposed system regarding its work ability.
The key consideration involved in the feasibility study is:
•Technical
•Economic
•Behavioral
•Operational
•Technical FeasibilityTechnical Feasibility center on the existing computer system and to what extent it can support the proposed system addition.
• Behavioral FeasibilityPeople are inherently resistant to change and computers have been known to facilitate change. An estimate should be made of how strong a reaction the user staff is likely to have towards the development of computerized system.
•Economical feasibility
This software is technically feasible therefore it is very cost effective and can be run on any computer. Hence, economical feasible. There is no need to purchase extra software & hardware. Any person or organization which is using any traditional development environment can use this user friendly development environment instead of that at no extra cost.
•Operational feasibility This project meets the operating requirement of the professional programmer. This test asks if the system will work when it is installed. There are sufficient supports for the project from user. User may welcome, may change that will bring about a more operational and useful system.
SCOPE OF APPLICATION
SOFTWARE SCOPE
•Reusability
Reusability is possible as and when require in this application. We can update it next version. Reusable software reduces design, coding and testing cost by amortizing effort over several designs.
Reducing the amount of code also simplifies understanding, which increases the likelihood that the code is correct. We follow up both types of reusability:Sharing of newly written code within a project, andreuse of previously written code on new projects.
•UnderstandabilityA method is understandable if someone other than the creator of the method can understand the code (as well as the creator after a time lapse). We use the method, which small and coherent helps to accomplish this.
•Cost-effectivenessIts cost is under the budget and make within given time period. It is desirable to aim for a system with a minimum cost subject to the condition that it must satisfy the entire requirement. Scope of this document is to put down the requirements, clearly identifying the information needed by the user, the source of the information and outputs expected from the system.
REQUIREMENTS
Number Description Alternatives (If available)
1 PC with 2 GB hard-disk and 256 MB RAM
Not-Applicable
1. Hardware requirements
2. Software Requirements
Number Description Alternatives (If available)1 PHP2 SQl Server 2000 Oracle 83 Windows 2000 Alternatively, Windows 98
with IIS Server Installed.
3. FUNCTIONAL REQUIREMENTS
Requirement Essential / Desirable
Description of the Requirement
Remarks
The system should have a login
Essential A login box should appear when the system is invoked.
The logins are assigned by the mail-admin
The system should have help screens
Essential Help about the various features of the system should be provided in sufficient detail in a Q&A format.
Some tips on writing a neat resume can be given in the help section.
Requirement Essential / Desirable
Description of the Requirement
Remarks
The system should ‘lock’ the login id if wrong password is entered 3 times in a row
Desirable This feature will improve the robustness of the application
Since the application is going to be used only by the employees of the organization, this feature is not essential. However, if time is there, this will be implemented
Requirement Essential / Desirable
Description of the Requirement
Remarks
The System Should enable the user to Logout.
Essential This feature is necessary for the Security purpose.
The System should show proper error messages in case of an error
Desirable Making the Application Robust and more User friendly.
There should be no unhandled exception. The application should never hang due to an unhandled error.
4. User Characteristics Every user should be comfortable of working with computer and net browsing. He must have basic knowledge of English too.
5. Constraints•GUI is only in English.•Login and password is used for identification of customer and there is no facility for guest.•This system is working for single server.•We will use server space for our project, hence we can access through single machine or a number of simultaneous user.• Another importance is, in case of system crash we will not be needed backup as we can get it from server.
DATABASE TABLES1. LOGIN TABLE :
Field Name Data type Valid values for the field
Remarks
Username Text Should be 20 characters long and cannot contain special characters
All users will have their username and administrator will have login ADMIN
Password Text Must be atleast 6 characters and should not exceed by 15 characters
All users will get password by the admin which they can change and update later.
2. DATABASE 2 :
Field Name Valid values for the field
Remarks
Employee Number It will be numerical starting with EMP
This is the key field of the database as it is unique for an employee in the organization. This may also serve as the login for the system.
Name Up to 15 characters in length.Will Have First Name , last name and middle name
Special characters like underscore are not allowed.
Role Pre-defined set (like engineers/managers/etc)
The reporting hierarchy is based on the role of the person. For example, an engineer reports to a manager, a manager reports to a business manager etc
Field Name Valid values for the field
Remarks
Email Id Up to 25 characters in length (including the domain name)
This field should also be unique for a person because no two employees in an organization can have the same email id.
Age Will be numeric
Phone Number Should contain STD codeAnd should not be more than 10 digits in case of mobile
Will contain al phone number that is residence, office, mobile number
Address Should be valid address and must contain all details
The address should contain city , state , pin code etc.
Objective Should not be more than 200 characters.
This field contains the objective of your resume
Field Name Valid values for the field
Remarks
Summary Should not be more than 500 characters
This field contains the summary of the resume.
Educational History Should contain percentage and passing year
This field contains all the educational information of 10,10+2, graduation and if post graduation with percentage and passing year.
Employment History Should have date of service not more than the current or joining date
It contains all the detail about the previous employer of the employee
Awards Should be verified This field contains the descriptions of awards the employee has got
Field Name Valid values for the field
Remarks
Certifications These can be international or company
It contains all the description about the certifications the employee has got
Skills Will be multiple valued It has all the description about the skills which a employee has and can be useful for the company
Publications Should contain the publication date and magazine name
It contains the papers or articles if any published by the employee
References Should have field whether the reference if employee here or outsider
It contains information about the employee’s referencee
USE CASE DIAGRAM
USE CASE TABLEUse Case Login # Help
Actors System Administrator and Employee
Description System administrator and employee will need to enter user name and password before they can access the system for security reasons
Pre-condition Login screen is active prompting user to enter user name and password or goto to the help screen.
Flow
Of
Events
Enter username Enter password
Password confirmation If password correct go to user logged in If password is wrong go to error message OR
Press F1 or click “HELP” button for help
DATA FLOW DIAGRAMS
Resume
BuilderUser Administrator
Level-0 DFD
LEVEL 1
LEVEL - 2 MAIN WINDOW
LEVEL - 2 SEARCH
LEVEL - 2 LOGIN / HELP
LEVEL - 2 PRINT
LEVEL - 2 HELP
E-R DIAGRAM
SNAPSHOTS
LOGIN WINDOW
MAIN WINDOW
HELP WINDOW
CONTACT INFORMATION WINDOW
ADRESS WINDOW
OBJECTIVE WINDOW
EDUCATIONAL HISTORY WINDOW
EMPLOYMENT WINDOW
AWARDS WINDOW
SKILLS WINDOW
LICENSE AND CERTIFICATE WINDOW
REFERENCE WINDOW
PUBLICATIONS WINDOW