Eccentric Network For Intrnet
Eccentric Network For Intrnet
Eccentric Network For Intrnet
Carried out at
In partial fulfillment of the requirements For the award of the degree of BACHELOR OF TECHNOLOGY In INFORMATION TECHNOLOGY
Carried out by
CERTIFICATE
CERTIFICATE OF EXAMINERS
ACKNOWLEDGEMENTS
We manifest our heartier thankfulness pertaining to our contentment over Mrs. xxxxxxx, Department of Information Technology as a project guide with whose
adroit concomitance the excellence has been exemplified in bringing out this project work with artistry. We express our gratitude to head of the department for the encouragement and assistance to us, which contribute to the successful completion of this project. Involuntarily, we are perspicuous to divulge our sincere gratefulness to our principal, xxxxxxxxx , who has been observed posing valiance in abundance forwards our individuality to acknowledge our project work tendentiously.
We express our gratitude to xxxxxxx, Head of the department (IT). for the encouragement and assistance to us, which contribute to the successful completion of this project. A heart full and sincere gratitude to our beloved parents for their tremendous motivation and moral support. We also express the over all exhilaration and gratitude to all those who animated our project work and accentuated our stance.
ABSTRACT
Eccentric network is mainly used in software companies. Because many persons involve in completion of the project like team leader, project leader. Team members should finish their daily task and their source code should be stored in the main server. This is the dayto-day task done by the team members. Project leader assigns modules for the team members. These details are informed to the members manually. If the team member or the team leader is not in the office they cant perform this task. So here we developed a private network for the team leader and the team member. Using this network the project leader can assign the projects to the respective team members. Once the team member comes to work, they can come know the work assigned by checking offline. This information contains with the team member network id and password with project name and the roll of the project and time duration of the projects. Once any team member got the project assignment mail they can interact with our private network and they do their daily task at any time. Here the project leader and
project team member have their individual section for their processing. Using the admin section the project leader can assign the projects. Users can interact with the network through user section. Here they can view all the files and folders, which are uploaded by them. If they have the permission to delete the file it can be done remotely
CONTENTS
CHAPTER-1
1.1. 1.2. 1.3. 1.4. 1.5. 1.6. 1.7.
PREAMBLE
General Introduction Statement of the Problem Objectives of the study Scope of the study Limitations of the study Review of Literature Methodology
Page No
01 01 01 02 02 02 03 09 16 26 26 27 35 39 39 40 40 42
CHAPTER-2
2.1 2.2
PROJECT PROGRAMMING
ASP.NET C#
CHAPTER-3
SYSTEM ANALYSIS
3.1 Analysis Principles 3.2 Information Domain 3.3 Modeling 3.4 Functional Model 3.5 System Requirement 3.6 Hardware Requirement
CHAPTER-4
SYSTEM DESIGN
4.1 Data Design 4.2 Architectural Design 4.3 Interface Design
42
45 46 47 48 60
INTERPRETATION OF RESULTS
Testing Testing Methods
CHAPTER 1
PREAMBLE
Preamble
Provide Interactive interface through which a user can interact with different areas of application easily.
Deploy the application on a single system and make is available on all the systems with in the network, there by reducing the maintenance cost of software. 1
Preamble
1.6 Review of Literature Keeping in view the above problem, apart from the standard literature from various textbooks and websites were referred to understand the various steps involved in the process of development of the project. Information regarding our project was searched. And the information about Net framework has been referred from various websites.
Preamble
All the above literature was found to be more informative in the development of this project.
1.7 Methodology
Microsoft .NET Framework
The .NET Framework is a new computing platform that simplifies application development in the highly distributed environment of the Internet. The .NET Framework is designed to fulfill the following objectives:
To provide a consistent object-oriented programming environment whether object code is stored and executed locally, executed locally but Internet-distributed, or executed remotely.
To provide a code-execution environment that minimizes software deployment and versioning conflicts.
To provide a code-execution environment that guarantees safe execution of code, including code created by an unknown or semi-trusted third party.
To provide a code-execution environment that eliminates the performance problems of scripted or interpreted environments.
To make the developer experience consistent across widely varying types of applications, such as Windows-based applications and Web-based applications.
To build all communication on industry standards to ensure that code based on the .NET Framework can integrate with any other code. The .NET Framework has two main components: the common language runtime
and the .NET Framework class library. The common language runtime is the foundation of the .NET Framework. You can think of the runtime as an agent that manages code at 3
Preamble
execution time, providing core services such as memory management, thread management, and remoting, while also enforcing strict type safety and other forms of code accuracy that ensure security and robustness. In fact, the concept of code management is a fundamental principle of the runtime. Code that targets the runtime is known as managed code, while code that does not target the runtime is known as unmanaged code. The class library, the other main component of the .NET Framework, is a comprehensive, object-oriented collection of reusable types that you can use to develop applications ranging from traditional command-line or graphical user interface (GUI) applications to applications based on the latest innovations provided by ASP.NET, such as Web Forms and XML Web services. The .NET Framework can be hosted by unmanaged components that load the common language runtime into their processes and initiate the execution of managed code, thereby creating a software environment that can exploit both managed and unmanaged features. The .NET Framework not only provides several runtime hosts, but also supports the development of third-party runtime hosts. For example, ASP.NET hosts the runtime to provide a scalable, server-side environment for managed code. ASP.NET works directly with the runtime to enable Web Forms applications and XML Web services, both of which are discussed later in this topic. Internet Explorer is an example of an unmanaged application that hosts the runtime (in the form of a MIME type extension). Using Internet Explorer to host the runtime enables you to embed managed components or Windows Forms controls in HTML documents. Hosting the runtime in this way makes managed mobile code (similar
Preamble
to Microsoft ActiveX controls) possible, but with significant improvements that only managed code can offer, such as semi-trusted execution and secure isolated file storage. The following illustration shows the relationship of the common language runtime and the class library to your applications and to the overall system. The illustration also shows how managed code operates within a larger architecture.
Preamble
compilers generate managed code that conforms to the CTS. This means that managed code can consume other managed types and instances, while strictly enforcing type fidelity and type safety. In addition, the managed environment of the runtime eliminates many common software issues. For example, the runtime automatically handles object layout and manages references to objects, releasing them when they are no longer being used. This automatic memory management resolves the two most common application errors, memory leaks and invalid memory references. The runtime also accelerates developer productivity. For example, programmers can write applications in their development language of choice, yet take full advantage of the runtime, the class library, and components written in other languages by other developers. Any compiler vendor who chooses to target the runtime can do so. Language compilers that target the .NET Framework make the features of the .NET Framework available to existing code written in that language, greatly easing the migration process for existing applications. While the runtime is designed for the software of the future, it also supports software of today and yesterday. Interoperability between managed and unmanaged code enables developers to continue to use necessary COM components and DLLs. The runtime is designed to enhance performance. Although the common language runtime provides many standard runtime services, managed code is never interpreted. A feature called just-in-time (JIT) compiling enables all managed code to run in the native machine language of the system on which it is executing. Meanwhile, the memory manager removes the possibilities of fragmented memory and increases memory locality-ofreference to further increase performance finally, the runtime can be hosted by high6
Preamble
performance, server-side applications, such as Microsoft MS Access and Internet Information Services (IIS). This infrastructure enables you to use managed code to write your business logic, while still enjoying the superior performance of the industry's best enterprise servers that support runtime hosting.NET Framework Class Library The .NET Framework class library is a collection of reusable types that tightly integrate with the common language runtime. The class library is object oriented, providing types from which your own managed code can derive functionality. This not only makes the .NET Framework types easy to use, but also reduces the time associated with learning new features of the .NET Framework. In addition, third-party components can integrate seamlessly with classes in the .NET Framework. For example, the .NET Framework collection classes implement a set of interfaces that you can use to develop your own collection classes. Your collection classes will blend seamlessly with the classes in the .NET Framework As you would expect from an object-oriented class library, the .NET Framework types enable you to accomplish a range of common programming tasks, including tasks such as string management, data collection, database connectivity, and file access. In addition to these common tasks, the class library includes types that support a variety of specialized development scenarios. For example, you can use the .NET Framework to develop the following types of applications and services:
Console applications. Scripted or hosted applications. Windows GUI applications (Windows Forms). 7
Preamble
For example, the Windows Forms classes are a comprehensive set of reusable types that vastly simplify Windows GUI development. If you write an ASP.NET Web Form application, you can use the Web Forms classes.
Project Programming
Project Programming
applications, such as traditional client applications, Web-based applications, or even other XML Web services. As a result, XML Web services technology is rapidly moving application development and deployment into the highly distributed environment of the Internet. If you have used earlier versions of ASP technology, you will immediately notice the improvements that ASP.NET and Web Forms offers. For example, you can develop Web Forms pages in any language that supports the .NET Framework. In addition, your code no longer needs to share the same file with your HTTP text (although it can continue to do so if you prefer). Web Forms pages execute in native machine language because, like any other managed application, they take full advantage of the runtime. In contrast, unmanaged ASP pages are always scripted and interpreted. ASP.NET pages are faster, more functional, and easier to develop than unmanaged ASP pages because they interact with the runtime like any managed application. The .NET Framework also provides a collection of classes and tools to aid in development and consumption of XML Web services applications. XML Web services are built on standards such as SOAP (a remote procedure-call protocol), XML (an extensible data format), and WSDL (the Web Services Description Language). The .NET Framework is built on these standards to promote interoperability with non-Microsoft solutions. For example, the Web Services Description Language tool included with the .NET Framework SDK can query an XML Web service published on the Web, parse its WSDL description, and produce C# or Visual Basic source code that your application can use to become a client of the XML Web service. The source code can create classes derived
10
Project Programming
from classes in the class library that handle all the underlying communication using SOAP and XML parsing. Although you can use the class library to consume XML Web services directly, the Web Services Description Language tool and the other tools contained in the SDK facilitate your development efforts with the .NET Framework. If you develop and publish your own XML Web service, the .NET Framework provides a set of classes that conform to all the underlying communication standards, such as SOAP, WSDL, and XML. Using those classes enables you to focus on the logic of your service, without concerning yourself with the communications infrastructure required by distributed software development. Finally, like Web Forms pages in the managed environment, your XML Web service will run with the speed of native machine language using the scalable communication of IIS. Active Server Pages.NET ASP.NET is a programming framework built on the common language runtime that can be used on a server to build powerful Web applications. ASP.NET offers several important advantages over previous Web development models:
running on the server. Unlike its interpreted predecessors, ASP.NET can take advantage of early binding, just-in-time compilation, native optimization, and caching services right out of the box. This amounts to dramatically better performance before you ever write a line of code.
rich toolbox and designer in the Visual Studio integrated development environment.
11
Project Programming
WYSIWYG editing, drag-and-drop server controls, and automatic deployment are just a few of the features this powerful tool provides.
runtime, the power and flexibility of that entire platform is available to Web application developers. The .NET Framework class library, Messaging, and Data Access solutions are all seamlessly accessible from the Web. ASP.NET is also language-independent, so you can choose the language that best applies to your application or partition your application across many languages. Further, common language runtime interoperability guarantees that your existing investment in COM-based development is preserved when migrating to ASP.NET.
form submission and client authentication to deployment and site configuration. For example, the ASP.NET page framework allows you to build user interfaces that cleanly separate application logic from presentation code and to handle events in a simple, Visual Basic - like forms processing model. Additionally, the common language runtime simplifies development, with managed code services such as automatic reference counting and garbage collection.
system, which simplifies applying settings to your server environment and Web applications. Because configuration information is stored as plain text, new settings may be applied without the aid of local administration tools. This "zero local administration" philosophy extends to deploying ASP.NET Framework applications as well. An ASP.NET Framework application is deployed to a server simply by copying the
12
Project Programming
necessary files to the server. No server restart is required, even to deploy or replace running compiled code.
Scalability and Availability. ASP.NET has been designed with scalability in mind, with features specifically
tailored to improve performance in clustered and multiprocessor environments. Further, processes are closely monitored and managed by the ASP.NET runtime, so that if one misbehaves (leaks, deadlocks), a new process can be created in its place, which helps keep your application constantly available to handle requests.
Customizability and Extensibility. ASP.NET delivers a well-factored architecture that allows developers to
"plug-in" their code at the appropriate level. In fact, it is possible to extend or replace any subcomponent of the ASP.NET runtime with your own custom-written component. Implementing custom authentication or state services has never been easier. Security. With built in Windows authentication and per-application configuration, you can be assured that your applications are secure. Language Support The Microsoft .NET Platform currently offers built-in support for three languages: C#, Visual Basic, and JScript.
13
Project Programming
What is ASP.NET Web Forms? The ASP.NET Web Forms page framework is a scalable common language runtime programming model that can be used on the server to dynamically generate Web pages. Intended as a logical evolution of ASP (ASP.NET provides syntax compatibility with existing pages), the ASP.NET Web Forms framework has been specifically designed to address a number of key deficiencies in the previous model. In particular, it provides: The ability to create and use reusable UI controls that can encapsulate common functionality and thus reduce the amount of code that a page developer has to write. The ability for developers to cleanly structure their page logic in an orderly fashion (not "spaghetti code"). The ability for development tools to provide strong WYSIWYG design support for pages (existing ASP code is opaque to tools). ASP.NET Web Forms pages are text files with an .aspx file name extension. They can be deployed throughout an IIS virtual root directory tree. When a browser client requests .aspx resources, the ASP.NET runtime parses and compiles the target file into a .NET Framework class. This class can then be used to dynamically process incoming requests. (Note that the .aspx file is compiled only the first time it is accessed; the compiled type instance is then reused across multiple requests). An ASP.NET page can be created simply by taking an existing HTML file and changing its file name extension to .aspx (no modification of code is required). For example, the following sample demonstrates a simple HTML page that collects a user's
14
Project Programming
name and category preference and then performs a form post back to the originating page when a button is clicked: ASP.NET provides syntax compatibility with existing ASP pages. This includes support for <% %> code render blocks that can be intermixed with HTML content within an .aspx file. These code blocks execute in a top-down manner at page render time. Introduction to ASP.NET Server Controls In addition to (or instead of) using <% %> code blocks to program dynamic content, ASP.NET page developers can use ASP.NET server controls to program Web pages. Server controls are declared within an .aspx file using custom tags or intrinsic HTML tags that contain a runat="server" attributes value. Intrinsic HTML tags are handled by one of the controls in the System.Web.UI.HtmlControls namespace Server controls automatically maintain any client-entered values between round trips to the server. This control state is not stored on the server (it is instead stored within an <input type="hidden"> form field that is round-tripped between requests). Note also that no client-side script is required. In addition to supporting standard HTML input controls, ASP.NET enables developers to utilize richer custom controls on their pages. For example, the following sample demonstrates how the <asp: adrotator> control can be used to dynamically display rotating ads on a page. ASP.NET Web Forms provide an easy and powerful way to build dynamic Web UI.
15
Project Programming
ASP.NET Web Forms pages can target any browser client (there are no script library or cookie requirements). ASP.NET Web Forms pages provide syntax compatibility with existing ASP pages. ASP.NET server controls provide an easy way to encapsulate common functionality. ASP.NET ships with 45 built-in server controls. Developers can also use controls built by third parties. ASP.NET server controls can automatically project both up level and down-level HTML. ASP.NET templates provide an easy way to customize the look and feel of list server controls. ASP.NET validation controls provide an easy way to do declarative client or server data validation.
2.2 C#.NET
ADO.NET OVERVIEW
ADO.NET is an evolution of the ADO data access model that directly addresses user requirements for developing scalable applications. It was designed specifically for the web with scalability, statelessness, and XML in mind. ADO.NET uses some ADO objects, such as the Connection and Command objects, and also introduces new objects. Key new ADO.NET objects include the Dataset, Data Reader, and Data Adapter.
16
Project Programming
The important distinction between this evolved stage of ADO.NET and previous data architectures is that there exists an object -- the Dataset -- that is separate and distinct from any data stores. Because of that, the Dataset functions as a standalone entity. You can think of the Dataset as an always disconnected record set that knows nothing about the source or destination of the data it contains. Inside a Dataset, much like in a database, there are tables, columns, relationships, constraints, views, and so forth.
A Data Adapter is the object that connects to the database to fill the DataSet. Then, it connects back to the database to update the data there, based on operations performed while the Dataset held the data. In the past, data processing has been primarily connection-based. Now, in an effort to make multi-tiered apps more efficient, data processing is turning to a message-based approach that revolves around chunks of information. At the center of this approach is the Data Adapter, which provides a bridge to retrieve and save data between a Dataset and its source data store. It accomplishes this by means of requests to the appropriate SQL commands made against the data store. The XML-based Dataset object provides a consistent programming model that works with all models of data storage: flat, relational, and hierarchical. It does this by having no 'knowledge' of the source of its data, and by representing the data that it holds as collections and data types. No matter what the source of the data within the Dataset is, it is manipulated through the same set of standard APIs exposed through the Dataset and its subordinate objects. While the Dataset has no knowledge of the source of its data, the managed provider has detailed and specific information. The role of the managed provider is to connect, fill, and persist the Dataset to and from data stores. The OLE DB and SQL Server .NET Data Providers (System.Data.OleDb and System.Data.SqlClient) that are part of the .Net 17
Project Programming
Framework provide four basic objects: the Command, Connection, DataReader and Data Adapter. In the remaining sections of this document, we'll walk through each part of the Dataset and the OLE DB/SQL Server .NET Data Providers explaining what they are, and how to program against them. The following sections will introduce you to some objects that have evolved, and some that are new. These objects are:
Connections: For connection to and managing transactions against a database. Commands: For issuing SQL commands against a database. DataReaders: For reading a forward-only stream of data records from a SQL
Datasets: For storing, Remoting and programming against flat data, XML data and
relational data.
DataAdapters: For pushing data into a DataSet, and reconciling data against a
database. When dealing with connections to a database, there are two different options: SQL Server .NET Data Provider (System.Data.SqlClient) and OLE DB .NET Data Provider (System.Data.OleDb). In these samples we will use the SQL Server .NET Data Provider. These are written to talk directly to Microsoft SQL Server. The OLE DB .NET Data Provider is used to talk to any OLE DB provider (as it uses OLE DB underneath).
Connections:
Connections are used to 'talk to' databases, and are represented by providerspecific classes such as SqlConnection. Commands travel over connections and result sets are returned in the form of streams which can be read by a DataReader object, or pushed into a DataSet object.
18
Project Programming
Commands:
Commands contain the information that is submitted to a database, and are represented by provider-specific classes such as SqlCommand. A command can be a stored procedure call, an UPDATE statement, or a statement that returns results. You can also use input and output parameters, and return values as part of your command syntax. The example below shows how to issue an INSERT statement against the Northwind database.
Data Readers:
The DataReader object is somewhat synonymous with a read-only/forward-only cursor over data. The DataReader API supports flat as well as hierarchical data. A DataReader object is returned after executing a command against a database. The format of the returned DataReader object is different from a recordset. For example, you might use the DataReader to show the results of a search list in a web page.
19
Project Programming
updating the source data. The Get Changes method of the Dataset object actually creates a second Dataset that contains only the changes to the data. This Dataset is then used by a Data Adapter (or other objects) to update the original data source. The Dataset has many XML characteristics, including the ability to produce and consume XML data and XML schemas. XML schemas can be used to describe schemas interchanged via Web Services. In fact, a Dataset with a schema can actually be compiled for type safety and statement completion.
20
Project Programming
Performance
1. ADO.NET is the next evolution of ADO for the .Net Framework. 2. ADO.NET was created with n-Tier, statelessness and XML in the forefront. Two new objects, the DataSet and DataAdapter, are provided for these scenarios. 3. ADO.NET can be used to get data from a stream, or to store data in a cache for updates. 4. There is a lot more information about ADO.NET in the documentation. 5. Remember, you can execute a command directly against the database in order to do inserts, updates, and deletes. You don't need to first put data into a DataSet in order to insert, update, or delete it. 6. Also, you can use a DataSet to bind to the data, move through the data, and navigate data relationships
systems are relational databases. Also, server databases such as relational databases on mainframe or minicomputer systems support the use of Structured Query Language (SQL), as well as proprietary tools for accessing data.
21
Project Programming
22
Project Programming
Hierarchical and network databases were difficult to work with for several reasons. One reason was that the physical and logical definitions of data storage in hierarchical and network databases had to be written in a cryptic syntax. Another difficulty of working with data definitions came from the fact that different types of internal pointers, numeric references to data locations, and other lowlevel details had to be set up and stored through the databases. The pointers were used for the subsequent direct retrieval of data. In Cods relational database model, the data is referenced as though it were stored in a two-dimensional table. The actual physical storage of the data-although significant for the time required to store, change, or retrieve data-is insignificant syntactically for reference. The two-dimensional table model permits data to be referenced as the rows and columns of the table. In a Relational Database, data is referenced as the rows and columns of a table. We can easily visualize data stored as a table, because we often encountered data stored in tables in every day life. We reference train and plane schedules as a table, for example and we create typical work sheets as a table.
23
Project Programming
Each system in a client/server model performs one or more of the data storage, access, or processing operations. Client/Server computing can not be done with a system that uses terminals or PCs running terminal emulators that are connected to another computer. In this arrangement, the terminal are the PC thats used as a terminals is simply too passive; it only sends and displays sets of characters. When PCs and Servers are connected, the overall processing should be divided between the server, main frame, or mini computer system and the client system. The client and the server each process works with in its own capability. A form of team work that contributes to the efficiency and speed of the overall operation. Client/Server as the name implies, also involves an unequal division of processing. The in equality results from the processing disparity between the server and the client. The larger and faster server computer transfers data faster, stores greater qualities of data, and typically performs more extensive processing than the client system. Smaller PC Systems are used as Client in Client/Server systems because the PCs perform proportionally less of the overall work, relaying primarily on the server for heavy duty data manipulation. Also , the PCs key board and monitor allowed into work as an input device , by generating commands and data , and as on output device by displaying data to the user. MS SQL Server is a perfect example of a Client/Server system. The SQL Server Database must be installed on the Windows NT platform. The Windows NT operating system provides an extremely broad range of processor systems that we can use as our server. Windows NT is supported on I86 Processor based systems, PPC, MIPS, and ALPHA AXP RISC Processor based systems.
24
Project Programming
SQL Server provides the server software that install on the server system and some client software thats installed on the client PC systems Windows GUI application tools allow into create , maintain and access the database and all objects from the client. The Network software components required for the inter connection of clients and server computer are built into the windows NT system. Windows NT also provides a choice of network protocols for communication between the client and the server systems. A Client can run windows 95, which also contains built-in network software for connection with the Windows.NT server system. The Window95 Client and Windows.NT server systems support a void range of network cards.
25
CHAPTER-3
SYSTEM ANALYSIS
System Analysis
Its necessary to take a header look at softwares role-to understand the specific requirements that must be achieved to build high quality software. Thats the job of software requirement Analysis. Requirement analysis allows the job of the software allocation and builds models of the data, functional, and behavioral domains that will be treated by software. It is a task that bridges the gap between system levels requirements engineering and software design. It provides the software designer with a representation of information, function, and behavior that can be translated to data, architectural, interface, and component-level designs. Finally, the requirement specification provides the developer and the customer with means to access quality once software is built.
26
System Analysis
building activity. Establishing a complete information description a detailed functional and behavioral description an indication of performance requirements and design constraints and other data pertinent to requirements refines the function and performance allocated to the system.
3.3 Modeling:
The tools that are used in software requirement analysis are 1. Data flow diagrams and 2. Data dictionary
DFD SYMBOLS:
In the DFD, there are four symbols 1. A square defines a source(originator) or destination of system data 2. An arrow identifies data flow. It is the pipeline through which the information flows 3. A circle or a bubble represents a process that transforms incoming data flow into outgoing data flows. 4. An open rectangle is a data store, data at rest or a temporary repository of data
27
System Analysis
Data flow
Data Store
CONSTRUCTING A DFD:
Several rules of thumb are used in drawing DFDs: 1. Process should be named and numbered for an easy reference. Each name should be representative of the process. 2. The direction of flow is from top to bottom and from left to right. Data traditionally flow from source to the destination although they may flow back to the source. One way to indicate this is to draw long flow line back to a source. 3. An alternative way is to repeat the source symbol as a destination. Since it is used more than once in the DFD it is marked with a short diagonal. 4. When a process is exploded into lower level details, they are numbered.
28
System Analysis
5. The names of data stores and destinations are written in capital letters. Process and dataflow names have the first letter of each work capitalized A DFD typically shows the minimum contents of data store. Each data store should contain all the data elements that flow in and out. Questionnaires should contain all the data elements that flow in and out. Missing interfaces redundancies and like is then accounted for often through interviews.
1. CURRENT PHYSICAL:
In Current Physical DFD process label include the name of people or their positions or the names of computer systems that might provide some of the overall system-processing label includes an identification of the technology used to process the data. Similarly data flows and data stores are often labels with the names of the actual physical media on hich data are stored such as file folders, computer files, business forms or computer tapes.
2. CURRENT LOGICAL:
29
System Analysis
The physical aspects at the system are removed as mush as possible so that the current system is reduced to its essence to the data and the processors that transform them regardless of actual physical form.
3. NEW LOGICAL:
This is exactly like a current logical model if the user were completely happy with he user were completely happy with the functionality of the current system but had problems with how it was implemented typically through the new logical model will differ from current logical model while having additional functions, absolute function removal and inefficient flows recognized.
4. NEW PHYSICAL:
The new physical represents only the physical implementation of the new system.
DATA STORE
1) Data cannot move directly from one data store to another data store, a process must move data. 2) Data cannot move directly from an outside source to a data store, a process, which receives, must move data from the source and place the data into data store 3) A data store has a noun phrase label.
SOURCE OR SINK
The origin and /or destination of data
30
System Analysis
1) Data cannot move direly from a source to sink it must be moved by a process 2) A source and /or sink has a noun phrase land
DATA FLOW
1) A Data Flow has only one direction of flow between symbols. It may flow in both directions between a process and a data store to show a read before an update. The later is usually indicated however by two separate arrows since these happen at different type. 2) A join in DFD means that exactly the same data comes from any of two or more different processes data store or sink to a common location. 3) A data flow cannot go directly back to the same process it leads. There must be at least one other process that handles the data flow produce some other data flow returns the original data into the beginning process. 4) A Data flow to a data store means update (delete or change). 5) A data Flow from a data store means retrieve or use. A data flow has a noun phrase label more than one data flow noun phrase can appear on a single arrow as long as all of the flows on the same arrow move together as one package.
31
System Analysis
About login
Login
About Eccentric
Events
Achievem ents
Forgetting of Password
Clients
Project Leader
Project Member
Admin MODULE
Compose Compose
Inbox
Sent Items
Work Space
Forms
About
32
Project
Project, Employee, Clients
System Analysis
Compose
Inbox
Sent Items
Work Space
People Finder
Project Member
News
Forms
Details Of User
About
Project Compose
Inbox Sent Items
Work Space
People Finder
News
Forms
Details Of User
About
Project
System Analysis
Clients
Details Of User
Compose
Inbox
Sent Items
Work Space
News
Forms
About
Project
3.4 Functional Model: The complete system can be divided into two halves on basis of access levels A) User interaction module
34
System Analysis
About: Eccentric Network is mainly used in software companies. In this company day to day tasks are intimated by the project leader. And communication and event news over the work group is also manual. Events: The information regarding the project will be shared by each member and they completed their work within time. It provides instant information regarding work under5 process within the company. Achievements: Management interacts with private network and share their views and internal communication on the application of the organization. It should arrange conference over the processing information in order to reach destination. Forgetting of Password: If users forget the Password, then some hint will be provided for getting the password.
35
System Analysis
Administrator: An administrator has all the privileges that of the guest as well as the normal registered user. Along with these common features an administrator has the administrator related features such as creating new users and granting roles to those newly created users. The roles granted by the administrator cannot be changes by the user. An administrator can create new user as a guest or as a user or as an administrator. The access levels are as per the grants done by the administrator. An administrator can also be part of a team and could lead a project team this is possible only if administrator when building a team includes himself in the team section. If included as a manager he is not a part of the team but supervisor of the team. The register option on the homepage of the application is provided only to register a new user as a guest.
PROJECT LEADER
Deliver Results: Project results delivered on time, within budget. Implement change when and where needed with skilled project management. Control performance: Plan, estimate and schedule to control scope, performance and risk . Control the project explosion.
Solve Problems:
Challenges-solutions for tough problems-ready when needed just in time tested and proven in the caldron of projects Develop Leaders
36
System Analysis
Enable project leaders and project teams to achieve extraordinary results. Exceptional teamwork breeds success.
PROJECT MEMBERS
Being a great project member can aid the team process as much as a good team leader. Just as project members will have expectations of team leaders, they will also have expectations of other team members. Here are some of the elements that make a great team member: Commitment to the team above themselves. Positive contribution to the team process and goals. Enthusiasm energy, inspiration and sufficient expertise. Willingness to take responsibility for elements of the teams work. If an individual is to be fully valued by team, they must be committed to the success of the team. If they agree to carryout action steps at team meetings, there is an expectation that these will be carried out, unless that expectation is changed. If at the following team meeting, the team is surprised by an individual not delivering on what they agreed, there is a danger that they will lose trust in the individual.
Clients:
Provide Clients: Provide necessary business information Ensure deliverables are prepared to satisfy the project requirements, cost and schedule. Help provide status reporting of team activities against the program plan or schedule keep the coordinates meetings with the product committee. 37
System Analysis
The team is surprised by an individual not delivering on what they agreed, there is a danger that they will lose trust in the individual. It is better to resist the pressure to deliver initially and set appropriate expectations, than to say yes, and then spend the next weeks finding ways of apologizing.
access to its file system. This command will normally be the first command transmitted by the user after the control connections are made (some servers may require this). PASSWORD (PASS) This command must be immediately preceded by the user name
command, and, for some sites, completes the user's identification for access control. Since password information is quite sensitive, it is desirable in general to "mask" it or suppress type out.
Requirements
3.5 System Requirements
Web-Technologies : ASP.NET 38
System Analysis
: : : :
39
CHAPTER 4
SYSTEM DESIGN
System Design
After completing the analysis of the project, we have clearly got the set of goals to be achieved. In the design phase we have to make an overall of structure of the project using the data collected from the analysis phase. Design is a meaningful engineering representation of something that is to be built. Software design is located at the technical kernel of software engineering and is applied regardless of software process model that is used. It is first of the three technical activity designs, code generation and test. It focuses all four major areas of concern: Data Design Architectural Design Interface Design Code Design
Project Details
S .No 1 2 3 4 5 6 7 8 9 Column Name Project id Project name Project status Start date Completion date Client name Client location Project description Id information Data Type int nvarchar (50) nvarchar(50) smalldatetime smalldatetime varchar(50) varchar(50) varchar(MAX) Varchar(50) Description
40
System Design
Forums
S .No 1 2 3 4 5 Column Name Subject Username Authority Message Date of post Data Type varchar(50) varchar(50) Varchar(50) ntext datetime Description
Inbox
S .No 1 2 3 4 5 Column Name to1 from1 subject message date Data Type varchar(50) Varchar(50) Varchar(50) Varchar (MAX) datetime Description
News
S .No 1 2 3 4 5 Column Name subject username authority message dateofpost Data Type varchar(50) varchar(50) varchar(50) ntext char(10) Description
UserDetails
S.No 1 2 3 4 5 6 7 8 9 10 11 Column Name firstname lastname username password authority phoneno email Dateofbirth securityquestion answer location Data Type nchar(10) nchar(10) nvarchar(50) nvarchar(50) nvarchar(50) char(10) nvarchar(50) nchar(10) nvarchar(50) nvarchar(50) nvarchar(50) Description
41
System Design
42
System Design
assessed for quality; this is the only way that can accurately translate the user requirements into finished software product or system. System design serves as the foundation for all software engineering and software maintenance steps that follow. System design goes through two phases of development: logical and physical design.
Logical Design
This design describes the inputs, outputs, databases and procedures all in a format that meets the users requirements. Logical design specifies the user needs at a level of detail that virtually determines the information flow into and out of the system and the required data resources. The design covers the following: Input/Output specifications This include screens, format and content. File specifications This includes specifying rules for edit correction, backup procedures and the controls that ensure processing and file integrity. Processing specifications This specifies the implementation plan.
Physical Design
Logical design is followed by physical design. This produces the working system by defining the design specifications that tell programmers exactly what the system must do. This produces the report on a hard copy or displays it on a screen, and maintains an updated database at all times. This design consists of following steps: Design physical system This specifies input/output media, design of database and design of information flow. Plan system implementation This specifies the target date. Determines training procedures and courses. Devise a test and implementation plan. This system has been designed with a scientific approach and ended developing an application,
43
System Design
which can be used, and embed in ease and can utilize it for further developments and in applications where it is felt necessary.
44
CHAPTER 5
INTERPRETATION OF RESULTS
Interpretation of Results
5.1 TESTING :
The completion of a system is achieved only after it has been thoroughly tested and implemented. Though this gives a feel the project is completed, there cannot be any project without going through this stage. Though the programmer may take many precautions not to commit any mistakes that crop up during the execution stage. Hence in this stage it is decided whether the project can under go the real time environment execution without any breakdowns, therefore a package can be rejected even this stage. In short this stage is meant to decide if the package is good for complete implementation.
ROBUSTNESS:
To study the behavior of the module in case of feeding in the relevant data and ensure that the system is able to display appropriate message and role back to its initial state.
45
Interpretation of Results
46
CHAPTER 6
CONCLUSION
Conclusion
SYSTEM EVALUATION:
The developed software is tested with sample data and outputs obtained in according to the requirements. The performance of the system is evaluated, and is found to be much more efficient than the existing system. Though it could not be claimed that ours is an ideal project, it will meet the primary requirements of the concern. Even though we have tried our level best to make it a dream project, due to time constraints we could not add more facilities to it. So the project has to be improved by having modifications as and when the necessity arises in due course.
FUTURE EXPANSIONS:
The efficiency of developed system can be much enhanced with some minor modifications. Further developments can be made in the proposed system by implementing the Eccentric Network for Intranet. They are: 1. The application is capable of managing only projects and their respective allotments where as there is not scope of communication between two project groups or between the employees. The information between them is still in terms of documents. The application can improve in this area of communication and document preservation as well as client maintenance. 2. The application can be converted into a Mobile based using ASP.net with which the deployment of application will be done only on enterprises server and is accessible to all other departments of the organization. The current application is confined to only one enterprise.
47
CHAPTER 7
ANNEXURES
Annexure
48
Annexure
49
Annexure
Fig(7.3):- It shows the total people of Eccentric Network Fig (7.3):- It shows News in Eccentric Network
Fig (7.4):- It shows the Forums of Eccentric Network Fig (7.4.1):- It shows the Creation of Forums in Eccentric Network Fig (7.5):- It shows the Details of use in Eccentric Network Fig (7.6):- It shows the About of Administrator work in Eccentric Network Fig (7.7):- It shows the Project info of Eccentric Network Fig (7.7.1):- It shows the Creation of Project details Eccentric Network
Fig (7.8):- It shows the Clients Info Eccentric Network Fig (7.8.1):- It shows the Creation of Client Eccentric Network
Annexure
Fig (7.9.1):- It shows the Employee Creation in Eccentric Network Fig (7.10):- It shows the Compose box of Eccentric Network Fig (7.11):- It shows the Inbox of the login member in Eccentric Network Fig (7.12):- It shows the Sent Items of the login member in Eccentric Network
Fig (7.13):- It shows the Inbox or Sent Items message of login member in Eccentric Network
51
CHAPTER 8
BIBLIOGRAPHY
Bibliography
BOOKS REFERRED:
[1]. [2]. Roger.S.Pressman, Software Engineering. Mc.Graw Hill, Apress.Beginning. ASP.NET.2.0.in.C.Sharp.2005.
Novice.to.Professional, Jan 2006 [3]. [4]. Karumanchi Narayana Rao, Introduction to Microsoft .net. Database Management System. Raghu Ramakrishnan,
60