PART I

INTRODUCTION

Chapter 1 Introduction to Project

1.1 Detailed Description Of Problem 1.2 Objectives 1.3 Limitations Of Existing System

1.1 Detailed Description of Problem

Today Real Estate is growing rapidly and to survive in the market is quite difficult with previous technologies. So to survive in the market new technologies are mandatory. The industry must be flexible enough to undertake changes. The industry must continue to grow. And to grow in market the good management system must be there. During our visit we found that the industry is running with the old style with paper work, the static departments at one place. Time consuming verification tasks, lake of communication between employees, mismatch between employee privileges, challenging rescheduling tasks and difficult complain handling. Here are the problems explained: Construction Project Phase Issued: Project is created in phases. But once the phase is created, updating in the phase is not possible. Phase becomes static. If there is any change in the phase then whole phase is discarded and new phase is created. Paper Work Issues: The institute is totally running on paper based work. This makes the task time consuming. To store this paper work is another problem. It needs space to store hard documents. The volume of paper work is continuously growing. The cost of doing the paper work has been rising rapidly. The time required for the preparation of the paper work, which when delays are involved makes it increasingly less valuable. Errors and inaccuracies detract from the value of the finished product. Searching for document is another issue. The document searching takes more time when there are too many documents at one place. Searching process becomes very hard.

Verification of documents by higher authority takes time to get accomplished. This process increases cycle time because without verification no work can be started or terminated.

The security of the paperwork may not be considered soundproof and is always a threat when more important documents are considered.

Attendance Issue: Cannot find record of available workers at the field so that work allocation task becomes difficult. Employee management becomes difficult and time consuming as attendance data is not readily available. Employee Management Issues: The institute is having some problems in management of employees as the privileges were not set accurately for employees. New recruit employees data are not handled very well. Employee profiles are not created properly so that training issues are also there as there is no clear record of employees. Work Allocation Issues: Work allocation is not done properly in hierarchical manner. Work allocation is not done as per the employee capability as there is no clear record of the employee profiles. For instance by mistake some employees are getting too many work and some capable employees are getting less work. Work Reporting Issues: Work Reporting must be done as the work is completed. There is no reminder or alert facility for employees regarding completion of the work.

Uncompleted work must be reported to and responded by the higher authority. But there is no such facility at industry.

Complaint Issues: There is no facility for managing complaint of employees. Complaint is not going as per the hierarchy of the industry.

Rescheduling Issues: In the system, there is no proper reporting of finished work/pending work to higher authorities. So, Rescheduling becomes very difficult. Rescheduling work also becomes time consuming as the data is not readily available. If the data is lost then it is very difficult to reschedule the work.

Monitoring Issues: Monitoring is mandatory for industry as the on-going field work needs to be reported to higher authority but there is no handling of monitoring report. Communication Issues: There is no proper way of communication between employees. Employees are not able to send documents to the higher authorities as soon as possible. Sharing of Legal Documents is also difficult because of security reasons. Employees are not able to send a single report to more than one department at a time.

1.2 Objectives
Software is effective only if it can support the realities of business and offer cost effective solutions to the problems. So according to the problems we proposed a solution as ERP system for Construction Industry. This software generates information on a daily basis. Separate systems are no longer required to manage the individual operations of industry. With this project Construction ERP Software, adequate care has been taken on integrating all functional departments by the use of a single business tool to seamlessly blend property development with performance enhancement and accountability at every stage of the construction activity. Whether you are a main contractor or a specialist trade contractor, an architect, surveyor, project manager or consulting engineer, a maintenance contractor or house builder, we will have a solution to meet your specific requirements. This Software enables you to make better, faster decisions through real-time business intelligence. With our modular solutions industry can assemble a fully integrated system that meets exact business requirements to save time and money and helps to make better business decisions. Dynamic Construction Phase: The construction project will be managed dynamically that means the phases will be created, updated or deleted as per the requirements. Attendance management: Attendance will be taken and the report will be generated as per the requirements. Other departments will be provided attendance data on a single click. This will save time of work allocation. There will be a clear record of current employees working on a field and those who are not.

Better Employee Management Employees will be given privileges as per capabilities. Employees profile will be created at the time of recruitment. And can be updated by the time. This will make authorities clear. No other employee is allowed to access restricted area. Training will be provided to the user whenever new technology is adopted. Employee profile comparison will be easy.

Better Work Allocation: Work allocation will be done as per the employee profiles. That will improve employee satisfaction and that will result into improved employee relation with the industry. Work Reporting: Work reporting will be done in hierarchical manner.

Work Reallocation: Work reallocation will be easy as the data will be available on the click. Reallocation process time will be reduced.

Better Complaint Management: Complaint management will handle all complaints generated. All the verified complaints will be responded.

