Chapter 1

INTRODUCTION
A Knowledge Transfer Platform is a blog (a blend of the term web log) is a type of
website or part of a website, which is the publication of regular articles over time in some
area of personal or professional interest. Knowledge transfer platform can be usually
maintained by an individual with regular entries of commentary, descriptions of events, or
other material such as graphics or video. Blog can also be used as a verb, meaning to
maintain or add content to a blog.
There are many different types of blogs, differing not only in the type of content, but
also in the way that content is delivered or written. The software for writing blogs can be
divided into user hosted (software application installed by web log authors to run on their
own system) and developer hosted (software services operated by the developer, requiring
no software installation for the blog author.)
Developer-hosted services are Blogger.

1.1 PROJECT SCOPE

The scope of Knowledge Transfer Platform (KTP) is to vastly expand the following
field
Personal blogs
The personal blog, an ongoing diary or commentary by an individual, is the traditional, most
common blog. Personal bloggers usually take pride in their blog posts, even if their blog is
never read. KTP often become more than a way to just communicate; they become a way to
reflect on life, or works of art. Blogging can have a sentimental quality. Few personal blogs
rise to fame and the mainstream but some personal blogs quickly garner an extensive
following. One type of personal blog, referred to as a microblog, is extremely detailed and
seeks to capture a moment in time. Some sites, such as Twitter, allow bloggers to share
thoughts and feelings instantaneously with friends and family, and are much faster than
emailing or writing.
Corporate and organizational KTP
A KTP can be private, as in most cases, or it can be for business purposes. Blogs used
internally to enhance the communication and culture in a corporation or externally for
marketing, branding or public relations purposes are called corporate KTP. Similar blogs for
clubs and societies are called club blogs, group blogs, or by similar names; typical use is to
inform members and other interested parties of club and member activities.
By genre
Some blogs focus on a particular subject, such as political blogs, travel blogs (also known as
travelogs), house blogs, fashion blogs, project blogs, education blogs, niche blogs, classical
music blogs, quizzing blogs and legal blogs (often referred to as a blawgs) ordreamlogs. Two
common types of genre blogs are art blogs and music blogs. A blog featuring discussions
especially about home and family is not uncommonly called a mom blog. While not a
legitimate type of blog, one used for the sole purpose of spamming is known as a Splog.
By media type
A blog comprising videos is called a vlog, one comprising links is called a linklog, a site
containing a portfolio of sketches is called asketchblog or one comprising photos is called a
photoblog. Blogs with shorter posts and mixed media types are called tumblelogs. Blogs that
are written on typewriters and then scanned are called typecast or typecast blogs; see
typecasting (blogging).
Science
A means of spreading data or discussing activities or results.
Social
Used to maintain social networks between people.
Consumer-generated advertising in KTP
Consumer-generated advertising is a relatively new and controversial development and it has
created a new model of marketing communication from businesses to consumers. Among the
various forms of advertising on blog, the most controversial are the sponsored posts. These
are blog entries or posts and may be in the form of feedbacks, reviews, opinion, videos, etc.
& usually contain a link back to the desired site using a keyword/s.
Many blogs provide commentary or news on a particular subject; others function as more
personal online diaries. A typical blog combines text, images, and links to other blogs, Web
pages, and other media related to its topic. The ability of readers to leave comments in an
interactive format is an important part of many KTP. Most blogs are primarily textual,
although some focus on art (art blog), videos (video blogging), music (MP3 blog), and audio
(podcasting). Micro blogging is another type of blogging, featuring very short posts.

1.2 PROJECT OBJECTIVE
By the analysis on website, It was expected that for common people to develop
website, they have to face many problems and also they want to share their knowledge,
technology, articles, etc.
The objective of KTP is to provide its entire user with easy access to relevant, and by
using provide them Choosing facility to component.
People will make their blog using choose their style, template, etc.


















Chapter 2
Litature survey




















Chapter 3
Ruby on rails & Knowledge transfer platform

