Preliminry report

1. INTRODUCTION

The project is dedicated to automation of all project work which is done by students

and project coordinators manually. These will be useful from group formation to project

submission. All the phases such as group formation, project approvals, FTR’s, project

submission and evaluation will be possible to done through this web application. It will

help to keep the track of all the project work and in the evaluation process of projects.

This web application will work in two modules. One will take care of all the online

project work, submission and work plan. Another module will evaluate the overall

progress of students and their projects. The evaluation of project will be done by using

software engineering approach to assess the quality of project. This web application will

make it easy to view particular projects or related information as this involves a proper

classification according to domains.

1.1 PROJECT IDEA

The web application provides the facility to students to search information about

groups formed, faculty and their domains. Also information on past projects is available.

The plan of action to be followed is also provided. This web application provides a

platform for guide student communication. All the deadline notifications will be sent to

students regularly. Also the remarks given by faculty member can be known anytime

students wish. The project will be given ratings by the faculty at all levels. At the time of

final evaluation the staff can refer the graphs representing the overall performance. Thus

the web application helps in proper communication and systematic evaluation.

1.2 MOTIVATION OF PROJECT

The aim is to develop a web application where students and guides will be able to carry

out project related activities. This portal will be a great relief to the students and the

respective guides. Tasks like group formation, project approval and guide allocation,

Vishwakarma Institute of Information Technology 2013-20141

submission of synopsis, communication on various project aspects will be done online

more efficiently. Also with this efficient web application we can have systematic follow

u up of all the activities and proper evaluation of the same.


2. PROBLEM DEFINITION

2.1 LITERATURE SURVEY

2.1.1 Research on PHP development

PHP is one of the leading web development languages, however,the development

model of existing PHP organizes without a structure, which mixes the code of data access,

the processing of business logic ,and web presentation layer together, as a relult, it brough

about many problems in the web applications, meanwhile, it could not meet the rapid

development of web apply any more. In this paper, a implementation of PHP based on

MVC design patterns – FDF framework was provided for PHP developers, which can

offer a framework for web applications, separate the data, view and control of web

applications, afford to achieve loose coupling, thereby enhanced the efficiency, reliability,

maintainability and scalability of application development.

2.1.2 Research on Yii framework

Yii is a high-performance PHP framework best for developing Web 2.0 applications.

Yii helps Web developers build complex applications and deliver them on-time. This is

often the accurate, and most concise response to inquires from those new to Yii. Yii is a

free, open-source Web application development framework written in PHP5 that promotes

clean, DRY design and encourages rapid development. It works to streamline your

application development and helps to ensure an extremely efficient, extensible, and

maintainable end product.

Being extremely performance optimized, Yii is a perfect choice for any sized project.

However, it has been built with sophisticated, enterprise applications in mind. You have

full control over the configuration from head-to-toe (presentation-to-persistence) to


conform to your enterprise development guidelines. It comes packaged with tools to help

test and debug your application, and has clear and comprehensive documentation.

2.1.3 Data Clustering

Cluster analysis or clustering is the task of grouping a set of objects in such a way that

objects in the same group (called a cluster) are more similar (in some sense or another) to

each other than to those in other groups (clusters). It is a main task of exploratory data

mining, and a common technique for statistical data analysis, used in many fields,

including machine learning, pattern recognition, image analysis, information retrieval, and

bioinformatics.

Cluster analysis itself is not one specific algorithm, but the general task to be solved. It

can be achieved by various algorithms that differ significantly in their notion of what

constitutes a cluster and how to efficiently find them. Popular notions of clusters include

groups with small distances among the cluster members, dense areas of the data space,

intervals or particular statistical distributions. Clustering can therefore be formulated as a

multi-objective optimization problem. The appropriate clustering algorithm and parameter

settings (including values such as the distance function to use, a density threshold or the

number of expected clusters) depend on the individual data set and intended use of the

results. Cluster analysis as such is not an automatic task, but an iterative process of