Efficient Monitoring: A continuous monitoring will be done and reports will be generated as per requirement like hourly, daily, weekly.

Bulk Mailing: Mailing will improve internal communication between employees.

Employees will be able to Share legal Documents and Papers rather than moving from one department to other.

Additional Outcomes: This project will save time and expenses of user. Work can be allotted to the employees from anywhere. It provides mobility to the industry. Improves management decision making. Reports about employees everyday work can be generated as required. Employee will be able to rearrange the work, delete or modify tasks. The entire arrangement related to employees training will become easier. Ease of expansion/growth and increased flexibility. Big amount of time is saved from paper work so the project cycle reduces. Keeps track on the daily work done by the employees. Builder can have real time project environment on the screen.

1.3 Limitations

During our visit at Softcom Technologies we were offered an ERP software for Construction Industry. Construction Industry wants to get work done from anywhere. Here are the problem points. A real estate world is growing rapidly so company must have latest technologies and management schemes for seamless grow. Mobility, that is the first requirement, was not there at construction industry. That means the work must be carried out manually. That was a big problem. The project management was very difficult. It was almost not possible to handle two projects at the same time. The project handling in phases was not arranged properly. So the phases of project were very static. Once the project phase was created workers must follow the phase. That is tremendous sometimes. Employee management was quite ok but not very effective for the Organization as it should be. Proper attendance report was not found at Organization. Without attendance the employee management was not possible. Requirements of employees were handled but there was not record of requirements so further planning was facing some problem. Communication within the employees was not as fast as it should be. The time required for the preparation of the paper work, which when delays are involved makes it increasingly less valuable. Errors and inaccuracies detract from the value of the finished product. Rescheduling process needs all record of previous work. This task is very difficult here. Work planning was very difficult as no centralization was possible. The security of the paperwork may not be considered soundproof and is always a threat when more important documents are considered.

PART II SYSTEM ANALYSIS AND DESIGN

Chapter 2 Project Planning

2.1 Software Process Model 2.2 Tools and Technology 2.2.1 Hardware Requirement 2.2.2 Software Requirement

2.1 Software Process Model

To solve actual problems in an industry setting, a software engineer or a team, of engineers must incorporate a development strategy that encompasses the process, methods, and tools. This strategy is often referred as a Process Model or Software Engineering Paradigm The different phases of Software Development Life Cycle are as follows.

System Engineering Analysis

Design

Coding Testing

i.

Phase - 1 -Problem Identification In this phase, the Problem Statement is been defined which describes the user Problem as a whole.

ii.

Phase - 2- Requirement Analysis In this phase, the document containing the details about the System to Be Is generated which is known as Software Requirement Specification (SRS). Objective of this document is to understand nature of system to be build. This Document covers details like problem statement, Man power required to build System, hardware & Software Configuration, Time Period, System Infrastructure etc. Simultaneously, Data collection is also performs in which the transactional & Master data of existing system are collected. These data will be used later at the Time of validation, verification and testing of new system.

iii.

Phase -3 - System Modeling In this phase, the document known as Software Design Specification (SDS) is generated, which shows graphical representation like DFDs etc. of System to be? This phase mainly focuses on four distinct attribute of the system: Data structure, software architecture, interface representation and procedural Details. Using these diagrams the validation process is being carried out using The Collected data to validate software and procedural details.

iv.

Phase - 4 - Designing In this phase, the system user interface is defined and verified against the SDS. If any conflict occurs in the problem definition or designing, the SRS or SDS Documents review or redesign.

v.

Phase 5 - Coding After validating & verifying SDRS Documents, the design is translated into a Machine readable form. This phase perform this task. Simultaneously, user manuals are also generated for testing purpose.

vi.

Phase - 6 Testing Once code has been generated, program testing begins with collected data. The Testing process focuses on the logical internals of the software, ensuring that all Statements have been tested, and functional externals; that are, conducting tests to uncover errors and ensure that defined input will produce actual results that Agree with required results. This phase includes both alpha & beta testing

vii.

Phase 7 - Monitoring Software will undoubtedly undergo change after it is delivered to the customer. Change will occur because: Errors have been encountered. The software must be adapted to accommodate changes in its external environment. The customer requires functional or performance Enhancement Software Support & maintenance reapplies each of the preceding phases to an Existing system rather than a new one.

Software Model
Each project need to be developed with software model which makes the project with high quality, reliable and cost effective. We have chosen Waterfall Model for developing the ERP system. I. Introduction The Waterfall Model derives its name due to the cascading effect from one phase to the other as is illustrated in Figure. In this model each phase well defined starting and ending point, with identifiable deliveries to the next phase. Note that this model is sometimes referring asthe linear sequential modelorthesoftware life cycle.