3.1 WHAT IS RUBY?
Ruby is an open-source, multi-paradigm, interpreted programming language (abit of a
mouthful I know! I'm going to explain it, I promise!). Ruby was createdby Yukihiro "Matz"
Matsumoto, a very fine Japanese gentleman who currently resides in Shimane Prefecture,
Japan; Matz's work on the language was started on February 24, 1993 (commonly considered
the birthday of the language; I hear that over in Japan they roll out a two-story cake and sing)
and released to the public in 1995. Ruby is often hailed as one the most expressive and
concise languages available to developers today. In that spirit of expressiveness, let's look at
exactly what it all means. Let us now eviscerate these verbal furbelows with conviction!
Open Source The official implementation of the language is free software distributed under
the GPL and the Ruby open source license. If you're unaware of what "open source" means,
then look at it this way: Matz programmed the entire Ruby interpreter and library, then gave
away the code he used to do it. Since the source code is available, people can now take it and
improve it. Many people take the code, improve it, and Matz (and his crack team of
maintainers) integrate their changes back into the main source code. The benefit of open
source is chiefly that you get a lot more minds working on a project than a proprietary project
(and typically for free to boot!).
Multi-Paradigm Like to write code in a functional style a la Haskell or Scheme? That's cool;
Ruby does that. Really dig object orientation like Java or Smalltalk? No problem; Ruby
handles that, too. Prefer to use a procedural (a.k.a. imperative) style like Forth or Ada? Ruby
can "get its procedure on" as good as any other language! Don't know what any of those
mean but just really want to program? Excellent! Ruby is a multi-paradigm language because
it doesn't constrain to a single programming mindset; you can use any of the aforementioned
programming paradigms with no problems in Ruby. You can pick the one you prefer (or the
easiest for you to learn) and go with it: Ruby doesn't mind. Unlike some other languages, it
doesn't get jealous and give you "errors" if you break it off with objects and decide to go
steady with closures instead.
Interpreted If you've used something like Assembly, Pascal, Fortran, or C/C++, you've used
a compiled language. "Compiled" means that you've had to run your code through a little
compiler and it spits out some sort of native code that will run without any sort of
interpretation by the computer other than by the operating system itself. This can become
time consuming as your project grows larger and larger, and sometimes can even be a severe
hindrance to productivity.
Oh, but there is another way! Ruby is an interpreted language, which means that there is an
interpreter that reads your code and then emits native code to the operating system. Maybe
this diagram will make more sense...


Figure 1: An overview of how Ruby handles programs.

There is a bit more to it than that (e.g. you have to coax Jeff out of his box), but that's the
general concept. Code goes in, Ruby plays around with it, program comes out. When running
Ruby code, you have a few options. The first option you have is to create a file with your
source code in it, and then tell Ruby to execute that file by giving it as a command line option
to the ruby command. Your next option is that you can use your editor's Ruby runner (if it
has one) by using their shortcut; for example, SciTE has this feature that you can use by
pressing F5. The last option is to use an interactive shell like irb or fxri; these shells give you
a "Ruby prompt" at which you can type in lines of Ruby code and have them immediately
executed. I used irbextensively in writing this book because it allows speedier feedback than
running from a file. These prompts are possible because Ruby is a dynamic language ran in
an interpreter. The interpreted nature of Ruby allows it to have many of the features that
make it so great. Compiled programs are not nearly as dynamic as interpreted ones because
they don't (usually) allow for runtime change to code or the application itself.
Because interpreted programs are simply, well, interpreted from their original source (or a
slightly compiled bytecode), they can allow for more far-reaching runtime interaction.
We'll discuss all of this a lot more later as these features reveal themselves; now we need to
make sure you actually have Ruby. Otherwise, these features will be like chasing the wind
when it's running faster than you: meaningless!

3.2 WHAT IS RAILS?
Currently much of the excitement surrounding Ruby can be attributed to a web
development framework called Rails popularly known as Ruby On Rails. Rails is an
impressive framework but it is not the be-all and end-all of Ruby. Indeed, if you were to leap
right into Rails development without first mastering Ruby, you might find that you end up
creating applications that you dont even understand (this is, in fact, all too common among
Ruby On Rails novices). Understanding Ruby is a necessary prerequisite of understanding
Rails.

