SCB2053/SDB1123 SAD June 2014|Page 1

Semester MAY 2014

SCB2053/SDB1123 Project Final Due Date: Week 12 (5 August 2014)

Marks: 15% of total Course work marks

Instructions

For this project you are required to form a group of 6 students.

This project is divided into TWO phases with two different submission dates as written

below (refer to Phase 1 and Phase 2). You are expected to submit your detail final work

during Week 12 (8 August 2014).

Phase 1: Identification of Organization and System Request

(Deadline: 27 June 2014: Friday)

Total Marks: 25 marks

Objectives:

The objectives of this phase are to understand the organization business functions and

propose the potential project to overcome the problem or to improve the business values.

Students also will be experienced in conducting the feasibility study for the project prior

to the project execution and implementation.

Tasks:

For this phase, your group is required to propose a new or an update system. The system

maybe a totally new system or upgrade the existing system. Working with your teammates,

- if the system is a new system, justify your idea, why you need to develop the system.

- If you plan to do the upgrade system, research any problem that you are aware of with the selected information system of the chosen organizations business function. Then, think on improvement for the current problem by proposing a

suitable, potential information system project.

For both option, develop a system request for the propose system after identifying the

business value of the project. Next, conduct a feasibility study for the project.

Phase 1 Deliverables:

For this Phase 1, you are required to submit the following documents:

1. Organization background and the selected business function 10 marks 2. System Request 5 marks 3. Feasibility Study Report Technical, Economic and Organizational feasibility of

the propose project 10 marks

SCB2053/SDB1123 SAD June 2014|Page 2

Phase 2: Project Analysis and Design

(Deadline: 8August 2014 : Friday)

Total Marks: 100 marks

Objectives:

The main objective of this project is to give students an experience in doing analysis

for System Development Life Cycle process. Among others, the students will

experience the project management tasks for the project and involve in the analysis

phase activities. These included gathering requirements using variety of techniques,

analyzing the requirements that were gathered and developing various type of modeling

that are necessary for the system development.

Tasks:

For this phase, your group is required to use the findings from phase 1 where we will move

to the next phase of System Development Life Cycle Planning, Analysis and Design. Please note that you are not required to do the implementation (coding) for the project.

You are required to do the following tasks:

1. Identify and discuss a suitable methodology for your system development. State your justifications for the selection.

2. Your group is required to estimate the projects size, effort and schedule. Use a technique that has been introduced to you in the class (See Chapter 2 Project Management) for this purpose.

3. Develop a workplan that lists the tasks that will need to be completed to meet the project objectives. Create a Gantt chart in a project management tool to graphically

show the high level tasks of the project.

4. Identify the roles that will be needed to develop your project? List them and write short descriptions for each of the identified roles. Which roles will each of your

team members perform? Will some team members perform multiple roles? What

will be the reporting structure for the project?

5. Develop a risk assessment document i.e. a document that tracks potential risks along with an evaluation of the likelihood of the risk and its potential impact on the

project.

6. Conduct further study to understand the current systems and processes that already existed in the organization by using the requirements-gathering techniques and

write the as-is business process. Keep all relevant documents involved such as questionnaires, survey results, interview results, industry reports and statistics, and

so on, and submit as attachments to the project proposal later.

7. Using the requirements analysis techniques and requirements-gathering techniques, collect all the necessary information and try to identify the business requirements

for the system. Develop a requirements definition document. As the project

progress, add the requirements to the requirements definition and try to group it by

requirements type Nonfunctional and Functional requirements.

SCB2053/SDB1123 SAD June 2014|Page 3

8. Create Functional models for your project. a. Create activity diagrams to model the overall flow of execution of the

business process of the new system being developed. (i.e. the to-be system).

b. Identify 3 to 7 use cases and give a detailed use case description for each of the use cases

c. Based on the use cases descriptions developed in part (b), create a use case diagram for each.

9. Develop Structural models for your project. a. Create a set of Class-Responsibility-Collaboration (CRC) Cards for your

system.

b. Create a class diagram from the CRC Cards created in part (a). c. Create an object diagram based on the class diagram you drew in part (b).

10. Develop Behavioral models for your project by creating a sequence diagram for

your project.

11. Review the requirements definition and the other deliverable that your team created

during the analysis phase. Review the propose methodology your team suggested

for the system development as to meet the schedule deadline. Identify whether there

is a need for an incremental release of the system. If yes, identify the system

features for each version. Revise your workplan accordingly, review the feasibility

analysis and update it where appropriate. All of the deliverables from project then

combined into a system proposal. Combine all of the project deliverables into a

system proposal