The model consists of six distinct stages, namely: i. Requirement Analysis Phase In the Requirement Analysis phase a) The problem is specified along with the desired service objectives (goals) b) The constraints are identified ii. Specification Phase In the Specification phase, the system specification is produced from the detailed definitions of (a) and (b) above. This document should clearly define the product function. iii. Design Phase In the system and software design phase, the system specifications are translated into a software representation. The software engineer at this stage is concerned with: a) b) c) d) Data structure Software architecture Algorithmic detail and Interface representations

The hardware requirements are also determined at this stage along with a picture of the overall system architecture. By the end of this stage the software engineer should be able to identify the relationship between the hardware, software and the associated interfaces. Any faults in the specification should ideally not be passed down stream iv. Implementation and Testing Phase In the implementation and testing phase stage the designs are translated into the software domain a) Detailed documentation from the design phase can significantly reduce the coding effort. b) Testing at this stage focuses on making sure that any errors are identified and that the software meets its required specification. v. Integration and System Testing Phase In the integration and system testing phase all the program units are integrated and tested to ensure that the complete system meets the software requirements. After this stage the software is delivered to the customer

vi. Maintenance The maintenance phase is usually the longest stage of the software. In this Phase the software updated to: a) Meet the changing customer needs b) Adapted to accommodate changes in the external environment c) Correct errors and oversights previously undetected in the testing phases d) Enhancing the efficiency of the software Observe that feed loop allow for corrections to be incorporated into the model. For Example a problem/update in the design phase requires a revisit to the specification Phase. When changes are made at any phase, the relevant documentation should be updated to reflect that change. II. Advantages i. ii. iii. III. Testing is inherent to every phase of the waterfall model It is an enforced disciplined approach It is documentation driven, that is, documentation is produced at every stage

Implementation in our project In our project, we have followed this model strategy which helps us to prepare a better final product. As mentioned in the above discussion, we kept the project control task which was prepared on the base of requirement and derived design of the system. One effective use of this type of model is for product development, in which the developers (we) themselves provide the specifications and therefore have a lot of control on what specifications go in the system and what stay out. In fact, most products undergo this type of development process. First, a version released that contains some capability. Based on the feedback and experience with this version, a list of additional desirable features and capabilities are generated.

IV.

How we use this model for developing this project i. ii. iii. iv. First task of our project begins with requirement analysis, in this task we are trying to understand what user asks and what he wants? Then we are reviewing ourselves what we understood about project and prepare problem specification, which we had to show to the user. And finally they approve problem specification and the requirement analysis task gets over. Then I started to design this project.

v. vi. vii. viii. ix. x. xi.

Initially I had started by building UMLs for the project. These UMLs are useful to understand the flow of the project and the data within it. Than after we designs forms for each modules. After successful completion of the design task we started coding for this project modules wise. After coding the most difficult and important task is testing. First we apply the unit testing after that integration testing find the lots of bugs in whole system. Here first we prepared test cases for fixing bugs in the developed project. Then we conducted tests one by one and trying to fix bugs, whichever was found. Finally we test whole system and ensure that our system is mostly error free.

2.2 Tools and Technology

1. 2. 3. 4. 5. 6. 7. 8. 9. 10. 11. Platform Client OS Server OS Client Authoring Server Side Code Behind Web Server Development Tool Version & Source Control Back-End Tools A&D/UML : Microsoft Visual Studio .NET 2010 : Windows XP / Vista / Windows 7 : Windows 2003 Server Enterprise Edition : XHTML, JavaScript , CSS : ASP.NET 3.5 : C#.NET 2010 : IIS6 : Visual Studio .NET 2010 : Visual Source Safe 2005 : MS SQL Server 2008 : MS Visio 2007

2.2.1 Hardware Specifications:

Server Configuration:

CPU 2.0 GHz RAM 4GB Network 100Mb/s

Client Configuration:

CPU 2.0 GHz RAM 1GB Network 100Mb/s

2.2.2 Software Specification

Overview ASP.NET

ASP.NET is a web application framework developed and marketed by Microsoft to allow programmers to build dynamic web sites, web applications and web services. It was first released in January 2002 with version 1.0 of the .NET Framework, and is the successor to Microsoft's Active Server Pages (ASP) technology. ASP.NET is built on the Common Language Runtime (CLR), allowing programmers to write ASP.NET code using any supported .NET language. The ASP.NET SOAP extension framework allows ASP.NET components to process SOAP messages. Features of ASP.NET Improved performance Flexibility Configuration settings Security Web Hosting

Overview SQL Server 2008

