Information Systems 1 64665371.

doc INFORMATION SYSTEMS I PROJECT: 2011

Project Specification: HTML PROJECT

A. Purpose:
The purpose of this project is diagnostic and for grading purposes and will contribute 10% towards the final mark for Information Systems I. The areas being tested are: Problem solving logic Design skills Report writing skills Presentation skills Project management skills Basic Web site design principles HTML and web Design skills However, individuals that go beyond the prescribed text and incorporate concepts, which were not covered during the taught component of the subject, will attract high marks. The Web design component (web design tool being used) is a selflearning portion, where students are welcome to use any software tool like FirstPage, Dreamweaver, etc

B.

Scenario:

You have completed your first year studies at the University of Technology and your desire to become an entrepreneur has sparked off the idea to start your own small software development company. To cut cost initially, you have decided to run the business entirely on your own. One of the tasks in your marketing strategy is to attract clients by creating a Project Team Profile. Each individual project team must plan, analyze, design and create a basic web site that represents the following: Web Design and Project Management knowledge and skills. Ability to collaborate on a team project.

The web site should consist of the following: A Home Page introducing the Project Team. The following information must be included: Created/Adapted Project Team Logo. Project Team vision and mission statement. Goals/objectives of Project Team in relation to IS1. Link from HOME PAGE to a Project Team Page including: All the team members. Their specific roles/duties in relation to this project. A photo of each member. Each team member's name to link to their individual profile page see below. A Profile Page for EACH member of the Project Team. The following information (data fields) must be included for each profile:

Page

Information Systems 1 64665371.doc

Photo Name(s) & Surname Facebook Profile URL Student Number Date of Birth Gender Age Own a car? eMail address Brief description of yourself {at least 50 words} Likes {at least 5} Dislikes {at least 5} Hobbies {at least 3} Description of contribution to this project. From the HOME PAGE create a Content Page briefly summarizing ONE feature/principle (per group) related to Web Design. Include the appropriate citation and referencing in the Harvard format. Find at least three (3) references. Length should be at least about 400 words. From the HOME PAGE create a Summary Page describing what the team learned from this project. {At least about 100 words}.

C.

What is expected of you

This project is a group undertaking, under no circumstances can a students work on his/ her own. Marks will be awarded as follows: D. Group Work

Each group is expected to carefully study the scenario given above and meet the deadlines set. Each group should consist of 4 members per group. Groups should be from the same class group. (If not, marks will not be allocated to the group. Once group names are submitted no changes will be accepted.). Groups are to be allocated via blackboard. All students should already be in project teams! There might be some changes to the current project teams, i.e. All project teams MUST be finalized by 5 August 2011 on the blackboard system. All students that are not part of a Project Team will be automatically assigned to a project team by the Subject Coordinator/lecturers. Each Project Team shall consist of of 4 members. NO CHANGES WILL BE CONSIDERED TO PROJECT TEAMS AFTER the 5 August 2011.

E.

Resources: Own creative genius. Software (e.g. 1st Page, MS Office XP, etc.). Traditional Textbooks (e.g. In the library). Journal articles / Magazine articles. Web sites (e.g. Results from Search Engines).

Page

Information Systems 1 64665371.doc E.

Newspapers. Interviews Etc.

Project Presentation Each group will present their project to their lecturers. Each group will be given a maximum of 10 minutes to present their project.

F.

Activity Log
A detailed Log, which includes dates and purposes of meetings held, activities assigned to each member with due dates and completed tasks. Evidence must be shown that each member made an equal contribution to the development of the project. The Project Plan should include the project Objectives and Gantt Chart (Tasks, Schedule & Deadlines) Note: Any evidence of research beyond the prescribed reading will attract a high mark.

G.

