MODULAR PROGRAMME

ASSESSMENT

SPECIFICATIONModule DetailsModule Code Run Module TitleUFCFB3-30-1 17OCT/1 ay Web Programming

Module Leader Module TutorsMazhar Hussain Malik Mazhar Hussain Malik

Component and Element Number Weighting: (% of the Module's assessment)A 70%

Element Description Total Assignment timeGroup Demo and Presentation 24 hours

DatesDate Issued to Students Date to be Returned to05 December 2017 Students

Submission Place Submission Date5th January 2018

P.8 Submission Time

1.00 pmDeliverablesReport with CD which includes:

An integrated web system with source code in ZIP file (using e.g., 7Zip). This should contain all the files and folders for the full working website. All programme files must have group ID and student name who has written the code.

Relevant Database (e.g. MySQL or MariaDB or MongoDB) dump. A word document that includes names and student ids of all group members. This document should

also provide a very basic guide (or instructions) about how to setup their website for testing including any test usernames and passwords. Suitable test data should also be provided to test the website functionality.

A presentation in MS PowerPoint (if you are working in Linux these slides can be in PDF format).

All above four items can be submitted in one ZIP file. The naming standard of the zip file is WP1234567.zip where 1234567 is the student Id of a member of the group.

ONE submission per group but you MUST include a student number for each member of your group, within the report and the web site (i.e. programs or scripts).

Module Leader SignatureMazhar Hussain Malik

Web Programming

UFCFB3-30-1

Semester Project

CLASS PROJECT

As a part of the class, groups of 2 students will implement a semester-long project. An open-ended class project complements the traditional lecture-and-exam format of this course. While exams rigorously assess your conceptual understanding, the project allows you to hone your pragmatic Web programming skills, to practice project management, and to express your creativity.

Each group has to choose a topic from the list (See suggested topics) and create a web application for it.

REQUIREMENTS

Students should be able to create a CRUD (Create Read Update and Delete) web application using HTML, CSS, Java Script and PHP with Db connectivity. Students will identify the requirements in their initial proposal using MoSCoW method. Web application should have responsive UI, LESP, system architecture need to clearly define and implemented. Students will secure Bonus marks if they are able to implement bonus requirements.

GROUPS

You need to form a group of 2 students. All members will collectively submit a single copy of all milestones and receive a single grade. It's your responsibility to divide up the work fairly amongst members. The staff will not intervene in intra-group conflicts.

MILESTONES

To provide some structure to this semester-long endeavour, we have provided three graded milestones. For each milestone, you must submit a PDF report documenting your progress. For legibility, use an 11-point or larger standard font with at least 1-inch margins.

Designate one group member to submit all project reports, and include all of your group members' names and your email addresses on it. Also, pick a (tasteful) team or project name so that we can easily identify your group.

When you submit your PDF file, put all of your group members' names in the filename so that the staff can easily identify the creator of each PDF file by glancing at the filename. e.g., if your group is John and Jane, then you can turn in a file named "Milestone 1 - John and Jane.pdf"

(If your designated group member can't make the deadline for whatever reason, it's OK for someone else in the group to submit. But remember that deadlines are final; no extensions.)

FINAL DELIVERABLES

A Project Report in hard copy as per guidelines with Standard top sheet. Report will contain a CD which should have soft copy of the report, complete code

and ppt slides.

CD should contain the following:

1. An integrated web system with source code in ZIP file (using e.g., 7Zip). This should contain all the files and folders for the full working website. All programme files must have group ID and student name who has written the code.

2. Relevant Database (e.g. MySQL) dump.

3. A word document that includes names and student ids of all group members. This document should also provide a very basic guide (or instructions) about how to setup their website for testing

including any test usernames and passwords. Suitable test data should also be provided to test the website functionality.

4. A presentation in MS PowerPoint.

Project Milestone 1: Due at 13:00 on December 11, 2017

By this milestone, you need to turn in a one-page project proposal. Your project's details will likely change throughout the semester, but it's important to have some starting point. Your proposal must address these questions:

Who is the target audience for your Web application? [Stretch goal: Identify a target audience that none of your group members belong to.]

What problem is it intended to solve? Explain chosen topic initially understand requirements using MoSCoW method which you

need to cater and additional requirements can be added after initial proposal review.

We understand that this milestone comes early in the semester before you've learned much in this course. But in many real-world projects, you must often start designing and prototyping before you're fully aware of the constraints. The staff will be available in lab and office hours to answer your questions about project proposals and to work with you to refine your ideas.

Don't forget to put your team or project name on your proposal and if we think your proposal needs to be amended, then we will give you feedback in lab on after a week.

Project Milestone 2: Due at 13:00 on Dec 17, 2017

By this milestones, you need to lay out and design all the pages and forms (Validation checks and Db connectivity will be done later.

At this stage, students will be able to define layout and design. (can use diagram design tools e.g Visio) to understand and show that how many web pages and forms needed and each page/form will contain which type of data.

Each group will submit the Milestone 2 on due date in hardcopy and feedback will be provided with in a week.

Project Milestone 3 and final report: Due at 13:00 on Jan 5 2018

By this milestone, you should implement complete functionality:

Application should have attractive and well-designed web pages related with chosen area. Web application should have administrator and normal user account to get access. There

should a sign up page to create account and after getting permission, user should able to get log in and perform tasks.

CRUD operations need to be implemented and submitted for demonstration.

Project Presentation: Due at 10:00 on Jan 07, 2018

Your group will do a 15-minute presentation during the final week of class. Your whole group comes to the front of the class.

You need to bring your laptop for demo. You step me through using your Web app on your laptop to demonstrate all of its main

functionality. Time expires after 15 minutes, and the next group comes up!

A sample ppt template will be shared with students and group should have the following slides.

Slide 1 will be title slide will contain project title and group information In slides 2 and 3 you give a brief introduction to the motivation behind your project. e.g.,

what problem are you trying to solve? Who is your target audience? Slide 4 will be based on Functional and non functional requirements of the project. Slide 5 and 6 will be based on design and implementation information. Slide 7 and 8 will be related with project Testing.

FREQUENTLY ASKED QUESTIONS

Q: Can I re-use or extend parts of a project that I created before this class began?

A: No, you must start a new Web application from scratch.

Q: What happens to my code after the class ends?

A: It's yours to keep. Make sure you save a backup copy on your own computer, though, since we cannot rely on Web hosting services to preserve your data indefinitely. We encourage you to think creatively about how your project can extend into a larger, more ambitious project in the future.

Q: Can I change my project idea after submitting the initial proposal?

A: Definitely! But please go over changes with your TA to make sure they approve and are aware of your changes. And do not make any changes that would make your project either out of scope (i.e., not a CRUD Web app) or contain any inappropriate content.

Q. How I can score maximum marks?

A: Marks distribution criteria is shown at the end of the assignment under Grading criteria heading.

Suggested Topic

Blood Bank Management System

Employees Payroll Management System

Library Management System

Design and Implementation Requirements

Blood Bank Management System

Blood Bank Management system will contain some basic information related with Blood bank and

CRUD operations need to apply by keeping in mind the following actors along with the types of

action which they can perform.

ADMIN:-

• Manage Registration for user• Manage Blood bank information like (update, delete)• Manage Donor Request for Donor• Manage patient Request for needy people• Manage Inquiry form for Appropriate Reply• Manage feedback for Appropriate Reply Blood bank information view/update View Donor information Manage Patient Blood Request.

DONOR:-

• Manage Donor information(profile)• Add new Donation for Blood

PATIENT:-

• Manage patient information(profile)• Give the Request for patient for blood

Employees Payroll Management System

Employees Management system will contain some basic information related with Blood bank and

CRUD operations need to apply by keeping in mind the following actors along with the types of

action which they can perform.

Registration of user

• View employees• Generate payslip• Generate Reports• Show Payslip• Show Reports

Admin

• Login• Manage Employee• Generate Repots.• Generate Pay slip.• View Employee• Logout Employee Payroll System.

Manager

• Login• Show Reports• Logout

Employee

• Login• Show pay slip• Logout

Library Management System

Requirements for The Librarian

1.Add Book

New entries must be entered in database

2.Update Update

Any changes in articles should be updated in case of update3.

Delete Book

Wrong entry must be removed from system

4.Inquiry Members

Inquiry all current enrolled members to view their details

5.Inquiry Issuance

Inquiry all database articles6.

Check out Book

To issue any article must be checked out

7.CheckInBook

After receiving any article system will re-enter article by Checking

8.Inquiry waiting for approvals

Librarian will generate all newly application which is in waiting list

9.ReserveBook

This use case is used to reserve any book with the name of librarian, it can be pledged10.

Set user Permission

From this user case Librarian can give permission categorically, also enabling/disabling of user permission can be set through this use case

MEMBER

1.Authentication

User must be authenticated before accessing system

2.Search Book

User can search any article

3.RequestBook

After successful searching member mark this book as requested article

4.Check Account

This use case is used to check account details

Guest

1.Register user

User must 8ulfil all application form for registration

Web Project Student Checklist (Tick the relevant option)

1. Navigation ComplianceAlways Sometimes Never

There is a clear indication of the current locationThere is a clearly-identified link to the Home pageAll major parts of the site are accessible from the Home pageSite structure is simple, with no unnecessary levelsIf necessary an easy to use search function is available

2. Functionality ComplianceAlways Sometimes Never

All functionality is clearly labelledAll necessary functionality is available without leaving the site

3. Control ComplianceAlways Sometimes Never

The user can cancel all operationsThere is a clear exit point on every pageAll graphics links are available as textual linksThe site support the user flowsThe site support all browsersLanguage Compliance

Always Sometimes Never

The language used is simple4. Feedback Compliance

Always Sometimes NeverIf necessary, online help is availableIt is always clear what is happening on the siteUsers can receive email feedback if necessaryUsers can give feedback via email or a feedback form

5. Consistency ComplianceAlways Sometimes Never

Only one word or term is used to describe any itemLinks match titles of the pages to which they referStandard colours are used for links and visited linksTerminology is consistent with general web usage

6. Error prevention and correction ComplianceAlways Sometimes Never

Errors do not occur unnecessarilyError message is in plain languageError messages describe what action is necessaryError messages provide a clear exit pointError messages provide contact details for assistance

7. Visual clarity ComplianceAlways Sometimes Never

The layout is clearAll images have ALT text assignedUnnecessary animation is avoided

Grading Criteria

Assessment mark sheet

<END>