knowledge discovery or interactive multi-objective optimization that involves trial and

failure. It will often be necessary to modify data preprocessing and model parameters until

the result achieves the desired properties

The convergent K-means algorithm and its ANN equivalent, the Kohonen net, have

been used to cluster large data sets. The reasons behind the popularity of the K-means

algorithm are:

1. Its time complexity is O(mkl), where m is the number of instances; k is the number of

clusters; and l is the number of iterations taken by the algorithm to converge. Typically, k


and l are fixed in advance and so the algorithm has linear time complexity in the size of

the data set.

2. Its space complexity is O(k+m). It requires additional space to store the data matrix. It

is possible to store the data matrix in a secondary memory and access each pattern based

on need. However, this scheme requires a huge access time because of the iterative nature

of the algorithm. As a consequence, processing time increases enormously.

3. It is order-independent. For a given initial seed set of cluster centers, it generates the

same partition of the data irrespective of the order in which the patterns are presented to

the algorithm. However, the K-means algorithm is sensitive to initial seed selection and

even in the best case, it can produce only hyper spherical clusters. Hierarchical algorithms

are more versatile.

2.2 PROBLEM STATEMENT

The problem is to design efficient tool for all project management work and evaluate

the quality of past projects.

The problem of Designing tool for project management.

Affects The engineering institutes conducting

project activities.

The impact of which is Quality analysis will be done more

accurately and efficiently

A successful solution

would

It will help to process the evaluation and

dataset handling efficiently.

Table 1: Problem Statement


2.3 GOALS AND OBJECTIVES

• The objectives of this project were:

• Automation in overall college project work.

• Design a model using software engineering approach for smooth conduction.

• Systematic evaluation of project work.

• Design method for proper evaluation.

• Provide single platform for all project activities.


3. SOFTWARE REQUIREMENTS SPECIFICATION

3.1 INTRODUCTION

3.1.1 Project scope

The scope of our project is limited to the engineering projects. There are certain norms for

following up and evaluation of the project approved by individual colleges. According to

the norms and formats set by our institute the application is been designed and

implemented. But it may be modified to fit into the criteria of other institutes. With this

we promote paperless transactions. Also a database of current and passed projects is

maintained. These are helpful for future references.

3.1.2 User classes and characteristics

USER CLASSES

a. Use Case ID = A001

|b. Use Case Name = Project Management Tool

c. Actors = Students, Project Coordinator(Admin), Guide

d. Prerequisites = Site to be opened on the browser.

e. Steps:-

i. Specify whether you have an account on the website or not.

ii. If yes login into your account.

iii. If a new user then create an account.

iv. Form project group.

v. Give the domain as per your area of interest and interact with respective teachers for

project topic.

vi. Apply for approval.

vii. Get the details of further project proceedings.

USER CHARACTERISTICS

• This system will be used by the students of final year.


• The students can perform the following functions:-

• Browse the information provided like past projects, faculty and their domain.

• Get the suggestions by the guides and improve accordingly.

3.1.3 OPERATING ENVIRONMENT

3.1.4 Design And Implementation Constraints

The web application must be designed to allow web usability. That is, the product

must be designed in such a way that will be easy to use and visible on most of the

browsers.

3.1.5 Assumptions and Dependencies

Our assumption for this web application is that user has access to internet. The

dependency of evaluation process is on the input given by guides. More appropriate result

will give more effective evaluated results.

3.2

3.3 SYSTEM FEATURES

3.2.1 All the validation at the client side is carried out using filters. This feature will

prevent user from sending malicious content to the server.


Software used Description

Operating system We have chosen Windows operating system for its best

support.

PHP Server Pages To implement the project we have chosen PHP Server Pages

for its ability to combine HTML and JAVA code together for

dynamic web application.

3.2.2 The UI is well designed to have ease of access.

3.2.3 The database is provided to store all project data at one place.

3.2.4 The proper evaluation is being done to analyse a quality of work.

3.2.5 A platform is being provided for easy communication between the students and

