Menu

ARTIST AT WORK A PROJECT REPORT Submitted By Parikh Maitry

0 Comment

ARTIST AT WORK
A PROJECT REPORT
Submitted By
Parikh Maitry (160773107524)
Parmar Preksha (160773107525)
Parmar Sweety (160773107526)

In fulfillment for the award of the degree of
BACHELOR OF ENGINEERING
In
COMPUTER ENGINEERING
2981325101092
SILVER OAK COLLEGE OF ENGINEERING AND TECHNOLOGY
OPP. BHAGWAT VIDYAPITH, NEAR GOTA CROSS ROAD, AHMEDABAD- 382481.

We Will Write a Custom Essay Specifically
For You For Only $13.90/page!


order now

We Will Write a Custom Essay Specifically
For You For Only $13.90/page!


order now

Candidate’s Declaration
We hereby declare that project report titled “ARTIST AT WORK” submitted towards the completion of project in 7th semester of bachelor of Computer Engineering in Silver Oak College Of Engineering ; Technology, Ahmedabad is an authenticate record of our work carried out. We further declare that to the best of our knowledge the report of C.E 7th semester.

Candidate’s signature:
First candidates name: Maitry R Parikh
Branch: Computer
Enrollment Number: 160773107524
Candidate’s signature:
Second candidates name: Preksha D ParmarBranch: Computer
Enrollment Number: 160773107525
Candidate’s signature:
Second candidates name: Sweety A ParmarBranch: Computer
Enrollment Number: 160773107526
Submitted to:
Silver Oak College Of Engineering & Technology, Ahmedabad Affiliated to:
Gujarat Technological University
Abstract
Now a days there are many job portals or recruitment system for educated people, there is no any application who hire or approach or recruit the artist. Large amount of talented artists are not getting work because they don’t have any platform or high profile connection in their field that they can pursue their career in their area of interest. to overcome this problem ,we are making this web application. Called “ARTIST AT WORK” !! Here any artist can register with this website and see the available opportunity in their area of interest and give the auditions online Any recruiters also can register with the website and post their requirements, the artist view that requirements and give the auditions online.

ACKNOWLEDGEMENT
We are heartily thankful to my supervisor, Mr. Ishan Rajani, whose encouragement, supervision and support from the preliminary to the concluding level enabled me to develop an understanding of the subject. At the end, we offer my regards and blessings to all of those who supported us in any respect during the completion of the project and to our college for providing a resources and materials.

2.1 Incremental model 10
2.2 Pie chart 11
2.3 Roles ; Responsibilities 12
4.1 Use case(artist-admin) 25
4.2 Use case(recruiter-admin) 26
4.3 Sequence diagram(artist) 28
4.4 Sequence diagram(recruiter) 29
4.5 Activity diagram(admin) 30
4.6 Activity diagram(artist) 31
4.7 Activity diaram(recruiter) 32
4.7 e-r diagram 35
4.8 Class diagram 36
5.1 Flow chart(admin) 42
5.2 Flow chart(artist) 43
5.3 Flow chart(recruiters) 44
2.1 Project plan 10
2.2 Milestone and deliverables 12
2.3 Cost estimation 1
4.1 Artist registeration37
4.2 Recruiters registeration37
4.3 job 38
4.4 Contact us 38
4.5 notification 38
Chapter No TITLE Page No.

INTRODUCTION Project Summary 2
Project Scope 2
Objective 2
Technologies and Literature Review 4
2. SOFTWARE PROJECT MANAGEMENT Project Planning and Scheduling8
8
2.1.1 Project Planning 8
Project Scheduling 8
Project Development Approach 8
Project Plan 10
Milestone and Deliverables 11
Roles and Responsibilities 12
Cost Estimation 14
2.3.4 The COCOMO Model 14
Chapter No TITLE Page No.

