reflection paper

JOB PORTAL

Login

System

Registrtion

Administrator

Job Apply

Save job

Search job

Block company

Block category

Block user

View C-Profile

Resume dev.

Response boost

Add category

Set pacage

Post job

Candidate

Company

«uses»

«uses»

«uses»

«uses»

«uses»

«uses»

«uses»

«uses»

«uses»

«uses»

«uses»

«uses»

«uses»

«uses»

«uses»

«uses»

«uses»

«uses»

Data Dictionary/Database Files

A Data Dictionary is simply a record of data about data. It may be manually compiled or it may be a fully automated package. All definitions of elements in the system – data flows, processes, and data stores – are stored in Data Dictionary.

Data Dictionary is an integral component of structured analysis. Data Dictionary provides additional information about the system.

A Data Dictionary is a catalog- a repository --- of the elements in a system. These elements center on data and the way they are structured to meet user requirements and organization needs. The major elements are data flows, data stores and processes. The data Dictionary stores details and descriptions of these elements

The Data Dictionary is the only common source of definitions for users and investigators alive. It is the single source of answer of answers to all questions regarding the format and context of the data sets used in the system.

Data Elements

The most fundamental level of data is the data element. Data elements are building blocks for all other data in the system like Data Names, Data Description, Aliases, Length, and Data Values.

Data structures

The Data Structure is a set of data items that are related to one another and that collectively describe a component in the system.

· Job Portal

LOGIN

Field name	Data type	Constraint	Description
username	char(20)	Primary key	Name of user
password	varchar2(12)	-	Password of user
Role	char(10)	-	Admin/ HR /Candidate

CANDIDATE

Field name	Data type	Constraint	Description
candidate_id	number	Primary key	ID of Candidate
username	char(15)	Foreign key	Username
que_id	number	Foreign key	ID of Question
Ans	varchar2(15)	-	Answer
profile_date	date	-	Date of Profile
first_name	char(15)	-	First name of user
middle_name	char(15)	-	Middle name of user
last_name	char(15)	-	Last name of user
Gender	char(6)	-	Gender
Dob	date	-	Date of birth
contact_no	number(15)	-	Contact no
email_id	varchar2(30)	-	Email ID
profile_status	char(5)	-	Active / Inactive

CANDIDATE_EDUCATION

Field name	Data type	Constraint	Description
candidate_id	number	Primary key	ID of Candidate
perc11	number(4,2)	-	11th Percentage
perc12	number(4,2)	-	12th Percentage
graduation	varchar2(10)	-	Graduation
institute_grad	varchar2(25)	-	Institute of Graduation
perc_grad	number(4,2)	-	Graduation %
post_grad	varchar2(10)	-	Post-graduation
institute_post_grad	varchar2(25)	-	Institute of Post-grad
perc_post_grad	number(4,2)	-	Post-graduation %
dr_phd	varchar2(10)	-	Doctorate / PhD
institute_dr_phd	varchar2(25)	-	Dr. / PhD Institute
perc_dr_phd	number(4,2)	-	Dr. / PhD %
certification	varchar2(10)	-	Certification Course

CANDIDATE_PROFESSIONAL

Field name	Data type	Constraint	Description
candidate_id	number	Primary key	ID of Candidate
candidate_prof_id	number	-	ID of Professional
area_id	number	Foreign key	ID of area
Expr	varchar2(15)	-	How much Experience
Salary	varchar2(20)	-	Salary
Industry	varchar2(25)	-	Work Industry
ind_role	varchar2(25)	-	Role in industry
Skills	varchar2(50)	-	Key Skills

CANDIDATE_ADDRS

Field name	Data type	Constraint	Description
candidate_id	Number	Foreign key	ID of Candidate
candidate_addrs_id	Number	Primary key	ID of Address
candidate_addrs	varchar2(50)	-	Local address
city_id	Number	Foreign key	ID of City

COMPANY

Field name	Data type	Constraint	Description
company_id	Number	Primary key	ID of Company
company_name	varchar2(20)	-	Name of Company
contact_person	varchar2(25)	-	Contact-person Name
company_contact	number(15)	-	Contact number
company_email_id	varchar2(30)	-	Company email id
company_details	varchar2(200)	-	Details of Company
company_status	char(10)	-	Active / Inactive

COMPANY_BRANCH_ADDRS

Field name	Data type	Constraint	Description
company_id	Number	Foreign key	ID of Company
branch_id	Number	Primary key	ID of Branch
area_id	Number	Foreign key	ID of Area
branch_address	varchar2(50)	-	Local address
city_id	Number	Foreign key	ID of City

PACKAGE

Field name	Data type	Constraint	Description
package_id	Number	Primary key	ID of Package
package_cost	Number	-	Total or Per-resume
no_jobpost	Number	-	No. of Job-postings

COMPANY_PACKAGE

Field name	Data type	Constraint	Description
company_package_id	Number	Primary key	ID-Company package
company_id	Number	Foreign key	ID of Company
package_id	Number	Foreign key	ID of Package
package_date	Date	-	Date of selection

JOB_APPLIED

Field name	Data type	Constraint	Description
applied_id	Number	Primary key	ID of Applied job
candidate_id	Number	Foreign key	ID of Candidate
jobpost_id	Number	Foreign key	ID of Vacancy
resume_id	Number	Foreign key	ID of Resume
applied_date	Date	-	Date when applied

JOB_POST

