Final Document Resume Builder

7/27/2019 Final Document Resume Builder

1/31

1. INTRODUCTION

1.1 ORGANISATION PROFILE

DAFFODILLS INDIA, established in the year 2006.They are located

near Edayarpalayam, Coimbatore.

DAFFODILLS INDIA is the organization and the development from based

on the customer satisfaction and service towards the nation and the clients in

abroad.

Solutions are committed in providing innovative Software Solutions to its

Clients and recognize the importance of technology. DAFFODILLS INDIA

seasoned software Professional has Expertise in a wide range of technologies

including, but limited to,

Web Technology

Client Server Technology

Database Design, Development and Administration

Customized Package Software implementation like

Accounts

Development of System Software Low Level

Programming

Server Side Programming

DAFFODILLS INDIA undertake Short Team and Long Term Projects on a

contract and regular basis with reputed Clients. DAFFODILLS INDIA goal is to

clearly understand their Clients need and provide them with real and lasting

Solutions that meet and exceed their Expectations.

The data generated has to be processed speedily and accurately to produce

useful formation that will help the organization in managing its business more


2/31

efficiently and effectively. This results in an increased need for the introduction of

modern technology to the transaction and events at source of origin and to make

information available to the user.


3/31

1.2 ABOUT THE PROJECT

A resume also spelled resume or resume also called curriculum vitae

or CV, is a document that contains a summary or listing of relevant job

experience and education. The rsum or CV is typically the first item that a

potential employer encounters regarding the job seeker and is typically used

to screen applicants, often followed by an interview, when seeking

employment.

In the job search process, a well-written and well-designed resume

is essential. Our program does the thinking and writing for you.

Resume Builder simplifies the work of finding the job by providing

intelligent and user-friendly software

Resume Builder can display the resume structure in a user-friendly

format, so that you can choose which sections of the resume to publish.

You can also modify the order of the Published Sections Biographical

Data, Objective, Employment History, Education History, Personal, Skill

Areas, Publications, Summary and Certifications.


4/31

2. SYSTEM CONFIGURATION

2.1 HARDWARE CONFIGURATION

1. Processor Pentium IV with 3.0 GHz.

2. RAM 256MB

3. HDD 40GB

4. Monitor 15 Color monitor with 16 million colors

5. Pointing device Two - button Mouse or 3-button Mouse.

6. Keyboard 104 Keys

2.2 SOFTWARE CONFIGURATION

1. FRONT END VB.NET

2. Platform Microsoft Windows server

3. Back End MS SQL SERVER 2000


5/31

3. SYSTEM STUDY AND ANALYSIS

The system analysis is conducted with the following objectives in mind.

They are to satisfy the customers according to their needs, to evaluate the system

concept for feasibility, to allocate functions to hardware, software, people,

database and other system elements to create a system definition that forms the

foundation for all subsequent engineering works.

3.1FACT FINDING

Fact finding is the stage in which data about the system are collected in

terms of technical and functional requirements. In this project the data collection is

completed using the data carriers which are existing in the tables.

3.2FEASIBILITY ANALYSIS

When developing a system, it is necessary to evaluate the feasibility of

project at the earliest possible time. Unexpected technical problems and timing

problems can occur when poor problem definition is obtained. It is advisable to

conduct discussions regarding the analysis and design of the project before starting

it.

Economic Feasibility

The proposed system developed includes the following related issues.

Cost of resources needed for development.

Cost benefit analysis.

Potential market growth.

While concerning the cost of resources for the server side, amount is

invested for the high capacity of storage media, high speed processor and large


6/31

amount of memory needed for the system. While concerning the client side a

minimal amount of cost is needed. Overall the cost of setting up the server and

configuring it will be costly at the time of installation. While considering the cost

benefit analysis, huge amount will be invested only at the time of first installation.

Technical Feasibility

The technical feasibility involves the analysis of all possible condition for

obtaining the system. It actually involves a study of function Performance and

constraints that may affect the ability to achieve an acceptable system, the

considerations that are normally associated with the technical feasibility include

the following:

Development risk

Resource availability

Technology

The development risk concerns the probability the function of all elements

