The document discusses enhancing the flexibility of the Selangkah System used by UiTM to assist students in identifying suitable study programs. It aims to allow easier changes to the system to accommodate annual updates to admission rules and regulations. The current system's hardcoded rules make changes difficult. The research will review the system, verify requirements, and design a more flexible system through documentation and a design that allows dynamic rule changes. This will benefit both students and administrators.

1. Enhancing the flexibility to the
design
of
Selangkah System
Name : Muhammad Izzat Bin Abd. Hadi
Matrix No : 2010681642
Supervisor’s Name : Pn. Suriyati Razali

2. Research Background
―Enhancement is the process of adding new functionality to a system.
This is usually done at the request of system users. This activity
requires a full life-cycle of its own. That is, enhancements demand
requirements, design, implementation, and test.‖
(Roger S. Pressman,2001)
―System design is associated with building a formal morphology of
the system, comprising the process of defining the system
parameters, submodels, and criteria, selecting an optimal candidate,
and preparing a detail implementation plan for the chosen candidate.
It is primarily a wholistic approach to engineering a system, and is
differentiated from operations research and other analytical
methods. ‖
(Charles C Willow,2007)

3. Research Background
 This research focus on the Sistem Semakan Syarat Selangkah
ke UiTM (Selangkah).
 Selangkah System is developed and owned by Bahagian
Pengambilan Pelajar (BPP) UiTM.
 Selangkah System is to assist student in identify the suitable
programme for them based on their SPM or STPM results.
 Selangkah System also assist universities staff itself in order to
guiding student during outreach program such as Karnival
Pengajian Tinggi Negara (KPTN) where they will meet the
student and give information about each programme offered.

4. Manual System :
SPM’s candidate and STPM’s candidate Current Selangkah System:
check their eligibility to enter UiTM with SPM candidate and STPM candidate to
the manually. check either they are eligible to apply for
https://online.mohe.gov.my/upu/emas/ind the program required by the SPM results.
ex_epanduan.php?pagefunc=epanduan http://www.selangkah.uitm.edu.my/

5. Problem Statement
Current normal practice in UiTM the
rules and regulation of programme
frequently change every year
However the developer of the system
is having difficulties to change system
functionality that relates to the new
regulation because the rules are hard-
coded. Furthermore, there is no paper
documentation on the system
description.

6. Aim
Aim :
To enhance the design for existing system to make more flexible in
changing the regulation every year and provide the appropriate
documentation for existing systems.
―A flexible system is a system designed to maintain a high level of
performance through real time changes in configuration when
operating conditions or requirements change in a predictable or
unpredictable way.‖
(Andrew Olewnik and Kemper Lewis, 2006)

7. Objectives & Scope
 The objectives are:
◦ To review functionality Selangkah System.
◦ To verify requirement document.
◦ To design Selangkah System that allow
flexible in changing rule.
 Scope
◦ To be used for SPM and STPM candidate
to apply programme in UiTM only.

8. Stakeholders
 Student:
◦ SPM’s candidate
◦ STPM’s candidate
 The administrator

9. Significant of Project
 To the student
◦ Allow student to search for suitable
programme to enter UiTM
 To the administrator:
◦ To ease system developer do the changes
on the rules and regulation

10. Literature Review
Title / Author Important Quotes Findings
Software Engineering -Enhancement is the process of adding new functionality The terminology
(A Pratitioner’s to a system. This is usually done at the request of system for
Approach) users. This activity requires a full life-cycle of its own. Enhancement
That is, enhancements demand requirements, design,
Roger S. Pressman implementation, and test.
(2001)
-Enhancement as software is used, the customer/user will
recognize additional functions that will provide benefit.
Perfective maintenance extends the software beyond its
original functional requirements
Ethical Issues in Enhancement is typically contraposed to therapy. In broad The terminology
Human Enhancement terms, therapy aims to fix something that has gone wrong, for
by curing specific diseases or injuries, while enhancement Enhancement
Nick Bostrom, Rebecca interventions aim to improve the state of an organism
Roache beyond its normal healthy state.
(2008)

