4. ÁLVAR NÚÑEZ CABEZA DE VACA: UN EXPLORADOR CONTROVERTIDO
4.6 El ‘héroe’ que supocruzar la frontera de la ‘Otra Edad’
The project can be used to identify an applicant in the organization. The database would maintain the complete details of the applicant.
Each applicant will be assigned a specific applicant number.
- 17 -
2. SYSTEM REQUIREMENTS
2.1. Software Specification
• Language : C#
• Tool used : asp.net
• Database : Ms-access
• OS : windows vista or 7
• MS visual studio 8
2.2. Hardware Specification
• Server
• Minimum 2Gb Ram processor
- 18 - with a more thorough understanding of the problems, opportunities related to personnel’s. A feasibility study should be conducted to determine the viability of an idea before proceeding with the development of the HUMAN RESOURCE. An important outcome of the preliminary investigation phase of the System Development Life cycle is the determination that the requested system is feasible. The following facets describe the feasibility:
• Operational feasibility
• Technical feasibility
• Financial and Economic feasibility
3.1.1 Operational feasibility
The proposed system is beneficial if and only if it can be turned into an information system that will meet the operating requirements of the organization. This facet of feasibility asks: if the system will work when it is developed and installed and are there any major barriers for system
implementation and many more issues. Before switching to new technology, it mainly examines whether the employees at work are comfortable with organizational framework. The requirements, specifications and design are clearly explained to the employees, so that they conduct their operations successfully. The system up gradations are done in accordance to the application developed or the application is developed in accordance to the available system.
- 19 - 3.1.2 Technical feasibility
The investigation is done mainly keeping in mind this aspect of feasibility.
The analyst has to keep in mind while performing requirement elicitation that the requested work flow is what is feasible technically. Major issues in technical feasibility are to see if the required resources-trained manpower, software and hardware are available or not. The assessment is based on an outline design of system requirements in terms of Input, Processes, Output, Fields, Programs, and Procedures. This can be quantified in terms of volumes of data, trends, frequency of updating, etc. in order to estimate whether the new system will perform adequately or not. Technological feasibility is carried out to determine whether the company has the capability, in terms of software, hardware, personnel and expertise, to handle the completion of the project.
3.1.3 Financial and economic feasibility
As the word denotes that the economic feasibility means more benefit at less expenditure. So every organization must keep in mind while recruitment of the personnel that more people should not be employed than required as it can raise the cost. This thus
becomes a very crucial facet because every industry is governed by finances.
Economic analysis is the most frequently used method for evaluating the effectiveness of a new system. More commonly known as cost/benefit analysis, the procedure is to determine the benefits and savings that are expected from a candidate system and compare them with costs. If benefits outweigh costs, then the decision is made to design and implement the system. An entrepreneur must accurately weigh the cost versus benefits before taking an action.
Cost-based study: It is important to identify cost and benefit factors, which can be categorized as follows:
- 20 - 1. Development costs
2. Operating costs.
This is an analysis of the costs to be incurred in the system and the benefits derivable out of the system.
Time-based study: This is an analysis of the time required to achieve a return on investments. The future value of a project is also a factor.
- 21 -
4 SYSTEM DESIGN
4.1 Module description
We have developed four modules to finally get to the main working site. These four modules work in an integrated environment to give the end used, administrator exactly what he has fired as query.
• User module
• Applicant information module
• Administration module
• Application management module.
4.1.1 User Module
This is the basic structure of the website containing all the necessary information about the company. This has multiple links to other modules which have been created in order to facilitate the user and the administrator.
4.1.2 Applicant Information Module
This is the module designed to update the database. Here the
applicants submit all their professional and personal details regarding the job or internship they seek.
This module saves the details in a specified format so that the
database is updated in an analogous way for every applicant. All the data entered by the applicant is arranged in tables and can be
retrieved as and when required by the administrator.
It also has been incorporated to pay the applicant fees online using the applicant information forms.This information module makes a
- 22 -
pool of applicant available all the time for the HR department of the company making it extremely viable for the heads to cling on to whenever there is a need or vacancy.
4.1.3 Administrative Module
This module is the control panel of the whole site. The administrator has power rights like update, delete, view, restrict other administrator
powers to access the data.
This module manages other module which is used for dynamic updates of the site, changes to be offered in the site etc.
Administrator can access applicants profile any time, can shortlist various applicants according to required need using the appropriate search filters. This module also has been incorporated with feature to retrieve, download and save the resume files from the database.
4.1.4 Application Management Module
This is the module which comes into picture during the finalization process of the application. Who to call for interview, selected candidate to be marked as employed candidate of the company, restoring the information of the applicant in a separate database for future reference.
This module specially acts as a catalyst to the final process of recruitment or internship in the company.
- 23 - 4.2 Data Flow Model : MVC
Figure 2 MVC architecture
System Architecture
Model View Controller Architecture (MVC)
MVC stands for Model, View, and Controller. Here, the Model is the data access layer, the Controller is the business-logic layer, and the View is the interface
- 24 -
layer. This separation means that one can assign different parts to different people, and they don’t necessarily have to interfere with each other’s code.
MVC defines the separation of these three types of objects:
• Model objects hold data and define the logic for manipulating that data.
The model manages the behavior and data of the application domain, responds to requests for information about its state (usually from the view), and responds to instructions to change state (usually from the controller). In event-driven systems, the model notifies observers (usually views) when the information changes so that they can react.
• View objects represent something visible in the user interface, for example a panel or button. The view renders the model into a form suitable for interaction, typically a user interface element. Multiple views can exist for a single model for different purposes. A viewport typically has a one to one correspondence with a display surface and knows how to render to it.
• Controller object acts as a Mediator between the Model and View objects.
A Controller object communicates data back and forth between the Model objects and the View objects. A controller also performs all application specific tasks, such as processing user input or loading configuration data.
There is usually one controller per application or window, in many applications the Controller is tightly coupled to the view.
The controller receives user input and initiates a response by making calls on model objects. A controller accepts input from the user and instructs the model and viewport to perform actions based on that input.
Many applications use a persistent storage mechanism such as a database to store data. MVC does not specifically mention the data access layer because it is understood to be underneath or encapsulated by the model.
- 25 - Advantages :
Here are the main advantages of building applications using MVC framework.
• MVC Framework is built upon a proven MVC design-pattern.
• One of the biggest problems in ASP.NET is HTML size of controls and view state. View state stores all the data rendered and final HTML gets too large. If one is on a slow internet connection, he/she will notice load time delays. This has been taken care in MVC framework. There is no view state concept in MVC framework.
• Client caching is available and by integrating, we can take advantage of it. That makes applications load faster and some of the processing can be done in web browsers. Not only the client site but the server side execution is faster too. The integration with MVC makes it even better and now we can write our code that runs in the browser and takes away load from the server.
• MVC supports multiple views.
• It also supports unit testing as a part of Visual Studio 2008 and 2010 Disadvantages
Some of the key challenges one may face while using MVC Framework are
• It is not easy to understand and code when one needs some
customization. If one is building based on a 100% mature database it works well. But if one has frequent changes in the database, he/she may find it annoying to keep building application again and again. It may also break several other parts of the application.
- 26 - 4.3 Context Level Diagram
Figure 3 context level diagram
Involved entity’s in the context level diagram :
Modules -> Applicant user, Recruitment manager, System admin.
Sub modules -> Processes in modules.
Involved association’s in the context level diagram :
- 27 -
Modules -> modules connected to Campus Recruitment Management.
Sub modules -> various processes interconnected among their respective modules.
4.4 Data Flow Diagrams
4.4.1 DFD level 0
Figure 4 DFD level-0
- 28 - 4.4.2 DFD level 1
Figure 5 DFD level-2
- 29 - 4.4.3 DFD level 2
Figure 6 DFD level-2
- 30 - 4.5 Class Diagram
Figure 7 class diagram
- 31 - 4.6 Sequence Diagrams
4.6.1 Sequence Diagram 1
Sequence name : creation and storage of profile at applicant user information module.
Figure 8 At applicant user end
- 32 -
Sequence description : shows the sequential interaction of various processes while the creation and updating of applicant profile from the front end of the site.
4.6.2 Sequence Diagram 2
Sequence name : searching, short listing, viewing and recruitment of applicant from admin user module.
Sequence Description : shows the sequential interaction of various processes while the applicants are searched from the database, shortlisted, their profiles are viewed and resumes downloaded for recruitment.
- 33 -
Figure 9 At admin user end
- 34 - 4.7 Database Description
Database Name
Database Description
Admin This stores the various attributes like admin user id, username, password, type and email addresses of all the admin users.
Category This saves the attributes of categories of products featured on the company’s web page as category id, name, rank , status.
Content This saves the attributes of content of pages namely Home, About us and Contact us like content id, title, meta_title , meta_keyword, type, link, description.
department This saves the attributes like id, name, meta title, meta keyword, meta description and description of various aspx pages linked on the mainframe of the website.
Experience This saves the options presented for the experience field to be filled by the applicant on the web page for job application form.
jobapplication This saves the data presented by all the applicants belonging to various fields on the job application form like first name, last name, email address, phone number, age, gender, address, qualification, experience and current salary.
Menu This saves the attributes of various links on the control panel of the administrator side like the link name, linked aspx page, parent id and rank.
Product This saves the attributes of various products in different categories and their descriptions.
qualifications This saves the options presented for the qualifications field to be filled by the applicant on the web page for job application form.
Table 1 Datbase description
- 35 -
1 narendra Admin admin [email protected]
2 Hitarth Hitarthsaini subadmin [email protected] m
3 Varun Varunmundra subadmin [email protected]
Table 2 Admin table
4.7.1.2 Category Table
Table 3 Category table
Id Category name rank activestatus
1 Turning 1 active
- 36 - 4.7.1.3 Experience Table
Table 4 Experience table
- 37 - 4.7.1.5 Menu table
menu_id menu_name ASPX_page parent_id rank
1 adminmanager 0 1
11 jobapplication jobapplication.aspx 10 11
- 38 -
5 USER INTERFACE
The following are the screens with their corresponding description:
5.1 Screen name : home.aspx
Figure 10 home
Description:
• This is the menu screen displayed to the user as soon as he/she opens the website.
• This screen contains links to various pages/screens.
- 39 - 5.2 Screen Name : applyforjobs.aspx
Figure 11 job application form
Description :
• This is the form that is presented to the applicant for applying to job.
• This form has various options as provided by the asp.net toolbox like dropdown, submit, upload buttons.
• The fields marked * are mandatory for the applicant to fill the form.
- 40 -
• Some fields have options already presented that need to be selected while others have a set of defined inputs for them.
5.3 Screen Name : applyforjobs.aspx
Figure 12 job application form filled
Description :
• This is an example of how the applicant has to fill the various fields as presented in the form.
• The screen shows how after filling and submitting the form the control is being transferred to another aspx page.
- 41 -
• The next screen that is loaded after this is the paypal sandbox screen where the applicant has to pay for the application online.
• It is mere transfer of control from one site to other.
• The user can return back to the previous screen and can also skip the option of payment of fee.
• This will only submit the profile filled online by the applicant in the system’s database which is accessible to the resource manager or admin users anytime.
5.3 Screen name : administratorlogin.aspx
Figure 13 Admin window
- 42 - Description :
• This is the site which admin users can access anytime.
• For security reasons it has been featured to submit username and password of the admin user.
Until and unless the correct match is not provided, the site will not proceed and will return back to reload of the same aspx page.
5.4 Screen name : administrator.aspx
Figure 14 Administrator
- 43 - Description :
• This is the main page of the admin user side.
• This shows the map to various sections of site on its left and also shows the profiles of various admin users.
• This has also been incorporated with various features using aspx toolbox.
• There is a search by email option, add and delete admin user profile option, a clock presented all the time and an edit profile option.
5.5 Screen name : jobapplication.aspx
Figure 15 Aplication search
- 44 - Description :
• This is the page which presents the admin user with all the available job applicants from the pool created by the database.
• The page gives admin user rights to view and delete various profiles.
• The page also is integrated with search options where the admin user can search for a particular applicant fitting to some
particular job profile.
• A search can be made when the search parameters are set.
5.6 Screen name : jobapplication.aspx
Figure 16 Search procedure
- 45 - Description :
• This shows the available qualification parameters that can be selected for the search of the applicants.
• The options for qualifications are already in the aspx page which were added during its design and can be changed by the system administrator.
5.7 Screen name : viewprofile.aspx
Figure 17 Display
- 46 - Description :
• This is the profile displayed of the applicant that admin user selects and views.
• The profile is presented to admin user and the details of the applicant are shown.
- 47 - corrections remade, the corrections are also noted for future use.
It includes a vast variety of test put together to develop an active application which can be used under varied stress and load situation.
The GUI is also tested with performance and error handling testing.
6.2 Unit Testing
Testing is a set of activities that can be planned in advance and conducted systematically. The proposed system is tested in parallel with the software that consists of its own phases of analysis, implementation, testing and maintenance. Following are the tests conducted on the system.
During the implementation of the system each module of the system was tested separately to uncover errors within its boundaries. User interface was used as a guide in the process.
Unit testing may reduce uncertainty in the units themselves and can be used in a bottom-up testing style approach. By testing the parts of a program first and then testing the sum of its parts, integration testing becomes much easier.
- 48 - 6.3 Module Testing
A module is composed of various programs related to that module. Module testing is done to check the module functionality and interaction between units within a module. It checks the functionality of each program with relation to other programs within the same module. It then tests the overall functionality of each module. Modules being the integral part of the system have to interact with each other efficiently and without errors, because error here would bring the complete system to a stand still. The server would run out of responses thus causing a massive system crash.
6.4 Integration Testing
The purpose of integration testing is to verify functional, performance, and reliability requirements placed on major design items. Integration testing is a systematic technique for constructing the program structure while conducting tests to uncover errors associated with interfacing. The objective is to take unit-tested module and build a program structure that has been dictated by design.
Test cases are constructed to test that all components within assemblages interact correctly, for example across procedure calls or process activations, and this is done after testing individual modules, i.e. unit testing. The overall idea is a "building block" approach, in which verified assemblages are added to a verified base which is then used to support the integration testing of further assemblages.
- 49 -
7 IMPLEMENTATION PHASE
The implementation is the final and important phase. It involves User training, system testing and successful running of the developed system. The users test the developed system when changes are made according to the needs. The testing phase involves the testing of the developed system using various kinds of data. An elaborate testing of data is prepared and system is tested using the tests data.
Implementation is the stage where theoretical design turned into a working system. Implementation is planed carefully to propose system to avoid unanticipated problems. Many preparations involved before and during the implementation of proposed system. The system needed to be plugged in to the organization’s network then it could be accessed from anywhere, after a user logins into the portal. The tasks that had to be done to implement the system were to create the database tables in the organization database domain. Then the administrator was granted his role so that the system could be accessed.
Implementation is the stage where theoretical design turned into a working system. Implementation is planed carefully to propose system to avoid unanticipated problems. Many preparations involved before and during the implementation of proposed system. The system needed to be plugged in to the organization’s network then it could be accessed from anywhere, after a user logins into the portal. The tasks that had to be done to implement the system were to create the database tables in the organization database domain. Then the administrator was granted his role so that the system could be accessed.