CT046-3.5-2 SDM – SYSTEM DEVELOPMENT METHODS APU DEGREE – LEVEL 2

ASIA PACIFIC UNIVERSITY

CT046-3.5-2 SDM – SYSTEM DEVELOPMENT METHODS - APU DEGREE – LEVEL 2

COURSEWORK

Handout Date : 1 June 2015

Submission Date : 3 August 2015

PLEASE CONSIDER THE ENVIRONMENT AND DO NOT PRINT THIS DOCUMENT UNNECESSARILY. QUICK TIPS; CONVERT TO SLIDE FOR DISCUSSION or PRESENTATION, DISTRIBUTE SOFT-COPY ONLY, PRINT

DRAFT, PRINT CONTENTS ONLY, PRINT DOUBLE-SIDE, PRINT 2IN1, USE RE-CYCLED PAPERS ONLY. THANK YOU.

Learning Outcomes:

Purpose, structure and scope of a traditional methodology. Selection and justify an appropriate methodology to develop a prototype.

Analysis and develop different views of a system. Using structured analysis, design and implementation techniques to develop a simple prototype. Knowledge of fundamental issues of HCI by applying interface design principles.

Objective:

The objective of this assignment is to use structured techniques and a method such as SSADM to analyze, design and implement a system that utilizes a database. Aspect of HCI relevant to this type of system will be considered. Multimedia and Web based approaches will be discussed.

Car Park Management System

You have been approached by operators of a car park management company. The company manages a number of indoor and outdoor parking spots in the Klang Valley. The company would like to implement an internet based system to facilitate the better management of the parking operations. You are required to identify and include some of the major functions and operations. Among others, the system could be used by customers to reserve parking and make payment. The site should have a content management portal where the administrator could perform standard administrative function such as sending receipts and acknowledgement, updating parking lots, replying to enquiries and generating the necessary reports or outputs.

Note that the above descriptions are not exhaustive. Please make the necessary assumptions. Do consult your lecturers or tutors on your possible solution. You may give fictitious names to the people or organisation who are hiring you for the project.

ASIA PACIFIC UNIVERSITY 1 102014

CT046-3.5-2 SDM – SYSTEM DEVELOPMENT METHODS APU DEGREE – LEVEL 2

Task:Assuming you are a technology consultant, and your company (group) has been hired to propose a solution for the operators. You have been given the task to analyze, design and develop a prototype for the given Case Study. Your class will be divided into groups. Each group will comprise of 3 or 4 team members. Part-A (70%) is a ‘Group Component’, to be completed in a collaborative manner. Part-B (30%) is an ‘Individual Component’, to be completed by each member of the group respectively.

PART-A – GROUP COMPONENT (70%)

1. Project Planning

1.1. Introduction - This should include the introduction of the company, its business process, overview of proposed system and your system objectives.

1.2. Problem Definition - Briefly discuss the problems and/or limitations of the existing systems including the cause and the effects of it.

1.3. Proposed Solution - Briefly explain your proposed solutions. You may use diagrams to aid your explanation. Include the scope and the objectives of proposed system.

1.4. Scheduling - Create a simple Gantt chart showing your project scheduling. The stages in the Gantt chart should comply with the methodology that you have proposed for this system. (You could alternatively use the SDLC flow as well).

2. System Analysis

2.1. Requirement Elicitation - Describe a few methods of information gathering (investigation or requirement gathering) that you would use for this system. Describe how each method would be used to collect information. Discuss the benefits and setbacks methods chosen. Attached some sample question where applicable.

2.2. Requirement Analysis - Describe how you would compile, analyze and present the gathered information. Include some diagrams or tables where appropriate.

2.3. Requirement Specification – List the necessary requirement that you have finalized for the new system. Classify the requirements into different categories, for example functional requirements, non-functional requirements, business requirements, user requirements, technical requirements, system requirements, etc.

3. Logical Design

3.1. Conceptual design – Create a conceptual design diagram such as a Context Diagram or Use Case diagram for the proposed system

3.2. Process Design – Create a logical design diagram such as DFD Level-0 or a Activity diagram for the proposed system

3.3. Data Design - Create a data design diagram such as an Entity Relationship Diagram or a Class Diagram for the proposed system.

3.4. Behavior Design – Create a process definition diagram such as an Entity Life History or a State Diagram, for any of the processes in the Process Specification (e.g. Structured English, Decision Table and Decision Tree)

4. Physical Design

Prototype is a popular tool used during design for better presentation of the product. A prototype shows the main and important component of the product which could be improved according to feedbacks.

4.1. Prototype - Create a sample prototype for the above system, showing all of the main solutions that you have suggested. (NOTE: You are not required to produce a fully functional program, such as inclusion of database and online components which may be beyond the scope of this module. Any relevant development tools such as PHP, Visual.NET, Java etc are allowed).

4.2. HCI - Discuss the Human Computer Interaction (HCI) principals that you have considered and applied into creating the GUI of your prototype. Describe how this helps in making your product better.

ASIA PACIFIC UNIVERSITY 2 102014

CT046-3.5-2 SDM – SYSTEM DEVELOPMENT METHODS APU DEGREE – LEVEL 2

PART-B – INDIVIDUAL COMPONENT (30%)

This part involves individual (member) contribution to this assignment. Each member is required to choose and explain a suitable (distinctive) methodology for the project. The whole discussion should not exceed 1000 words.

5. Selection of Methodology

5.1. Select and explain a few IS development methodologies which you consider suitable to be used for this project. Compare a few methodologies for this project. Include any frameworks and/or diagrams as aid.

5.2. From your above comparison, choose a methodology and explain the purpose, structure and scope of the methodology. State the reasons for your choice. Explain in detail how your project will be developed according to the methodology stages. (group members are encouraged to select different methodology from each other). The application of the methodology should be elaborated at your the final presentation.

5.3. List the tools and techniques that are recommended within the methodology and their use in your project.

6. Project Presentation

6.1. Present your solution and suggestion including explanation of each section of your topics.

6.2. A demo of your actual prototype.

6.3. A detailed presentation of your individual component.

Assignment Deliverables and Conditions:

Final Documentation has to be word processed, printed in A4 size paper (double sided preferred) and professionally bound. The maximum of 5000 words is recommended.

Clearly separate and indicate the Group component, followed by Individual component in your documentation. Individual components need to be included with Student’s Name and TP Number.

Include a ‘Workload Matrix’, indicating the contribution of each individual for each required component (shown in percentage) and should be signed off by each team member, attached to the APPENDIX part of the final document.

Please consider the environment and don't print unnecessarily. Include all your work (copy) into an optical disk, to be attached to the documentation. This could be used to scan for plagiarism. Any additional / redundant materials that you wish to attach could also be included into the optical disk.

Citation of facts is mandatory. Obtain your facts from credible sources into references / bibliography. Avoid ‘dumping of data’. Instead the facts that you discuss should be made relevant to your case/project.

It is acceptable for discrete activities of this assignment to be undertaken by individual group members. However, it is essential that all group members understand the presentation in its entirety. At the end of the demonstration your group will be asked a series of questions to explore your understanding and analysis of the given problem.

The presentation will be conducted according to the date & time allocated to each group. Late submissions will not be assessed unless extenuating circumstances are upheld.

ASIA PACIFIC UNIVERSITY 3 102014