11. Literature Review
Title / Author Important Quotes Findings
A decision support A flexible system is a system designed to maintain a high The terminology
framework for flexible level of performance through real time changes in for Flexible
system design configuration when operating conditions or requirements System
change in a predictable or unpredictable way.
Andrew Olewnik,
Kemper Lewis
(2006)
Qualitative decision System design is associated with building a formal The terminology
making with integrated morphology of the system, comprising the process of for System
systems design defining the system parameters, submodels, and criteria, Design
methodology selecting an optimal candidate, and preparing a detail
implementation plan for the chosen candidate. It is
Charles C Willow primarily a wholistic approach to engineering a system,
(2007) and is differentiated from operations research and other
analytical methods.

12. Literature Review
Title / Author Important Quotes Findings
Software System documentation includes all of the documents The terminology
Documentation describing the system itself from the requirements for System
specification to the final acceptance test plan. Documents Documentation
Ian Sommerville describing the design, implementation and testing of a
(2001) system are essential if the program is to be understood and
maintained. Like user documentation, it is important that
system documentation is structured, with overviews
leading the reader into more formal and detailed
descriptions of each aspect of the system.

13. Literature Review
Title / Author Important Quotes Findings
SYSTEMS There are process for documentation: Process for
DOCUMENTATION Documentation
(a practical case study) -Documentation must be done parallel to the
development of a system if it is ever to end up
Rlcardo Ameneyro, properly documented
Carolina Arena, Ruben -Documentation must guide the reader only
Colmenares, Pedro throughout the sections t h a t are relevant to his
Cornejo, Rafael Garcia, particular interest at that time
Eloy Hernandez, Genaro -Documentation must help to locate the modules the
Mariscal, and Socrates maintainer has to modify in order to fulfill the new
Rivera requirements
(1984) -Documentation must aid the maintainer to evaluate
the impact in the system as a whole induced by the
proposed modification
-Documentation must be as dynamic as the system
itself and remain constantly up to dateto date

14. Literature Review
Title / Author Important Quotes Findings
Software Documentation Process documentation falls into a number of categories: Process System
Documentation
Ian Sommerville 1)Plans, estimates and schedules - These are documents
(2001) produced by managers which are used to predict and to control
the software process.
2)Reports - These are documents which report how resources
were used during the process of development.
3)Standards - These are documents which set out how the
process is to be implemented. These may be developed from
organizational, national or international standards.
4)Working papers - These are often the principal technical
communication documents in a project. They record the ideas
and thoughts of the engineers working on the project are
interim versions of product documentation, describe
implementation strategies and set out problems which have
been identified. They often, implicitly, record the rationale for
design decisions.
5)Memos and electronic mail messages - These record the
details of everyday communications between managers and
development engineers.

15. Literature Review
Title / Author Important Quotes Findings
Important Papers In The -Document preparation has been an increasingly Important of
History Of Document important application of computers for over twenty-five System
Preparation Systems: years. When first developed, document preparation Documentation
Basic Sources systems were only one of many applications supported
on a computing system (and, indeed, an application that
Richard Furut system administrators often tried to suppress rather than
(1992) support). In the modern computing environment, it is
common to find computers that are used only for
document preparation.
-In addition to being an important target for development
projects, document preparation systems have become the
focus of academic research, carried out both in
universities and in industrial research centers. Indeed,
the research is wide ranging as a successful document
preparation system draws ideas from a broad collection
of areas. Document preparation systems have also been
the target of standardization, and international standards
organizations have issued standards for some parts of the
document preparation process.

16. Literature Review
Title / Author Important Quotes Findings
The Information The documentation of information system is a Important of
Systems component of communication, control and System
Documentation – monitoring of the development, operation and Documentation
maintenance project. At the same time, the
Another Problem
documentation should be regarded as one of
for Project the results of the stages of the system life
Management cycle. This is why, the system documentation
is important from the viewpoint of the project
Prof. Dumitru Oprea, management and of its development and
Assoc. Prof. Gabriela operation. Unfortunately, one can find that
Mesnita most often in practice the documentation is
(2006) either incomplete or totally missing.

