1.

INTRODUCTION
1.1 Project Profile ABOUT THE PROJECT Definition
SOFTWARE PROJECT MANAGEMENT TOOL deal with the various levels

of project development and will account for time used in phase viz analysis,design, coding, testing and implementation etc.

Description
SOFTWARE PROJECT MANAGEMENT TOOL gives the management clear picture of usage of time by projects. By analyzing the results provided by the software They might resify the defects in utilizing time and take remedial actions. It takes timesheet reports as input. It gives the individual reports of the project, which contains time used for various tasks. In this tool CLIENT gives requirements to the BDO and makes an agreement with him. The new project information is entered by the BDO, based on the project information the PROJECT MANAGER will take resources from the HR and assign activities to DEVELOPERS who are working under him. Employees fill the time sheet and complete the task assigned to them .these completed tasks are tested and finally the project is submitted to the client.This project deals with five modules Client, Bussiness development officer (BDO), Developer, Human Resource Manager (HR), Project Manager (PM). Client deals with checking the status of the project by the client. Only the authenticated client login to the web page and checks in which phase the project is. BDO deals with collecting the requirements from the client and add the client details and project details into the database and also views and updates the respective details Developer deals with filling the timesheets. Updating and viewing the timesheets and also checking the project status.

HR deals with providing resources to the project manager by checking the employee details like skill and designation. HR can also view the status of the project. PM deals with planning the project i.e. dividing the project into different tasks and assigning those tasks to the developers. PM also checks the timesheets of developers. Fills his own timesheet, updates and views the timesheet. PM can also check the status of the project. Software Project Mangaement Tool (SPMT) will do the following tasks: Record different phases of project. Define phase wise tasks. Keep a track of project schedules. Record project definition. Phase wise project closures. Assign resources to a project. Access control for resources. Take daily efforts from each resource.

Objectives
The objectives of this application is functionality and architecture of the SOFTWARE PROJECT MANAGEMENT TOOL, and to estimate the effort of the project. The general objectives are: Maintain project details. Maintain client details. Maintain employee details.

2. SOFTWARE REQUIREMENTS
HARDWARE AND SOFTWARE REQUIREMENTS

Hard ware Specification

Processor Processor Speed RAM Hard Disk : : : : Intel P-IV based system 250 MHz to 833MHz 512MB 8GB to 30GB

Software Specification
Language Technologies Database Web/Application server Operating System : : : : : C#.NET ASP.NET SQL SERVER 2000 Internet Information services (IIS) Windows NT/2000/XP

3. SYSTEM ANALYSIS
3.1 Requirement Analysis
A requirement is a feature that must be included in the actual design and

implementation, getting to know the system to be implemented is of prime importance. Main emphasis is on: The inputs to the system. The output expected from the system. The people involved in the working of the system. The volume of DATA (INPUTS) and the amount of INFORMATION (OUTPUTS) that will be involved. With respect to the system itself, the following facts are taken into consideration. The major process involved. The main points of application . The processing rules for the collected data . The exceptions that may be present . The checks that should be placed in order to avoid wrong entries.

Purpose
The purpose of this document is that it deals with various levels of project development and will account for time used in analysis, design, programming, testing and verification etc.

Scope
The tool involved in giving the management the clear picture of the usage of time by projects by analyzing the results provided by the software. Documentation overview:This document has major sections. Section1 provides an overview of entire software requirement specification. Section2 provides the product that will be produced. Section3 addresses the specific requirements of the system.

3.2 Proposed System

To take advantage of the latest technology and to facilitate client to make Online inquires about their project status a tool need to be developed. The tool should accomplish the following functions. The tool should be able to manage all the projects effectively and ensure that projects cycle goes on smoothly and they are completed on time. While accepting clients requirements, al necessary validations should be performed. It should also store the clients details.

The system should generate the following reports: Clients details list. Employee details list.

Allocated resources list.

Project details list. Allocated tasks list.

Investigation
For the study of the project, I met the client and collect his requirements and got the information about various levels of project development and time assigned for each phase. The main objective of this study is to determine whether the proposed system is feasible or not. Solution strategies are usually generated without regard for feasibility because one cannot be both creative and critical at the same time. Hence feasibility analysis is a must to arrive at the most appropriate solution strategy. This feasibility analysis is done after the thorough study of the system. The planning objective is achieved through a process of information discovery that leads to reasonable estimation. Keeping the following aspects in mind, the system analysis for the development of the project is done. Identify the drawbacks of the existing system. Identify the need for conversion. Perform feasibility study. Identify hardware, software and the database requirements. Create a system definition that performs the foundation for the subsequent work.

Software Scope
The first activity in software project planning is the determination of the software scope. The functions and performance allocated to software should be assesses to establish a project scope. Software scope describes function, performance, reliability and constraints.

