CT046-3.

5-2 SDM SYSTEM DEVELOPMENT METHODS

LEVEL 2

APU DEGREE

ASIA PACIFIC UNIVERSITY

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

COURSEWORK

Handout Date

: Week 4

Submission Date

:Week 14

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:

Explain the purpose, structure and scope of modern Information System Development
Methodologies and select and justify appropriate methods of analysis, design and
implementation for a particular component or application, be it traditional, multimedia or web
based.

Analyze and design different views of a system using tools and techniques.

Apply UML analysis, design and implementation techniques to develop a simple prototype,
with a suitable interface, from conception through to implementation.

Demonstrate a knowledge of the fundamental issues of prototyping by applying standard

design principles.

Case Study:
The Computer Shop

The Computer Shop is a leading Malaysia local retail and distributor for all kind of computer
accessories. They serve walk in customers in their shop located in Mid Valley Mall. They also receive
call and email orders from customers and deliver the computer accessories to their door step.
As their business grows, The Computer Shop would like to have a better management of their
inventory and relationship with the customers. The vision of The Computer Shop is to be a market
leader in the use of technology to provide the best possible customer service with the broadest range of
computer accessories.
In view of the growing request from their customers, The Computer Shop is planning to establish the
online store by Feb 2016 .Your team is assigned the project to develop the online store which will
among other standard functions, would have the following:
Scenario:

Supplier of computer accessories frequently sends list of accessories details to the store
manager. The store manager compiles a list of needed accessories and sends an order to the
suppliers. The supplier supplies the ordered accessories to the warehouse. The store manager
records the details of a new accessory, along with the number of the accessories that have
arrived in the warehouse. The store clerk updated the website with and the information of new
accessories. Invoice is sent to the accounts department to be processed and payment made.

ASIA PACIFIC UNIVERSITY

092015

CT046-3.5-2 SDM SYSTEM DEVELOPMENT METHODS

APU DEGREE
LEVEL 2
Customers who wish to purchase, need to initially register as a member. Becoming members
has their privileges such as discounts, gifts, etc. Members will be able to view the accessories,
read reviews and compare the online accessories with other similar accessories.
Members who wish to purchase can select their accessories into the websites shopping cart.
The cart will show the summary of the selection and total cost to be paid. Once the payment
is made, the customer will be able to print or save the receipts. The store will send the
accessories to the customers within 7 working days.
The system should manage information about accessories information and it should also store
information about user opinions and accessories ratings. Staff should be able to manage the
inventory of the computer accessories and manage customer delivery.
Customers can also provide feedback on the system or accessories.

Task:
Assuming you are a professional Software House, your company (group) is hired to
develop the The Computer Shop online Store 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 current business
process, overview of proposed system and your system objectives.
1.2. Problem Statement - Briefly discuss the problems of the existing systems including the
cause and the effects of it. Briefly explain your proposed solutions. You may use diagrams
to aid your explanation. Include the scope and the objectives of proposed system.
1.3. Scheduling - Create a simple Gantt chart showing your planned project scheduling
(not of this coursework). 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).
1.4. Requirement Gathering - Describe a few techniques of information gathering
(investigation or requirement gathering) that you would apply for this project. Describe
how each method would be used to collect information. Discuss the benefits and setbacks
methods chosen. Attached some sample question where applicable.
2. System Analysis
2.1. Requirement Analysis - Describe the methods that you would use to compile, analyze
and present data gathered from your investigations.
2.2. Requirement Specification List the necessary requirement that you have finalized for
the new system. Classify the requirements into functional requirements, non-functional
requirements, business requirements, user requirements, technical requirements, system
requirements, etc.
3. Initial Design
3.1. Conceptual Design Create a Use Case diagram for the proposed system. Create Use
Case Description for few of the processes (recommended one process each student).
3.2. Data Design - Create a Class Diagram for the proposed system.
3.3. Behavior Design Create a State Diagram, for any of the processes in your new system
(recommended one process each student).
ASIA PACIFIC UNIVERSITY

092015

CT046-3.5-2 SDM SYSTEM DEVELOPMENT METHODS

LEVEL 2
4. Physical Design

APU DEGREE

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 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

092015

CT046-3.5-2 SDM SYSTEM DEVELOPMENT METHODS

LEVEL 2

APU DEGREE

5. Implementation and Deployment

5.1. Testing - Suggest a few Testing Methods suitable for your system. Create a simple Test
Plan to show test areas and expected results.
5.2. System Deployment - Discuss the final steps that you would carry-out when deploying
your system. You may include a schedule to show the planned activities.

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.
6. Selection of Methodology
6.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.
6.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.
7. Project Presentation
7.1. Present your solution and suggestion including explanation of each section of your topics.
7.2. A demo of your actual prototype.
7.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 Students 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

092015

CT046-3.5-2 SDM SYSTEM DEVELOPMENT METHODS

LEVEL 2

ASIA PACIFIC UNIVERSITY

APU DEGREE

092015

CT046-3.5-2 SDM SYSTEM DEVELOPMENT METHODS

LEVEL 2
Marking Criteria
The coursework will be marked based on the following area:
Chapters

APU DEGREE

Marks Allocated

1. Project Planning
1.1. Introduction
1.2. Problem Statement
1.3. Scheduling
1.4. Requirement Elicitation

4
4
4
4

3. System Analysis
3.1. Requirement Analysis
3.2. Requirement Specification

6
6

5. Logical Design
5.1. Conceptual Design
5.2. Data Design
5.3. Conditional Control Design

6
6
6

7. Physical Design - Prototype

8. Implementation and Deployment

8.1. Testing
8.2. System Deployment

6
6

Overall Documentation

9. Selection of Methodology
10.

20

(Individual Component)
Project Presentation
(Group and Individual Component)

10

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
ASIA PACIFIC UNIVERSITY

092015

CT046-3.5-2 SDM SYSTEM DEVELOPMENT METHODS

APU DEGREE
LEVEL 2
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.
Pass (40% - 55%)
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-to-peer evaluation of individuals contribution is
poor.

ASIA PACIFIC UNIVERSITY

092015