1.1. Introduction of Company: Work Order Management System

Work Order Management System
1. Introduction
1.1. Introduction of Company
Celestial Softech is a leading information technology (IT) Services Company that specializes in providing complete consulting solutions and staff augmentation to its clients. We provide on-time, on-budget and quality service to our clients and consistently meet their expectations. We are known for our superior execution on a sustained basis. Celestial Softech is a wide spectrum of IT services including Information Systems Strategy Planning, Customized Software Solutions, Packaged Software Implementation, Migration, Web Solutions, Porting and Staff Augmentation. We work with our clients to understand their business problems so that we can deliver the right solution to meet each client's needs. Celestial Softech is an information technology outsourcing and staffing company providing technical professionals ranging from help desk analysts to developers, IT professionals
1.2. Introduction of Project

Work Order Management System is Web base Android Application. As the name suggest that it is use to manage the work of assign the technician of particular company. In this System, there is two type of login either admin of Company (Company Manager) or the Technician (Employee) of that Company. If Manager is login then the application is use to manage the work order also manage the list of customer, list of technician, list of Item with list of Unit Meager Type of Item, list of service location and list of Tax authority. Also using this application manager assigns the work to technician at which place it perform. Also, If the login into application using Technician then it will show that what is the today route of work order, also they check their pending, completed, future, All work order and completed work order. The technician start their work order by initiate the start time and end with end time also they can upload the start position of work and end position of work after complete the work order.
S.V. Institute of Computer Studies, Kadi
Page 1 of 57
Work Order Management System 1.3. Proposed Timeline Chart
Page 2 of 57
2. Goals and Objective

Work Order Management System has the following goals which are selling point of it.
Goals:

Built-in "point and click" Planning and Scheduling tools. Easy to operate. Access & manage your work orders via Android. Real time job updates to office from field. Automatically records location of resource at time of job start. Transfer Employee Hours Worked to database. Update Inventory master in database with parts used.
Objective:
Create a work order master record. Identify the required information for a master record. Enter record type information for a work order. Locate a specific work order or group of work orders. Understand the work order approval process. Charge costs and hours to a work order. Set up the information necessary to use the Work Orders system. Generate management reports to track performance measures such as response time and costs. Coordinate with in-field crews on work order statuses and to receive updates on work progress.
Integrate with the Location of Work Order.
Page 3 of 57
3. Problem Definition and Project Definition

3.1. Problem Definition
In a nowadays, there is not any mobile application for Work Order Management System. The Existing system is totally Web Based mobile application. Also, This System is Official use only not for general people. It is online Work Order Management System so its must require internet connection on mobile.
3.2.
Project Definition
Word Order Management System is a totally office automation web-based Android application for Engineering service based company that handle the work order life cycle from end to end which includes Cost Estimation, Time Sheet, Service Entry and Invoice. Generate management reports to track performance measures such as response time and costs Coordinate with in-field crews on work order statuses and to receive updates on work progress Integrate with the citys GIS system
Page 4 of 57
4. System Analysis and Feasibility Study

4.1. Proposed System and Targeted Users
Proposed System:
This Android Application have main intention is that easy to manage the work order of Technician of the Company. The user perform major function on this mobile application are, Add and Update Customer Detail Add and Update Employee (Technician ) Detail Add and Update Work Order Add and Update Item Add and Update Item Unit Measure Type Add and Update Sales Person Detail Add and Update Tax Authority Show Todays Route Show Futures Work Order Show Pending Work Order Show Completed Work Order Show All Work Order
Targeted Users:
Company Manager Company Technician
Page 5 of 57
Work Order Management System 4.2. User Requirement Specification

