• Share
  • Email
  • Embed
  • Like
  • Save
  • Private Content
Enhancing the flexibility to the design of selangkah system

Enhancing the flexibility to the design of selangkah system






Total Views
Views on SlideShare
Embed Views



2 Embeds 102

http://izzatfyp.blogspot.com 101
http://izzatfyp.blogspot.sg 1



Upload Details

Uploaded via as Microsoft PowerPoint

Usage Rights

© All Rights Reserved

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
Post Comment
Edit your comment

    Enhancing the flexibility to the design of selangkah system Enhancing the flexibility to the design of selangkah system Presentation Transcript

    • Enhancing the flexibility to the design of Selangkah SystemName : Muhammad Izzat Bin Abd. HadiMatrix No : 2010681642Supervisor’s Name : Pn. Suriyati Razali
    • Research Background―Enhancement is the process of adding new functionality to a system.This is usually done at the request of system users. This activityrequires a full life-cycle of its own. That is, enhancements demandrequirements, design, implementation, and test.‖ (Roger S. Pressman,2001)―System design is associated with building a formal morphology ofthe system, comprising the process of defining the systemparameters, 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 isdifferentiated from operations research and other analyticalmethods. ‖ (Charles C Willow,2007)
    • 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.
    • Manual System :SPM’s candidate and STPM’s candidate Current Selangkah System:check their eligibility to enter UiTM with SPM candidate and STPM candidate tothe manually. check either they are eligible to apply forhttps://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/
    • 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.
    • AimAim :To enhance the design for existing system to make more flexible inchanging the regulation every year and provide the appropriatedocumentation for existing systems.―A flexible system is a system designed to maintain a high level ofperformance through real time changes in configuration whenoperating conditions or requirements change in a predictable orunpredictable way.‖ (Andrew Olewnik and Kemper Lewis, 2006)
    • 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.
    • Stakeholders Student: ◦ SPM’s candidate ◦ STPM’s candidate The administrator
    • 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
    • Literature Review Title / Author Important Quotes FindingsSoftware 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 forApproach) 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 requirementsEthical Issues in Enhancement is typically contraposed to therapy. In broad The terminologyHuman Enhancement terms, therapy aims to fix something that has gone wrong, for by curing specific diseases or injuries, while enhancement EnhancementNick Bostrom, Rebecca interventions aim to improve the state of an organismRoache beyond its normal healthy state.(2008)
    • Literature Review Title / Author Important Quotes FindingsA decision support A flexible system is a system designed to maintain a high The terminologyframework for flexible level of performance through real time changes in for Flexiblesystem 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 terminologymaking with integrated morphology of the system, comprising the process of for Systemsystems design defining the system parameters, submodels, and criteria, Designmethodology selecting an optimal candidate, and preparing a detail implementation plan for the chosen candidate. It isCharles C Willow primarily a wholistic approach to engineering a system,(2007) and is differentiated from operations research and other analytical methods.
    • Literature Review Title / Author Important Quotes FindingsSoftware System documentation includes all of the documents The terminologyDocumentation describing the system itself from the requirements for System specification to the final acceptance test plan. Documents DocumentationIan 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.
    • Literature Review Title / Author Important Quotes FindingsSYSTEMS There are process for documentation: Process forDOCUMENTATION Documentation(a practical case study) -Documentation must be done parallel to the development of a system if it is ever to end upRlcardo Ameneyro, properly documentedCarolina Arena, Ruben -Documentation must guide the reader onlyColmenares, Pedro throughout the sections t h a t are relevant to hisCornejo, Rafael Garcia, particular interest at that timeEloy Hernandez, Genaro -Documentation must help to locate the modules theMariscal, and Socrates maintainer has to modify in order to fulfill the newRivera 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
    • Literature Review Title / Author Important Quotes FindingsSoftware Documentation Process documentation falls into a number of categories: Process System DocumentationIan 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.
    • Literature Review Title / Author Important Quotes FindingsImportant Papers In The -Document preparation has been an increasingly Important ofHistory Of Document important application of computers for over twenty-five SystemPreparation Systems: years. When first developed, document preparation DocumentationBasic Sources systems were only one of many applications supported on a computing system (and, indeed, an application thatRichard 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.
    • Literature Review Title / Author Important Quotes FindingsThe Information The documentation of information system is a Important ofSystems component of communication, control and SystemDocumentation – monitoring of the development, operation and Documentation maintenance project. At the same time, theAnother Problem documentation should be regarded as one offor Project the results of the stages of the system lifeManagement cycle. This is why, the system documentation is important from the viewpoint of the projectProf. Dumitru Oprea, management and of its development andAssoc. Prof. Gabriela operation. Unfortunately, one can find thatMesnita most often in practice the documentation is(2006) either incomplete or totally missing.
    • Research Methodology Description of Stage Process Method Deliverables Activities -Identify and understand the problem Problem -Identify the aim, ProjectPlanning identification scope, objectives and proposal significance -Plan the project schedule
    • 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 SpecificationRequirement 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
    • 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 forSystemDesign according to Selangkah application System Detail design architecture 3 used allow flexibility in changing rules and regulation
    • Project Schedule(CSP600: 12.9.2011 –23.12.2011)TASK NAME START FINISH DURATIONIdentify topic & problem 12/9/2011 2/11/2011 37 DaysstatementIdentify supervisor 13/9/2011 28/9/2011 11 DaysResearch topic & 15/9/2011 20/10/201 25 DaysWorking title 1Problem statement & 22/9/2011 28/10/201 26 Daysobjectives 1Literature Review 13/10/2011 24/11/201 30 Days 1Research Methodology 31/10/2011 24/11/201 18 Days 1First draft submission 18/11/2011 18/11/201 0 Days 1Mock presentation 18/11/2011 18/11/201 0 Days 1
    • Project Schedule (CSP650: 23.01.2012 – 16.07.2012)TASK NAME START FINISH DURATIONProject progress 23/1/2012 29/6/2012 114 DaysRequirement review 23/1/2012 6/2/2012 14 DaysRequirement Requirement 8/2/2012 22/2/2012 14 DaysSpecification andRequirement ModelingRequirement Verification 23/2/2012 23/3/2012 30 DaysSystem Design 23/1/2012 31/5/2012 93 DaysDraft submission 1/6/2012 1/6/2012 0 DaysValidation of project draft 6/6/2012 15/6/2012 7 DaysValidation of final project 20/6/2012 21/6/2012 1 DaysreportFinal project presentation 25/6/2012 13/7/2012 14 DaysFinal project report 16/7/2012 16/7/2012 0 Dayssubmission
    • 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