Module 12-5205 Web-Based Information Systems

Group Assignment

[Part 1 worked example] [Part 2 worked example] [Marking Scheme]

Information about the Assessment

Aims	· To allow you to produce an industry standard report · To enable you to consider issues in the development of a web-based information system solution. · To allow you to examine all the factors that impact on the success of a web-based integrated information system · To allow you the opportunity to present findings in a concise group report
Objectives	· Analyse an existing business system · Describe a system using the UML · Design an integrated web-based information solution · Use proprietary web-based integration technologies · Implement client and server side functionality · Financially justify your solution
Outcomes	· A report describing a proposal for a web-based information system

Introduction

You are responsible for the production of a report that describes your investigation, analysis, justification, design and implementation of a web-based information system.

You will need to make assumptions about the example organisation, and these should be clearly indicated in your report. Where information is unavailable (such as privileged information to which you do not have access), you are strongly encouraged to imagine what this information might be.

Hand-in Date

You need to ensure that you submit your work on the dates shown below. The normal regulations for the submission of late work apply available at: http://students.shu.ac.uk/rightsrules/3d.html

There are two facets of the assignment which you should be aware of:

1. You are required to hand in a paper-based report comprising each of the components described in Sections One, Two and Three.

2. You are also required to make your technical solution and financial models available on the web. You will be given your own space on a development server so that you can complete the assignment. Your web submission must be placed there.

You must also hand-in a copy of the PDP form. Assignments without PDP forms will be deemed incomplete and therefore not marked.

Section	Submission Date	Details
Group Project	16:00 Friday 5th March	CMS Reception Office

Resources

· Online Learning Materials from the WBIS website at: http://www.shu.ac.uk/schools/cms/teaching/rh1/wbis.htm

· Additional external web-based materials identified by the teaching team and yourself

· Additional reading materials as indicated throughout each of the Five Key Learning Outcomes.

· Access to the WBIS Module teaching team

· Kevin Bowman

· Richard Hill (Module Leader)

· Mo Rezai

· Dharmendra Shadija

· Paul Henderson

· Carl Davies

Assessment

You must achieve a minimum summative grade of 35% in each section of the group assessment, and you need to achieve 40% average across the whole group assessment to pass the module.

Assessment Breakdowns

You will notice that the assessment is broken down into three specific sections, which have components that you need to consider.

There are strict guidelines for the maximum length of each section of the group report. You should aim to keep within these maximum lengths, although these are an indication of the most we expect you to produce rather than a stipulation of actual length - they may be shorter if that is appropriate.

Both page and word limits are given. If you find the word limits too restrictive, remember that there are alternative ways of presenting information, such as diagrams, tables, pictures etc.

Remember that every page will be counted, excluding only the assignment submission cover sheet (yellow copy). If you exceed the limit with contents pages, bibliographies and such like you will lose marks!

Assignments that exceed the lengths specified will be penalised.

The group assessment is worth a total of 25% of the module marks.

The mark breakdowns for each section are as follows:

Submission		Breakdown (%age)
Group project	Analysis of existing business systems	25
	Technical solution	55
	Financial justification and capital expenditure plan	20

Section One: Analysis of Existing Business Systems (25%)

Using the online documentation at:

http://www.shu.ac.uk/schools/cms/teaching/rh1/elearning/uml/business_process/uml_process_improvement/business_process_qual.htm, you must produce a documented analysis of the current business system using the UML.

You must decide as a group how you will represent your analysis, bearing in mind that you must be able to communicate your ideas to a wide ranging audience. Remember that 'a picture speaks a thousand words'. Your analysis should be clearly and logically presented.

The information supplied is deliberately ambiguous. You are expected to 'fill in the gaps' by asking pertinent questions of your colleagues and the teaching staff.

Output

· A documented analysis of the existing business systems, demonstrating improvements to the model.

Maximum length

· 4 A4 sides maximum for the whole analysis section.

· 200 words maximum for the whole analysis section.

Section Two: Technical Solution (55%)

From your analysis of the existing business systems you should derive a technical solution using the existing database that will prototype your ideas.

The solution must be described using the appropriate UML notation. You should also include some screen dumps of the software working, as well as a sample report output.

Output

· Model/s to support description of proposed technical solution.

· Screen dumps and a written narrative of how the solution works.

· Sample report output.

In addition, the technical solution must be made available online using an account that you will be given. Solutions that do not work will be penalised.

Maximum length

· 7 A4 sides maximum for the whole technical solution section.

· 300 words maximum for the whole technical solution section.

Section Three: Financial Justification and Capital Expenditure Plan (20%)

You must demonstrate the financial viability of your proposal by submitting financial models to support your analysis and technical solution.

Output

• A financial evaluation of the proposed system. This must comprise the following elements:
• A description of the total costs incurred.
• A model of the benefits.
• A financial model of the cash flows, ROI, NPV, Cost/Benefit Ratio, Profitability Index and IRR.

In addition, your financial models must be made available on the same web space that you implement your technical solution.

Guideline maximum lengths

· 3 A4 sides maximum for the whole financial justification section.

· 100 words maximum for the whole financial justification section.