Assignment - Prototype website

  • Posted
  • Proposals 0
  • Remote
  • #1732
  • Expired
  • 0


Experience Level: Expert
This is a University assignment at Masters level. The task is to build a website, using technology, that employs a database or persistent XML. The database should be capable of shared access i.e. the system should use a server-side database management system e.g. sql*server or XML equivalent. The focus of assessment is on technical competence and not specific functionality of the web site. Therefore a discourse of your own may be used. However, the site must- be an application (i.e. uses the .net runtime and class library)

Reusable components and source may be employed. This development must respect all copyright and acknowledge the scope, source and employment of any acquired components (with the exception of the .net class library). There must be a clear demarcation between acquired components and your own work. All components must include configuration management data including authorship claims, and this data should appear on the user interface where possible. All components must be portable.

The following is offered as guidance for the discourse, and can be used as a discourse for the assessment.

The system may use XML and associated technology, or normal database technology, or both. Data concerning the documents may be manipulated using normal database representations and mechanisms, or as XML/XSD.

The web application must make significant use of classes from the following namespaces


The data source must contain at least five related entities with a minimum of 25 attributes in total.

The application should be styled using Master Page, Theme, Skin(s) and CSS as appropriate


An application that manages landscape image data is required.

Basic image data includes date image captured, line of sight (compass direction camera pointing in degrees 0-360, North is 0), horizon width (positive decimal measured in km), photographer details, date and time the image was captured or created, and location of the file containing the image.

Location is recorded in two ways.

1. 6 figure grid reference e.g. NZ 145 567
2. latitude (positive north of the equator, negative south, from %u201390 to 90, 0 on equator) and longitude (positive east of the Greenwich meridian, negative west, from %u2013180 to 180, 0 on meridian). Each is held in two forms
%u2022 as degrees (integer), minutes (integer), and seconds (double)
%u2022 as a decimal (double) representation.

As an example, a longitude of 122 degrees 45 minutes 45 seconds East is equal to 122.7625 degrees East.

The relationship between the decimal representation and angular representation is
Decimal value = Degrees (Minutes/60) (Seconds/3600)

Photographers create the images. The image will have a date and a copyright owner. The photographer may be a member of a team or acting as an individual. The photographer may be a member of a number of teams. The teams have unique names. The image is of a type e.g. monochrome, sepia, abstract, realist. An image may be produced (owned) by the team or individual.

An image may be a montage of other images. The images that make up the montage must be recorded. In this case the montage will have no location but the images making up the montage will. A montage may be composed of montages, or a mix of montages and individual images.

You may make any assumptions you wish, but an assumption must not contradict anything in the discourse.

Incremental Delivery strategy
Gradually build up the capability of the application and deploy for testing after each version (i.e. v1.1,1.2%u2026%u2026.v2.1, v2.2%u2026)
Basic data manipulation (Version 1)
1. System to persistently hold basic image, location and photographer data.
2. User interface to browse data.
3. User interface to add, update and remove data.
4. Styling of application.
Visual representation of data (Version 2)
1. Capability to display the locations of images on a map.
2. Capability to add notes to the image data and map.
3. Capability to display image and image data via a map location, date/times and direction angle
4. Capability to define a mapping area and display images in that area that match specified criteria.

Note: Do not use or submit any live (copyright) data. Use invented example data.

Gateway Application and Source Submission
The development of this web application should be viewed as part of a larger web site. This website will be titled 'YWA Showcase' and be known as the Gateway website. Your web application (or at least a version of it) should be portable to this Gateway website.

The Gateway application will be owned and managed by the tutor and hosted in a single application directory on iis server %u2018scm-2003%u2019. Contributions to the Gateway application will be made electronically, and incrementally. At the end of each stage of application building i.e. before final submission, a contribution should be made to the Gateway i.e. to the tutor, using a shared file system, e-mail, or CD. This will act as a means of testing the quality of the application in terms of portability and reliability, and enable an incremental approach to implementation and delivery.

A progress matrix will be available which will provide information on these contributions and if they have been successfully integrated into the Gateway. Submission will be in the form of 'source' that can be 'built' to produce a target application. The tutor will build the application in the context of the Gateway project.

All source code should be supplied on CD with instructions to build the application and how to access it on the Gateway site.

Assessment Criteria

1. Quality of the database schema (or persistent structures) 25 marks
i.e. a formal, portable description of the persistent data structure inc. relationships, and integrity constraints. Quality is concerned with how well the description covers the semantics drawn from the discourse, the amount of detail covered, and the intelligibility and portability of the description.

2. Quality of the data manipulation operations on the database (or persistent structures) 25 marks
i.e. how easily persistent structures can be changed and configured, operations on the metadata, the ease and flexibility with regard to updates of content, how easily operations can be modified to take account of structure changes.

3. Quality of the user interface design and implementation 25 marks
i.e. ease-of-use, ease-of-change, degree of customisation to user requirements, security considerations, maintainability of styling rules, consistency

4. Quality of functionality, ease of application building and integration with the Gateway 25 marks
i.e. portability, sharability and configuration management of the application. System capability (quantity and quality of relevant functions)

Clarification Board

    There are no clarification messages.