Field name	Data type	Constraint	Description
jobpost_id	Number	Primary key	ID-Company package
company_id	Number	Foreign key	ID of Company
job_title	varchar2(20)	-	Title of Job
area_id	Number	Foreign key	ID of Area
branch_id	Number	Foreign key	ID of Branch
post_id	Number	Foreign key	ID of Post
no_vacancy	Number	-	Number of vacancy
start_date	Date	-	Starting date
end_date	Date	-	Ending date
expr_req	varchar2(15)	-	Experience Requirement
skills_req	varchar2(30)	-	Skills Requirement
edu_req	varchar2(10)	-	Education Requirement
basic_req	varchar2(30)	-	Basic Requirement
salary_given	varchar2(20)	-	Salary Given
jobpost_status	char(10)	-	Active/ Outdate / Full

COMPANY_BLOCK

Field name	Data type	Constraint	Description
ccb_id	number	Primary key	ID of Blocking
candidate_id	number	Foreign key	ID of Candidate
company_id	number	Foreign key	ID of Company
block_date	date	-	Date when blocked
block_status	char(10)	-	Active / Inactive

POST

Field name	Data type	Constraint	Description
post_id	number	Primary key	ID of Area
area_id	number	Foreign key	ID of Area
post_name	char(10)	-	Name of the Post

CATEGORY

Field name	Data type	Constraint	Description
category_id	number	Primary key	ID of Category
category_name	char(10)	-	Name of Category
category_status	char(10)	-	Active / Inactive

AREA

Field name	Data type	Constraint	Description
area_id	number	Primary key	ID of Area
category_id	number	Foreign key	ID of Category
area_name	varchar2(10)	-	Name of the area

QUESTION

Field name	Data type	Constraint	Description
que_id	number	Primary key	ID of Question
Que	varchar2(50)		Full Question

COUNTRY

Field name	Data type	Constraint	Description
country_id	number	Primary key	ID of Country
country_name	char(20)	-	Name of the Country
country_status	char(10)	-	Active / Inactive

STATE

Field name	Data type	Constraint	Description
state_id	number	Primary key	ID of State
state_name	char(20)	-	Name of the State
country_id	number	Foreign key	ID of the Country
state_status	char(10)	-	Active / Inactive

CITY

Field name	Data type	Constraint	Description
city_id	number	Primary key	ID of City
city name	char(20)	-	Name of the City
state_id	number	Foreign key	ID of the State
dist_status	varchar2(10)	-	Active / Inactive

RESUME

Field name	Data type	Constraint	Description
resume_id	number	Primary key	ID of Resume
resume headline	varchar2(30)	-	Headline of Resume
candidate_id	number	Foreign key	ID of Candidate

PAGES

Field name	Data type	Constraint	Description
page_id	number	Primary key	ID of Page
page title	varchar2(20)	-	Title of Page
page_discription	varchar2(500)	-	Description

· Functional and Behavioral modeling

DFD

Administrator DFD

2.8 Student DFD

2 DFD

Main module of System

Jobseeker Section

Registration Module:

· User enter account details, contact details, and resume summary, education details, upload resume information to become a member.

· Free resume posting during the registration.

· User can easily select the job mail alert and news letter alert during the registration itself.

· Activation emails send it to the user after registration.

Login Module

· User easily login with their username and password.

Forget Password Module

· User receive mail for forget password

Home Page Module

· Home town search - user search the job in his / her home town

· Search agent - user can create the agent and search job by any one search agent

· User can block and unblock the companies which one company he / she want to block or unblock Set profile visibility of his / her profile.

· User can set their resume either active or inactive.

· Change password - user change new password into new password.

· User can preview, edit, delete and print their resume.

· User can update the profile

Search job Module

· Quick job search - Enter any keyword to search jobs.

· Advance job search - Enter keyword or experience or location or functional area to search jobs.

· Jobs search by role - Selecting the category or subcategory to search jobs.

· Job search by industry - Choose any one industry to search jobs.

· My Saved Jobs - User can view their saved jobs.

Saved Job Module

· User can save the jobs when they are searching the jobs in the site.

· User can apply the jobs from the saved job list.

Employer Section

Registration Module

· User enters their account information, company details, and primary contact details.

· User can easily select the job mail alert and news letter alert during the registration itself.

· Activation emails send it to the user after registration

Login Module

· User easily login with their username and password.

Forget Password Module

· User receive mail for forget password

Profile

· Profile view

Edit profile

· Update contact details - Name, Gender, DOB, Country and Contact Details

· Update resume summary - Experience, key skills, functional area, industry, resume headline.

· Update education details - Qualification, specialization and year of passing.

Find Candidate

· Find the job seekers who are apply for the posting jobs.

· View their responses.

· Recruiter can send email to the job seekers.

· Recruiters create the common mail message before sending the email.

· Recruiter can download the job seekers resume who are all apply for the job.

· Resume access

Recruiters are searching the application of the user.

· Enter the detail about job position, functional area, industry type, keyword, experience, qualification, location, country, and order by date.

· If the employer or recruiter was not order any package it shows the buy package link

· After the employers or recruiters are buying the package then only they can search the job seeker resumes.

Post job

· Post the job for recruitment.

· For posting the job the employer should order the package.

· If the user was not buying the pack they can’t post any single job.

Database access

· Database accessing has two packages.

· By choosing any one they got the database accessing.

Job posting

· Job posting have four packages.

· By choosing any one they got the permission for how many jobs the employer or recruiter can post.

· Based on the package they have some validity. Up to the validity the employer can post the job after that they have to buy the package for post job.

Featured employer

· For featured employer have two types of packages.

· By choosing any one they got the information about the featured employers in their home page.