and its performance should be same in all platforms and in the system that is being

developed. This system is developed according to the web standards and the

development software tools are selected in such a way to avoid the problems sited

above.

The resource availability states whether skilled staffs are available to

develop the system elements and the availability of hardware and software. The

hardware is provided by the organization satisfying all the requirements.


7/31

3.3EXISTING SYSTEM

Analyzing the customer complaints, orders and generating reports are done

manually which is time consuming. The customer response also becomes a tedious

task. Drafting required for trainees also done manually. Searching for information

through multiple files and data analysis also becomes a tedious task.

Draw Backs

Time-consuming

A tedious task

Cause damage to the brand image of the organization

Slow updation and retrieval of information


8/31

3.4 PROPOSED SYSTEM

No Experience

Resume writing software can be a welcome relief to job seekers who are

uncomfortable with the idea of drafting a resume from scratch. Resume

writing software can provide a step by step foundation, where the job seeker

needs to only answer a few questions about their work history and

experience and they almost instantly have a resume.

Quick & Easy

Resume writing software can provide a quick and easy resume. For job

seekers pressed for time, using resume creation software is a perfect choice.

With this option there is no longer any need to labor over a resume, trying to

put the information in the correct places and choose the right wording.

Resume writing software practically does all the work for the job seeker.

Affordable

Resume writing software, such as a free resume maker, can be irresistible.

The idea of obtaining a resume that is quick, easy and free can be hard to

pass up, particularly when professional resume writers charge a fee to craft a

personalized resume.

Guarantee

One further benefit of using on-line software is that it is instantly available

as a download onto your computer. In common with most on-line products

they normally have a no questions asked 100% money back guarantee.


9/31

4. SYSTEM DESIGN

System design consist of a following,

1. Database Design2. Input Design

3. Output Design

INTRODUCTION

It is where the approach to the creation of the new system. It provides

understanding of the procedural details necessary for implementing the system. It

involves first logical design and then the physical construction of the system.

Logical design is like the blue print. Physical design produces software, files and

working system. Th efundamental objective in the design is that it ensures very

attractive and user friendly.

4.1 DATABASE DESIGN

The goal of a relational database design is to generate a set of relations

that allows storing information easily. The database is designed in the relational

model in which the data are organized into entries and relations between them.

All the tables designed for the system conform to the first, second ad third

normal forms.

Stored procedures are used to save a significant amount of processing at

execution time and client execution requests use the network more

efficiently.Appropriate integrity constraints such as domain, entity, integrity,

referential integrity and check conditions are used whenever possible.


10/31

4.1 INPUT DESIGN

Input design is the link between the information system and the users and

those steps that are necessary to put transaction data in to a usable form for

processing data entry. The activity of putting data into the computer for processing

can be activated by instructing the computer to read data from a written printed

document or it can occur by keying data directly into the system. The designs of

input focusing on controlling the amount of input required controlling the errors,

avoid delay extra steps, and keeping the process simple. This system has

individual form for administrator and customer.

4.2 OUTPUT DESIGN

Designing computer should proceed in well thought out manner. The term

output means any information produced by the information system whether

printed or displayed. When analyst design computer out put they identified the

specific output that is needed to meet the requirement. Computer is the most

important source of information to the users. Output design is a process that

involves designing necessary outputs that have to be used by various users

according to requirements. Efficient intelligent output design should improve the

system relationship with the user and help in decision making. Since the reports

are directly required by the management for taking decision and to draw the

conclusion must be simple, descriptive and clear to the user. Options for outputs

and forms are given in the system menus.

When designing the output, system analyst must accomplish the following:

Determine the information to present.

Decide whether to display, print, speak the information and select the

output medium

Arrange the information in acceptable format.


11/31

5. SYSTEM DEVELOPMENT

The .NET Framework is a new computing platform that simplifies

application development in the highly distributed environment of the

Internet. The .NET Framework is designed to fulfill the following

objectives:

To provide a consistent object-oriented programming environment

whether object code is stored and executed locally, executed locally

but Internet-distributed, or executed remotely. To provide a code-execution environment that minimizes software

deployment and versioning conflicts.

