DOCSLIB.ORG

Rapid Software Development Software Prototyping Benefits of Prototyping

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
Rapid Software Development Software Prototyping Benefits of Prototyping Software prototyping z A prototype is an initial version of a system used to demonstrate concepts and try out Rapid software development design options. z A prototype can be used in: • The requirements engineering process to help with requirements elicitation and validation; • In design processes to explore options and develop a UI design; • In the testing process to run back-to-back tests. ©Ian Sommerville 2004 Software Engineering, 7th edition. Chapter 17 Slide 1 ©Ian Sommerville 2004 Software Engineering, 7th edition. Chapter 17 Slide 2 Benefits of prototyping The prototyping process z Improved system usability. z A closer match to users’ real needs. z Improved design quality. z Improved maintainability. z Reduced development effort. ©Ian Sommerville 2004 Software Engineering, 7th edition. Chapter 17 Slide 3 ©Ian Sommerville 2004 Software Engineering, 7th edition. Chapter 17 Slide 4 Characteristics of RAD processes Incremental development and prototyping z The processes of specification, design and implementation are concurrent. There is no detailed specification and design documentation is minimised. z The system is developed in a series of increments. End users evaluate each increment and make proposals for later increments. z System user interfaces are usually developed using an interactive development system. ©Ian Sommerville 2004 Software Engineering, 7th edition. Chapter 17 Slide 5 ©Ian Sommerville 2004 Software Engineering, 7th edition. Chapter 17 Slide 6 Conflicting objectives Agile methods z The objective of incremental development is z Dissatisfaction with the overheads involved in design to deliver a working system to end-users. methods led to the creation of agile methods. These The development starts with those methods: • Focus on the code rather than the design; requirements which are best understood. • Are based on an iterative approach to software z The objective of throw-away prototyping is to development; validate or derive the system requirements. • Are intended to deliver working software quickly and evolve this quickly to meet changing requirements. The prototyping process starts with those z Agile methods are probably best suited to requirements which are poorly understood. small/medium-sized business systems or PC products. ©Ian Sommerville 2004 Software Engineering, 7th edition. Chapter 17 Slide 7 ©Ian Sommerville 2004 Software Engineering, 7th edition. Chapter 17 Slide 8 Principles of agile methods Problems with agile methods z It can be difficult to keep the interest of customers Principle Description who are involved in the process. Customer involvement The customer should be closely involved throughout the development process. Their role is provide and prioritise new z Team members may be unsuited to the intense system requirements and to evaluate the iterations of the system. involvement that characterises agile methods. Incremental delivery The software is developed in increments with the customer specifying the requirements to be included in each increment. z Prioritising changes can be difficult where there are People not process The skills of the development team should be recognised and multiple stakeholders. exploited. The team should be left to develop their own ways of working without prescriptive processes. z Maintaining simplicity requires extra work. Embrace change Expect the system requirements to change and design the system z Contracts may be a problem as with other so that it can accommodate these changes. approaches to iterative development. Maintain simplicity Focus on simplicity in both the software being developed and in the development process used. Wherever possible, actively work to eliminate complexity from the system. ©Ian Sommerville 2004 Software Engineering, 7th edition. Chapter 17 Slide 9 ©Ian Sommerville 2004 Software Engineering, 7th edition. Chapter 17 Slide 10 Extreme programming The XP release cycle z Perhaps the best-known and most widely used agile method. z Extreme Programming (XP) takes an ‘extreme’ approach to iterative development. • New versions may be built several times per day; • Increments are delivered to customers every 2 weeks; • All tests must be run for every build and the build is only accepted if tests run successfully. ©Ian Sommerville 2004 Software Engineering, 7th edition. Chapter 17 Slide 11 ©Ian Sommerville 2004 Software Engineering, 7th edition. Chapter 17 Slide 12 Extreme programming practices 1 Extreme programming practices 2 Incremental planning Requirements are recorded on Story Cards and the Stories to be Pair Programming Developers work in pairs, checking each otherÕs work and included in a release are determined by the time available and providing the support to always do a good job. their relative priority. The developers break these Stories into Collective Ownership The pairs of developers work on all areas of the system, so that development ŌTasksÕ. no islands of expertise develop and all the developers own all the Small Releases The minimal useful set of functionality that provides business code. Anyon e can change anything. value is developed first. Releases of the system are frequent and Continuous Integration As soon as work on a task is complete it is integrated into the incrementally add functionality to the first release. whole system. After any such integration, all the unit tests in the system must pass. Simple Design Enough design is carried out to meet the current requirements and no more. Sustainable pace Large amounts of over-time are not considered acceptable as the net effect is often to reduce code qua lity and medium term Test first development An automated unit test framework is used to write tests for a new productivity piece of functionality before that functionality itself is implemented. On-site Customer A representative of the end-user of the system (the Customer) should be available full time for the use of the XP team. In an Refactoring All developers are expected to refactor the code con tinuously as extreme programming process, the customer is a member of the soon as possible code improvements are found. This keeps the development team and is responsible for bringing system code simple and maintainable. requirements to the team for implementation. ©Ian Sommerville 2004 Software Engineering, 7th edition. Chapter 17 Slide 13 ©Ian Sommerville 2004 Software Engineering, 7th edition. Chapter 17 Slide 14 XP and agile principles Requirements scenarios z Incremental development is supported through z In XP, user requirements are expressed as small, frequent system releases. scenarios or user stories. z Customer involvement means full-time customer z These are written on cards and the engagement with the team. development team break them down into z People not process through pair programming, collective ownership and a process that avoids long implementation tasks. These tasks are the working hours. basis of schedule and cost estimates. z Change supported through regular system releases. z The customer chooses the stories for z Maintaining simplicity through constant refactoring of inclusion in the next release based on their code. priorities and the schedule estimates. ©Ian Sommerville 2004 Software Engineering, 7th edition. Chapter 17 Slide 15 ©Ian Sommerville 2004 Software Engineering, 7th edition. Chapter 17 Slide 16 Story card for document downloading XP and change z Conventional wisdom in software engineering is to design for change. It is worth spending time and effort anticipating changes as this reduces costs later in the life cycle. z XP, however, maintains that this is not worthwhile as changes cannot be reliably anticipated. z Rather, it proposes constant code improvement (refactoring) to make changes easier when they have to be implemented. ©Ian Sommerville 2004 Software Engineering, 7th edition. Chapter 17 Slide 17 ©Ian Sommerville 2004 Software Engineering, 7th edition. Chapter 17 Slide 18 Testing in XP Task cards for document downloading z Test-first development. z Incremental test development from scenarios. z User involvement in test development and validation. z Automated test harnesses are used to run all component tests each time that a new release is built. ©Ian Sommerville 2004 Software Engineering, 7th edition. Chapter 17 Slide 19 ©Ian Sommerville 2004 Software Engineering, 7th edition. Chapter 17 Slide 20 Test case description Test-first development z Writing tests before code clarifies the requirements to be implemented. z Tests are written as programs rather than data so that they can be executed automatically. The test includes a check that it has executed correctly. z All previous and new tests are automatically run when new functionality is added. Thus checking that the new functionality has not introduced errors. ©Ian Sommerville 2004 Software Engineering, 7th edition. Chapter 17 Slide 21 ©Ian Sommerville 2004 Software Engineering, 7th edition. Chapter 17 Slide 22 Pair programming COTS reuse z In XP, programmers work in pairs, sitting together to z An effective approach to rapid development develop code. is to configure and link existing off the shelf z This helps develop common ownership of code and spreads knowledge across the team. systems. z It serves as an informal review process as each line z For example, a requirements management of code is looked at by more than 1 person. system could be built by using: z It encourages refactoring as the whole team can • A database to store requirements; benefit from this. • A word processor to capture requirements and z Measurements suggest that development productivity with pair programming is similar to that format reports; of two people working independently. • A spreadsheet for traceability management; ©Ian Sommerville 2004 Software Engineering, 7th edition. Chapter 17 Slide 23 ©Ian Sommerville 2004 Software Engineering, 7th edition. Chapter 17 Slide 24.
Load more