17. Research Methodology
Description of
Stage Process Method Deliverables
Activities
-Identify and
understand the
problem
Problem
-Identify the aim, Project
Planning identification
scope, objectives and proposal
significance
-Plan the project
schedule

18. Research Methodology
Description of
Stage Process Method Deliverables
Activities
Interview session Identify admission rules
(Admin staff at and regulation
Requirement procedure
BPP)
Review
Observe Identify system
Selangkah System functionality
SRS for
-Provide descriptions of
Selangkah
identified functionality
Requirement System
-Create requirement
Specification
Requirement Interview session models :
and 1
(Developer) use case diagram
Requirement
Use case Description
Modeling
Sequence Diagram
-Verify requirement
Requirement Requirement with:
Admin Verified SRS
Verification checklist
Developer 2

19. Research Methodology
Description of
Stage Process Method Deliverables
Activities
Understand
Review
Document the Selangkah
current system
review System
architecture
architecture
To design
Selangkah
System: SDD for
System
Design according to Selangkah
application System
Detail design architecture 3
used
allow
flexibility in
changing rules
and regulation

20. Project Schedule(CSP600: 12.9.2011 –
23.12.2011)
TASK NAME START FINISH DURATION
Identify topic & problem 12/9/2011 2/11/2011 37 Days
statement
Identify supervisor 13/9/2011 28/9/2011 11 Days
Research topic & 15/9/2011 20/10/201 25 Days
Working title 1
Problem statement & 22/9/2011 28/10/201 26 Days
objectives 1
Literature Review 13/10/2011 24/11/201 30 Days
1
Research Methodology 31/10/2011 24/11/201 18 Days
1
First draft submission 18/11/2011 18/11/201 0 Days
1
Mock presentation 18/11/2011 18/11/201 0 Days
1

21. Project Schedule (CSP650: 23.01.2012 –
16.07.2012)
TASK NAME START FINISH DURATION
Project progress 23/1/2012 29/6/2012 114 Days
Requirement review 23/1/2012 6/2/2012 14 Days
Requirement Requirement 8/2/2012 22/2/2012 14 Days
Specification and
Requirement Modeling
Requirement Verification 23/2/2012 23/3/2012 30 Days
System Design 23/1/2012 31/5/2012 93 Days
Draft submission 1/6/2012 1/6/2012 0 Days
Validation of project draft 6/6/2012 15/6/2012 7 Days
Validation of final project 20/6/2012 21/6/2012 1 Days
report
Final project presentation 25/6/2012 13/7/2012 14 Days
Final project report 16/7/2012 16/7/2012 0 Days
submission

22. References
 Rlcardo Ameneyro, Carolina Arena, Ruben Colmenares,Pedro Cornejo, Rafael Garcia,
Eloy Hernandez,Genaro Mariscal, and Socrates Rivera, (1984) SYSTEMS
DOCUMENTATION (a practical case study), Centro de Procesamiento Arturo
Rosenblueth Ministry of Public Education, Mexico.
 Charles C Willow (2007), Qualitative decision making with integrated systems design
methodology, Management Information Systems, Department of Management &
Marketing, School of Business Administration, Monmouth University, West Long
Branch, NJ 07764-1898, USA
 Richard Furuta (1992), Important Papers In The History Of Document Preparation
Systems: Basic Sources, National Institute of Standards and Technology and University
of Maryland
 Nick Bostrom, Rebecca Roache (2008), Ethical Issues in Human Enhancement,New
Waves in Applied Ethics, eds. Jesper Ryberg, Thomas Petersen & Clark Wolf (Pelgrave
Macmillan, 2008):
 Prof. Dumitru Oprea, Assoc. Prof. Gabriela Mesnita (2006), The Information Systems
Documentation – Another Problem for Project Management, University, Iasi, Romania
 Roger S. Pressman(2001), Software Engineering (A Pratitioner’s Approach), Americas,
New York, NY, 10020
 Ian Sommerville (2001), Software Documentation, Lancaster University, UK
 Andrew Olewnik, Kemper Lewis(2006), A decision support framework for
flexible system design, University at Buffalo—SUNY, USA