Posted jobs

· Posted jobs are listed.

· The employer can edit the jobs.

· Delete jobs.

· View jobs.

ADMIN SECTION:

Manage site:

· Administrator

· Maintain the administrator username and password.

· Add username and password.

· Edit and delete password. Functional Area

· Add functional area

· Edit functional area

· Remove functional area Industry Type

· Add industry type

· Edit industry type

· Remove industry type Home Page Ads

· Add home page ads.

· Edit ads

· Remove ads

· Maintain active and inactive ads

Enquires

· Queries or comments are posted by user.

· Manage the admin enquiries

· Reply queries or comments to the user.

· Delete enquiries.

· Edit about Us

· Edit the about us information

· Edit here in user view these information is update well.

· Edit Terms & conditions

· Edit the terms and condition information.

· Admin can edit this information and in user view these

Information will update.

· Edit Copyright

· Edit the copy right information.

· Admin can edit this information and in user view these

· Information will update.

Price settings:

· Database access price

· Add product

· Edit product

· Remove product

· These updates are viewed in the payment package details in user view section.

Job Postings

· Add product.

· Edit product.

· Remove product.

· Maintains the product name, days allowed, number jobs, price amount. The admin update and delete and add these details.

Featured Employer

· Add product.

· Edit product.

· Remove product.

· Maintains the product name, days allowed, number jobs, price amount. The admin update and delete and add these details.

Newsletters:

· Job seekers

· Send the news letter about the jobs site to the job seekers.

Recruiters

· Send the news letter about the jobs site to the recruiters.

Manage seekers:

· Users Address

· Maintains the user address information.

User’s profile

· Maintains the user profile information.

· Delete the user profile.

· Make the user profile as an active or inactive profile.

· Based on that status when the recruiter search the resumes,

· If the profile status was active recruiter can view their user profile otherwise they can't view their profile information.

· When the admin is going to make the profile status either active or inactive admin have to enter the reason for change the profile status.

· Reason will send it to the user.

· Manage employers:

Featured Employer

· Employer or recruiter buys the package for feature employer.

· Admin Maintain the featured logo details.

· Admin Mark the feature logo status either active or inactive

· Before mark as active or inactive the admin contact the recruiter to send the format of images.

· Based on the admin status it will view in the home page as a featured employer list.

List of Members

· Maintains the database access members

· Maintain the standard employers.

· Maintain the featured employers.

· Maintain the list of premium employers.

· Maintain the list of club members.

Employers Address

· Maintain the employers address details.

Employers Profile

· Maintain the employers profile details

· Admin can delete the employers

· Admin can mark the employer either active or inactive.

· Admin can view employer's profile.

Reports:

· CV's Search-Nationality

· Maintain the CV's by nationality that is country vice.

· List the county and members count.

· Export these details in the excel format.

CV's Search-Industry

· Maintain the CV's by industry that is Industry vice.

· Maintain these details in the excel format.

Members Reports

· Maintain the CV's by nationality that is country vice.

· Maintain these details in the excel format.

Product Features

Manage Logo

· Admin Can Change Logo from Admin Panel

· Admin Also Upload New Logo for Website

Manage Site Information

· Admin can Change Website Name

· Admin can Website Path

· Admin can Manage Email Address

Manage Site Content

· Admin can Change Site Content

· Admin can Change Contact Information

· SYSTEM DESIGN

DATABASE DESIGN/DATA STRUCTURE DESIGN:

Tables and Relationships: Database Tables’ Names and Description

Table Name	Table Description
Login	Login Details
Candidate	Basic information about Candidates
Candidate_education	Educational details about the candidate
Cadidate_Professonal	Professional details about the candidate.
Candidate_addrs	Address about Candidate
Company	Company details
Company_Branch_add	Branch details of company
Package	Package decided by admin
Company_package	Packages held by companies
Job_Applied	Applied jobs by candidates
Job_post	Posted jobs
Post	Post (designation)
Category	Categories.
Area	Areas
Sate	States
Country	Countries
Questions	Security questions
City	cities
Resume	Resumes of candidates

Relationships:

After logged in as an administrator, one can see the all details of jobseeker & recruiter placed by user and all registered user the administrator can also edit the items and the categories.

Logical Description of Data:

Whenever any user puts their information, the data provided by him/her goes to the _master table.

SYSTEM PROCEDURAL DESIGN

Methods for Pseudo Code

Pseudo-code

· intuitive/informal notational system

· Good starting point for representing algorithms in any high-level programming language.

Pseudo code is a kind of structured English for describing algorithms. It allows the designer to focus on the logic of the algorithm without being distracted by details of language syntax.  At the same time, the pseudo code needs to be complete.  It describes the entire logic of the algorithm so that implementation becomes a rote mechanical task of translating line by line into source code.

In general the vocabulary used in the pseudo code should be the vocabulary of the problem domain, not of the implementation domain.  The pseudo code is a narrative for someone who knows the requirements (problem domain) and is trying to learn how the solution is organized.

The "structured" part of pseudo code is a notation for representing six specific structured programming constructs: SEQUENCE, WHILE, IF-THEN-ELSE, REPEAT-UNTIL, FOR, and CASE. Each of these constructs can be embedded inside any other construct. These construct represent the logic, or flow of control in an algorithm.

It has been proven that three basic constructs for flow of control are sufficient to implement any "proper" algorithm.

SEQUENCE is a linear progression where one task is performed sequentially after another.

WHILE is a loop (repetition) with a simple conditional test at its beginning.

