Essay:

Essay details:

  • Subject area(s): Engineering
  • Price: Free download
  • Published on: 7th September 2019
  • File format: Text
  • Number of pages: 2

Text preview of this essay:

This page is a preview - download the full version of this essay above.

CHAPTER 1

INTRODUCTION   

1.1 PROJECT SUMMARY

This project is for e-local and home services provider system. Now Days finding Person for local and home services are hard to find. Here we found a different solution for that problem.

We don’t need to go anywhere for finding the service man we can do it by sitting at home and  by just one click we can get the required service.

We will manage it in our secure database so no issue of data theft.

The basic function of this system is get or book the service men(workers) through different agents or Agency. Daily many workers and agents will be approved and the new records are updated so that User can view them and if they are interested they can book the worker for their work.

The worker details will be given to the user. This system can also handle multiple booking of workers at one time i.e. the user can access various workers from the agency at one time. The user can submit their feedback.

1.2 PURPOSE    

In “Agency Biding System” a user can use this online system without any difficulty. Users and Agent or Agency has to fill a registration form to register them self. All the entries are submitted to the DATABASE.

Using Agency biding the Agency can put their workers information, and users can see it and can book the worker for some particular work.

Objectives:

1. To make easy work for users as well as workers using our website.

2. To reduce the stress for finding workers.

3. To provide best services.

4. To reduce the time period of user to find workers.

5. To provide more options of workers and agency.

1.3 SCOPE

The scope of the project that is hosted on the server there is a DATABASE which is maintained by the site Administrator in which all the names of Agency or Agent and workers are saved.

The scope of the project is to provide fast service and worker information to the user.

Purpose of making this website is to provide more facilities to Users to get easy access to find the required worker. And to get their required services by sitting at home with just one click.

The payment system will be much simpler. The agency will give fix time for making the work completed.

1.4 TECHNOLOGIES AND LITERATURE REVIEW:       

1.4.1 TECHNOLOGY AND TOOLS:-

• TECHNOLOGY :- PHP

• Front end :- HTML, CSS, JS

• Back end :- SQL server 2008

 Why PHP?

1. Open source: It is developed and maintained by a large group of PHP developers, this will helps in creating a support community, abundant extension library.

2. Speed: It is relative fast since it uses much system resource.

3. Easy to use: It uses C like syntax, so for those who are familiar with C, it’s very easy for them to pick up and it is very easy to create website scripts.

4. Stable: Since it is maintained by many developers, so when bugs are found, it can be quickly fixed.

5. Powerful library support: You can easily find functional modules you need such as PDF, Graph etc.

6. Built-in database connection modules: You can connect to database easily using PHP, since many websites are data/content driven, so we will use database frequently, this will largely reduce the development time of web apps.

7. Can be run on many platforms, including Windows, Linux and Mac, it’s easy for users to find hosting service providers.

 The MVC Framework is…

Model: The Model component corresponds to all the data related logic that the user works with. This can represent either the data that is being transferred between the View and Controller components or any other business logic related data. For example, a Customer object will retrieve the customer information from the database, manipulate it and update it data back to the database or use it to render data.

View: The View component is used for all the UI logic of the application. For example, the Customer view would include all the UI components such as text boxes, dropdowns, etc. that the final user interacts with.

Controller: Controllers act as an interface between Model and View components to process all the business logic and incoming requests, manipulate data using the Model component and interact with the Views to render the final output. For example, the Customer controller would handle all the interactions and inputs from the Customer View and update the database using the Customer Model. The same controller would be used to view the Customer data.

(Fig 1.1: - MVC Framework Architecture)

The Framework Design Goals

• Component Development for the Internet

• Reliability and Security

• Simple Development and Deployment

1.4.2 LITERATURE REVIEW:-

PHP:

The PHP Hypertext Preprocessor (PHP) is a programming language that allows web developers to create dynamic content that interacts with databases. PHP is basically used for developing web based software applications.

• PHP is a recursive acronym for \"PHP: Hypertext Preprocessor\".

• PHP is a server side scripting language that is embedded in HTML. It is used to manage dynamic content, databases, session tracking, even build entire e-commerce sites.

