27-08-2014, 02:39 PM
TruText -a unique messaging app: – The project is to make a messaging system that will link a user with a unique account and allow them to make multiple profiles under that account. Within the TruText ecosystem, the user will be able to identify themselves as any of their profiles and engage in communication with other profiles. A unique feature of the project is that profiles can be transferred (or sold) between accounts. i.e. a user can make a request to the system that a particular profile under their account is available for transfer to another account. After the transaction is complete, the original account will no longer have access to the profile. The profile and anything associated with it will belong to another user who will be able to identify as that profile.
A problem is well defined very rarely. The first task is to get more crucial information by interviewing and meeting concerned people. It clarifies how the problem is felt, how often it occurs, how it affects the one.s life and which aspect of life are suffering most with this. This phase consists of the following tasks.
This was a preliminary investigation done with a view to have a “feel” of the working of the proposed system. This phase has been identified the end-user directly involved in the system who were the managers, assistant officer and database administrator, and the development department. By understanding the working of database, its flow and also after conducting meetings and interviews with the concerned persons of the department, a clear idea about the working was obtained.
A flexible approach is adapted towards people who are interviewed. Short hand written notes are prepared based on the response of the people. The interviews are preferably conducted at the work place of the person being interviewed. Detailed investigation is done in order to define the scope of the problem .The interview is concluded with a quick resume of the ground covered during the interview .The Questionnaire technique is combined with interviews to get the best result. Proper care has been taken in the design of such questionnaires so that the persons answering these questions do not feel hesitant. An explanatory note that serves to gain cooperation and avoid misunderstanding by setting out the purpose of the exercise clearly accomplishes each questionnaire.
Observation technique is also used for fact finding. The work described at the time of interview is observed personally ads it reduces the chances of misunderstanding and omissions. Some important things observed are like the flow of information through the system and important data transactions, the data being maintained and the frequency of their updating.
By the end of this phase, idea as to how the information enters the system, how it is stored, how it is processed, how information changes affects the working of the system and finally the output format required by the end-user was collected. All the information generated from this phase acted as an input to the next phase.
TruText is a project is to make a messaging system that will link a user with a unique account and allow them to make multiple profiles under that account. Within the TruText ecosystem, the user will be able to identify themselves as any of their profiles and engage in communication with other profiles.
A unique feature of the project is that profiles can be transferred (or sold) between account i.e. a user can make a request to the system that a particular profile under their account is available for transfer to another account. After the transaction is complete, the original account will no longer have access to the profile. The profile and anything associated with it will belong to another user who will be able to identify as that profile.
1.1 Scope and Objective of Project
The main objective of the first phase of development is to use an open source XMPP server for backend infrastructure. All the end-user systems will implement an XMPP client. This will be the foundation on which the instant messaging feature will be built upon. A separate control system will be built to handle the account creation features. The following figure shows the high-level logical overview of the system.
Figure 1.1-System Overview(Use Case Diagram)
The diagram Figure 1.1-System Overview can be divided into 3 layers. The top layer shows the backend, consisting of the TruText control system and XMPP server. The middle layer shows the user-facing components, and the bottom layers show the users. The arrows between the different sections show how communication will happen. Dotted lines represent interfaces that need to be designed.
.
2 System Study and Problem Formulation 2.1 Existing System
There exist several communication channel one users need to use for completion of its requirement.s. Avg. person need to have mainly one business profile to get connected and updates its business links and and also it helps them to create a new business relations and also to promote its business .for Business profile one person uses “LinkedIn” or “Yellow Pages”
LinkedInis a business-orientedsocial networking service. Founded in December 2002 and launched on May 5, 2003,]it is mainly used forprofessional networking. In 2006, LinkedIn increased to 20 million viewers.As of June 2013, LinkedIn reports more than259 million acquiredusers in more than 200 countries and territories”
Yellow pagesrefer to atelephone directoryofbusinesses, organized by category, rather than alphabetically by business name and in whichadvertisingis sold. The directories were originally printed on yellow paper, as opposed towhite pagesfor non-commercial listings. The traditional termyellow pagesis now also applied toonline directoriesof businesses.”
For social purpose, one may use facebook and twitter .Now days both are very popular among peoples and have a very large user base
Twitteris an onlinesocial networkingandmicro bloggingservice that enables users to send and read short 140-charactertext messages, called"tweets". Registered users can read and post tweets, but unregistered users can only read them. Users access Twitter through the website interface,SMS, or mobile deviceapp. Twitter Inc. is based inSan Franciscoand has offices inNew York City,Boston,AustinandDetroit.
2.1.1 Detailed Study of the Existing System
This phase provides the overall requirement for the system what is to be done. Input for this phase is the information collected through several data collecting schemes such as survey, cross-questioning-answering etc and the raw data obtained which is not properly ordered and not in the precise manner. So here this raw data is converted into useful information written in precise manner and thus output is a formal document.
After collecting all the information and requirements, they were verified from the concerned persons by presenting a diagrammatic version of the proposed system. The points missing were added to the system specifications for the desired system. So this final document provides the system requirement specifications for the desired system. It helps in reducing the total development cost and also establishes the various points for validation and verification.
Possibility for TruText app arises due to the fact that different communication channels are able to provide some API that can be used to use them and combine them all at one place is possible because their result format can be either Json or Xml depend upon need XML based reports areeasy to parse programmatically and many programming languages provide libraries to parse suchfiles with ease. This allows easy processing of data and possibility of combing them easy this can further be extended to export data into meaningful knowledge-base, which can be used to perform studies related pertaining to security.
The TruText app also diminishes time wastage as the data is analysed and processedat one place so switching time between them is very low. This can remove all structural errors from the differ channels, leaving the end user to focus only on the specific channel they need to use rather than thinking of time spend in switching .
2.2 Limitations of Existing System
v Complex to use
v Tedious
v Time Consuming
v Fetching and working out various channel is difficult
v Entails training to dealing with different channels data
v High potential of privacy breach
2.3 Proposed System
TruText is a cloud-base text messaging application for mobile, desktop and browser. TruText combines the very best of mobile messaging, social networking and the cloud. Multiple TruText IDs allow you to organize your personal and professional life. So, proposed app is very effective in handling the various needs for communication channels at one place with very user friendly interface and allowing user to easily switching between the different lives for their different needs.
2.4 Advantages of Proposed System
· Requires less efforts
· Error Free
· Time Saving
· Fetching and switching is easy.
· Dynamic
· Quick and easy to use
2.5 Feasibility Study
A feasibility study is a test of a system proposal according to its workability impact on organization, ability to meet user needs and effective use of resources. The objective of a feasibility study is not to solve a problem but to acquire a sense of its scope. During the study, the problem definition is crystallized and the aspects of the problem to be included in the system are determined. After the initial investigation of the system is done, it is needed to have in-depth study of the existing system, understanding its strength and weaknesses and the requirements for the new proposed system. Feasibility study was done in three phases documented below.
2.5.1.1 Behavioural feasibility
People are inherently resistant to change and computers have been known to facilitate change. There is always some reluctance among the users against the introduction of new system but they were told that this system would eliminate the unnecessary overhead of database migration and conversion, which presently had to be carried out on daily basis to facilitate transactions between the different departments. The objective this feasibility phase is to take the operational staff into confidence.
As the success of a good system depends upon the willingness of the operating staff, they were taken into full confidence that the new proposed system would make their jobs easier, relieve them from the unnecessary overheads and reduce the possibility of errors creeping into the system.
2.5.1.2 Economic feasibility:
Economic feasibility is the most frequently used method for evaluating the effectiveness of the candidate system. More commonly known as costenefit analysis, the procedure is to determine the benefits and savings that are expected from a candidate system and compare them with the costs. If benefits outweigh the costs, then the decision is made to design and implement the system. A costenefit analysis was done for the proposed system to evaluate whether it would be economically viable or not.
The organization has in store many machines with high processing power necessary to implement the system. Also the organization has necessary software or hardware to support the system. Considering the programmer time and the negligible hardware/software cost required for developing the system, it was found that the benefits in terms of reduced overhead was more than the cost.
2.5.1.3 Technical feasibility
Technical feasibility centres on the existing computer system. (Hardware/software) and to what extent it can support the proposed addition also the organization already has sufficient high-end machines to serve the processing requirements of the proposed system. So there is no need to purchase new software as the organization has necessary software or hardware to support the proposed system. Having gone through the steps of the overall analysis and feasibility study the next step was to carry out a detailed system analysis. The project analysis phase was conducted to learn about the proposed system, to study the problems and finally select a system that would take care of the problems identified in the working of the present system.
3 Project Plan 3.1 Analysis Phase
Systems analysis is the study of sets of interacting entities, including computer systems analysis. This field is closely related to operations research. It is also "an explicit formal inquiry carried out to help someone (referred to as the decision maker) identify a better course of action and make a better decision than he might otherwise have made."
Analysis is defined as the procedure by which we break down an intellectual or substantial whole into parts so that we can achieve our end goals.
The development of a computer-based information system includes a systems analysis phase which produces or enhances the data model which itself is a precursor to creating or enhancing a database. There are a number of different approaches to system analysis. When a computer-based information system is developed, systems analysis would constitute the following steps:
Conducting fact-finding measures, designed to ascertain the requirements of the system.s end-users. These typically span interviews, questionnaires, or visual observations of work on the existing system.
Gauging how the end-users would operate the system (in terms of general experience in using computer hardware or software), what the system would be used for etc.
Another view outlines a phased approach to the process. This approach breaks systems analysis into 5 phases:
o Scope definition
o Problem analysis
o Requirements analysis
o Logical design
o Decision analysis
Use cases are a widely-used systems analysis modelling tool for identifying and expressing the functional requirements of a system. Each use case is a business scenario or event for which the system must provide a defined response. Use cases evolved out of object-oriented analysis.
3.1.1 User Requirement
Since end users are the ones who are finally going to use the system, their requirements need to be identified. This involves questioning the end users what their expectations were. The main requirement of the end user is that the system should be easy to use and take less time. In addition to these another important factor was to eliminate the need for database conversion and migration that had to be carried out presently. After conducting interviews with the users a document called the software requirement specification was created. This is the most important document that forms the basis for system development. It should be consistent, complete, unambiguous, traceable and inter-related.
3.1.2 Functional Requirements
The functional requirements specify relationship between the inputs and outputs. All the operations to be performed on the input data to obtain output are to be specified. This includes specifying the validity checks on the input and output data, parameters affected by the operations and the other operations, which must be used to transform the inputs into outputs. Functional requirements specify the behaviour of the system for valid input and outputs.
3.1.3 Performance Requirements
This section includes performance of the product that are set by user interaction and studying the existing system of the organization. These are stated in complete measurable terms, so that they can be verified during system evaluation phase. Some of the performance requirements are stated below.
o User Friendly: The system produced is user friendly, understandable and easy to use so that the users of the system can easily learn to use the system. For this the system is made menu-driven with well-documented programs.
o Time Element (response and processing time): The response time of the system is very less and takes less time to execute queries and triggers.