S.NO.
1.
PARTICULARS
INTRODUCTION
1.1
1.2
1.3
1.4
2.
3.
4.
5.
6.
PAGE NO
3.1
Existing System
3.2
Proposed System
3.3
System Description
3.4
Feasibility Study
3.5
3.6
Input Design
4.2
Output Design
4.3
Database Design
10
4.4
Code Design
10
4.5
11
4.6
Module Description
12
4.7
Development
13
Objectives of Testing
14
5.2
Test Plan
14
5.3
Testing Methods
15
5.4
16
5.5
Implementation
16
COMPARATIVE STUDY
7.
CONCLUSION
8.
9.
BIBLIOGRAPHY
10.
APPENDIX
A. Sample Code
22
B. Sample Screens
26
28
D. ER Diagram
29
1. INTRODUCTION
1.1.About the system
Smart OS is a Skelton of a web operating system that lets you run diverse
applications within a web browser. In this project mainly concentrating on the File
Management part of Online Operating System. Its prime concern is to provide online
management of files to Administrator. This enables the Administrator and user to view, edit
files etc online. This is a web operating system that lets you run diverse applications
within a web browser. Small applications like sticky notes or clocks. Large applications like
word processing, mp3 players, and instant messaging. Even better, it's very easy to tweak
an existing application or write your own.
It is a web application platform that mimics the look and feel of classic desktop
operating systems such as Microsoft Windows, Mac OS X or KDE. As applications can be
executed in an integrated and parallel way, the Online Operating System can be considered
a web operating system, web desktop or web top. It provides basic services such as a GUI,
a virtual file system, access control management and possibilities to develop and deploy
applications online. As the Online Operating System is executed within a web browser, it is
not a real operating system but rather a portal to various web applications, offering a high
usability and flexibility.
In Online Operating System each user is given some free space of 2GB in the web .In
Online Operating System users can create their own text documents and view them and also
they can edit them and save them. They can also upload their own multimedia files and
store them to the web. They can also view or listen the audio or videos online. In this
application there is a discussion form which allows users to post their own questions and
answers so that all of them will be visible to every user. This application also provides the
facilities of instant messaging for the online users of Online Operating System. There is an
option for accessing the command prompt of local system
so that we can have the access of local drive by online. Email service is also available for
each user within the application.
identity of principals.
A key enabling feature is fine-grained control of capabilities provided to remote
space the same interface, caching, and performance of existing distributed file systems
Persist: Do some work. Log out. Log in later from another computer. It's like you never
left.
Centralize: Manage all your web services, files, and accounts in one secure place.
Collaborate: Share files and apps through a simple, intuitive buddy list.
a multitasking project after this version also we can update an use multitasking.thisproject
has a huge expectation from youngsters because of this multitasking
2.2 Objectives
The main objective of this project is to make a good interaction with a computer User and
Computer Hardware. Also to provide the best overall system performance, client
applications must be able to dynamically locate the server to deliver the highest quality of
service.
The main aims are
To provide facility for the File Management part of Online Operating System.
To provide facility for each user, who were registered, to handle their own files with
high security.
Now there exist some discreet systems that help the companies with minimal
information. The programmers need extra effort to do their duties because of the lack of
framework.
Drawbacks of Existing System
Lack of Security
Difficulty in searching
Report making is Tedious
No management information system
Persist: Do some work. Log out. Log in later from another computer. It's like you
never left.
Centralize: Manage all your web services, files, and accounts in one secure place.
Collaborate: Share files and apps through a simple, intuitive buddy list.
Customize: Install apps written by friends or write your own.
Operating environment for web based application is a Skelton of a web operating
system that lets you run diverse applications within a web browser. In this project mainly
concentrating on the File Management part of Online Operating System. Its prime concern
is to provide online management of files to Administrator. This enables the Administrator
and user to view, edit files etc online. This is a operating environment that lets you run
diverse applications within a web browser. Small applications like sticky notes or clocks.
Large applications like word processing, mp3 players, and instant messaging. Even better,
it's very easy to tweak an existing application or write your own.
In operating environment system, there are mainly following modules.
Administrator module
User module
File System Module
GOAL
The main goal of the proposed system is to provide easy handling of user files which
are stored in the server with high security. Some of the main goals of the system are
Technical Feasibility
A study of function, performance and constraints may improve the ability to create an
acceptable system. Technical feasibility is frequently the most difficult area to achieve at
the stage of product engineering process.
Considering that are normally associated with the technical feasibility include
Development risk
Resource availability
Technology
Technical feasibility study deals with the hardware as well as software
requirements. The scope was whether the work for the project is done with the current
equipments and the existing software technology has to be examined in the feasibility
study. The outcome was found to be positive.
In the proposed system, data can be easily stored and managed using database
management system software. The reports and results for various queries can be generated
easily. Therefore, the system is technically feasible.
Economical Feasibility
A cost evaluation is weighed against the ultimate income or benefit derived from the
developed system or product. Economic j1.lstification is generally the "bottom-line"
consideration that includes cost benefit analysis, long term corporate income strategies,
impact on other profit centers or products, cost of resources needed for development and
potential market growth. When compared to the advantage obtained from implementing the
system its cost is affordable. Also the system is designed to meet the modifications required
in the future. So most of the required modifications can be done without much re-work.
Proposed system was developed with the available resources. Since cost input for the
software is almost nil the output of the software is always a profit. Hence Software is
economically feasible. In the existing system, manpower is more required. In the proposed
system, number of employees to be involved is reduced drastically. So, the proposed system
is said to be economic.
In the existing system, storage of the records should be properly done and security
should be provided for the records. In the proposed system, the software provides security
and maintenance and it hardly needs one or two persons to operate the system.
Operational Feasibility
Proposed projects are beneficial only if they can be turned into information systems
that will meet the organization's operating requirements. Simply stated, this test of
feasibility asks if the system will work when it is developed and installed. Are there major
barriers to implementation? Here are questions that will help test the operational feasibility
of a project:
new system will be used if it is developed and implemented. And whether there will be
resistance from users that will undermine the possible application benefits.
There was no difficulty in implementing the system and the proposed system
is so effective, user friendly and functionally reliable so that the users will find that the new
system reduce their hard-steps. If the users of the system are fully aware of the internal
working of the system then the users will not be facing any problem in running the system.
3.5SYSTEM SPECIFICATION
Operating System: Windows XP or Above
Database: SQL
SOFTWARE REQUIREMENTS
Operating System
Software
Front End
Back End
:
:
:
:
WINDOWS XP/7
Visual Studio 2010
ASP.Net with C# scripting, HTML
SQL Server 2008
HARDWARE REQUIREMENTS
Minimum Requirements
Processors
:
Intel Pentium Pro or Processor running at 133MHz
Hard Disk
:
40 GB Hard Disk
RAM
:
Client Level Minimum 512MB
Recommended Requirements for peak performance
Processors
:
Intel Pentium 4 running at 450 MHz
RAM
:
512MB
3.6 SCHEDULING
Scheduling is the culmination of a planning activity that is a primary component of
software project Helveita. When combined with estimation methods and risks analysis,
scheduling establishes a road map for the project manager. Scheduling begins with process
decomposition.
Programming Maintenance
Apart from the bugs, the programmer has to maintain the program he /she has created.
Program Maintainance is a term used for the updating of a program after the program after
the program is put into use. This updating may be a result of the users request or a change
in the way the program needs to operate.
Project
A project is a collection of files that make up your application. A single Application
might consist of several files and the projects is the collection of those files
Input Design.
Output Design.
Database Design.
Code Design.
In system design, the overall structure of the process is checked out. The design is
carried out using top-down design strategy. First the major modules are identified then they
are divided into sub modules at the lowest level and are addressed as a single function of
the whole system.
The first step in design process is review and refinement of all the DFD diagrams
developed during requirements definition and external design.
The second step is to determine whether the system is transformed centered or
transaction driven and to derive a high-level process chart on this determination.
The third step is the deposition of each subsystem using guidelines such as coupling,
cohesion, information hiding, levels of abstraction, data abstraction, and other
decomposition criteria.
The objective of the system design is to deliver the requirements as specified in the
feasibility report. System design involves first logical design (logical design) and then
physical construction (detailed design) of the system. The logical design
describes the structure and characteristics of features, such as the outputs, inputs, files,
databases, and procedures. The physical construction produces actual program software,
files, and working system. System design goes through two phases of development:
Logical Design
Physical Design
Logical Design
The logical design of a system pertains to an abstract representation of the data flows,
inputs and outputs of the system. This is often conducted via modeling, using an overabstract (and sometimes graphical) model of the actual system. In the context of systems
design are included. Logical design includes ER Diagrams i.e. Entity Relationship
Physical Design
The physical design relates to the actual input and output processes of the system. This
is laid down in terms of how data is input into a system, how it is verified/ authenticated,
how it is processed, and how it is displayed as output. Put another way, the physical portion
of systems design can generally be broken down into three sub-tasks:
User Interface Design
Data Design
Process Design
User Interface Design is concerned with how users add information to the system and
with how the system presents information back to them. Data Design is concerned with
how the data is represented and stored within the system. Finally, Process Design is
concerned with how data moves through the system, and with how and where it is
validated, secured and/or transformed as it flows into, through and out of the system.
A relation is said to be in second normal form if and only if it satisfies all the first
normal form conditions for the primary key and every non-primary key attributes of the
relation is fully dependent on its primary key alone.
Third Normal Form
A relation is said to be in third normal form if only if it is in second normal form
and more over the non key attributes of the relation should not be depend on other non key
attribute.
First Normal Form
A relation is said to be in first normal form if only if it satisfies the constraints that
contain the primary key only.
Second Normal Form
A relation is said to be in second normal form if and only if it satisfies all the first
normal form conditions for the primary key and every non-primary key attributes of the
relation is fully dependent on its primary key alone.
Third Normal Form
A relation is said to be in third normal form if only if it is in second normal form
and more over the non key attributes of the relation should not be depend on other non key
attribute.
TABLE STRUCTURE
Table: UserMaster
Column name
UserId(PK)
FirstName
LastName
UserName
Email_Id
Password
GroupId
Gender
Age
Address
City
State
Country
Photo
Table: Login Details
Datatype
varchar(50)
varchar(50)
varchar(50)
varchar(50)
varchar(50)
varchar(50)
varchar(50)
varchar(50)
varchar(50)
varchar(MAX)
varchar(50)
varchar(50)
varchar(50)
varchar(50)
Description
User id
FirstName
Last Name
User name
Emailid
Password
User Type
Gender
Age
Address of user
City
State
Nation
Path of users photo
Column name
Datatype
Description
LoginId(PK)
Int
LoginId
userId(FK)
Int
Users Id
Logstat
Int
Login Status
Column name
Eventid(PK)
userId
Events
Date
Table: Questions
Datatype
Int
Int
varchar(50)
Date
Description
Event Id
User id
Events
Date
Column name
Qid(PK)
userName
Question
Date
Table: Answer
Datatype
Int
varchar(50)
varchar(MAX)
DateTime
Description
Question Id
User Name
Question
Date
Column name
AnsId(PK)
userName
Qid(FK)
Answer
Date
Table: Schedules
Datatype
Int
varchar(50)
Int
varchar(MAX)
Date
Description
Answer Id
Username
Question Id
Answer
Date
Column name
ScheduleId(PK)
userId
Schedule
Date
Table: Messages
Datatype
Int
Int
varchar(MAX)
DateTime
Description
Schedule id
Users Id
Program scheduled
Date for that program
Column name
MessageId(PK)
userId(FK)
Message
Date
Datatype
Int
Int
varchar(MAX)
DateTime
Description
Messsage Id
Users id
Message typed
date
Datatype
Int
Description
File id
Table: Events
Table: Files
Column name
FileId(PK)
userId
File
Path
Date
Allow
Int
varchar(MAX)
varchar(50)
DateTime
Bit
Users id
File name
Path of file
Date
Permission of file
INPUT DESIGN
The input design is a crucial part of any system errors. Inaccurate inputdata are the
most common cause of the errors in the processing. Data entry errors can be controlled by
input design. Input design is the process of converting user-oriented inputs to computer
based formats .the goal of designing input data is to make data entry as easy, logical and
free from errors as possible.
The following are the objectives of input design:
the nature of inputs is made more explicit during the physical design. The impact of inputs
on the system is also determined.
Effort has been made to ensure that input data remains accurate from the stage at which it is
recorded and documented to the stage at which it is accepted by the computer.Validation
procedures are also present to detect errors in data input, which is beyond control
procedures. Validation procedures are designed to check each record, data item or field
against certain criteria.
Use proper indentation when selection and looping structure are implemented.
Avoid heavy nesting of loops, preferable not more than three levels.
Use simple conditions test, if necessary break complicated condition into simple
condition.
Use parenthesis to clarify logical and arithmetic expressions.
Use space, whenever possible, to improve readability.
INPUT AND OUTPUT FORMATS: INPUT/OUTPUT FORMATS should be simple and acceptable to users. A number of
guideline should be considered during coding:
4.6MODULES DESCRIPTION
Administrator Module
Login
Events Tracking
User module
Registration
Login
File Management
File Search
Schedule programs
Discussion Forum
Chat
Email Service
Command Shell
File System Module
Text Editor
Image Gallery
Web Multimedia
4.7 DEVELOPMENT
Development is the state in the project where the theoretical design is turned a working
system. The most critical stage in achieving a new successful system and getting in
confidence on the new system for the user that it will work efficiently and effectively. The
system can be developed only after through testing is done and if it is found to work to the
specifications. It involves careful planning, investigation of the current system and its
constraints on development. More complex the system being developed, the more work
involved will be the system analysis and design effect required for development
All tests should be traceable to customer requirements. The focus of testing will shift
progressively from programs. Exhaustive testing is not possible. To be more effective,
testing should be one, which has probability of finding errors.
The following are the attributes of good test:
LEVELS OF TESTING
The details of the software functionality tests are given below. The testing procedure
that has been used as follows
Unit Testing
Integration Testing
Validation Testing
Output Testing
User acceptance Testing
Unit Testing
The first level of testing is called as unit testing. Here the different modules are tested
and the specification produced during design for the modules. Unit testing is essential for
verification of the goal and to test the internal logic of the modules. Unit testing was
conducted to the different modules of the project. Errors were noted down and corrected
down immediately and the program clarity was increased. The testing was carried out
during the programming stage itself. In this step each module is found to be working
satisfactory as regard to be expected output from the module.
Integration Testing
The second level of testing includes integration testing. It is a systematic testing of
constructing structure. At the same time tests are conducted to uncover errors with the
interface. It need not to be the case, that software whose modules when run individually
showing results will also show perfect results when run as a whole.
The individual modules are tested again and the results are verified. The goal is to see
if the modules can integrated between the modules. Poor interfacing may result in data
being lost across an interfacing causing serious problems. This testing activity can be
considered as testing the design and emphasizes on testing modules interaction.
Password Testing
If the administrator has to enter the server side of the software he has to specify the
user name and the password. When the user enters the user name and the password,
checking it with already registered username and the password in the database will be
validated. If it matches, then only the user is allowed to access the page otherwise access is
denied and there by provides a strong security.
Validation Testing
The next level of testing is validation testing. Here the entire software is tested. The
reference document for this process is the requirement and the goal is to see if the software
meets its requirements.
The requirement document reflects and determines whether the software functions as
the user expected. At culmination of the integration testing, software is completely
assembled as a package, interfacing and corrected and a final series of software test
validation test begins. The proposed system under construction has been tested by using
validation testing and found to be working satisfactory.
Data validation checking is done to see whether the corresponding entries made in
different tables are done correctly. Proper validation checks are done in case of insertion
and updating of tables, in order to see that no duplication of data has occurred. If any such
case arises proper warning message will be displayed. Double configuration is done before
the administrator deletes a data in order to get positive results and to see that no data have
deleted by accident.
Output Testing
The output of the software should be acceptable to the system user. The output
requirement is defined during the system analysis. Testing of the software system is done
against the output and the output testing was completed with success.
User Acceptance System
An acceptance test has the objective of selling the user on the validity and reliability of
the system. It verifies that the system procedures operate to system specification and the
integrity of the vital data is maintained.
5.5 IMPLEMENTATION
Conversions to new systems often get off track because companies fail to plan the
project realistically or they don't execute or manage the project by the plan. Remember that
major systems conversions are not just IT projects. Companies should maintain joint
responsibility with the vendor in the project-planning process, maintenance of the projectplan status, as well as some degree of control over the implementation.
All key user departments should have representation on the project team, including the
call center, website, fulfillment, management, merchandising, inventory control, marketing
and finance. Team members should share responsibilities for conversion, training and
successful completion of the project tasks. The software vendor should have a time-tested
project methodology and provide a high-level general plan. As the merchant client, your job
is to develop the detailed plan with the vendor, backed up with detail tasks and estimates.
For example, a generalized plan may have a list of system modifications, but lack the
details that need to be itemized. These may include research, specifications, sign-offs,
program specs, programming, testing and sign-off, and the various levels of testing and
program integration back into the base system. Plan for contingencies, and try to keep
disruptions to the business to a minimum. We have seen systems go live and withs
management initially unable to get their most frequently used reports this can be a big
problem.
Along the same lines, you should schedule the go-live for the slowest period of the year.
In consumer retail and ecommerce businesses, systems generally aren't brought live from
January through April. The systems project should have a senior manager who acts as the
project sponsor. The project should be reviewed periodically by the steering committee to
track its progress. This ensures that senior management on down to the department
managers are committed to success. Once you have a plan that makes sense, make sure you
manage by the plan. This sounds elementary, but many companies and vendors stumble on
it.
Early in the project publish a biweekly status report. Once you get within a few months,
you may want to have weekly conference call meetings and status updates. Within 30 days
of go live, hold daily meetings and list what needs to be achieved. Required most
vendors offer not only the initial training, but also more advanced instruction for super
users. Budget for the additional training; it's the smallest part of the total expense. And
perform a post implementation audit 30 to 60 days after the go-live. Identify the
individuals and departments for which additional training is necessary.
Implementation uses the design document to produce code. Demonstration that the
program satisfies its specifications validates the code. Typically, sample runs of the
program demonstrating the behavior for expected data values and boundary values are
required. Small programs are written using the model:
Write
Compile
Test
It may take several iterations of the model to produce a working program. As
programs get more complicated, testing and debugging alone may not be enough to
produce reliable code. Instead, we have to write programs in a manner that will help insure
that errors are caught or avoided.
Top-Down Implementation
Top down implementation begins with the user-invoked module and works toward the
modules that do not call any other modules. The implementation may precede depth-first
or breadth-first.
Bottom-Up Implementation:
Implementation begins with modules that do not call any other modules and works
toward the main program. Test harness is used to test individual modules. The main
module constitutes the final test harness.
Stub Programming:
Stub programming is the implementation analogue of top-down and stepwise
refinement. It supports incremental program development by allowing for error and
improvement. A stub program is a stripped-down, skeleton version of a final program. It
doesn't implement details of the algorithm or fulfill all the job requirements. However, it
does contain rough versions of all sub programs and their parameter lists. Furthermore, it
can be compiled and run. Extensive use of procedures and parameter are the difference
between stub programs and prototypes. Quick and dirty prototypes should be improved-they should be rewritten. A stub program helps demonstrates that a program's structure is
plausible. Its procedures and functions are unsophisticated versions of their final forms,
but they allow limited use of the entire program. In particular, it may work for a limited
data set.
6. COMPARATIVE STUDY
In the Existing system has contains lots of problems existing it does not contain all
contents. This application created for the multitasking users, they register and login our
application then learn all materials throw their Helveita software. All materials and contents
are stored in our application.
The proposed system is developed after a detailed study about the requirements
requested by the user. Proposed system is a windows based application one, where all the
limitations of manual system are compensated. It is provides the users with learning
contents easily learn throw their widows based application Previous application only
provided limited contents, if user learns fully they use only websites for learning. The
vendor's approach is typ0ically to train your trainer. From there, it's your responsibility to
develop training materials and approaches for the various departments and the new policy
and standard operating procedures.
Most companies don't have full-time trainers. It's a good idea to train each department
manager on the application, and then have them develop the SOPs and set training for their
department. All of this will need to be standardized so that the documentation is at the same
level of detail across the operational departments. It generally takes six to 12 months after
implementation for companies to start feeling comfortable with the new systems. It may
take longer to achieve the ROI from the application. Training is the single most important
thing you can do to shorten the learning curve
7.CONCLUSION
This was the first considerably large and important project undertaken by me during
my MCA course. It was an experience that changed the way I perceived project
development. The coding could not be started before the whole system was completely
finalized. Even then there were so many changes required and the coding needed to be
changed. I attribute this to inadequate information gathering from the user. Though there
were many meetings with the user and most of the requirements were gathered, a few
misinterpretations of the requirements still crept in. It made me realize how important the
systems analysis phase is. The project is a classic example for the adage that learning of
concepts needs to be supplemented with application of that knowledge. On the whole it was
a wonderful experience developing this project and I would have considered my education
incomplete without undertaking such a project which allowed me to apply all that I have
learnt.
FUTURE ENCHANCEMENT
The project entitled operating environment for web based application is developed
successfully from mostly all modules .the further development of this project I will try
implement new technology. And also this project can be host to the internet.
.
9.BIBLIOGRAPHY
Books
Software Engineering
Ian Sommerville
Sixth Edition
Web Sites
www.msdn.com
www.w3schools.com
www.codeproject.com
www.sqlcourse.com
10.APPENDIX
A.SAMPLE CODING
using System;
using System.Collections.Generic;
using System.Linq;
using System.Web;
using System.Web.UI;
using System.Web.UI.WebControls;
using System.Data.SqlClient;
using System.Data;
SqlCommand cmd;
string gid;
}
protected void Button1_Click1(object sender, EventArgs e)
{
int newflag = 0;
SqlCommand comand = new SqlCommand("select status from usermaster
where username='" + TextBox1.Text + "'", c.con);
SqlDataReader redr = comand.ExecuteReader();
if (redr.Read())
{
if (redr[0].ToString() == "1")
{
newflag = 1;
}
}
redr.Close();
if (newflag == 1)
{
int flag = 0;
string s = TextBox1.Text;
Session["Username"] = TextBox1.Text;
Session["password"] = TextBox2.Text;
SqlCommand cm1 = new SqlCommand("select logstat,secid from logid
where username='" + Session["username"].ToString() + "'", c.con);
SqlDataReader rdr = cm1.ExecuteReader();
while (rdr.Read())
{
Session["logstat"] = rdr["logstat"];
Session["secid"] = rdr["secid"];
}
rdr.Close();
cmd = new SqlCommand();
cmd.Connection = c.con;
cmd.CommandType = CommandType.StoredProcedure;
cmd.CommandText = "login";
cmd.Parameters.AddWithValue("@uname", TextBox1.Text);
cmd.Parameters.AddWithValue("@pas", TextBox2.Text);
cmd.Parameters.AddWithValue("@gid", "User");
cmd.ExecuteNonQuery();
SqlDataReader rd = cmd.ExecuteReader();
while (rd.Read())
{
if (rd["username"].ToString() != s.ToString() ||
rd["password"].ToString() != TextBox2.Text.ToString())
{
}
else
{
flag = 2;
//gid = rd["groupid"].ToString();
}
}
rd.Close();
if (flag == 1)
{
//if (gid == "Admin")
//{
SqlCommand cm = new SqlCommand("update logid set
logstat='1',secid='1' where username='" + Session["username"].ToString() +
"'", c.con);
cm.ExecuteNonQuery();
Response.Redirect("Admin folder/Admindesk.aspx");
}
//}
//else
if (flag == 2)
{
SqlCommand cm = new SqlCommand("update logid set
logstat='1',secid='1' where username='" + Session["username"].ToString() +
"'", c.con);
cm.ExecuteNonQuery();
Response.Redirect("userdesktop.aspx");
}
protected void Login1_Authenticate(object sender, AuthenticateEventArgs e)
{
}
protected void Button2_Click(object sender, EventArgs e)
{
}
protected void Page_Init(object sender, EventArgs e)
{
//Session["username"] = "No User";
//Session["password"] = "No User";
}
protected void Button2_Click1(object sender, EventArgs e)
{
}
}
Sample Screen
Figure 2-REGISTRAATION
Operatinvir
ot
CONTEXT LEVEL 0
Admin/user
Web OS
LEVEL 1
Web os
Admin/use
r
Select option
OS Explorer
Discussion Forum
User
Login
Schedules
LEVEL 2 OF ADMIN
MultiMedia Gallery
Command
Shell
Search
Chat
Mail service
OS Explorer
Administrative Tools
Administrator
Login
Dicussion Forum
LEVEL 2 OF USER
Select Option
Event Log
Events
Multimedia Gallery
Command Shell
Search
Schedules
ER DIAGRAM