• It is integrated with a number of popular databases, including MySQL, PostgreSQL, Oracle, Sybase, Informix, and Microsoft SQL Server.

• PHP is pleasingly zippy in its execution, especially when compiled as an Apache module on the Unix side. The MySQL server, once started, executes even very complex queries with huge result sets in record-setting time.

• PHP supports a large number of major protocols such as POP3, IMAP, and LDAP. PHP4 added support for Java and distributed object architectures (COM and CORBA), making n-tier development a possibility for the first time.

• PHP is forgiving: PHP language tries to be as forgiving as possible.

• PHP Syntax is C-Like.

JAVA SCRIPT:

• JavaScript supports the development of both client and server components of web based applications.

• On the client side, it can be used to write programs that are executed by a web browser within the context of the web page.  

• On the server side, it can be used to write web server programs that can be process information submitted by a web browser and then update the web browser display accordingly.

Advantages:

• It can be used for server side and client side scripting.

• It is more flexible then JavaScript.

Back-End:   DBMS

SQL SERVER: ¬

SQL Server is an SQL-compliant RDBMS. SQL-compliant means it use the ANSI (American National Standard Institute) version of Structured Query Language or ‘SQL’. Structured Query Language is a command that allow us to modify or retrieve information from the database.

Client server means that SQL Server is designed to store data in the central location (the server) and deliver it on demand to numerous other locations (the client). SQL Server is also a Relational Database Management System (RDBMS).

FEATURES OF SQL SERVER 2008:

1. Information representation

2. Unique definition of rows

3. Systematic treatment of Null values

4. Guaranteed access

5. High level Update, Insert, and Delete

6. Retrieving information from the database.

7. Accepting query language statements.

8. Enforcing security specifications.

9. Enforcing data integrity specifications

10. Enforcing transaction consistency

11. Managing data sharing

12. Optimizing queries

13. Managing System catalogs

Enterprise Manager:

SQL Server Enterprise Manager is a graphical tool that allows easy configuration and management of Microsoft SQL Server and SQL 2008 program group.

SQL Server Enterprise Manager can also be used to:

1. Manage logins, permission and users.

2. Create a database

3. Take back-up of database and transaction logs.

4. Manage tables

Query Analyzer:

The SQL Server Query Analyzer allows us to create queries and run them interactively. We may also execute Transact-SQL statements stored in text file and view the result in result plane or result grid. The Query Analyzer also has a color-coded editor to assist the user with checking of syntax. It also has context sensitive help.

Queries are processed in two steps:

Interpret- First the Queries are checked for syntax.

       Execute- Then the processing take place.

CHAPTER-2

PROJECT MANAGEMENT

2.1 PROJECT PLANNING AND SCHEDULING

2.1.1 PROJECT DEVELOPMENT APPROACH

2.1.2 PROJECT PLAN

2.1.3 SCHEDULE REPRESENTATION

2.2 RISK MANAGEMENT

2.2.1 RISK IDENTIFICATION

2.2.2 RISK ANALYSIS

2.2.3 RISK PLANNING

2.3 ESTIMATION

2.3.1 EFFORT AND COST ESTIMATION

CHAPTER 2

PROJECT MANAGEMENT

SOFTWARE PROJECT MANAGEMENT is the collection of activities within software engineering. This chapter provides how to plan, track and estimates this website by managing various phases. It comprises of project development approach\'s justification, schedules, and risk analysis, cost and effort estimation.

2.1 PROJECT PLANNING AND SCHEDULING

Project planning is part of project management , which relates to the use of schedules such as Gantt charts to plan and subsequently report progress within the project environment .Initially, the project scope is defined and the appropriate methods for completing the project are determined. Following this step, the durations for the various tasks necessary to complete the work are listed and grouped into a work breakdown structure. Project planning is often used to organize different areas of a project, including project plans, workloads and the management of teams and individuals. The logical dependencies between tasks are defined using an activity network diagram that enables identification of the critical path. Float or slack time in the schedule can be calculated using project management software. Then the necessary resources can be estimated and costs for each activity can be allocated to each resource, giving the total project cost.

2.1.1 PROJECT DEVELOPMENT APPROACH

