Reference no: EM132783880

DWIN309 Developing Web Information Systems - Kent Institute Australia

Task - Formative Assessment

Learning Outcome 1: Develop a web-based information system using basic technologies such as mark-up languages, stylesheets, JavaScript, and databases

Learning Outcome 2: Produce relevant design, implementation and test documentation, including risk, service and change management plans

Learning Outcome 3: Critically analyse a range of software development methodologies, compare their strengths and weaknesses and have an in-depth understanding of the design process, platforms and tools for developing a web information system

Learning Outcome 4: Work effectively as part of a team in the production of a web information system and related documentation and reports

ASSESSMENT DESCRIPTION:

This assignment will be undertaken in groups of Three or Four students. Based on the project case study provided in the Assignment 2, students are required to develop and submit the project (Working Tested System) by adding extra 3 functional requirements.

In the report (support documentation), students are required to prepare a dot-point progress report considering the below points:

• The coded programs are understandable and maintainable.
• The system has been adequately tested. Sufficient and appropriate information will support the system's implementation, use and maintenance.
• Provides the required functionality
• Achieves the required non-functional objectives
• Your responses on the feedback from your Lecturer.

This project is aimed at developing an Online Banking for customer. The system is an online application that can be accessed throughout the organization and outside as well with proper login provided.

The project has been planned to have a simple MVC architecture, with a centralized storage of the database. The user interfaces have to be designed using HTML or HTML5 and CSS styling when necessary. The middleware can be developed using PHP scripts along with the SQL queries.

Following are the functional needs of the system:
• Customer must have a valid user ID and password to login to the system. (You can have a hardcoded user details to start with in the back end. Also have initial balance to start with zero)
• After the valid user logs in, the system shows the present balance in that particular account.
• Customer can perform transactions like deposit and withdrawal from his account.
• Proper help to be provided as and when requested by the customer.
• Transfer of funds to other accounts.
• Deposit of funds by the client.
• You need to keep track of all the transactions for future references as this is supposed to be show the customer as a statement.
• Faster balance enquiry.
• The system should also have another type of user who is an Administrator of the system.
• Administrator can see, add, edit and remove any customers from the banking list.
• Username and password authentication for login to the site
• So, all the above-mentioned tasks should be interacting with the Database in the backend using SQL queries along with the PHP scrips in the middleware and HTML, HTML5 and CSS for the front end.
• When a user logs out after depositing funds or transferring funds and then logs in back again, the old transactions along with the updated balance should not be lost.

According to the above project, the students in groups required to perform the following tasks to demonstrate the completion of their project and including the System Implementation Report. The final project, testing solution and the implementation of the project must include the following criteria:

1. Construction of Web Structure/User Interface

Main menu design
Page layout design

2. Structure of pages and files used in the system (MVC pattern)

3. PHP/MSQL coding with comments

4. Required functionality

5. Testing the system

6. Unit testing (testing of an individual program or module including identifying and eliminating execution errors that could the program to terminate abnormally, and logic errors that could have been missed during desk checking.

7. Documentation
Program documentation describing the inputs, outputs, and processing logic for all program modules)
System documentation (describing the system's functions and how they are implemented - e.g. Data dictionary entries, data flow diagrams, screen layout, source documentation)
User documentation (consists of instructions and information to users who will interact with the system and includes user manuals)

Attachment:- Developing Web Information Systems.rar