To provide a code-execution environment that guarantees safe

execution of code, including code created by an unknown or semi-

trusted third party.

To provide a code-execution environment that eliminates the

performance problems of scripted or interpreted environments.

To make the developer experience consistent across widely varying

types of applications, such as Windows-based applications and Web-

based applications.

To build all communication on industry standards to ensure that code

based on the .NET Framework can integrate with any other code.


12/31

ADO.NET Overview

ADO.NET is an evolution of the ADO data access model that directly

addresses user requirements for developing scalable applications. It was

designed specifically for the web with scalability, statelessness, and XML in

mind.

ADO.NET uses some ADO objects, such as the Connection and

Command objects, and also introduces new objects. Key new ADO.NET

objects include the DataSet, DataReader, and DataAdapter.

The important distinction between this evolved stage of ADO.NET

and previous data architectures is that there exists an object -- the DataSet --

that is separate and distinct from any data stores. Because of that, the

DataSet functions as a standalone entity. You can think of the DataSet as an

always disconnected recordset that knows nothing about the source or

destination of the data it contains. Inside a DataSet, much like in a database,

there are tables, columns, relationships, constraints, views, and so forth.

A DataAdapter is the object that connects to the database to fill the

DataSet. Then, it connects back to the database to update the data there,

based on operations performed while the DataSet held the data. In the past,

data processing has been primarily connection-based. Now, in an effort to

make multi-tiered apps more efficient, data processing is turning to a

message-based approach that revolves around chunks of information. At the

center of this approach is the DataAdapter, which provides a bridge to

retrieve and save data between a DataSet and its source data store. It

accomplishes this by means of requests to the appropriate SQL commands

made against the data store.


13/31

The XML-based DataSet object provides a consistent programming

model that works with all models of data storage: flat, relational, and

hierarchical. It does this by having no 'knowledge' of the source of its data,

and by representing the data that it holds as collections and data types. No

matter what the source of the data within the DataSet is, it is manipulated

through the same set of standard APIs exposed through the DataSet and its

subordinate objects.

While the DataSet has no knowledge of the source of its data, the

managed provider has detailed and specific information. The role of the

managed provider is to connect, fill, and persist the DataSet to and from data

stores. The OLE DB and SQL Server .NET Data Providers

(System.Data.OleDb and System.Data.SqlClient) that are part of the .Net

Framework provide four basic objects: the Command, Connection,

DataReader and DataAdapter. In the remaining sections of this document,

we'll walk through each part of the DataSet and the OLE DB/SQL Server

.NET Data Providers explaining what they are, and how to program against

them.


14/31

Commands

Commands contain the information that is submitted to a database,

and are represented by provider-specific classes such as SQLCommand. A

command can be a stored procedure call, an UPDATE statement, or a

statement that returns results. You can also use input and output parameters,

and return values as part of your command syntax. The example below

shows how to issue an INSERT statement against the Northwind database.

DataReaders

The DataReader object is somewhat synonymous with a read-

only/forward-only cursor over data. The DataReader API supports flat as

well as hierarchical data. A DataReader object is returned after executing a

command against a database. The format of the returned DataReader object

is different from a recordset. For example, you might use the DataReader to

show the results of a search list in a web page.

DataSets and DataAdapters

DataSets

The DataSet object is similar to the ADO Recordset object, but more

powerful, and with one other important distinction: the DataSet is always

disconnected. The DataSet object represents a cache of data, with database-

like structures such as tables, columns, relationships, and constraints.

However, though a DataSet can and does behave much like a database, it is

important to remember that DataSet objects do not interact directly with

databases, or other source data. This allows the developer to work with a

programming model that is always consistent, regardless of where the source

data resides. Data coming from a database, an XML file, from code, or user

input can all be placed into DataSet objects. Then, as changes are made to


15/31

the DataSet they can be tracked and verified before updating the source data.

The GetChanges method of the DataSet object actually creates a second

DatSet that contains only the changes to the data. This DataSet is then used

by a DataAdapter (or other objects) to update the original data source.

The DataSet has many XML characteristics, including the ability to

produce and consume XML data and XML schemas. XML schemas can be