faculties.

3.2.6 Data mining techniques are being implemented to categorise projects well

according to various domains.

3.2.7 Data duplication is being avoided by keeping log of the system.

3.2 EXTERNAL INTERFACE REQUIREMENTS

3.3.1 User Interfaces

When the customer first goes to our website he is welcomed at “Home Page”

where some information is provided about our tool. User is also provided with options in

different tabs like Login, Signup, About us and Contact us. To get a view of the past

projects that are available for the member, he first needs to log in if he is already

registered or create a new account if he is a new member. Once member has logged in to

the portal he can select, perform various actions such as browsing through past projects,

get statistical details of past years. A new member will be able to perform various

activities from group formation to project evaluation and submission.

3.3.2 Hardware Interfaces

Not Applicable.

3.3.3 Software Interfaces

We have connected our system to MySQL database where all the details of the new

members will be stored and also where past data is saved.


3.4 NON FUNCTIONAL REQUIREMENTS

3.4.1 Performance requirements

• The time required to fetch details of past projects should be less

• The result generated regarding the past years overall performance and past year

project details must be precise.

• Evaluation of the project must be done efficiently.

• System should not degrade performance

3.4.2 Security requirement

• The user should be authenticated by providing the user – name and

password.

• The database should be secured from personnel.

• Only administrator should have permission to manage the database.

3.4.3 Software Quality Attributes

The quality attributes of a proposed system can be evaluated by determining the summary

of the output produced by the system.

• Availability:

a. Any time the students can login into the system and proceed with it. Also they can

view the comments given by their respective guides. Communicate with their

mentors.


b. Guide can look over the work done by students. Give suggestions. Rate the work

done on every stage. Refer the pictorial representations of students performance

and give their final evaluation.

• Correctness

a. The system works correctly and efficiently if it is used in the way mentioned in the

user manual.

b. The accuracy of the system should not dependable on the number of users using it.

• Readability

a. The system provides a very easy to use interface to the user. It involves no

complicated procedures

b. Since all users are familiar with the usage of browsers, no specific training is

required.

c. The system is user friendly and self – explanatory

• Integrity

a. Only administrator has the rights to enable / disable links.

b. The system is internally consistent i.e. all internal logic and data makes sense

when operating together.

• Maintainability

a. The maintenance cost of the system is very low.

b. Maintenance of this particular application would be a part of the development

of its higher versions which might also bring in more scope of the system.

c. Also the data about the past projects is to be maintained in the database.

• Portability

a. The system is completely portable since it is a website driven tool.


b. The user only needs an internet connection and a browser to use our system.


3.5 OTHER REQUIREMENTS

3.5.1 Database requirements

This system requires a database to store information of the members of our system.

In the database the details of the previous year’s projects will also be stored which

will be required for the future reference.

3.5.2 Internalization requirements

This Web application runs all supported browsers.

3.5.3 Legal requirements

Genuine developement tools must be used.

Genuine PHP Framework must be used.

3.6 ANALYSIS MODEL

The analysis model describes the structure of the system or application that is being

modeling. It consists of Data Flow Diagrams, Class diagrams and Use-Case Diagrams that

describe the logical implementation of the functional requirements that has been identified

in the use case model.


3.6.1 Use Case Analysis

Figure 1: Use case diagram 1

Figure 2: Use case diagram 2


Template:

ID: U1.0

Title: Communication

Description: All students need to register in order to get access to all the project

related activities and to communicate with the concerned faculty.

Primary Actor: Student

Preconditions: Student is logged into system

Postconditions: Student is registered

Main

Success Scenario:

1. System displays list of other registered users.

2. Student selects his group for approval and also submits his

project title.

3. Student clicks "Submit" button.

4. System processes students request and displays a confirmation

message.

Extensions: 1. Student must be registered and logged in to make any requests.

2. Group must be finalised and approved before he can seek

approval for project title.

3. Only after title approval student can submit his plan of action

Frequency of Use: A few times every quarter

