RANCANG BANGUN MODEL SISTEM PENGELOLAAN DOKUMEN DALAM PENINGKATAN PELAYANAN ADMINISTRASI PADA SUBBAGIAN TATA USAHA PIMPINAN DI BAGIAN PROTOKOL KABUPATEN LAMPUNG TIMUR

 Documents are one of the important factors in measuring the level of achievement of organized activities in government. The development of science and technology currently causes changes in all aspects of life, as well as in administrative activities. At present many parties are utilizing electronic media in document management. Using electronic media in document management will facilitate data management.This research is an exploratory research with a system approach in the form of Soft System Methodology (SSM) which is an approach to solve complex unstructured problem situations. The analysis used is to use 7 (seven) stages in Soft System Methodology (SSM).From the results of the study it can be concluded that the management of documents to improve administrative services leadership can be done through the use of an input system for documents or letters electronically so as to streamline time, Lack of understanding of JFU in existing technology so that it is a bit difficult to implement the existing system, Lack of understanding of the manuscript service so that there is often a lack of understanding of correspondence. Requirement of protocol training for all protocols so that they can understand their respective duties and functions and Standard Operating Procedures that have not been optimal for managing incoming and outgoing letters and the absence of Standard Operating Procedures for the Secretary of the Regent

Modelling the Strategic Alignment of Software Requirements using Goal Graphs

This paper builds on existing Goal Oriented Requirements Engineering (GORE) research by presenting a methodology with a supporting tool for analysing and demonstrating the alignment between software requirements and business objectives. Current GORE methodologies can be used to relate business goals to software goals through goal abstraction in goal graphs. However, we argue that unless the extent of goal-goal contribution is quantified with verifiable metrics and confidence levels, goal graphs are not sufficient for demonstrating the strategic alignment of software requirements. We introduce our methodology using an example software project from Rolls-Royce. We conclude that our methodology can improve requirements by making the relationships to business problems explicit, thereby disambiguating a requirement's underlying purpose and value.Comment: v2 minor updates: 1) bitmap images replaced with vector, 2) reworded related work ref[6] for clarit

Process of designing robust, dependable, safe and secure software for medical devices: Point of care testing device as a case study

This article has been made available through the Brunel Open Access Publishing Fund.Copyright © 2013 Sivanesan Tulasidas et al. This paper presents a holistic methodology for the design of medical device software, which encompasses of a new way of eliciting requirements, system design process, security design guideline, cloud architecture design, combinatorial testing process and agile project management. The paper uses point of care diagnostics as a case study where the software and hardware must be robust, reliable to provide accurate diagnosis of diseases. As software and software intensive systems are becoming increasingly complex, the impact of failures can lead to significant property damage, or damage to the environment. Within the medical diagnostic device software domain such failures can result in misdiagnosis leading to clinical complications and in some cases death. Software faults can arise due to the interaction among the software, the hardware, third party software and the operating environment. Unanticipated environmental changes and latent coding errors lead to operation faults despite of the fact that usually a significant effort has been expended in the design, verification and validation of the software system. It is becoming increasingly more apparent that one needs to adopt different approaches, which will guarantee that a complex software system meets all safety, security, and reliability requirements, in addition to complying with standards such as IEC 62304. There are many initiatives taken to develop safety and security critical systems, at different development phases and in different contexts, ranging from infrastructure design to device design. Different approaches are implemented to design error free software for safety critical systems. By adopting the strategies and processes presented in this paper one can overcome the challenges in developing error free software for medical devices (or safety critical systems).Brunel Open Access Publishing Fund

IT and the NHS: Investigating different perspectives of IT using soft systems methodology

The UK NHS National Programme for IT has been criticized for a lack of clinical engagement. This paper uses a soft systems methodology (SSM) analysis of a case study from the use of electronic systems within a National Health Service (NHS) Mental Health Trust in the United Kingdom (UK) to explore the legal and ethical implications of the failure to develop clinical systems which are fit for purpose. Soft systems methodology (SSM) was used as a theoretical model both to derive deeper insights into the survey data and suggest how communication between those producing information and those using it, could be improved. Multiple methods were employed which included a postal survey and participant interviews to triangulate the data The use of SSM reinforced the concept that the national IT programme is based on a 'hard' systems view and does not take local factors (which are related to 'soft systems' thinking) into account. The study found administrative staff to be a crucial link between clinicians and information departments and highlighted the need for a joint-up information strategy and integrated systems. The article concludes with a discussion of the legal and ethical implications of the findings and the lessons for the broader UK national programme. It argues that the failure to deliver systems that are fit for purpose is not value neutral but an ethical issue

A Platform-Based Software Design Methodology for Embedded Control Systems: An Agile Toolkit

A discrete control system, with stringent hardware constraints, is effectively an embedded real-time system and hence requires a rigorous methodology to develop the software involved. The development methodology proposed in this paper adapts agile principles and patterns to support the building of embedded control systems, focusing on the issues relating to a system's constraints and safety. Strong unit testing, to ensure correctness, including the satisfaction of timing constraints, is the foundation of the proposed methodology. A platform-based design approach is used to balance costs and time-to-market in relation to performance and functionality constraints. It is concluded that the proposed methodology significantly reduces design time and costs, as well as leading to better software modularity and reliability

Using quality models in software package selection

The growing importance of commercial off-the-shelf software packages requires adapting some software engineering practices, such as requirements elicitation and testing, to this emergent framework. Also, some specific new activities arise, among which selection of software packages plays a prominent role. All the methodologies that have been proposed recently for choosing software packages compare user requirements with the packages' capabilities. There are different types of requirements, such as managerial, political, and, of course, quality requirements. Quality requirements are often difficult to check. This is partly due to their nature, but there is another reason that can be mitigated, namely the lack of structured and widespread descriptions of package domains (that is, categories of software packages such as ERP systems, graphical or data structure libraries, and so on). This absence hampers the accurate description of software packages and the precise statement of quality requirements, and consequently overall package selection and confidence in the result of the process. Our methodology for building structured quality models helps solve this drawback.Peer ReviewedPostprint (published version

A goal-oriented requirements modelling language for enterprise architecture

Methods for enterprise architecture, such as TOGAF, acknowledge the importance of requirements engineering in the development of enterprise architectures. Modelling support is needed to specify, document, communicate and reason about goals and requirements. Current modelling techniques for enterprise architecture focus on the products, services, processes and applications of an enterprise. In addition, techniques may be provided to describe structured requirements lists and use cases. Little support is available however for modelling the underlying motivation of enterprise architectures in terms of stakeholder concerns and the high-level goals that address these concerns. This paper describes a language that supports the modelling of this motivation. The definition of the language is based on existing work on high-level goal and requirements modelling and is aligned with an existing standard for enterprise modelling: the ArchiMate language. Furthermore, the paper illustrates how enterprise architecture can benefit from analysis techniques in the requirements domain