used to describe schemas interchanged via WebServices. In fact, a DataSet

with a schema can actually be compiled for type safety and statement

completion.

DataAdapters (OLEDB/SQL)

The DataAdapter object works as a bridge between the DataSet and

the source data. Using the provider-specific SqlDataAdapter (along with its

associated SqlCommand and SqlConnection) can increase overall

performance when working with a Microsoft SQL Server databases. For

other OLE DB-supported databases, you would use the OleDbDataAdapter

object and its associated OleDbCommand and OleDbConnection objects.

The DataAdapter object uses commands to update the data source after

changes have been made to the DataSet. Using the Fill method of the

DataAdapter calls the SELECT command; using the Update method calls

the INSERT, UPDATE or DELETE command for each changed row. You

can explicitly set these commands in order to control the statements used at

runtime to resolve changes, including the use of stored procedures. For ad-

hoc scenarios, a CommandBuilder object can generate these at run-time

based upon a select statement. However, this run-time generation requires an

extra round-trip to the server in order to gather required metadata, so

explicitly providing the INSERT, UPDATE, and DELETE commands at

design time will result in better run-time performance.


16/31

SQL SERVER

DATABASE

A database management, or DBMS, gives the user access to their data

and helps them transform the data into information. Such database

management systems include dBase, paradox, IMS, SQL Server and SQL

Server. These systems allow users to create, update and extract information

from their database.

A database is a structured collection of data. Data refers to the

characteristics of people, things and events. SQL Server stores each data

item in its own fields. In SQL Server, the fields relating to a particular

person, thing or event are bundled together to form a single complete unit of

data, called a record (it can also be referred to as raw or an occurrence).

Each record is made up of a number of fields. No two fields in a record can

have the same field name.

During an SQL Server Database design project, the analysis of your

business needs identifies all the fields or attributes of interest. If your

business needs change over time, you define any additional fields or change

the definition of existing fields.

SQL Server Tables

SQL Server stores records relating to each other in a table. Different

tables are created for the various groups of information. Related tables are

grouped together to form a database.

Primary Key

Every table in SQL Server has a field or a combination of fields that

uniquely identifies each record in the table. The Unique identifier is called


17/31

the Primary Key, or simply the Key. The primary key provides the means to

distinguish one record from all other in a table. It allows the user and the

database system to identify, locate and refer to one particular record in the

database.

Relational Database

Sometimes all the information of interest to a business operation can

be stored in one table. SQL Server makes it very easy to link the data in

multiple tables. Matching an employee to the department in which they work

is one example. This is what makes SQL Server a relational database

management system, or RDBMS. It stores data in two or more tables and

enables you to define relationships between the table and enables you to

define relationships between the tables.

Foreign Key

When a field is one table matches the primary key of another field is

referred to as a foreign key. A foreign key is a field or a group of fields in

one table whose values match those of the primary key of another table.

Referential Integrity

Not only does SQL Server allow you to link multiple tables, it also

maintains consistency between them. Ensuring that the data among related

tables is correctly matched is referred to as maintaining referential integrity.

Data Abstraction

A major purpose of a database system is to provide users with an

abstract view of the data. This system hides certain details of how the data

is stored and maintained. Data abstraction is divided into three levels.

Physical level: This is the lowest level of abstraction at which one describes

how the data are actually stored.


18/31

6. TESTING AND IMPLEMENTATION

6.1 SYSTEM TESTING

Testing Methodologies

Testing is generally done at two levels - Testing of individual

modules and testing of the entire system (System testing). During systems

testing, the system is used experimentally to ensure that the software does

not fail, i.e., that it will run according to its specifications and in the way

users expect. Special test data are input for processing, and the results

examined. A limited number of uses may be allowed to use the system so

analysis can see whether they use it in unforeseen ways. It is preferable to

discover any surprise before the organization implements the system and

depends on it.

Testing is done throughout systems development at various stages (not

just at the end). It is always a good practice to test the system at many

different levels at various intervals, that is, sub systems, program modules as

work progresses and finally the system as a whole. If this is not done, then

the poorly tested system can fail after installation. As you may already have

gathered, testing is very tedious and time-consuming job. For a test to be