A Software process model is a simplified abstract representation of a software process, which is presented from a particular idea. A process model for a software engineering is chosen based on nature of the project and applications, the methods and tools to be used, and the controls and deliverables that are required. All software development can be characterized as a problem-solving loop which in four distinct stages is encountered as:

• REQUIREMENT ANALYSIS                                        

• DESIGN

• TESTING

• IMPLEMENTATION

ESTIMATION ON AGENCY BIDING follows SPIRAL MODEL APPROACH because while developing tendering project the risk level of modules is very high so for handling this type of risk we use spiral modal.  

SPIRAL MODEL was defined by Barry Boehm in his 1988 article, “A spiral Model of Software Development and Enhancement.  This model was not the first model to discuss iterative development, but it was the first model to explain why the iteration models.

As originally envisioned, the iterations were typically 6 months to 2 years long.  Each phase starts with a design goal and ends with a client reviewing the progress thus far.   Analysis and engineering efforts are applied at each phase of the project, with an eye toward the end goal of the project.

The steps for Spiral Model can be generalized as follows:

• The new system requirements are defined in as much details as possible.  This usually involves interviewing a number of users representing all the external or internal users and other aspects of the existing system.

• A preliminary design is created for the new system.

• A first prototype of the new system is constructed from the preliminary design.  This is usually a scaled-down system, and represents an approximation of the characteristics of the final product.

• A second prototype is evolved by a fourfold procedure:

1. Evaluating the first prototype in terms of its strengths, weakness, and risks.

2. Defining the requirements of the second prototype.

3. Planning a designing the second prototype.

4. Constructing and testing the second prototype.

• At the customer option, the entire project can be aborted if the risk is deemed too great.  Risk factors might involve development cost overruns, operating-cost miscalculation, or any other factor that could, in the customer’s judgment, result in a less-than-satisfactory final product.

• The existing prototype is evaluated in the same manner as was the previous prototype, and if necessary, another prototype is developed from it according to the fourfold procedure outlined above.

• The preceding steps are iterated until the customer is satisfied that the refined prototype represents the final product desired.

• The final system is constructed, based on the refined prototype.

• The final system is thoroughly evaluated and tested.   Routine maintenance is carried on a continuing basis to prevent large scale failures and to minimize down time.

The following diagram shows how a spiral model acts like:

(Fig 2.1-Spiral Model)

2.1.2 PROJECT PLANNING

The software project management process begins with the set of activities that are collectively called project planning. The objective of software planning is to provide a framework that enables administrator to make reasonable estimates of resources, cost and schedule.

Table 2.1: Table of project schedule

TASK

FROM DATE

TO DATE

REQUIREMENT GATHERING AND ANALYSIS 27/08/2015 10/09/2015

PROTOTYPE PREPARATION 12/09/2015 29/09/2015

UI DESIGN AND DATABASE DESIGN 31/09/2015 28/10/2015

CODING 29/10/2015 10/12/2015

TESTING

AND

INTEGRATION 12/12/2015 30/12/2015

IMPLEMENTATION 01/01/2016 18/03/2016

MILESTONES AND DELIVERABLES

Management needs information as software is intangible, this information can only be provided as documents that describe the state of the software being developed without this information it is impossible to judge progress and schedules cannot be updated. Milestone is an end point of the software process activity.

Table 2.2: Milestones and Deliverables.

SOFTWARE PROCESS ACTIVITY

MILESTONE

Requirement Analysis User requirement , Schedule , Flow

Design

1. GUI

2.Data base System Design Document , Codes , Validations

Testing Identification of bugs and recovery

Implementation Access rights

Each milestone should give formal output that can represent management. Milestones are used by project managers to check the progress.

2.1.3 PROJECT SCHEDULING

 Gantt chart

 (Fig 2.2: Gantt chart)

2.2 RISK MANAGEMENT

Agency and Workers Information is simply posted on the internet as \'Pure information\'. Although exposed to minimum level of risk, attention must be given to its contents- that is truth, accuracy, not misleading etc.  

2.2.1 RISK IDENTIFICATION

Risk identification refers to the process of identifying dangerous or hazardous situations and trying to characterize it. It is a procedure to deliberately analyze, review and anticipate possible risks.

TECHNOLOGY RISK: - technical risk concerns server-failure, maintenance problem, and virus.