Estimation
Software project planning estimate can be done in many ways such as Lines Of Code (LOC) based estimation, Functional Point Estimation (FP), Process Based Estimation. We should select best of them depending on the requirement.

Resource Availability
The resources which are common to any system, consist of human effort, information

and development resource. Developing any system with out satisfactory resources is inappropriate and impossible. The design development team for this project consists of five members or roles that are responsible for software development and internal testing and its usage. Information assembly is vital to this project. Various sources of information are available.

3.3 Modules Business Development Officer

He is a person who actually, interacts with the people who are demanding the project. He collects all the requirements of their projects.

Project Manager
The manger from the name itself indicates that to manage the projects. He plans the project and takes requirements from the HR. he then divides the project into tasks and assigns those tasks to the developers. He fills his own timesheet and also checks the developers timesheets.

Developer
He deals with the actual coding part i.e. filling the time sheets and perform coding according to the time allotted to him. He then submits the filled timesheets and completed task to the system.

Human Resource Manager

His main activity is to provide resources to the project. he also checks the time sheets and decides the remuneration for the work done according to the time, in that timesheet.

Client
He is the person who demands the project and specifies the time, for which he needs the project back done. If the time is large slot then he has to accept the problems, and partial results. So that, he could place the new requirements for his project along with the advancement in the technology used.

Operational Feasibility
The system is operationally feasible, it is made so easy that operator will not encounter any problem during working, as it is very user-friendly. Operational feasibility checks the scope of the system. The system under consideration should have enough operational research. It is observed that the proposed system would provide a very interactive means to share information and have a far and wide range. The proposed system would make the information more interactive. Thus operational feasibility of the proposed system id found to be high.

4. SYSTEM DESIGN
4.1 Introduction
The most creative and challenging phase of the life cycle is system design. The term design describes a final system and the process by which it is developed. It refers to the technical specifications that will be applied in implementations of the candidate system. The design may be defined as the process of applying various techniques and principles for the purpose of defining a device, a process or a system with sufficient details to permit its physical realization. The designers goal is how the output is to be produced and in what format. Samples of the output and input are also presented. Second input data and database files have to be designed to meet the requirements of the proposed output. The processing phases are handled through the program Construction and Testing. Finally, details related to justification of the system and an estimate of the impact of the candidate system on the user and the organization are documented and evaluated by management as a step toward implementation. The importance of software design can be stated in a single word Quality. Design provides us with representations of software that can be assessed for quality. Design is the only way where we can accurately translate a customers requirements into a complete software product or system. Without design we risk building an unstable system, which might fail if small changes are made. It may as well be difficult to test, or could be one whos quality cant be tested. So it is an essential phase in the development of a software product. The following steps are followed in designing software: The statements of functions desired from software to be developed are recognized. The database design steps are applied to identify the various entities and relationships between them. General access methods are then applied to the conceptual schema to get the logical model, which is then further transformed into relational tables. The concept of s/w engineering is then applied to get logical architecture of the system comprising of different modules each containing all the related functions.

4.2 Data Flow Diagrams

A graphical tool used to describe and analyze the moment of data through a system manual or automated including the process, stores of data, and delays in the system. Data Flow Diagrams are the central tool and the basis from which other components are developed. The transformation of data from input to output, through processes, may be described logically and independently of the physical components associated with the system. The DFD is also know as a data flow graph or a bubble chart.

Context Diagram:
The top-level diagram is often called a context diagram. It contains a single process, but it plays a very important role in studying the current system. The context diagram defines the system that will be studied in the sense that it determines the boundaries. Anything that is not inside the process identified in the context diagram will not be part of the system study. It represents the entire software element as a single bubble with input and output data indicated by incoming and outgoing arrows respectively.

Types of data flow diagrams

DFDs are two types

1. Physical DFD:
Structured analysis states that the current system should be first understand correctly. The physical DFD is the model of the current system and is used to ensure that the current system has been clearly understood. Physical DFDs shows actual devices, departments, people etc., involved in the current system

2. Logical DFD:
Logical DFDs are the model of the proposed system. They clearly should show the requirements on which the new system should be built. Later during design activity this is taken as the basis for drawing the systems structure charts.

10

The Basic Notation used to create a DFDs are as follows: Dataflow: Data move in a specific direction from an origin to a
Destination.

Process:

People, procedures, or devices that use or produce (Transform) Data. The physical component is not identified.

Source:

External sources or destination of data, which may be People , programs, organizations or other entities.

Data Store: Here data are stored or referenced by a process in the

System

11

CLIENT

BDO

Reqirements Project Details Client Information

Implementation Plan

PM
Details

