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
73
10.2.3 Documentation
i Inline documentation of database and code – included in programming database construction time.
ii Application web help files iii User Guide
iv Detailed operational and maintenance manual
Approximate months required: 4
10.2.4 Data Conversion, Import and Entry
The most time consuming single component of the SEAD database development. See section 4 for details of the relative volumes data and complexity of tasks involved.
Approximate months required: 14
10.2.5 Implementation, Training and Parallel Running
Close contact with MAL staff and partner researchers will be essential in activating SEAD. The estimate includes time for MAL staff and external cooperation partners to
interact with the developers. MAL staff, who will initially be the primary data managers will need to be instructed on the use of SEAD. They will also form the primary test
population.
Approximate months required: 12
10.2.6 Evaluation
SEAD will undergo a fully documented evaluation on completion. Approximate months per year required: 1
10.2.7 Operational Maintenance data, software and hardware
A certain degree of maintenance, as outlined in section 5.9, will be required to keep SEAD running. One day a week should be an absolute minimum for a database manager
and administrator. This will not include data entry or any major redevelopments or enhancements. This figure should be increased should the scope and cooperation base of
SEAD be increased.
Approximate months per year required: 2
10.2.8 Publication, Presentation, Meetings and Marketing
It is suggested that time be allocated for the preparation of presentations and marketing material in order to promote awareness of SEAD. This will be a combination of website
promotion, brochure distribution and poster presentation. Meetings, both internal and with external partners will be required during the entire
developmental phase.
74 Developer time should also be allocated to provide close support with those preparing
and writing up research which implements SEAD. The developers will also be required to write papers concerning the construction and workings of SEAD as outlined in the
publication strategy in section 9.1. Conference participation, and the associated material production is included in this
unit.
Approximate material and logistic costs: 1 international conference per year for two people: 20000 Kryr
Review meetings at 6 monthly intervals: 5000 Kryr will increase if more external partners involved
Approximate months required: Writing publications, brochures posters: 2 months
10.3 Commercial Potential
SEAD will most probably be a commercially viable product and service. There are, however, currently no plans to realize its commercial potential as this is regarded as
detrimental to the principles of academic freedom and open access. The physical presence of, and the experience gained during the development of SEAD
will greatly enhance MAL’s national and international research status and competitiveness and will thus lead greater possibilities for attracting funding and
research to Umeå University.
Kategori