successful the tester, should try and make the program fail. The tester maybe

an analyst, programmer, or specialist trained in software testing. One should

try and find areas in which the program can fail. Each test case is designed

with the intent of finding errors in the way the system will process it.

Through testing of programs do not guarantee the reliability of systems. It is

assure that the system runs error free.


19/31

Unit Testing

This involves the tests carried out on modules programs, which make

up a system. This is also called as a Program Testing. The units in a system

are the modules and routines that are assembled and integrated to perform a

specific function. In a large system, many modules at different levels are

needed. Unit testing focuses on the modules, independently of one another,

to locate errors. The programs should be tested for correctness of logic

applied and should detect errors in coding.

For example in the OBSE system, feeding the system with all

combinations of data should test all the calculations. Valid and invalid data

should be created and the programs should be made to process the data to

catch errors. In the OBSE system, the Employee no: consists of three digits,

so during testing one should ensure that the programs do not accept anything

other than a three-digit code for the employee no. Another e.g. for valid and

invalid data check is that, in case three digit no is entered during the entry oftransaction, and that number does not exit in the master file, or if the

number entered is an exit case, then the programs should not allow the entry

of such cases. All dates that are entered should be validated. No program

should accept invalidates. The checks that are needed to be incorporated are:

in the month of Feb the date cannot be more than 29. For the months having

days one should not be allowed to enter 31. All conditions present in the

program should be tested. Before proceeding one must make sure that all the

programs are working independently.

System Testing


20/31

When unit tests are satisfactorily concluded, the system, as a complete

entity must be tested. At this stage, end users and operators become actively

involved in testing. While testing one should also test to find discrepancies

between the system and its original objective, current specifications and

systems documentation.

For example, one module may expect the data item for employee

number to be numeric field, while other modules expect it to be a character

data item. The system itself may not report this error, but the output may

show unexpected results. A record maybe created and stored in one module,

using the employee number as a numeric field. If this is later sought on

retrieval with the expectation that it will be a character field, the field will

not be recognized and the message requested record not found would not be

displayed.

System testing must also verify that file sizes are adequate and their

indexes have been built properly. Sorting and rendering procedures assumed

to be present in lower level modules must be tested at the systems level to

see that they in fact exist and achieve the results modules expect.

Output Testing

After performing the validation testing, the next step is output testing

of the proposed system, since no system could be useful if it does not

produce the required output in the specified format. The outputs generated or

displayed by the system under consideration are tested by asking the users

about the format required by them. Hence the output format is considered in

2 ways one is on screen and another in printed format.


21/31

Validation Checking

Validation checks are performed on the following fields.

Text Field

The text field can contain only the number of characters lesser than or

equal to its size. The text fields are alphanumeric in some tables and

alphabetic in other tables. Incorrect entry always flashes and error message.


22/31

Numeric Field

The numeric field can contain only numbers from 0 to 9. An entry of

any character flashes an error messages. The individual modules are checked

for accuracy and what it has to perform. Each module is subjected to test

run along with sample data. The individually tested modules are integrated

into a single system. Testing involves executing the real data information is

used in the program the existence of any program defect is inferred from the

output. The testing should be planned so that all the requirements are

individually tested.

6.2 IMPLEMENTATION

Implementation Procedures

After proper testing and validation, the question arises whether the

system can be implemented or not. Implementation includes all those

activities that take place to convert from old system to new. The new system

may be totally new replacing an existing manual or automated system, or it

may be a major modification to an existing system. In other case, proper

implementation is essential to provide a reliable system to meet organization

requirements.

User Training

A well-designed system, if not operated and used properly could fail.

Training the users is important, as if not done well enough could prevent the

successful implementation of an information system. Through the systems

development life cycle the user has been involved. By this stage the analyst


23/31

should possess an accurate idea of the users they need to be trained. They

must know what their roles will be, how they can use the system and what

the system will do and will not do. Both system operators and users need

training. During their training, they need to be given a trouble-shooting list

that identifies possible problems and identifies remedies for the problem.

They should be advised of the common mal functions that may arise and

how to solve them.

Operational Documentation