3. SYSTEM REQUIREMENT STUDY User Characteristics 2
3.2 Hardware ; Software Characteristics 2
3.3 Constrains 2
Regularitiy policies 4
3.3.2 Hardware limitations 4. SYSTEM ANALYSIS Study of Current System8
8
4.2 Requirement of the system 8
Functional Requirement 8
Non functional Requirement Feasibility Study 8
Requirement Validation 10
4.5 Functions of the System 11
Use case diagram 12
4.5.2 Sequence diagram 14
4.5.3 Activity diagram Chapter No TITLE Page No.

4.6 Data Modeling 2
4.6.1 E-R diagram 2
4.6.2 Class diagram 4.6.3 Data dictionary 4.7 Main module of the New System 2
4.8 Justification 5. SYSTEM DESIGN Database design 8
8
5.1.1 Classes to object 8
System Procedural Design 8
5.2.1 design pseudo code ; algorithm for method 10
5.2.2 Flowchart diagram 5.3 Data Modeling 11
5.3.1 State transition diagram 12
CHAPTER: 1 INTRODUCTION
CHAPTER 1 INTRODUCTION
Project Summary:
In this project we are going to develop the python based web application which involves artist recruitment online.
There are mainly two modules recruiter, artist.

In this portal, whenever the recruiters post the requirement of the artist the interested artist would apply for it, if recruiter finds it appropriate artist as per their requirement they would hire that artist.

It includes various functionalities such as perfect UI interactions, search opportunities(by skills, locations, languages),notification box, profile updation.

There is much functionality like services by the website, security, goggle map integration etc.

Purpose:
Main purpose of this system to recruit the talented and deserved artist.

The task of recruiters becomes easy by using this website because they can view the talent of different artists and hire them accordingly.

Scope:
The scopes are mention below:
Available Opportunities: user can view the opportunities sorted by skills, location, Language etc. This opportunity would be posted by the recruiters which requires the artist(s).

Post requirement: the recruiter will post the requirement that will be visible to registered artist.

Manage Tender: government will manage it. They decide that which vendor is selected for particular work according to their requirements.

Manage users: users are managed by completing their requirements. By giving response to them. They can login on the portal and be a part of the portal. They can provide suggestion to AMC through this portal.

Manage Notifications: admin will manage this. Vendors can manage it. Users can see all the notifications.

Technology and Literature Review:
The front end used in our project is Python, HTML, JavaScript, CSS and the back end used is MySQL.

Tools used are MySQL, Python IDLE
We will follow the Iterative model for developing this Project and whole Project will be developed using the SDLC scenario.

HTML
HTML an initialize of Hyper Text Markup Language for web pages.

It provides a means to describe the structure of text based information in document by denoting text as headings, paragraphs, lists and so on and to supplement that text with interactive forms, embedded images and other objects.

JavaScript
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.

Python technology:
Python  is an open source programming language that was made to be easy-to-read.

A Dutch programmer named Guido van Rossum made Python in 1991.
He named it after the television show Python Monty Python’s Flying Circus.
Many Python examples and tutorials include jokes from the show.

Benefit of the Python:
Presence of Third Party Module
Extensive Support Libraries
Open Source and Community Development
Learning Ease and Support Available
User-friendly Data Structures
Productivity and Speed
MySQL:
MySQL is an open-source relational database management system (RDBMS).

The MySQL development project has made its source code available under the terms of the GNU General Public License, as well as under a variety of proprietary agreements.

The scope of SQL includes data insert, query, update and delete, schema creation and modification, and data access control. Although SQL is often described as, and to a great extent is, a declarative language (4GL), it also includes procedural elements.

MySQL was owned and sponsored by a single for-profit firm, the Swedish company MySQL AB, now owned by Oracle Corporation.

For proprietary use, several paid editions are available, and offer additional functionality.

 
CHAPTER: 2
SOFTWARE PROJECT MANAGEMENT
CHAPTER 2 SOFTWARE PROJECT MANAGEMENT
Project planning and scheduling
Project Planning
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.

Project Scheduling
Project Scheduling is the culmination of a planning activity that is primary component of software project management.

When combined with estimation methods and risk analysis, scheduling, establishes a road map for the project management.

Scheduling begins with the process composition. The characteristics of the project are used to adapt an appropriate task set for the work to be done.