User Requirements Specifications describes what users require from the system. User requirement specifications are written early in the validation process, typically before the system is created. It is written by the System Owner and End Users, with input from Quality Assurance. In our Work Order management system, user of our application is not general public but the users of this application is any company manager or employee, so it doesnt want to start like normal application without login. Application will start base on login of different main category (of Company Manager or Company Employee). After authorized log in depending on access they get start screen. The Company Master will be set up by Super Admin and Master User can add more info to it, if they wish or change and add users for them with proper use authorization Company Manager can insert update and delete in the list of Customer, Technician, Sales Person, Tax Authority Person, Item and also manage the work order for the Technician. While the Employee can only read their assigned work Order of todays, pending, futures, Completed also can show list of all Work Order with Ability to show present location to destination with travel or satellite map. In the work order management system the employee can only change in their work status if it will complete or not with their start time and end time. The Project shall include the following 1) Set-up multi tenant Company Master 2) Customer Master 3) Service location Master tied to Employee 4) Employee Master 5) Item Master 6) Salesman Master 7) Work performed master 8) User Master
Page 6 of 57
Work Order Management System 4.3. Feasibility Study

Preliminary investigations of system examine the project feasibility. There are three specific feasibilities are technical, operational and economical on this the project is feasible or not determined.
Technical Feasibility
Technical Feasibility means that the technology will all readly available or not? If available whether it useable? For development of the system Work Order Management System we require software like Eclipse, Android Sdk (latest version) and Java (JDK & JRE) for fulfill the different aspects of system like front end and back end. But software required as the version of Android 2.3. It is available in the company. We need not have to download the software to install in the Companys computer to fulfill the requirement.
Operational Feasibility
Operational feasibility means whether the proposed solution can fit in with operation and whether the right information at the right time is provided to the users. All the operational transactions that are going to be taken place with the system are entrusted with no much complexity. The user of the system will get the information at the time when they need it. Economical Feasibility Economic feasible means whether the finance is available for developing of the system and whether the expense is being recovered by the savings or by user satisfaction. The tools and software required for developing the project are available so there is no requirement for purchasing the tool or software. Therefore, economic balance is maintained.
The proposed project passed all the tests and was declared feasible to the organization and it is functioning.
Page 7 of 57
5. System Architecture Diagram

5.1. System Requirement Specification Hardware Specification Dual Core processor or other computable. Intel chipset motherboard. 1 GB DDR RAM. 20 GB Hard disk space. Color monitor. Keyboard and Mouse. Software Specification Operating System: windows XP and above. Development tool : Eclipse IDE Programming Tools :
android-sdk-windows
JDK and JRE Ksoap2 library Asp.net (Web Service) Microsoft Word (Documentation) Microsoft PowerPoint (Presentation) EDRAW Max 6.3 (Diagrams)
Page 8 of 57
Work Order Management System 5.2. Module Hierarchy

Definition of Module:A design segment that can be implemented as an autonomous unit, sometimes linked to produce a system.
Sub module:A module that is embedded inside another module is known as a Sub module.
Page 9 of 57
6. Diagram
6.1. Use Case Diagram
A Use case diagram in the Unified Modeling Language (UML) is a type of behavioral diagram defined by and created from aUse-case analysis. Its purpose is to present a graphical overview of the functionality provided by a system in terms of actors, their goals (represented as use cases), and any dependencies between those use cases
Use Case Diagram For Company Manager:
Page 10 of 57

Use Case Diagram for Technician:
Page 11 of 57
Work Order Management System 6.2. CRC Index Cards

CRC (Class-Responsibility-Collaborator) Card Modeling is a simple yet powerful object-oriented analysis technique. CRC modeling often includes the users, analysts, and developers in a modeling and design process, bringing together the entire development team to form a common understanding of an OO development project. It is one of many tools that should be used in the collaborative design of a system. A CRC Model is a collection of cards (usually standard index cards or larger) that are divided into three sections. 1. Class 2. Responsibility 3. Collaborator
Class Responsibility Collaborator
1. Class:A Class represents a collection of similar objects. Objects are things of interest in the system being modeled. They can be a person, place, thing, or any other concept important to the system at hand. The Class name appears across the top of the CRC card. 2. Responsibility:A Responsibility is anything that the class knows or does. These responsibilities are things that the class has knowledge about itself, or things the class can do with the knowledge it has. For example, a person class might have knowledge (and responsibility) for its name, address, and phone number. 3. Collaborator A Collaborator is another class that is used to get information for, or perform actions for the class at hand. It often works with a particular class to complete a step (or steps) in a scenario. The Collaborators of a class appear along the right side of the CRC card.
S.V. Institute of Computer Studies, Kadi Page 12 of 57

