'n Raamwerk vir die bestuur van koste tydens programmatuurontwikkeling
- Authors: Loubser, Hennie
- Date: 2015-03-17
- Subjects: Software engineering , Software engineering - Management
- Type: Thesis
- Identifier: uj:13430 , http://hdl.handle.net/10210/13467
- Description: M.Com. (Informatics) , Research into formalised methods for software engineering has resulted in many solutions to the known problems of software development. One of these problems is the difficulty involved In managing the cost of software development. Though attempts are made to solve the problem of budget and schedule overruns during project management, there still seems to be a lack of useful formal methods and approaches. In this dissertation such a formalised approach is presented. This approach Is based on the principle that cost should be actively managed just like any other aspect of software development. Within this framework the management of cost is defined as a process of identifying, estimating, measuring and controlling those factors that Influence the cost of development. Many methods exists through which the estimation of cost can be facilitated. The fact that such methods are available does not seem to solve the problem because cost management Involves more than just cost estimation. The research done to formalise this approach includes a discussion on the background of software engineering and the state of the science. It also includes an investigation Into the use of development metrics. The cost of software development is analyzed to determine the influence of different environmental factors on cost. A few estimation models are also discussed to determine the useability of such methods during cost management. A synopsis of how these subjects are covered In this dissertation is as follows: Chapter one serves as an Introduction to the research by giving a background to the development of software engineering. The limitations of current practices are emphasized and certain research questions are formulated. Chapter two discusses formal methods of development in the form of process models as a basis for the management of development cost. This chapter also analyzes development metrics as a method of measurement during development and cost management. The analysis provides as a framework for the identification and application of metrics during the process of cost management. Chapter three defines the extent of development cost and analyzes all factors contributing to the cost of software. The chapter discusses each of these factors by examining the possible influence of each on the effort of development and the Interdependence of these factors. Chapter four discusses a case study to be applied during discussions In the rest of the dissertation. Chapter five examines different approaches to the estimation of software development cost. The chapter serves as an introduction to subsequent chapters that deal with specific estimation models. Chapter six discusses an estimation model developed by Blokdijk. The chapter gives an overview of the principles Involved in and the application of the model.
- Full Text:
- Authors: Loubser, Hennie
- Date: 2015-03-17
- Subjects: Software engineering , Software engineering - Management
- Type: Thesis
- Identifier: uj:13430 , http://hdl.handle.net/10210/13467
- Description: M.Com. (Informatics) , Research into formalised methods for software engineering has resulted in many solutions to the known problems of software development. One of these problems is the difficulty involved In managing the cost of software development. Though attempts are made to solve the problem of budget and schedule overruns during project management, there still seems to be a lack of useful formal methods and approaches. In this dissertation such a formalised approach is presented. This approach Is based on the principle that cost should be actively managed just like any other aspect of software development. Within this framework the management of cost is defined as a process of identifying, estimating, measuring and controlling those factors that Influence the cost of development. Many methods exists through which the estimation of cost can be facilitated. The fact that such methods are available does not seem to solve the problem because cost management Involves more than just cost estimation. The research done to formalise this approach includes a discussion on the background of software engineering and the state of the science. It also includes an investigation Into the use of development metrics. The cost of software development is analyzed to determine the influence of different environmental factors on cost. A few estimation models are also discussed to determine the useability of such methods during cost management. A synopsis of how these subjects are covered In this dissertation is as follows: Chapter one serves as an Introduction to the research by giving a background to the development of software engineering. The limitations of current practices are emphasized and certain research questions are formulated. Chapter two discusses formal methods of development in the form of process models as a basis for the management of development cost. This chapter also analyzes development metrics as a method of measurement during development and cost management. The analysis provides as a framework for the identification and application of metrics during the process of cost management. Chapter three defines the extent of development cost and analyzes all factors contributing to the cost of software. The chapter discusses each of these factors by examining the possible influence of each on the effort of development and the Interdependence of these factors. Chapter four discusses a case study to be applied during discussions In the rest of the dissertation. Chapter five examines different approaches to the estimation of software development cost. The chapter serves as an introduction to subsequent chapters that deal with specific estimation models. Chapter six discusses an estimation model developed by Blokdijk. The chapter gives an overview of the principles Involved in and the application of the model.
- Full Text:
A case study in the management of engineering software design
- Authors: Kruger, Wynand
- Date: 2012-03-05
- Subjects: Computer software , Software engineering
- Type: Thesis
- Identifier: uj:2120 , http://hdl.handle.net/10210/4489
- Description: M.Ing.
- Full Text:
- Authors: Kruger, Wynand
- Date: 2012-03-05
- Subjects: Computer software , Software engineering
- Type: Thesis
- Identifier: uj:2120 , http://hdl.handle.net/10210/4489
- Description: M.Ing.
- Full Text:
A new perspective and a framework for software generation
- Authors: De la Harpe, Margaretha
- Date: 2012-08-17
- Subjects: Computer software - Development , Software engineering
- Type: Thesis
- Identifier: uj:2645 , http://hdl.handle.net/10210/6090
- Description: M.Sc. , The following questions led to this study: Why are there still so many approaches to the software generation process without one single approach taking the lead? Not only are there several methodologies available for the software generation process, but a methodology is not in use for long before it is replaced by an improved version or even another methodology. This is as a result of continuing further development and research. Sometimes the new methodology is not necessarily an improvement, but a paradigm shift. An example of this is object-orientation which followed shortly after the introduction of CASE as an alternative to software generation. Why are users to a large extent still dissatisfied and disillusioned with the software generation process even though they are more involved with it than before? User are more involved in the software generation process as a result of the availability of sophisticated tools, as well as joint sessions with the developer during the analysis and design stages of the software generation process. Yet, despite this, software systems in most cases still do not perform according to users' expectations. Why did the use of formal methodologies, based on successful techniques of the engineering field, only result in a limited improvement of the quality, control and operationalization of the software system? The cost of maintenance is still very high in relation to the total cost of generating a software system. The same degree of success attained in, say, the engineering field, could not be achieved [AND I]. Why is there a simultaneous movement towards incremental approaches and formal methods although these approaches are really moving in opposite directions? The incremental approach is based on obtaining quick results through prototyping without necessarily following a formal methodology [AND2]. Formal methods, on the other hand, attempt to formalize the software generation process through mathematical transformations. The advantage of using these mathematical transformations is that automation and verification of processes can be achieved [McC1]. Both these approaches show promising results, but the incremental approach might suit the developer better and is already used widely by practitioners. Why is it so difficult to find the correct methodology for generating a software system? The selection of an appropriate methodology is extremely difficult because of the variety of methodologies, technologies and hardware available. Some methodologies are also used for only a limited period because of rapid advances in technology. Why do sophisticated and user-friendly tools not succeed in simplifying the software generation process? Despite sophisticated tools such as CASE, where the user of these tools is guided through the different steps of the methodology, these tools have not succeeded in delivering the results expected by industry. The problems experienced during the software generation process are investigated. In order to distinguish between different approaches to software generation, is it necessary to place different approaches in relation to one another by considering the different elements of each. The characteristics and constraints of the software generation process must also be considered. All the issues pertaining to the software generation process will be discussed in terms of the problem statement.
- Full Text:
- Authors: De la Harpe, Margaretha
- Date: 2012-08-17
- Subjects: Computer software - Development , Software engineering
- Type: Thesis
- Identifier: uj:2645 , http://hdl.handle.net/10210/6090
- Description: M.Sc. , The following questions led to this study: Why are there still so many approaches to the software generation process without one single approach taking the lead? Not only are there several methodologies available for the software generation process, but a methodology is not in use for long before it is replaced by an improved version or even another methodology. This is as a result of continuing further development and research. Sometimes the new methodology is not necessarily an improvement, but a paradigm shift. An example of this is object-orientation which followed shortly after the introduction of CASE as an alternative to software generation. Why are users to a large extent still dissatisfied and disillusioned with the software generation process even though they are more involved with it than before? User are more involved in the software generation process as a result of the availability of sophisticated tools, as well as joint sessions with the developer during the analysis and design stages of the software generation process. Yet, despite this, software systems in most cases still do not perform according to users' expectations. Why did the use of formal methodologies, based on successful techniques of the engineering field, only result in a limited improvement of the quality, control and operationalization of the software system? The cost of maintenance is still very high in relation to the total cost of generating a software system. The same degree of success attained in, say, the engineering field, could not be achieved [AND I]. Why is there a simultaneous movement towards incremental approaches and formal methods although these approaches are really moving in opposite directions? The incremental approach is based on obtaining quick results through prototyping without necessarily following a formal methodology [AND2]. Formal methods, on the other hand, attempt to formalize the software generation process through mathematical transformations. The advantage of using these mathematical transformations is that automation and verification of processes can be achieved [McC1]. Both these approaches show promising results, but the incremental approach might suit the developer better and is already used widely by practitioners. Why is it so difficult to find the correct methodology for generating a software system? The selection of an appropriate methodology is extremely difficult because of the variety of methodologies, technologies and hardware available. Some methodologies are also used for only a limited period because of rapid advances in technology. Why do sophisticated and user-friendly tools not succeed in simplifying the software generation process? Despite sophisticated tools such as CASE, where the user of these tools is guided through the different steps of the methodology, these tools have not succeeded in delivering the results expected by industry. The problems experienced during the software generation process are investigated. In order to distinguish between different approaches to software generation, is it necessary to place different approaches in relation to one another by considering the different elements of each. The characteristics and constraints of the software generation process must also be considered. All the issues pertaining to the software generation process will be discussed in terms of the problem statement.
- Full Text:
Cost estimation methods for software engineering
- Authors: Ladeira, Andre
- Date: 2012-03-05
- Subjects: Software engineering , Computer software , Cost estimates
- Type: Mini-Dissertation
- Identifier: uj:2133 , http://hdl.handle.net/10210/4500
- Description: M.Eng. (Engineering Management). , This dissertation summarizes several classes of software cost estimation models and techniques. Experience to date indicates that expertise-based techniques are less mature than the other classes of techniques (algorithmic models), but that all classes of techniques are challenged by the rapid pace of change in software technology. The primary conclusion is that no single technique is best for all situations, and that a careful comparison of the results of several approaches is most likely to produce realistic estimates. As more pressure on accurate cost estimation increase, research attention is now directed at gaining a better understanding of the software-engineering process as wall as constructing and evaluating software cost estimation tools. This dissertation evaluated four of the most popular algorithmic models used to estimate software cost (SLIM, COCOMO II, Function points and SLOC) This dissertation also provides an overview of the baseline cost estimation model tailored to these new forms of software engineering. The major new modeling capabilities are an adaptable family of software sizing models, involving Function Points and Source Lines of Code. These models are serving as a framework for an extensive current data collection and analysis effort to further refine and calibrate the model's estimation capabilities.
- Full Text:
- Authors: Ladeira, Andre
- Date: 2012-03-05
- Subjects: Software engineering , Computer software , Cost estimates
- Type: Mini-Dissertation
- Identifier: uj:2133 , http://hdl.handle.net/10210/4500
- Description: M.Eng. (Engineering Management). , This dissertation summarizes several classes of software cost estimation models and techniques. Experience to date indicates that expertise-based techniques are less mature than the other classes of techniques (algorithmic models), but that all classes of techniques are challenged by the rapid pace of change in software technology. The primary conclusion is that no single technique is best for all situations, and that a careful comparison of the results of several approaches is most likely to produce realistic estimates. As more pressure on accurate cost estimation increase, research attention is now directed at gaining a better understanding of the software-engineering process as wall as constructing and evaluating software cost estimation tools. This dissertation evaluated four of the most popular algorithmic models used to estimate software cost (SLIM, COCOMO II, Function points and SLOC) This dissertation also provides an overview of the baseline cost estimation model tailored to these new forms of software engineering. The major new modeling capabilities are an adaptable family of software sizing models, involving Function Points and Source Lines of Code. These models are serving as a framework for an extensive current data collection and analysis effort to further refine and calibrate the model's estimation capabilities.
- Full Text:
Die integrering van inligtingsekerheid met programmatuuringenieurswese
- Booysen, Hester Aletta Susanna
- Authors: Booysen, Hester Aletta Susanna
- Date: 2014-11-20
- Subjects: Computer security , Software engineering , Computer networks - Security measures
- Type: Thesis
- Identifier: uj:13039 , http://hdl.handle.net/10210/12921
- Description: M.Com. (Informatiks) , Please refer to full text to view abstract
- Full Text:
- Authors: Booysen, Hester Aletta Susanna
- Date: 2014-11-20
- Subjects: Computer security , Software engineering , Computer networks - Security measures
- Type: Thesis
- Identifier: uj:13039 , http://hdl.handle.net/10210/12921
- Description: M.Com. (Informatiks) , Please refer to full text to view abstract
- Full Text:
Funksionele benadering tot rekenaargesteunde programmatuuringenieurswese
- Authors: Toerien, Nelie
- Date: 2015-03-17
- Subjects: Software engineering
- Type: Thesis
- Identifier: uj:13431 , http://hdl.handle.net/10210/13468
- Description: M.Sc. (Computer Science) , Since the late 1980's CASE ("Computer-Aided Software Engineering") is a common concept in the world of information technology. Nevertheless, many people in the information technology environment do not know what CASE is, or have different concepts about CASE. The author also found a variety of definitions for CASE in literature. This variety of concepts and definitions was the first problem the author investigated. Although many people know about CASE, companies are slow in adopting CASE and the tools are not used to their full potential. This was the second problem the author investigated. To address these problems, the research is divided in two logical parts. The author initiated this study with literature research regarding CASE in which the above mentioned problems were identified. The author found the solution to the first problem in literature and by attending CASE conferences. Guidelines to help with the second problem was derived from bits and pieces of information found in literature regarding the installation and use of CASE tools. It was also derived from practical experience during the last six months of study at a company busy with the installation of a CASE tool. To address the first problem, the different aspects surrounding CASE was investigated. The author tried to provide answers to the following questions: What is CASE? What is the logical components and functions of CASE? How can CASE be classified? CASE and integration - what is the difference between CASE, I-CASE and IPSE? Where does CASE fit in the software environment? In the last chapter of this first part, AD/Cycle from IBM (ISM in South Africa) is discussed as an industry standard for the CASE environment. To address the second problem, the author proposed a methodology covering the initiation phase to the maintenance phase of the implementation of CASE tools in a company. The methodology consists of four phases, namely, initiation, evaluation and selection, installation and training, and maintenance. In the initiation phase, the use of CASE tools to solve system development problems like the system backlog, bad productivity and poor system quality, are initiated. In the evaluation and selection phase, the different vendors and products on the market are evaluated against the needs of the company. The product which was the best suited for those needs was selected and acquired. In the installation and training phase, that product was installed in the information technology environment ...
- Full Text:
- Authors: Toerien, Nelie
- Date: 2015-03-17
- Subjects: Software engineering
- Type: Thesis
- Identifier: uj:13431 , http://hdl.handle.net/10210/13468
- Description: M.Sc. (Computer Science) , Since the late 1980's CASE ("Computer-Aided Software Engineering") is a common concept in the world of information technology. Nevertheless, many people in the information technology environment do not know what CASE is, or have different concepts about CASE. The author also found a variety of definitions for CASE in literature. This variety of concepts and definitions was the first problem the author investigated. Although many people know about CASE, companies are slow in adopting CASE and the tools are not used to their full potential. This was the second problem the author investigated. To address these problems, the research is divided in two logical parts. The author initiated this study with literature research regarding CASE in which the above mentioned problems were identified. The author found the solution to the first problem in literature and by attending CASE conferences. Guidelines to help with the second problem was derived from bits and pieces of information found in literature regarding the installation and use of CASE tools. It was also derived from practical experience during the last six months of study at a company busy with the installation of a CASE tool. To address the first problem, the different aspects surrounding CASE was investigated. The author tried to provide answers to the following questions: What is CASE? What is the logical components and functions of CASE? How can CASE be classified? CASE and integration - what is the difference between CASE, I-CASE and IPSE? Where does CASE fit in the software environment? In the last chapter of this first part, AD/Cycle from IBM (ISM in South Africa) is discussed as an industry standard for the CASE environment. To address the second problem, the author proposed a methodology covering the initiation phase to the maintenance phase of the implementation of CASE tools in a company. The methodology consists of four phases, namely, initiation, evaluation and selection, installation and training, and maintenance. In the initiation phase, the use of CASE tools to solve system development problems like the system backlog, bad productivity and poor system quality, are initiated. In the evaluation and selection phase, the different vendors and products on the market are evaluated against the needs of the company. The product which was the best suited for those needs was selected and acquired. In the installation and training phase, that product was installed in the information technology environment ...
- Full Text:
Integration of a CASE tool and a software engineering methodology
- Authors: Hertenberger, Manfred Paul
- Date: 2015-03-17
- Subjects: Computer-aided software engineering , Software engineering
- Type: Thesis
- Identifier: uj:13436 , http://hdl.handle.net/10210/13473
- Description: M.Sc. (Computer Science) , This study addresses the topic of integration between CASE tools and software engineering methodologies. Specific attention is given to the object-oriented paradigm to solve the problem of integration. The component developed in this study to handle the integration is the so-called feedback loop mechanism. The feedback loop is the focus of the study. A number of CASE tools are available today. These tools help developers achieve specific aims and to solve specific problems. Similarly, a number of different software development methodologies abound. Due to the fact that these methodologies are usually not specific to the use of CASE tools, these methodologies can be used for a variety of development environments. The problem addressed by this study is the direct integration of CASE tools and software engineering methodologies. A number of studies have been carried out with regard to both CASE tools and software engineering methodologies. A discussion of current trends in both the CASE tool and methodology arenas is presented at the beginning of this study. Also, the problems experienced with more traditional approaches are discussed. Given that the feedback loop mechanism is developed during the course of this study, a detailed discussion is presented regarding the components to be used in the construction of the feedback loop. The object-oriented paradigm is presented as the best solution to the integration problem. In fact, the object-oriented paradigm forms the core of the feedback loop. By making use of the object-oriented approach, the processes involved in the integration of the CASE tool and the methodology may be mapped accurately. Repository structures such as relational tables and stored procedures, or triggers, are also used in the construction of the feedback loop...
- Full Text:
- Authors: Hertenberger, Manfred Paul
- Date: 2015-03-17
- Subjects: Computer-aided software engineering , Software engineering
- Type: Thesis
- Identifier: uj:13436 , http://hdl.handle.net/10210/13473
- Description: M.Sc. (Computer Science) , This study addresses the topic of integration between CASE tools and software engineering methodologies. Specific attention is given to the object-oriented paradigm to solve the problem of integration. The component developed in this study to handle the integration is the so-called feedback loop mechanism. The feedback loop is the focus of the study. A number of CASE tools are available today. These tools help developers achieve specific aims and to solve specific problems. Similarly, a number of different software development methodologies abound. Due to the fact that these methodologies are usually not specific to the use of CASE tools, these methodologies can be used for a variety of development environments. The problem addressed by this study is the direct integration of CASE tools and software engineering methodologies. A number of studies have been carried out with regard to both CASE tools and software engineering methodologies. A discussion of current trends in both the CASE tool and methodology arenas is presented at the beginning of this study. Also, the problems experienced with more traditional approaches are discussed. Given that the feedback loop mechanism is developed during the course of this study, a detailed discussion is presented regarding the components to be used in the construction of the feedback loop. The object-oriented paradigm is presented as the best solution to the integration problem. In fact, the object-oriented paradigm forms the core of the feedback loop. By making use of the object-oriented approach, the processes involved in the integration of the CASE tool and the methodology may be mapped accurately. Repository structures such as relational tables and stored procedures, or triggers, are also used in the construction of the feedback loop...
- Full Text:
Strategic quality: a software engineering approach
- Authors: Van Staden, Roelof Johannes
- Date: 2009-02-27T06:04:11Z
- Subjects: Software engineering , Software measurement , Quality of products , Total quality management , Strategic planning
- Type: Thesis
- Identifier: uj:8188 , http://hdl.handle.net/10210/2192
- Description: M.Ing. , Software engineering organizations face a struggle for daily survival in an extremely volatile climate. Numerous times it has been shown that the quality of a service or product could make the difference between an organization existing or closing down. The way in which quality is approached in any organization is part of a strategy; unbeknown to the managers and employees in many instances. Even though there are numerous books, articles, internet sites and other sources devoted to the subject of quality, total quality management, and strategic planning, not many of these information sources link quality and the strategy of the organization in such a way as to consider the quality of the organization’s products and services to be a major factor of strategic survival – or even the very existence of the organization. Quality is known under various names and terms in organizations, these terms and definitions will be investigated to grasp the true meaning of software quality and strategy as it concerns modern software engineering organizations. The tools and techniques required to improve and measure strategy and quality will also be scrutinized. One dominant factor about quality and strategy should be borne in mind, and that is that these programs depend on teamwork and management support as the major underlying framework. There are many tools and techniques that leaders and members of software teams can employ, but one of the most important factors is to gain a picture of the total process of continuous improvement and measurement. For this reason the author has included a large section on Jack Welch, who managed to use continuous improvement techniques to create one of the best, and biggest international organizations in recent years. It is vital that all people realize that they need an improvement and measurement model, and they need guidance in using such a model. This dissertation investigates the reasoning behind implementing strategic quality processes in software engineering organizations. Following the investigation into the necessity for a quality strategy, the methods, processes, tools and techniques that are required for a strategic quality framework (improvement and measurement model) for software engineering organizations will be researched to provide a basic framework and guidance in implementing such a model.
- Full Text:
- Authors: Van Staden, Roelof Johannes
- Date: 2009-02-27T06:04:11Z
- Subjects: Software engineering , Software measurement , Quality of products , Total quality management , Strategic planning
- Type: Thesis
- Identifier: uj:8188 , http://hdl.handle.net/10210/2192
- Description: M.Ing. , Software engineering organizations face a struggle for daily survival in an extremely volatile climate. Numerous times it has been shown that the quality of a service or product could make the difference between an organization existing or closing down. The way in which quality is approached in any organization is part of a strategy; unbeknown to the managers and employees in many instances. Even though there are numerous books, articles, internet sites and other sources devoted to the subject of quality, total quality management, and strategic planning, not many of these information sources link quality and the strategy of the organization in such a way as to consider the quality of the organization’s products and services to be a major factor of strategic survival – or even the very existence of the organization. Quality is known under various names and terms in organizations, these terms and definitions will be investigated to grasp the true meaning of software quality and strategy as it concerns modern software engineering organizations. The tools and techniques required to improve and measure strategy and quality will also be scrutinized. One dominant factor about quality and strategy should be borne in mind, and that is that these programs depend on teamwork and management support as the major underlying framework. There are many tools and techniques that leaders and members of software teams can employ, but one of the most important factors is to gain a picture of the total process of continuous improvement and measurement. For this reason the author has included a large section on Jack Welch, who managed to use continuous improvement techniques to create one of the best, and biggest international organizations in recent years. It is vital that all people realize that they need an improvement and measurement model, and they need guidance in using such a model. This dissertation investigates the reasoning behind implementing strategic quality processes in software engineering organizations. Following the investigation into the necessity for a quality strategy, the methods, processes, tools and techniques that are required for a strategic quality framework (improvement and measurement model) for software engineering organizations will be researched to provide a basic framework and guidance in implementing such a model.
- Full Text:
- «
- ‹
- 1
- ›
- »