What to hand-in:
You are required to have a printed copy of documentation including Activity log prior to presentation. All projects to be uploaded on blackboard. All students to hand in their project at the presentation on CD. Make sure the website runs from this CD. Please note: A completed bound copy of all documentation and activity log is required at the presentation. No mark will be allocated if the documentation is not handed in before the presentation. Gantt Chart User manual (Screen shots etc.)

H.

Due Dates:
See individual subject requirements attached The penalty for late submission is a mark of zero. If you have a valid reason for late submission, you should ask for an extension (supported by written or certified evidence) in advance of the due date if possible.

I.

Viruses:
Ensure that you are protected as far as possible against virus attack by retaining at least two backup copies of your work. Please ensure that your disk(s) are virus free. A disk submitted that contains a virus will result in a mark of zero.

J.

Plagiarism:
These subjects are based on continuous assessment. Any attempt to obtain a pass by unfair means is therefore very serious. Any cases of copying the work of others will result in zero marks for the copier and also for the supplier if this was done knowingly. After working in the computer labs at

Page

Information Systems 1 64665371.doc the Institution, ensure that you clear all relevant project files from the computer's hard disk. Do not simply copy information, images, etc. from Web pages or other sources!!! This information might be copyrighted and using this information as is without permission of the owner is plagiarism. K. The Project Specifications MAY CHANGE Refer back to this document on a regular basis!!!

Project Presentation and hand-in Project presentations will take place in practical classes refer to your lecturer for presentation dates

Project Management (Activity Log and Gantt chart)

A detailed Log, which includes dates and purposes of meetings held, activities assigned to each member with due dates and completed tasks. Evidence must be shown that each member made an equal contribution to the development of the project. Note: Any evidence of research beyond the prescribed reading will attract a high mark.

L.

Due Dates:
Group Work: all websites and documentation should be submitted. Project Presentation: As per lecturer due dates check blackboard for updates (Please check the notice boards regularly for presentation schedules.)

M.

Evaluation Criteria
Students should demonstrate the ability to: Plan the project; Analyse the problem and break it down into a manageable set of tasks; Design the website; Implement the solution; Test and evaluate the effectiveness of the solution and refine as necessary; Communicate the solution in appropriate ways.

Rubrics per Submission: Activity Log and Gantt Chart [30%] Performance Indicators Criteria Poor [0] Significantly lacks details. Does not provide a clear and useful summary of activities. Needs Accomplished Improvement [1] [2-3] Some isolated and unrelated details provided. Needs significant improvement. Adequate log that provides some useful and clear details. A basic summary of activities. Exceptional [4-5] Exceptionally detailed log that provides a useful and clear summary of activities.

General

Page

Information Systems 1 64665371.doc

5.2.7 Web site Presentation [70%]

Performance Indicators Criteria Poor [0] Needs Improvement [2]

Satisfactory [3]
Demonstrates a basic awareness of designing a solid foundation for a web site. "Bells and whistles" distract some of the focus in the design. Average example of simplicity in design. Satisfactory design and some evidence of a coherent whole. Some evidence of inconsistencies that break down the harmonious whole. An average demonstration of knowledge, skills and application of the web design principles. Adequate utilization of images an colour. Most images display. The usage of images and colour is somewhat functional. Provides an adequate visual effect. Demonstrates very average

Accomplished [4]

Exceptional [5]

Basic Web Site?

Little awareness Requirements requirements. not adhered to. Lacks solid Lacks solid foundation for a foundation. web site. "Bells "Bells and and whistles" whistles" play a prominent. Poor significant role. example of Inadequate simplicity in example of design. simplicity in design. Little evidence of coherent design. Needs significant improvement. Evidence of major inconsistencies that break down the harmony as a whole. Little demonstration of knowledge, skills and application of the web design principles.

Good awareness of requirements. Relative solid foundation. Minor focus on "bells and whistles". Good example of simplicity in design.

Strong awareness of requirements. Well designed foundation. Very little focus on "bells and whistles". Excellent example of simplicity in design.