The task network is used to compute the critical project path, a time line chart and a variety of project information.

Project Development Approach
The activities we followed for this project is listed below:
Planning the work or objectives
Analysis & Design of objectives
Assessing and controlling risk
Allocation of resources
Organizing the work
Database Designing
Form Design
The Process Paradigm we used for our project is Incremental Model.

The Incremental Software Process Model
The Incremental Model combines elements of the linear sequential model with the iterative philosophy of prototyping. The incremental model applies linear sequences in a staged fashion as calendar time progresses.

Each linear sequence produces a deliverable “increment” of the software. For example, word processing software developed using the incremental paradigm might deliver basic file management, editing and document production functions in the first increment; more sophisticated editing and document production capabilities in the second increment; spelling and grammar checking in the third increment; and advanced page layout capability in the fourth increment.

It should be noted that the process flow for any increment can incorporate the prototyping paradigm.

When an incremental model is used, the first increment is often a core product. That is, basic requirements are addressed, but many supplementary features remain undelivered.

The core product is used by the customer. As a result of use and/or evaluation, a plan is developed for the next increment. The plan addresses the modification of the core product to better meet the needs of the customer and the delivery of additional features and functionality.

This process is repeated following the delivery of each increment, until the complete product is produced.

The Incremental process model, like prototyping and other evolution approaches, is iterative in nature.

But unlike prototyping, the incremental model focuses on the delivery of an operational product with each increment.

Figure 2.1 Incremental Model
Project Plan

From Date To Date
1. Preliminay Investigation 25/06/2018 25/07/2018
2.Requirment Analysis 3.Designing 4.Implementation 5.Testing Table 2. 1 Project Plan

Figure 2.2 Pie Chart
Milestone and Deliverables:
In this project, we went through Module Wise Completion. First we did analysis of first module; we went through all the requirements for first module that is Admin Module.

By this analysis we decided field of all the tables of Admin Module. Then we started Database Design.

After competing it we started with the design of all forms of this module. Then we did coding and finally validations and testing of forms that we made.

After completing the first module we started the same procedure for the Member Module.

After that we completed User Module. Between this we did settings forms e.g. Change theme, change background color of the main screen etc.

There was continuously interaction with the client that was very beneficial for us.

When we completed whole project we started testing the whole project for final verification.

Then we started documentation of our project. Finally, we completed the project with client’s satisfaction.

Software Process Activity Milestones
Project Plan Project Schedule
Requirement Collection User requirements
Data Flow Analysis System Flow
Design
User Interface Design
System Design
Databse Design System Design Document
Implementation
Code For giving security
Code for reports Access Reports
Reports
Testing Setting validation and error message
Table 2. 2 Milestones and Deliverables
Roles and Responsibilities:
ARTIST AT WORK

MAITRI
Investigation
Requirement Analysis
DB Design
Coding
Testing
SWEETY
Investigation
Requirement Analysis
DB Design
Coding
Testing
PREKSHA
Investigation
Requirement Analysis
DB Design
Coding
Testing

Figure 2.3 Roles and Responsibilities
2.3.3 Cost estimation:
The COCOMO Model
Like all estimation models for software, the COCOMO models require sizing information.

Three different sizing options are available as part of the model hierarchy: object points, function points, and lines of source code.

Like function points, the object point is indirect software that is computed using counts of the number of
Screens (at the user interface),
Reports,
Components likely to be required to build the application.

Once complexity is determined, the number of screens, reports, and components are weighted according to Table above.

The object point count is then determined by multiplying the original number of object instances by the weighting factor in table above and summing to obtain a total object point count.

When component based development or general software reuse is to be applied, the percent of reuse (%reuse) is estimated and the object point count is adjusted:
NOP = (object points) X (100 – %reuse) / 100.

Where NOP is defined as new object points. To derive an estimate of effort based on the computed NOP value, a “productivity rate” must be derived.

PROD=NOP / person-month
For different levels of developer experience and development environment maturity. Once the productivity rate has been determined, an estimate of project effort can be derived as Estimated effort = NOP/PROD.