SPMT

Task Plan Time Sheets

DEVELOPER

HRM

Manpower

Client DFD
D3
C Acoounts

User acounts

D2
D3

project DB
User acounts

D3

User acounts

Login Client Message

P1
Authenti cation
Uid, pwd

project DB C Acoounts

P3

BDO

Agreemen t Proposal
Cost,time

Client
C Acoounts

P4
D1
C Acoounts

Client DB

Client
C Acoounts

Status checking

Time
Project

D2 DB

12

BDO DFD

D3

User Acount

P1 BDO Authentication

P4
Status Checking

BDO

uid,pwd

D1 Client DB D2 Project DB

P2 Providin gDetails s
Client,Proj

P3
Agreeme nt process

D2 Project DB

Cost,time

Client

13

PM Level1 Client
PM Message P1 P2 PM Authentication
Uid,pwd Platform

D2

Project DB

P3
Project Planning Process

Acquires Project Details

Time

D3 User Account D2 Project DB

Requesting P4 Requesting Resources

P5 Task Allocation Checking task Progress

Time,Quali ty

Time,Dura tion

HR

Developer

PM

14

PM Level2 DFD
HR

P3.1

P3.2

P4.4

Retrieving
Deve loper

Project Plan Process

Uid,pwd

Feedback From Official

Uid,pwd

Project infor
Uid,pwd

Officials D2 Developer

P3.3

Approval of The plan

Uid,pwd

PM

D2

Developer

15

Human Resource

HR Message P1
Authentication

D2 P2

Project DB P5
Status Checking

Taking Project Plan

HR
Uid,pwd

HR

D2 D3
User Accounts

Project

P3
Checking

P4

D4

Employee DB

Resources availability

Allocates Resources

HR

16

Developer DFD:

D3

User Accounts

D2

Project DB

P1

P4

Authentication
Developer
Login

Submission Of Tasks&Time Sheet

PM

Uid,pwd

Uid,pwd

Message D2 Project DB

P2
Accepting Tasks

P3 D2 Project DB
Viewing Project Details

PM

17

4.3UML Diagrams 4.3.1E-R Diagram

The following diagrams depicts various entities involve in the Software project management tool and relationships those entities.
Check s

Requirement s

Provides

Accepts Works for Assigns

Maintains

Views

Allocates

18

4.3.2 Class Diagram:

19

4.3.3Usecase Diagram

Checks Status client

Takes final project

maintain client details BDO maintain project details

Allocate tasks

Provides login d's&passwords Project Manager(PM)

checktimesheets

maintain emp list Human Resource (HR) developer

maintain timesheets

20

4.3.4Client Sequence Diagram:

client validate client search project client record project record status of project

1: input clientid 2: valid/invalid

3: validate client id

4: clent record

5: input projectID

6: check projectID

7: project record 8: projectId correct/wrong

9: project status 10: % of work completed

21

5. DESIGN CONVENTION
GUISTANDARDS Labels
A label consists of read only text or graphics, it identifies components and communication the status of a process. You can use labels with a component or can use it to describe a group of components.

Text Field
A Text Field is a rectangular box that displays a single line or text. If the line is too long to fit in the text field, The text automatically Scrolls horizontally.

Password Field
A Password Field is a variation of text field. When you type in a password field, instead of characters asterisks (*) are displayed. The asterisks are referred to as a Masking agent.

List Box
A List Box is used to display a set of items. One can use a list to present user with a set of choices.

Command Buttons
The Command Buttons is a component with a rectangular box that displays a single line or text. The text typically consists of a single word that represents the action associated with that button.

22

REPORTS

The system should generate the following reports: Clients details list. Employee details list. Allocated resources list. Project details list. Allocated tasks list.

23

6. SYSTEM ENVIRONMENT
6.1 Microsoft .NET Framework
The .Net frame work is a new computing platform that simplifies application development in the highly distributed environment of the internet. The .NET frame work 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 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 communications 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: o The common language runtime. o 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 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 runtime. Code that targets the runtime is known as managed code, while code that does not target the runtime is known as managed code. The class library, the other main component of the.NET Framework, is a comprehensive, object-oriented
24

collection of reusable types that you can use to develop application ranging from traditional command line or graphical user interface (GUI) applications to applications to latest innovations provide by Windows applications. 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 be 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 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. 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 possible, but with significant improvement 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 application and to the overall system. The illustration also shows how managed code operates within a larger architecture.

Features of the common Language Runtime:

The common language runtime manages memory, thread execution, code execution, code safety verification, compilation, and other system services. These features are intrinsic to the managed code that runs on the common runtime. Language compilers that target the .NET Framework makes the features of the .NET Framework available to existing code written in that language, greatly easing the migration process for existing application. While the runtime is designed for the software of the future, it also supports of today and yesterday. Interoperability between managed and unmanaged code enables developers to use necessary COM components and DLLs.
25

