Online Construction Company

 CHAPTER 1

REQUIREMENTS STUDY AND ANALYSIS

Introduction

The process of system analysis is largely concerned with determining developing and agreeing user’s requirements. The system analyst should use this opportunity to communicate well with users and conceive an understanding of what a system should be doing together with a view of relative importance of the system. It involves studying the ways an organization currently retrieves and process data to produce information with intention of finding out how make things better. System analysis includes investigation and suggesting possible change to the existing system.

System analysis produces a description of the existing system and set of requirements for the new system. Analysis is followed by design, which proposes a new system to meet requirements.

1.1 Feasibility study

During the study phase we have gathered all relevant data and a preliminary analysis is carried out in sufficient depth to permit a technical and economic evaluation of the proposed system. Feasibility is a test of system proposed according to workability, impact on the organization ability to meet user needs, and effective use of resources. Following are the feasibility study employed

1.1.1 Operational feasibility

The employees who are responsible for data entry and processing are computer-trained personals, so there is no need for special training, if not then one week training can be required for him to operate the system. And for the users, it is easy to log on to the system using his id and password. Thus the system is operationally feasible.

 1.1.2 Technical feasibility

This software users use VB.net technology, which is platform independent. This system is technically feasible. The proposed system is a windows application; it must satisfy the specified hardware and software configuration. The existing personal computers can accommodate the proposed system without changing the hardware and software.

1.1.3 Economic feasibility

Economic analysis is the most frequently used method for evaluating the effectiveness of a candidate system. More commonly known as cost/benefit analysis, the procedure is to determine the benefit of the candidate system and compare them automating the process of report generation. A system that can be developed technically and that will be used if installed is a good investment for the organization. The only cost required is for installing. NET technology. It is benefited individually. Hence this package is economically feasible.

1.2 User Interview

Interviewing some of the employees in the construction company, they said the problems facing with the existing. The main problem they are facing is the time consumed in the existing system. We also interviewed managers and administrator in different company and they also said their problem they are facing with the existing system. As we understood these all are the drawbacks so we proposed a new system ‘ONLINE CONSTRUCTION COMPANY’ which we believe that it will wipe out all these problems.

1.3 Project Plan

Sl. No	Activity  description	Role	Start date	Target date
1	User Interview	All members	22.02.2011	02.03.2011
2	Documentation	All members	09.03.2011	18.03.2011
3	Preparation And Review	All members	20.03.2011	25.03.2011
4	SRS Approval	Internal Guide		01.04.2011
5	SRS Enhancement	All members	15.04.2011	17.04.2011
6	Feasibility Study	All members	19.04.2011	23.04.2011
7	Identification Of Entities	All members	25.04.2011	30.04.2011
8	Identification Of Attributes	All members	31.04.2011	03.05.2011
9	Security Analysis	All members	05.05.2011	07.05.2011
10	Normalization	All members	09.05.2011	24.05.2011
11	Table Definition	All members	25.05.2011	27.05.2011

Table 1.1 Preparing of project

1.4 Existing System

In the existing system, all construction process is done by manually. There is no online construction company. So it causes lot of time to complete all process.

1.5 Problems in Existing System                                    

The existing system has many drawbacks that can be rectified, when the system is made user friendly. The drawbacks of the existing system are:

Ø  Lack of security: Authorized or unauthorized users can corrupt the data stored in the registers.

Ø  Cost increasing.

Ø  Lack of integrity.

Ø  Poor reliability:  Since the data is handled manually, it is prone into data entry errors and manipulation errors making the data less reliable.

Ø  Low speed:  The processing speed is very low.

Ø  Redundancy:  There is a great chance of duplication of data.

Ø  Accuracy:  Less accuracy or chance of mistake is very high.

1.6 New Requirements

By developing the system we can attain the following facilities.

·      A user friendly interface is needed for

Þ                Improving the existing system in the company.

Þ                Minimizing the paper work and manual errors.

Þ                Improving time efficiency.

Þ                Improving administrator- manger interaction.

Þ                Improving manager-employee interaction.

·      Fast access to the database

·      Easy updating of employees details

·      It reduces time consuming

·      Reduction in work load

·      Time and effort is considerably reduced 

1.7 Proposed System

Study of existing system and identification of its drawbacks lead to designing of the proposed system. It will be compatible with the existing one. It is implemented in VB.NET and ASP.NET.

The proposed system is fully a menu driven one. This makes the system very user friendly and easy to use. In the proposed System Security is provided through hierarchical division of authorities. The entire system is monitored by the administrator. Only the administrator has the power to register new work. The manager can view the assigned work from the admin and assign those works to the employees working under them. They also assign salary to employee and update the grade of employee on the basis of their work status. The employee can login into the site and search or assigned work and also he/she can update the status of their work. Admin can view the status of the work and can assign salary to the manager.

Advantages of the proposed system:

Ø    The proposed system is much faster than existing one and human errors can be avoided.

Ø    User friendly since all facilities are provided through Graphical User Interface.

Ø    It provides high accuracy, security and greater efficiency.

Ø    Decision-making is easier.

Ø    Storing of data is in consistent manner.

Ø    Less time consumption.

Ø    Duplication of records is avoided.

Ø    Deletion and updating of documents are easy.

Ø    The co-ordination among workers can be done more easily.

Ø    The user can interact efficiently with the new system

1.8 Software and Hardware Requirements

HARDWARE:

Processor                                 Pentium 4

RAM                                       256 MB

Hard Disk                               40 GB

Peripheral                                CD ROM

Monitor                                   SVGA Display

Mouse:                                    Microsoft series or compatible

Keyboard                                101 keys or above

SOFTWARE:

Operating System:                  WINDOWS XP

Front End:                               VB.NET

Backend:                                 Microsoft SQL Server 2005