3.3 Knowledge Transfer Platform
The objective of KTP planning is to provide a SMART:
S:-specific
M:-measurable
A:-action-driven
R:-realistic
T:-time-bound framework that enables the developers to make reasonable estimates, cost,
and scheduling.
These estimates are made within a limited time frame at the beginning of a software
project and should be updated regularly as the project progresses.
There are many issues in the KTP software project planning as follows


3.3.1 SOFTWARE SCOPE
The first activity is the determination of software scope. Function and performance
allocated to software during system engineering should be assessed to establish a scope that
is unambiguous and understandable at the management and technical levels.
Software scope describes the data and control to be processed, function, performance,
constraints, interfaces, and reliability. Functions described in the statement. The availability
of historical information has a strong influence on estimation risk. By looking back, we can
emulate things that worked and improve areas where problems arose.
When comprehensive software metrics are available for past projects, estimates can
be made with greater assurance, schedules can be established to avoid past difficulties, and
overall risk is reduced.

3.4 Basic Principal
Project management is the process by which a proposed project is developed within a
rigorous framework. The process by which the various activities that need to be undertaken
during a projects lifetime should be scheduled. There are a range of activity management
tools that are commercially available.
The KPT project scheduling is an activity that distributes estimated effort across the
planned project duration by allocating the effort to specific software engineering tasks.
Project Scheduling
Project scheduling is concerned with the techniques that can be employed to manage the
activities that need to be undertaken during the development of a project.
Scheduling is carried out in advance of the project commencing and involves:
Identifying the tasks that need to be carried out;
estimating how long they will take;
allocating resources (mainly personnel);
Scheduling when the tasks will occur.

Once the project is underway control needs to be exerted to ensure that the plan continues to
represent the best prediction of what will occur in the future:
based on what occurs during the development;
often necessitates revision of the plan.

Effective project planning will help to ensure that the systems are delivered:
within cost;
within the time constraint;
to a specific standard of quality.

Proper scheduling requires
Effort and timing are intelligently allocated to each task.
Interdependencies between tasks are properly indicated.
Resources are allocated for the work to be done.

3.5 RISK MANAGEMENT
Risk:Defined by ISO ,It is the effect of uncertainty on objectives-whether positive or
negative.

Risk management is the identification, assessment, and prioritization of risks
followed by coordinated and economical application of resources to minimize,
monitor, and control the probability and/or impact of unfortunate events] or to
maximize the realization of opportunities.
Risks can come from uncertainty in financial markets, project failures
at any phase in
design,
Development
production,
Sustainment life-cycles.
Risk management standards have been developed including the Project Management
institute, the National Institute of Science and Technology, actuarial societies, and
ISO standards.
Methods, definitions and goals vary widely according to whether the risk
management method is in the context of project management, security, engineering,
industrial processes, financial portfolios, actuarial assessments, or public health and
safety.
The strategies to manage risk typically include transferring the risk to another party,
avoiding the risk, reducing the negative effect or probability of the risk, or even

Risk Identification
Risk identification is a systematic attempt to specify threats to the project plan. By
identifying known and predictable risks, I take first step towards avoiding them when
possible and controlling them when necessary.

3.5.1 Risk identification artifacts
Different types of risks are listed below:
ScheduleRisk: Project schedule get slip when project tasks and schedule release
risks are not addressed properly. Schedule risks mainly affect on project and finally on
company economy and may lead to project failure. Schedules often slip due to following
reasons:
Wrong time estimation
Resources are not tracked properly. All resources like staff, systems, skills of
individuals etc.
Failure to identify complex functionalities and time required to develop those
functionalities.
Unexpected project scope expansions.

Budget Risk:
Wrong budget estimation.
Cost overruns
Project scope expansion

Operational Risks: Risks of loss due to improper process implementation, failed system
or some external events risks.
Causes of Operational risks:
Failure to address priority conflicts
Failure to resolve the responsibilities
Insufficient resources
No proper subject training
No resource planning
No communication in team.

Technical risks: A technical risk generally leads to failure of functionality and
performance. Causes of technical risks are:
Continuous changing requirements
No advanced technology available or the existing technology is in initial stages.
Product is complex to implement.
Difficult project modules integration.