The runtime is designed to enhance the performance. Although the common language runtime provides many standards runtime service, 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-of-reference to further increase performance. Finally the run time can be hosted by high performance, servers side applications such as Microsoft SQL Server 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 industrys best enterprise servers that supports runtime hosting.

.NET Framework class library:

The .NET Framework class library is a collection of usable types that integrate with the common language runtime the class library is object oriented providing types from which your managed codes 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 .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.

26

In addition to these common tasks, the class library type that supports a variety of specialized development scenarios. For example, you can use the .NET Framework to develop the following types if applications and services. 1 2 3 4 5 6 Console applications scripted or hosted applications windows GUI applications(Windows forms) ASP .NET applications XML Web services Windows services. 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.

6.2 Client Application Development:

Client applications are the closest to a traditional style of application in windows based programming. These are the types of applications that display windows or forms on the desktop, enabling a user to perform a task. Client applications include applications such as word processors and spreadsheets, as well as custom business applications such as data-entry tools, reporting tools, and so on. Client applications usually employ windows, menus, buttons, and other GUI elements, and they likely access local resources such as the file system and peripherals such as printers. Another kind of client applications is the traditional ActiveX control (now replaced by the managed Windows Forms control) deployed over the internet as a web page. This application is much like other client applications: it is executed natively, has access to local resources, and includes graphical elements.

27

6.3 ACTIVEX DATA OBJECTS

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 Data Set, Data Reader, and Data Adapter. The important distinction between this evolved stage of ADO .NET and previous data architectures is that there exists an object--the Dataset--that is separated 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 in 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 tired apps more efficient, data processing is truing 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 objects 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 within the Dataset is, it is

28

manipulated through the same set of standards 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 persists the Dataset to and from data stores. The OLEDB and SQL server .NET Data Providers (System.Data.OleDb and System.Data.Sqlclient) that are part of the .NET Framework provider four basic objects: the command, connection, Data Reader and Data Adapter. In the remaining sections of this document, well 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 some objects that have evolved, and some that are new. These objects are: Connections. For connection to and transaction against database. Commands. For issuing SQL commands against a database. Data Readers. For reading a forward-only stream of data records from a SQL server data source. Datasets. For storing, removing and programming against flat data, XML data and relational data. Data Adapters. For publishing 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 provide-specific classes such SQLConnections. Commands travel over connections and result sets are returned in the format of streams which can be read by a Data Reader Objects, or pushed into a Dataset objects.

29

Commands
Commands contain the information that us submitted to a database, and are represented by provider classes such as SQLCommand. A command can be a stored procedure call, an UPDATYE 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 North wide database.

Data Readers
The Data Reader object is somewhat synonymous with a read-only/forward-only cursor over data. The Data Reader API supports flat as well as hierarchical data. A Data Reader object is returned after executing a command against a database. The format of the returned Data Reader object is different from a record set. For example, you might use the Data Reader to show the results of a search list in a web page.

Data Sets and Data Adapters

Data sets The DataSet object is similar to the ADO Record set object, but more powerful, and with one other important distinction: the DataSet is always disconnected. The DataSet object represents a cache of data, with database-like structure such as tables, columns, relationships and constrains. However, through a DataSet can and does behave much like a database, it is important to remember that dataset objects do not interact directly with databases, or other source data. This allows the developer to work with a programming model that is always consistent, regardless of where the source data resides. Data coming from a database, an XML file, from code, or user input can all be placed into Dataset objects. Then, as changes are made to the Dataset they can be tracked and verified before updating the source data. The Get Changes

30

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 DataAdapter 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 WebServices. In fact, a Dataset with a schema can actually be compiled for type safety and statement completion.

Data Adapters
The Data Adapter object works as a bridge between the Dataset and the source data. Using the provider-specific SqlDataAdapter (along with its associated SqlCommand and SqlConnection) can increase overall performance when working with a Microsoft SQL Server databases. For other OLE DB-supported databases, you would use the OleDbDataAdapter object and its associated OleDbCommand and OleDbConnection objects. The Data Adapter objects uses commands to update the data source after changes have been made to the Dataset. Using the fill method of the DataAdapter calls the SELECT command; using the Update method calls the INSERT, UPDATEOR DELETE commands for each changed row. You can explicitly set these commands in order to control the statements used at runtime to resolve changes, including the use of stored procedures. For ad-hoc scenarios, a CommandBuildr object can generate these at run-time based upon a select statement. However this run-time generation requires an extra round trip to the server in the order to gather required metadata. So explicitly providing the INSERTING, UPDATEING, DELETEINTG commands at design time will result in better run-time performance. ADO.NET was created with n-Tier, stateless and XML in the forefront. Two new objects, the dataset and data adapter, are provided for these scenarios.