Microsoft SQL Server is a relational database server, developed by Microsoft: It is a software product whose primary function is to store and retrieve data as requested by other software applications, be it those on the same computer or those running on another computer across a network (including the Internet). SQL server 2008 makes giants strides in performance, reliability and scalability, giving your organization many opportunities to create intelligent, real world business solutions. By voicing a need for more simplified and costsaving features, organizations inspired the following innovation in SQL Server 2008. Scalable from laptop to multiprocessor luster Dynamic row-level locking Dynamic self-management Wide array of replication options SQL Server Desktop Integrated OLAP services Data transformation services Microsoft English query These innovations, plus many more changes, make SQL Server highly scalable and excellent for data warehousing.

The software does not encourage the entry of any malware that can cause any problems with the computer of the user. The user is ensured that there would be no data loss while using this software.

Why Visual Studio & C#? Why Visual Studio?

Parallel Development Microsoft now provides an environment that will help do this through Visual Studio IDE support for Parallel development and Native C++ libraries and compiler support for parallel applications.

Coding Improvements A new editor uses Windows Presentation Foundation technology to provide integrated support that helps you understand your code.

Web Development A new set of ASP.Net tools allows developers to use TDD to build Model-ViewController (MVC) based websites.

Modeling Tools Using VSTS 2010 Architecture, both technical and non-technical users can work together to model business systems using either UML or DSL this modeling capability is part of the Oslo modeling platform.

Why C#? Advantages over C and C++

It is compiled to an intermediate language (CIL) of the language it was developed or the target architecture and operating system. Automatic garbage collection. Pointers no longer needed (but optional). You can't use non-Boolean variables (integers, floats...) as conditions. This is much cleaner and less error prone.

Advantages over java

Usually it is much more efficient than java and runs faster. CIL (Common (.NET) Intermediate Language) is a standard language, while java byte code is not a standard language. Simplified multithreading.

Chapter 3 System Analysis

3.1

3.2

Feasibility Study 3.1.1 Operational Feasibility 3.1.2 Technical Feasibility 3.1.3 Financial and Economic Feasibility 3.1.4 Schedule Feasibility Requirement Specification 3.2.1 Functional Requirements 3.2.2 Non-functional Requirements

3.1 Feasibility Study

Preliminary investigations examine project feasibility; the likelihood the system will be useful to the organization. Three tests of feasibility-all equally important are studied: operational, technical and financial. Operational Feasibility Proposed projects are beneficial only if they can be turned into information systems that will meet the organizations operating requirements. To know whether system will work when implemented, here are some points we will look when we market the product:

Is there a sufficient support for the project from management? From users? Is there a reason
for change? Do we have resistance from employees?

Are current methods of business acceptable to users? If not they might welcome the change. We will try to involve users as much as possible through training to reduce chances of
resistances.

Most importantly assessment is done to assure that the proposed system will not cause harm
or poor results in any respect or area and will not slow performance of any individual or organization.

Technical Feasibility There are number of technical issues which are generally raised during the feasibility stage of investigation. The technical feasibility involves the study about the availability of the tools required for the proposed system. Here the tools involve the hardware required for the development and the implementation of the system. The technical needs of the system may vary considerably, but might include: The facility to produce output in a given period of time. Response time under certain conditions. Ability to process a certain volume of transaction at a particular speed. Facility to communicate data to distant location.

Hardware Feasibility Server:

CPU 2.4 GHz, core i-5 RAM 4GB Network 1Gb/s

Client:

CPU 1.8 GHz, dual core RAM 1GB Network 100Mb/s