Programmatic Risks: These are the external risks beyond the operational limits. These
are all uncertain risks are outside control of program. These external events can be:
Running out of fund.
Market development
Changing customer product strategy and priority
Government rule changes.

3.6 PROJECT ESTIMATION
Project Estimation proper evaluation of the system and to get the estimation of the
project, it was needed to do some metrics calculation for this project. Software project
metrics are the way to do this task efficiently. Project metrics allow knowing the size and
complexity of the project and helping us on the planning and cost estimation.
Function Points can be counted using the following information domains:
Number of external inputs (EIs) inputs given by a user or another system.
Number of external outputs (EOs) outputs derived within the system or
given to another system.
Number of external inquiries (EQs) as an online input that results in
generation of some immediate software response in the form of an on-line
output.
Number of internal logical files (ILFs) logical grouping of data that
resides within the applications boundary and is maintained via external
inputs.
Number of external interfaces files (EIFs) - logical grouping of data that
resides external to the application but provides data that may be of use to the
application.




Chapter-4

SYSTEM ANALYSIS AND REQUIREMENTS

4.1 Feasibility Study
Time Schedule Feasibility
The estimated time duration based on the complexity of the project requires about 10
months.
The organization and The University allow us to develop our project work within the
specified time duration.

Operational Feasibilit
Performance: - Current mode of operation of the web-portal provides instantaneous
actions & responses such as getting registered and taking appointments by SMS and
E-Mail.It also provides room for donating organ by willing user and getting its
authority.
Information: - The web-portal provides all the information to the Administrator.
Economy: - Instantaneous actions can save lot of time as well as information is
presented in digital form so can reduce the cost of stationary items of information
archive.
Control: - Authentication based access to the system. Prevents also from SQL
Injection attacks. Information is available only to the authorized users of the system.
Efficiency: - All the available resources can be utilized at maximum.
Services:-All the facilities provided by web-portal are reliable and the system can be
expandable for future enhancements.

4.2 Functional Requirements

4.2.1 User Requirement
User who using this website should have their identity proof (Email id) for
registration.


4.2.2 User Interface:
Describes the logical characteristics of each interface between the software product
and the users. This may include sample screen images, any GUI standards or product family
style guides that are to be followed, screen layout constraints, standard buttons and functions
(e.g., help) that will appear on every screen, keyboard shortcuts, error message display
standards and so on. It defines the software components for which a user interface is needed.
It also specifies the details of the user interface design that are to be documented in a separate
user interface specification.
4.2.2.1 HTML Tags
HTML markup tags are usually called HTML tags
HTML tags are keywords surrounded by angle brackets like <html>
HTML tags normally come in pairs like <b> and </b>
The first tag in a pair is the start tag, the second tag is the end tag
Start and end tags are also called opening tags and closing tags

HTML Documents = Web Pages
HTML documents describe web pages
HTML documents contain HTML tags and plain text
HTML documents are also called web pages

The purpose of a web browser (like Internet Explorer or Firefox) is to read HTML
documents and display them as web pages. The browser does not display the HTML tags, but
uses the tags to interpret the content of the page:

<html>
<body>
<h1>My First Heading</h1>
<p>My first paragraph.</p>
</body>
</html>
HTML Images The <img> Tag and the Src Attribute
In HTML, images are defined with the <img> tag.
The <img> tag is empty, which means that it contains attributes only, and has no closing tag.
To display an image on a page, you need to use the src attribute. Src stands for "source". The
value of the src attribute is the URL of the image you want to display.
Syntax for defining an image:
<img src="url" alt="some_text"/>

The HTML frameset Element
The frameset element holds one or more frame elements. Each frame element can hold a
separate document.
The frameset element states HOW MANY columns or rows there will be in the frameset, and
HOW MUCH percentage/pixels of space will occupy each of them.

The HTML frame Element
The <frame> tag defines one particular window (frame) within a frameset.
In the example below we have a frameset with two columns. The first column is set to 25%
of the width of the browser window. The second column is set to 75% of the width of the
browser window. The document "frame_a.htm" is put into the first column, and the
document "frame_b.htm" is put into the second column:

