CE00046-3-2 SDM SYSTEM DEVELOPMENT METHODS

SU DEGREE LEVEL 2

ASIA PACIFIC UNIVERSITY SU DEGREE LEVEL 2 CE00046-3-2 SDM SYSTEM DEVELOPMENT METHODS COURSEWORK
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.

Case Study: The Coursework Management System (CMS) for APU An Academic Coursework is a set of tasks given to a student or group, which needed to be completed and submitted to the faculty in order to fulfill the requirement and achievement of academic qualification. At Asia Pacific University (APU), a form titled Coursework Submission and Feedback Form (dubbed CSFF), is used to officially monitor the development and the completion of each coursework. The form contains all the necessary attributes pertaining to the course, including grades achieved and feedbacks from instructors to the students at the end of the course. Currently all data relating to the coursework are manually stored in paper folders and spreadsheets. As number of student increases, the management of APU wishes to establish a comprehensive Information System to manage the coursework efficiently. The new system, dubbed Coursework Management System (CMS) is a database enabled, intranet based system which is planned to be made available in the Webspace 2 at the end of the quarter. CMS can be used to manage, maintain and secure the facultys assignment preparation, setting marking criteria, results and feedbacks across the schools. This components and features of system are further described below: The University maintains 3 main faculties: Engineering, Computing and Business & Management. Each faculty is further divided as clusters, example: Computing faculty has Application cluster, ICT cluster and Interactive cluster. Each cluster is assigned several modules conducted at the university. Each lecturer at APU is assigned to one or more modules at a time to lecture. For example Mr. Raj and Ms. Cindy can be assigned to lecture DWDS for different batch of students at the same time. Each module is also managed by a Module Leader. The module is in charge of updating the module information. For instance, Mrs. Smith of Application clusters lectures three (3) modules: Object Oriented Programming (OOP) and Systems Analysis and Design (SAD) and Visual Basic (VB). At the same time, Mrs. Smith is the module owner of Systems Analysis and Design (SAD) and Visual Basic (VB).

ASIA PACIFIC UNIVERSITY

042013

CE00046-3-2 SDM SYSTEM DEVELOPMENT METHODS

SU DEGREE LEVEL 2

Scenario: 1) In any given day, a Faculty Administrator may create a new course on CMS. The course will also contain all the modules that will be offered through the academic year. 2) The module leaders then will update their respective modules with further information such as coursework percentage, individual or group work, etc. 3) The delegated lecturers would be able to upload new coursework specification (question) into the CMS, along with some vital information such as due-date and specific criteria. 4) Students are to download the assignment and complete it as per instruction. Competed assignment need to be printed and submitted to the Exam Unit Staff. Upon receiving, the Exam Unit staffs would key in the date of document received accordingly into CMS. 5) The lecturer will then collect the coursework and mark it based or the some standard criteria as shown below: a) The weight of each Coursework (i.e.: 100%, 50%, 25%) b) Group or Individual Coursework. (If group, then the coursework may be further divided to show percentage of individual contribution within it). c) Feedback or comments for the students about the coursework. d) Marks and Grades according to the following criteria.
Distinction A+: 80% A: 75-79% Credit B+: 70-74% B: 65-69%, Pass C: 55-64%, D: 50-54% Marginal Fail F+: 40-49%, Fail F: 0-39%

6) Upon completion of marking, the Exam Unit Staff will prepare the final result to be published in the CMS. 7) Students could view their assignment grade as they login into the system. Each student should be able to view their grades according to criteria and view the feedback (remarks) given by their lecturers. They would not be able to view other students grade or their group members grade. 8) Students marks are kept confidential and only lecturers and Exam Unit Staff are able to view them.

ASIA PACIFIC UNIVERSITY

042013

CE00046-3-2 SDM SYSTEM DEVELOPMENT METHODS

SU DEGREE LEVEL 2

Task 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 2 or 3 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 project objectives. 1.2. Problem Definition - Briefly discuss the problems 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. Discuss the benefits and setbacks methods chosen 2.2. Requirement Analysis - Describe the methods that you would use to analyze the collected data. 2.3. Requirement Specification List the necessary requirement that you have finalized for the new system. 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 a 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 4.1. Prototype - Create a simple 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. Visual Basic is the recommended programming environment. Other tools such as Delphi, PowerBuilder, Visual Caf, PHP and etc are allowed.

ASIA PACIFIC UNIVERSITY

042013

CE00046-3-2 SDM SYSTEM DEVELOPMENT METHODS

SU DEGREE LEVEL 2

