Corporate organisations often want to implement some of the functionality of Web 2.0 sites to build an Enterprise 2.0 Intranet.
Your task is to develop an ASP.NET version of a staff Microblogging site (similar to twitter, tumblr, posterous, etc.). The site must store and use data from an Access database that you design. The site must be a secure site with two types of users: General Users and System Administrators.
Unauthenticated users of the “outward facing” web site must be able to see the organisation’s staff and department lists, and the Microblog entries marked as Public.
General Users must be able to create their own accounts, change their own passwords and have individual profiles. Users are organised into departments (eg Human Resources, Accounts, Marketing, IT Support). They will only appear listed on the outward facing web site when they have been authorised by the System Administrator, who also attaches them to departments.
Once registered they must be able to use their own Microblog account, with each entry being added at the top of their page with the date and time of posting clearly visible. Each entry must be restricted to 200 characters (including spaces). Users should be able to edit their own entries, but not anyone else’s. They can comment on other entries. By default all entries are Private to the company, but authenticated users can change their own entries to Public at any time which has the effect of making them visible on the outward facing web site.
You only need to develop a small number of ASP.NET pages that use data from a MS Access database, including
• A list of departments (coming from the database). Selecting a department will give a list of all the staff in the department. Selecting a member of staff gives full details of the person, including all their Public Microblog entries.
• A list of staff in alphabetical order by surname, with a link to their full details.
• All Microblog entries by all users in reverse order by date posted, paginated 10 per page
• Option to include or exclude comments in the listings.
System Administrators have all the above functionality. They are all in the IT Support Department. They also need pages with the following functionality that no one else can access:
• Add, edit and delete departments, but departments with staff should not be able to be deleted (to preserve referential integrity).
• Authenticate new users
• Attach staff to departments, or remove them from departments.
• Change the status of a user from General User to System Administrator
• View a list of new user, with easy links to authenticate them.
In addition, your site will be assessed for interface design, usability and accessibility features. It will also be assessed on whether it meets the client's requirements.
The site can be hosted on Localhost.
1. A formal report in PDF format containing:
• Title page, including the usernames and passwords needed to test the site.
• Table of Contents
• Overview of your site with images showing sample pages to prove the requirements have been met.
• An image of your Relationship Diagram from Access
• A list of the validation of input that is implemented
• Evidence of site design (eg wireframe models)
• Evidence that can be used to assess your sites for interface design, usability, accessibility and to determine whether they meet the client's requirements. This needs to be in the form of a test plan and test log. You need to ensure you have added sufficient data to fully test the site.
2. A ZIP file of your entire site, including the database.
The report and ZIP file must be uploaded by the due date.
A demonstration of your system to your tutor is required at a time to be notified.
Quality and completeness of the report 10%
Database implementation, including sufficient quantity of data 10%
General User pages, including validation 20%
System Administrator pages, including security 20%
Test plan and test log 10%
Interface design, usability and accessibility 10%
Weekly uploads 20%
A professional report showing a high level of competence in the use of Internet and Intranet technologies. Demonstrates a clear understanding of the processes involved in evaluating and developing a complex data-driven web site and intranet.
A well-written report showing competent use of Internet and Intranet technologies and demonstrating some understanding of the processes involved in developing a complex data-driven web site and intranet.
A poorly written report demonstrating little understanding of Internet and Intranet technologies.