<Enter Team Name Here>

Feasibility Report Version <1.0> 4／9／2018

 2003 Feasibility Report

Document Control

Approval The Guidance Team and the Customer shall approve this document.

Document Change Control Initial Release: 9/12/2009 Current Release: 28/1/2008 Indicator of Last Page in Document: Date of Last Review: Date of Next Review: Target Date for Next Update:

Distribution List This following list of people shall receive a copy of this document every time a new version of this document becomes available: Guidance Team Members: Assist. Prof. Mehmet M. Kunt(Replace with your project supervisors’ name)

Clients: << Famagusta Municipality(Replace with the involved agency) >>

Software Team Members: <> <> << Team member 3>>

Change Summary The following table details changes made between versions of this document

Version Date Modifier Description

Feasibility Report Date Page 4/9/2018 12:14 下午 ii Feasibility Report

Table of Contents DOCUMENT CONTROL...... II

APPROVAL...... II DOCUMENT CHANGE CONTROL...... II DISTRIBUTION LIST...... II CHANGE SUMMARY...... II 1. INTRODUCTION...... 4

1.1. PURPOSE OF THE FEASIBILITY REPORT...... 4 1.2. PROJECT DESCRIPTION...... 4 1.3. JUSTIFICATION FOR THE PROPOSED SYSTEM...... 4 1.4. DESIRED SYSTEM FUNCTIONALITY...... 4 1.4.1. Use Case Diagram...... 4 1.4.2. Actors...... 4 1.4.3. Use Case Descriptions...... 4 1.5. USER INTERFACE DESCRIPTION...... 4 2. EXISTING SYSTEMS AND TECHNOLOGIES...... 5

2.1. <...... 5 2.1.1. Option 1...... 5 2.1.2. Option 2 … Option n...... 5 2.2. << SECOND ITEM>>...... 5 2.2.1. Option 1...... 5 2.2.2. Option 2 … Option n...... 5 3. SOLUTIONS...... 6

3.1. SOLUTION 1...... 6 3.1.1. Resources Needed...... 6 3.1.2. Limitations...... 6 3.2. SOLUTION 2...... 6 3.2.1. Resources Needed...... 6 3.2.2. Limitations...... 6 3.3. SOLUTION 3...... 6 3.3.1. Resources Needed...... 6 3.3.2. Limitations...... 6 4. CONSIDERATIONS...... 7

4.1. HEADER 1...... 7 5. RISKS AND COST ESTIMATES...... 8

5.1. RISKS AND RISK MITIGATIONS...... 8 5.2. SCHEDULE AND COST ESTIMATES...... 8 6. COMPARISON OF SOLUTIONS...... 9 7. CONCLUSIONS...... 10 8. REFERENCES...... 11

Feasibility Report Date Page 4/9/2018 12:14 下午 iii Feasibility Report

1. Introduction << BEFORE YOU BEGIN: This outline is structured in sections. To display section breaks, headers and footers, from the View menu, point to Page Layout. To add information to a chapter, insert the information before a section break to ensure it flows onto the next page properly. Information inserted after a section break disrupts the header and footer layout scheme and results in incorrect pagination. For more information about section breaks, consult Microsoft Word’s online help. >>

1.1. Purpose of the Feasibility Report << Example: The purpose of this document is to design a pavement management system for municipalities in GIS Environment >>

1.2. Project Description << Provide an overview of project. You should summarize the RDD and additional information. This should be between 1/3 of a page and a full page. You may include an appendix, if you feel that additional information is necessary. >>

1.3. Justification for the Proposed System << Example: The system provides an easy method to manage the network since funds are not enough to do such job. In addition, its cost is low since it requires only database updating from time to time, and skilled people to do this job manually are not enough >>

1.4. Desired System Functionality << This should include use case diagram, actor descriptions, and use case summaries. see below. >>

1.4.1. Use Case Diagram

1.4.2. Actors << List all actors and describe each. >>

1.4.3. Use Case Descriptions << List main use cases and describe them. It may be possible to outline the scenarios, but it is not necessary for this report for CS4310 to provide complete scenarios. >>

1.5. User Interface Description << To the extent possible, describe the desired user interface. >>

Feasibility Report Date Page 4/9/2018 12:14 下午 4 Feasibility Report

2. Existing Systems and Technologies << This section will describe systems and technologies that either achieve a solution or can be used to achieve a solution. You should describe any prototype or production system that is in place, commercial and off-the-shelf software that can be used, and open source software that might apply. Your descriptions should include software that you might use to create a solution. For example, if you require data management, you will need to discuss database management systems. If the system requires interactive graphics, you should discuss graphics packages that can be used. You should find at least two (preferably three) examples of each type of software.

2.1. < << GPS could be the first item considered since it helps >>

2.1.1. Option 1: finding coordinates of the wanted area in an easy way.

2.1.2. Option 2: gives very accurate measurements with least error.

2.2. << Second Item>>

2.2.1. Option 1

2.2.2. Option 2 … Option n

3. Solutions << Describe possible solutions. Each solution should be complete in the sense that it will fully achieve the goals of the proposed system. If your solution includes existing software, it must be described in Section 2. You must provide at least three solutions. >>

3.1. Solution 1 << Describe the solution.>>

3.1.1. Resources Needed << Include software, hardware, and training. >>

3.1.2. Limitations << If the solution does not meet all of the goals or if modifications to exiting software or hardware are needed, describe these. >>

4. Considerations << This section establishes the criteria upon which you will evaluate possible solutions. You must identify the primary concerns related to this project. You need to decide what aspects of the system are most important. Is performance something to worry about? Is usability the driving factor? Is security something for which you must plan? What features in the system matter most?>>

4.1. Header 1

5. Risks and Cost Estimates

5.1. Risks and risk mitigations << identify risks to the completion of the system. Possible risks include technical infeasibility as well as time- to-market risks. For each risk, identify possible mitigations. >>

5.2. Schedule and Cost Estimates << Provide a brief production schedule and initial cost estimates, if possible. >>

6. Comparison of Solutions << This section should discuss how each option measures up against the considerations described in Section 4 and how each compares with the others. You may choose to include some of the following: • Specific hardware and software requirements • Time constraints • Ease of use • Staffing levels and training required • User preference • Security issues A matrix that compares features is required. >>

7. Conclusions << Summary and recommendations >>

8. References << All information in the above text that comes from outside sources should be cited. All references that are cited should be enumerated below. Use IEEE citation style. >>

Feasibility Report Date Page 4/9/2018 12:14 下午 11