Software Feasibility The S/W requirements for developing this system are as follows: Windows 7 / Vista / XP (Service Pack 3) Visual Studio 2010 (ASP.NET 4.0 using C#) SQL Server 2008 SP2

Financial and Economic Feasibility A software product needs to be a good investment for the organization. Financial benefits must equal or exceed the costs. We are examining the Costs of Other Multilevel system before and after installation of Textile Multilevel System. Also as for development cost we have sufficient programming Tools and knowledge base available. Schedule Feasibility Projects are initiated with specific deadline. We need to evaluate whether the deadlines are mandatory or desirable. Time is the one of the critical factor in the development of any system but this kind of feasibility is hardly perfect in any system. We have been asked to complete the project within the working days of the organization having period of 5-6 months approximately. So we have managed to complete the project before given deadline. In this project planning section we have elaborate our ideas to develop the system within the given period.

Selecting the Project Development Strategy: After preliminary investigation, we need to decide development strategy. There are mainly two types of applications: Institutional Applications: Affect broad corporate activities, multiple departments, or basic business processes on which the organization is built. Examples: Work allocation, Defect Tracking, Employee Management, E-mail Services, etc. End-User Applications: Limited in scope, often producing information that remains within the department or work unit in which it is generated; report- and output-oriented rather than transaction- or inputdriven. Typically use fourth-generation languages, personal computer software packages and focus on information retrieval and presentation. Example: sales call history, price quotation and project proposal, assorted one-time spreadsheet analysis etc. From the above concept our system is end-user oriented. But sometimes it can be institutional also, suppose for example in Generates a candidates it will affects to whole department of the system because after generates the candidates payment process will be done also book generation and coupons generation also done parallel and this process will affects to all the sections of the system. Also we would like to take institutional approach since our system can span across many departments of a company.

3.2 Requirement Analysis

The requirement analysis of ERP System, system contains the study of the existing system in which they are working. By the study of existing system we got the basic requirement and idea for proposed system. It also includes analysis of software interface with hardware, people, and database. Requirement gathering is a base part of system planning. Most of the basic and hidden requirement needs to be study. It also includes users, system, and hardware requirement. Requirement gathering means to collect and understand all the related requirements by all the possible sources. By the study of existing system, by discussing with users, etc. are the sources of requirement gathering. Requirement should be gather very clearly with good sense of mind. After the requirement gathering the next most important thing is requirement analysis, gathered requirement are like rough information. We have to analysis requirement on technical and practical level. Requirement analysis provides the system designer with a representation of information and function that can be translated data function and procedure, requirement analysis bridges the gaps between manual system and proposed system. Requirement analysis involves study of all the requirements, study of current system, and study of internal and external interface. By the entire conclusion we get the idea about how it works and where improvements are possible.

3.2.1 Functional Requirements:

Project Phase will be created dynamically. This Work Allocation Module will allow the Controller to allocate work units to each of the assembly and preparation areas. Work allocation helps in keeping track of the work done by the employees on day-to-day basis. Reports Module will give you startling insights about your team and projects. Work can be allotted to the employees from anywhere. Ease of expansion/growth and increased flexibility. It provides a comprehensive enterprise view. It makes realtime information available to management anywhere, any time to make proper decisions. Builder can have real time project environment on the screen. User management is handled by Employee Management module of the system. This provides information of user when needed. Any kind of defects can be handled from any time anywhere. Employees can communicate through mailing. And also can send or receive documents. Employees can be aware about ongoing events in industries via news and events dashboard.
Computers can be used to keep track of vital pieces of business information, including client activities, billing and pay roll data. In courier companies, a database can be used to store information about clients established destinations and pick up points, as well as their credit limits and payment history. This database can be used to link services directly to the billing system, so that invoices are automatically generated and billed to each client's account.

Email communications have rapidly become an indispensable business tool. This combines the speed of picking up the phone with the assurance of having a written record of what jobs were requested when, by whom, and the cost for the services. You can send electronic confirmation when services are complete.

An integrated computer tracking system can detail when each job was picked up and when it was delivered. It can also serve as a record of who accepted delivery. This can alleviate any security issues regarding lost packages.

What all you need to do in order to send a courier or parcel to any corner of the world, is just to call a courier company. The company not only just picks up the parcel from the desired location, but also makes arrangements for packing, loading and unloading. Unlike the typical postal service, you dont need to visit any office to book your shipment. Further, you can also book your parcel delivery online and get the tracking number instantly.

Our Courier service provides very speedy and efficient courier service, so that the receiver can get his / her courier in least time duration and there is very less chance for sending courier to wrong place.

3.2.2 Non Functional Requirements

Non-Functional Requirement is a requirement that specifies criteria that can be used to judge the operation of a system, rather than specific behaviors. This should be contrasted with functional requirements that define specific behavior or functions. Non-functional requirements are attributes that either the system or the environment must have. Such requirements are not always in the front of stakeholders' minds, and often you must make a special effort to draw them out. To make it easier to capture non-functional requirements, we organize them into five categories: Usability Reliability Performance Supportability Security

Usability describes the ease with which the system can be learned or used. A typical usability requirement might state: The system should allow novice users to install and operate it with little or no training. The end user shall be able to given privileges as per the role of the user. The end user shall be able to access page within four seconds.

Reliability describes the degree to which the system must work for users. Specifications for reliability typically refer to availability, mean time between failures and mean time to repair, accuracy, and maximum acceptable bugs. For example: The system shall meet the terms of a Service Level Agreement.

Performance specifications typically refer to response time, transaction throughput, and capacity. For example: All Web pages must download within three seconds during an average load, and five seconds during a peak load. While executing a search, the system must be able to display 500 search results per page.

Supportability refers to the software's ability to be easily modified or maintained to accommodate typical usage or change scenarios. For instance, in our help desk example, how easy should it be to add new applications to the support framework? Here are some examples of supportability requirements: The system shall allow users to create new workflows without the need for additional programming. The system shall allow the system administrator to create and populate Email and news. Security refers to the ability to prevent and/or forbid access to the system by unauthorized parties. Only authorized system administrators shall be permitted to access employee profile.

Chapter 4 System Design

4.1 4.2 4.3 4.4 4.5

Data Flow Diagrams Flow Chart Process Hierarchy Activity Diagram Data Dictionary

4.1 Data Flow Diagram

4.1 4.1.1 4.1.2 4.1.3 4.1.4 4.1.5 4.1.6 4.1.7 4.1.8 4.1.9 4.1.10 4.1.11 4.1.12 4.1.13

Data Flow Diagram Context Level Diagram Zero Level DFD 1st Level DFD for Enterprise 1st Level DFD for Project Creation 1st Level DFD for Project Phase Creation 1st Level DFD for Employee Management 1st Level DFD for Leave Management 1st Level DFD for Work Allocation 1st Level DFD for Work Reporting 1st Level DFD for Defect Track 1st Level DFD for Rescheduling 1st Level DFD for News and Events 1st Level DFD for Bulk Mailing

4.1.1 Context Level Diagram

Set Registration details

Employee

Request for work Submit Report

Set Registration details Req. for information

Client

View Report Get feedback Get Information Check varification/validation Check client info. Edit Check Work

Get Information Get Verification/validation data Check varification/validation Check client info. Delete Edit Check Work

ERP for Construction Industry

Response

Response Feedback Get data Get details(weekly)

Admin

Feedback Get data Get details(weekly)

Super Admin

Get details (weekly, monthly) Set details (weekly, monthly)

Report

4.1.2 Zero Level DFD:

4.2.3 First Level DFD for Enterprise Hierarchy

4.2.4 First Level DFD for Project Creation

4.2.5 First Level DFD for Project Phase Creation

4.2.6 First Level DFD for Employee Management

4.2.7 First Level DFD for Leave Management

4.2.8 First Level DFD for Work Allocation

4.2.9 First Level DFD for Work Reporting

4.2.10 First Level DFD for Defect Track

4.2.11 First Level DFD for Rescheduling

4.2.12 First Level DFD for News and Events

4.2.13 First Level DFD for Bulk Mailing

4.2 Flow Chart

4.3 Process Hierarchy

Project Creation

2.1

2.2

2.3

2.4

2.5

Create Project

Analysis

Verification & Validation

Accept / Reject

Edit

2.2.1

2.2.2

2.2.3

2.2.4

2.2.5

Create Project

Create Project

Create Project

Create Project

Create Project

Phase Creation

3.1

3.2

3.3

3.4

View Phase

Phase Creation

Submit

Approval

3.2.1

3.2.2

Create Phase

Update Phase

Employee Management

4.1

4.2

4.3

4.4

Add Employee

Verification & Validation

Edit

Delete

4.1.1

4.1.2

4.1.3

4.1.4

4.1.5

View

Request Form

Fill Up Form

Submit

Approval

Leave Management

5.1

5.2

5.3

Apply for Leave

Verification & Validation

Approval

Work Allocation

6.1

6.2

6.3

6.4

View

Allocate Work

Submit

Approval

View Allocated Work

6.5

Work Reporting

7.1

7.2

7.3

7.4 Approval

View

Submit Report

Verification & Validation

Defect Track

8.1

8.2

8.3

8.4

8.5

View

Check Report

Evaluate Defect

Submit to Higher Authority

Approval

Rescheduling

9.1

9.2

9.3

9.4

9.5

View

Reallocation

Submit

Verification & Validation

Approval

News and Events

10.1

10.2

10.3

10.4

10.5

View

Add

Update

Delete

Publish for Employees

Bulk Mailing

11.1

11.2

11.3

11.4

View

Send Mail

Receive Mail

Delete

4.4 Activity Diagram

4.4.1 Activity Diagram for Admin

4.4.2 Activity Diagram for Employee

4.4.3 Activity Diagram for Project Leader

4.5 Data Dictionary

1. Table Name : Employee_Master Primary Key : EmpId Foreign Key : CountryId, StateId , CityId, DesignationId, DepartmentId, SkillId Description : Contains details of Employee. Serial No. 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 Field Name EmpId Password EmpFname EmpLname Gender Address CountryId StateId CityId DOB MobileNo EmailAdd DOJ DeptId DesigId SkillId Qualification Experience Seq.Ques Answer EmpImg Data Type Int nvarchar nvarchar(20) nvarchar(20) nvarchar(7) nvarchar(100) Int Int Int Date Int nvarchar(30) Date Int Int Int nvarchar(100) nvarchar(100) Int nvarchar(50) nvarchar(15) Constraints Primary Key Not Null Not Null Not Null Not Null Not Null Foreign Key Foreign Key Foreign Key Not Null Not Null Not Null Not Null Foreign Key Foreign Key Foreign Key Not Null Not Null Not Null Not Null Not Null Description Identification no. of Employee Password of Employee First name of Employee Last name of Employee Gender of Employee Address of Employee Identification no. of Country Identification no. of State Identification no. of City Birthdate of Employee Mobile No of Employee E-mail Address of Employee Date of joining of Employee Identification no. of Department Identification no. of Designation Identification no. of Skill Qualification of Employee Experience of Employee Security Question of Employee Answer of Security Question Photo of Employee

2. Table Name : Client Master Primary Key : ClientId Foreign Key : ProjectId , CountryId, StateId , City Id Description : Contains details of Client. Serial No. 1 2 3 4 5 6 7 8 9 10 Field Name ClientId ClientName ClientAdd CountryId StateId CityId MobileNo OfficeNo EmailAdd ProjectId Data Type Int nvarchar(50) nvarchar(100) Int Int Int Text Int nvarchar(50) Int Constraints Primary Key Not Null Not Null Foreign Key Foreign Key Foreign Key Not Null Not Null Not Null Foreign Key Description Identification no. of Client Name of Client Address of Client Identification no. of Country Identification no. of State Identification no. of City Contact number of Client Office number of Client Email Address of Client Identification of Project

3. Table Name : Project_Master Primary Key : ProjectId Discription : Details of Project. Serial No. 1 2 3 4 5 6 7 Field Name ProjectId ProjectName ProjectType ProjectDuration ProjectStartDate ProjectCost ProjectStatus Datatype Int nvarchar(30) nvarchar(30) int date int int Constraints Primary Key Not Null Not Null Not Null Not Null Not Null Not Null Description Identification no. of Project Name Of Project Type of Project Duration of Project Start Date of Project Cost of Project Status of Project

4. Table Name : Country_Master Primary Key : CountryId Description : Selection of Country. Serial No. 1 2 Field Name CountryId CountryName Data Type Int nvarchar(20) Constraints Primary Key Not Null Description Identification no. of Country Name of Country

5. Table Name : State_Master Primary Key : State Id Foreign Key : CountryId Description : Selection of State. Serial No. 1 2 4 Field Name StateId StateName CountryId Data Type Int nvarchar(20) Int Constraints Primary Key Not Null Foreign Key Description Identification no. of State Name of State Identification no. of Country

6. Table Name : City_Master Primary Key : CityId Foreign Key : CountryId, StateId Description : Selection of City. Serial No. 1 2 4 5 Field Name CityId CityName StateId CountryId Data Type Int nvarchar(20) Int Int Constraints Primary Key Not Null Foreign Key Foreign Key Description Identification no. of City Name of City Identification no. of State Identification no. of Country

7. Table Name : Project_Leader_Master Primary Key : PLId Foreign Key : CountryId, StateId , CityId, DesignationId , DepartmentId, SkillId Description : Contains details of Employee. Serial No. 1 Field Name PLId Data Type Int Constraints Primary Key Description Identification no. of Project Leader Password of Project Leader First name of Project Leader Last name of Project Leader Gender of Project Leader Address of Project Leader Identification no. of Country Identification no. of State Identification no. of City Birthdate of Project Leader Mobile No of Project Leader E-mail Address of Project Leader Date of joining of Project Leader Identification no. of Department Identification no. of Designation Identification no. of Skill Qualification of Project Leader Experience of Project Leader Security Question of Project Leader Answer of Security Question Photo of Employee

2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21

Password PlFname PlLname Gender Address CountryId StateId CityId DOB MobileNo EmailAdd DOJ DeptId DesigId SkillId Qualification Experience Seq.Ques Answer EmpImg

nvarchar nvarchar(25) nvarchar(25) nvarchar(7) nvarchar(75) Int Int Int Date Int nvarchar(30) Date Int Int Int nvarchar(100) nvarchar(100) Int nvarchar(50) nvarchar(15)

Not Null Not Null Not Null Not Null Not Null Foreign Key Foreign Key Foreign Key Not Null Not Null Not Null Not Null Foreign Key Foreign Key Foreign Key Not Null Null Not Null Not Null Not Null

8. Table Name : Department_Master Primary Key : DeptId Description : Details of Department. Serial No. 1 2 3 Field Name DeptId DeptName DeptDescription Data Type Int nvarchar(15) nvarchar(100) Constraints Primary Key Not Null Not Null Description Identification no. of Department Name of Department Description of Department

9. Table Name : Designation_Master Primary Key : DesgId Description : Designation Details. Serial No. 1 2 3 Field Name DesgId DesgName DesgDescription Data Type Int nvarchar(15) nvarchar(100) Constraints Primary Key Not Null Not Null Description Identification no. of Designation Name of Designation Description of Designation

10. Table Name : Skill_Master Primary Key : SkillId Description : Skill Selection. Serial No. 1 2 3 Field Name SkillId SkillName SkillDescription Data Type Int nvarchar(15) nvarchar(100) Constraints Primary Key Not Null Not Null Description Identification no. of Skill Name of Skill Description of Skill

11. Table Name : Phase_Master Primary Key : PhaseId Discription : Details of Project Phase. Serial No. 1 2 3 4 Field Name PhaseId PhaseName PhaseDetail ProjectId Datatype Int nvarchar(30) nvarchar(200) Int Constraints Primary Key Not Null Not Null Not Null Description Identification no. of Phase Name Of Phase Description of Phase Identification no. of Project

12. Table Name : Leave_Master Primary Key : LeaveId Discription : Details of employee Attendance. Serial No. 1 2 3 4 5 Field Name LeaveId LeaveReason FromDate ToDate Status Datatype Int nvarchar(50) Date Date int Constraints Primary Key Not Null Not Null Not Null Not Null Description Identification no. of Leave Reason of Leave Start Date of Leave End Date of Leave Status of Leave

13. Table Name : Work_Master Primary Key : WorkId Foreign Key : ProjectId, PhaseId Discription : Details of Work that are going to be performed in Industry. Serial No. 1 2 3 4 5 Field Name WorkId WorkName WorkDetail ProjectId PhaseId Datatype Int nvarchar(30) nvarchar(50) int int Constraints Primary Key Not Null Not Null Foreign Key Foreign Key Description Identification no. of Work Name Of Work Description of Work Identification no. of Project Identification no. of Phase

14. Table Name : Project_Leader_Detail Primary Key : AllocPlId Foreign Key : PLId, ProjectId Description : Project Leader Details. Serial No. 1 2 3 Field Name AllocPlId PLId ProjectId Data Type Int nvarchar(15) nvarchar(15) Constraints Primary Key Foreign Key Foreign Key Description Identification no. of Project Leader Detail Identification no. of PL Identification no. of Project

15. Table Name : Admin Primary Key : AdminId Description : Administration Login Data. Serial No. 1 2 Field Name AdminId Password Data Type nvarchar(15) nvarchar(15) Constraints Primary Key Not Null Description Identification no. of Admin Password of Admin

16. Table Name : Work_Allocation Primary Key : WorkAllocId Foreign Key : ProjectId, PhaseId, WorkId, SkillId, EmpId Description : Work Allocation Details. Serial No. 1 2 3 4 5 6 7 8 9 Field Name WorkAllocId ProjectId PhaseId WorkId SkillId EmployeeId StartDate EndDate AllocationDate Data Type Int Int Int Int Int Int Date Date Date Constraints Primary Key Foreign Key Foreign Key Foreign Key Foreign Key Foreign Key Not Null Not Null Not Null Description Identification no. of work allocation Identification no. of Project Identification no. of Phase Identification no. of work Identification no. of skill Identification no. of Employee Start Date of Work Expected End Date of Work Allocation Date of Work

17. Table Name : Submit_Work Primary Key : SubmitWorkId Foreign Key : WorkId, Description : Work Reporting Details. Serial No. 1 2 3 4 5 Field Name SubmitWorkId WorkId WorkDesc. WorkStatus SubmitDate Datatype int Int nvarchar(200) Int Date Constraints Primary Key Foreign Key Not Null Not Null Not Null Description Identification no. of Submit work Identification no. of work Description of Work Work Status Work Submit Date

18. Table Name: Defect_Work Primary Key: DefectId Foreign Key: SubmitWorkID,WorkID Description: Defect Tracking Data.

Serial No. 1 2 3 4 5 6 7

Field Name SubmitWorkId WorkId WorkDesc. WorkStatus SubmitDate DefectID DefectDesc

Datatype int Int nvarchar(200) Int Date Int Nvarchar(200)

Constraints Foreign Key Foreign Key Not Null Not Null Not Null Primary Key Not Null

Description Identification no. of Submit work Identification no. of work Description of Work Work Status Work Submit Date Identification no. of Defect Work Description of Defect in Work

19. Table Name: Scheduling_Work Primary Key: ScheduleID Foreign Key: DefectID,WorkID Description: Rescheduled Work Information

Serial No. 1 2 3 4 5 6

Field Name DefectID WorkId WorkDesc. ScheduleID ScheduleDate WorkAllocID

Datatype int Int nvarchar(200) Int Date Int

Constraints Foreign Key Foreign Key Not Null Primary Key Not Null Not Null

Description Identification no. of Defect work Identification no. of work Description of Work Rescheduled Work ID Rescheduled Date Rescheduled Work Identification no.