Class Name : Company Master Responsibilities It shows the List of Company Collaborators Company Type
It checks Valid Company master will login Tax Authority or not.
Class Name : Company Type Responsibilities It describe the company will come in which type Collaborators
Class Name : Customer Master Responsibilities It show the list of Customer Add and Search Customer Collaborators Company Master Sales Person Master Tax Authority Master
Class Name : Employee Master Responsibilities It describe the employee It checks Valid employee will login or not. Collaborators Company Master Employee Leave Master
Class Name : Employee Leave Master Responsibilities It describe the employee Leave type Collaborators
Page 13 of 57

Class Name : Inventory Time Spent Master Responsibilities It describe the Inventory It shows the time of employee at site. Collaborators Company Master Item Master Employee Master Work Order Master
Class Name : Item Master Responsibilities It describe the Item parts Detail . Collaborators UM Type Master Company Master
Class Name : Sales Person Master Responsibilities It describe the Sales Man Collaborators Company Master
Class Name : Service Location Master Responsibilities Collaborators
It describe the Location of Service for Customer Master employee Tax Authority Master Sales Person Master Company Master
Class Name : Tax Authority Master Responsibilities Collaborators
It describe the Tax Authority Person of Company Master particular Company
Page 14 of 57

Class Name : Work Order Master Responsibilities Collaborators
It describe the Work Order for the Customer Master employee for which purpose. Also it show the work order of particular Sales Person Master employee with time and schedule date Company Master Service Location Master
Page 15 of 57
Work Order Management System 6.3. Class Diagram

A Class diagram shows a set of classes, interfaces, and collaboration and their relationships. Class diagram are the most common diagram found in modeling object-oriented systems. You use class diagram to illustrate the static design view of system. Class Diagram include active classes are used to address the static process view of system.
Page 16 of 57
Work Order Management System 6.4. State Transition Diagram

A state chart diagram shows a state machine; emphasizing the flow of control from state to state. A state machine is a behavior that specifies the sequences of state an object goes through during its lifetime in response to events. State chart diagrams may be attached to class, use case, or entire system in order to visualize, specify, construct, and documents the dynamics of individual object. A state represents a stage in the behavior pattern of an object, and like UML activity diagrams it is possible to have initial states and final states
Page 17 of 57
Work Order Management System 6.5. Sequence Diagram

A sequence diagram represents the interaction between different objects in the system. The important aspect of sequence diagram is that it is time oriented. This means that the exact sequence of the interaction between the objects is represented step by step. Different objects in the sequence diagram interact with each other by passing Messages.
Manager:
Page 18 of 57

Technician:
Page 19 of 57
6.6.
Activity Diagram
Activity diagrams are graphical representations of workflows of stepwise
activities and actions with support for choice, iteration and concurrency. In the Unified Modeling Language, activity diagrams can be used to describe the business and operational step-by-step workflows of components in a system. An activity diagram shows the overall flow of control.
Manager
Page 20 of 57

