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

Nov 2014

Submission Date

Feb 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.
Case Study:
APUs E-Bookstore
The availability of books and reading material for purchase within the Asia Pacific University (APU)
is quite inadequate. Although the APU library have vast collection of books (both hardcopy and ebooks), the availability of it is quite limited and bound by many restrictions. Student and staffs
only have the options of a small book shop within the enterprise. Larger books store in the city
are often sorted for other varieties.
In view of the growing population within APU, the university is planning to establish an ebookstore. The online store will facilitate the purchase of latest books and material of many
genres. Your team is assigned the project to develop the online APUs e-Bookstore System. The
system, among other standard functions, would have the following:

Scenario:

Publishers of books frequently send list of latest books and materials to the e-bookstore
manager. The store manager compiles a list of needed books and sends an order to the
suppliers. The supplier supplies the ordered books to the warehouse. The store manager
records the details of a new book, along with the number of the books that have arrived in the
warehouse. The store clerk updated the website with and the information of new materials.
Invoice is sent to the accounts department to be processed and payment made.
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 book, read
reviews and compare the online products with other similar articles.

ASIA PACIFIC UNIVERSITY

102014

CT046-3.5-2 SDM SYSTEM DEVELOPMENT METHODS

APU DEGREE
LEVEL 2
Members who wish to purchase can select their books 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 books to
the customers within 7 working days.
The system should manage information about books in the bookstore, inventory, (registered)
customers and books they have ordered. It should also store information about user opinions
and book ratings.
Users can also provide 'feedback' for a book, as a score (1-10 which is 0= terrible, 10=
masterpiece) along with optional short text. Users can also rate other users' feedback as
'useless', 'useful', 'very useful'. The bookstores staffs are also allowed to declare other users
as 'trusted' or 'not-trusted', based on customers track records. No changes are allowed; only
one feedback per user per book is allowed.
Task:
Assuming you are a professional Software House, your company (group) is hired to
develop the APUs E-Bookstore. 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 system 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. 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 the methods that you would use to compile, analyze and
present data. Include some sample diagrams or table that you would use for this purpose.
2.3. 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. 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.
ASIA PACIFIC UNIVERSITY

102014

CT046-3.5-2 SDM SYSTEM DEVELOPMENT METHODS

APU DEGREE
LEVEL 2
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 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).
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.

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

ASIA PACIFIC UNIVERSITY

102014

CT046-3.5-2 SDM SYSTEM DEVELOPMENT METHODS

APU DEGREE
LEVEL 2
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

102014

CT046-3.5-2 SDM SYSTEM DEVELOPMENT METHODS

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

Marks Allocated

1. Project Planning
1.1. Introduction
1.2. Problem Definition
1.3. Proposed Solution
1.4. Scheduling
3. System Analysis
3.1. Requirement Elicitation
3.2. Requirement Analysis
3.3. Requirement Specification
5. Logical Design
5.1. Conceptual Design
5.2. Process Design
5.3. Data Design
5.4. Conditional Control Design
7. Physical Design
7.1. Prototype
7.2. Interface Design

3
3
3
6
6
3
5
6
6
6
5
8
5

Overall Documentation

8. Selection of Methodology
9.

APU DEGREE

20

(Individual Component)
Project Presentation
(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
address most issues with regards to not only their own component of the module but also be
ASIA PACIFIC UNIVERSITY

102014

CT046-3.5-2 SDM SYSTEM DEVELOPMENT METHODS

APU DEGREE
LEVEL 2
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

102014

CT046-3.5-2 SDM SYSTEM DEVELOPMENT METHODS

LEVEL 2
Sample Workload Matrix
(The original spreadsheet version could be obtained from Webspace2)

APU DEGREE

ASIA PACIFIC UNIVERSITY

CE00046-3-2 SDM SYSTEM DEVELOPMENT METHODS
Student Coursework Workload Matrics - Grades and Feedback Attachment
INTAKE: UC2FXXXXX
STUDEN
T
NAME

PROJECT TITLE
APU E-Bookstore

TP NO.

John

TP9906464

A. Group
Component
NO

ASSINMENT
COMPONENT

ALLOCAT
ED
MARKS

CONTRIBUT
ION
PERCENTAG
E

CONTRIBUT
ION
PERCENTAG
E

CONTRIBUT
ION
PERCENTAG
E

CONTRIBUT
ION
PERCENTAG
E

TOTAL
%

Project Planning

15

System Analysis

14

Logical Design

23

Physical Design

13

A.

Overall
Documentation

Total Marks and

Contribution

70

0%

0%

0%

0%

Signatur
e

ASIA PACIFIC UNIVERSITY

102014