Você está na página 1de 3

CT046-3.

5-2 SDM SYSTEM DEVELOPMENT METHODS APU DEGREE LEVEL 2


ASIA PACIFIC UNIVERSITY 1 082013
ASIA PACIFIC UNIVERSITY
CT046-3.5-2 SDM SYSTEM DEVELOPMENT METHODS - APU DEGREE LEVEL 2

Case Study:
The Human Resources Management System (HRMS) for XBase Inc.
This system is intended to provide basic functions to store and manage information on employees in the
Human Resources (HR) department of an accounting firm known as XBase Inc. XBase started as a small
company back in 2006 but has grown significantly in recent years, with employee numbers having
increased by several folds. The implication of this change is that XBase can no longer depend on its
existing manual system to store and manage its growing number of employee records. The current
manual system requires HR staff to spend a considerable amount of time searching for specific employee
records. They are also faced with other problems such as misplaced, inconsistent and incomplete data as
well as illegible handwritings.
This system is intended to eradicate the conventional method of manually storing and processing
employee records by using a dedicated HR Management System (HRMS) which has a database enabled
intranet based system that stores and manages employee records effectively and efficiently.
The scope of this system is confined to the basic functions that are performed within the HR department
specifically employee record keeping, leave and training tracking as well as staff appraisals. The system
however does not cover some of the other functions such as generating payroll which comes under the
purview of the Finance department in XBase. This system also does not support recruitment activities
such as advertising and matching potential employees to specific positions because XBase has outsourced
those functions to a professional recruitment firm.

Suggested features of XBase HRMS:
1. The HRMS provides different views of the system to authorized users according to their access
privileges. Each user is categorized as either a Normal, Supervisor or Admin user. In general, all
employees access the system as Normal users; all employees who supervise other employees are
granted Supervisor access to the system. However, they are able to access only those employee
records of their immediate supervisees. The HR manager and other selected HR personnel have
Admin access to the system.
2. When a new employee joins XBase Inc., the Admin inserts his/her record into the system. Similarly
when an employee leaves XBase, the Admin deletes his/her record from the system. The system also
allows the Admin to edit or update employee details when necessary.
3. All employees are able to view and modify their personal information.
4. All employees are able to apply for leave and check their respective leave application status in the
system. When an employee submits a leave application his/her supervisor is able to view, approve or
reject their leave applications.
5. The Admin updates the system with a list of available training programs. Employees who are
interested can then apply to attend those programs, subject to the approval of their supervisors.
6. The system is also able to track employee appraisals which are carried out on a quarterly basis.
Supervisors can input performance ratings, merits, warnings and other remarks related to their
respective supervisees into the system.
7. The system allows the Admin to view an employees current leave status, training status,
performance status, personal information and system account information in an integrated interface.
CT046-3.5-2 SDM SYSTEM DEVELOPMENT METHODS APU DEGREE LEVEL 2
ASIA PACIFIC UNIVERSITY 2 082013
Deliverables;
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 facts finding (investigation or requirement
gathering) that you would use for this system. Describe how each method would be used to
collect information. Attached some sample question for each method.
2.2. Requirement Analysis - Describe the methods, tool and techniques that you would use to
compile, analyze and present data that you would gather. Discuss the benefits of your approach.
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.
3.4. Conditional Control Design Create a Conditional Control chart such as Structured English,
Decision Table and Decision Tree.
(1 PERSON DO ALL 3)
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).
CT046-3.5-2 SDM SYSTEM DEVELOPMENT METHODS APU DEGREE LEVEL 2
ASIA PACIFIC UNIVERSITY 3 082013
4.2. Interface Design - Discuss good interface design principles that you have considered and applied
into creating 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 comprehensive presentation of your individual component.