Recommended publications
  • Software Prototyping Rapid Software Development to Validate Requirements
    FSE Foundations of software engineering Software Prototyping Rapid software development to validate requirements G51FSE Monday, 20 February 12 Objectives To describe the use of prototypes in different types of development project To discuss evolutionary and throw-away prototyping To introduce three rapid prototyping techniques - high-level language development, database programming and component reuse To explain the need for user interface prototyping FSE Lecture 10 - Prototyping 2 Monday, 20 February 12 System prototyping Prototyping is the rapid development of a system In the past, the developed system was normally thought of as inferior in some way to the required system so further development was required Now, the boundary between prototyping and normal system development is blurred Many systems are developed using an evolutionary approach FSE Lecture 10 - Prototyping 3 Monday, 20 February 12 Why bother? The principal use is to help customers and developers understand the requirements for the system Requirements elicitation: users can experiment with a prototype to see how the system supports their work Requirements validation: The prototype can reveal errors and omissions in the requirements Prototyping can be considered as a risk reduction activity which reduces requirements risks FSE Lecture 10 - Prototyping 4 Monday, 20 February 12 Prototyping bene!ts Misunderstandings between software users and developers are exposed Missing services may be detected and confusing services may be identi!ed A working system is available early in
    [Show full text]
  • Test Driven Development
    Test Driven Development René Barto SES Agile Development - Test Driven Development 27-09-2006 Contents • About Myself • About SES • Agile Development • A Typical Developer’s Day • Test Driven Development • Questions SES 27-09-2006 2 About Myself • Born 1966 • Graduated from TU Eindhoven (Information Technology) • Around 20 years of experience in software development • Joined Philips CFT in 1995 • Joined Philips Research in 2001 • Moved to SES in end 2002 SES 27-09-2006 3 About SES • Founded in 2000 with three permanent staff, to support Philips Research in software prototype development • In 2002, SES moved to the Prototyping and Instrumentation sector, to facilitate combined hardware / software prototyping • Since 2003, many start-up companies (incubators) have been served as well, moving the focus more to product development • Now (September 2006), SES consists of 11 permanent staff and some 70 temporary staff SES 27-09-2006 4 Agile Development – An Introduction Agile development is based on a lightweight process. The concepts are formulated by the Agile Alliance in “The manifesto for Agile Software Development” The Agile Alliance Values: • Value Individuals and interactions over process and tools, • Value Working software over comprehensive documents, • Value Customer collaboration over contract negotiation, • Value Responding to change over following a plan. http://www.agilealliance.org SES 27-09-2006 5 Agile Development - What Is It? • Lightweight (lean and mean) process for development, originated in the SW development community
    [Show full text]
  • Process Models in Software Engineering
    Process Models in Software Engineering Walt Scacchi, Institute for Software Research, University of California, Irvine February 2001 Revised Version, May 2001, October 2001 Final Version to appear in, J.J. Marciniak (ed.), Encyclopedia of Software Engineering, 2nd Edition, John Wiley and Sons, Inc, New York, December 2001. Introduction Software systems come and go through a series of passages that account for their inception, initial development, productive operation, upkeep, and retirement from one generation to another. This article categorizes and examines a number of methods for describing or modeling how software systems are developed. It begins with background and definitions of traditional software life cycle models that dominate most textbook discussions and current software development practices. This is followed by a more comprehensive review of the alternative models of software evolution that are of current use as the basis for organizing software engineering projects and technologies. Background Explicit models of software evolution date back to the earliest projects developing large software systems in the 1950's and 1960's (Hosier 1961, Royce 1970). Overall, the apparent purpose of these early software life cycle models was to provide a conceptual scheme for rationally managing the development of software systems. Such a scheme could therefore serve as a basis for planning, organizing, staffing, coordinating, budgeting, and directing software development activities. Since the 1960's, many descriptions of the classic software life cycle have appeared (e.g., Hosier 1961, Royce 1970, Boehm 1976, Distaso 1980, Scacchi 1984, Somerville 1999). Royce (1970) originated the formulation of the software life cycle using the now familiar "waterfall" chart, displayed in Figure 1.
    [Show full text]
  • Prototyping Process
    With contributions by: Steven Jacobs, Eck Doerry With credit and thanks for some slides and ideas to Larry Bernstein’s Quantitative Software Engineering Course at Stevens Institute of Technology, Hoboken, NJ Software Requirements Development Process 1. Requirements Elicitation (what the user wants) 2. Requirements Analysis (filling in the blanks) 3. Use Cases (Explore interaction dynamics) 4. Prototype/Modeling (prove that it can work) 5. Requirements Specification (formalize it) 6. Requirements Management (trace/verify) 2 Software Prototyping Process Key tool for targeting Software prototyping: implementation! the process of creating an incomplete model of the future full- featured software Or of key pieces/modules Process: Identify basic requirements Develop Initial prototype Review with customers users Revise and enhance http://crackmba.com/tag/sdlc/ 3 Prototypes as Specifications? Could we use a prototype as a specification? “Let me show you sort of what I want (prototype)…” “…and then we’ll use that as spec!” No! Because: Some parts of the requirements may be impossible to prototype E.g., safety-critical functions An implementation has no legal standing as a contract! It is no substitute for a clear specification of requirements. Non-functional requirements cannot be adequately tested in a system prototype 4 Types of Software Prototypes Throwaway prototype: Idea: creating a very rapid model (demonstration or marketing) Early tool for envisioning software look and feel. Could be paper: posters, screen sheets Evolutionary
    [Show full text]
  • Prototyping As a Requirements Engineering Technique Franz Lang, Alexander Mjöberg
    MASTER’S THESIS 2020 Prototyping as a Requirements Engineering Technique Franz Lang, Alexander Mjöberg ISSN 1650-2884 LU-CS-EX: 2020-29 DEPARTMENT OF COMPUTER SCIENCE LTH j LUND UNIVERSITY EXAMENSARBETE Datavetenskap LU-CS-EX: 2020-29 Prototyping as a Requirements Engineering Technique Franz Lang, Alexander Mjöberg Prototyping as a Requirements Engineering Technique Franz Lang Alexander Mjöberg [email protected] [email protected] June 22, 2020 Master’s thesis work carried out at the Department of Computer Science, Lund University. Supervisors: Elizabeth Bjarnason, [email protected] Maria Blomberg, [email protected] Examiner: Björn Regnell, [email protected] Abstract CONTEXT: Requirements Engineering is an important part of Software de- velopment. Software development has largely moved towards agile practices and the eld of Requirements Engineering is no exception. However, within Agile Requirements Engineering much research remains to be done [1]. Prototyping has been identied by one study as a technique that can solve challenges sur- rounding Agile Requirements Engineering [2]. As the practical use of prototypes is not self-evident, prototyping methodology is useful to understand before be- ing used in an Agile Requirements Engineering context. This begs the question, what is a meaningful model of prototyping and how can it be applied in an Agile Requirements Engineering context? METHOD: We perform a case-study at Telavox, a company seeking to develop a new product with agile software development methodology. A literature study is conducted to gather knowledge on prototyping methodology and assemble a model. An exploratory case study with prototyping activities is conducted to better understand delity in the context of prototyping.
    [Show full text]
  • Rapid Software Prototyping Using Visual Language Techniques
    Rapid Software Prototyping Using Visual Language Techniques Kang Zhang Guang-Lei Song Jun Kong Department of Computer Science, University of Texas at Dallas Richardson, Texas 75083-0688, USA {kzhang, gxs017800, jxk019200}@utdallas.edu Abstract fashion [14]. Visual languages include languages where programming is done by manipulation of visual objects, Rapid prototyping of domain-specific software requires a languages designed to facilitate algorithm and program systematic software development methodology and user- animation, and languages for use in computer-oriented ap- friendly tools. Being both executable and easy to use, visual plications such as software engineering and database design languages and their automatic generation mechanisms are and access [3]. Different from CASE toolsets, visual lan- highly suitable for software prototyping. This paper pre- guages are executable specification languages that are de- sents a software prototyping methodology based on the fined by graph grammars and syntax-directed rewriting visual language generation technology, that allows visual rules, apart from being at high level [19]. This means that prototyping languages to be specified and generated using prototyped domain software can also be rigorously verified an expressive graph grammar formalism. Executable proto- according to the provided specification. We will call the types and their verification and code generation are made visual languages designed for rapid software prototyping as possible by syntax-directed computations. The paper dem- visual executable prototyping languages (VEPLs). This onstrates this methodology through a prototyping example paper presents an automatic language-generation mecha- built on our current implementation. nism as a meta-tool for the fast generation and reuse of do- main-specific language modules, using a graph grammar- based approach to the specification and verification of do- main software prototypes.
    [Show full text]
  • Application Software Prototyping and Fourth Generation Languages
    NATL INST OF STANDARDS & TECH R.I.C. Computer Science A1 11 02661 975 Fisher, Gary E/Application software prot and Technology QC100 .U57 NO.500-148 1987 V19 C.I NBS-P PUBLICATIONS NBS Special Publication 500-148 Application Software Prototyping and Fourth Generation Languages Gary E. Fisher 1987 Tm he National Bureau of Standards' was established by an act of Congress on March 3, 1901. The Bureau's overall goal is to strengthen and advance the nation's science and technology and facilitate their effective application for public benefit. To this end, the Bureau conducts research to assure international competitiveness and leadership of U.S. industry, science arid technology. NBS work involves development and transfer of measurements, standards and related science and technology, in support of continually improving U.S. productivity, product quality and reliability, innovation and underlying science and engineering. The Bureau's technical work is performed by the National Measurement Laboratory, the National Engineering Laboratory, the Institute for Computer Sciences and Technology, and the Institute for Materials Science and Engineering. The National Measurement Laboratory Provides the national system of physical and chemical measurement; • Basic Standards^ coordinates the system with measurement systems of other nations and • Radiation Research furnishes essential services leading to accurate and uniform physical and • Chemical Physics chemical measurement throughout the Nation's scientific community, • Analytical Chemistry industry,
    [Show full text]
  • I – Software Engineering – SCSA1303
    SCHOOL OF COMPUTING DEPARTMENT OF COMPUTER SCIENCE AND ENGINEERING UNIT – I – Software Engineering – SCSA1303 1 I INTRODUCTION S/W engineering paradigm - Life cycle models - Water fall - Incremental - Spiral - Evolutionary - Prototyping - Object oriented system engineering - Computer based system - Verification - Validation - Life cycle process - Development process - System engineering hierarchy - Introduction to CMM - Levels of CMM. Evolving Role of Software: Software is more than just a program code. A program is an executable code, which serves some computational purpose. Software is considered to be collection of executable programming code, associated libraries and documentations. Software, when made for a specific requirement is called software product. Engineering on the other hand, is all about developing products, using well- defined, scientific principles and methods. Software engineering is an engineering branch associated with development of software product using well-defined scientific principles, methods and procedures. The outcome of software engineering is an efficient and reliable software product. Fritz Bauer, a German computer scientist, defines software engineering as: Software engineering is the establishment and use of sound engineering principles in order to obtain economically software that is reliable and work efficiently on real machines. Software Evolution The process of developing a software product using software engineering principles and methods is referred to as software evolution. This includes the initial development of software and its maintenance and updates, till desired software product is developed, which satisfies the expected requirements, 2 Fig 1.1: Software Evolution Evolution starts from the requirement gathering process. After which developers create a prototype of the intended software and show it to the users to get their feedback at the early stage of software product development.
    [Show full text]
  • Rapid Software Development
    Rapid software development ©Ian Sommerville 2004 Software Engineering, 7th edition. Chapter 17 Slide 1 Objectives ● To explain how an iterative, incremental development process leads to faster delivery of more useful software ● To discuss the essence of agile development methods ● To explain the principles and practices of extreme programming ● To explain the roles of prototyping in the software process ©Ian Sommerville 2004 Software Engineering, 7th edition. Chapter 17 Slide 2 Topics covered ● Agile methods ● Extreme programming ● Rapid application development ● Software prototyping ©Ian Sommerville 2004 Software Engineering, 7th edition. Chapter 17 Slide 3 Rapid software development ● Because of rapidly changing business environments, businesses have to respond to new opportunities and competition. ● This requires software and rapid development and delivery is not often the most critical requirement for software systems. ● Businesses may be willing to accept lower quality software if rapid delivery of essential functionality is possible. ©Ian Sommerville 2004 Software Engineering, 7th edition. Chapter 17 Slide 4 Requirements ● Because of the changing environment, it is often impossible to arrive at a stable, consistent set of system requirements. ● Therefore a waterfall model of development is impractical and an approach to development based on iterative specification and delivery is the only way to deliver software quickly. ©Ian Sommerville 2004 Software Engineering, 7th edition. Chapter 17 Slide 5 Characteristics of RAD processes ● The processes of specification, design and implementation are concurrent. There is no detailed specification and design documentation is minimised. ● The system is developed in a series of increments. End users evaluate each increment and make proposals for later increments. ● System user interfaces are usually developed using an interactive development system.
    [Show full text]
  • Software Prototyping: Implications for the People Involved in Systems Development
    Software Prototyping: Implications for the People Involved in Systems Development Pam Mayhew School of Information Systems University of East Anglia Norwich, NR4 7TJ, England Abstract This paper explores the adoption of systems prototyping and, in particular, concentrates on the various ways in which this may affect those people associated with systems development. One widely accepted prerequisite for successful prototyping is that it requires a fundamental change of attitudes for developers, users and managers alike. This all too frequently ignored requirement is discussed and illustrated. Adopting a prototyping approach to systems development can have a significant effect on the roles played by both users and developers. These alterations in roles and responsibilities are examined. Particular attention is given to the role of the prototyper, as well as to the issues to be considered when choosing who should play this crucial part. Examples are drawn from experience of both teaching prototyping within a University and its adoption in a commercial environment. 1. Introduction During the 1980's systems prototyping has fast been transformed from a relatively unknown research topic to a widely discussed approach to developing computer based information systems. Consequently, there now exists a considerable mount of literature on the subject. The majority of these publications deal with one or more of the following areas: • a general discussion of prototyping often concentrating on advantages and problem areas; • a description of the execution of prototyping, often in an ad-hoc and retrospective fashion; 290 • a detailed presentation of a particular product, followed by an argument as to its suitability for use as a prototyping tool.
    [Show full text]
  • Effectiveness of Prototyping Acquisition Strategies for Major Defense Acquisition Programs
    OFFICE OF THE INSPECTOR GENERAL EFFECTIVENESS OF PROTOTYPING ACQUISITION STRATEGIES FOR MAJOR DEFENSE ACQUISITION PROGRAMS Report No. 94-181 September 2, 1994 ~!llilittmtili;ill;i;i;i;i;i;i~;i;i;i;i;m;i;Mml@;i;mi~;l~;i;l;i;l;l~~~~~;mmimmi~;miM;l;~~i;i~~;i;i~;l;i;imi~tmi;i;i;imittiM~ti;i;i;i~;i;l:i;i;i;i;l;~i~~;i;i~ti~;i;i;i~;i;i;rititl~i~; Department of Defense Additional Copies To obtain additional copies of this report, contact the Secondary Reports Distribution Unit, Audit Planning and Technical Support Directorate, at (703) 604­ 8937 (DSN 664-8937) or FAX (703) 604-8932. Suggestions for Future Audits To suggest ideas for or to request future audits, contact the Planning and Coordination Branch, Audit Planning and Technical Support Directorate, at (703) 604-8939 (DSN 664-8939) or FAX (703) 604-8932. Ideas and requests can also be mailed to: Inspector General, Department of Defense OAIG-AUD (ATTN: APTS Audit Suggestions) 400 Army Navy Drive (Room 801) Arlington, Virginia 22202-2884 DoD Hotline To report fraud, waste, or abuse, call the DoD Hotline at (800) 424-9098 or write to the DoD Hotline, The Pentagon, Washington, D.C. 20301-1900. The identity of writers and callers is fully protected. Acronyms API Acquisition Program Integration ARPA Advanced Research Projects Agency BAT Brilliant Anti-Armor Submunition EMD Engineering and Manufacturing Development EOA Early Operational Assessment FDS Fixed Distributed System IDA Institute for Defense Analysis JSOW Joint Standoff Weapon System LRIP Low-Rate Initial Production MDAP Major Defense
    [Show full text]
  • Lessons from Implementing a League Table Application in the Health Sector
    Lessons from implementing a league table application in the health sector A case from Malawi Kristoffer Adam Tronerud , Martin Theodor Vasbotten Master’s Thesis Spring 2016 Lessons from implementing a league table application in the health sector Kristoffer Adam Tronerud Martin Theodor Vasbotten 18th May 2016 ii Abstract Malawi’s Health Management Information System(HMIS) is currently going through a strengthening process. Though good progress has been made, the data in the system receives limited usage and is of poor quality. As HMISs are dependent on available quality data to support decision-making, further strengthening efforts are needed to increase the availability of quality data. This thesis and its research builds upon prior research suggesting that league tables can be used to improve data quality and usage in Malawi’s routine health management. Earlier research also found that creating league tables using the existing functionality of Malawi’s HMIS can be challenging, suggesting that an dedicated application could be a solution. Hence, this thesis looks at the process of designing, developing and implementing an app, called the League Tables Application(LTA) in Malawi’s HMIS. Furthermore, it looks at challenges and opportunities related to these processes. This study has involved potential users from all levels of the health system in the process in order to identify common thoughts and ideas for the application. Through demonstrations and users testing the application, feedback suggests that the LTA was a user-friendly tool to analyse data for decision-making. It also proved to give motivation as well as stimulating competition. Though the application showed promise, it also showed a lack of quality data and usage which in turn reduced the analytical value of its results.
    [Show full text]