31

6.4 SQL SERVER

A data base management, or DBMS, gives the user access to their data helps them transform the data into information. Such as management system includes dbase, paradox, and IMS, SQL and SQL server. These systems allow users to create update and extract from their database. A database is a structured collection of data. Data refers to the characteristics of people, things and events; SQL server stores each data in its own fields. In SQL server the fields relating to particular person, thing or event are bundled together to form a single complete unit of data, called a record (it can also be referred to as a row or an occurrence). Each record is made up of a number of fields .no two fields in a record can have the same field. During a SQL server database design project the analysis of your business needs identifies all the fields or attributes of interest .if your business needs change over time, you define any additional fields or change the definition of existing fields. SQL server tables SQL server stores records relating to each other in a table. Different tables are created for the various groups of information. Related tables are grouped together to form a database.

Primary key
Every table in SQL server has a field or a combination of fields that uniquely identifies each record in table. The unique identifier is called the primary key, or simply the key. The primary key provides the means to distinguish one record from all other in a table. It allows the user and the database system to identify, locate and refer to one particular record in the database.

Relational database
Sometimes all the information of interest to business operation can be stored in one table. SQLServer makes it very easy to link the data in multiple tables. Matching an employee to the department in which they work is one example. This is what makes SQL server a relational database management system, or RDBMS. Stores data in two or more tables and enables you to define relationships between the tables and enables you to define relationships between the tables.

32

Foreign Key
When a field is one table matches the primary key of another field is referred to as a foreign key. A foreign key field or a group of fields in one table whose values match those of the primary key of another table.

Referential Integrity
Not only does SQL Server allow you to link multiple tables, it also maintains consistency between them. Ensuring that the data among related tables is correctly matched is referred to as maintaining referential integrity.

Data Abstraction
A major purpose of database system is to provide users with an abstract view of the data. This system hides certain details of how data is stored and maintained. Data abstraction is divided into three levels. Physical level: This is the lowest level of abstraction at which one describes how the data are actually stored. Conceptual Level: At this level of database abstraction all attributed and what data are actually stored is described and relationship among them View Level: This is the highest level of abstraction at which one describes only part of the database.

Advantages of RDBMS
1. Redundancy can be avoided. 2. Inconsistency can be eliminated. 3. Data can be shared. 4. Standards can be enforced .5. Security restrictions can be applied .6. Integrity can be maintained .7. Conflicting requirements can be balanced.
33

Disadvantages of DBMS
A significant disadvantage of the DBMS System is cost. In addition to the cost of purchasing of developing the software, the hardware has to be upgrade to allow for the extensive programs and the workspace required for their execution and storage. While centralization reduces duplication requires that the database be adequately backed up so that in case of failure the data can be recovered.

Features of SQL SERVER (RDBMS)

SQL Server is one of the leading database management system (DBMS) because it is the only Database that that meets the uncompromising requirements of todays most demanding information systems. From complex decision support system (DSS) to the most rigorous online transaction processing (OLTP) application, even application that require simultaneous DSS and OLTP access to the same critical data, SQL Server leads the industry in both performance and capability. SQL SERVER is a truly portable, distributed, and open DBMS that delivers unmatched performance, continuous and support for every database. SQL SERVER RDBMS is high performance fault tolerant DBMS which is specially designed for online transaction processing and for handling large database application. SQL SERVER with transaction processing option offers two features which contribute to very high level of transaction processing throughput, which are The row level lock manager

Enterprise wide Data Sharing

The unrivaled portability and connectivity of the SQL server DBMS enables all the systems in the organization to be linked into a single, integrated computing resource.

34

Portability
SQL SERVER is fully portable to more 80 distinct hardware and operating systems platforms, including UNIX, MSDOS, OS/2, Macintosh and dozens of proprietary platforms. This portability gives complete freedom to choose the database server platforms that meet the system requirements

Open System
SQL SERVER offers a leading implementation of industry-standard SQL. SQL Servers open architecture integrates SQL SERVER and non-SQL SERVER DBMS with industrys most comprehensive collection of tools, application, and third party software products SQL Servers open architecture provides transparent to data from other relational database and even non-relational database.

Distributed Data Sharing

SQL Servers networking and distributed database capabilities to access data stored on remote server with the same ease as if the information was stored on a single local computer. A single SQL statement can access data multiple sites. You can store data where system requirements such as performance, security or availability dictate.

Unmatched performance
The most advanced architecture in the industry allows SQL SEVER DBMS to deliver unmatched performance.