1.9 General Description

In this software it helps the admin to assign the work to the manager through web and also the manger can assign the work to the employee also through the web. It also helps to maintain the documentation about the work, employee etc... Which is regarding to the company.

1.10 Specific Requirement

The new system is an automated system which helps to communicate between administrator and the manager, and also between manager and the employee also keep complete records of the company. The new system requires some features such as:

·            Automated system

·            User friendly

·            Communicate between administrator and manager

·            Communicate between manager and employee

·            Keep the records regarding to the company

1.11 Identification of Entity and Attributes

Administrator	User Name
	Password
Manager	User Name
	Password
	Manager’s ID
	Manager’s Name
	Manager’s Address
	Manager’s Mobile Number
	Manager’s  Phone Number
	Manager’s Place
	Manager’s Country
	Manager’s  Email Address
	Faculty’s Pin Code
Student	User Name
	Password
	Employee’s ID
	Employee’s Name
	Employee’s Address
	Employee’s Mobile Number
	Employee’s  Phone Number
	Employee’s Place
	Employee’s Country
	Employee’s Email Address

                              Table 1.2  Identification of Entity and attribute

1.12 Context Analysis Diagram

The Context Analysis Diagram (CAD) may be used to represent the top level overviews of the existing system.  The CAD is drawn to represent the state of the system during the requirement analysis phase.

The CAD shows the system as a single process represented by a circle at the center of the model.  There shall always be only one system process in a CAD.  The model shows entities external to the system process.  The entities are representative of the existing significant objects in the current system scenario.  The external entities are connected to the central process through connectors representing the information flowing into/ out of the system.  CAD should be drawn with the help of latest version of the Turbo Analyst tool available with the company.

                                                Fig 1.1 Context analysis diagram

1.13 Data Flow Diagram

A DFD, also known as Bubble Chart, has the purpose of clarifying system requirements and identifies major transformation that will become programs in system design. So it is the starting point of design phase that functionally decomposes the elements specification down to the lowest level of details. A DFD consists of a series of bubbles joined by lines. The bubble represents data transformation and line represents data flow in the system.

Data Flow Diagrams represent one of the most ingenious tools used for structured analysis. A Data Flow Diagram or DFD as it is shortly called is also known as a bubble chart. It has the purpose of clarifying system requirement and identifying major transformation that will become programs in system design. It is the major starting point in the design phase that functionally decomposes the requirement specification down to the lowest level of details. A DFD consists of a series of bubble joined by lines. The bubble represents data transformation and lines represent data flow in the system.

In DFD, there are four main symbols: -

 

                                                 - Source or Destination of data

     

                            -                  - Flow of Data

                                                -   Process transforming data

                                                 -   Temporary repository of data

                                                                                                                              

Level 0

                                                                 Fig 1.2 Data Flow Diagram of level 0  

LEVEL 1

ADMIN:

               

                                                                Fig 1.3 Data Flow Diagram of Administrator module

LEVEL 2

MANAGER:

                                                                Fig 1.4 Data Flow Diagram of Manager module

LEVEL 3

EMPLOYEE:

                               

                                                                Fig 1.5 Data Flow Diagram of Employee module

1.14 Entity Relationship Diagram

The Entity Relationship Diagram (also known as an ERD or E-R diagram) is a network model that describes the stored data layout of a system at a high level of abstraction. The ERD should represent the relationships between all the entities. Any two entities must be connected to each other by some relationship set and type of relationship should also be specified.

Fig 1.6 Entity-Relation-Diagrams

Conclusion

The subsection of the chapter provides an overview of proposed system design and its other

functional requirements clearly and precisely.

CHAPTER 2

System Design and Development

Introduction

System design is a creative act of invention and developing new inputs, database off-line files, procedures and outputs for processing business data to meet organization objectives, system designs build information gathered during the system analysis. In the design phase, the detailed design of the system selected in the study phase is accomplished.

The characteristics associated with a well-designed system include:-

·         Acceptability

·         Decision-making ability

·         Economy

·         Flexibility

·         Reliability

·         Simplicity

An information processing system must be functional in design, it must supply information quickly, eliminate duplication of effort and tasks and must make effective use of people, technology and procedures.

2.1 Scope

System design involves logical design first and then physical construction of the system while formulating a logical design, we write detailed specification the system, describe its features, the output files and databases, all in a manner that meet project requirements.

The logical design of an information system shows the major features and also how are they related to one another.

Physical design involves developing programs, files, and a working system. Design specification instructs the programmers about what the system should do. The physical design consists of the developing the screen for the input and the program steps written in the programming language.

2.2 Purpose

2.2.1 Time:

The major constraint is the time. The system has been developed in a fixed time constraint, so only the major activities could be included in the system.

2.2.2 Security:

A serious problem we have to face is to provide proper security to the system. By setting password we can avoid the unauthorized access to the system. Only a person who knows the correct username and password can enter into the system. If both are wrong the error message “INVALID ID OR PASSWORD” will be displayed. Every sections of work of the software are provided with proper individual passwords to avoid the fraudulent malpractices. The administrator has only the power to register new employers as members and provide employee Id as username and password.

2.2.3 End User Characteristics

Most of the end users of the system are unaware about computer though they have high qualifications. This software in VB.net and ASP is built in an easier and friendly manner so that end-user may not be desperate. Users range from naïve to highly sophisticated. The naïve users should learn how to operate the system but needn’t know about the principles and facts behind each function. The formal users know the principles and follow the functions as well.

If complications arrive, these people may not be able to handle it. So we provide user manuals along with the report for their doubt clarifications. Though it may be a tedious task at first sight, the user can easily cope with it for the easy utilization of the Network implementation. Keeping the above characteristics of the end user, the system has been developed in order to meet the requirement of all persons involved in the system.