PEOPLE RISK: - leaking of information, unauthorized access.

TOOLS RISK: - Scripting error, Database Corrupt.

Table 2.3: Table of project Risk

DESCRIPTION

RISK TYPE

Power off Tool risk

Connection error Technical risk

Leaking of data People risk

Failure of administration Technical risk

Broken link Tool risk

Database Corrupt People risk

2.2.2 RISK ANALYSIS

Risk analysis, attempts to rate each risk in two ways - the likelihood or probability that risk is real and consequences of the problems associated with the risk should it occur.

Table 2.4: Risk involved in the project

RISK TYPE

RISK CAUSES/ DESCRIPTION PROBABILITY

EFFECTS

Power off Error in power connection. Low Customer can’t use the application.

Connection error

Lower quality of ISP

Low

Can’t access that particular application

Leaking of data Less security, hacking.

High

Can’t manage the properly the system.

Failure of administration Less security in login authentication. High Can fail the product

Broken link

Not proper coding.

Medium

User can not access the particular

Module directly.

Database Corrupt Large data added. High Security will in the risk

2.2.3 RISK PLANNING

Risk planning refers to the identification and scheduling of actions needed to reduce the level of risk within a project. “Risk management planning is the process of deciding how to approach and plan the risk management activities for a project.” Whether you decide to identify risks before the project begins or in the middle, a Risk Management Plan should be drafted. Among other things, the Risk Management Plan determines how risks will be identified, monitored, controlled, and eliminated. This plan will identify what will be considered a risk and how it will be managed. It also defines the team roles and responsibilities for risk management.

Table 2.5: Remedies for risk involved

RISK TYPE

DESCRIPTION

Power off Power Bank based Power supply

Connection error Use better ISP

Leaking of data Provide security to fetch the data.

Failure of administration Provide the security.

Broken link Provide proper coding.

Database Corrupt Provide security through frequently back-up.

2.3 ESTIMATION

Presumed amount of the WEBSITE:

The overall presumed value of the tender is estimated at Rs.155000.00 excluding VAT.

This estimation is based on the average number of events that occurred during the course of the previous service contract and is to be considered purely an indication; it shall be used merely to determine the presumed overall value of the tender and in no way commits the contracting authority to award a tender for the entire above mentioned total sum.   

2.3.1 EFFORT ESTIMATION

The process of forecasting or approximating the time and cost of completing project deliverables Effort estimation consists in predicate how many hours of work and how many workers are needed to develop a project. The effort invested in a software project is probably one of the most important and most analyzed variables in recent years in the process of project management.

In this project we have used COCOMO Model. The constructive cost model is an algorithmic software cost estimation model developed by Barry w. Boehm. The model uses a basic regression formula with parameters that are deriving from historical project data and current as well as future project characteristics. These models rely on the experience gained on previous software projects.

Modes of project development

Organic projects - “Small” teams with “good” experience working with “less than rigid” requirements.

Semi-detached projects - “Medium” teams with mixed experience working with a mix of rigid and less than rigid requirements.

 Embedded projects - Developed within a set of “tight” constraints. It is also combination of organic and semi- detached projects.

In our project we have used Semi - detached mode because it supports medium team size and more or less experience.

2.3.2 COST ANALYSIS

We are using Semi - detached development mode of COCOMO model for effective cost estimation.

For finding the project cost we can use some predefined constants which are as follow.

Table 2.6: Parameters of COCOMO Model.

SOFTWARE

PROJECT A

B

C

D

Organic 2.4 1.05 2.5 0.38

Semi - detached 3.0 1.12 2.5 0.35

Embedded 3.6 1.20 2.5 0.32

EQUATIONS FOR ESTIMATION

Effort Applied (E) = a (KLOC) b [man- month]

Development Time (D) = e (Effort applied) d [months]

People required (p) = Effort applied/development time [count]

2.3.3 COST ESTIMATION

For finding the total cost of the project we need to find the total lines of code of the system.

• Estimation of LOC

• Module 1: 300

• Module 2: 300

• Module 3: 280

• Module 4: 100

• Module 5: 400

• Total LOC = 1380 (1.38 K)

We have used Semi - detached mode for development so we will consider the values of a, b, c, d has given for Semi - detached mode.