IF-THEN-ELSE is a decision (selection) in which a choice is made between two alternative courses of action.

Although these constructs are sufficient, it is often useful to include three more constructs:

REPEAT-UNTIL is a loop with a simple conditional test at the bottom.

CASE is a multiway branch (decision) based on the value of an expression. CASE is a generalization of IF-THEN-ELSE.

FOR is a "counting" loop.

Algorithm for Operations

FOR USERS

Step1 Start.

Step2 First of all users will login.

IF username & password = true THEN

Login

ELSE

Display (Error page, sorry login not valid!!!)

ENDIF

Step 3 Login successfully done.

Step 4 The users will go to home page.

Step 5 if the user want to Search Jobs

CASE Search Jobs to be open

Condition: Fill Search Details.

ENDCASE

Step 6 If Search details submitted then continue

Progress of case

Condition 1: view the progress of your case.

Condition 2: Case id

Step 7 End

Access Control & Security

The ASP.NET security model is designed to support single sign on access to application services. Component developers can specify the security requirements of a component at the method level to ensure that only users with appropriate permissions can access specific data operations. While ASP.NET provide programmatic security control, the basic role-based security Mechanism (where groups of users share specific permissions) is specified entirely at application deployment time. This provides both greater flexibility and better security control.

In the project the passwords are given to each user of the Bankers Avenue and to the Admin for their login purpose. This criterion is maintained for the security of the project. For more security purpose we can provide digital signature and any other for more security.

State Transition Diagram

Use state diagrams to demonstrate the behavior of an object through many use cases of the system.  Only use state diagrams for classes where it is necessary to understand the behavior of the object through the entire system.  Not all classes will require a state diagram and state diagrams are not useful for describing the collaboration of all objects in a use case.

SYSTEM ARCHITECTURAL DESIGN

Fundamental design Concepts

A set of fundamental design concepts are evolved over the past three decades. Although the degree of interest in each concept has varied over the years, each has stood the test of time. Each provides the software designer with a foundation from which more sophisticated design methods can be applied. Fundamental design concepts provide the necessary framework for “getting it right”.

Abstraction

Abstraction permits one to concentrate on a problem at some level of generalization without regard to irrelevant low level details, use of abstraction also permits one to work with concepts and terms that are familiar in the problem environment without having to transform them to an unfamiliar structure. Two types of abstraction are there, one is procedural abstraction and data abstraction. A procedural abstraction is a named sequence of instructions that has a specific and limited function. A data abstraction is a named collection of data that describes a data object.

Modularity

Modularity is the single attribute software that allows a program to be intellectually manageable. Software architecture embodies modularity, that is, software is divided into named and addressable components, called modules that are integrated to satisfy problem requirements.

Software Architecture

Software Architecture alludes to “the overall structure of the software and the ways in which that structure provides conceptual integrity for a system”. Control hierarchy also called program structure”, represents the organization of control. The tree structure used to represent the control hierarchy.

Structural Partitioning

The program structure should be partitioned both horizontally and vertically. Horizontal partitioning defines separate branches of the modular hierarchy for each major program function, Vertical partitioning called factoring, suggest that control and work should be distributes top-down in the program architecture. Top level modules should perform control functions and do little actual processing work. Modules reside low in the architecture should be the workers, performing all input, computational, an output tasks.

Data Structure

Data Structure is a representation of logical relationship among individual elements of data. Because the structure of information will invariably affects the final procedural design, data structure is very important as the program structure to the representation of the software architecture. Data structure dictates the organization, methods of access, degree of associatively, and processing alternatives for information. The organization and complexity of a data structure are limited only by the ingenuity of the designer. Scalar item array and linked list are some of the representations of the data structure.

Software Procedure

Program structure defines control hierarchy without regard to the sequence of processing and decisions. Software procedure focuses on the processing details of each module individually. Procedure must provide a precise specification of processing, including sequence of events, exact, decision points, repetitive operations and even data organization / structure. Information hiding suggests that modules be “characterized by design decisions that hide from all others.” In other words, modules should be specified and designed so that information contained within module is inaccessible to other module.

Design is defining a model of the new system and continues by converting this model to a new system. The method is used to convert the model of the proposed system into computer specification. Data models are converted to a database and processes and flows to user procedures and computer programs. Design proposes the new system that meets these requirements. This new system may be built by a fresh or by changing the existing system. The detailed design starts with three activities, database design, user design and program design. Database design uses conceptual data model to produce a database design. User procedure design uses those parts of the DFD outside the automation boundary to design user procedures.

Our system design includes mainly the design of the UML diagrams and constructing the code. The code construction and its description are also given as separate topic. System design may also include the data flow diagrams (DFD) which models a system by using external entities from which data flows to a process, which transforms the data and creates output data flows which go to other processes or external entities or data stores. Stored data may also flow to processes as inputs. The main merit of DFD is that it can provide an overview of what data a system would process, what transformation of data are done, what data are stored and which stored data are used, and where the results flow. The graphical representation of the system makes it a good communication tool between user and an analyst on the one hand and the analyst and the system designer on the other hand.

DFD is mainly used for the representation of the dataflow in the system, which uses database for the storing and retrieving the data. But as our system doesn’t use any database, we haven’t provided any data flow diagram here.

Component Diagram

The component diagram contains components and dependencies.  Components represent the physical packaging of a module of code.  The dependencies between the components show how changes made to one component may affect the other components in the system.

Dependencies in a component diagram are represented by a dashed line between two or more components.  Component diagrams can also show the interfaces used by the components to communicate to each other.

Figure of Component Diagram