2.3 Database Design

Database design runs in parallel with the application design. As we collect information about what is to be done, we will obviously collect information about what data needs to be entered, stored, message and printed on reports. One of the main tasks in building a new system is determining the contents and structure of the database. The type of retrieval and recording required by the user and availability of inputs determine what data has to be stored. The database is a collection of related data.

A comprehensive database should contain all the information necessary to manage the enterprise. Database can be implemented directly using file management program or a database management system. The objectives in establishing a database can be summarized as:

Ø  Eliminate redundant data as much as possible.

Ø  Integrate data files.

Ø  Incorporate changes easily and quickly.

Ø  Lower the cost of storing and retrieving data.

Ø  Improve accuracy, integrity and consistency.

Ø  Data independence.

Ø  Privacy and security.

The various steps involved in database design are given below:

*    Organizing the data

As we gather the data, we will organize it into tables and begin to work out its connections. Our first goal is to identify the tables and the columns within the tables.

*   Identify the keys

The next step in database design is to identify the key that is used as a primary key. A primary key is a column, which uniquely identifies a row in a table.

Uniqueness is the key property of a primary key, so we have to choose it carefully. Then identify the foreign keys that are used. A foreign key is a key that is a column in a table, which acts as a primary key for another table. So after identifying the primary keys and the foreign keys, go to the next step of database design.

NORMALISATION

Data structuring is refined through the process called normalization. The basic objective of normalization is to reduce the data redundancy, which means that information is stored only once. There are several normal forms, they are

FIRST NORMAL FORM

A relation is said to be   in first normal form if and only if all the attribute values are atomic.

In the First normal form;

v  All the key attributes are defined.

v  There are no repeating groups in the table. In  other words, each  row/column  intersection  can contain one and only  one  not  a set of values

v  All the attributes are dependent on the primary key.

SECOND NORMAL FORM

To be in second normal form a table must be in first normal form and no attribute of the table should be functionally dependent on any part of the primary key

 A table is in second normal form if:

v  It is in 1 NF

v  It include no PARTIAL DEPENENCIES; that is no attribute is dependent on a portion of the primary key

THIRD NORMAL FORM

v  To be in third normal form a table must be in second normal form and no attribute of the table should be transitively functionally dependent on the primary key.

v  It is in 2NF

v  It contains no transitive dependencies.

BOYCE – CODE NORMAL FORM

To be in BCNF a table must only have candidate keys as determinants.  It is a stronger definition of third normal form.  If a table contains only one candidate key, 3NF and BCNF are equivalent.

FOURTH NORMAL FORM

The rule for fourth normal form is a table is in BCNF and it does not contain any multi-valued dependencies.

2.4 Tables

In this system there are seven tables used in the data base. Here is a brief description about them.

·        Login Table

Column Name	Description	Data Type	Width	Constraints	Screen label name
EmpId	ID of the employees in the company	Numeric	18	Primary Key	User ID
Password	Password of the Employee	nvarchar	50		Password

Table 2.1

·        Employee Registration Table

Column Name	Description	Data Type	Width	Constraints	Screen label name
EmpId	ID of the Employee in the company	numeric	18	Primary Key	Emp ID
EmpName	Name of the Employee	nvarchar	50		Emp Name
Address	Address of the Employee	nvarchar	50		Address
Designation	Designation of the Employee	nvarchar	50		Designation
MobNo	Mobile no of the Employee	bigint			Mobile No
PhoneNo	Phone no of the Employee	bigint			Phone No
Place	Place of the Employee	nvarchar	50		Place
Country	Country of the Employee	nvarchar	50		Country
Email	Place of the Employee	nvarchar	50		Email

Table 2.2

·        Assign Emp to Manager Table

Column Name	Description	Data Type	Width	Constraints	Screen label name
EmpId	ID of the Employee in the company	numeric	18	Primary Key	Emp ID
MangId	Assign Employee to the Manger	numeric	18		Manger

                                                                        Table 2.3

·        Salary Details Table

Column Name	Description	Data Type	Width	Constraints	Screen label name
EmpId	ID of the Employee in the company	numeric	18	Primary Key	Emp ID
date	Date of the salary is updated	nvarchar	50		Date
BasicSalary	Basic salary of the Employee	float			Basic Salary
Incentive	Incentive to the Employee	float			Incentive
TotalSalary	Total Salary of the Employee	Float			Total Salary

                                                                        Table 2.4

·        Work Assign Table

Column Name	Description	Data Type	Width	Constraints	Screen label name
WorkId	ID of the Employee in the company	numeric	18	Primary Key	Work ID
EmpId	ID of the Employee in the company	numeric	18		Emp ID
date	Date of the salary is updated	nvarchar	50		Date
Work	Type of Work	nvarchar	50		Work
Status	Status of Work	nvarchar	50		Status
Type	Type of Working	nvarchar	50		Type
Designation	Designation of the Emp	nvarchar	50		Designation

                                                Table 2.5

·        Work Registration Table

Column Name	Description	Data Type	Width	Constraints	Screen label name
WorkId	ID of the Employee in the company	numeric	18	Primary Key	Work ID
Work	Type of Work	nvarchar	50		Work
Date	Date of the salary is updated	nvarchar	50		Date
Amount	Amount of Work	float			Amount
Status	Status of Work	nvarchar	50		Status

                                                                        Table 2.6

·        Employee Grade Table

Column Name	Description	Data Type	Width	Constraints	Screen label name
EmpId	ID of the Employee in the company	numeric	18	Primary Key	Emp ID
Grade	Grade of the Employee	nvarchar	50		Grade

                                                                        Table 2.7

·        Work Status Table