• Values for Semi - detached mode

• a = 3.0

• b = 1.12

• c = 2.5

• d = 0.35

Putting values in above formulas

Efforts applied

3.0*(1.38^1.12) = 4.303 person-months

Development time

2.5*(1.38^0.35) = 2.798 months

People Required

4.303/2.798 = 1.57 = 2 persons

COST

The average productivity for our product is: (LOC/ per month)

The labour charges estimated is: (per month): 4.303

Thus the cost per line of code is :( approximately) 7000

Hardware cost: 6000

Total estimated project cost is = 15000

CHAPTER-3

SYSTEM REQUIREMENT STUDY

3.1 USER CHARACTERISTICS

3.2 HARDWARE AND SOFTWARE REQUIREMENT

3.3 CONSTRAINTS

3.3.1 REGULARITY POLICIES

3.3.2 HARDWARE LIMITATION

3.3.3 ASSUMPTIONS AND DEPENDENCY

CHAPTER 3

SYSTEM REQUIREMENTS STUDY

3.1 USER CHARACTERISTICS

Type of users who is dealing with the system

User characteristic describes the type of users, which deals with the website i.e. a person or any other entity that interacts with the website. This website is basically used by internal users and public user . The user can perform following operations:

Every user should be:

- Comfortable with Internet Browser.

- He must have brief knowledge about the site.

- He must also have basic knowledge of English too.

INTERNAL USERS:

1. Administrator:

• All passwords recovered by the specified administrator.

• The administrator role has access to the following functionality:

- Message configuration

- User configuration

- Password recovery

- System configuration

2. Worker Approval:

 The process of approving worker must involve the login of a worker which allows the user access to the \"Workers details\" page.

3. Worker manager:

 Manage the worker functionality must allow the worker manager to change the state of these worker as necessary.

 The worker manager role has access to the following functionality:

- Verifying workers

- Managing workers

PUBLIC USERS:

 1.   Registered Users:

 Registered Users can directly search for a workers by login.

- View workers details

- Apply for booking.

 2.   Anonymous users:

 The anonymous users have access to the following functionality:

- Search for a workers

- View worker details (but cannot do booking)

- Online registration

3.2 HARDWARE & SOFTWARE REQUIREMENTS

 Hardware  requirement :-

 The system must have the following hardware requirements:

- Processor :- Pentium IV

- Hard disk :- Minimum 20GB

- RAM :- 512 MB

- Monitor Resolution :- 1024*768

- Machine                      :-                      Server, Client

 Software  requirement :-

 The system must have the following software requirements:

- Operating System :- Microsoft Windows 7

- Frontend :- HTML, CSS, JS

- Backend :-         SQL server 2008

- Editor :- NET BEANS

- Browser :- Mozilla Firefox and Google chrome

- Server :- SQL Server 2008

3.3 CONSTRAINTS

In current system a lot of hectic work is involved. The system is based on manual system which is a very time consuming process. No proper records available which leads to difficulty in manual report generation. People who are interested for getting worker have to travel long distances to find them.

All the above issues are resolved in online Agency Biding System. Agency who want to enter their workers need to register online through the website. After registering the Agency adds the various workers which are needed by the Users as per their requirement. Now, when User visits the site it registers itself and can view the various workers. Thus, now can apply for the workers that are required.

3.3.1 REGULARITY POLICIES:

Agency select the appropriate of all workers for specific work. All the workers are displayed on the website leading to transparency between clients and Agency.

Regulatory policies, or mandates, limit the discretion of individuals and agencies, or otherwise compel certain types of behaviour.

These policies are generally thought to be best applied when good behaviour can be easily defined and bad behaviour can be easily regulated and punished through fines or sanctions.

3.3.2 HARDWARE LIMITATION:

The smooth functionality of the application mainly depends on the speed of the hardware and then on the speed of the internet.

It is always advisable to be update as far as hardware is concerned. The hardware limitations will occur if the user is still using a processor less than a RAM of 512Mb, inbuilt memory of 64MB and processor with API level 8 and above.

Performance requirements:

• The website must be efficient & fast. Its response time should be minimal. The output should be responded within a maximum of 10 seconds depending on the internet connection speed and handset performance.