Employee
Page 21 of 57
7. Software Design
7.1. ER Diagram
An entity-relationship (ER) diagram is a specialized graphic that illustrates the interrelationships between entities in a database. ER diagrams often use symbols to represent three different types of information. Boxes are commonly used to represent entities. Diamonds are normally used to represent relationships and ovals are used to represent attributes.
Page 22 of 57
7.2.
Field Name C_Id(P.K) C_Password C_Name C_Add C_Phone C_Email
Data Dictionary
Class Name: Company Master Data Type Integer(5) Varchar(8) Char(20) Varchar(30) Integer(12) Varchar(15) Integer(5) Integer(5) Boolean Discription Id of Company Password of Company Name of Company Address of company Contact Number of Company Email address of company Company type Company Tax Payers Id Company will activate or not
C_TypeId(F.k) C_TaxPayerId (F.k) C_IsActive
Class Name: Customer Master Field Name CustId(P.K) CustName CustAdd CustPhone CustEmail SalesPersId (F.K.) TaxId (F.K.) CustIsActive C_Id(F.K.) Data Type Integer(5) Char(20) Varchar(30) Integer(12) Varchar2(20) Integer(5) Integer(5) Boolean Integer(5) Discription Id of Customer Name of Customer Address of Customer Contact Number of Customer Email address of Customer Company type Company Tax Payers Id Company will activate or not Id of Company
Page 23 of 57

Class Name: Employee Master Field Name EmpId(P.K) EmpPassword EmpName EmpAdd EmpPhone Data Type Integer(5) Varchar(8) Char(20) Varchar(30) Integer(12) Discription Id of Employee Password Of Employee Name of Employee Address of Employee Contact Number of Employee EmpEmail EmpSkill EmpRPH EmpRpOT Varchar(20) Char(10) Integer(3) Integer(3) Email address of Employee Skill of Employee Rate of Employee work Rate of Employee work for Over Time EmpIsActive C_Id(F.K.) LeaveId(F.K.) Boolean Integer(5) Integer(5) Employee will activate or not Id of Company Id of Employee Leave Master
Class Name: Employee Leave Master Field Name LeaveID LeaveType Data Type Integer(5) Char(10) Discription Id of Leave Type Name of Leave Type
Class Name: Company Type Field Name ComTypeId ComTypeName Data Type Integer(5) Char(10) Discription Id of Company Type Name of Company Type
Page 24 of 57

Class Name: Inventory Time Spent Master Field Name InventoryId(P.K) WOId(F.K) InvDate EmpId(F.K) FromTime Data Type Integer(5) Integer(5) Date Integer(5) Date Discription Id of Inventory Id of Work Order Date of Inventory Id of Employee Contact Number of Employee ToTime TimeSpent Rate Amount Date Integer(3) Float(5,2) Float(8,2) Email address of Employee Skill of Employee Rate of Employee work Rate of Employee work for Over Time C_Id(F.K.) PartId(F.K.) Integer(5) Integer(5) Id of Company Id of Item Part
Class Name: Item Master Field Name PartId(P.K) PartName UM_TypeId(F.K) Price C_Id(F.K) Description Data Type Integer(5) Char(15) Integer(5) Float(5,2) Integer(5) Char(20) Discription Id of Item Part Name of Item Part UM type of Item Price of Item Id of Company Description of Item Part
Page 25 of 57

Class Name: Sales Person Master Field Name SalePersId(P.K) SalesPersName SalesPersAdd SalesPersPhone SalesPersEmail Data Type Integer(5) Char(30) Varchar(30) Integer(12) Varchar(20) Discription Id of Sales Person Id Name of Sales Person Address of Sales Person Sales Person Phone Email address of Sales Person SalesPersIsActive C_ID(F.k) Boolean Integer(5) Sales person is active or not Company id
Class Name: Service Location Master Field Name ServLocId(P.K) CustId(F.k) ServLocName ServLocAdd TaxId(F.k) SalesPersId(F.K) ServLocsIsActive Data Type Integer(5) Integer(5) Char(30) Varchar2(30) Integer(5) Integer(5) Boolean Discription Id of Service Locition Id of Customer Name of Service Location Service location Address Id of Tax Id of Sales Person Service location is active or not C_ID(F.k) Integer(5) Email address of Employee
Class Name: UM Type Master Field Name UMTypeId(P.K) UMName Data Type Integer(5) Char(10) Discription Id of Item UM Type Name of Item UM Type
Page 26 of 57