Deployment Diagram

Deployment and component diagram combines the features of both diagrams into one diagram.

The deployment diagram contains nodes and connections.  A node usually represents a piece of hardware in the system.  A connection depicts the communication path used by the hardware to communicate and usually indicates a method such as TCP/IP.

Figure of Deployment Diagram

· Implementation Environment

Since we have developed a web application which will definitely be a multi-user application.

Factors Considered

Before developing a internet or intranet website, it is a worthwhile to explore the differences between the two, as well as the issues related to developing the internet and intranet websites. The next two sections, “Internet website development” and “Intranet website development” discuss internet and intranet web development as they related to the following topics:

· Bandwidth availability

One major difference between internet and intranet websites is bandwidth available to users browsing the websites. Most internet users are connected to the internet via relatively slow POTS ( Plain Old Telephone Service ) modem links. Information published on an internet websites should deoptimized for transmittal over low bandwidth internet connections.

· Server Latency:

Server latency must be addressed when deploying a website on the internet. Web servers are no longer used exclusively to publish static content on the internet. Increasingly, web servers are using server side applications to create dynamic content. Although a 486DX2/66 computer can saturate a T1 connection with static content, the situation changes dramatically when the same computer has to process database

query and execute server side applications to fulfill http requests. Use windows NT Performance monitor top detect bottlenecks and other server latency issues. Although the performance of your server can be enhanced by adding more RAM , if CPU usage is high, you will have to upgrade your server to a multiprocessor server.

· SCOPE OF NETWORK:

Taking to account, the scope of your network when setting up your web server. Confidential information that should remain only within your organization should not be published from a server that accessible via internet.

· Platform Compatibility:-

The internet’s consist of a wide variety of hardware platforms and operating systems. When publishing information, platform compatibility should be taken into a account to ensure that information published at your web site is accessible to a wide variety of users. When users need to use a special helper application to view a file at your website, provide URLs for downloading helper application that run on several platforms. At minimum, windows and Macintosh users should be able to view information publish at your website as should those who use widely used flavors of UNIX.

· Security:-

While an internet web site is accessible primarily to select individuals, an internet web site is accessible to millions of users all over the world. Never use clear text passwords to protect sensitive information distributed to and from an internet websites. When distributing sensitive information via the internet, configure your website to encrypt the data. See chapter 20 , “Security” , of volume 2 of this kit(Windows NT internet and intranet administration) for more information about internet security encryption.

· Scope of audience:-

The internet consists of a very diverse group of users. When developing an internet website, consider the scope of your audience. For example, if the targeted audience of your website is not very technically inclined, do not assume your users use the latest version of internet explorer or Netscape navigator, and do not assume that they have helper application installed on their systems.

· SECURITY FEATURES

We have used ASP.NET developer platform. We have used inbuilt security of .Net .

ASP.NET, in conjunction with Microsoft internet information services (IIS) , can authenticate users credential such as names and passwords using any of following authentication methods.

· Windows: basic, digest, integrated windows authentication ( NTLM or Kerberos).

· Forms authentication, in which your login page and manage authentication in your application.

· Microsoft passport authentication.

· Client certificate authentication

ASP.NET controls access to site information by comparing authenticated credential, or representations of them, to NTFS file system permissions or an XML file that lists authorized users, authorized roles (group) or authorized http verbs .

ASP.NET membership gives you a built in way to validate and store user credential. ASP.NET membership therefore helps you to manage user authentication in your web sites. You can use ASP.NET membership with ASP.NET forms authentication or with the ASP.NET login controls to create a complete system for authenticating users.

ASP.NET membership supports facilities for :

· Creating new users and passwords

· Storing membership information like username, password, supporting data in Microsoft SQL server, Active directory or alternative data sotres.

· Authenticating users who visit your website. You can authenticate users programmatically, or you can use the ASP.NET T login controls to create a complete authentication system that requires a little or no code.

· Managing a password, that includes creating, changing, and resetting them. Depending on membership options you choose, the membership system can also provide an automated password-reset system that takes a user supplied questions and response.

· Exposing a unique identification for authenticated users that you can use in your own applications and that also integrates with the ASP.NET personalization and role management system.

· Specifying a custom membership provider, which allows you to substitute your own code to manage membership and maintain membership data in a custom data store.

MEMBERSHIP, ROLES AND USER PROFILES

Although the membership is self – standing feature in ASP.NET for authentication, it can be integrated with ASP.Net role management to provide authorization services for your site. Membership can also be integrated with user profile to provide application specific customization that can be tailored individual user.

How membership works?

To use membership, you must first configure it for your site, in outline you follow these steps:

1. Specify membership options as a part of your website configuration. By default , membership is enabled. You can also specify what membership provider you want to use. (In practical terms, this means that you are specifying what type of database you want to keep membership information). The default provider uses a Microsoft SQL server database. You can also choose to use active directory to store membership information or you can specify a custom provider. For information on membership configuration option that can be specified in web config file for your ASP.Net application.

2. Configure your application to use forms authentication ( as distinct from Windows or Passport authentication). You typically specify that some pages or folders in your application are protected and are accessible only to authenticated users.

3. Define user accounts for membership. You can do this in a variety of ways. You can use the Web Site Administration Tool, which provides a wizard-like interface for creating new users ASP.NET web page where you collect a username and password ( and optionally an e-mail address), and then use a membership function named Create User to create a new user in the membership function.

