Universiti Teknologi MARA. The Perception of IT Organizations Towards Software Development Methodology Adoption
|
|
- Gervais Morgan
- 8 years ago
- Views:
Transcription
1 Universiti Teknologi MARA The Perception of IT Organizations Towards Software Development Methodology Adoption Fazilahsul ParidalHaisah Binti Mohd Ali Thesis submitted in fulfillment of the requirements for Bachelor of Science (Hons) Information System Engineering Faculty of Information Technology And Quantitative Science May 2007
2 DECLARATION I certify that this thesis and the research to which it refers are the product of my own work and that any ideas or quotation from the work of other people, published or otherwise are fully acknowledged in accordance with the standard referring practices of the discipline MAY 30, 2007 FAZILAHSUL PARIDALHAISAH BINTIMOHD ALI
3 APPROVAL THE PERCEPTION OF IT ORGANIZATIONS TOWARDS SOFTWARE DEVELOPMENT METHODOLOGY ADOPTION SHAHALAM BY FAZILAHSUL PARIDALHAISAH BINTIMOHD ALI This thesis project was prepared under the direction of supervision of the thesis coordinator, Puan Wan Nor Amalina binti Wan Hariri, Department of System Science and it has been approved by the supervisor, Puan Juliana Hamka binti Kamaroddin. It was submitted to the Faculty of Information Technology and Quantitative Science and was accepted as partially fulfillment of the requirement for degree on Bachelor of Sc (Hons) Information System Engineering. Approved by: Puan Wan Nor Amalina binti Wan Hariri Thesis Coordinator %t^ Puan Juliana Hamka binti Kamaroddin Thesis Supervisor Date: May 30,2007 Date: May 30,2007
4 ACKNOWLEDGEMENT First and foremost, praise to the Almighty "Allah S.W.T" for giving me the mental and physical strength, and confidence to complete this research. I would like to express my sincere gratitude and appreciation to my supervisor, Puan Juliana Hamka binti Kamaroddin, for her constructive ideas, criticisms, guidance and patience throughout the duration of preparing this research. She has successfully guided me to sharpen my understanding of this research. Also a special thanks to Puan Ariza binti Nordin and Puan Wan Nor Amalina binti Wan Hariri, as the coordinators for their lectures, guidance and advices towards better understanding in producing this report. I also would like to convey my special thanks to the entire respondents for their cooperation during the survey session. Special thanks to my friends at the Faculty of Information Technology and Quantitative Science, University Technology MARA, Shah Alam for inspiring and helping me in several ways. I'm really thankful to my mother, Rafeah binti Mohd Sarip and my siblings for giving the moral support and encouragement to complete this research. Always showing concern and motivate me to overcome my frustrations in the process of conducting this study. Last but not least I owe my thanks to everyone that involved directly or indirectly in the completion of this research paper. Their support is priceless and memorable for me ever. This study is possible because of all of you. Thank You IV
5 ABSTRACT This study was conducted to investigate the factors that impact the adoption of Software Development Methodology (SDM). This study uses interview and survey instrument to identify the SDM that mostly adopted by IT organizations. The survey focuses on the organizational perspective which is significant to obtain more information in relation to the SDM selection and adoption. Five factors of adoption by Roger's were identified and used to achieve findings in this research. The factors include relative advantage, compatibility, complexity, trialability, and observability. All the relevant data that is valuable to this study will be collected and analyze to reach the possible results. Then, the results will address the methodology used in software development industry, and also the factors that has greater impact to the adoption of that method. The result found that Rapid Application Development (RAD) is the method that mostly adopted by IT organizations. While relative advantage can be the dominant factor that influences the adoption of that method.
6 TABLE OF CONTENTS TITLE PAGE DECLARATION APPROVAL ACKNOWLEDGEMENT ABSTRACT TABLE OF CONTENTS LIST OF TABLES LIST OF FIGURES LIST OF ABBREVIATIONS ii iii iv v vi x xi xiii CHAPTER 1: INTRODUCTION 1.1 Introduction Research Background Research Problem Objective of the Research Significance of the Research Scope of the Research Summary 8 CHAPTER 2: LITERATURE REVIEW 2.1 Introduction Related Studies on Software Development Methodology (SDM) Adoption Software Development Methodology (SDM) Build and Fix Model Waterfall Model Rapid Prototyping Model Extreme Programming Object-Oriented Programming (OOP) 17 VI
7 2.3.6 Rational Unified Process Rapid Application Development (RAD) Incremental Model Spiral Model Iterative Development ADR Method Robust Software Development Process Agile Manifesto Cleanroom Software Engineering ICONIX MBASE Lightweight Methodology Feature Driven Development (FDD) Jackson System Development (JSD) RITE Method TROPOS Capability Maturity Model (CMM) ISO ISO ISO (SPICE) Diffusion and Adoption of Innovation Perceived Characteristics of Innovations Adoption Stages Adoption Factors by Rogers Relative Advantage Complexity Compatibility Trialability Observability Summary 36 vu
8 CHAPTER 3: RESEARCH APPROACH AND METHODOLOGY 3.1 Introduction Research Approach and Methodology Problem Formation Research Design Population Sampling Technique Data Collection Primary Data Secondary Data Data Analysis Finding Summary 44 CHAPTER 4: RESULT AND FINDINGS 4.1 Introduction Interview Results Analysis for Online Survey Analysis for Questionnaire Analysis of Organization Description Analysis for Organizations that Adopt FSDM Roger's Factors of Adoption Relative Advantage Complexity Compatibility Trialability Observability Analysis for Organizations that Adopt FSDM and Innovation The Identification of SDM Adoption The Investigation of Factors Affect SDM Adoption by Category 69 VUl
9 4.6.1 FSDM FSDM with Innovation Own Method Summary 74 CHAPTER 5: CONCLUSION AND RECOMMENDATION 5.1 Introduction Conclusions Recommendations Summary 79 REFERENCES 80 APPENDICES IX
10 LIST OF TABLES TITLE PAGE Table 2.1: The Activities Livolve in Feature Driven Development 24 Table 2.2: The Tools Used for Feature Driven Development 25 Table 4.1: Interview Result 46 Table 4.2: Number of Method Used by IT Organizations 51 Table 4.3: SDM Adoption by IT Organizations 68 Table 4.4: Factors Affect SDM Adoption by FSDM Category 69 Table 4.5: Result for Factors Affect SDM Adoption by FSDM Category 70 Table 4.6: Factors Affect SDM Adoption by FSDM+Innovation Category 71 Table 4.7: Result for Factors Affect SDM Adoption by FSDM+Innovation Category 72 Table 4.8: Factors Affect SDM Adoption by Own Method Category 73 Table 4.9: Result for Factors Affect SDM Adoption by Own Method Category 74 Table 5.1: SDM Adoption by IT Organizations 76 Table 5.2: Summary of SDM Adoption by FSDM Category 76 Table 5.3: Summary of SDM Adoption by FSDM+Innovation Category 76 Table 5.4: Summary of Factors Affecting the SDM Adoption by Category (FSDM, FSDM+Innovation, and Own Method) 77
11 LIST OF FIGURES TITLE PAGE Figure 2.1: Waterfall Model for Software Development 16 Figure 2.2: The Innovation Diffusion Process Model (Adapted from Rogers, 1983) 29 Figure 2.3: Factors Affecting IT Diffusion. (Adapted from Rogers, 1983) 31 Figure 2.4: Stages of the Innovation Diffusion Process (Adapted from Rogers, 1983) 32 Figure 3.1: Research Approach and Methodology 3 8 Figure 4.1: Total number of ftilltime employees by category (FSDM, FSDM+Innovation, and Own Method). 48 Figure 4.2: Annual sales turnover rate by category (FSDM, FSDM+Innovation, and Own Method). 49 Figure 4.3: Types of project involves within organization by category (FSDM, FSDM+Innovation, and Own Method). 50 Figure 4.4: Methodology used by category (FSDM, and FSDM+Innovation). 51 Figure 4.5: Advantages of method usage by category (FSDM, FSDM+Innovation, and Own Method). 52 Figure 4.6: Comparison for complex method by category (FSDM, FSDM+Innovation, and Own Method). 53 Figure 4.7: Comparison for reducing method complexity by category (FSDM, FSDM+Innovation, and Own Method). 54 Figure 4.8: Comparison for the need of methodology adoption by category (FSDM, FSDM+Innovation, and Own Method). 5 5 XI
12 Figure 4.9: Comparison for factors influence compatibility by category (FSDM, FSDM+Innovation, and Own Method). 56 Figure 4.10: Comparison for compatibihty factor that influence project management process by category (FSDM, FSDM+Inno, and Own Method). 57 Figure 4.11: Comparison for the acceptance of method adoption by category (FSDM FSDM+Innovation, and Own Method). 58 Figure 4.12: Comparison for level of satisfaction by category (FSDM FSDM+Innovation, and Own Method). 59 Figure 4.13: Comparison for observability aspect by category (FSDM, FSDM+Innovation, and Own Method). 60 Figure 4.14: Comparison for reasons for methodology adoption by category (FSDM FSDM+Inno, and Own Method). 61 Figure 4.15: Years taken for Methodology Innovation by FSDM+Innovation Category. 62 Figure 4.16: Sources for idea of an innovation by FSDM+Innovation Category 63 Figure 4.17: People responsible for methodology innovation by FSDM+Innovation Category. 64 Figure 4.18: Problem with FSDM by FSDM+Innovation Category. 65 Figure 4.19: Benefit of innovated SDM by FSDM+Innovation Category. 66 Figure 4.20: Objectives of SDM innovation by FSDM+Innovation Category. 67 xu
13 LIST OF ABBREVIATIONS FSDM SDM OOP RAD RUP FDD JSD CMM Formal Software Development Methodology Software Development Methodology Object-Oriented Programming Rapid Application Development Rational Unified Process Feature Driven Development Jackson System Development Capability Maturity Model XUl
14 CHAPTER 1 INTRODUCTION 1.1 Introduction The most organizational aim is the goal to perceive new work methods that will provide organizations with relative advantages over some previous method(s). Indeed, the method which is used in software development is also known as Software Development Methodology (SDM). It is able in helping people to plan, organize, and manage the software development processes. A common software development organizational problem involves unsuccessful implementation of newly acquired methodology innovation. Although the problem becomes clearer and takes time to solve, but the acceptance of this innovated technology supposedly provides significant affects that enable other innovation being made to improve it uses. The innovation processes can be viewed over various perspectives, but this study is focused on organizational view of SDM innovation and adoption. This study describes the adoption of given innovation targeted to population of user, is called innovation diffusion. It means that the communities within the population are able to do innovation to improve performance and productivity. Loch's and Huberman's (1999) defined the diffusion as the acceptance and spread of new technology in a market or user community. This research is focused on the factors that may contribute to the SDM adoption in the software development organization. The software development will perform better since the adoption of its methodology organized and implement properly. This is supported by Rogers (1995) where he stated that the stages of adoption process concerns with the knowledge, persuasion, decision, implementation and confirmation. These stages will be used in adopting those methodologies to figure out the benefits of implementing it.
15 The study assumes that the organizational purpose of methodology adoption is to improve software performance as long as organization benefits from it. This research is attempted to find the relevant user perception of the methodology adoption. The user in this context involves programmer, developer, project manager, and organization manager which are likely to lead to user perceptions of methodology adoption performance. The elaborative impact of user perceptions includes relative advantage, compatibility, complexity, trialability and observability which are as assigned by (Rogers, 1995). The application of the innovation to SDM also creates implications for helping organizations to better manage their business reengineering. With the innovated SDM, organizations are able to reorganize the development of software process to ensure the reliability and effectiveness of the software delivery itself. Thus, organizations that provide the right methodology will give them the right software products. This impact brings the organization to properly manage SDM on their way. The perception of users of a newly implemented SDM in countries such as United States, Australia, South Africa, and Finland were assessed. These countries implemented different characteristics of innovation. Templeton and Byrd (2003) used relative advantage, voluntariness, compatibility, image, ease of use, resuh demonstrability, visibility, and trialability as the innovation variables. Huisman and livari (2002) used relative advantage, complexity, compatibility, demonstrability and trialability as their characteristics. However, Mark et al., (2002) used characteristics which is similar to the one used by Rogers (1995) and did not extend to other characteristics which are relative advantage, compatibility, complexity, trialability and observability as an approach. However, in Malaysia there is no other research on this particular topic. This paper will first describe the theoretical background that brings a need for this research. A research and its associated hypotheses are expressed and viewedfi-ompast
16 researches. The methods and results of the study are then analyzed, followed by a discussion offindings,conclusions and recommendations for future research. 1.2 Research Background Software Development Methodology (SDM) involve wide varieties of terms, issues, components, factors, models and many more. As an introduction, the definition of Software Engineering (SE) is the practice of using selected process techniques to improve the quality of software development effort. This means that a methodical approach to software development resulted to fewer defects, shorter delivery time as well as better value. It is also noted that, SDM as a significant aspect in producing software can be defined as a documented collection of policies, procedures, and processes used by a development team or organization to practice software engineering. However, methodology in the context of software engineering and project management is a codified set of practices (sometimes accompanied by training materials, formal educational programs, worksheets, and diagramming tools) that may be repeatedly carried out to produce software. By defining the right methodology will help to perform correctly and identify quality software products. However, there are many aspects that an organization needs to know in terms of how to identify the right methodology. Methodology is always related to risk management. The only challenge is to select and track the methodology in an organization is just to do it wisely. By following a methodology, it will provide sufficient process disciplines to deliver the required quality for a business succeed, as long as they avoid steps that will waste time, reduce productivity, or demoralize developers. The best approach for applying a methodology is to consider that it will be able to manage risk which is obtained from the previous projects.
17 Other significant terms that should be defined is an adoption. Adoption means to take or use something, approval or acceptance, usually applied to amendments or resolutions. This is a major contribution to this topic which concerns with the adoption of SDM. Although, the term Software Development can be described as a set of activities performed to produce software products. Software development may include new development, innovation, modification, reuse, re-engineering, maintenance, or any other activities that result in software products. The suitability or otherwise of these models, or indeed the reporting of new models, for examining the intention to adopt system or software development methodologies has received relatively little research (Roberts, 1998). Technology or methodology innovations adapted to the IT industry that rarely grow for long at one institution unless they also spread among many institutions. If it is widely used and the achievement clearly identified, the various user can support each other in the long term survival SDM innovation. This is so that the widespread adoption of innovated SDM will acquire high values to the organizational and industry investment. According to Fitzgerald (1998), the arguments for using a methodology are persuasive but many organizations are resistant to change, either to using any methodology or to changing it. This means, since traditional methodologies are in placed, there still have organizations adopted the SDM. The use of that methodology is as a guideline to ensure its efficiency and effectiveness to the organization management. Even though the adopted SDM may enhance in getting better performance, it is also requires another existence of SDM to support the use of this innovated SDM. The changes of technology and the potential projects that fit to the appropriate methodology are usually the cause of the adoption of the irmovated SDM. All the terms that had been defined earlier has significant relationship with this research. The combinations of those terms provide the valuable information to this research. Focusing on the factors that are affecting the rates of Software Development
18 Methodology (SDM) adoption on IT organizations in Malaysia, the use of Rogers' factors will evidently help researchers to measure it. Additionally, factors identified by Rogers include relative advantage, compatibility, complexity, trialability and observability. All this factors will be significant in this research to investigating how far software development companies applied Rogers' factors in adopting their SDM. 1.3 Research Problem Most of software development involves disorganized activity. The software is built without much planning, and designing of the system is a combination from the short term decisions. As long as the system is running, the user's requirements are met, it is then considered as complete and can be used in appropriate circumstances. However, the system developer should work to gain trust from users to propose a system that can meet the requirements and able to achieve high expectations from the users besides, only to be used in basic conditions. Most of IT organizations have bad practice to create this high expectation. The ways they develop a system create problems in choosing the correct SDM. Even if there are best practices available, some IT companies' still face this problem. The role of SDM as a guidance that are able to bring large impacts to the software development process gives the organization to develop the system based on the existing procedures and policies in the industry. From developer perspectives, they have consideration to choose or customize the SDM because they know the overall processes that must be included in a software development. One of the SDM problems is that the development team treats the process of software development as an orderly, rational process. Fowler (2003) challenges the notion of the engineering metaphor as a basis for 'predictive' software development and proffers an alternate view of it as an 'adaptive' process that recognizes the reality of uncertainty as part of the requirements and design processes. A fiirther problematic aspect identified was that SDM fraditionally focused on technical rather than social
19 issues. From the OASIG study, it reported that the methods appeared not to work, as system developers are too technically oriented. According to the study, it mentioned that from previous few years, the types of software that are developed are changed from a more technical systems to a more user focused system (developed for users who have limited computer skills). However, the ability of traditional methods to deliver production software in a timely manner is another serious concern raised by (Fitzgerald, 1998). Another problem raised from software development methodologies is by considering that so many systems failed. According to Russo and Stolterman (1998), they have been suggested that "currently, many software developers do not follow software development methodologies when developing software system". This explained how the real software development environment occurs today. The methodology that is being adopted only as a name, but the use of that methodology is out of control. To support the above statement, Fitzgerald (1998) in his research found that there are 60 percent of respondents did not applied the development methodology, but only six percent of them have followed the methodology rigorously. The complexities of the methodology or the system itself may rise and becomes a problem to them. So, the important thing is that the methodologies adopted must fit with the needs of developers to ensure the software development processes run smoothly. The other problems that always occur in developing software also include the application of incorrect requirements. Requirements are important since the initial development process. The lack of requirements may occur because development team failed to capture the usable and accurate data while conducting an interview session. The misunderstanding concepts by users are also the problems that always arise. Other than that, development team also takes a long time to deliver the output from each phase. Because of time, the entire development processes will be diflficuh to manage and the next processes will be delayed. Therefore, on the perspective of the development costs, it will exceed because the management team failed to plan the time as well as to follow development schedule taken for each steps. This is so that, the
20 product can still be completed but with various conflicts such as cost and schedule overruns and also the lack of certain features or functions. However, the problems mentioned above in regards to the problems that occurred due to the failure of selecting the right methodology. This research conducts to look in depth what are the factors influencing the adoption of a methodology by the organization. This is because in the real world of software development industry, there are no dominating factors that can be identified as the main motivators for using a software development methodology. This theory is supported by Avison and Fitzgerald (2003) by which they said that methodologies are often contingent on the type or a size of a project, technology environment and organizational context. By doing this research, measuring the SDM adoption rate by organization using Rogers' factor may come out with the appropriate effects. Thus, there not only be able to get information about methodologies that are available, but this can also provide the organization with the useful information about the SDM adoption. The measurement will be done with the use of methodology adoption within the organization. 1.4 Objectives of the Research This research has been conducted according to its objectives. The objectives of this research are as follows: i. To identify Software Development Methodology (SDM) applied by IT organizations, ii. To investigate the perception of IT organizations towards SDM adoption using Rogers' factors of adoption.
21 1.5 Significance of the Research The significance of the research is listed as below: i. Provide development team with the important factors on selecting and adopting correct SDM in developing quality software, ii. To expose the management team with the SDM chosen that will affect the entire software processes, iii. To provide developer with better understanding, knowledge as well as to improve skills and experiences in software development environment. 1.6 Scope of the Research The scope of the research will focus on Information Technology (IT) organizations in Malaysia that involves in software development environment. 1.7 Summary The technologies growth pursued the emergence of industrial changes and challenges. However, as globally accepted that it perform to various industries as new equipments to allow the organization to compete with others. Software development industry is a large community that fully utilizes the technological usage. Software Development Methodology (SDM) is considered as new technology applied in its industry. The adoption of methodology may provide the organization with the correct procedures and policies for development processes. Even though it becomes important, there are a number of problems faced during software development process. There is no dominating factors are used as main motivators for using software development methodology, incomplete requirements, and inability to apply adopted methodology as a guideline to develop software, cost and time overruns, high number of project failures, and low number of adopting SDM are the problems that occurred. This section describes each of problems that are related to this research and focuses on the factors of adopting those SDM.
22 CHAPTER 2 LITERATURE REVIEW 2.1 Introduction Information Technology (IT) projects such as developing software are organizational investment. It requires various types of components to complete tasks. When an organization focuses on IT projects, it commits considerable time, money and resources to the projects so that it will give values to the organization in thefiiture.to be a successful organization in IT projects will be difficult without the correct Software Development Methodology (SDM) chosen, expertise and knowledge among team members. Nowadays, software products are growing with unceasing endeavor. The implementation of that software helps people in surviving their working life. It also capable to give impacts in working environment that is willing to increase their performance and makes it challenging with other technological products. However, the software products increased depends on the various factors such the way to produce products, as well as the features andfiinctionalitiesthat must be included so that the expected outcomes will be in the future. Software Development Methodology (SDM) is relatively close to producing the software. It is one of the important aspects that must be included in the software processes and also provided the developer with the sequence of steps that must be followed. There are various methodologies available for software development. A methodology is comprised of tools, techniques and methods. The correct selection of methodology plays a crucial role for the delivery of reliable and correct software products. The selected methodology must match the characteristics of the problem domain.
23 However, according to Fitzgerald (1995), many companies develop their own or adapt existing methodologies or simply do not use at all. 2.2 Related Studies on Software Development Methodology (SDM) Adoption Due to the nature of this research topic, much of the literature that has been published does not fall under the specification of this research. Approximately, the number of the literature regarding this research is quite high because it requires various data from the past research. This paper also describes the rationale and relatedness of those issues that may reflects to the findings of this research. This study found that there are critical differences among methodologies under real circumstances. It is requires to understand how methodologies are selected or adapted or how should be selected. Clearly, this research conducted to identify what are the criteria which will reflects the selection and adoption of methodologies within IT organizations. However, various literatures assign several causes and factors that will end up with adoption of a methodology. Software development methodologies (SDM) have been defined in the regulatory manner with an underlying assumption of universal applicability. However, as industrial practice suggests such Fitzgerald et al., (1996), this assumption is fiindamentally flawed. Software development projects very rarely adopt a methodology in such a rigid fashion. Patel et al., was initially introduced as a means to improve the problems of the software crisis, SDM marked serious limitations due to the lack of any disposition to flexibly adapt to the needs of specific projects, domains and organizational settings. As a consequence, significant undesired effects were generated. Fitzgerald et al., (2003) provide the effects that include lack of a political and organizational dimension, goal displacement, developers resistance to change, and inhibition of creative thinking. 10
24 According to Fitzgerald (1998), practitioners have been reluctant to adopt SDMs resulting in more than one half of them abstaining. Furthermore, it was noted that 79% of the non-adopters intend to stay that way. While there is strong belief in their potential value, where SDMs have largely failed to deliver and this is reflected adoption rates. Fitzgerald (1998) also identified a number of 'arguments' from practitioners against the use of methodologies, and detailed the 'pressures' preventing SDM adoption. Fitzgerald raised the first argument for using a methodology is persuasive but many organizations are resistant to change, either to using any methodology or to changing methodology and only one half of organizations follow any methodology. The second argument is that the importance of the actual system being developed is often conquered by the processes of the methodology. SDMs have been developed to assist software developers build systems that meet their clients needs. These methodologies are generally formalized procedures or protocols to guide development. Clearly, there are problems with software development methodologies considering so many systems fail. Russo and Stolterman (1998) suggested that many developers currently do not even follow software development methodologies when developing software systems. They also suggest that there is currently a misfit between existing methodologies and the needs of developers. Oftentimes, multiple methods are adopted and used together for the same project, but at different phases of the development lifecycle said (Khalifa and Vemer, 2000). From the other point of view. Khalifa and Vemer (2000) were found that there are two main constructs that will be the drivers of software development method usage which are process quality and facilitating conditions. It used as a proven where there is no dominating factors have been identified as the main motivators for using a software development methodology. Huisman and livari (2002) were reported in their research the relationship of various factors that contribute to the deployment of SDMs. They allocate that the relative advantage, compatibility, trailability of a systems development methodology, an individual's experience in systems development and his/her experience in systems development methodologies, management support and 11
How To Understand And Understand The Software Development Process In Korea
Universiti Teknologi MARA Designing a Proposed Model of Software Development Practices Nor Hasikin Bt Husian Thesis submitted infiilfillmentof the requirements for Bachelor of Science (Hons) Information
More informationUniversiti Teknologi MARA. Requirement Analysis Using UML Approach for Research Management System (RMS)
C^tJ O19OO(^'J.Tfi^'i- Universiti Teknologi MARA Requirement Analysis Using UML Approach for Research Management System (RMS) Enamul Hasan Bin Rusly Thesis submitted in fulfillment of the requirements
More informationA WEB-BASED SYSTEM APPLYING THE CUSTOMER RELATIONSHIP MANAGEMENT (CRM) CONCEPTS ON CUSTOMER SERVICES AND SUPPORT (CSS)
3-7455 A WEB-BASED SYSTEM APPLYING THE CUSTOMER RELATIONSHIP MANAGEMENT (CRM) CONCEPTS ON CUSTOMER SERVICES AND SUPPORT (CSS) IN INSTITUTE OF RESEARCH, DEVELOPMENT AND COMMERCIALIZATION (IRDC), UiTM SHAH
More informationUniversiti Teknologi MARA. User Perception on Electronic Customer Relationship Management (E-CRM) Features in Online Hotel Reservation
Universiti Teknologi MARA User Perception on Electronic Customer Relationship Management (E-CRM) Features in Online Hotel Reservation HasUza Binti Azizan Thesis submitted in fulfillment of the requirements
More informationUniversiti Teknologi MARA. The Implementation of Software Configuration Management in MSC Organizations
Universiti Teknologi MARA The Implementation of Software Configuration Management in MSC Organizations Siti Mastura Bt. Sheikh Abu Bakar Thesis submitted in fulfillment of the requirements for Bachelor
More informationSurveying and evaluating tools for managing processes for software intensive systems
Master Thesis in Software Engineering 30 Credits, Advanced Level Surveying and evaluating tools for managing processes for software intensive systems Anuradha Suryadevara IDT Mälardalen University, ABB
More informationSoftware Development Life Cycle (SDLC)
Software Development Life Cycle (SDLC) Supriyo Bhattacharjee MOF Capability Maturity Model (CMM) A bench-mark for measuring the maturity of an organization s software process CMM defines 5 levels of process
More informationSoftware Development Methodologies in Industry. By: Ahmad Deeb
Software Development Methodologies in Industry By: Ahmad Deeb Methodologies Software Development Methodologies in Industry Presentation outline SDM definition Project and analysis approach Research methods
More informationSelecting a Software Development Methodology based on. Organizational Characteristics. Adrienne Farrell
ATHABASCA UNIVERSITY Selecting a Software Development Methodology based on Organizational Characteristics BY Adrienne Farrell An essay submitted in partial fulfillment Of the requirements for the degree
More informationTRADITIONAL VS MODERN SOFTWARE ENGINEERING MODELS: A REVIEW
Year 2014, Vol. 1, issue 1, pp. 49-56 Available online at: http://journal.iecuniversity.com TRADITIONAL VS MODERN SOFTWARE ENGINEERING MODELS: A REVIEW Singh RANDEEP a*, Rathee AMIT b a* Department of
More informationUniversiti Teknologi MARA. ANALYSIS THE PERFORMANCE OF VIDEO CONFERENCING BASED ON QUALITY OF SERVICE (QoS) Nor Hayaty binti Amran
Jb^O00 2^^Zf Universiti Teknologi MARA ANALYSIS THE PERFORMANCE OF VIDEO CONFERENCING BASED ON QUALITY OF SERVICE (QoS) Nor Hayaty binti Amran Thesis submitted in fulfilment of the requirements for BSc
More informationCUSTOMER ONLINE PURCHASE INTENTION TOWARDS AIRLINE E-TICKETING IN KLANG VALLEY CHEW YUH YIING CHONG CHOOI SUN MICHELLE SIM KAI FERN YONG SOOK HUOI
CUSTOMER ONLINE PURCHASE INTENTION TOWARDS AIRLINE E-TICKETING IN KLANG VALLEY BY CHEW YUH YIING CHONG CHOOI SUN MICHELLE SIM KAI FERN YONG SOOK HUOI A research project submitted in partial fulfillment
More informationA Capability Maturity Model (CMM)
Software Development Life Cycle (SDLC) and Development Methods There are some enterprises in which a careful disorderliness is the true method. Herman Melville Capability Maturity Model (CMM) A Capability
More informationThe most suitable system methodology for the proposed system is drawn out.
3.0 Methodology 3.1 Introduction In this chapter, five software development life cycle models are compared and discussed briefly. The most suitable system methodology for the proposed system is drawn out.
More informationA STUDY ON SOTWARE PRODUCT DEVELOPMENT APPROACHES IN THE SRI LANKAN SOFTWARE INDUSTRY
u b / s o ^ /?2 /o~j A STUDY ON SOTWARE PRODUCT DEVELOPMENT APPROACHES IN THE SRI LANKAN SOFTWARE INDUSTRY By V.Manoharan LIBRARY HWIVERSITY OF R/iORATuWA, SRI LANKA MORATUWA The Dissertation was submitted
More informationUnjverslti Teknologi MARA. Prototype Of Web - Based Journal Publication Systems For Institute Of Research, Development Commercialization (IRDC)
31 Goo Unjverslti Teknologi MARA Prototype Of Web - Based Journal Publication Systems For Institute Of Research, Development Commercialization (IRDC) Shanniza binti A. Hamid Thesis submitted in fulfillment
More informationSoftware Development Process
Software Development Process A software development process, also known as software development lifecycle, is a structure imposed on the development of a software product. Similar terms include software
More informationEmergence Of Agile Software Development Methodologies: A Sri Lankan Software R & D Outlook
Emergence Of Agile Software Development Methodologies: A Sri Lankan Software R & D Outlook W.K.S.D Fernando, D.G.S.M Wijayarathne, J.S.D Fernando, M.P.L Mendis, C.D Manawadu Abstract: In software development
More informationUNIVERSITI TEKNOLOGI MARA THE EFFECTIVENESS OF MARKETING MIX STRATEGY CASE STUDY: SETIA ALAM
UNIVERSITI TEKNOLOGI MARA THE EFFECTIVENESS OF MARKETING MIX STRATEGY CASE STUDY: SETIA ALAM HIZMA RAZLIATI BINTI ABDUL RAHIM SEPTEMBER 2011-JANUARI 2012 JABATAN PENGURUSAN HARTANAH FAKULTI SENIBINA PERANCANGAN
More information(Refer Slide Time: 01:52)
Software Engineering Prof. N. L. Sarda Computer Science & Engineering Indian Institute of Technology, Bombay Lecture - 2 Introduction to Software Engineering Challenges, Process Models etc (Part 2) This
More informationAgile Web Engineering (AWE) Process
Agile Web Engineering (AWE) Process Andrew McDonald and Ray Welland Department of Computing Science, University of Glasgow, Glasgow, Scotland. G12 8QQ Abstract 02 December 2001 This document describes
More informationImplementing Models and Standards for Software Development Benefits and Risks
Implementing Models and Standards for Software Development Benefits and Risks Tsvetelina Kovacheva, Quality Manager Musala Soft June 19, 2007 Agenda Difference between Model and Standard Software Development
More informationCHAPTER_3 SOFTWARE ENGINEERING (PROCESS MODELS)
CHAPTER_3 SOFTWARE ENGINEERING (PROCESS MODELS) Prescriptive Process Model Defines a distinct set of activities, actions, tasks, milestones, and work products that are required to engineer high quality
More informationRedesigned Framework and Approach for IT Project Management
Vol. 5 No. 3, July, 2011 Redesigned Framework and Approach for IT Project Management Champa Hewagamage 1, K. P. Hewagamage 2 1 Department of Information Technology, Faculty of Management Studies and Commerce,
More informationSUCCESSION PLANNING AND MANAGEMENT PRACTICES AMONG PRIVATE SECTOR FIRMS IN MALAYSIA KRISHNA NAIDU S/O D. SUPPIAH
SUCCESSION PLANNING AND MANAGEMENT PRACTICES AMONG PRIVATE SECTOR FIRMS IN MALAYSIA KRISHNA NAIDU S/O D. SUPPIAH GRADUATE SCHOOL OF BUSINESS FACULTY OF BUSINESS AND ACCOUNTANCY UNIVERSITY OF MALAYA JUNE
More informationCS4507 Advanced Software Engineering
CS4507 Advanced Software Engineering Lectures 2 & 3: Software Development Lifecycle Models A O Riordan, 2015 Some diagrams from Sommerville, some notes from Maciaszek/Liong Lifecycle Model Software development
More informationAGILE METHODOLOGY IN SOFTWARE DEVELOPMENT
AGILE METHODOLOGY IN SOFTWARE DEVELOPMENT Shivangi Shandilya, Surekha Sangwan, Ritu Yadav Dept. of Computer Science Engineering Dronacharya College Of Engineering, Gurgaon Abstract- Looking at the software
More informationUniversiti Teknoiogi MARA. Measuring Web Quality Metrics of Telecommunication Service Providers in Malaysia
Universiti Teknoiogi MARA Measuring Web Quality Metrics of Telecommunication Service Providers in Malaysia Nazihah Binti Zainal Abidin 2005617976 Thesis submitted in fulfillment of the requirements for
More informationFactors Influencing the Adoption of Biometric Authentication in Mobile Government Security
Factors Influencing the Adoption of Biometric Authentication in Mobile Government Security Thamer Omar Alhussain Bachelor of Computing, Master of ICT School of Information and Communication Technology
More informationStandardized software development model for SME software houses in Pakistan
Standardized software development model for SME software houses in Pakistan Abstract There are many software development models that exist for software development like Extreme Programming, Waterfall,
More information2012/2013 Programme Specification Data. Financial Management
2012/2013 Programme Specification Data Programme Name Programme Number Programme Award QAA Subject Benchmark Statements Financial Management P10423 MSc/PGDip Business Programme Aims Outcomes: Knowledge
More informationIT3205: Fundamentals of Software Engineering (Compulsory)
INTRODUCTION : Fundamentals of Software Engineering (Compulsory) This course is designed to provide the students with the basic competencies required to identify requirements, document the system design
More informationManaging TM1 Projects
White Paper Managing TM1 Projects What You ll Learn in This White Paper: Traditional approaches to project management A more agile approach Prototyping Achieving the ideal outcome Assessing project teams
More information6. Software Lifecycle Models. A software lifecycle model is a standardised format for planning organising, and running a new development project.
6. Software Lifecycle Models A software lifecycle model is a standardised format for planning organising, and running a new development project. Hundreds of different kinds of models are known and used.
More informationIT3203 Fundamentals of Software Engineering (Compulsory) BIT 2 nd YEAR SEMESTER 3
Fundamentals of Software Engineering (Compulsory) BIT 2 nd YEAR SEMESTER 3 INTRODUCTION This course is designed to provide the students with the basic competencies required to identify requirements, document
More informationTitle: Topic 3 Software process models (Topic03 Slide 1).
Title: Topic 3 Software process models (Topic03 Slide 1). Topic 3: Lecture Notes (instructions for the lecturer) Author of the topic: Klaus Bothe (Berlin) English version: Katerina Zdravkova, Vangel Ajanovski
More informationNADHIRA YASMIN ZULKAPLI (2003323669)
Title: IMPLEMENTING A WEB- BASED SINGLE-SIGN-ON By NADHIRA YASMIN ZULKAPLI (2003323669) A project paper submitted to FACULTY OF INFORMATION TECHNOLOGY AND QUANTITATIVE SCIENCE, UNIVERSITI TEKNOLOGI MARA
More informationIntroduction to Agile Software Development
Introduction to Agile Software Development Word Association Write down the first word or phrase that pops in your head when you hear: Extreme Programming (XP) Team (or Personal) Software Process (TSP/PSP)
More informationSOFTWARE PROCESS MODELS
SOFTWARE PROCESS MODELS Slide 1 Software Process Models Process model (Life-cycle model) - steps through which the product progresses Requirements phase Specification phase Design phase Implementation
More informationCOMPARATIVE STUDY ON SOFTWARE PROJECT MANAGEMENT MODELS
COMPARATIVE STUDY ON SOFTWARE PROJECT MANAGEMENT MODELS *1 Mrs. Kalaivani S., * 2 Mrs. Kavitha S., *1 M.Phil Research Scholar, Department of Computer Science Auxilium College (Autonomous), Vellore, TamilNadu,
More informationTest Cases Design for Software Database Provisioning Development
Test Cases Design for Software Database Provisioning Development Sunguk Lee Research Institute of Industrial Science and Technology Pohang, Gyeongbuk, South Korea sunguk@rist.re.kr Abstract This paper
More informationABHINAV NATIONAL MONTHLY REFEREED JOURNAL OF RESEARCH IN SCIENCE & TECHNOLOGY www.abhinavjournal.com
SOFTWARE DEVELOPMENT LIFE CYCLE (SDLC) ANALYTICAL COMPARISON AND SURVEY ON TRADITIONAL AND AGILE METHODOLOGY Sujit Kumar Dora 1 and Pushkar Dubey 2 1 Programmer, Computer Science & Engineering, Padmashree
More informationSoftware Development with Agile Methods
Case Study Software Development with Agile Methods Introduction: Web application development is a much studied, heavily practiced activity. That is, capturing and validating user requirements, estimating
More informationAnd the Models Are 16-03-2015. System/Software Development Life Cycle. Why Life Cycle Approach for Software?
System/Software Development Life Cycle Anurag Srivastava Associate Professor ABV-IIITM, Gwalior Why Life Cycle Approach for Software? Life cycle is a sequence of events or patterns that are displayed in
More information10/4/2013. Sharif University of Technology. Session # 3. Contents. Systems Analysis and Design
Session # 3 Contents Systems Analysis and Design 2 1 Tiers of Software Development 10/4/2013 Information system development project Realistic behavior 3 Information system development project System Development
More informationLecture 8 About Quality and Quality Management Systems
Lecture 8 About Quality and Quality Management Systems Kari Systä 10.03.2014 10.03.2014 TIE-21100/21106; K.Systä 1 Content of today s lecture Two weeks ago we discussed about testing and inspections, that
More informationUsing Simulation to teach project management skills. Dr. Alain April, ÉTS Montréal alain.april@etsmtl.ca
Using Simulation to teach project management skills Dr. Alain April, ÉTS Montréal alain.april@etsmtl.ca Agenda of the workshop 1 The software project management theory overview (40 minutes) 2 Why use SDLC
More informationPROCESS OF MOVING FROM WATERFALL TO AGILE PROJECT MANAGEMENT MODEL
PROCESS OF MOVING FROM WATERFALL TO AGILE PROJECT MANAGEMENT MODEL Sanja Vukićević 1, Dražen Drašković 2 1 Faculty of Organizational Sciences, University of Belgrade, vukicevicsanja@yahoo.com 2 Faculty
More informationFrom myths and fashions to evidence-based software engineering! Magne Jørgensen
From myths and fashions to evidence-based software engineering! Magne Jørgensen Most of the methods below have once been (some still are) fashionable... The Waterfall model, the sashimi model, agile development,
More informationAgile Software Development. Mohsen Afsharchi
Agile Software Development Mohsen Afsharchi I. Agile Software Development Agile software development is a group of software development methods based on iterative and incremental development, where requirements
More informationSoftware Development Life Cycle Models - Process Models. Week 2, Session 1
Software Development Life Cycle Models - Process Models Week 2, Session 1 PROCESS MODELS Many life cycle models have been proposed } Traditional Models (plan-driven) } Classical waterfall model } Iterative
More informationContents. viii. 4 Service Design processes 57. List of figures. List of tables. OGC s foreword. Chief Architect s foreword. Preface.
iii Contents List of figures List of tables OGC s foreword Chief Architect s foreword Preface Acknowledgements v vii viii 1 Introduction 1 1.1 Overview 4 1.2 Context 4 1.3 Purpose 8 1.4 Usage 8 2 Management
More informationBridging the IT Business Gap The Role of an Enterprise Architect
Whitepaper Bridging the IT Business Gap The Role of an Enterprise Architect Today s enterprises understand the value that Information Technology (IT) can bring to their business. IT supports day-to-day
More informationUNIVERSITITEKNOLOGI MARA ' ' ' ELECTRONIC CUSTOMER RELATIONSHIP (e-crm): A PULSE ON THE RETAILING COMMUNITY
3 UNIVERSITITEKNOLOGI MARA ' ' ' ELECTRONIC CUSTOMER RELATIONSHIP (e-crm): A PULSE ON THE RETAILING COMMUNITY Engku Badrul Nizam b. Engku Abdul Rahman 2003361436 Thesis submitted in fulfillment of the
More informationUniversiti Teknologi MARA. A Proposed Framework of Online Banking Service Quality Website. Che Wan Hasnawati Aida bt C.W.Ahmad
3 7(^4 Universiti Teknologi MARA A Proposed Framework of Online Banking Service Quality Website Che Wan Hasnawati Aida bt C.W.Ahmad Thesis submitted in fulfillment of the requirements for Bachelor of Science
More informationIMPLEMENTATION OF SECURE MEDICAL RECORD USING SMARTCARD TECHNOLOGY
IMPLEMENTATION OF SECURE MEDICAL RECORD USING SMARTCARD TECHNOLOGY JOTHI PRAKASH A/L MURUGAN DISSERTATION SUBMITTED IN FULFILMENT OF THE REQUIREMENTS FOR THE DEGREE OF MASTER OF COMPUTER SCIENCE FACULTY
More informationTotal Quality Management in the Malaysian Automobile Industry
Total Quality Management in the Malaysian Automobile Industry Ismah Osman Faculty of Business Management, Universiti Teknologi MARA 40450, Shah Alam, Selangor, Malaysia Tel: 60-3-554-4446 E-mail: ismah817@salam.uitm.edu.my
More informationHow To Model Software Development Life Cycle Models
Various Software Development Life Cycle Models Sahil Jindal, Puneet Gulati, Praveen Rohilla Dronacharya College of Engineering, India Abstract:An SDLC model is a conceptual framework describing different
More informationClassical Software Life Cycle Models
Classical Software Life Cycle Models SWEN 301 Trimester 1, 2015 Lecturer: Dr Hui Ma Engineering and Computer Science Lecture slides make use of material provided on the textbook's companion website Motivation
More informationFuture of CMM and Quality Improvement. Roy Ko Hong Kong Productivity Council
Future of CMM and Quality Improvement Roy Ko Hong Kong Productivity Council 1 Agenda Future Development of CMMI CMMI and Small Organizations CMMI and Agile Development Good Enough Quality CMMI and Other
More informationCHAPTER 3 : AGILE METHODOLOGIES. 3.3 Various Agile Software development methodologies. 3.4 Advantage and Disadvantage of Agile Methodology
CHAPTER 3 : AGILE METHODOLOGIES 3.1Introductions 3.2 Main Stages in Agile project 3.3 Various Agile Software development methodologies 3.4 Advantage and Disadvantage of Agile Methodology 3.1Introductions
More informationThe Changing Role of Software Tester
The Changing Role of Software Tester Anna Royzman ari16a@gmail.com Abstract In 2008 my company reorganized into product units and adopted Agile process methodology. As a result, my QA manager position
More informationPlan-Driven Methodologies
Plan-Driven Methodologies The traditional way to develop software Based on system engineering and quality disciplines (process improvement) Standards developed from DoD & industry to make process fit a
More informationWeb Application Development Process
Web Engineering Web Application Development Process Copyright 2013 Ioan Toma & Srdjan Komazec 1 Where we are? # Date Title 1 5 th March Web Engineering Introduction and Overview 2 12 th March Requirements
More informationWaterfall vs. Agile Methodology
2012 Waterfall vs. Agile Methodology Mike McCormick MPCS, Inc. Revised Edition 8/9/2012 Contents Waterfall vs. Agile Model Comparison...3 Conceptual Difference...3 Efficiency...4 Suitability...4 Waterfall
More informationModellistica Medica. Maria Grazia Pia, INFN Genova. Scuola di Specializzazione in Fisica Sanitaria Genova Anno Accademico 2002-2003
Modellistica Medica Maria Grazia Pia INFN Genova Scuola di Specializzazione in Fisica Sanitaria Genova Anno Accademico 2002-2003 Lezione 18-19 The Unified Process Static dimension Glossary UP (Unified
More informationUS ONSHORING OFFERS SUPERIOR EFFECTIVENESS OVER OFFSHORE FOR CRM IMPLEMENTATIONS
US ONSHORING OFFERS SUPERIOR EFFECTIVENESS OVER OFFSHORE FOR CRM IMPLEMENTATIONS Whitepaper Eagle Creek Software Services March 2015 Introduction CRM services are shifting from a focus on point solution
More informationQuality Assurance Software Development Processes
Quality Assurance Software Development Processes Part II - Lecture 3 1 The University of Auckland New Zealand 254 12/09/ /2012 The FBI Virtual Case File 254 12/09/ /2012 Database application developed
More informationSoftware Process Improvement Framework for Software Outsourcing Based On CMMI Master of Science Thesis in Software Engineering and Management
Software Process Improvement Framework for Software Outsourcing Based On CMMI Master of Science Thesis in Software Engineering and Management ZAHOOR UL ISLAM XIANZHONG ZHOU University of Gothenburg Chalmers
More informationUnit 1 Learning Objectives
Fundamentals: Software Engineering Dr. Rami Bahsoon School of Computer Science The University Of Birmingham r.bahsoon@cs.bham.ac.uk www.cs.bham.ac.uk/~rzb Office 112 Y9- Computer Science Unit 1. Introduction
More informationSystem Software Product Line
System Software Product Line 2 1 Introduction The concept of Software Product Lines has been developed for more than a decade. Being initially an academic topic, product lines are more and more incorporated
More informationMTAT.03.243 Software Engineering Management
MTAT.03.243 Software Engineering Management Lecture 17: Other SPI Frameworks and QM Systems Dietmar Pfahl Spring 2014 email: dietmar.pfahl@ut.ee Structure of Lecture 17 Other SPI Frameworks People CMM
More informationAgile Projects 7. Agile Project Management 21
Contents Contents 1 2 3 Agile Projects 7 Introduction 8 About the Book 9 The Problems 10 The Agile Manifesto 12 Agile Approach 14 The Benefits 16 Project Components 18 Summary 20 Agile Project Management
More informationApplication of software product quality international standards through software development life cycle
Central Page 284 of 296 Application of software product quality international standards through software development life cycle Mladen Hosni, Valentina Kirinić Faculty of Organization and Informatics University
More informationWhat CMMI Cannot Give You: Good Software
What CMMI Cannot Give You: Good Software Ivar Jacobson ivar@ivarjacobson.com ivar@jaczone.com Objective To understand what CMM/CMMI is and what it is not To demonstrate how the unified process helps you
More informationSupporting Workflow Overview. CSC532 Fall06
Supporting Workflow Overview CSC532 Fall06 Objectives: Supporting Workflows Define the supporting workflows Understand how to apply the supporting workflows Understand the activities necessary to configure
More informationCS 389 Software Engineering. Lecture 2 Chapter 2 Software Processes. Adapted from: Chap 1. Sommerville 9 th ed. Chap 1. Pressman 6 th ed.
CS 389 Software Engineering Lecture 2 Chapter 2 Software Processes Adapted from: Chap 1. Sommerville 9 th ed. Chap 1. Pressman 6 th ed. Topics covered Software process models Process activities Coping
More informationGlobal Delivery Excellence Best Practices for Improving Software Process and Tools Adoption. Sunil Shah Technical Lead IBM Rational
Global Delivery Excellence Best Practices for Improving Software Process and Tools Adoption Sunil Shah Technical Lead IBM Rational Agenda Organization s Challenges from a Delivery Perspective Introduction
More informationOn Project Management Process in Agile Systems Development Methodologies and the ISO/IEC 29110 Standard (Entry Profile)
On Project Management Process in Agile Systems Development Methodologies and the ISO/IEC 29110 Standard (Entry Profile) Sergio Galván-Cruz 1, Manuel Mora 2,, Rory O Connor 3, Francisco Acosta-Escalante
More informationHow To Analyze The Performance Of Voip Internet Telephony Based On Quality Of Service (Qos)
looooo 3(p S 36 MARA University of Technology AN ANALYSIS OF VOIP INTERNET TELEPHONY PERFORMANCE BASED ON QUALITY OF SERVICE (QoS) NORFADZILAH BINTIABD MANAP Thesis submitted in fulfilment of the requirements
More informationDefinitions, reuse and technology: How context impacts technology support for knowledge management.
Definitions, reuse and technology: How context impacts technology support for knowledge management. Vanessa Freke, B.InfoTech (Hons) Institute for Integrated and Intelligent Systems School of Information
More informationTransitioning from Waterfall to Agile Course AG01; 3 Days, Instructor-led
Transitioning from Waterfall to Agile Course AG01; 3 Days, Instructor-led Course Description Identify the challenges you will face when implementing an Agile approach to software development and then plan
More information2. Analysis, Design and Implementation
2. Subject/Topic/Focus: Software Production Process Summary: Software Crisis Software as a Product: From Individual Programs to Complete Application Systems Software Development: Goals, Tasks, Actors,
More informationHow To Design An Information System
Information system for production and mounting of plastic windows MARCEL, MELIŠ Slovak University of Technology - Faculty of Material Sciences and Technology in Trnava, Paulínska 16 street, Trnava, 917
More informationRUP for Software Development Projects
RUP for Software Development Projects George Merguerian www.bmc-online.com 1 Specialists in Global Project Management Brussels Frankfurt Houston Istanbul Milan Ottawa Shanghai Singapore Warsaw Washington
More informationREGULATIONS AND CURRICULUM FOR THE MASTER S PROGRAMME IN INFORMATION ARCHITECTURE FACULTY OF HUMANITIES AALBORG UNIVERSITY
REGULATIONS AND CURRICULUM FOR THE MASTER S PROGRAMME IN INFORMATION ARCHITECTURE FACULTY OF HUMANITIES AALBORG UNIVERSITY SEPTEMBER 2015 Indhold PART 1... 4 PRELIMINARY REGULATIONS... 4 Section 1 Legal
More informationRISK MANAGEMENT OVERVIEW - APM Project Pathway (Draft) RISK MANAGEMENT JUST A PART OF PROJECT MANAGEMENT
RISK MANAGEMENT OVERVIEW - APM Project Pathway (Draft) Risk should be defined as An uncertain event that, should it occur, would have an effect (positive or negative) on the project or business objectives.
More informationEMPIRICAL STUDY ON CAPABILITY MATURITY MODEL INTEGRATION (CMMI) FRAMEWORK IMPLEMENTATION INSTITUT PENGURUSAN PENYELIDIKAN UNIVERSITI TEKNOLOGI MARA
EMPIRICAL STUDY ON CAPABILITY MATURITY MODEL INTEGRATION (CMMI) FRAMEWORK IMPLEMENTATION INSTITUT PENGURUSAN PENYELIDIKAN UNIVERSITI TEKNOLOGI MARA 40450 SHAH ALAM, SELANGOR MALAYSIA BY: SHUKOR SANIM BIN
More informationCertificate IV in Frontline Management
MARCH 2011 Certificate IV in Frontline Management Ai Group is pleased to provide you with information regarding the Certificate IV in Frontline Management - BSB40807. BENEFITS OF TRAINING Effective training
More informationSoftware Engineering for Software-Intensive Systems: III The Development Life Cycle
Software Engineering for Software-Intensive Systems: III The Development Life Cycle Assistant Professor Dr. Room E 3.165 Tel. 60-3321 Email: hg@upb.de Outline I Introduction II Foundations III The Development
More information218 Chapter 11. Conclusions. Therefore, this thesis aims to contribute to improving productivity of SMEs through DM and Project Communication.
218 Chapter 11. Conclusions 11. Conclusions 11.1. General conclusions The final objective of whatever research is to improve the knowledge and provide tools to improve it. In whatever company and in whatever
More informationSoftware Life Cycle. Main issues: Discussion of different life cycle models Maintenance or evolution
Software Life Cycle Main issues: Discussion of different life cycle models Maintenance or evolution Not this life cycle SE, Software Lifecycle, Hans van Vliet, 2008 2 Introduction software development
More informationCHAPTER. Software Process Models
CHAPTER Software Process Models 4 Chapter Objectives Introduce the generic concept of software engineering process models. Discuss the three traditional process models. Waterfall Incremental Spiral Discuss
More informationWhere in the curriculum is the right place for teaching agile methods?
Citace: BUCHALCEVOVÁ, Alena. Where in the curriculum is the right place for teaching agile methods? Prague 20.08.2008 22.08.2008. In: Proceedings 6th ACIS International Conference on Software Engineering
More informationSoftware Development Process Selection Approaches
The Journal of Applied Science Vol. 11 No. Vol. 2:45-50 11 No. 2 [2012] ISSN 1513-7805 Printed in Thailand Review Article Software Development Process Selection Approaches Phongphan Danphitsanuphan Department
More informationCUSTOMER RELATIONSHIP MANAGEMENT AND ITS INFLUENCE ON CUSTOMER LOYALTY AT LIBERTY LIFE IN SOUTH AFRICA. Leon du Plessis MINOR DISSERTATION
CUSTOMER RELATIONSHIP MANAGEMENT AND ITS INFLUENCE ON CUSTOMER LOYALTY AT LIBERTY LIFE IN SOUTH AFRICA by Leon du Plessis MINOR DISSERTATION Submitted in partial fulfilment of the requirements for the
More informationLearning Module On Effective. Communication. In Nursing Management
Learning Module On Effective Communication In Nursing Management Prepared by: Mona AL-Aseeri Supervised by: Prof.Dr. Soheir Mokabel EffectiveCommunication... It is two way. It involves active listening.
More informationA. Waterfall Model - Requirement Analysis. System & Software Design. Implementation & Unit Testing. Integration & System Testing.
Processing Models Of SDLC Mrs. Nalkar Sanjivani Baban Asst. Professor, IT/CS Dept, JVM s Mehta College,Sector 19, Airoli, Navi Mumbai-400708 Nalkar_sanjivani@yahoo.co.in Abstract This paper presents an
More informationLECTURE # 2. 4 P s in Project Management
SOFTWARE PROJECT MANAGEMENT LECTURE # 2 4 P s in Project Management 15 th September, 2011 Contact Information 2 Instructor: Lecturer Department of Software Engineering U.E.T Taxila Email: ali.javed@uettaxila.edu.pk
More information