• It should also work in slow 2G (less than 15 Kbits/second) internet connection. For this, some kind of catching mechanism should be implemented.

Safety and security considerations:

• The website should have a high level of security and safety consideration above any of the feature so that an unauthorized user cannot log into the system.

• The website must utilize some hash based encryption algorithm to protect the critical databases from hackers.

Reliability requirements:

• The website must implement error checking and crash recovery features.

• The sever must be available all the time and it must be capable for maintaining high load of concurrent database operations.

• The website should be protected against failure by dynamically resolving the use of system resources at runtime.

3.3.3 ASSUMPTIONS AND DEPENDENCIES:

• It is assumed that user is aware of rules and regulations.

• It is assumed that user is well familiar with this system.  

CHAPTER-4

SYSTEM ANALYSIS

4.1   STUDY OF CURRENT SYSTEM

4.2   PROBLEMS AND WEAKNESSES OF CURRENT SYSTEM

4.3   REQUIREMENT OF NEW SYSTEM

4.4   FEASIBILITY STUDY

4.5   REQUIREMENTS VALIDATION

4.6   FUNCTIONS OF SYSTEM

4.6.1 USE CASE DIAGRAM

4.7   DATA MODELING

4.7.1 CLASS DIAGRAM / E-R DIAGRAM

4.7.2 SYSTEM ACTIVITY DIAGRAM  

4.8   FUNCTIONAL AND BEHAVIOURAL MODELING

4.8.1 DATA FLOW DIAGRAM

4.9     MAIN MODULE OF NEW SYSTEM

4.10 SELECTION OF HARDWARE AND SOFTWARE AND       JUSTIFICATION

CHAPTER 4

SYSTEM ANALYSIS

4.1    STUDY OF CURRENT SYSTEM

In current system a lot of hectic work is involved. The system is based on manual system which is a very time consuming process. No proper records available which leads to difficulty in manual report generation. People who are interested for getting worker have to travel long distances to find them.

4.2 PROBLEM AND WEAKNESS OF CURRENT SYSTEM

• It is more time consuming

• It leads to complex work

• It includes wastage of money

• Does not get many options.

• Not User Friendly: The existing system is not user friendly because the it is more time consuming and hectic.

• Difficulty in finding workers: We require lot of searching to find the required worker for particular work.

• Time consuming: Mainly finding the required worker is hard and it takes lot of time.

4.3   REQUIREMENTS OF NEW SYSTEM

4.3.1 USER REQUIREMENTS

Our system will have default password using that Agency will have to login and give detail of Workers to Administrator. Agency Biding is a system by which any user can choose his/her workmen according to their requirement.

4.3.2   SYSTEM REQUIREMENTS

• The Agency Biding shall operate with the following Web browsers: Google chrome, Microsoft Internet Explorer and Mozilla Firefox.

• The Agency Biding System shall operate on a server running on the Internet.

• The Agency Biding System shall permit user access from the Internet.

4.3.3 FUNCTIONAL REQUIREMENTS

 It deals with the functionalities required from the system which are as follows:

• The website will help the any Agency to fill their workers form.

• Any new Agency should contain all the details including attachments of the required documents.

• Only authorized Agency can access related details.

• Admin can change their information.

• The Agency can login through USERNAME and PASSWORD and it can get the information.

• Administrator will be responsible for updating the site.

• The admin can update the agency details and they want the eligible worker for the required work.

4.3.4 NON-FUNCTIONAL REQUIREMENTS

Security:

• Website will be accessible only after login successfully i.e. login credentials must be correct.

• Website should use some hash based encryption algorithm to protect critical databases like user account details etc.

• The user wants the data stored in database must be secured and cannot be accessed by unauthorized user.

Reliability:

• The database of projects, project tasks and client maintained by the system should be correct and maintained up to date.

Usability:

• The website will provide user friendly environment to its users and must be easy to access its various features. And must provide easy and fast access without consuming more cost.

Scalability:

• The system will be scalable enough to be able to add any additional functionality even after the project is developed once.

Accuracy:

• The user should require that data are obtained from database and stored in database must be accurate.

Maintainability:

• User wants that the system should be maintained easily means that if there are some changes required in the system that can be done easily.