If you are login controls, they will automatically use the membership system to validate a user. If you have created a login form by hand, you can prompt the user for a user name and password and then call the validate user method to perform the validation. After the user is validated, information about the user can be persisted ( for example, with an encrypted cookie if the user’s browser accepts cookies) using forms authentication. The login controls perform this task automatically. If you have created a login form by hand, you can call methods of the Forms authentication class to create the cookie and write it to the user’s computer. If a user has forgotten his or her password, the login page can call membership functions that help the user remember the password or create a new one.

Each time the user requests another protected page, ASP.NET forms authentication checks, whether the user is authenticated and then either allows the user to view the page or redirects the user to the login page. By default, the authentication cookie remains valid for the user’s session.

After a user has been authenticated, the membership system makes available an object that contains information about the current user. For example, you can get properties of the membership user object to determine the user’s name and e-mail address, when the user last logged into your application, and so on.

An important aspect of the membership system is that you never need to explicitly perform any low level database functions to get or set user information. For example, you create a new user by calling the membership called “Create user method” . The membership system handles the details of creating the necessary database records to store the user information. When you call the Validate user method to check the user’s credentials, the membership system does all the database lookup for you.

Secure Membership Configuration

The membership feature is enabled by default for ASP.NET applications and can not be disabled. The default configuration settings are set to the most secure values. For information about membership configuration settings and their default values, see membership element (ASP.NET Setting Schema). You should set the requires Questions and Answers attribute to true, especially where enable Password Reset or enable Password Retrieval is likewise true.

Secure Membership Configuration

When storing sensitive information in a configuration file for an application, you should encrypt the sensitive values using Protected Configuration. Information that is especially sensitive includes the encryption keys stored in the machine key configuration element and connection strings to a data stored in the connection strings configuration element.

Secure Encryption Keys and Hashing

It is highly recommended that you encrypt user passwords in the membership data source using a password Format attribute set to Hashed or Encrypted, where Hashed is the most secured format. The encryption key values for the specified encryption algorithm are stored in the machine key configuration element. For strong encryption, specify an encryption key and specify the IsolateApps option with key.

You can set the machine configuration on a host server to deny applications from overriding configuration settings. This includes denying the ability for encryption keys to be redefined in the Web. Config file for applications.

Securing Connections to a membership Data Source

Connection Strings

To keep the connection to your database server secure, you should encrypt connection-string information in the configuration using Protected Configuration.

Connecting to SQL server using Integrated Security

You should connect to computers running SQL server using integrated security to avoid the possibility of your connection string being compromised and your user id and password being exposed. When you specify a connection that uses Integrated Security to connect to a computer running SQL server, the membership feature reverts to the identity of the process. You should ensure that the identity of the process running ASP.NET ( for example , the application pool) is the default process account or a restricted user account.

SQL Server Express Worker Process Identity

SQL Server Express 2005 includes a new mode of operation where it can start a worker process running as the identity of the connecting user. This capability is referred to as “ run as faster” mode. Although this mode of operation is suitable for desktop development while using IIS, starting worker processes is not appropriate on Web servers hosting multiple, untrusted customer code bases. Shared hosting servers that contain applications that do not trust each other should explicitly disable the “run as user” functionality. This functionality can be turned off by connecting to the SQL Express instance.

Secure Web Pages that Use Membership

Application pages that work with sensitive data, such as logon pages, should be secured using standard Web-Security mechanisms. These include measures such as using Secured Socket Layer (SSL) and requiring that users be logged on to carry out sensitive operations like updating user information or deleting users.

Additionally, pages should not expose sensitive feature data such as passwords and in some cases user names, in clear text. Ensure that pages that display such information make use of SSL and are available only to authenticated users. Also, avoid storing sensitive feature data in cookies or sending it across insecure connections.

Securing Against Denial of Service Attacks

Methods that perform updates or large search operations can reduce the responsiveness of your membership data source if called concurrently by a number of clients. To reduce exposure to a denial of service attack, restrict access to ASP.NET pages that use methods that perform database updates or searches to administrative users, and expose only ASP.NET pages that provide validation and password management for general use.

· CODING STANDARDS

Rules for building High Performance Code

We have got the following rules for creating high-performance software.

· Know where you are going (understand the objective of the software).

· Make a big map (have an overall program design firmly in the mind, so the various parts of the program and the data structures work well together).

· Make lots of little maps (design an algorithm for each separate part of the overall design).

· Know the territory (understand exactly how the computer carries out each task).

· Know when it matters (identify the portions of your programs where performance matters, and don’t waste your time optimizing the rest).

· Always consider the alternatives (don’t get stuck on a single approach; odds are there’s a better way, if you are clever and inventive enough).

· Know how to turn on the juice (optimize the code as best you know how when it does matter).

Testing

Generally, it has been specified thought for testing that:

“Testing is the critical element of any software quality assurance and represents the ultimate review of specification, design and code generation.”

Software testing has a dual function; it is used to establish the presence of defects in program and it is used to help judge whether or not the program is usable in practice. Thus software testing is used for validation and verification, which ensure that software conforms to its specification and meets the need of the software customer.

Developer resorted Alpha testing, which usually comes in after the basic design of the program has been completed. The project scientist will look over the program and give suggestions and ideas to improve or to correct the design. They also report and give after a program has been created.

Testability:-

Software Testability is simply how easily a computer program can be tasted. The check list that follows provides a set of characteristics that lead to testable software.

· Operability

· Observables

· Controllability

· Decomposability

· Simplicity

· Stability

· Understandability

Following are the attributes of the Good Test

· A good test has a high probability of finding an error.

· A good test is not redundant.

· A good test should be “Best of Breed”.

