INDORE INSTITUTE OF SCIENCE &

TECHNOLOGY

VIRTUAL SOCIAL PROJECT

FRAMEWORK

Guided By: Submitted By:

Dr. Upendra Yadav
Mr. Rahul Bakshee
Gyanendra Singh
 CONTENTS

 .
1. Project definition
2. Analysis
3. Designing
4. Working Demo.
5. Reference
 Project definition
 The problem which is to be solved by our project is basically
related to government sectors. The government sectors like
Municipal Corporation, an other government offices require
various software for their functionality. But whenever they
want any software they have to search for the software
providing organization or such software engineers who can
fulfill their requirement by proving efficient software. They
do not have an intermediate platform between them and the
software providers.
 Our main aim to make a web portal. To provide
a platform for government sector for getting the new
readymade software by submitting their problem on this
portal and directly interact with software providers.

 Features of our Portal
 The portal is an online application.
 The basic functionality of the project is to put the requirement of public

sector related to software field online so that they get the online
application by the software professionals, by the software organization
or by the student of software engineering students. Thus the problem
of searching the software provider can be solved.
 The other functionality of the project is that the software professionals,

the software organization or the student of software engineering can

apply directly on the portal for providing readymade software to the
various organizations.
 The project reduces the paper work in the public sector as they do not

have to give advertisement for software professionals for there work in

newspaper and on other sources. Thus time money and effort are
saved.
 ANALYSIS

 1. ER Diagram
 C_contactno
C_profile
S_city S_pincode

S_loginid C_website
C_name
S_contactno

S_areaofinterest
C_id C_role
S_address
STUDENT COMPANY
S_qualification * 1
S_name
* *
S_role
S_id

Work on

Work on
Work for
P_id
Work for
1 *
PROJECT P_name

* * P_details

P_status
Maintain
record
allot
A_city
A_contactn
O_id
o
A_pincode
* * 1
O_name ORGANIZATION ADMIN
O_prjname
1 A_id

A_address
O_address
A_mail id

O_contactno O_problemdefinition A_pwd A_name

ER DIAGRAM
 3. Use Case Diagram

USE CASE DIAGRAM

SEND RESUME

READ PROBLEM

SEND REQUEST FOR

COMPANY PROJECT

HIRE THE PROJECT

SEND COST

<<INCLUDE>>

COST CALCULATION
MAINTAIN THE
RECORD
STUDENT

LOGIN
SEND PROFILE

ADMINISTRATOR

GIVE PROBLEM
DEFINATION

SELECT STUDENT

ORGANIZATION

GIVE ALL ASPECTS

OF PROJECT

GIVE DEADLINE

APPROVAL OF
PROJECT
 Use Case Description

 Use Case Specification:

 1. Login:

 a. Brief Description: This use case describes how a computer user logs
into the system.
 b. Flow of Events:

 i.Basic Flow: This use case starts when the actor wishes to login the

system.
 The system requests that the actor enter his/her username and password for

accessing Portal services.

 The actor enters his/her id and password.

 System validates the entered name and password and logs the actor into the

system.
 ii.Alternative Flow: Invalid User Id /Password

 If in the basic flow, the actor enters an invalid user id and /or password,
the System displays an error message.
 The actor can choose to either return to the beginning of the basic
flow or cancel the login, at which point the use case ends.
c. Special Requirements: None.
d. Pre-Conditions: The User must have a valid user id &
Password
e. Post-Conditions: If the use case was successful, the actor is
now logged into the system.

2. Registration for new user:

a. Brief Description:. This use case describes how a computer
user registers into the system.
b. Flow of Events:
i.Basic Flow: This use case starts when the actor wishes to
register on the system.
The system requests that the actor to fill the registration form and
thus get his/her username and password and got registered.
The actor enters his/her id and password and other information
for registering to portal.
 System validates the entered name and password and other
information and finally, registers the actor into the system.

 ii.Alternative Flow: Invalid User Id /Password or other field

information
 If in the basic flow, the actor enters an invalid user id and /or
password or other field information, the System displays an
error message. The actor can choose to either return to the
beginning of the basic flow or cancel the registration, at which
point the use case ends.
 c. Special Requirements: None.
 d. Pre-Conditions: The User must not be registered earlier.
 e. Post-Conditions: If the use case was successful, the actor
is now registered into the system and an account is created
for the respective client.
 3. Submit resume or profile:
a. Brief Description: This use case describes how a computer
user can submit their resume (by student) or profile (by company).
b. Flow of Events:
i. Basic Flow: This use case starts when the actor wishes
to submit resume or profile.
•The system requests that the actor is a student then enters
Submit resume & if it is a company then enters submit profile.
•The actor enters his resume and profile.
•System validates the entered information and finally, stores the
resume of the student or profile of the company.
ii. Alternative Flow: Invalid data entry in the information
field.
If in the basic flow, the actor enters an invalid data entry in
the information field , the System displays an error message. The
actor can choose to either return to the beginning of the basic flow
or cancel the submitting their resume or profile, at which point the
use case ends.
 c. Special Requirements: None.
d. Pre-Conditions: The User must not be registered earlier
and logged in properly.
e. Post-Conditions: If the use case was successful, the
resume or profile is now stored into the database of the
system.

4. Submit problem or read problem:

a. Brief Description: This use case describes how a
organization submit problem that could be viewed by students
and companies.
b. Flow of Events:
i. Basic Flow: This use case starts when the actor wishes
to submit problem & other want to view on the system.