4.4   FEASIBILITY STUDY

Feasibility study is the main core of system analysis phase in software development. It actually calculates the feasibility of all the requirements gathered from the users and those documented in SRS. This is of very prime necessary because before developing a new system or replacing an existing system, it should be known well in advance whether the requirements to develop a system are feasible considered to various aspects.

One important activity of any project developing team is to check the feasibility of the software of they are the building. Feasibility study gives us more knowledge about the actual behavior of environmental factors that are going to affect after or during the project developing.

We will analyze Agency Biding System for following types of the feasibility.

Three types of project feasibility we will consider are:

1) Operational feasibility.

2) Technical feasibility.

3) Financial and Economic feasibility.

4.4.1 Operational feasibility.

It is mainly related to human organizations and political aspects. The points to be

Considered are:

• What changes will be brought with the system?

• What organization structures are disturbed?

• What new skills will be required?

The system is operationally feasible as it very easy for the End users to operate it. It only needs basic information about Windows platform.

4.4.2 Technical Feasibility

A study of resource availability that may affect the ability to achieve an acceptable system this evaluation determines whether the technology needed for the proposed system is available or not.

• Can the work for the project be done with current equipment existing software technology & available personal?

• Can the system be upgraded if developed?

• If new technology is needed then what can be developed?

• This is concerned with specifying equipment and software that will successfully satisfy the user requirement. The technical needs of the system may include:

Front-end and back-end selection

An important issue for the development of a project is the selection of suitable front-end and back-end. When we decided to develop the project we went through an extensive study to determine the most suitable platform that suits the needs of the organization as well as helps in development of the project.

The aspects of our study included the following factors.

Front-end selection:

1. It must have a GUI that assists employees that are not from IT background.

2. Scalability and extensibility.

3. Flexibility.

4. Robustness.

5. According to the organization requirement and the culture.

6. Must provide excellent reporting features with good printing support.

7. Platform independent.

8. Easy to debug and maintain.

9. Event driven programming facility.

10. Front end must support some popular back end.

According to the above stated features we selected PHP as the front-end for developing our project.

Back-end Selection:

1. Multiple user support.

2. Efficient data handling.

3. Provide inherent features for security.

4. Efficient data retrieval and maintenance.

5. Stored procedures.

6. Popularity.

7. Operating System compatible.

8. Easy to install.

9. Various drivers must be available.

10. Easy to implant with the Front-end.

According to above stated features we selected MY SQL 2008 as the backend.

The technical feasibility is frequently the most difficult area encountered at this stage. It is essential that the process of analysis and definition be conducted in parallel with an assessment to technical feasibility. It centers on the existing computer system and to what extent it can support the proposed system.

4.4.3 Financial and Economic Feasibility

Economic justification is generally the “Bottom Line” consideration for most systems. Economic justification includes a broad range of concerns that includes cost benefit analysis. In this we weight the cost and the benefits associated with the candidate system and if it suits the basic purpose of the organization i.e. profit making, the project is making to the analysis and design phase.

The financial and the economic questions during the preliminary investigation are

Verified to estimate the following:

• The cost to conduct a full system investigation.

• The cost of hardware and software for the class of application being considered.

• The benefits in the form of reduced cost.

• The proposed system will give the minute information, as a result the

• Performance is improved

• This feasibility checks whether the system can be developed with the available funds. The Agency Biding does not require enormous amount of money to be developed. This can be done economically if planned judicially, so it is economically feasible. The cost of project depends upon the number of man-hours required.

4.5 REQUIREMENTS VALIDATION

Requirements validation is concerned with showing that the requirements actually define the system which the user wants. All forms, menus should be standardized i.e. all forms have a standard way of accepting inputs form the users and giving massage to the users. The system validate the all standard input form validations required to be done in name , username , password , email , date of join , salary etc..

Some of them described here:

1. There will be a validation for checking whether all entities are filled or not.

2. Display date and time must be in specific format.

3. E-mail must be written in specific formats.

4. Timings for check in and check-out must be clearly obtained.

5. User must be a current member (part) of the organization.

4.6 FUNCTIONS OF SYSTEM

4.6.1 USE CASES