Class Name: Tax Authority Master Field Name TaxId(P.K) T_Name TaxPer TaxIsActive C_Id(F.K) Data Type Integer(5) Char(5) Float(4,2) Boolean Integer(5) Discription Id of Tax Name of Tax Percentage of Tax Is active or not Tax Id of Company
Class Name: Work Order Master Field Name WOId(P.K) CustId(F.k) ServLocId(F.K) CustComp SalesPersId(F.k) ScheDate ArriveSiteAt LeftSiteFrom WOIsBillable BillAmount Data Type Integer(5) Integer(5) Integer(5) Char(30) Integer(5) Date Varchar(6) Varchar(6) Boolean Float(5,2) Discription Id of Work order Id of Customer Name of Service Location Customer Complain Id of Sales Person Date of Work order Schedule Arrive at Service location Left at Service location Work order is billable or not If billable then amount of bill to pay WorkPerf C_ID(F.k) Char(30) Integer(5) Status of work order Email address of Employee
Page 27 of 57
8. GUI Screens and User Manual

8.1. Screen Shots
[ Login Screen ]
[ Layout For Company Manager ]
Page 28 of 57
[ List of The Company Customer ]
[ Update Customer Detail ]

[ Choose Sales Person for Customer ]
[ Choose Tax Authority of Customer ]

[ Add New Coustomer ]
[ Service Location of Customer ]
Page 31 of 57
[ Selected Service Location for Update or Change ]
[ List of Work Order with corresponding status ]

[ Selected Work order Detail ]
[ Time log of Work order ]
Page 33 of 57
[ Add Time of Particular work order ]
[ List of Item Inventory for work order ]
Page 34 of 57
[ Add New Item for work order in item Inventory ]
[ Add New Technician in the Company ]
Page 35 of 57
[ List of Technician of the Company ]
[ All work order which will sort by Technician and work order status ]
Page 36 of 57
[ Select Technician for sort work order (same as for work order status )]
[ List of Item ]
Page 37 of 57
[ Update Item for the list of Item ]
[ Add New Unit Masour Type for Item ]
Page 38 of 57
[ List of all Unit Masour for the Item ]
[ Add New Sales Person for the Company ]
Page 39 of 57
[ List of Sales Person of the Company ]
[ Add New Tax Authority of the Company ]
Page 40 of 57
[ List of All the Tax Authority of the Company ]
[ Layout for The Technician of The Company ]

[ All Work Order of the Technician ]
[ Selected Work Order from the List ]

[ Add Photo image before start work and after end of the work ]
[ Confirmation Massage for Log out from the Application ]
Page 43 of 57
8.2.
Navigation Chart
Page 44 of 57
9. Test Cases
9.1. Login
Purpose
Expected result:
Login successfully with valid User Name and password message display login successfully otherwise display error message display.
Actual result:
Login successfully with valid email and password. Pre-requirement Test data Steps Notes
Connect with internet And Registered User. Validation of User Name and password (1) Enter User Name and password
(2) Click on login button.
Review : Success Action Required : Not Required
9.2. Add and Update Customer
Purpose
Expected result:
Add or Update successfully with valid Customer name, add, Service location, phone Number Massage display successfully otherwise display error message display.
Actual result:
Add and Update successfully Customer Pre-requirement Test data Steps
Connect with internet And Registered User Can Change. Validation of Customer Name, add, Service Location, phone Number and etc... (1) Enter Customer Name, add, Service Location, phone Number and etc...
(2) Click on Save button.
Notes
9.3. Update Work Order Detail


Purpose
Expected result:
Add or Update successfully with valid work order From time to To time , work performed massage, wo status, bill y/n, bill amount .Massage display successfully otherwise display error message display.
Actual result: Update Work order Detail Successfully