Once the implementation plan is decided, it is essential that the user of

the system is made familiar and comfortable with the environment.

Education involves right atmosphere & motivating the user. A

documentation providing the whole operations of the system is being

developed. The system is developed in such a way that the user can work

with it in a well consistent way. The system is developed user friendly so

that the user can work the system from the tips given in the application

itself. Useful tips and guidance is given inside the application itself to help

the user. Users have to be made aware that what can be achieved with the

new system and how it increases the performance of the system. The user of

the system should be given a general idea of the system before he uses the

system.

System Maintenance

A system should be created whose design is comprehensive and

farsighted enough to serve current and projected user for several years to


24/31

come. Part of the analysts expertise should be in projecting what those

needs might be in building flexibility and adaptability into the system.

The better the system design, the easier it will be to maintain and the

maintenance costs is a major concern, since software maintenance can prove

to be very expensive. It is important to detect software design errors early

on; as it is less costly than if errors remain unnoticed until maintenance is

necessary. Maintenance is performed most often to improve the existing

software rather than to respond to a crisis or system failure. As user

requirements change, software and documentation should be changed as part

of the maintenance work.

Maintenance is also done to update software in response to the change

made in an organization. This work is not as substantial as enhancing the

Software, but it must be done. The system could fail if the system is not

maintained properly.


25/31

7. CONCLUSION

The new computerized system was found to be much faster and

reliable and user friendly then the existing system. The system has beendesigned and developed step by step and tested successfully. It eliminates

the human error that are likely to creep in the kind of working in which a

bulk quantity of data and communications as to be processed.

None of the products examined proved any better than the current

method for ease of use or customization, and some would not allow as much

information as the current model rsum contains. They do, however, offer

several document templates to choose from, which would allow students to

have some greater control over their rsums appearance without having to

manipulate large sections of information in Word files (e.g., students with

more job experience could more easily place that section before the

education section). However, they dont allow users to customize sections

within the rsum builder interfaces

This system when implemented would give an active online status of

the remote things happening at the remote site. This would not only benefit

the organization of misuse of time or other resources of the concern but also

give the management to take appropriate decisions based on the remote

informations provided.


26/31

7. SCOPE FOR FURTHER DEVELOPMENT

The application developed is designed in such a way that any

further enhancements can be done with ease. The system has the

capability for easy integration with other systems. New modules

can be added to the existing system with less effort.

Software restructuring is carried out. Software restructuring

modifies source code in an effort to make it amenable to future

changes. In general, restructuring does not modify the over all

program architecture. It tends to focus on the design details of

individual modules and can local data structure defined within

modules.

Resume Manager completely automates the entire resume handling

process, which increases efficiency and productivity of your work and

saves money for your company. Because you stay focused on finding the

right people instead of worrying about all the paperwork, you can be sure

you have chosen the best candidates available! Even if you prefer to do the

important work by hand.


27/31

8 BIBLIOGRAPHY

VB.NET A Beginners Guide, Dave Mercer,

TATA McGRAW-Hill EDITION.

MCAD/MCSD Training Kit Developing Web Applications with

Microsoft Visual Basic .NET and Microsoft Visual C# .NET.

PUBLISHED BY

Microsoft Press - A Division of Microsoft Corporation

VB.NET DATABASE PROGRAMMING

WEEKEND CRASH COURSE

JASON BUTLER, TONY CAUDILL

Microsoft ADO .NET Step by Step,

by Rebecca M. Riordan ISBN: 0735612366, Microsoft Press 2002

ASP.NET Unleashed, Second Edition, By Stephen Walther

http://www.developer.com/net/asp/article.php/3096831

http://www.aspnetemail.com/Examples.aspx

Advanced SQL Database Programmer Handbook

Donald K. Burleson, Joe Celko, John Paul Cook, Peter Gulutzan
http://www.developer.com/net/asp/article.php/3096831http://www.aspnetemail.com/Examples.aspxhttp://www.developer.com/net/asp/article.php/3096831http://www.aspnetemail.com/Examples.aspx


28/31

9. APPENDIX

SCREEN LAYOUT


29/31


30/31


31/31

Documents

Final Document Resume Builder