Sophisticated Concurrency Control

Real world applications demand access to critical data. With most database Systems applications becomes connection bound- which performance is limited not by the CPU power or by disk I/O, but user waiting on one another contention free queries to minimize and in many cases entirely eliminates contention waits times.

35

No I/O Bottlenecks
SQL Servers fast commit groups commit and deferred write technologies dramatically reduce disk I/O bottlenecks. While some database write whole data block to disk at commit time, SQL SERVER commits transactions with at most sequential log file on disk at commit time, On high throughput systems, one sequential log file on disk at commit multiple transactions. Data read by the transaction remains as shared memory so that other transactions may access that data without reading it again from disk. Since fast commits write all data necessary to the recovery to the log file, modified blocks are written back to the database independently of the transactions commit, when written from memory to disk.

36

7.CODING
HOME
using System; using System.Data; using System.Configuration; using System.Web; using System.Web.Security; using System.Web.UI; using System.Web.UI.WebControls; using System.Web.UI.WebControls.WebParts; using System.Web.UI.HtmlControls; public partial class _Default : System.Web.UI.Page { protected void Page_Load(object sender, EventArgs e) { } protected void LinkButton1_Click(object sender, EventArgs e) { Response.Redirect("welcome.aspx"); } protected void LinkButton2_Click(object sender, EventArgs e) { Response.Redirect("bdo.aspx"); } protected void LinkButton5_Click(object sender, EventArgs e) { Response.Redirect("developer.aspx"); } protected void LinkButton4_Click(object sender, EventArgs e) { Response.Redirect("pmlogin.aspx"); } protected void LinkButton3_Click(object sender, EventArgs e) { Response.Redirect("hrlogin.aspx"); } }

37

ADD CLIENT
using System; using System.Data; using System.Configuration; using System.Collections; using System.Web; using System.Web.Security; using System.Web.UI; using System.Web.UI.WebControls; using System.Web.UI.WebControls.WebParts; using System.Web.UI.HtmlControls; using System.Data.SqlClient;

public partial class Default6 : System.Web.UI.Page { protected void Page_Load(object sender, EventArgs e) { } protected void Button1_Click(object sender, EventArgs e) { SqlConnection con = new SqlConnection("Data Source=.;Initial Catalog=spm;Integrated Security=True"); SqlDataAdapter da; da = new SqlDataAdapter("select * from clientdetails", con); DataSet ds = new DataSet(); SqlCommandBuilder cb = new SqlCommandBuilder(da); da.Fill(ds, "clientdetails"); DataRow dr; dr = ds.Tables["clientdetails"].NewRow(); dr["clientid"] = TextBox1.Text; dr["cname"] = TextBox2.Text; dr["officeadress"] = TextBox3.Text; dr["homeadresss"] = TextBox4.Text; dr["phonenum"] = TextBox5.Text; dr["email"] = TextBox6.Text; dr["scale"] = TextBox7.Text; dr["industry"] = TextBox8.Text; dr["aggrement"] = TextBox9.Text; dr["validity"] = TextBox10.Text; dr["panality"] = TextBox11.Text; dr["name"] = TextBox12.Text; dr["phonen"] = TextBox13.Text; ds.Tables["clientdetails"].Rows.Add(dr);
38

da.Update(ds, "clientdetails"); TextBox1.Text = ""; TextBox2.Text = ""; TextBox3.Text = ""; TextBox4.Text = ""; TextBox5.Text = ""; TextBox6.Text = ""; TextBox7.Text = ""; TextBox8.Text = ""; TextBox9.Text = ""; TextBox10.Text = ""; TextBox11.Text = ""; TextBox12.Text = ""; TextBox13.Text = ""; Response.Write("<script>alert('successfully added')</script>"); } protected void Button2_Click(object sender, EventArgs e) { Response.Redirect("bdosheet.aspx"); } protected void Button3_Click(object sender, EventArgs e) { Response.Redirect("home.aspx"); } protected void TextBox10_TextChanged(object sender, EventArgs e) { } }

39