<frameset cols="25%,75%"> <frame
src="frame_a.htm" /> <frame
src="frame_b.htm" /> </frameset>

4.3 NON FUNCTIONAL REQUIREMENTS
There are lots of features that we have included in the software. But some of them
were described over here.
4.3.1 Easy to maintain records: All the records are stored in the site database.
4.3.2 Less Time Consuming: All the entries are done easily so it requires less time
and also calculation is done automatically through computer so take less time.
4.3.3 Editing of Data: Easy to change the record.
4.3.4 No redundancy of data: Not allowed duplicate or fake account.

4.4 Hardware and Software Requirements
These requirements are described below.
We have Include hardware and software interfaces.

4.4.1 Hardware Interfaces
Motherboard(pIV).
RAM of 1GB.
80GB HDD
Color Monitor. [1024 x 768 Display ]
Keyboard.
Mouse.
500 V.A UPS. [Used in case of power failure]

4.4.2 Software Interfaces
Software Configuration
Operating System : Microsoft Windows XP/7.
Application Software : Ruby on rails

Software used in designing (code) of the system :
Operating System : Microsoft Windows Windows XP.
Application Software : Ruby on rails
Data Base : Sqlite3

4.5 Features Of New System.
Tips for the visitors.
Online help about System.
Online registration for the visitors to get notified for the various function and
activities performed by the organization throughout the year.
Online comments.
Mailing system and SMS for the users who are seeking information.
Optimized search for all users about any Blog.
Simple and effective service to its entire user in very less amount of time.
Chapter-5
SYSTEM DESIGN

5.1 Class Diagram.




Fig 5.1 Class Diagram



The above diagram shows the class diagram of the KTP which have person,
administration, registered user, visitor, comment, blog, template, post. The person will first
visit the page it will get notice in the administration then it goes to central server then server
gives the registration form then after getting registered then they will get the user code i.e id
and that person can be give feedback, create new blog, modify the blog and comment. The
blog get created by registered user then that blog can be viewed by the visitors and they can
comment on that blog and that persons are called as members of that site. The blog which is
created the members they can create template and posts for that blog.
The person should have to give name, address, DOB, phone no in administration
person will get the id and in registration they should give id, username and password when
creating blog they should give id, name and number of blog and while creating post and
template they should give id and name when giving comment also we have to give id and
description and visitor may have the email id and should be the member

5.2 Activity Diagram

The activity diagram as the name tells it is the flow chart when the person gets
registered in to the site in these flow diagram we are having enter username and password
after entering if the data entered is correct it will get login i.e enter into the profile of the user
and they perform operation on blog after the performance they can logout from the site. If the
entered username and password is not correct means it will get remain in the same sheet.


Fig.5.2 Flow chart of the user login and logout







5.3. Use case Diagram:

Fig 5.3 use case diagram


The diagram shows that the use cases of the visitors, registered user and
administration
In the diagram its clearly shown that the works done by the above listed users.
The use case of the Visitor, registered user and administration is listed below;
Visitor: they can give feedback, view blog, registration, and comment.
Registered user: can give comment, login and logout, can view, modify or delete blog,
privacy setting.
Administration: and logout, can view, modify or delete blog, privacy setting, system
management and control.

5.4. Data Flow Diagram:
The Data flow diagram is the flow of the data in the blogger and the user we have
divided in to 2 levels i.e. DFD level 0 which gives the data flow of the user interface to the
blogger and 2
nd
level is DFD level 1 which gives the data flow of the bloggers.

5.4.1 DFD level 0


Fig 5.4.1 Data flow diagram of user interface to the blogger

Now we are seeing the data flow diagram of the 3 types of the users visitors,
registered user and admin. In the above fig we can see all the user is get interacting with the
blogger and the performance they can do on it. 1
st
come to the visitor he can write comment,
view blog, and give feedback. 2
nd
registered user can give feedback, create blog, settings,
login, logout and view blog. Lastly Admin can manage userprofile, get login and logout,
other operations, and get result from the blogger.

