71
Developmental costs
Phase Item Months
Cost SEK
2 Database backend
2 3 Local client software local frontend
11 3 Onsite
GIS interface
4 3 Web interface including GIS simulation
4 6 Documentation
4 5 Data Conversion, Import and Entry
14 4 Implementation, Training and Parallel Running
12 8 Evaluation
1 Publication, Presentation, Meetings and Marketing
2 pa
Consultation with
experts 10000
Software 29800
Hardware 91000
Sum 54 130800
Annual costs pa
Operational Maintenance website, data, software hardware 2
Conferences, meetings, marketing, publications 25000
Software
¤
12000 Hardware
6000
Annual Sum 2
43000
Table 10.4. Summary of time required and projected cost for SEAD development. Developmental phases as shown in Figure 3.1, and described below.
¤
Annual software costs dependent on ESRI licensing situation
10.2.1 Skills required for development team
• A working knowledge of environmental archaeology and laboratory based scientific data. Knowledge of taxonomic systems andor geoarchaeology would be of
considerable advantage. • Experience of database development preferable using MS SQL Server or MS
Access. • Knowledge of programming in an MS Windows environment preferably object
orientated and MS VBAVB. • Advanced skills in MS Word, Excel and Access would be of considerable
advantage. • GIS knowledge, preferably including application development.
• Advanced web authoring skills, preferably including graphic design, Flash development and database access ASP skills would be advantageous.
72
10.2.2 Estimate of programming and database development time
10.2.2.1 Database backend
This planning phase document outlines the required database structure, and as such the time required for development includes only the physical construction of the data
elements and relationships and a limited set of queries. Fine tuning of this structure is inevitable during the other phases.
Approximate months required: 2
10.2.2.2 Local client software local frontend
From past experience it has been seen that, aside from the actual input of data, the development of user interfaces is one of the most time consuming components of
database system development. This is primarily due to the complex and variable nature of the data involved, and the unfamiliarity of the target users with database and in some
cases computing concepts. Development in such cases becomes as much a dialogue between the developers and the users on the possibilities of interface design, as a series
predetermined development tasks. This rings particularly true for systems with a wide and varied user base.
It is estimated that a period of at least one week per user form group is adequate, including the design and coding of interfaces, construction of underlying queries,
reports and validation checks. Fine tuning of these interfaces will be inevitable during the Implementation, Debugging and Parallel Running phase.
43 initial form groups have been identified, covering the interfaces required for the entry, retrieval and management of the data areas outlined in the database design
section 5, and shown in the structure diagrams see Appendix I for an overview. This excludes GIS and Web interfaces.
Approximate months required: 11
10.2.2.3 Onsite GIS interface
A customized ArcMAP interface integrated through MS Visual Studio to SQL Server. Approximate months required: 4
10.2.2.4 Web interface remote frontend including GIS simulation
A combination of Dreamweaver, SwishMax Flash authoring and MS Visual Studio database integration will provide the necessary tools for advanced website development.
Approximate months required: 4