Status: Pending

Owner: VIIT

Priority: P5 – High


3.6.2 Activity Diagram

Figure 3: Activity Diagram

3.6.3 Data flow diagram

A data flow diagram (DFD) is a graphical representation of the "flow" of data through

an information system, modeling its process aspects. Often they are a preliminary step

used to create an overview of the system which can later be elaborated. DFDs can also be

used for the visualization of data processing (structured design).A DFD shows what kinds

of information will be input to and output from the system, where the data will come from

and go to, and where the data will be stored. On a DFD, data items flow from an external

data source or an internal data store to an internal data store or an external data sink, via

an internal process.


Figure 4: Data Flow Diagram – Level 0

Figure 5: Data Flow Diagram – Level 1


3.7 System Implementation Plan

Figure 6: Project Plan


4.1 System Designs

4.1 System Architecture

Figure 7: System Architecture

4.2 UML Diagrams

4.2.1 Class Diagram


4.2.2 Package Diagram

Figure 9: Package Diagram

4.3 Behavioral Design and description

Figure 10: State Diagram


5. TECHNICAL SPECIFICATION

It is a detailed description of technical requirements, usually with specific acceptance

criteria, stated in terms suitable to form the basis for the actual design development and

production processes of an item having the qualities specified in the operational

characteristics.

5.1 Advantages

• Proper Data Clustering will be done.

• Statistical analysis will be done for past records.

• Single platform will take care of all project activities.

5.2 Disadvantages

Not as such.

5.3 Application

• Tool will be used for assessing the quality of project. This quality can be improved

by continuous assessments, for which related functionalities like log maintenance

and notification features are provided.

• It can also be used in various industries and firms where project activities are

conducted and hence can be evaluated efficiently using this tool.

• The tool can be used in colleges where project activities are being carried out.


6. TEST SPECIFICATION

Software testing provides an objective, independent view of the software to allow the

business to appreciate and understand the risks of software implementation. Test

techniques include, but are not limited to, the process of executing a program or

application with the intent of finding software bugs (errors or other defects).

6.1 TESTING STRATEGIES

6.1.1 White Box Approach :

Internal code is considered for testing. Testing based on executing the program with

the intent of finding errors. Test case based on the information regarding the internal

structure of the component or system under test. Various models are used for test case

generation.

6.1.2 Black Box Approach :

Internal code is not considered for testing. Testing based solely on analysis of

requirement. Test case based on specifications Black-box techniques are based on an

analysis of the test basis documentation, including both functional and non-functional

aspects. They do not use any information regarding the internal structure of the

component or system under test.

Testing will be done for the functional units like whether they are working properly

as per requirements or not. Also testing for nonfunctional requirements like performance,

scalability, accuracy will be done.


7. CONCLUSION

Thus we have completed the analysis on project management tool successfully where

the main motto of the project is to provide a single tool for all project data set handling

and proper evaluation of the quality of projects. The tool is designed in order to maintain

the efficiency and accuracy in quality evaluation and working.


8. APPENDIX A

Data Mining

Data Mining is the computational process of discovering patterns in large data

sets involving methods at the intersection of artificial intelligence, machine

learning, statistics, and database systems. The overall goal of the data mining process is to

extract information from a data set and transform it into an understandable structure for

further use.


http://en.wikipedia.org/wiki/Artificial_intelligence

http://en.wikipedia.org/wiki/Database_system

http://en.wikipedia.org/wiki/Statistics

http://en.wikipedia.org/wiki/Machine_learning

http://en.wikipedia.org/wiki/Machine_learning

10. BIBLOGRAPHY

[1] Jing Li, Lin Huang, Wei Cui: The Research of PHP Development FrameworkBased on MVC Pattern

[2] Keiji Hokamura, Shin Nakajima: Aspect-Oriented Development of PHP-based Web

Applications

[3] Odokoya, O.H. Adagunodo: An Improved Data Clustering Algorithm for MiningWeb Documents


Education

Preliminry report