5.4.2 DFD level 1:
In the level 1 the data flow of the blog manage is given it have the user database info,
comment database info, blog database info, publishing database info, profile database info,
and permission database info. In the user database we are having Admin, Register user.
The flow of the data control is given in the below fig 5.4.2 all the user details will be
in user database info which manage user, the comment manage which manages all comment
details in the commentdb info, bog manage manages all blog info which of store data view
blog create blog process. The Admin is having the publishing of data which can be done by
the publishing setting, the registered user have the publishing, profile, permission data which
can be handled by the publishing setting, profile manage, permission setting respectively.
The publishing settings data will be in publishing db info, the profile manage data in the
profile db info, and permission settings data in the permission db info.
The fig 5.4.2 also contains the visitor flow of data in that the visitor just show i.e.
view the blog and give data i.e. write comment these comment will be stored in the comment
db info.


Fig 5.4.2 data flow diagram of the blogger



Chapter-6
IMPLEMENTATION ENVIRONMENT

6.1 The MVC Architecture
At the core of Rails is the Model, View, Controller architecture, usually just called MVC.
MVC benefits include:
Isolation of business logic from the user interface
Ease of keeping code DRY
Making it clear where different types of code belong for easier maintenance
6.1.1 Models
A model represents the information (data) of the application and the rules to manipulate that
data. In the case of Rails, models are primarily used for managing the rules of interaction
with a corresponding database table. In most cases, each table in your database will
correspond to one model in your application. The bulk of your applications business logic
will be concentrated in the models.
6.1.2 Views
Views represent the user interface of your application. In Rails, views are often HTML files
with embedded Ruby code that perform tasks related solely to the presentation of the data.
Views handle the job of providing data to the web browser or other tool that is used to make
requests from your application.
6.1.3 Controllers
Controllers provide the glue between models and views. In Rails, controllers are
responsible for processing the incoming requests from the web browser, interrogating the
models for data, and passing that data on to the views for presentation.
6.2 Components
KTP consists of three main components: Articles, Comments and Tags
6.2.1 Articles

6.2 Implementation Environment
Can be used by multiple Registered User and Visitors.
Uniform GUI Design
Microsoft SQL server 2005 User Id and Password required for normal/network base
access.
Internet support.

6.2 Security Features
User must enter his/her valid user Id & password to get in to the System
Registered User need to submit their valid information so that fake entry will be
minimized.

6.3 CODING STANDARAD
Always use the extension .aspx.
The use of white space and simple comments is strongly encouraged.
Comments in .net can be For like line put

Software Inspection
Analyze and check system representations such as the requirements document, design
diagrams and the program source code. They may be applied at all the stages of the process.

6.4 Test Plan
A test plan documents the strategy that will be used to verify and ensure that a
product or system meets its design specifications and other requirements
Software is tested at various levels by various techniques like black box, white box, Unit
testing and Integration testing etc.

6.4.1 The Testing Process
We test the software process activities such as Design, Implementation, and
Requirement Engineering. Because Design errors are very costly to repair once
system has been started to operate, therefore, it is quite obvious to repair them at early
stage of the system development.
6.4.2 Requirements Traceability
As most interested portion in the system is system meeting its requirements
therefore testing should be planned so that all requirements are individually tested.
We checked the output of certain combination of inputs, which gives desirable result,
or not. Strictly stick to your requirements specification gives you the path to get
desirable result for system users.























Chapter-7
CONCLUSION AND FUTURE ENHANCEMENT
7.1 Future Enhancements
Future enhancement means that the scope in the future of the system.
Try to make as more user friendly as possible.
We are going to integrate Chat server with the Application.

7.2 CONCLUSION
We have included as many features as we can make the site viable and usable and
also web application very friendly and mobile application very easy to use for all user to
make blog. Our proposed system is online and real time based on Internet, which is very
much ahead to go so, user of the system would like to use this.






















Chapter-8
BIBLIOGRAPHY

[1] OOP with Microsoft VB.NET and C#.NET Step By Step
[2] Building .NET Applications for Mobile Devices
[3] Programming Microsoft ASP.Net Core Reference
[4] www.google.com
[5] www.asp.forums.net
[6] www.msdn.microsoft.com