Pre-requirement Test data Steps
Connect with internet And Registered User Can Change. Validation of work order From time to To time , work performed massage, wo status, bill y/n, bill amount etc... (1) Enter work order From time to To time , work performed massage, wo status, bill y/n, bill amount etc...
Notes
9.4. Update Inventory of Work Order
Purpose
Expected result:
Add or Update successfully with valid Work order No., Date, Item name, Qty, Item Price, Comment, Massage display successfully otherwise display error message display.
Actual result:
Pre-requirement Test data Steps Notes
Update Item Inventory of Work order Successfully Connect with internet And Registered User. Validation of Work order No., Date, Item name, Qty, Item Price (1) Enter Work order No., Date, Item name, Qty, Item Price
Page 46 of 57
Work Order Management System 9.5. Add and Update Technician
Purpose
Expected result:
Add & Update successfully with valid Technician Name, add, Skill, Rate per hr, Working day, email id, U name and password. The message display Add and Update successfully otherwise display error message display.
Actual result:
Add or Update successfully with Technician Detail. Pre-requirement Test data
Connect with internet And Registered User. Validation of Technician Name, add, Skill, Rate per hr, Working day,
email id, U name and password
Steps
(1) Enter Technician Name, add, Skill, Rate per hr, Working day, email id,
U name and password (2) Click on Save button.
Notes
9.6. Add and Update Tax Authority
Purpose
Expected result:
Add & Update successfully with valid Tax Authority Name and Tax %. The message display Add or Update successfully otherwise display error message display.
Actual result:
Add or Update Successfully with Tax Authority detail Pre-requirement Test data Steps Notes
Connect with internet And Registered User. Validation of Tax Authority Name and Tax %. (1) Enter Tax Authority Name and Tax %
Page 47 of 57
Work Order Management System 9.7. Add and Update Salesman

Purpose
Expected result:
Login successfully with valid Salesman Name, Add, phone number and email id message display Add or Update successfully otherwise display error message display.
Actual result:
Add Or Update Successfully with valid Salesman Detail Pre-requirement Test data Steps Notes
Connect with internet And Registered User. Validation of Salesman Name, Add, phone number and email id. (1) Enter Salesman Name, Add, phone number and email id
9.8. Add Time of Work Order

Purpose
Expected result:
Add successfully with valid Work orders No, date, Technician, From Time, To Time message display login successfully otherwise display error message display.
Actual result:
Add successfully with valid Work orders Time Detail. Pre-requirement Test data Steps Notes
Connect with internet And Registered User. Validation of Work orders No, date, Technician, From Time, To Time (1) Enter Work orders No, date, Technician, From Time, To Time
Page 48 of 57
10. Future Enhancements

In future additional functionality such as GPS are added in this Work Order Management System. Current Work Order Management system cannot be available on internet. So, users have to manipulate this system where it is installed and used. The application will be available for Android Mobile users & After Developing for the iphone and Black Berry Mobile also.
Page 49 of 57
11. References
Websites.
www.google.com stackoverflow.com code.google.com www.mobilemancer.com www.learn-android.com sarangasl.blogspot.in www.vogella.de www.c-sharpcorner.com java.dzone.com tips4android.blogspot.in brainflush.wordpress.com www.firstdroid.com
Page 50 of 57
12. Appendix
12.1. About Software Tools Used
Google Android What is Android? Android is a software platform and operating system for mobile devices, based on the Linux kernel, developed by Google and Open Handset Alliance. It allows developers to write managed code in the Java language, controlling the device via Google-developed Java libraries. Applications written in C and other languages can be compiled to ARM native code and run, but this development path isn't officially supported by Google.
The unveiling of the Android platform on 5 November 2007 was announced with the founding of the Open Handset Alliance, a consortium of number of hardware, software, and telecom companies devoted to advancing open standards for mobile devices. Google released most of the Android code under the Apache license, a free-software and open source license.
Features
Handset Layouts: The platform is adaptable to larger, VGA, 2D graphics library, 3D graphics library based on OpenGL ES 1.0 specifications, and traditional Smartphone layouts. Storage: The Database Software SQLite is used for data storage purposes.
Page 51 of 57

