Transactions on Information and Communications Technologies vol 11, 1995 WIT Press, ISSN
|
|
- Logan Roberts
- 6 years ago
- Views:
Transcription
1 An investigation of quality profiles for different types of software T. Musson," E. Dodman* * Department of Computer Studies, Napier University, 219 Colinton Road, Edinburgh, EH 14 1DJ, UK tim@dcs.napier.ac.uk School of Computing, Leeds Metropolitan University, The Grange, Beckett Park, Leeds, LS6 3QS, UK e.dodman@lmu.ac.uk ABSTRACT This paper describes some of the trends which may be seen in the development of software quality models and their interaction with the software development process. Based on these trends two hypotheses are presented: 1. it is possible to define the quality requirements for any software by selecting one from a standard set of models (a model includes a profile of desired quality attributes) 2. based on readily identifiable characteristics, software types can be identified for which a particular model will be appropriate Some of the implications of these hypotheses are explored and a brief description is given of ongoing work which is aimed at determining their validity and usefulness. INTRODUCTION Several major methodological decisions need to be made, more or less consciously, in the development of a software system. These include the lifecycle model to be used, design methods to be used and the quality model to be used (defining non-functional or quality attributes of importance and the way in which they will be measured). This paper considers a possible approach to making these decisions.
2 120 Software Quality Management BACKGROUND The first serious software quality models were developed in the late 70s, starting with the work of McCall et al [1] and of Boehm et al [2]. These were "general" models which assumed that quality is an attribute which can be hierarchically decomposed into a wide range of measurable components. The top-level "quality factors" (such as maintainability, reliability, usability), which are mainly external attributes, are decomposed through a series of levels to give "quality metrics" which may be measured directly and are commonly internal code attributes. These models assumed that the same set of factors and decomposition was appropriate for all software products. The problems associated with the early general quality models have been widely documented (e.g. by Kitchenham [3] and by Musson [4]). The main problem of these general models, their lack offlexibility,has been addressed more recently by work such as that of Gilb [5] and that of Kitchenham [3]: both of these approaches advocate, and give guidelines for, the development of a local quality model for each project. The models proposed are still general (based on a range of attributes) and still use hierarchical decomposition. Kitchenham's COQUAMO includes attributes which are: 1. common to most applications, but have a general definition (e.g. maintainability) 2. common to most applications, but need specific definition (e.g. usability) 3. specific to certain types of system (e.g. integrity) 4. closely related to development process (e.g. correctness) Criticising Kitchenham's approach, Roche and Jackson [6] state that "A predictive model should provide interpretation of metric values and recommend action to be taken within context of the development process". This suggests that, for any particular software project, it may be appropriate both to define a local quality model and to use it to determine certain aspects of the development process (quality assurance procedures, development methods, testing criteria, etc). The trend towards the development of local quality models has been continued by Delen and Rijsenbrij [7]. Their work specifies attributes for a particular type of system (information systems), but emphasises the need for local specification of the requirements for each attribute. Another interesting development in this direction is quality function deployment (Erikkson and McFadden, [8]), which involves mapping customer requirements onto software characteristics and, in turn, software characteristics onto production features. Some work has been carried out specifically on the selection of an appropriate software process model for a particular project (Alexander and Davis [9]). This work considered both aspects of the product itself (e.g. product size and complexity, "ility" requirements, such as usability reliability
3 Software Quality Management 121 maintainability) and of the project's environment (e.g. funds available, staff profile, user's experience). The choice of the 20 criteria used was based on a literature search and informal observation, with most being subjectively evaluated as, effectively, low, medium or high. The above discussion shows a trend towards local models (i.e. adapting the quality model to the software being produced) and towards adapting the process to attributes of the software. This trend is explicitly supported by Fuggetta and Ghezzi [10]: "In general, much work is still needed to better understand what is a realistic and effective characterization of different application domains and problems with respect to the variety of available process technologies" (p55). If we accept this as being an appropriate direction then there still remain the issues of how, for any particular project, the local model is determined and how it is to be used in determining the development process. The following sections of this paper hypothesise an approach, related to that of Alexander and Davis [9], to resolving these issues and explore its consequences. THE HYPOTHESES It is proposed that: 1. it is possible to define the quality requirements for any software product by selecting one from a standard set of models (a model includes a profile of desired quality attributes) 2. based on readily identifiable characteristics, software types can be identified for which a particular model will be appropriate A quality model is regarded as a quality profile, together with any definitions needed in order to measure quality attributes. A software quality profile is a ranking of quality attributes in order of importance. In defining a profile it is considered appropriate to use high-level attributes, such as: maintainability usability reusability portability reliability efficiency The definitions which accompany the profile will normally include hierarchical decomposition of the attributes and low level metrics to allow measurement. An initial questionnaire-based investigation of the hypotheses has not given the information needed to confirm them (Musson and Dodman, [11]). However, it did confirm that there is considerable confusion with respect to quality metrics in the software industry: many quality attributes which selected by software developers as most or very important were often measured either very crudely or not at all.
4 122 Software Quality Management The failure to reach any conclusions concerning the hypotheses is considered to be a result of: 1. the small number (23) of questionnaires returned, 2. the difficulties referred to at the end of the previous section concerning the realistic and effective characterisation of application domains Both of these issues are currently (December 1994) being addressed in a followup survey. The questionnaire being used asks software quality managers to describe, in terms of certain characteristics, a software product which has been developed recently by their company. They are also asked to indicate the important quality characteristics together with their assessment procedures and to summarise important features of the development process used. It is hoped that this survey will allow the identification of the standard set of quality models, together with appropriate software types related to them. In the next section some different ways in which software can be characterised are presented, and in each case suggestions are made for quality attributes which are likely to be considered important and possible implications for the development process. Software characteristics which are considered to be important include both the application domain and the application environment. SOFTWARE TYPES The following categories of software are not intended to form a taxonomy: they are certainly not mutually exclusive. They are candidate characteristics (individually or in tuples) for identifying the types hypothesised above. Batch vs Real-time Reliability is likely to be the most important attribute for both these categories of software (the authors' previous survey [11] has found that reliability is perceived as being the most important quality attribute for software in general), particularly for process control systems. For batch software maintainability is also expected to be very important, as, typically, it is run many times over a long time period in a continually evolving environment. Such software is usually developed using the standard waterfall life-cycle model, or some variation of it, and a method such as SSADM or Yourdon. Apart from reliability, attributes which are considered particularly important for real-time systems are usability and efficiency. Typically, process control systems incorporate user involvement in the control feedback loop and hence require good usability. Similarly file interrogation and transaction processing systems will require high levels of usability. For most of these systems, where user interaction is involved, time efficiency is important to avoid
5 Software Quality Management 123 user dissatisfaction - this becomes particularly important for process control, where process instability may be dangerous. For such systems, particularly those which are safety-critical, formal or semi-formal methods are likely to be appropriate for development, together with prototyping of the user interfaces Interactive vs non-interactive Usability is likely to be the most important attribute for interactive systems. Reliability is also likely to be important to an interactive user. This suggests that prototyping is likely to be important in the development process, allowing incremental development of the interface. A fairly formal approach to development (including the interface design) may be appropriate for the required reliability. Much interactive software is developed for use in a Windows environment. It is becoming normal to develop this making considerable use of standard libraries and object-oriented development. This facilitates development by encouraging considerable reuse of code and also makes it easier to conform to a standard interface style hence giving a greater level of usability. Goal-oriented vs Output-oriented The distinction between goal-oriented and output-oriented software has been made by Bull and Musson [12]. The essential difference is that the output of output-oriented software is seen as intrinsically useful (perhaps to be taken away as hard copy) whereas that from goal-oriented software is only considered useful in terms of supporting the user in achieving a goal. Traditional data processing systems tend to be very output-oriented whereas decision support systems, computer based learning environments and other knowledge-handling systems tend to be goal-oriented. Correctness will be an important attribute for most output-oriented systems whereas usability will be important for goal-oriented systems. A much more difficult aspect of the evaluation of goal-oriented systems concerns the assessment of the extent to which the user is supported in achieving the goal. This goes considerably beyond usability and requires an analysis of user behaviour and a comparison of the success in performing relevant tasks both using the system and either unsupported or using other systems. The development of output-oriented software is likely to be carried out using a conventional waterfall model life-cycle (or similar). However, the development of goal-oriented software should involve a high degree of prototyping, checking that the goal is being met at each stage of development: this can only be achieved by continually involving members of the target user group to obtain feedback into the development process.
6 124 Software Quality Management Long-lived vs Short-lived The expected lifetime of a software system can be expected to influence the required level of most quality attributes, particularly maintainability. Short lifetime systems will often be developed as cheaply as possible with a very low level of quality assurance: it is usually not considered worthwhile spending a great deal of money on achieving high quality levels for such systems. Such systems may well be produced with very little formal design and testing and a small amount of documentation. Appropriate development methods may include heavy reliance on reuse or modification of code from previous projects. Preliminary results from the survey currently being undertaken suggest that the importance attached to maintainability is directly related to the expected lifetime: companies producing software products for which a lifetime of around ten years is expected normally class maintainability as one of the two most important quality attributes, whereas for shorter lifetime products it does not always appear as a required attribute at all. DISCUSSION The previous section has given some potentially useful ways of characterising software products and has considered their implications in terms of expected desired quality attributes and development issues. There are many other ways in which software may be characterised: these include data processing, systems software, networked, decision support, expert system, computer based learning environment, market sector, safety-critical. The usefulness of these categories in the context of our hypotheses is an open research issue, however it seems fairly sure that some of them will be relevant The characteristic "safety-critical" implies a need for high reliability and this suggests that formal methods will be an appropriate technique. It is also anticipated that market sector will have a strong influence on the required quality attributes: this characteristic itself may be seen as having several components, including commercial sector, vertical vs horizontal and inhouse vs external user. The hypotheses themselves have arisen from a consideration of trends in the development of software quality models, in particular the movement from general, fixed models towards specific, locally-developed models. They have the potential for giving considerable guidance to software developers in terms of both appropriate development methods and quality models.
7 CONCLUSION Software Quality Management 125 It has become clear from recent work in the area that quality models and development methods should be defined locally in the context of a particular project. Suitable processes for defining these are still not clear. This paper has discussed one possible approach to this problem. Its validity is not yet established, however, survey work currently being undertaken is aimed at demonstrating this. Results from the survey are expected to be available by April ACKNOWLEDGEMENT The authors would like to express their gratitude to Professor Inger Eriksson for her constructive and valuable comments on an earlier draft of this paper. REFERENCES 1. McCall, J.A., Richards, P.K., Walters, G.F. 'Factors in Software Quality' Vols I, II, III. US Rome Air Development Center Reports NTIS AD/A ,015,055, Boehm, B.W., Brown, J.R., Kaspar, L.R., Lipow, M., MacCleod, G.J., Merrit, M.J. Characteristics of Software Quality. North Holland, Kitchenham, B. Towards a Constructive Quality Model. Part 1: Software Quality Modelling, Measurement and Prediction* Software Engineering Journal, Vol.2,4,ppl05-113, Musson, T. The Evaluation of Instructional Software Quality' Proceedings of SQM'94, Edinburgh, UK; Computational Mechanics Publications, Gilb, T. Principles of Software Engineering Management. Addison Wesley Roche, J. and Jackson, M. 'Software Measurement Methods: Recipes for success?' Information and Software Technology, Vol. 36, 3, pp!73-189, Delen, G.P.AJ. and Rijsenbrij, D.B.B. The Specification, Engineering, and Measurement of Information Systems Quality' Journal of Systems and Software, Vol 17, 3,pp , 1992.
8 126 Software Quality Management 8. Erikkson, I. and McFadden, F. 'Quality Function Deployment: a Tool to Improve Software Quality' Information and software Technology, Vol. 35, 9, pp , Alexander, L.C. and Davis, A.M. 'Criteria for Selecting Software Process Models' Proceedings of IEEE COMPSAC91, Washington DC, pp , IEEE Computer Press, Fuggetta, A. and Ghezzi, C. 'State of the Art and Open Issues in Process- Centered Software Engineering Environments' Journal of Systems and Software, Vol. 26, 1, pp53-60, Musson, T. and Dodman, E. 'An Investigation of Desired Quality Attributes for Different Types of Software' Proceedings of ICSQP'94, Hong Kong: Software Quality and Productivity: Theory, Practice, Education and Training, (Lee, M. et al, eds), Chapman and Hall, Bull, S. and Musson, T. 'Goal-Oriented Software: When the Development Process is Different...' Proceedings of SQM'94, Edinburgh, UK; Computational Mechanics Publications, 1994.
A prototype Web-based implementation of the QEST model
82 A prototype Web-based implementation of the QEST model Alain Abran 1, Martin Kunz 2, Reiner R. Dumke 2, Luigi Buglione 1 3 1 École de Technologie Supérieure - ETS 1100 Notre-Dame Ouest, Montréal, Canada
More informationANALYTICAL STUDY OF MAINTAINABILITY MODELS FOR QUALITY EVALUATION
ANALYTICAL STUDY OF MAINTAINABILITY MODELS FOR QUALITY EVALUATION Rimmi Saini Computer Science & Engineering Department,Greater Noida Institute of Engineering & Technology, Greater Noida,U.P., 201306,India
More informationUsability Evaluation as a Component of the OPEN Development Framework
Usability Evaluation as a Component of the OPEN Development Framework John Eklund Access Testing Centre and The University of Sydney 112 Alexander Street, Crows Nest NSW 2065 Australia johne@testingcentre.com
More informationEvaluation of Commercial Web Engineering Processes
Evaluation of Commercial Web Engineering Processes Andrew McDonald and Ray Welland Department of Computing Science, University of Glasgow, Glasgow, Scotland. G12 8QQ. {andrew, ray}@dcs.gla.ac.uk, http://www.dcs.gla.ac.uk/
More informationHarmonization of usability measurements in ISO9126 software engineering standards
Harmonization of usability measurements in ISO9126 software engineering standards Laila Cheikhi, Alain Abran and Witold Suryn École de Technologie Supérieure, 1100 Notre-Dame Ouest, Montréal, Canada laila.cheikhi.1@ens.etsmtl.ca,
More informationAn Approach to Software Component Specification
Page 1 of 5 An Approach to Software Component Specification Jun Han Peninsula School of Computing and Information Technology Monash University, Melbourne, Australia Abstract. Current models for software
More informationQuality and usability: A new framework
van Veenendaal, E, and McMullan, J (eds) Achieving software product quality, Tutein Nolthenius, Netherlands, 1997 Quality and usability: A new framework Nigel Bevan Usability Services National Physical
More informationHCI Research Methods
HCI Research Methods Ben Shneiderman ben@cs.umd.edu Founding Director (1983-2000), Human-Computer Interaction Lab Professor, Department of Computer Science Member, Institute for Advanced Computer Studies
More informationIntroduction to Software Engineering
Introduction to Software Engineering Gérald Monard Ecole GDR CORREL - April 16, 2013 www.monard.info Bibliography Software Engineering, 9th ed. (I. Sommerville, 2010, Pearson) Conduite de projets informatiques,
More informationAgile Accessibility. Presenters: Ensuring accessibility throughout the Agile development process
Agile Accessibility Ensuring accessibility throughout the Agile development process Presenters: Andrew Nielson, CSM, PMP, MPA Ann Marie Davis, CSM, PMP, M. Ed. Cammie Truesdell, M. Ed. Overview What is
More informationTowards Systematic Usability Verification
Towards Systematic Usability Verification Max Möllers RWTH Aachen University 52056 Aachen, Germany max@cs.rwth-aachen.de Jonathan Diehl RWTH Aachen University 52056 Aachen, Germany diehl@cs.rwth-aachen.de
More informationSoftware re-use assessment for quality M. Ramachandran School of Computing and Mathematical Sciences, Jo/m Moores C/mrerszZ?/,
Software re-use assessment for quality M. Ramachandran School of Computing and Mathematical Sciences, Jo/m Moores C/mrerszZ?/, ABSTRACT Reuse of software components can improve software quality and productivity
More informationFORMALIZED SOFTWARE DEVELOPMENT IN AN INDUSTRIAL ENVIRONMENT
FORMALIZED SOFTWARE DEVELOPMENT IN AN INDUSTRIAL ENVIRONMENT Otthein Herzog IBM Germany, Dept. 3100 P.O.Box 80 0880 D-7000 STUTTGART, F. R. G. ABSTRACT tn the IBM Boeblingen Laboratory some software was
More informationThe «SQALE» Models for assessing the Quality of Software Source Code
The «SQALE» Models for assessing the Quality of Software Source Code Quality Model and Analysis Model The need to assess and know the quality of the software one has required or payed for is not new. When
More informationTransactions on Information and Communications Technologies vol 4, 1993 WIT Press, ISSN
Use of quality characteristics graphs for a knowledge-based assistance in software quality management H. Basson, M.C. Haton, J.C. Derniame Centre de Recherche en Informatique de Nancy, BP 239, 54506 Vandoeuvre-les-Nancy,
More informationOverview of the course. User-Centred Design. Group. Practical issue. Writting the report. Project work. Fang Chen
Overview of the course User-Centred Design Fang Chen 6 lectures, 3 hr each. L 1: April 6, 9-12, user-centered design concept L2: April 14, 9-12, usability concept L3. user-centered requirement study L4.
More informationObject Oriented Measurement
Object Oriented Measurement Diego Chaparro González dchaparro@acm.org Student number: 59881P 17th January 2003 Abstract This document examines the state of art in software products measurement, with focus
More informationCh 1: The Architecture Business Cycle
Ch 1: The Architecture Business Cycle For decades, software designers have been taught to build systems based exclusively on the technical requirements. Software architecture encompasses the structures
More informationSystem Design and Modular Programming
CS3 Programming Methodology Lecture Note D1, 2 November 2000 System Design and Modular Programming System design involves meeting competing requirements and satisfying constraints on the system and the
More informationProvenance in Software Engineering - A Configuration Management View
Association for Information Systems AIS Electronic Library (AISeL) AMCIS 2005 Proceedings Americas Conference on Information Systems (AMCIS) 2005 Provenance in Software Engineering - A Configuration Management
More informationProduct Quality Engineering. RIT Software Engineering
Product Quality Engineering Q vs q Quality includes many more attributes than just absence of defects Features Performance Availability Safety Security Reusability Extensibility Modifiability Portability
More informationTopic 01. Software Engineering, Web Engineering, agile methodologies.
Topic 01 Software Engineering, Web Engineering, agile methodologies. 1 What is Software Engineering? 2 1 Classic Software Engineering The IEEE definition: Software Engineering is the application of a disciplined,
More informationA Logical Pattern for Integrating Business Intelligence into Information Systems Design
A Logical Pattern for Integrating Business Intelligence into Information Systems Design Stephen Opoku-Anokye and Yinshan Tang Informatics Research Centre, Business Informatics, Systems and Accounting,
More informationWork Environment and Computer Systems Development.
CID-133 ISSN 1403-0721 Department of Numerical Analysis and Computer Science KTH Work Environment and Computer Systems Development. Jan Gulliksen and Bengt Sandblad CID, CENTRE FOR USER ORIENTED IT DESIGN
More informationQUALITY METRICS IMPLEMENTATION IN COMPONENT BASED SOFTWARE ENGINEERING USING AI BACK PROPAGATION ALGORITHM SOFTWARE COMPONENT
I.J.E.M.S., VOL.3(2) 2012: 109-114 ISSN 2229-600X QUALITY METRICS IMPLEMENTATION IN COMPONENT BASED SOFTWARE ENGINEERING USING AI BACK PROPAGATION ALGORITHM SOFTWARE COMPONENT Sidhu Pravneet SPCET, Mohali,
More informationINTEGRATING DESIGN RATIONALE WITH A PROCESS MODEL
INTEGRATING DESIGN RATIONALE WITH A PROCESS MODEL J. E. BURGE, D. C. BROWN AI in Research Group Department of Computer Science WPI, 100 Institute Road Worcester, MA 01609, USA Abstract. One goal for having
More informationScenarios, Quality Attributes, and Patterns: Capturing and Using their Synergistic Relationships for Product Line Architectures
Scenarios, Quality Attributes, and Patterns: Capturing and Using their Synergistic Relationships for Product Line Architectures Muhammad Ali Babar National ICT Australia Ltd. and University of New South
More informationTaxonomy Governance Checklist
Author and Manage a SharePoint Taxonomy Taxonomy Governance Checklist v.1.0 Table of Content Introduction Methodology Phase 1: Planning Phase 2: Taxonomy Authoring Phase 3: Maintenance Appendix 1: Non-functional
More informationUsing the Common Industry Format to Document the Context of Use
Human-Computer Interaction. Human-Centred Design Approaches, Methods, Tools, and Environments - 15th International Conference, HCI International 2013, Las Vegas, NV, USA, July 21-26, 2013, Proceedings,
More informationThe Relationship between Slices and Module Cohesion
The Relationship between Slices and Module Cohesion Linda M. Ott Jeffrey J. Thuss Department of Computer Science Michigan Technological University Houghton, MI 49931 Abstract High module cohesion is often
More informationν Software product usage dictates that Software product Strategic Considerations ν Software product development dictates that Software product
Software Texts and Readings Building into software products Content overview Software Quality:Definitions and strategic issues - in library for reference. Ince, D. (1994) ISO 9001 and Software assurance.
More informationSpemmet - A Tool for Modeling Software Processes with SPEM
Spemmet - A Tool for Modeling Software Processes with SPEM Tuomas Mäkilä tuomas.makila@it.utu.fi Antero Järvi antero.jarvi@it.utu.fi Abstract: The software development process has many unique attributes
More informationCHAPTER 4 HUMAN FACTOR BASED USER INTERFACE DESIGN
CHAPTER 4 HUMAN FACTOR BASED USER INTERFACE DESIGN 4.1 Introduction Today one of the most important concerns is how to use the system with effectiveness, efficiency and satisfaction. The ease or comfort
More informationLOGICAL OPERATOR USAGE IN STRUCTURAL MODELLING
LOGICAL OPERATOR USAGE IN STRUCTURAL MODELLING Ieva Zeltmate (a) (a) Riga Technical University, Faculty of Computer Science and Information Technology Department of System Theory and Design ieva.zeltmate@gmail.com
More informationA Model-Based Reference Workflow for the Development of Safety-Related Software
A Model-Based Reference Workflow for the Development of Safety-Related Software 2010-01-2338 Published 10/19/2010 Michael Beine dspace GmbH Dirk Fleischer dspace Inc. Copyright 2010 SAE International ABSTRACT
More informationAddressing Quality Issues: Theory and Practice A Case Study on a Typical Software Project
Addressing Quality Issues: Theory and Practice A Case Study on a Typical Software Project Michalis Nik. XENOS Computer Technology Institute and Hellenic Open University Tel: +3061 361490, Fax: +3061 361410
More informationUser-Centred Evaluation Criteria for a Mixed Reality Authoring Application
User-Centred Evaluation Criteria for a Mixed Reality Authoring Application Marjaana Träskbäck, Toni Koskinen, Marko Nieminen Helsinki University of Technology, Software Business and Engineering Institute
More informationCreating and Checking the PIRLS International Database
Chapter 8 Creating and Checking the PIRLS International Database Juliane Barth and Oliver Neuschmidt 8.1 Overview The PIRLS 2006 International Database is a unique resource for policy makers and analysts,
More informationSoftware Engineering Lifecycles. Controlling Complexity
Software Engineering Lifecycles Class url:http://laser.cs.umass.edu/courses/cs320.spring11/ Controlling Complexity Separation of Concerns Planning Ahead Do a little work now to make later work easier The
More informationVO Software Engineering
Administrative Issues Univ.Prof. Dr. Peter Auer Chair for Information Technology Email: auer@unileoben.ac.at Lecture Thursday 10:15 11:45 Project Lab Montag 16:00 19:00 Literature Helmut Balzert, Lehrbuch
More informationSoftware quality Texts and Readings
Software quality Texts and Readings Software Quality:Definitions and strategic issues - in library for reference. Ince, D. (1994) ISO 9001 and Software quality assurance. Lecture handouts. 1 Building quality
More informationDEVELOPING DECISION SUPPORT SYSTEMS A MODERN APPROACH
DEVELOPING DECISION SUPPORT SYSTEMS A MODERN APPROACH Ion Lungu PhD, Vlad Diaconiţa PhD Candidate Department of Economic Informatics Academy of Economic Studies Bucharest In today s economy access to quality
More informationThe Tagging Tangle: Creating a librarian s guide to tagging. Gillian Hanlon, Information Officer Scottish Library & Information Council
The Tagging Tangle: Creating a librarian s guide to tagging Gillian Hanlon, Information Officer Scottish Library & Information Council Introduction Scottish Library and Information Council (SLIC) advisory
More informationCOLUMN. Worlds apart: the difference between intranets and websites. The purpose of your website is very different to that of your intranet MARCH 2003
KM COLUMN MARCH 2003 Worlds apart: the difference between intranets and websites Beyond a common use of HTML, intranets and corporate websites (internet sites) are very different animals. The needs they
More informationIncremental development A.Y. 2018/2019
Incremental development A.Y. 2018/2019 Incremental development Interleaves the activities of specification, development, and validation. The system is developed as a series of versions (increments), with
More informationThe IDN Variant TLD Program: Updated Program Plan 23 August 2012
The IDN Variant TLD Program: Updated Program Plan 23 August 2012 Table of Contents Project Background... 2 The IDN Variant TLD Program... 2 Revised Program Plan, Projects and Timeline:... 3 Communication
More informationINTERNATIONAL JOURNAL OF COMPUTER ENGINEERING & TECHNOLOGY (IJCET) NEED FOR DESIGN PATTERNS AND FRAMEWORKS FOR QUALITY SOFTWARE DEVELOPMENT
INTERNATIONAL JOURNAL OF COMPUTER ENGINEERING & TECHNOLOGY (IJCET) International Journal of Computer Engineering and Technology (IJCET), ISSN 0976 6367(Print), ISSN 0976 6367(Print) ISSN 0976 6375(Online)
More informationChapter 2 Overview of the Design Methodology
Chapter 2 Overview of the Design Methodology This chapter presents an overview of the design methodology which is developed in this thesis, by identifying global abstraction levels at which a distributed
More informationSOFTWARE ARCHITECTURE & DESIGN INTRODUCTION
SOFTWARE ARCHITECTURE & DESIGN INTRODUCTION http://www.tutorialspoint.com/software_architecture_design/introduction.htm Copyright tutorialspoint.com The architecture of a system describes its major components,
More informationCombining UML and Z in a Software Process
Combining UML and Z in a Software Process Ebba Thora Hvannberg University of Iceland, Reykjavik, Iceland, ebba@hi.is Abstract: Observing students writing specification in UML and Z has motivated the work
More informationAutomated Improvement for Component Reuse
Automated Improvement for Component Reuse Muthu Ramachandran School of Computing The Headingley Campus Leeds Metropolitan University LEEDS, UK m.ramachandran@leedsmet.ac.uk Abstract Software component
More informationAN ONTOLOGICAL EVALUATION OF JACKSON'S SYSTEM DEVELOPMENT MODEL. Fiona Rohde. Department of Commerce The University of Queensland, 4072.
AN ONTOLOGICAL EVALUATION OF JACKSON'S SYSTEM DEVELOPMENT MODEL Fiona Rohde Department of Commerce The University of Queensland, 4072. Australia ABSTRACT Within the discipline of information systems, numerous
More informationCPSC 444 Project Milestone III: Prototyping & Experiment Design Feb 6, 2018
CPSC 444 Project Milestone III: Prototyping & Experiment Design Feb 6, 2018 OVERVIEW... 2 SUMMARY OF MILESTONE III DELIVERABLES... 2 1. Blog Update #3 - Low-fidelity Prototyping & Cognitive Walkthrough,
More informationPattern-Based Architectural Design Process Model
Pattern-Based Architectural Design Process Model N. Lévy, F. Losavio Abstract: The identification of quality requirements is crucial to develop modern software systems, especially when their underlying
More informationCHAPTER 1. Topic: UML Overview. CHAPTER 1: Topic 1. Topic: UML Overview
CHAPTER 1 Topic: UML Overview After studying this Chapter, students should be able to: Describe the goals of UML. Analyze the History of UML. Evaluate the use of UML in an area of interest. CHAPTER 1:
More informationSEA-Manual. ,,Environmental Protection Objectives. Final report. EIA-Association (Ed.) UVP-Gesellschaft e.v. July 2000
SEA-Manual,,Environmental Protection Objectives Final report EIA-Association (Ed.) UVP-Gesellschaft e.v. July 2000 Daniel Rauprich Dieter Wagner Johannes Auge Dr. Frank Scholles Peter Wagner Translation:
More informationCh 1: The Architecture Business Cycle
Ch 1: The Architecture Business Cycle For decades, software designers have been taught to build systems based exclusively on the technical requirements. Software architecture encompasses the structures
More informationDESIGN AND TECHNOLOGY
Qualification Accredited A LEVEL NEA Marking Criteria April 2017 DESIGN AND TECHNOLOGY H404, H405 and H406 For first teaching in 2017 www.ocr.org.uk/gcsedesignandtechnology A Level Design and Technology
More informationApplying ISO/IEC Quality Model to Quality Requirements Engineering on Critical Software
Applying ISO/IEC 9126-1 Quality Model to Quality Engineering on Critical Motoei AZUMA Department of Industrial and Management Systems Engineering School of Science and Engineering Waseda University azuma@azuma.mgmt.waseda.ac.jp
More informationITERATIVE MULTI-LEVEL MODELLING - A METHODOLOGY FOR COMPUTER SYSTEM DESIGN. F. W. Zurcher B. Randell
ITERATIVE MULTI-LEVEL MODELLING - A METHODOLOGY FOR COMPUTER SYSTEM DESIGN F. W. Zurcher B. Randell Thomas J. Watson Research Center Yorktown Heights, New York Abstract: The paper presents a method of
More informationCS 292 Software Development
CS 292 Software Development and Professional Practice Structured Design and More Design Principles CS 292 Design Principles 1 Unless otherwise expressly stated, all original material of whatever nature
More informationDigital Library on Societal Impacts Draft Requirements Document
Table of Contents Digital Library on Societal Impacts Draft Requirements Document Eric Scharff Introduction... 1 System Description... 1 User Interface... 3 Infrastructure... 3 Content... 4 Work Already
More informationChapter I INTRODUCTION. and potential, previous deployments and engineering issues that concern them, and the security
Chapter I INTRODUCTION This thesis provides an introduction to wireless sensor network [47-51], their history and potential, previous deployments and engineering issues that concern them, and the security
More informationICAEW REPRESENTATION 68/16
ICAEW REPRESENTATION 68/16 Improving the Structure of the Code of Ethics for Professional Accountants - Phase 1 ICAEW welcomes the opportunity to comment on the Improving the Structure of the Code of Ethics
More informationWhite Paper. Incorporating Usability Experts with Your Software Development Lifecycle: Benefits and ROI Situated Research All Rights Reserved
White Paper Incorporating Usability Experts with Your Software Development Lifecycle: Benefits and ROI 2018 Situated Research All Rights Reserved Learnability, efficiency, safety, effectiveness, memorability
More informationReducing the costs of rework. Coping with change. Software prototyping. Ways to Cope with change. Benefits of prototyping
Coping with change Change is inevitable in all large software projects. Business changes lead to new and changed system requirements New technologies open up new possibilities for improving implementations
More information10. Software Testing Fundamental Concepts
10. Software Testing Fundamental Concepts Department of Computer Science and Engineering Hanyang University ERICA Campus 1 st Semester 2016 Testing in Object-Oriented Point of View Error Correction Cost
More informationSetting up an IT Network
Unit 16: Setting up an IT Network Unit code: M/601/3274 QCF Level 2: BTEC Specialist Credit value: 10 Guided learning hours: 60 Aim and purpose This unit enables learners to understand the role of IT networks
More informationThe OWASP Foundation. Compliance driven vulnerabilities The effect of a quality aspect on software security. BeNeLux OWASP Day 2009
Compliance driven vulnerabilities The effect of a quality aspect on software security Colin Watson Watson Hall Ltd colin.watson(at)owasp.org BeNeLux OWASP Day 2009 Copyright The OWASP Foundation Permission
More informationUnit title: Computing: Authoring a Website (SCQF level 6)
National Unit specification General information Unit code: F3T2 12 Superclass: CB Publication date: December 2013 Source: Scottish Qualifications Authority Version: 02 Unit purpose This Unit is designed
More informationWJEC/Eduqas Geography A-Level. Independent Investigation Non-Exam Assessment. How to Write your Independent Investigation
WJEC/Eduqas Geography A-Level Independent Investigation Non-Exam Assessment How to Write your Independent Investigation Notes Writing a Report To achieve a high mark, the coursework should resemble a scientific
More informationFoundation Level Syllabus Usability Tester Sample Exam
Foundation Level Syllabus Usability Tester Sample Exam Version 2017 Provided by German Testing Board Copyright Notice This document may be copied in its entirety, or extracts made, if the source is acknowledged.
More informationVerification and Validation. Ian Sommerville 2004 Software Engineering, 7th edition. Chapter 22 Slide 1
Verification and Validation Ian Sommerville 2004 Software Engineering, 7th edition. Chapter 22 Slide 1 Verification vs validation Verification: "Are we building the product right?. The software should
More informationA Tutorial on Agent Based Software Engineering
A tutorial report for SENG 609.22 Agent Based Software Engineering Course Instructor: Dr. Behrouz H. Far A Tutorial on Agent Based Software Engineering Qun Zhou December, 2002 Abstract Agent oriented software
More informationSoftware engineering Product quality Part 1: Quality model
SVENSK STANDARD SS-ISO/IEC 9126-1 Fastställd 2003-01-31 Utgåva 1 Software engineering Product Part 1: Quality model ICS 35.080.00 Språk: engelska Publicerad: mars 2003 Copyright SIS. Reproduction in any
More informationRetrofitting Security into a Web-Based Information System
Retrofitting Security into a Web-Based Information System David Bettencourt da Cruz, Bernhard Rumpe, Guido Wimmel Software & Systems Engineering, Technische Universität München 85748 Munich/Garching, Germany
More informationA Literature Survey on standards for software product quality
A Literature Survey on standards for software product quality Shreyas Lakhe B.E. 3 rd Year student College of Engineering, Pune Nagpur. 440010 (India) Rupali R. Dorwe Priyadarshini College of Engineering
More informationMaintaining & Increasing Stakeholder Confidence in IT Architecture
Maintaining & Increasing Stakeholder Confidence in IT Architecture Eoin Woods eoin@artechra.com www.eoinwoods.info 1 Content Defining IT Architecture IT Architecture & Requirements Identifying Stakeholders
More informationSafety Case Composition Using Contracts - Refinements based on Feedback from an Industrial Case Study
Safety Case Composition Using Contracts - Refinements based on Feedback from an Industrial Case Study Jane Fenn and Richard Hawkins BAE SYSTEMS, Brough, UK Phil Williams General Dynamics (United Kingdom)
More informationIJESRT. (I2OR), Publication Impact Factor: (ISRA), Impact Factor: 2.114
IJESRT INTERNATIONAL JOURNAL OF ENGINEERING SCIENCES & RESEARCH TECHNOLOGY EVALUATING ISO STANDARDS APPLICATION OF SECURITY REQUIREMENTS OF E- BANKING IN SUDAN Inshirah M. O. Elmaghrabi*, Hoida A. Abdelgadir,
More informationSecond. Incremental development model
3 rd Stage Lecture time: 8:30 AM-2:30 PM Instructor: Ali Kadhum AL-Quraby Lecture No. : 4 Subject: Software Engineering Class room no.: Department of computer science Second. Incremental development model
More informationCS:2820 (22C:22) Object-Oriented Software Development
The University of Iowa CS:2820 (22C:22) Object-Oriented Software Development! Spring 2015 Software Complexity by Cesare Tinelli Complexity Software systems are complex artifacts Failure to master this
More informationHuman Computer Interaction Lecture 06 [ HCI in Software Process ] HCI in the software process
Human Computer Interaction Lecture 06 [ HCI in Software Process ] Imran Ihsan Assistant Professor www.imranihsan.com aucs.imranihsan.com HCI06 - HCI in Software Process 1 HCI in the software process Software
More informationUNIT Engineering: Applying Information Technology (SCQF level 6)
National Unit Specification: general information CODE F5D4 12 SUMMARY This Unit is a mandatory Unit in the National Qualifications Group Awards (NQGA) in Engineering, but it can also be undertaken as a
More informationOPTIMIZATION MAXIMIZING TELECOM AND NETWORK. The current state of enterprise optimization, best practices and considerations for improvement
MAXIMIZING TELECOM AND NETWORK OPTIMIZATION The current state of enterprise optimization, best practices and considerations for improvement AOTMP.com The Next Evolution of Telecom Management OVERVIEW As
More informationVerification and Validation. Ian Sommerville 2004 Software Engineering, 7th edition. Chapter 22 Slide 1
Verification and Validation 1 Objectives To introduce software verification and validation and to discuss the distinction between them To describe the program inspection process and its role in V & V To
More informationWhat is Software Architecture
What is Software Architecture Is this diagram an architecture? (ATM Software) Control Card Interface Cash Dispenser Keyboard Interface What are ambiguities in the previous diagram? Nature of the elements
More informationThe Analysis and Proposed Modifications to ISO/IEC Software Engineering Software Quality Requirements and Evaluation Quality Requirements
Journal of Software Engineering and Applications, 2016, 9, 112-127 Published Online April 2016 in SciRes. http://www.scirp.org/journal/jsea http://dx.doi.org/10.4236/jsea.2016.94010 The Analysis and Proposed
More informationContinuous Security. Improve Web Application Security by using Continuous Security Scans
Continuous Security Improve Web Application Security by using Continuous Security Scans 1 The world of software development has changed. Nowadays around 65% of software projects use agile development 1.
More informationFinal Project Report
16.04.02 Final Project Report Document information Project Title HP Tool Repository of SESAR standard HP methods and tools Project Number 16.04.02 Project Manager DFS Deliverable Name 16.04.02 Final Project
More informationOCM ACADEMIC SERVICES PROJECT INITIATION DOCUMENT. Project Title: Online Coursework Management
OCM-12-025 ACADEMIC SERVICES PROJECT INITIATION DOCUMENT Project Title: Online Coursework Management Change Record Date Author Version Change Reference March 2012 Sue Milward v1 Initial draft April 2012
More informationUpdate on the TDL Metadata Working Group s activities for
Update on the TDL Metadata Working Group s activities for 2009-2010 Provide Texas Digital Library (TDL) with general metadata expertise. In particular, the Metadata Working Group will address the following
More informationThe SQALE Models for Assessing the Quality of Real Time Source Code
The SQL Models for ssessing the Quality of Real Time Source ode Jean-Louis LTOUZY 1, Thierry OQ 2 1: NV IT Global Services, rcueil, France, jean-louis.letouzey@dnv.com 2: NV IT Global Services, rcueil,
More informationBCS THE CHARTERED INSTITUTE FOR IT. BCS HIGHER EDUCATION QUALIFICATIONS BCS Level 5 Diploma in IT. March 2017 PRINCIPLES OF USER INTERFACE DESIGN
BCS THE CHARTERED INSTITUTE FOR IT BCS HIGHER EDUCATION QUALIFICATIONS BCS Level 5 Diploma in IT March 2017 PRINCIPLES OF USER INTERFACE DESIGN EXAMINERS REPORT General Comments Candidates should focus
More informationISSN: [Kaur* et al., 6(10): October, 2017] Impact Factor: 4.116
IJESRT INTERNATIONAL JOURNAL OF ENGINEERING SCIENCES & RESEARCH TECHNOLOGY COMPARATIVE ANALYSIS OF SOFTWARE DEVELOPMENT MODELS Sandeep Kaur* *Department of computer Science & Engineering, Guru Nanak Dev
More informationEuropean Commission - ISA Unit
DG DIGIT Unit.D.2 (ISA Unit) European Commission - ISA Unit INTEROPERABILITY QUICK ASSESSMENT TOOLKIT Release Date: 12/06/2018 Doc. Version: 1.1 Document History The following table shows the development
More informationData Quality Assessment Tool for health and social care. October 2018
Data Quality Assessment Tool for health and social care October 2018 Introduction This interactive data quality assessment tool has been developed to meet the needs of a broad range of health and social
More informationModeling Issues Modeling Enterprises. Modeling
Modeling Issues Modeling Enterprises SE502: Software Requirements Engineering Modeling Modeling can guide elicitation: It can help you figure out what questions to ask It can help to surface hidden requirements
More informationRequirements. CxOne Standard
Requirements CxOne Standard CxStand_Requirements.doc November 3, 2002 Advancing the Art and Science of Commercial Software Engineering Contents 1 INTRODUCTION... 1 1.1 OVERVIEW... 1 1.2 GOALS... 1 1.3
More informationRequirements Engineering. Establishing what the customer requires from a software system. Requirements Engineering. What is a Requirement?
Engineering Establishing what the customer requires from a software system Ian Sommerville 1995/2000 (Modified by Spiros Mancoridis 1999) Software Engineering, 6th edition. Chapters 5 and 6 Slide 1 Engineering
More information