Column Name	Description	Data Type	Width	Constraints	Screen label name
WorkId	ID of the Employee in the company	numeric	18	Primary Key	Work ID
EmpId	ID of the Employee in the company	numeric	18		Emp ID
Status	Status of Work	nvarchar	50		Status
date	Date of the salary is updated	nvarchar	50		Date
Type	Type of Work	nvarchar	50		Type

                                                                        Table 2.8

2.5 Process Design

2.5.1 Manager Registration

The Manager has to be registered by the administrator to avail the facility of the software Online Construction Company. He will be provided with an user id and password. With the user id and password he can able to access the services provided by the software.

Manager Registration

Manager/Emp details

Manager details

Fig 2.1process design diagram for manager registration

         

       

2.5.2 Employee Registration

The Employee has to be registered by the administrator to avail the facility of the software Online Construction Company. He will be provided with a user id and password. With the user id and password he can access the services provided by the software.

Employee Registration

Manager/Emp details

Emp details

Fig 2.2 process design diagram for employee registrations

2.5.3 Work Registration

The Work has to be registered by the administrator to avail the facility of the software Online Construction Company. The Work will be provided with a work id. With the work id the administrator can assign work to managers.

                                                                                                  

Work Registration

Work details

Work details

Fig 2.3 process design diagram for work registrations

2.5.4 Update Work Status  

The manager updates status to the administrator and also the employee updates the status to the manager by using the facility provided by the software. The administrator and the manger can view the status by using this software.

Update Work   Status

Status details

Work Status details

Fig 2.4 process design diagram for work status details

2.6 Input and Output Design

2.6.1 Inputs Design

The goal of input design is to capture data and get that data into a format suitable for the computer. When we computerize a system, the user-oriented program is to be converted into a programmer-oriented specification for the computer-based system. All systems need some input data for processing. In order to achieve the objectives of the system, input should be given accurately at the right time. Any ambiguity concerning the inputs will lead to total faults in the functioning of the System.

The most common source of inaccurate data processing errors is the inaccurate input data. The errors made by users can be controlled by input design. The aim of input design is to make operation as easy and error free as possible.

There are many major inputs to our project. They are User Ids, User Names and Passwords, mode of File transfers, Choosing Multimedia files etc….

2.6.2 Output Design

Computer outputs, the most visible component of working system, are the justification for the system. As the major idea of output is to convey information, its layout and design need careful consideration. Efficient and intelligible outputs improve the systems’ relationship with the user and help in better decision-making. Computer outputs should be simple to read and interpret. It must be acceptable to the end-users who will receive them.

Conclusion

Various subsections of the chapter provide an overview of design of the software.

CHAPTER 3

CODING

Introduction

The design must be translated into a machine- readable form. The coding steps perform this task. If design is performed in detailed manner, coding can be accomplished mechanistically.

3.1 Coding Technology

.NET

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.

To provide a consistent object-oriented programming environment whether object code is stored and executed locally, executed locally but Internet-distributed, or executed remotely, code-execution environment that minimizes software deployment and versioning conflicts, that minimizes software deployment and versioning conflicts, that guarantees safe execution of code, including code created by an unknown or semi-trusted third party, that eliminates the performance problems of scripted or interpreted environments. The developer experience consistent across widely varying types of applications, and Web-based applications, 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 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 the runtime. Code that targets the runtime is known as managed code, while code that does not target 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.

VB .NET

VB. NET is the next generation of the VB language from Microsoft. With VB you can build .NET applications quickly and easily. Applications made with VB are built on the services of the common language runtime and take advantage of the .NET Framework.

VB has many new and improved features such as inheritance, interfaces, and overloading that make it a powerful object-oriented programming language. Other new language features include free threading and structured exception handling. VB fully integrates the .NET Framework and the common language runtime, which together provide language interoperability, garbage collection, enhanced security, and improved versioning support. VB supports single inheritance and create Microsoft intermediate language (MSIL) as input to native code compilers.

VB is comparatively easy to learn and use, and has become the programming language of choice for hundreds of thousands of developers over the past decade. An understanding of  VB can be leveraged in a variety of ways, such as writing macros in Visual Studio and providing programmability in applications such as Microsoft Excel, Access and Word.

VB. NET, the next generation of the VB language, is a fast and easy way to create .NET-based applications. VB .NET has many new and improved features that make it a powerful object-oriented programming language, including inheritance, interfaces, and overloading. Other new language features include free threading and structured exception handling. VB .NET also fully integrates the .NET Framework and the Common Language Runtime, which provide language interoperability, garbage collection, enhanced security, and improved versioning support.

ASP .NET

ASP.NET 1.1, the latest version of Active Server Pages, is Microsoft’s technology for building dynamic, database-driven Web sites.ASP.NET is one of the most popular languages for building scalable, interactive Web sites. Several of the highest traffic Web sites on the Internet employs ASP.NET. Prominent examples include the Home Shopping Network, MSN, and the Microsoft site itself.ASP.NET represents a radical departure from previous versions of Active Server Pages. If you have programmed with earlier versions of Active Server Pages and you have not been exposed to the new features of ASP.NET, prepared to be shock Following are some of the significant features of ASP.NET:

ASP.NET uses compiled code written in Common Language Run time languages such as Visual Basic and C#. Unlike previous versions of Active Server Pages, this version does not use interpreted scripting languages such as VBScript.

ASP.NET pages are built out of server-side controls. Web server control enables you to represent and program against Hypertext Markup Language (HTML) elements using an intuitive object model.

ASP.NET includes a new technology called Web Services. You can use Web Services to access methods and properties and transfer database data across the Internet.ASP.NET is part of Microsoft’s .NET Framework. You can access thousands of .NET classes in your code that enable you to perform such wondrously diverse tasks as generating images on-the-fly and saving an array to a file.