Use case diagrams used to describe a set of actions (use cases) that some system or systems (subject) should or can perform in collaboration with one or more external users of the system (actors). Each use case should provide some observable and valuable result to the actors or other stakeholders of the system. Followings are the components of use case diagram:

• Use Case: A Use Case describes a sequence of actions that provide something of measurable value to the actor and is drawn as horizontal ellipse.

• Actors: An Actor is a Person, Organization, or external system that plays a role inane or more interactions with your systems. Actors are drawn as stick figures.

• Associations: Association between actors and use cases are indicated in use case diagrams using solid lines. An association exists whenever an actor is involved with an interaction described by the use case.

• Connector: Connector simply connects the use case with the actor, Denoted by a line.

USE CASE:

(Fig 4.1:use case)

4.7 DATA MODELING

CLASS DIAGRAM:

It is used for describing structure and behavior in the use cases. It provides a conceptual model of the system in terms of entities and their relationships. Following Modifiers are used to indicate visibility of attributes and operations.

• ‗+‘ is used to denote Public visibility (everyone)

• ‗#‘ is used to denote Protected visibility (friends and derived)

   •‗-‘   is used to denote Private visibility (no one)

There are some symbols and notations are used in class diagrams:

1. Class:

  It contains class name, attributes and methods or operations.

2. Links:

• Association:

    

    It is used to connect two or more than two objects.

• Generalization:

     It’s “is a” relationship where it can generalize sub class to super class

• Multiplicity:

   No instances of one class relating to no of instances of another class.

  No instance or one instance.

Exactly one instance

  Zero or more instance

   One or more instances at list one instances

CLASSDIAGRAM:  

(Fig 4.3: Class diagram of tendering system)

4.7.2 SYSTEM ACTIVITY DIAGRAM

Activity diagrams are graphical representations of workflows of stepwise activities and actions with support for choice, iteration and concurrency. In the Unified Modeling Language, activity diagrams are intended to model both computational and organizational processes (i.e. workflows). Activity diagrams show the overall flow of control.

1. States:

A state is an abstraction of the values and links of an object. As show in UML notation for state is a rounded box containing an optional state name.

2. Initial state:

A solid circle with an outgoing arrow shows the starting point of an activity diagram when an activity diagram is activated.

3. End of final state:

A solid circle surrounded by hollow circle shows the termination point. This Symbol only   has incoming arrows.

4. Diamond:

This symbol represents, if condition is true then go next state else terminate or restarting process.   

 5. Arrow:

 It is use to communicate with two state or link between two state.

USER ACTIVITY:

(Fig 4.4: user activity)

Admin Activity

(Fig4.5:admin activity)

Agent Activity

(Fig4.6 agent activity)

Sequence Diagram:

Admin

(Fig4.7:Adminsequence)

Agent:

(Fig4.8:Agentsequence)

User:

(Fig4.9:Usersequence)

4.8 MAIN MODULE OF NEW SYSTEM

The modules involved in the website are:

• The website provides detail of Workers. User can view and book the worker as per his/her requirement.

• User and Administrator login facilities are provided to check whether the user/admin is an authorized person or not. For this the user/admin should give the correct username and password. User must have to register an account before using functionalities within the website.

• Agency can view particular department of worker. Previous detail of worker will help Agency to learn a complete work done by worker.

• Registered User can view worker details related to particular department or apply for worker.

• Users are provided with search bar where they can write their require worker type. This module will allow user to search all workers details.

• The uses of Agency Biding system do not required sophistication in computer knowledge, and Agency and users with different background can successfully participate in the process.

4.9 SELECTION OF HARDWARE AND SOFTWARE AND JUSTIFICATION:

• Hardware Specification

• OS: Windows XP and up  

• 20 MB free space  

• RAM : 512 MB RAM (minimum)

• Software Specification

• Programming language: PHP

• Front End: HTML, CSS, JS

• Back End: Microsoft SQL Server 2008

• IDE: NET BEANS

e your essay in here...

...(download the rest of the essay above)

About this essay:

This essay was submitted to us by a student in order to help you with your studies.

If you use part of this page in your own work, you need to provide a citation, as follows:

Essay Sauce, . Available from:< https://www.essaysauce.com/essays/engineering/2016-10-5-1475645331.php > [Accessed 20.10.19].