Connectivity: Android supports connectivity technologies including GSM/EDGE, CDMA, EV-DO, UMTS, Bluetooth, and Wi-Fi. Messaging: SMS and MMS are available forms of messaging including threaded text messaging. Web Browser: The web browser available in Android is based on the open-source WebKit application framework. Dalvik Virtual Machine: Software written in Java can be compiled into Dalvik bytecodes and executed in the Dalvik virtual machine, which is a specialized VM implementation designed for mobile device use, although not technically a standard Java Virtual Machine. Media Support: Android will support audio/video/still media formats such as MPEG-4, H.264, MP3, AAC, OGG, AMR, JPEG, PNG, and GIF. Additional Hardware Support: Android can utilize video/still cameras, touch screens, GPS, accelerometers, and accelerated 3D graphics.
Page 52 of 57

Development Environment: Includes a device emulator, tools for debugging, memory and performance profiling, a plug-in for the Eclipse IDE. Market: Main article: Android Market Similar to the App Store on the iPhone, The Android Market is a catalog of applications that can be downloaded and installed to target hardware over-theair, without the use of a PC. Originally only freeware applications were supported. Paid-for apps have been available on Android Market since 19 February 2009. Multi-touch: Android has native support for multi-touch but disable this feature as a result of Apple's request. An unofficial mod has been discovered that enables multitouch.
Page 53 of 57
Work Order Management System Eclipse

Eclipse Galileo is a collection of plug-ins built on top of the Eclipse framework and packaged into what is called an "extension". An extension is a collection of plug-ins, separated into their own directory, and hooked into your Eclipse install by way of the Eclipse extension mechanism. Because of the size of Eclipse Galileo (~190 plug-ins as of Nov, 2009) it wouldn't make sense to ask our users to install so many plug-ins into their base Eclipse installation. Additionally, but keeping all the Eclipse plug-ins separate of the Eclipse install, is it easy to install/update and uninstall MyEclipse without affecting the base Eclipse install.
Plugins used for Google Android: Android-sdk-windows-2.0 ADT-0.9.6
Page 54 of 57
Work Order Management System 12.2. Terms and Glossary
WOMS is a Mobile Application. This manage work order of Technician. Extensible Markup Language (XML) is a markup language that defines a set of rules for encoding documents in a format that is both humanreadable and machine-readable.
XML
3 4 5 6 7 8 9
Customer Technician Item Item UM Type Sales Person Tax Authority Todays Route
Customer of Particular Company Technician(Employee) Particular Company Item which is provide by the company Item Unit Maser Type for Item Sales person of Company Tax Authority of Company It is navigate The Technician, On which way they have work order
10
Future
This is indicate that which work order is handle by them in future.
11
Pending
This is indicate that which work order is Pending og Technician.
12 13
All WO Completed
Give list of all work order assign to Technician. Give List of Work order completed by Technician
Page 55 of 57
Work Order Management System 12.3.

Convention
File names should use proper letters only. File name should be same as that of the class in that file. File name should have first letter capital in every consecutive word. All code and text files should be completely free from TAB character. All indentation must be done with space.
File Naming Conventions
Creating the source code We have added comments for each and every line of code that we have made. We have added description of each and every function and their attributes and parameters. Separate the consecutive methods with some -character line. General coding standards It is acceptable to break up long statements on to multiple lines or leave it in one long line. Do not put multiple statements in one line. Every coding block must be indented. The standard indentation is three spaces. The use of white space and simple comments is strongly encouraged. All the functions, variables and constants have to be declared on the top of the file in particular form. Identifier Standard Identifiers are formed from the letters A-Z, a-z, digits 0-9 and underscore. Case sensitive, so count and COUNT are different identifiers. Identifier always starts with small letter. Constants are shown as capitol letters only. Reserved words are all over the lower case and may not be used as identifiers. Comments in java can be added in number of ways. For single line put // and for multiple lines use /* and to end the comment -->. Naming Conventions
Comment Standard */
For putting comments in XML files we have to use <!-- to start comment