· A good test would be neither too simple nor too complex.

Compartmentalization:-

In this step we divide the project into number of manageable activities and task like

· Selection Module

· System Admin data module

· Dept. Admin data module

· Store and assign rendered module

· Employee data module

· Task creation data module

· Task allocation and reply data module

· Insert category and pwd Authority module

· Testing Module

· Documentation Module

Interdependency:-

Interdependencies of each compartmentalized activity were then found out. Some tasks must occur in sequence while there are many tasks, which can occur in parallel.

Software Inspection:-

Analyze and check system representations such as the requirements document, design, diagrams and the program source code. They may be applied at all the stages of process.

Figure of Testing Process

Test Plan:-

THE TESTING PROCESS

Developer tests the software process activity such as design, implementation and the requirement engineering. Because, design errors are very costly to repair when the system has been started to operate. Therefore, it is quite obvious to repair them at early stage of the system. So, analysis is the most important process of any project.

REQUIREMENTS TRACTABILITY

As most interested portion is whether the system is meeting its requirements or not, for that testing should be planned so that all requirements are individually tested. Developer checked the output of certain combinations of input, which gives desirable results, or not. Strictly stick to our requirements specifications, give you the path to get desirable results from the system.

TESTED ITEMS

Our tested items are like:

· Data fetching from the database

· Data insertion, updating and deleting in the database

· Form access to particular login

TESTING SCHEDULE

Developer has tested each procedure back to back so that errors and omissions can be found as earliest as possible. Once the system has been developed by fully developer tested it on other machines, which differs in configuration.

TESTING METHODS

Software testing involves executing an implementation of the software which tests data and examining the outputs of the software and its operational behavior to check that it is performing as required.

STATISTICAL TESTING

Statistical testing is used to test the program’s performance and reliability and to check how it works under operational conditions. Tests are designed to reflect the actual user inputs and their frequency.

The stages involved in the static analysis for this system are follows:

· Control Flow Analysis

· Unreachable code

· Unconditional branches into loops

· Data Use analysis

· Variable used before initialization

· Variables declared but never used

· Variables assigned twice but never used between assignments

· Possible array bound violations

· Declared variables

· Interface Analysis

· Parameter type mismatches

· Parameter number mismatches

· Non-usage of the results of function

· Uncalled functions and procedures

· Storage Management Faults

· Data not stored in proper tables

· Data cannot be fetched from proper table

DEFECT TESTING

Defect testing is intended to find inconsistencies between a program and its specifications. These inconsistencies are usually due to the program faults or defects.

UNIT TESTING:-

The Developer carries out unit testing in order to check if the particular module or unit of code is working fine. The unit testing comes at the very basic level as it is carried out as and when the unit of the code is developed or a particular functionality is built.

In this application we test one most important module as task allocation which is as follows:

LOOP TESTING:

Tester has tested the some condition in a code of application. So they test the looping in source code of application for finding miss route or any error or wrong direction of flow in code .

BLACK-BOX TESTING

In black box testing or functional testing, the developer is concerned about the output of the module and software, i.e. whether the software gives proper output as per the requirements or not. In another words, these testing aims to test a program behavior against specification without making any reference to the internal structure of the program or the algorithms used. Therefore, the source code is not needed, and so even purchased modules can be tested. The program just gets a certain input and its functionality is examined by observing the output.

This can be done in the following way:

· Input Interface

· Processing

· Output Interface

The tested program gets certain inputs. Then the program does its job and generates a certain output, which is collected by a second interface. This result is then compared to the excepted output, which has been determined before the test.

WHITEBOX TESTING:

It is also called ‘GLASS BOX’ or ‘STRUCTURAL’ testing. Tester has access to the system design.

· Simple Loops

· Nested Loops

· Concatenated Loops

· Unstructured Loops

· Continuous Loops

They can:

· Examine the design document

· View source code

· Individual path examine

· Logical path examine one time

· Logical decision on their true and false

The intention in white-box testing is to ensure that all possible feasible flow of control path through a sub-program is traversed while the software is under tested. This is not the same as saying that all statements in the sub-program will be executed as it is possible for all statements to be executed but for not all of the possible paths to be traversed. However, the conversed is true; whether all the possible paths through a sub-program are traversed then all statements in sub-programs will necessarily be executed.

When considering the number of possible paths through a sub-program two other factors need to be remembered. The first is that some of the possible paths through a sub-program turnout upon investigation to be non- feasible paths. The second consideration is that the number of possible paths to a sub-program indicated by a flow-graph analysis will indicate the minimum number of paths to ensure complete coverage. This may be less than the total number of paths which are possible when combinations of paths are allowed.

White-box testing is used as an important primary testing approach. Here, code is inspected to see what it does. Tests are designed to exercise the code. Code is tested using code scripts driver etc. which are employe to directly interfaced with and drive the code.

The tester can analyze the code and used the knowledge about the structure of a component to derive the test data.

Advantages of White box testing:-

· As the knowledge of internal coding structure is prerequisite, it becomes very easy to find out which type of input / data can help in testing the application effectively.

· The other advantage of white box testing is that it helps in optimizing the code.

· It helps in removing the extra lines of code, which can bring in hidden defects.

STRUCTURE TESTING:

Developer has done his path testing to exercise every independent execution path through a component or program. If every independent path is executed then all statements in the components must have been executed at least once. The structure of our program is also cheeked.

INTEGRATION TESTING:-

After our individual modules Developer tested out Developer go to the integrated to create a complete system. This integration process involves building the system for problems that arise from component interactions.