The system requests that the organization enters the problem

definition regarding their requirement.
The actor such as student or companies can view the problem
definition entered.
System validates the entered information and finally, displays the
information from the Database of the system.
c. Special Requirements: Problem should be technical oriented.
d. Pre-Conditions: None.
e. Post-Conditions: If the use case was successful, the problem is
now displayed to the viewer.

5. Select student & enter into discussion forum:

a. Brief Description: This use case describes how actors can
interact with each other.
b. Flow of Events:
i. Basic Flow: This use case starts when the actor wishes to
interact with another actor.
The system requests that the organization must select the student
or company.
The organization enters into the discussion forum with the
selected student or company.
 
4.3 Special Requirements: Both user should be registered.
4.4 Pre-Conditions: None.
4.5 Post-Conditions: If the use case was successful.
6. Get approval & hire the project:
a. Brief Description: This use case describes how a computer
user gets approval from the organization and hires the project.
b. Flow of Events:
i. Basic Flow: This use case starts when the
organization finalize the student or company to work for them.

•The organization enters the approval information.

•The student can view the approval information and then hires the
project.
•System validates the entered information into the Database.
c. Special Requirements: None.
d. Pre-Conditions: The organization can select only the.
e. Post-Conditions: If the use case was successful, then student or
company hires the project.
 1. Sequence Diagram
1. Sequence Diagram

1. Sequence Diagram
2. Activity Diagram
 3. State Chart Diagram [Composite state]

[Initial State]
[Transition]
Connect to Data Base

Log [Action]
in
Enter User ID
Idle

Login Login
failed again
Matching
Exit Enter Password
Log Out

Login [Nested State]

[State] Accepted
Main Screen
Exit

Final State
Connect
to Data
Base
Submit Submit
Back Back
Solution solution
Back Get approval for
project
Back

Solve Project
Register Send
Request View Project
Connect
to Data Connect
Base to Data Connect
Base to Data
Submit Base

Send
Fill
request or
registration project
form

View Problem View project already

definition made

STATE TRANSITION DIAGRAM FOR

STUDENT
 [Composite state]

[Initial State]
[Transition]
Connect to Data Base

Log [Action]
in
Enter User ID
Idle

Login Login
failed again
Matching
Exit Enter Password
Log Out

Login [Nested State]

[State] Accepted
Main Screen
Exit

Final State

Back
Back
Back

Register
Select
Connect Submit
to Data Connect
Base to Data Decide
Base Problem
Submit definition
Select
Give student &
organization give
profile approval

View students Submit

record

STATE TRANSITION DIAGRAM FOR

ORGANIZATION
 4. Designing
1. Class Diagram
USER * * WORK STATION

1
STUDENT COMPANY
1
*
ORGANISATION ADMIN
S_ID
S_NAME
S_ADDRESS
C_ID A_MAILID
S_QUALIFICATION O_ID
C_NAME A_PWD
S_MAILID O_NAME
C_PROFILE A_NAME
S_CONTACTNO O_ADDRESS
C_CONTACTNO A_ADDRESS
S_CITY O_CONTACTNO
C_WEBSITE A_CONTACTNO
S_PINCODE O_PRBLMDEFINATION
C_ROLE A_CITY
S_AROFINTEREST
A_PINCODE
S_LOGINID
S_PWD
S_ROLE

LOGIN() LOGIN() LOGIN()

RETRIEVE_PRJ() RETRIEVE_PRJ() SEND_PRBLM() LOGIN()
SEND_REQUEST() SEND_REQUEST() SELECT_STUDENT() MAINTAIN_RECORD()
HIRE_PRJ() HIRE_PRJ() SEND_RESPONSE() UPDATE()
SEND_COST() SEND_COST() APPROVE_COST() ADD()
SUBMIT_PRJ() SUBMIT_PRJ() SEND_DEADLINE() DELETE()
LOGOUT LOGOUT() LOGOUT() LOGOUT()

* * * 1 1 1

AUTHORISATION

ROLE DIRECTORY
VALIDATION

START_SESSION()

CLASS DIAGRAM
•2. Collaboration Diagram

Register and send Request for project

STUDENT SOTWARE INTERFACE

Get project

Select
student
and give
Send list of
approval
register
or the
student
project
request

Request for updates

ADMINISTRATOR Organisation

Updates
4. Working Demo
 Future Scope
 This project can be used for the advertisement purpose by the
industries & organization which are directly or indirectly related
to public sector for the publicity of their products.
 The project can also be expanded further for software
professional or & organization provider for the whole state’s
government or on national level.
 The project can also expand for the other organization and
private organization.
 Software industries can also join the portal as they provide reads
made various organizations 
 The future use for this project will put a new thing in the mind
for use in a large scale. It can be also use in various institutes and
organization which require software’s. This is a simple
application with larger extensible and convenient uses.
 Limitations
 As with every project, this project also has got some of
the limitations which are:
 The project has the limitation that it can communicate
between public sector and software provider only.
 Another drawback of the project is that it does not have
the list of software provider until or unless they apply
for a particular project mentioned in the project.
 5. References
 Pressman
 Korth
 www.msdn.microsoft.com/library/default.asp?
url=/library/en-us/dnasp/html/asptutorial.asp (ASP
tutorial)
 www.functionx.com/sqlserver/ (SQL-server tutorial)
 www.w3schools.com (Many Tutorials Available)
 Grady Booch “Unified Modeling Language” fourth
Edition