ASP.NET includes page and data caching mechanisms that enable you to easily and dynamically improve the performance of your Web site.

DATABASE SERVERS

A database server is used to store data in a database. Users can access the data and manipulate it. A web application can provide the user with the interface to the database. There are many types of databases. The most popular among them is the Relational Database Management System (RDBMS).

RDBMS:

RDBMS is a type of database management system that stores data in the form of related tables. Relational databases are powerful because they require few assumptions about how data is related or how it will be extracted from the database. As a result, the same database can be viewed in many different ways. An important feature of relational systems is that a single database can be spread across several tables. This differs from flat-file databases, in which each database is self-contained in a single table.

SQL:

The structured Query Language (SQL) comprises one of the fundamental building blocks of modern database architecture. SQL is an ANSI (American National Standards Institute) standards computer language for accessing and manipulating database systems. SQL statements are used to retrieve and update data in a database. SQL works with database programs like MS Access, Oracle, DB2, Informix, MS SQL Server and Sybase etc.

A database most often contains one or more tables. Each tables is identified by a name (E.g. “Customer” or “Orders”). A table contains record (rows) with data. With SQL we can query a database and have a result set returned. SQL is the syntax for executing queries. But the SQL language also includes the syntax to insert and delete records. These query and update commands together form the Data Manipulation Language (DML) part of SQL. The Data Definition Language (DDL) part of SQL permits database tables to be created or detected. We can also define indexes (keys), specify links between tables and imposes constraints between databases.

3.2 Codes

/*coding of the class where the execution is performed*/

/*Operator Class */

using System;

using System.Data;

using System.Configuration;

using System.Linq;

using System.Web;

using System.Web.Security;

using System.Web.UI;

using System.Web.UI.HtmlControls;

using System.Web.UI.WebControls;

using System.Web.UI.WebControls.WebParts;

using System.Xml.Linq;

using System.Data.SqlClient;

public class dboperator

{

      public dboperator()

      {

      }

SqlConnection con = new SqlConnection(@"Data Source=.\SQLEXPRESS;AttachDbFilename=D:\kmct_cnstr\kmct_cnstr\data\company.mdf;Integrated Security=True;Connect Timeout=30;User Instance=True");

public DataSet ret(SqlCommand cmd)

    {

        cmd.Connection = con;

        cmd.CommandType = CommandType.StoredProcedure;

        SqlDataAdapter ad = new SqlDataAdapter();

        ad.SelectCommand = cmd;

        DataSet ds = new DataSet();

        ad.Fill(ds);

        return ds;

    }

    public void nonret(SqlCommand cmd)

    {

        cmd.Connection = con;

        cmd.CommandType = CommandType.StoredProcedure;

        con.Open();

        cmd.ExecuteNonQuery();

        con.Close();

    }

    public int max(SqlCommand cmd)

    {

        int id;

        try

        {

            con.Open();

            cmd.Connection = con;

            cmd.CommandType = CommandType.StoredProcedure;

            id = Convert.ToInt32(cmd.ExecuteScalar()) + 1;

        }

        catch

        {

            id = 1;

        }

        finally

        {

            con.Close();

        }

        return id;

   

    }

}

/*Coding of Emp/Manager Registration*/

/*Container Class*/

using System;

using System.Data;

using System.Configuration;

using System.Linq;

using System.Web;

using System.Web.Security;

using System.Web.UI;

using System.Web.UI.HtmlControls;

using System.Web.UI.WebControls;

using System.Web.UI.WebControls.WebParts;

using System.Xml.Linq;

/

public class cont_Emp_reg

{

      public cont_Emp_reg()

      {

     

      }

    int EmpId;

    long mobileNo, phoneno;

    string EmpName, address,destination, place, country, email;

    public int pEmpId

    {

        set

        {

            EmpId = value;

        }

        get

        {

            return EmpId;

        }

    }

   

    public string pEmpname

    {

        set

        {

           EmpName  = value;

        }

        get

        {

            return EmpName ;

        }

    }

    public string paddress

    {

        set

        {

            address = value;

        }

        get

        {

            return address;

        }

    }

    public string pdestination

    {

        set

        {

            destination = value;

        }

        get

        {

            return destination;

        }

    }

    public long pmobileno

    {

        set

        {

            mobileNo = value;

        }

        get

        {

            return mobileNo ;

        }

    }

    public long pphoneno

    {

        set

        {

            phoneno = value;

        }

        get

        {

            return phoneno;

        }

    }

    public string pplace

    {

        set

        {

            place = value;

        }

        get

        {

            return place;

        }

    }

    public string pcountry

    {

        set

        {

            country = value;

        }

        get

        {

            return country;

        }

    }

    public string pemail

    {

        set

        {

            email = value;

        }

        get

        {

            return email;

        }

    }

  

}

/*provider Class*/

using System;

using System.Data;

using System.Configuration;

using System.Linq;

using System.Web;

using System.Web.Security;

using System.Web.UI;

using System.Web.UI.HtmlControls;

using System.Web.UI.WebControls;

using System.Web.UI.WebControls.WebParts;

using System.Xml.Linq;

using System.Data.SqlClient;

public class prov_emp_reg

{

    public prov_emp_reg()

    {

       

    }

    dboperator db = new dboperator();

    public DataSet sel()

    {

        SqlCommand cmd = new SqlCommand();

        cmd.CommandText = "sel_employeeregistration";

        return db.ret(cmd);

    }

    public DataSet selmanager()

    {

        SqlCommand cmd = new SqlCommand();

        cmd.CommandText = "selmanager";

        return db.ret(cmd);

    }

   

    public DataSet selemp()

    {

        SqlCommand cmd = new SqlCommand();

        cmd.CommandText = "selemp_empgrade";

        return db.ret(cmd);

    }