ADD PROJECT
using System; using System.Data; using System.Configuration; using System.Collections; using System.Web; using System.Web.Security; using System.Web.UI; using System.Web.UI.WebControls; using System.Web.UI.WebControls.WebParts; using System.Web.UI.HtmlControls; using System.Data.SqlClient; public partial class Default9 : System.Web.UI.Page { SqlConnection con = new SqlConnection("Data Source=.;Initial Catalog=spm;Integrated Security=True"); SqlDataAdapter da; SqlDataAdapter da1; DataSet ds = new DataSet(); protected void Page_Load(object sender, EventArgs e) { } protected void Button2_Click(object sender, EventArgs e) { Response.Redirect("bdosheet.aspx"); } protected void Button1_Click(object sender, EventArgs e) { da = new SqlDataAdapter("select * from projectdetails", con); SqlCommandBuilder cb = new SqlCommandBuilder(da); da.Fill(ds, "projectdetails"); DataRow dr; dr = ds.Tables["projectdetails"].NewRow(); dr["projectid"] = TextBox1.Text; dr["projecttitle"] = TextBox2.Text; dr["clientid"] = TextBox3.Text; dr["startdate"] = TextBox4.Text; dr["enddate"] = TextBox5.Text; dr["cost"] = TextBox6.Text; dr["existingsystems"] = TextBox7.Text; dr["noofpersons"] = TextBox8.Text; dr["proposedsystens"] = TextBox9.Text; dr["abstract"] = TextBox10.Text;
40

dr["typeofapplication"] = TextBox11.Text; dr["typeofos"] = TextBox12.Text; dr["projectmamager"] = TextBox13.Text; dr["platform"] = TextBox14.Text; dr["projectbulidinglocation"] = TextBox15.Text; dr["noofmodules"] = TextBox16.Text; ds.Tables["projectdetails"].Rows.Add(dr); da.Update(ds, "projectdetails"); da1 = new SqlDataAdapter("select * from clientdetails", con); SqlCommandBuilder cb1 = new SqlCommandBuilder(da1); da1.Fill(ds, "clientdetails"); DataRow dr1; dr1 = ds.Tables["clientdetails"].NewRow(); dr1["projectid"] = TextBox1.Text; dr1["projecttitle"] = TextBox2.Text; dr1["clientid"] = TextBox3.Text; dr1["timeleft"] = TextBox17.Text; dr1["status"] = TextBox18.Text; dr1["workdone"] = TextBox19.Text; ds.Tables["clientdetails"].Rows.Add(dr1); da1.Update(ds, "clientdetails"); TextBox1.Text = ""; TextBox2.Text = ""; TextBox3.Text = ""; TextBox4.Text = ""; TextBox5.Text = ""; TextBox6.Text = ""; TextBox7.Text = ""; TextBox8.Text = ""; TextBox9.Text = ""; TextBox10.Text = ""; TextBox11.Text = ""; TextBox12.Text = ""; TextBox13.Text = ""; TextBox14.Text = ""; TextBox15.Text = ""; TextBox16.Text = ""; TextBox17.Text = ""; TextBox18.Text = ""; TextBox19.Text = ""; Response.Write("<script>alert('successfully added')</script>"); } }
41

8.SYSTEM TESTING
Testing is the process of confirming that a program or system does what it is proposed off, Testing is the only way to assure the quality of s/w and it is an umbrella activity rather that a separate phase. This is an activity to be performed in parallel with the s/w efforts and one that consists of its own phase of analysis, design, implementation, execution and maintenance.

8.1 Testing Strategy:

Unit Testing: This testing method considers a module as single unit and checks the unit at interfaces and communities with other modules rather than getting into details at statement level. Here the module will be treated as BLACKBOX, which will take some inputs and generate output. Outputs for a given set of input combination are pre calculated and are generated by the module. Integration Testing: Here all the pre-tested individual modules will be assembled to create a larger system and tests are carried out at system level to make sure that all modules are working in synchronous with each other. This testing methodology helps in making sure that all modules which are running perfectly when checked individually and are also running cohesion with other modules. For this testing we create test-cases to check all modules once and then a generated test combination of test paths throughout the system to make sure that no path is making its way into chaos. Validation Testing: Testing is major quality control measure employed during software development. Its basic function is to detect errors. Sub functions when combined may not produce than it is desired. Global data structures can represent the problems. Integrated testing is a systematic technique for constructing the program structure while conducting the tests. To uncover errors that are associated with interfacing the objective is to make test modules and built a program structure that has detected by design. In a non-incremental integration all the modules are combined in advance and the program is tested as a whole. Here error will appear
42

in an end-less loop function.. In incremental testing the program is constructed andtested in small segments where the errors are isolated and corrected. Different incremental integration strategies are 3 4 5 Top-Down integration Bottom-Up integration Regression integration Testing means quality test. Testing is a process of executing a program with the intent of finding error. A good test case is one that has a high probability of finding an as yet un discovered error. Objective should be to design test that systematically uncover different classes of error and to do with a minimum amount of time and effort. Testing cannot show the absence of defects, it can only show that s\w defects are present. It is important to keep this statement in a mind as testing is being conducted. Any engineering product can be tested in one of the two ways. Knowing the specific function that a product has been designed to perform, test can be conducted that demonstrates each function is fully operational. This approach is called BLACK BOX TEXTING Knowing the internal working of the product, test can be conducted to ensure that all gears mesh, that is, that internal operation of the product performs according to specification and all internal components have been adequately exercised. This approach is called WHITE BOX TESTING. These approaches provide a mechanism that can help to ensure the completeness of tests and provide the highest likelihood for uncovering errors in s/w. The goals of verification and validation are to access and improve the quality of work products generated during development and modification of s/w. These are 2 types of verification namely.