There are three types of software project:
Organic project
Semi-deteched project
Embedded project
Cost required to develop project=effort*rs/month
Effort Estimation (E):
In Organic=2.4 (KLOC)1.05 PM
In semidetached=3.0(KLOC)1.12 PM In Embedded=3.6(KLOC)1.20PM
Duration Estimation (D):
In Organic=2.5(effort)0.38monthsIn semidetached=2.5(effort)0.35 months In Embedded=2.5((effort)0.32months
Person Estimation:
P=E/D
KLOC=Kilo Line of Code
Total line of code=12,535
?KLOC=12.54
We are using Organic Project Type,
Effort Estimation (E):
=2.4 (KLOC)1.05 PM
=33.30 PM
Duration Estimation (D):
= 2.5(effort)0.38 month
=2.5(33.30)0.38 months
=9.5 months
Project Cost:
=effort*RS/month
=33.30*12000
=3, 99,600 RS
Advantages of COCOMO:
COCOMO is factual and easy to interpret.

One can clearly understand how it works.

Accounts for various factors that affect cost of the project.

Works on historical data and hence is more predictable and accurate.

Disadvantages:
COCOMO model ignores requirements and all documentation.

It ignores customer skills, cooperation, knowledge and other parameters.

It oversimplifies the impact of safety/security aspects.

It ignores hardware issues
It ignores personnel turnover levels
It is dependenton the amount of time spent in eachphase.

CHAPTER 3
SYSTEM
REQUIREMENT
STUDY
CHAPTER 3
SYSTEM REQUIREMENT STUDY
System Requirement Study:
User Characteristics:
It describes the type of user which deals with the applications. Basically, this application has three types of users as given below:
Administrator
Recruiter
Artist
Administrator:
Responsibility of administrator is to manage the application database and update the data in database regularly. For e.g. manage the data of artist and recruiters.

Recruiter:
Role of recruiter is to post the jobs according to their requirements tasks.

Artist:
Role of artist is to search the job according to the requirement and their category.

Hardware and Software Characteristics:
Hardware Requirements:
Minimum 2.27Ghz processor
RAM: 2GB minimum
Software Requirements:
Web browser and internet
Hardware requirement for Web Application Development
Minimum 2.0 GHz processor
Minimum 2GB of RAM
Software requirement for web Application Development
Python editor
My SQL Database
Web browser
Flask web framework
Constraints:
Regulatory Policies:
Regulatory Policies or mandates, limit the discretion of individual and agencies, or otherwise compel certain types of behavior.

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

Hardware Limitation
The smooth functionality of the portal mainly depends on the speed of hardware and then on speed of the internet.

It is always advisable to be update as far as hardware is concerned. The hardware limitation occurs if the user is still using a very low MHz processor or a RAM or less than 128Mb.

CHAPTER 4
SYSTEM ANALYSIS
CHAPTER 4
SYSTEM ANALYSIS
4.1 STUDY OF CURRENT SYSTEM:
Currently there are many job portals for educated people but there is only a single web application called “talent khoj india” which recruits the artist. and this application also requires the subscription. This is the reason why we are developing this web application.

4.2 Requirement of the System:
We are developing this system for the artists who are not getting that much opportunity to explore their talent. At the end they get unsuccessful and get jobless. Hence, to recruit the artist we are developing this website.

FUNCTIONAL REQUIREMENT:

User Requirement:
User who uses this application should know how to operate web browser and basic knowledge of English.

Identification of functional requirement:
The high level functional requirement often needs to be identified from an informal problem description document or from a conceptual understanding of the problem.

Each high level requirement characterizes away of system usage by some users to perform some meaningful piece of work.

Documentation of functional requirement:
For documenting the functional requirement we need to specify the set of functionalities supported by the system.

A function can be identified the state at which the data to input to the system, its input data domain, the output data domain, and the type of possessing to be carried out on the input data to obtain the output data.

NON FUNCTIONAL REQUIREMENT:
Usability:
The interface should use terms and concepts, which are drawn from the experience of people who will make most o the system
Efficiency:
The portal must provide easy and fast access without consuming more cost.

Readability:
User should never be surprised by the behavior of the system and it should also provide meaningful feedback when error occurs so that user can recover from the error.

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

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

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.

FEASIBLITY STUDY:
Feasibility is the measure of how beneficial the development of information system will be to an organization.

The feasibility analysis is categorized under four different types.

Operational Feasibility
Technical Feasibility
Schedule Feasibility
Economic Feasibility
Operational Feasibility:
The System is to be developed for any user who wants to use it. We want our system user friendly and easy to use.

The administrator also may be non-technical, so the user interface will be designed in such a way that it gets comfortable for non-technical person to operate easily.

Technical Feasibility:
It is a partially measurement of specific technical solution and the availability of technical resorts and expertise.

The analyst must find out whether the current technical resources, which are available in the system is capable of handling the job.

If not, then the analyst with the help of developer should confirm whether the technology is available and capable or not.

Better Considering:
Here we have to consider those tools which are required for developing the project.

As far as basic knowledge concerned we have studied basic of objective-C and SQL.

Schedule Feasibility:
Schedule feasibility corresponds to whether sufficient time is available to complete the project.

Factor considered:
Schedule of the project
Time by which project has to be completed
Reporting period
Economic feasibility:
Economic feasibility is a measure of cost effectiveness of a project or solution.

For declaring that the system is economically feasible, the benefits from the project should exceed or at least to the equal to the cost of development.

REQUIREMENT VALIDATION :
Requirement validation examines this specification to ensure that all the system requirements have been stated unambiguously.

These inconsistent, error have been detected and corrected and the work products confirmed to the standard.

Source of the requirement are identified, final Statement of requirement has been examined by original source.

Requirements related to main requirements are founds.

Requirements are clarifying stated and are not misinterpreted.

All sources of requirements are covered to get a maximum requirement.

All method of finding requirements is applied.

FUNCTION OF THE SYSTEM:
Use-Case:
In software and systems engineering, a use case is a list of steps, typically defining interactions between actor and a system, to achieve a goal.

The actor can be a human, an external system, or time.

In systems engineering, use cases are used at a higher level than within software engineering, often representing missions or stakeholder goals.

The detailed requirements may then be captured in Systems Modeling Language or as contractual statements
Artist and admin:

Fig:4.1 use-case(artist-admin)
recruiter and admin:

fig:4.2 use-case(recruiter-admin)
Sequence Diagram:
The well-known Message Sequence Chart technique has been incorporated into the Unified Modeling Language (UML) diagram under the name of Sequence Diagram.

A sequence diagram shows, as parallel vertical lines, different processes or objects that live simultaneously, and, as horizontal arrows, the messages exchanged between them, in the order in which they occur.

This allows the specification of simple runtime scenarios in a graphical manner.

The well-known Message Sequence Chart technique has been incorporated into the Unified Modeling Language (UML) diagram under the name of Sequence Diagram. A sequence diagram shows, as parallel vertical lines, different processes or objects that live simultaneously, and, as horizontal arrows, the messages exchanged between them, in the order in which they occur. This allows the specification of simple runtime scenarios in a graphical manner.

ARTIST

Fig:4.3 sequence diagram(artist)
RECRUITER

Fig:4.4sequence diagram(recruiter)
ACTIVITY DIAGRAM:
Admin:

Fig:4.5activity diagram(admin)
Artist:

Fig:4.6activity diagram(artist)
Recruiters:

Fig:4.7activity diagram(recruiters)
Data Modeling:
E-R Diagram:
In software engineering, an entity–relationship model (ER model) is a data model for describing the data or information aspects of a business domain or its process requirements, in an abstract way that lends itself to ultimately being implemented in a database such as a relational database.

The main components of ER models are entities and the relationships that can exist among them, and databases.

An entity-relationship model is a systematic way of describing and defining a business process.

The process is modeled as components (entities) that are linked with each other by relationships that express the dependencies and requirements between them, such as: one building may be divided into zero or more apartments, but one apartment can only be located in one building. Entities may have various properties (attributes) that characterize them.

Diagrams created to represent these entities, attributes, and relationships graphically are called entity–relationship diagrams.

Fig:4.8E-R diagram
Class Diagram:
In software engineering, a class diagram in the Unified Modeling Language (UML) is a type of static structure diagram that describes the structure of a system by showing the system’s classes, their attributes, operations (or methods), and the relationships among objects.

The class diagram is the main building block of object oriented modeling.

It is used both for general conceptual modeling of the systematic of the application, and for detailed modeling translating the models into programming code.

Class diagrams can also be used for data modeling.

The classes in a class diagram represent both the main objects, interactions in the application and the classes to be programmed.

In the diagram, classes are represented with boxes which contain three parts:
The top part contains the name of the class. It is printed in Bold, centered and the first letter capitalized.

The middle part contains the attributes of the class. They are left aligned and the first letter is lower case.

The bottom part gives the methods or operations the class can take or undertake. They are also left aligned and the first letter is lower case.

Fig:4.9class diagram
Data Dictionary:
Artist registration:
Field name Datatype Size Constrains description
id integer – Primary key Artist id
password varchar 12 – Password of account
name varchar 25 – Name of artist
city varchar 15 – City of artist
Email id varchar 20 – Mail id
Phone no integer 10 – Phone no
languages varchar 30 – Languages known
Artist type varchar 10 – Group /solo/duet
profile media – – Profile pic of artist
Table:4.1 artist registration
Recruiter registeration:
Field name Datatype Size Constrains description
id integer – Primary key Recruiters id
password varchar 12 – Password of account
name varchar 25 – Name of recruiter
category varchar 15 – Category
Organization name varchar 10 – Name of organization
Email id varchar 15 – Mail id
Phone no integer 10 – Mobile no
Table:4.2 recruiter registration
Job:
Field name Datatype Size Constrains description
Job_idinteger – Primary key job id
title varchar 12 – Title of the job
category varchar 20 – Category of job
description varchar 50 – Description of job
Table:4.3 job
Notification:
Field name Datatype Size Constrains description
noti_idinteger – Primary key Notification id
description varchar 12 – Content of notification
Table: 4.4 notificationContact us:
Field name Datatype Size Constrains description
message_idinteger – Primary key Message id
name varchar 12 – Name of the person
Email id varchar 20 – Email id of person
message varchar 50 – Message content
Table: 4.5 contact us
Main Modules of New System
The water tank purification can be used to manage water tanks by AMC. It will support both standalone and also networking environment.

The main modules involved in this system are: 1 Login
2 Admin access
3 vender4 User interactionModule Wise description
Login and contact us:
Login module is used to check whether the user id authorized person or not.

For this user should give correct user name and password. The different types of user are: admin, vender, citizens.

Admin access
The tanks are managed by admin and also admin is responsible for assigning tasks to vender. He is responsible for managing different tasks such as time scheduling, area, tanks, notifications etc.

Vender
Vender is responsible for completing its assigned task. The task is assigned by admin. Vender manages its area. And he manages the labors to complete tasks. He generates monthly reports and sends it to amc.

User interaction
User can see the list of tanks and time schedule. Also gives suggestion to amc. They can give feedbacks about services. Also am send complains. By using this site he can directly interact with amc.

area wise management of tanks
By using this module tanks are displayed and managed by zone, ward and its particular area.
Justification:
Java is best open source programming language to develop web application for small and large enterprise with portable implementation.

MySql is also best open source database engine to work.

Combination of both will give great web application as output.

CHAPTER 5 SYSTEM DESIGN
Flowchart
admin
Fig:5.1flowchart
artist
Fig:5.2artist
Recuirter
1339215139636500

Fig:5.3recruiter-flowchart

x

Hi!
I'm Amelia

Would you like to get a custom essay? How about receiving a customized one?

Check it out
x

Hi!
I'm Annette!

Would you like to get a custom essay? How about receiving a customized one?

Check it out