    public int sel_maxeid()

    {

        SqlCommand cmd = new SqlCommand();

        cmd.CommandText = "max_EmployeeRegisterationTable";

        return db.max(cmd);

    }

   

    public void ins(cont_Emp_reg con)

    {

        SqlCommand cmd = new SqlCommand();

        cmd.CommandText = "ins_employeeregistration";

        SqlParameter pr = new SqlParameter();

        pr = cmd.Parameters.Add("@empid", SqlDbType.Int);

        pr.Value = con.pEmpId;

        pr = cmd.Parameters.Add("@empname", SqlDbType.VarChar);

        pr.Value = con.pEmpname;

        pr = cmd.Parameters.Add("@address", SqlDbType.VarChar);

        pr.Value = con.paddress;

        pr = cmd.Parameters.Add("@destination", SqlDbType.VarChar);

        pr.Value = con.pdestination;

        pr = cmd.Parameters.Add("@mobno", SqlDbType.BigInt);

        pr.Value = con.pmobileno;

        pr = cmd.Parameters.Add("@phoneno", SqlDbType.BigInt);

        pr.Value = con.pphoneno;

        pr = cmd.Parameters.Add("@place", SqlDbType.VarChar);

        pr.Value = con.pplace;

        pr = cmd.Parameters.Add("@country", SqlDbType.VarChar);

        pr.Value = con.pcountry;

        pr = cmd.Parameters.Add("@email", SqlDbType.VarChar);

        pr.Value = con.pemail;

        db.nonret(cmd);

    }

    public void upd(cont_Emp_reg con)

    {

        SqlCommand cmd = new SqlCommand();

        cmd.CommandText = "upd_employeeregistration";

        SqlParameter pr = new SqlParameter();

        pr = cmd.Parameters.Add("@empid", SqlDbType.Int);

        pr.Value = con.pEmpId;

        pr = cmd.Parameters.Add("@name", SqlDbType.VarChar);

        pr.Value = con.pEmpname;

        pr = cmd.Parameters.Add("@addr", SqlDbType.VarChar);

        pr.Value = con.paddress;

        pr = cmd.Parameters.Add("@dest", SqlDbType.VarChar);

        pr.Value = con.pdestination;

        pr = cmd.Parameters.Add("@mob", SqlDbType.BigInt);

        pr.Value = con.pmobileno;

        pr = cmd.Parameters.Add("@phn", SqlDbType.BigInt);

        pr.Value = con.pphoneno;

        pr = cmd.Parameters.Add("@place", SqlDbType.VarChar);

        pr.Value = con.pplace;

        pr = cmd.Parameters.Add("@country", SqlDbType.VarChar);

        pr.Value = con.pcountry;

        pr = cmd.Parameters.Add("@email", SqlDbType.VarChar);

        pr.Value = con.pemail;

        db.nonret(cmd);

    }

    public void del(cont_Emp_reg con)

    {

        SqlCommand cmd = new SqlCommand();

        cmd.CommandText = "del_employeeregistration";

        SqlParameter pr = new SqlParameter();

        pr = cmd.Parameters.Add("@empid", SqlDbType.Int);

        pr.Value = con.pEmpId;

        db.nonret(cmd);

    }

}

/*Coding of view work status*/

/*Container Class*/

using System;

using System.Data;

using System.Configuration;

using System.Linq;

using System.Web;

using System.Web.Security;

using System.Web.UI;

using System.Web.UI.HtmlControls;

using System.Web.UI.WebControls;

using System.Web.UI.WebControls.WebParts;

using System.Xml.Linq;

/// <summary>

/// Summary description for con_workstatus

/// </summary>

public class con_workstatus

{

      public con_workstatus()

      {

            //

            // TODO: Add constructor logic here

            //

      }

    int WorkId, EmpId;

    string status, date,type;

    public int pWorkId

    {

        set

        {

            WorkId = value;

        }

        get

        {

            return WorkId;

        }

    }

    public int pEmpId

    {

        set

        {

            EmpId = value;

        }

        get

        {

            return EmpId;

        }

    }

    public string pstatus

    {

        set

        {

            status = value;

        }

        get

        {

            return status;

        }

    }

    public string pdate

    {

        set

        {

            date = value;

        }

        get

        {

            return date;

        }

    }

    public string ptype

    {

        set

        {

            type = value;

        }

        get

        {

            return type;

        }

    }

}

Provider Class:

using System;

using System.Data;

using System.Configuration;

using System.Linq;

using System.Web;

using System.Web.Security;

using System.Web.UI;

using System.Web.UI.HtmlControls;

using System.Web.UI.WebControls;

using System.Web.UI.WebControls.WebParts;

using System.Xml.Linq;

using System.Data.SqlClient;

public class prov_workstatus1

{

      public prov_workstatus1()

      {

           

      }

    dboperator db = new dboperator();

    public DataSet sel()

    {

        SqlCommand cmd = new SqlCommand();

        cmd.CommandText = "sel_WorkStatusTable";

        return db.ret(cmd);

    }

    public DataSet sel_type()

    {

        SqlCommand cmd = new SqlCommand();

        cmd.CommandText = "sel_workstatustype";

        return db.ret(cmd);

    }

    public DataSet sel_empid(con_workstatus con)

    {

        

        SqlCommand cmd = new SqlCommand();

        cmd.CommandText = "sel_workstatusempid";

        SqlParameter pr = new SqlParameter();

        pr = cmd.Parameters.Add("@empid", SqlDbType.Int);

        pr.Value = con.pEmpId;

        return db.ret(cmd);

    }

    public void ins(con_workstatus con)