43

1. Life-cycle verification 2. Formal verification. Validation is the process of evaluating s/w at the end of s/w development process. Quality assurance is a planned and systematic pattern of action necessary to provide adequate confirms to the technical requirement.

Walkthroughs are sessions where the material being examined is examined is presented by a review and evaluated by a team of reviewers.

Inspection involves assessing the s/w life cycle and improving the quality of work products. Life-cycle verification is the process of determining the degree to which the work products of a given phase of the development cycle fulfill the specification established during prior phases. Formal verification is a rigorous mathematical demonstration that source code confirms to its specification.

High quality can be achieved through testing of source code alone. Although a program should be totally free of errors, this seldom the case for large s/w products. There are 3 major categories of s/w error. 1. 2. 3. Requirement errors Design errors Implementation errors Quality assurance defines the objective of the project and reviews the overall activities so that the errors are corrected early in the development process.

44

During analysis and design, an s/w verification plan and acceptance test plan is prepared. The verification plan describes the methods to be used in verifying that the requirements are satisfied by the design documents and that the source is consistent with the requirements specification and design documents. The acceptance test plan includes test cases, outcomes and capabilities demonstrated by each test case. Following completion of the verification plan and acceptance plan, an s/w verification review is held to evaluate the adequacy of the plans. During product evolution, in-process audits are conducted to verify consistency and completeness of the work products. Items to be audited for consistency include interface specification for hardware and software and people: internal design verses functional requirements verses test descriptions.

Prior to product delivery, a functional audit and a physical audit performed. The functional audit reconfirms that all the requirements have been met. The physical audit verifies that the source code and all associated documents are complete, consistent with one another and ready to deliver. An s/w verification summary is prepared to describe the results of all reviews.

8.2 SYSTEM TESTING:

A system is tested for online responses, volume of transactions, stress, recovery from failure and usability. System testing involves two kinds of activities-integration testing and acceptance testing.

8.3 ACCEPTANCE TESTING:

It involves planning and execution of functional tests and stress tests in order to demonstrate that the implemented system satisfies its requirements.

Tools to special importance during acceptance testing include: 4. Testing COVERAGE ANALYZER-RECORDS THE CONTROL PATHS FOLLOWED FOR EACH TEST USER.
45

5.

TRIMING ANALYZER-also calls a profiler, reports the time spent in various regions of the code are areas to concentrate on to improve system performance.

6.

Coding standards-static analyzer and standard checkers are used to insert code for deviations from standard and guidelines.

8.4 ALPHA and BETA TESTING:

If s/w is developed as product to be used by many customers, it is impractical to perform formal acceptance test with each one. So, one most developers use Alpha and Beta testing to uncover that only the end user seems able to find.

Alpha testing is conducted by the customer in the presence of many project leaders and recorded the errors and usage problems what they faced.

Beta testing is conducted at customer site by the end users of the s/w, the customer recorded that encountered during beta testing and sent those problems to us regular intervals. Then we made the modification and released to the entire customer base.

46

8.SCREENS HOME PAGE

47

WELCOME CLIENT :

48

VIEW CLIENT DETAILS:

49

BDO HOME:

50

ADD PROJECT DETAILS:

51

DEVELOPER HOME PAGE:

52

VIEW TIME SHEET:

53

PM HOME PAGE:

54

PM PROJECT DETAILS:

55

HR LOGIN SCREEN:

56

ADD EMPLOYEE DETAILS:

57

10. CONCLUSION
All the objectives that had been charted out in the initial phases were achieved successfully.

System Features: System satisfies all the requirements for which the company developed the system. System has strong security. System is fully GUI based. It is easy operate and user friendly. Platform includes the inbuilt backup and recovery facility. Working on the project was a good experience. Working together in teams helped us to communicate better. We understand the importance of planning and designing as a part of software development. The concept of peer-reviews helped to rectify the problems as and when they occurred and also helped us to get some valuable suggestions that were incorporated by us. Developing the project has helped us to gain some experienced on real time development procedures.

Suggestion for further development: System required sufficient RAM and faster server to run the application properly.

58

11. BIBLIOGRAPHY
C# .NET : C# .NET Unleashed

SQL Server 2000

: SQL Unleashed

ASP.Net

: ASP.Net Unleashed

http://www.msdn.Microsoft.com/webservices http://www.information-management-architect.com

59