Naming conventions make programs more understandable by making them easier to read. They can also give information about the function of identifier.
Identifier type Methods
Rules of Naming
Example
Methods should be verb; in mixed e.g. getSchdule() case with the first letter of the verb should be lower case. And after that every first letter of consecutive word should be upper case.
Variables
All the variables should be in e.g. Schdule_id upper case letters. It should not start with _ or $ characters. It must start with upper case letter.
Constants
The names of variable declared e.g. YEAR which are constants must be in upper case letter
XML Naming Rules
XML elements must follow these naming rules:
An XML element is everything from (including) the element's start tag to (including) the element's end tag.
Names can contain letters, numbers, and other characters Names cannot start with a number or punctuation character Names cannot start with the letters xml (or XML, or Xml, etc) Names cannot contain spaces
Any name can be used, no words are reserved.
Page 57 of 57

1.1. Introduction of Company: Work Order Management System

Загружено:

Сведения о документе

Исходное описание:

Оригинальное название

Авторское право

Доступные форматы

Поделиться этим документом

Поделиться или встроить документ

Параметры публикации

Этот документ был вам полезен?

Это неприемлемый материал?

Авторское право:

Доступные форматы

1.1. Introduction of Company: Work Order Management System

Загружено:

Авторское право:

Доступные форматы

Work Order Management System

1.2. Introduction of Project

S.V. Institute of Computer Studies, Kadi

Work Order Management System 1.3. Proposed Timeline Chart

S.V. Institute of Computer Studies, Kadi

Work Order Management System

2. Goals and Objective

Integrate with the Location of Work Order.

S.V. Institute of Computer Studies, Kadi

Work Order Management System

3. Problem Definition and Project Definition

S.V. Institute of Computer Studies, Kadi

Work Order Management System

4. System Analysis and Feasibility Study

S.V. Institute of Computer Studies, Kadi

Work Order Management System 4.2. User Requirement Specification

S.V. Institute of Computer Studies, Kadi

Work Order Management System 4.3. Feasibility Study

S.V. Institute of Computer Studies, Kadi

Work Order Management System

5. System Architecture Diagram

S.V. Institute of Computer Studies, Kadi

Work Order Management System 5.2. Module Hierarchy

S.V. Institute of Computer Studies, Kadi

Work Order Management System

Use Case Diagram For Company Manager:

S.V. Institute of Computer Studies, Kadi

Work Order Management System

S.V. Institute of Computer Studies, Kadi

Work Order Management System 6.2. CRC Index Cards

Class Responsibility Collaborator

Work Order Management System

It checks Valid Company master will login Tax Authority or not.

S.V. Institute of Computer Studies, Kadi

Work Order Management System

Class Name : Service Location Master Responsibilities Collaborators

Class Name : Tax Authority Master Responsibilities Collaborators

It describe the Tax Authority Person of Company Master particular Company

S.V. Institute of Computer Studies, Kadi

Work Order Management System

S.V. Institute of Computer Studies, Kadi

Work Order Management System 6.3. Class Diagram

S.V. Institute of Computer Studies, Kadi

Work Order Management System 6.4. State Transition Diagram

S.V. Institute of Computer Studies, Kadi

Work Order Management System 6.5. Sequence Diagram

S.V. Institute of Computer Studies, Kadi

Work Order Management System

S.V. Institute of Computer Studies, Kadi

Work Order Management System

S.V. Institute of Computer Studies, Kadi

Work Order Management System

S.V. Institute of Computer Studies, Kadi

Work Order Management System

S.V. Institute of Computer Studies, Kadi

Work Order Management System

C_TypeId(F.k) C_TaxPayerId (F.k) C_IsActive

S.V. Institute of Computer Studies, Kadi

Work Order Management System

S.V. Institute of Computer Studies, Kadi

Work Order Management System

S.V. Institute of Computer Studies, Kadi