    {

        SqlCommand cmd = new SqlCommand();

        cmd.CommandText = "ins_WorkStatusTable";

        SqlParameter pr = new SqlParameter();

        pr = cmd.Parameters.Add("@workid", SqlDbType.Int);

        pr.Value = con.pWorkId;

        pr = cmd.Parameters.Add("@empid", SqlDbType.Int);

        pr.Value = con.pEmpId;

        pr = cmd.Parameters.Add("@status", SqlDbType.VarChar);

        pr.Value = con.pstatus;

        pr = cmd.Parameters.Add("@date", SqlDbType.VarChar);

        pr.Value = con.pdate;

        pr = cmd.Parameters.Add("@type", SqlDbType.VarChar);

        pr.Value = con.ptype;

        db.nonret(cmd);

    }

    public void upd(con_workstatus con)

    {

        SqlCommand cmd = new SqlCommand();

        cmd.CommandText = "upd_WorkStatusTable";

        SqlParameter pr = new SqlParameter();

        pr = cmd.Parameters.Add("@workid", SqlDbType.Int);

        pr.Value = con.pWorkId;

        pr = cmd.Parameters.Add("@empid", SqlDbType.Int);

        pr.Value = con.pEmpId;

        pr = cmd.Parameters.Add("@status", SqlDbType.VarChar);

        pr.Value = con.pstatus;

        pr = cmd.Parameters.Add("@date", SqlDbType.VarChar);

        pr.Value = con.pdate;

        pr = cmd.Parameters.Add("@type", SqlDbType.VarChar);

        pr.Value = con.ptype;

        db.nonret(cmd);

    }

    public void del(con_workstatus con)

    {

        SqlCommand cmd = new SqlCommand();

        cmd.CommandText = "del_WorkStatusTable";

        SqlParameter pr = new SqlParameter();

        pr = cmd.Parameters.Add("@empid", SqlDbType.Int);

        pr.Value = con.pEmpId;

        db.nonret(cmd);

    }

    public void del1(con_workstatus con)

    {

        SqlCommand cmd = new SqlCommand();

        cmd.CommandText = "del_WorkStatusworkid";

        SqlParameter pr = new SqlParameter();

        pr = cmd.Parameters.Add("@workid", SqlDbType.Int);

        pr.Value = con.pWorkId;

        db.nonret(cmd);

    }

}

Conclusion

Various subsections of this chapter gives an overview of source codes and its usage in the software development.

CHAPTER 4

SYSTEM TESTING

Introduction

Software testing is critical element of software quality assurance and represent the ultimate review of the specification, design and coding. System testing makes a logical assumption that all the part of the system is correct; the goal will be successfully achieved.

Testing objectives are:

Testing is a process of executing a program with the intend of finding an error.

A good test is one that uncovers an as yet undiscovered error.

• Unit testing
• Integration testing
• System testing
• User acceptance testing

4.1 Unit Testing 

Unit testing enables a programmer to detect error in coding. A unit test focuses verification of the smallest unit of software design. This testing was carried out during the coding itself. In this testing step, each module is going to be work satisfactorily as the expected output from the module.

Project aspect:

The front-end design consists of various forms. They were tested for data acceptance. Similarly, the back-end also tested for successful acceptance and retrieval of data.

4.2 Integration Testing            

Through each program work individually, they should work after linking together. This is referred to as interfacing. Data may be lost across the interface; one module can have adverse effect on the other. Subroutines after linking may not do the desired function expected by the main routine. Integration testing is the systematic technique for constructing the program structure while at the same time conducting test to uncover errors associated with the interface. Using integrated test plan prepared in the design phase of the system development as a guide, the integration test was carried out. All the errors found in the system were corrected for the next testing step.

Project aspect:

After connecting the back-end and the front-end as whole module, the data entered in the front-end once submitted were successfully entered in the database. On request, data were successfully retrieved in to forms.

4.3 System Testing         

After performing the integration testing, the next step is output testing of the proposed system. No system could be useful if it doesn’t produce the required output in a specified format. The output generated are displayed by the system under consideration and then tested by comparing with the format require by the user. Here the output format is considered in to two ways, one in on-screen and other in printed format.

Project aspect:

The entire project was tested and found successful.

4.4 Validation testing

The user has to work with the system and check whether the project meets his needs. In the validation checking, the user works with the beta version of the software.

Project aspects:

User enters the appropriate data and results was checked and validated

4.5 User acceptance test

User acceptance of a system is a key factor of the success of any system. The system under consideration was tested for user acceptance by running a prototype of the software.

Project aspects:   

An alpha version is demonstrated to the users. Their suggestions are recorded.

4.6 Table Data

4.6.1 Login Table

User ID	Password	Remarks
555	admin	valid
Sham	1	invalid
100	100	valid
Hjlk	100	invalid
5655	15655	valid

Table 4.1

4.6.2 Employee Registration Table

Emp ID	Emp Name	Address	Designation	Mob No	Phone No	Place	Country	Email	Remarks
100	Mirza	Mirza house	Manager	99899804999	0468599959994	Calicut	India	mirz@gmail.com	valid
101	Sam	Sam house	Manager	99399393993	0398883883888	Calicut	India	sam@gmail.com	valid
103	Aftab	Aftab house	Manager	8989	65f	Calicut	India	aff@gmai.com	invalid
1	Aftab	Aftab house	Manager	89895454	6565656565	Calicut	India	aff@gmai.com	invalid
103	Aftab	Aftab house	Manager	8989	655454545	Calicut	India	affkkjkjlk	invalid

                                                            Table 4.2

4.6.3 Assign Employee to Manger Table

Manger ID	Emp ID	Remarks
101	20	valid
102	21	valid
103	22	valid
104	23	valid
105	987888	invalid

                                                            Table 4.3

4.6.4 Salary Details Table