Developer has applied top-down strategy to validate high-level components of a system before design and implementations have been completed. Because, our development process started with high-level components and Developer worked down the component hierarchy.

PERFORMANCE TESTING:-

Performance testing is designed to test the runtime performance of the system within the context of the system. These tests Developer performed as module level as developer as system level. Individual modules developers tested for required performance.

CONDITION TESTING:-

Condition testing is a test case design method that exercises the logical conditions contained in a program module. If the condition is incorrect, then as least one part of the condition is incorrect. It may include:

· Boolean variable error

· String index out of Bound error

· Null pointer Assignment

· Input Output Connection Exceptions

· Arithmetic expression error

· Parsing ( conversion) errors

· Image unloaded errors

INTERFACE TESTING:-

Interface testing is integral part of integration testing. Therefore, developer checked for the following.

· Interface misuse

· Interface misunderstanding

Developer examined the code to be tested and explicitly list each call to an external component. In the system, standards tests for various modules have been performed, which are follows.

· All the menu functions and sub menu functions have been checked.

· Validations for all inputs are done.

· All required fields are not left blank.

OBJECT TESTING:-

Object testing is to test object as individual components, which are often larger than single function. Here following activities have taken place.

· Testing the individual operations associated with object.

· Testing individual object classes.

· Testing cluster of objects.

· Testing object oriented systems.

Now we will discuss how testing and debugging is done of this application. Our application can be divided into parts like;

· To make queries to database and retrieve information from it.

· Reduce some memory requirements for the database.

· Maintain database so that unauthorized access can not affect.

Test Cases

Test Object	Inputs	Desired Outputs	Actual Outputs
File upload page of web application.	Zip file including Shape Files and its supporting database files.	Upload Successfully.	Upload Successfully.
Reading data from Text File and placing on the map at proper places.	Text File containing comma separated values.	Read and Placed Successfully.	Read and Placed Successfully.
Viewing Description of particular hotspot.	Text File containing comma separated values.	Viewed Successfully.	Viewed Successfully.

Home Page

Jobseeker’s Home page

New Registration:

Personal Details

Education Details

Professional Details

Jobseeker login

Your active profile

Forgot Password

Search Jobs

Recruiter Login

Recruiter Profile

Administrator Login

View Added Un & Pw

Employer’s Profile

Post Jobs

Admin More

Add Package

Posted Job

Security Question

Company Package

Limitations

· It can run only on windows servers. It is not compatible with LINUX servers.

· It is not cent percent safe from professional hackers.

· Only registered user can buy and sell their items using this website.

Future enhancements

· In future if we get a chance to work on the same project then we like to implement

Improvement for advertisement.

· We also like to make our site more secure.

CONCLUSION AND DISCUSSION

CONCLUSION:

In making of this application, we have learnt that handling files and maps is becoming easy.

Using this application, a user gets a different information and a cost effective solution by visiting unknown place efficiently with all the necessary information regarding to various hotspots the user visits.

Also this application satisfies collaboration objective i.e. “I make it and you use it; u make it and I use it” which is the actual motive of this application.

DISCUSSION:

This application is made for all the users so that user can see the required information at the website also in his/her own hand. So, the main goal of portability and mobility gets achieved by this application.

Further, this application is made using Asp.net and c# which is leading Microsoft application programming technology. Hence, this application is also economic solution for the user.

Now, this is a user friendly website so, any user can use this website to buy and sell different products. Therefore, this application provides collaborative interface to the users.

References

References Books

· C# 2.0 Complete Reference

· ProfessionalASP.NET 2.0

· ASP.NET in 21 days

· ASP.NET Complete Reference

· MSDN 2005

· System Analysis And Design

Internet Sources:

· Naukari.com

· Monster.com

· Shine.com

· www.thejobs4u.com

WORK EXPERIENCE

The past three months have proved to be a great learning experience and have made us aware of the hardships an organization has to deal with while building a software project. We also came across various methods and conventions that an organization follows in order to develop a project. Our project guide was always eager to lend a helping hand during the course of developing our project but made sure that we try solving our difficulties by ourselves first and then only ask her for her help thereby made us self-reliant. she also made sure that we understood every single aspect of the project. We would conclude this by saying that we gained a lot from this training and this knowledge surely will help us in the coming future.

1. Introduction

�

Project Summary

Purpose

Scope

Technology and Literature Review

�

�

2. Project Management

�

Project Planning and Scheduling

Risk Management

Estimation

�

�

3. System Requirements Study

�

User Characteristics

Hardware and Software Requirements

Constraints

�

�

�

Study of Current System

Requirements of New System

Feasibility Study

Requirements Validation

Functions of System

Functional and Behavioral Modeling

�

�

4. System Analysis

Authentication

Administrator

Login

“LEVEL 0”

“LEVEL 0.1”

Regi 1

Authentication

Login

5. System Design

�

Database Design/Data Structure Design

System Procedural Design

Input/output and Interface Design

System Architecture Design

�

Web Server

DB

Web pages

UI

MS SQL Server 2005

6. Implementation Planning & Details

�

Implementation Environment

Program/Modules Specification

Security Features

Coding Standards

Sample Coding

�

�

7. Testing

�

Testing Plan

Testing Strategy

Testing Methods

Test cases and result

�

�

8. User Guide

�

Snap Shots

�

9. Limitation and Future Enhancement

�

Limitations

Future Enhancements

�

10. Conclusion & Discussion

�

Conclusion

Discussion

�

11. Bibliography

�

References

�

12. Work Experience

�

Work Experiences