4.2. HCI - Discuss the Human Computer Interaction (HCI) principals that you have considered and applied into creating the GUI of your prototype.

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 800 words.

5. Selection of Methodology 5.1. Compare a few suitable IS development methodology for this project. State the reasons for your choice. 5.2. Explain the purpose, structure and scope of the methodology. Include any frameworks and/or diagrams as aid. 5.3. Choose a methodology and explain in detail how your project will be developed according to the methodology stages. Include the tools and techniques that are recommended within the methodology and their use in your project. 5.4. The application of the methodology should be elaborated at your the final presentation.

Project Presentation Present your solution and suggestion including explanation of each section of your topics. A demo of your actual prototype. A detailed presentation of your individual component.

Assignment Deliverables and Conditions: Clearly separate and indicate the Group component and Individual component in your documentation. 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. 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 could also be included into the optical disk. Include the list of references / bibliography and appendices where necessary. 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. 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

042013

CE00046-3-2 SDM SYSTEM DEVELOPMENT METHODS

SU DEGREE LEVEL 2

Marking Criteria The coursework will be marked based on the following area: Chapters 1. Project Planning 1.1. Introduction 1.2. Problem Definition 1.3. Proposed Solution 1.4. Scheduling 2. System Analysis 2.1. Requirement Elicitation 2.2. Requirement Analysis 2.3. Requirement Specification 3. Logical Design 3.1. Conceptual Design 3.2. Process Design 3.3. Data Design 4. Physical Design 4.1. Prototype 4.2. HCI 5. Selection of Methodology (Individual Component) 6. Assignment Presentation (Individual Component) 7. Overall Documentation Marks Allocated

4 5 5 4 5 5 5 5 5 5 7 5 20 10 5

Performance Criteria
Distinction (70% and above) This grade will be assigned to work where the documentation is complete and describes in detail, with little or no errors, the following components: introduction, feasibility study, usage of SDLC, selection and application of investigation techniques and analysis / logical design in accordance with excellent documentation standards. To obtain this grade, the candidates individual assignment should show all techniques of process applied with little or no errors. All deliverables of the individual component should be coherent with detailed description to explain the diagrams. Overall documentation standards for both the group project as well as the individual assignment should be of excellent quality. In order to obtain a grade at this level, individuals should be able to address all issues with regards to not only their own component of the module but also be those of the other group members. Individuals contribution to the project, at this level should be more than 75% and overall peer evaluation should indicate excellent standards. Credit (56% 69%) This grade will be assigned to work where the documentation is complete and describes briefly, with some errors, the following components: introduction, feasibility study, selection and application of investigation techniques and analysis / logical design in accordance with good documentation standards. To obtain this grade, the candidates individual assignment should show all techniques of methodology applied but some errors. All deliverables of the individual component should be coherent with detailed description to explain the diagrams. Overall documentation standards for both the group project as well as the individual assignment should be of excellent quality. In order to obtain a grade at this level, individuals should be able to address most issues with regards to not only their own component of the module but also be those of the other group members. Individuals contribution to the project, at this level should be more than 65% and overall peer evaluation should indicate excellent standards.
ASIA PACIFIC UNIVERSITY 5 042013

CE00046-3-2 SDM SYSTEM DEVELOPMENT METHODS Pass (40% - 55%)

SU DEGREE LEVEL 2

This grade will be assigned to work where, most of the basic requirements of the documentation listed above, such as introduction, feasibility reports, logical process models, data dictionary are of adequate standard which is evident in the hardcopy of the documentation. The physical design of the system in terms of the interactive screen design and report maps adequately against the logical design presented in the documentation. The documentation should be of adequate standard in terms of language, layout and flow. Some accurate, relevant and up-to-date referencing was visible. Group presentation of the team should have adequate visual aids with relevant information presented and adequate coordination among group members. Individuals should display an adequate level of professionalism and project knowledge. Peer-to-peer evaluation of individuals contribution should be adequate.

Fail (Below 40%) This grade will be assigned to work where, most of the basic requirements of the documentation listed above, such as introduction, feasibility reports, logical process models, data dictionary are of poor standard which is evident in the hardcopy of the documentation. The physical design of the system in terms of the interactive screen design and report shows little or no mapping / linking with the logical design presented in the documentation. The documentation is of poor standard in terms of language, layout and flow. Minimal or no referencing was done. Group presentation of the team has poor visual aids with irrelevant information presented and poor coordination among group members. Individuals display on the average a poor level of professionalism and project knowledge. Peer-topeer evaluation of individuals contribution is poor.

End.

ASIA PACIFIC UNIVERSITY

042013