Emp ID	Date	Basic Salary	Incentive	Total Salary	Remarks
101	1-2-11	100000	10000	110000	valid
10221	1-3-00	1000	1000	2000	invalid
104	1-2-11	100000	10000	110000	valid
103	1-2-11	100000	10000	110000	valid
fdxdfx	1-3-00	1000	1000	2000	invalid

                                                Table 4.4

4.6.5 Work Assign Table

Work ID	Emp ID	Date	Work	Status	Type	Designation	Remarks
10	101	1-6-11	plumbing	Not Started	Easy	Calicut	valid
1000	1055	1-6-11	plumbing	Not Started	Easy	Calicut	invalid
11	106	1-6-11	carpentary	Not Started	Easy	Calicut	valid
12	108	1-6-11	Constructing a building	Not Started	Easy	Calicut	valid
kljkl	1055	1-6-11	plumbing	Not Started	Easy	Calicut	invalid

                                                Table 4.5

4.6.6 Work Registration Table

Work ID	Work	Date	Amount	Status	Remark
10	Plumbing	1-2-10	2000000	Not Started	valid
1011	Plumbing	1-2-10	2000000	Not Started	invalid
11	carpentary	1-2-10	2000000	Not Started	valid
101	4454	1-2-10	2000000	Not Started	invalid
Kljkl	Plumbing	1-2-10	2000000	Not Started	invalid

                                                            Table 4.6

4.6.7 Employee Grade Table

Emp ID	Grade	Remark
100	A	valid
10011	Ioj	invalid
101	A	valid
108	D	valid
kljklj	A	invalid

                                                            Table 4.7

4.6.8 Work Status Table

Work ID	Emp ID	Status	Date	Type	Remark
10	100	Processing	1-8-11	plumbing	valid
Klk	1001	Processing	1-8-11	plumbing	invalid
14	100	Processing	1-8-11	carpentary	valid
18	100	Processing	1-8-11	painting	valid
101	Mklm	Processing	1-8-11	plumbing	Invalid

                                                   Table 4.8

Conclusion

Various subsections of the chapter provide an overview of validation and testing process.

CHAPTER 5

IMPLEMENTATION

Introduction

Implementation is a process of converting a new system into an operational one. The designed system is converted into an operational one using a suitable programming language. Implementation includes all those activities that take place to convert an old system into a new one. Proper implementation is necessary to provide a reliable system to meet organizational requirement.

The implementation phase involves careful planning investigations of the systems and constraints, design of methods to achieve the changeover, the training of staffs in the changeover phase and finally the evaluation of the changeover. Training is an important job in implementation. In this phase we teach the user how to use the system. If proper training is not given to the user then the system will became useless as all functionality of the system will not be used by the user.

The implementation phase of the software design consists of different tasks to be done sequentially for obtaining the desired results. Here we do not implement parallel; instead we first implement admin and then the user module. The different phases are:

5.1 Creating the Database

A Database is created, in which all the tables are defined which are required to do the different operations such as storage and retrieval of information. Databases are designed in such a way it can handle the different database queries. User and admin can retrieve required details from the system on clicking on the links and buttons. 

5.2 Creating Graphical User Interface

Graphical User Interface is created in Visual Studio 2005 Express Edition under .NET framework 2.0 for a user friendly interface. It is intended for two purposes. First is to create a user friendly interface for the software. Having a good user interface makes it easier for the user to use and understand the different functionalities of the software. Secondly, the user interface hides the end users from the complexities in the working of the software. So the user is made unaware of how a task is performed when he chooses to perform it.

5.3 Creating System Environment:

For the intended project to work on, we need to implement its required hardware and software requirements. This system is build using Visual Studio 2005 under .NET framework and based on Windows Operating System. Memory And Hard disk should confirm according to hardware requirements mentioned  above.

5.4 Performing Function  

Initially we implement the admin module because the operation made in admin reflects in the user module. After implementing this, we check whether all the operations and reports are up to the specification. Only after ensuring this we go for user module. With the help of a user-friendly visual interface, the end users can perform the desired operations. Upon selecting any operation, the corresponding link commands will be passed to database and the response is also received. The responses are then retrieved and displayed in screen.

Conclusion

Implementation describes about the whole activities necessary to provide a reliable system to meet organizational requirement.

CHAPTER 6

USER’S MANUAL

Introduction

The user manual provides user-friendly input and output forms that have been designed with interactive dialogue. It enables the end users to insert details very easily through corresponding interface forms.

6.1Screen Shots

6.1.1 Login page Form:

                                                Fig 6.1 Login page Form

6.1.2 Admin home page Form:

                                                Fig 6.2 Admin home page Form

6.1.3    Emp/Mang Resgisteration Form:

Fig 6.3 Emp/Manager Reg Form

6.1.4    Work Registration Form:

                                                            Fig 6.4 Work Reg  Form

6.1.5    Admin view Work status Form:

Fig 6.5 Admin view work status Form

6.1.6    Admin assign work to Manager Form:

                                                            Fig 6.6 Admin assign work  Form

6.1.7    Manager home page Form

                                                            Fig 6.7 Manager home page Form

6.1.8    Manager view Assigned work Form

Fig 6.8 Manager view assigned work Form

6.1.9    Manager assign grade to Emp Form

Fig 6.9 Manager Assign Grade  Form

6.1.10           Employee Home Page Form

Fig 6.10 Employee homepage Form

6.1.11           Emp Update Status Form:

Fig 6.11 Employee Update Status Form

Conclusion

Cooperative bank has made rapid strides towards increasing overall awareness among consumers to better plan and secures their future, and providing effective means to do so.

The cooperative bank provides finance for trade commerce and priority sectors to cater to the credit need of small artisans, self-employed persons, small traders etc.

Thus we can conclude that the loan automation system will be highly efficient in providing online loans for the customers. It will be reliable and scalable.