Poorly designed. No evidence of any coherent design. The use of various web Coherent Style elements is totally inconsistent and creates a very fragmented site. Poor demonstration of knowledge, Appropriate for skills and purpose application of the web design principles.

Good design and evidence of a coherent whole. Some minor inconsistencies are present that limit the establishment of a harmonious whole. A Good demonstration of knowledge, skills and application of the web design principles.

Well designed and coherent whole. The use of the various web site elements is consistent and creates a harmonious whole. An excellent demonstration of knowledge, skills and application of the web design principles. Efficient utilization of images and colour. All images display. The usage of images and colour is highly functional. Provides an excellent visual effect. Demonstrates some excellent

Images and Colour

Inadequate utilization of Poor utilization images an of images and colour. Most colour. Many images do images do not display. The display. The usage of usage of images and images and colour display colour is not little functional. functionality. Provides a poor Provides an visual effect. inadequate visual effect. Demonstrates no originality. Demonstrates very little

Good utilization of images an colour. All images display. The usage of images and colour is mostly functional. Provides a good visual effect.

Originality of Web site

Demonstrates some good

Page

Information Systems 1 64665371.doc

Images and text demonstrate no creativity and effort. Plagiarism strongly in evidence.

originality. Images and text demonstrate very little creativity and effort.

originality. Just another web site. Images and text demonstrate little creativity and effort.

original ideas that raises the site over the average. Images and text demonstrate some creativity and effort.

original ideas that make the site stand out. Images and text demonstrate creativity and effort.

Performance Indicators Criteria Poor [0] Needs Improvement [3] Very little application of design principles. The page design needs a lot of improvement in order to be visually pleasing, to support the page content to an extent, and to be appropriate for its intended audience. HTML code still tends to be confusing, redundant and not commented. The utilization of all web components displays little functionality. The navigation needs a lot of improvement. The site is not well organized and not easy to navigate. The relationship between pages is confusing and it's not easy to find an individual page. Each Satisfactory [5] Average application of design principles. The page design tends to be average in terms of visually impact, supporting the page content, and it's appropriatenes s for the intended audience. HTML code shows some evidence of clarity, conciseness and is sparsely commented. The utilization of all web components displays average functionality. The site is somewhat organized and easy to navigate. The relationship between pages is adequate but can be improved. Some pages are clearly linked to others. Links are Accomplishe d [7] Exceptional [10]

Design Principles and HTML

Poor application of design principles. The page design is not visually pleasing, does not support the page content, and is inappropriate for its intended audience. HTML code is confusing, redundant and not commented. The utilization of all web components displays no functionality.

Good application of design principles. The page design tends to be somewhat visually pleasing, generally supports the page content, and is mostly appropriate for its intended audience. HTML code is clear, concise and commented. The utilization of all web components displays good functionality.

Exceptional application of design principles. The page design is visually pleasing, supports the page content, and is appropriate for its intended audience. HTML code is clear, concise and well commented. The utilization of all web components is highly functional.

Well-structured navigation

The site is poorly organized and difficult to navigate. The relationship between pages is unclear and it's difficult to find an individual page. Each page is not clearly linked to another.

The site is well organized and relatively easy to navigate. The relationship between pages is relatively clear and it's generally easy to find an individual page. Most pages are clearly linked

The site is exceptionally organized and easy to navigate. The relationship between pages is clear and it's easy to find an individual page. Each page is clearly linked to another. Links are

Page

Information Systems 1 64665371.doc

page is not clearly linked to another. Links are not Links are appropriate inappropriate and not clearly and mostly not labelled. Links clearly do not have a labelled. Links definite do not have a purpose. Most definite links are purpose. Large broken. portions of the links are broken.

satisfactory and show some clarity in their labels. Links do show some purpose. Small portions of the links are broken.

to one another. Links are mostly appropriate and clearly labelled. Links mostly have a definite purpose. One or two links are broken.

appropriate and clearly labelled. Links have a definite purpose. All links work.

Page