Why?: Documenting the Missing Interrogative Using an Essential Logic Model
|
|
- Chad Ray
- 6 years ago
- Views:
Transcription
1 Why?: Documenting the Missing Interrogative Using an Essential Logic Model R.J.Collins Abstract This paper describes a diagramming convention called an Essential Logic Model (ELM). An ELM tells the story of the system and the decisions that were made during its construction. The ELM shows the relationship between broad classes of requirements and how these relate to the explanatory concepts developed and used during system development. The diagram also shows the important processes that exist within the system and the objects that the new system will interface to and on which it is dependent. During some stage of development, requirements for a system as a whole are normally decomposed and attributed to sub-system components. The ELM relates this information. It shows how the collection of requirements, existing real-world objects, processes and the explanatory concepts map onto the new design objects proposed as part of the system. It is argued that, if safe systems are to be produced and maintained then there must be harmony in the design decisions made by groups of software engineers. An implementation is the realisation of a design process. Project documentation may record the realisation but may lose the essence of the logical process that resulted in that realisation. An ELM is a didactic tool to be employed between software developers to externalise and record a logical series of thought processes that result in a design realisation. Experience suggests that this process of externalisation and documentation serves to highlight errors and inconsistencies in thinking. This seems to be particularly true in the case of large, complex systems when individuals are unlikely to be experts in all aspects of the system. Page 1
2 Introduction A number of system specification, design, analysis and implementation methods may be characterised with respect to simple interrogatives. For example, it has been argued that formal specifications employ a powerful abstracting mechanism by defining what a function should achieve without stating how it should be implemented. For example in talking about the formal language Z, Potter, Sinclair and Till have argued: In short, the concerns of specifications are the issues which describe what a system must offer rather than the prescription of how these things are to be achieved. Rann, Turner and Whitworth have re-iterated: (Potter, Sinclair and Till 1991) Formal specifications are used to define in a precise way the properties of a system. A specification describes what a system must do, not how it is to be done. (Rann, Turner and Whitworth 1994) Similar claims are made of other structured systems analysis techniques (Ashworth and Goodland 1990; Longworth 1992) Object Oriented designs employ the notion of encapsulation. The published operations of an object inform the client of what the object will do, whilst hiding the implementation level how information and hence protecting the user from details of construction. In talking about object-oriented programming, Cox has said: Encapsulation is the foundation of the whole approach... Whereas consumers once specified how each operation should be performed by naming a specific piece of code, they now specify only what should be done, leaving the object to choose code that is appropriate to its type or class (Cox, 1994) In a similar manner Who information is a vital component of human-computer interface design. Users must be characterised so that their specific needs can be adequately catered for. Software project management regimes must cater for the identification of personnel to complete specific development tasks. In this case the Who information refers to the developer rather than the user. The distinction of real-time software design compared to other types of software may be considered to be its time (or order) critical nature. The various methods of specifying dynamic behaviour, such as State-Transition Diagrams, address the when question for processes. Page 2
3 It is considered that existing documentation methods that encode what a system must do and how that function is achieved may fail to record why specific design decisions were made. If software updating efforts are to be consonant with an original design process effort then software engineers must understand why things are they way they are. This paper considers the role of the missing interrogative Why? and proposes a method for documenting the why information of system development Rann, Turner and Whitworth have argued:..a large part of software development effort is spent on making programs evolve to fit new needs. It is common to find that small changes take much longer to implement than would be expected. One reason for this is that it takes programmers some time to understand the system before they can even think about making changes (Rann, Turner and Whitworth 1994) It is considered that this issue may be particularly problematic in the case of safety critical software developments. Errors may be introduced into software designs during the modification and update processes because software engineers fail to appreciate the logic behind particular aspects of the design. Skills may be very diverse within an extended development team on a large system development. It may be argued that to increase harmony between design decisions made by different groups, each group must be able to both communicate and understand why particular decisions have been made. The following text presents a straight-forward method for expressing and documenting why things are, as they are, within a system design. The Essential Logic Model An Essential Logic Model (ELM) tells the story of the system and the decisions that were made during its construction. The ELM shows the relationship between broad classes of requirements and the explanatory concepts developed and used during system development. The diagram also shows the important processes that exist within the system and the objects that the new system will interface to and on which it is dependent. It often the case that during some stage of a large system development, requirements for the system as a whole are decomposed and attributed onto components of the system. The ELM relates this information in a concise manner. The ELM shows how the collection of requirements, existing objects, processes and the explanatory concepts applied to them lead onto the new objects proposed as part of the system. It is considered that the ELM finds a natural place within the collection of Object Oriented Analysis (OOA) conventions and techniques. The relationships between the defined objects and the existing system objects may be documented in an Information Page 3
4 Model (IM) or Entity Relationship Diagram (ERD) (Shlaer and Mellor 1992). This diagram and its accompanying documentation shows how the various components will relate to each other and highlights their important interfaces. If an ERD shows what a system is, then the ELM shows why the system is as it is. The ELM Symbology An ELM consists of four types of boxes as illustrated in figure 1. 1 An Object 2 A Process 3 A Requirement 4 A Concept Figure 1: The Four Symbols of an Essential Logic Model In this diagram Objects are exactly synonymous with the objects of OOA. Processes are synonymous with the processes of Data-Flow Diagrams. Requirements are intended to capture important constraints on system implementation. Concepts are the explanatory notions we introduce to make sense of the system and of the problem domain in general. Each box is given a unique number to facilitate referencing. In an ERD boxes contain short, explicit textual descriptions. Boxes are joined by lines intended to represent the flow of logic. In other words, the lines are not strongly typed in the sense that they represent data-flow or relationships. Rather, they connote the way in which one idea leads to another. The idea in this case may be an abstract concept, but it may also be an explicit requirement, a process or an object. Page 4
5 Accompanying an ELM diagram is a narrative text that provides more details of the story or logic of the design evolution. The next section presents an extended example of this narrative text and the ELM that accompanies it. An Extended Example of an ELM for a Automatic Train Control System The following list of numbered items refer to the ELM in Figures 2a and 2b: 1. There exist such things as 'Trains'. 2. There exist such a things as a 'Railway Network' (tracks and points with topology). 3. Trains must not make contact with each other. 4. Trains must be time-tabled around the network. 5 Time-Tabling (4) and train avoidance (3) represent constraints on train 'time and position'. 6. It is desirable to have a high packing density of trains within the network in order to increase utilisation and average speed. 7. Packing Density may be achieved by utilisation of 'Moving Block Principles'. 8. There are two broad schemes for handling time and position constraints: (1) Autonomous trains with knowledge of piers following avoidance strategy; or (2) A Central Control function with knowledge of all trains issuing nonintersecting paths. The later scheme was chosen 9. The concept of non-intersecting time and position (3+5) coupled with the concept of a central control (8) and of moving block principles (7) leads to a concept of centrally issued, non-intersecting paths (Limit of Movement Authority). 10. The central control (8) mechanism by which Limit of Movement Authorities (LMA) (9) and other moving block principles (7) are implemented is termed a Moving Block Processor. 11. For reasons of speed and safety It is required that trains be driven automatically. 12. The train (1) is subject to physical properties (such as momentum and wheel traction) that introduce time/speed/position constraints into the process of following an LMA. This leads to a concept of Safe Braking Distance. Page 5
6 13. In order to implement a 'Safe Braking Distance' algorithm it is necessary for a 'train' to have accurate information of its location and its speed. 14. Numerical safety requirements (and high-integrity design principles) can only be satisfied with diverse control and protection. 15. The diversity concept (14) has implications for speed and location measurement (13) and this results in diverse mechanisms for speed and location determination. 16. LMAs must be communicated from a central control system to the 'Train'; 17. The mechanism for transporting information from the central control mechanism to the train is are communications units; 18. In order to implement a safe braking distance (12) scheme there has to be a process of braking the train. 19. It is important that the diversity concept (14) be applied to the braking process (18) because braking is a key area of safety. 20. In order for an LMA to have meaning it must relate to a 'known' railway topology. 21. Different railways may have different topologies and topologies may change over time, this implies that such a thing as Configuration Data exists. 22. Configuration data (21) must necessarily be produced. 23. The mechanism for the production of configuration data (22) is a Data Generation Facility. 24. As well as being produced (22), configuration data (21) must be distributed to the various part of the system. 25. It is required that data describing the operational characteristics of should be collected from the various part of the system for the purpose of analysis. 26. The process of distributing data to system components (24) and of collecting data from them (25) is similar enough for both tasks to be efficiently accomplished by a single mechanism. 27. If data is to be analysed (25) then some mechanism must exist for performing this analysis. 28. Trains are fitted with doors. 29. There is a requirement for safe operation of doors that means that doors must reliably, only open under specific circumstances (Train position and time). 30. Platforms may be fitted with Platform Screen Doors (PSDs). 31. As is the case for train doors, there is a requirement for safe operation of the PSD. 32. The general concept of diversity coupled with the requirements for safe door operation leads to a concept of diverse door control. Page 6
7 33. The requirements for safe door opening (29) leads to a concept that there are special, safe positions for door opening. 34. The concept of safe positions for door opening (33) leads to a requirement that the train position must not move away from a safe location whilst the doors are open. 35. The requirement to not move whilst the doors are open (34) leads to the concept that door state must be communicated to the train control system 36. The general concept of diversity (14), the concept of diverse control for door opening (32) and the requirement for automated train driving (11) leads to separate implementations for train control and train protection. Conclusion The ELM has so far been used on two major systems developments by the author. Space does not permit a detailed description of these projects, however the diagrams were generally found to be easy to learn and straightforward to use. At an informal level the ELM was considered to be a useful addition to the armoury of system analysis and documentation tools. The method is tentatively offered here in the hope that it will be applied on further projects and that its usefulness will be measured in a more systematic manner by other workers. Ashworth, C. And Goodland, M. (1990) SSADM: A Practical Approach McGraw-Hill: Berkshire, UK ISBN Cox, B. (1944) Object-Oriented Programming Addison-Wesley ISBN Longworth, G. (1992) A User s Guide to SSADM NCC Blackwell: Manchester ISBN X References Potter, B., Sinclair, J. And Till, D. (1991) An Introduction to Formal Specification and Z Prentice Hall : New York ISBN Page 7
8 Rann, D., Turner, J. And Whitworth, J. (1994) Z: A Beginner s Guide Chapman and Hall: London ISBN X Shlaer, S. and Mellor, S.J. (1992) "Object-Lifecycles: Modelling the World in States" Prentice Hall: Englewood Cliffs Page 8
9 2 Railway Network 3 Train Avoidence 5 Time and Position 11 For reasons of speed and safety It is required that trains be driven automatically 1 Trains 6 Efficiency=> Packing density of trains 4 Time-Tabling Requirement 7 Moving Block Principles 9 Limit of Movement Authority 12 Safe Braking Distance 20 Topological Information about Railway 25 Operational Charatersitics of system must be observed/recorded and analysed 8 Central Control 21 Configuration Data 22 Preparation of data 24 Distribution of Data 10 MBP 23 Data Generation Facility 26 Data Update Unit (DDU) 16 Track to Train Comms 27 Data analysis system 17 MCU/FCU Figure 2 Page 9
10 36 ATP/ATO 14 Diversity 19 Service Brake/ Emergency Brake 18 Train Braking Speed and Location Measurement Tacho's, Dopplers and APRs (APRs) 35 Train control must have door state communicated to it 28 Train Doors 29 Requirement for Safe Operation of Train Doors 32 Diverse Control of Door Opening 34 Train must not move away from safe location when Doors open 30 Platform Screen Doors 31 Requirement for safe operation of PSD 33 Safe opening only possible when train at specific locations Figure 3 Page 10
Software Processes. Ian Sommerville 2004 Software Engineering, 7th edition. Chapter 4 Slide 1
Software Processes Ian Sommerville 2004 Software Engineering, 7th edition. Chapter 4 Slide 1 Objectives To introduce software process models To describe three generic process models and when they may be
More informationSoftware Processes. Objectives. Topics covered. The software process. Waterfall model. Generic software process models
Objectives Software Processes To introduce software process models To describe three generic process models and when they may be used To describe outline process models for requirements engineering, software
More informationObjectives. The software process. Topics covered. Waterfall model. Generic software process models. Software Processes
Objectives Software Processes To introduce software process models To describe three generic process models and when they may be used To describe outline process models for requirements engineering, software
More informationTopics covered. Software process models Process iteration Process activities The Rational Unified Process Computer-aided software engineering
Software Processes Objectives To introduce software process models To describe three generic process models and when they may be used To describe outline process models for requirements engineering, software
More informationInsurance Innovation Challenge. Systemize IT Submission: Product Modelling Workbench
Insurance Innovation Challenge Systemize IT Submission: Product Modelling Workbench systemizeit ltd 2015 A working model of your proposed innovation, product or service. A functional beta product is preferred,
More informationBCS THE CHARTERED INSTITUTE FOR IT. BCS HIGHER EDUCATION QUALIFICATIONS BCS Level 6 Professional Graduate Diploma in IT SOFTWARE ENGINEERING 2
BCS THE CHARTERED INSTITUTE FOR IT BCS HIGHER EDUCATION QUALIFICATIONS BCS Level 6 Professional Graduate Diploma in IT SOFTWARE ENGINEERING 2 Friday 30 th September 2016 - Morning Answer any THREE questions
More informationBCS Certificate in Systems Modelling Techniques Syllabus
BCS Certificate in Systems Modelling Techniques Syllabus Version 3.1 October 2011 Effective: 1 October 2011 Change History Version Number Version 3.0 August 2011 Version 3.1 October 2011 Changes Made Updated
More informationThe software process
Software Processes The software process A structured set of activities required to develop a software system Specification; Design; Validation; Evolution. A software process model is an abstract representation
More informationLectures 2 & 3. Software Processes. Software Engineering, COMP201 Slide 1
Lectures 2 & 3 Software Processes Software Engineering, COMP201 Slide 1 What is a Process? When we provide a service or create a product we always follow a sequence of steps to accomplish a set of tasks
More informationMETHODS of MANAGEMENT INFORMATION SYSTEMS MODELING
MMISMo_OM METHODS of MANAGEMENT INFORMATION SYSTEMS MODELING Course code: IEZ001210W Grażyna Hołodnik-Janczura, Ph.D. K4/Z1 Operation Research, Finance, and Information System Engineering Division B-4,
More informationMISMO_BIS MANAGEMENT INFORMATION SYSTEMS MODELING
MISMO_BIS MANAGEMENT INFORMATION SYSTEMS MODELING Course code: IEZ001203W Grażyna Hołodnik-Janczura, Ph.D. K4/Z1 Operation Research, Finance, and Information System Engineering Division B-4, room 517 phone:
More informationTrends in Change Management for 2018
Trends in Change Management for 2018 Author Melanie Franklin Director Agile Change Management Limited Contents Executive Summary 3 Setting the scene 3 Explaining the value of change management 4 Specific
More informationSoftware Development Methodologies
Software Development Methodologies Lecturer: Raman Ramsin Lecture 7 Agile Methodologies: Scrum 1 Agile Methodologies: Brief History First appeared in 1995. The once-common perception that agile methodologies
More informationCreating Responsive Information Systems with the Help of SSADM
Creating Responsive Information Systems with the Help of SSADM Outline of a methodology to integrate performance and software engineering within a structured method Bálint Molnár Information Technology
More informationThe application of selective door opening within a railway system
The application of selective door opening within a railway system K. Chan & D. Turner Mott MacDonald Limited, UK Abstract In an environment of continuing railway improvement, a new UK Railway Standard
More informationCLASS/YEAR: II MCA SUB.CODE&NAME: MC7303, SOFTWARE ENGINEERING. 1. Define Software Engineering. Software Engineering: 2. What is a process Framework? Process Framework: UNIT-I 2MARKS QUESTIONS AND ANSWERS
More informationA RFBSE model for capturing engineers useful knowledge and experience during the design process
A RFBSE model for capturing engineers useful knowledge and experience during the design process Hao Qin a, Hongwei Wang a*, Aylmer Johnson b a. School of Engineering, University of Portsmouth, Anglesea
More informationMapping Service-Orientation to TOGAF 9 Part IV: Applying Service-Orientation to TOGAF s Service Contracts
Mapping Service-Orientation to TOGAF 9 Part IV: Applying Service-Orientation to TOGAF s Service Contracts by Filippos Santas, Credit Suisse Private Banking in Switzerland In this series of articles we
More informationWorkflow Model Representation Concepts
Workflow Model Representation Concepts József Tick Institute for Software Engineering, John von Neumann Faculty, Budapest Tech tick@bmf.hu Abstract: Workflow management and the possibilities of workflow
More informationINTEGRATION OF AUTONOMOUS SYSTEM COMPONENTS USING THE JAUS ARCHITECTURE
INTEGRATION OF AUTONOMOUS SYSTEM COMPONENTS USING THE JAUS ARCHITECTURE Shane Hansen Autonomous Solutions, Inc. Phone: (435) 755-2980 Fax: (435) 752-0541 shane@autonomoussolutions.com www.autonomoussolutions.com
More informationSoftware Engineering II - Exercise
Software Engineering II - Exercise April 29 th 2009 Software Project Management Plan Bernd Bruegge Helmut Naughton Applied Software Engineering Technische Universitaet Muenchen http://wwwbrugge.in.tum.de
More informationSoftware Engineering
Software Engineering Part I. Aspects and Models of Software Development Process Gunadarma University 1 Software Engineering Outline 1 Introduction 2 Aspects of Software Engineering Software Engineering
More informationA Lightweight Incremental Effort Estimation Model For Use Case Driven Projects
A Lightweight Incremental Effort Estimation Model For Use Case Driven Projects Kan Qi, Dr. Barry Boehm University of Southern California {kqi,boehm}@usc.edu Outline Background of use case driven approach
More informationSafety standards and Scrum A synopsis of three standards
Safety standards and Scrum A synopsis of three standards Tor Stålhane IDI / NTNU, Thor Myklebust and Geir Kjetil Hanssen SINTEF ICT 1. Introduction There are a large number of standards used to develop
More informationLecture 3 Design Approaches and Methods
Lecture outline Unit IMS5302 Lecture 3 Design Approaches and Methods This lecture will cover: Organisation of knowledge Gulf of execution and evaluation Design principles Methodologies for developing effective
More informationBefore You Start Modelling
Chapter 2 Before You Start Modelling This chapter looks at the issues you need to consider before starting to model with ARIS. Of particular importance is the need to define your objectives and viewpoint.
More informationChapter 15. Supporting Practices Service Profiles 15.2 Vocabularies 15.3 Organizational Roles. SOA Principles of Service Design
18_0132344823_15.qxd 6/13/07 4:51 PM Page 477 Chapter 15 Supporting Practices 15.1 Service Profiles 15.2 Vocabularies 15.3 Organizational Roles Each of the following recommended practices can be considered
More informationEssentials of Business Architecture Roger Burlton
April 2, 2019 Essentials of Business Architecture Roger Burlton The Business Architecture Concept Model: Design the Business Phase In the last Column in the series, I broached the idea of a concept model
More informationPlanning tomorrow s railway - role of technology in infrastructure and timetable options evaluation
Planning tomorrow s railway - role of technology in infrastructure and timetable options evaluation D. Wood, S. Robertson Capacity Management Systems, AEA Technology Rail, UK Abstract Whether upgrading
More informationAnalysing client requirements
Analysing client requirements Before you can start to analyse the information you have gathered you should think about what you are trying to achieve . The client has presented you with a business problem.
More informationIndustrial IT System 800xA Engineering
Industrial IT System 800xA Engineering Overview Features and Benefits Integrated Engineering Environment Supports the engineering of the entire extended automation system - from field device to plant management
More informationThe Benefits of Object Oriented Development: Toward a Framework for Evaluation
Association for Information Systems AIS Electronic Library (AISeL) AMCIS 2005 Proceedings Americas Conference on Information Systems (AMCIS) 2005 The Benefits of Object Oriented Development: Toward a Framework
More informationSoftware Processes 1
Software Processes 1 Topics covered Software process models Process activities Coping with change 2 The software process A structured set of activities required to develop a software system. Many different
More informationAgile Tutorial for the Senior Project Class School of Computing and Information Sciences Florida International University
Agile Tutorial for the Senior Project Class School of Computing and Information Sciences Florida International University What is Agile? In simple terms, Agile is a collection of ideas to guide both the
More informationModern Systems Analysis and Design Seventh Edition
Modern Systems Analysis and Design Seventh Edition Jeffrey A. Hoffer Joey F. George Joseph S. Valacich The Systems Development Environment Learning Objectives Define information systems analysis and design.
More informationWatson Internet of Things. Agile Development Why requirements matter
Watson Internet of Things Agile Development Why requirements matter Executive summary The clear benefits of agile development better collaboration, incremental delivery, early error detection and the elimination
More informationLecture 1. In practice, most large systems are developed using a. A software process model is an abstract representation
Chapter 2 Software Processes Lecture 1 Software process descriptions When we describe and discuss processes, we usually talk about the activities in these processes such as specifying a data model, designing
More informationSTEP F DESIGN OF A RECORDKEEPING SYSTEM
STEP F DESIGN OF A RECORDKEEPING SYSTEM September 2001 September 2001 ISBN 0 642 34449 3 Commonwealth of Australia 2001 This work is copyright. Apart from any use as permitted under the Copyright Act 1968,
More informationCriteria For Selection of Software Development Environment For Construction Robotic Systems
Criteria For Selection of Software Development Environment For Construction Robotic Systems Khaled Zied and Derek Seward Engineering department, Lancaster University, Lancaster, LA1 4YR, UK k.zied@lancaster.ac.uk
More informationAvoiding Knowledge Management Pitfalls. Ten Common Mistakes and How to Avoid Them
Avoiding Knowledge Management Pitfalls Ten Common Mistakes and How to Avoid Them Table of Contents Introduction... 1 1. Failure to Set and Track Specific Goals... 1 2. Doing Too Much at Once... 2 3. Starting
More informationDetermination of Problem Frames Based on Role Activity Diagrams Leading to Function Points : A Case Study
International Journal of Computer Science & Communication Vol. 1, No. 2, July-December 2010, pp. 121-127 Determination of Problem Frames Based on Role Activity Diagrams Leading to Function Points : A Case
More informationDeveloped by: Steven Jacobs, Eck Doerry
Developed by: Steven Jacobs, Eck Doerry 1 Consequences of Bad Requirements Engineering http://www.knovelblogs.com/2012/08/30/the-importance-of-requirements-engineering/ 2 Building an efficient organization
More informationGS1 Healthcare - Discussion paper on multi-market packs for pharmaceutical products
Purpose This GS1 Healthcare paper has been written to help demonstrate ways in which GS1 bar codes can be used to minimise the need for multiple bar codes to appear on product packaging while still enabling
More informationII. Software Life Cycle. Laurea Triennale in Informatica Corso di Ingegneria del Software I A.A. 2006/2007 Andrea Polini
II. Software Life Cycle Laurea Triennale in Informatica Corso di Objectives To introduce software process models To describe three generic process models and when they may be used To describe outline process
More informationNigel Beacham Department of Computing Science L4 REQUIREMENTS DURING INCEPTION (CS5037 SYSTEMS ANALYSIS AND DESIGN)
Nigel Beacham Department of Computing Science L4 REQUIREMENTS DURING INCEPTION (CS5037 SYSTEMS ANALYSIS AND DESIGN) WHERE ARE WE NOW? Software development paradigms The Unified Process (UP) paradigm UP
More informationDEPARTMENT OF COMPUTER SCIENCE AND ENGINEERING Software Engineering Third Year CSE( Sem:I) 2 marks Questions and Answers
DEPARTMENT OF COMPUTER SCIENCE AND ENGINEERING Software Engineering Third Year CSE( Sem:I) 2 marks Questions and Answers UNIT 1 1. What are software myths Answer: Management myths: We already have a book
More informationIntroduction to Software Engineering
Introduction to Software Engineering 2. Requirements Collection Mircea F. Lungu Based on a lecture by Oscar Nierstrasz. Roadmap > The Requirements Engineering Process > Functional and non-functional requirements
More informationAutomated Black Box Testing Using High Level Abstraction SUMMARY 1 INTRODUCTION. 1.1 Background
Automated Black Box Testing Using High Level Abstraction Dake Song, MIRSE, USA Dr Uli Dobler, FIRSE, Germany Zach Song, EIT, Canada SUMMARY One of the big bottlenecks of modern signalling projects lies
More informationPRINCE2 and the National and International Standards
PRINCE2 and the National and International Standards Robert Buttrick, Project Workout Limited White Paper December 2012 2 PRINCE2 and the National and International Standards Contents 1 Introduction 3
More informationTutorial Software is the differentiating characteristics in many computer based products and systems. Provide examples of two or three products
Tutorial -1 1. Software is the differentiating characteristics in many computer based products and systems. Provide examples of two or three products and at least one system. 2. Provide five examples of
More informationOracle Unified Method (OUM) The OUM Implement Core Workflow The Key to Understanding and Applying OUM. An Oracle White Paper April 2012
Oracle Unified Method (OUM) The OUM Implement Core Workflow The Key to Understanding and Applying OUM An Oracle White Paper April 2012 OUM Implement Core Workflow White Paper Introduction... 3 OUM is Iterative...
More informationM. Zhao, C. Wohlin, N. Ohlsson and M. Xie, "A Comparison between Software Design and Code Metrics for the Prediction of Software Fault Content",
M. Zhao, C. Wohlin, N. Ohlsson and M. Xie, "A Comparison between Software Design and Code Metrics for the Prediction of Software Fault Content", Information and Software Technology, Vol. 40, No. 14, pp.
More informationManaging Human Factors in the Signalling Programme
Managing Human Factors in the Signalling Programme The latest development in the work of the Human Components Mapping Dr. Amanda C. Elliott Safety Team Banedanmark Presentation Outline Overall aim: To
More informationesign Build and Innovate your business with
esign Innovate your business with and Build Design And Build In the digital age, organisations are increasingly faced with the growing need to be more innovative, but are often confronted with various
More informationSoftware Development Methodologies
Software Development Methodologies Lecturer: Raman Ramsin Lecture 1: Basics 1 Software Development Methodology (SDM) A framework for applying software engineering practices with the specific aim of providing
More informationperspective Burke, ME perspective Burke, ME Conference or Workshop Item This version is available at:
Business strategy and the role of the information professional: a new perspective Burke, ME Title Authors Type URL Published Date 1997 Business strategy and the role of the information professional: a
More informationFMS: A SOFTWARE DEVELOPMENT ENVIRONMENT FOR FARM MANAGEMENT SYSTEMS.
FMS: A SOFTWARE DEVELOPMENT ENVIRONMENT FOR FARM MANAGEMENT SYSTEMS http:// www.cnptia.embrapa.br/fms.html Silvia M.F.S. Massruhá, Carlos A. A. Meira, Clevan R. Costa, Renato Fileto Brazilian Agricultural
More informationManaging the payments landscape Standing still is not an option
www.pwc.co.uk Managing the payments landscape Standing still is not an option The findings from a new PwC survey: Standing still is not an option Fast, efficient and reliable payment systems underpin the
More informationSystem Engineering and Analysis. system environments. Lecture Objectives. System Elements. Definition of System. Information system types
System Engineering and Analysis What is the role of the software? Information system types Manual (read a text by your eyes then summarize using your pen) Automated (get the rmation through a computerized
More informationGE/GN8640. Risk Evaluation and Assessment. Guidance on Planning an Application of the Common Safety Method on. Rail Industry Guidance Note
GN Published by: Block 2 Angel Square 1 Torrens Street London EC1V 1NY Copyright 2014 Rail Safety and Standards Board Limited GE/GN8640 Method on Risk Evaluation and Assessment Issue One; June 2014 Rail
More informationUsine Logicielle. Position paper
Philippe Mils: Contact : Thales Resear & Technology Usine Logicielle Project Coordinator philippe.mils@thalesgroup.com Abstract Usine Logicielle Position paper Usine Logicielle is a project operated in
More informationReliability Engineering & Asset Management (REAM) IMechE Accredited CPD Courses
Reliability Engineering & Asset Management (REAM) IMechE Accredited CPD Courses Prof Jyoti Sinha CEng, FIMechE Programme Director, REAM Head Dynamics Laboratory The University of Manchester has been delivering
More informationSample Exam ISTQB Agile Foundation Questions. Exam Prepared By
Sample Exam ISTQB Agile Foundation Questions Exam Prepared By November 2016 1 #1 Which of the following is the correct pairing according to the Agile Manifesto statement of values? a. Individuals and Interactions
More informationCommunication Model for Cooperative Robotics Simulator. Project Plan. Version 1.0
Communication Model for Cooperative Robotics Simulator Project Plan Version 1.0 1 Introduction This document provides an overview of project plan for Communication Model for Cooperative Robotics Simulator
More information1 Descriptions of Function
Customer Communications Portal Management Telecommunications Issues 1 Descriptions of Function Issues confronting an Energy Company s Management Systems responsible for management of Telecommunications
More informationSoftware Development Methodologies
Software Development Methodologies Lecturer: Raman Ramsin Lecture 4 Integrated Object-Oriented Methodologies: OPM and RUP 1 Object Process Methodology (OPM) Introduced by Dori in 1995. Primarily intended
More informationArcade Game Maker Product Line Concept of Operations
Arcade Game Maker Product Line Concept of Operations ArcadeGame Team July 2003 Table of Contents 1 Overview 1 1.1 Identification 2 1.2 Document Map 2 1.3 Concepts 3 1.4 Readership 3 2 Approach 4 3 Background
More informationCertificate in Project Management Reading List. Version 1.1. June 2011
Certificate in Project Management Reading List Version 1.1 June 2011 Certificate in Project Management The ISEB Project Management Certificate syllabus is designed to indicate the scope of the topics to
More informationSolution-Focused Rating (SFR ): New Ways in Performance Appraisal
Prof. Dr. Günter Lueger Solution-Focused Rating (SFR ): New Ways in Performance Appraisal Introduction Keywords: performance appraisal, appraisal interview, assessment, assessment centre, evaluation, solution-focused
More informationPMP Exam Preparation Workshop. Chapter # 5 Project Scope Management
PMP Exam Preparation Workshop Chapter # 5 Copyright PMI SOC 2013 1 Learning Objectives By the end of this session you will understand: How scope management processes relate to the process groups Project
More information1. Introduction. URDAD for System Design. Table of Contents. Dr. Fritz Solms. Abstract. Use-Case Responsibility Driven Analysis and Design
Solms Training, Consulting and Development Physical: 113 Barry Hertzog Ave, Emmarentia, Johannesburg, South Africa Postal: PostNet Suite no 237, Private Bax X9, Melville 2109, South Africa Phone: +27 (11)
More informationMTAT Enterprise System Integration
MTAT.03.229 Enterprise System Integration Lecture 5: Service-Oriented Architectures Marlon Dumas marlon. dumas ät ut. ee Service-Oriented Architecture (SOA) SOA is a paradigm for organizing and utilizing
More informationIdentifying Candidate Objects during System Analysis
Identifying Candidate Objects during System Analysis Stephan Düwel, Prof. Dr. Wolfgang Hesse University of Marburg Department of Mathematics/Computer Science Hans Meerwein-Str. D-35032 Marburg Germany
More informationOrganizing the Business Process Management Space. Mathias Weske
Organizing the Business Process Management Space Mathias Weske People 2 Real-World Example FP6 IP on Service composition platform Detailed project plan Sub projects dealing with Architecture Case Studies
More informationManaging System Performance
Managing System Performance System performance directly affects users. Centralized operations are easier to measure than complex networks and client/server systems. Various statistics can be used to assess
More informationComputer Aided Process Planning using STEP Neutral File for Automotive Parts
Computer Aided Process Planning using STEP Neutral File for Automotive Parts Vinod V Rampur 1 Assistant professor, Department of Mechanical Engineering PES Institute of Technology and Management Shivamogga,
More information(c) Addison Wesley Chapter 1. ! Software production is an art. ! Two groups. ! Main causes of software failures
MACIASZEK, L.A. (2001): Requirements Analysis and System Design. Developing Information Systems with UML, Addison Wesley Chapter 1 Software Process Copyright 2000 by Addison Wesley Version 1.0 Software
More informationSocial Organization Analysis: A Tutorial
Social Organization Analysis: A Tutorial Gavan Lintern Cognitive Systems Design glintern@cognitivesystemsdesign.net Copyright 2013 by Gavan Lintern Abstract Far less attention has been paid to social organization
More informationcoffee 2 minute guide Due diligence and suitability: what are advisory firms and discretionary investment/fund managers to do?
coffee with corfinancial. May 2016 London 09 2 minute guide Due diligence and suitability: what are advisory firms and discretionary investment/fund managers to do? london boston new york Cor Financial
More informationIEC Is it pain or gain?
IEC 61508 Is it pain or gain? Clive Timms, Director, C&C Technical Support Services Ltd. Introduction IEC 61508 (Ref. 1) provides designers and operators with the first generic internationally accepted
More informationChapter 1 Systems Development in an Organization Context
Systems Development in an Organization Context Learning Objectives Define information systems analysis and design. Describe the information Systems Development Life Cycle (SDLC). Explain Rapid Application
More informationMathcad : Optimize your design and engineering process.
Mathcad : Optimize your design and engineering process. Where engineering excellence begins. ENGINEERING CALCULATION SOFTWARE Solve, document, share and reuse vital engineering calculations. Engineering
More informationSolutions Manual. Object-Oriented Software Engineering. An Agile Unified Methodology. David Kung
2 David Kung Object-Oriented Software Engineering An Agile Unified Methodology Solutions Manual 3 Message to Instructors July 10, 2013 The solutions provided in this manual may not be complete, or 100%
More informationRecording in Social Group Work
226 Social Group Work: Working with Groups The above outline shows how very different activities can help the group learn listening skills. Lots of different skills can be developed in this way from practical
More informationLESSON 6 MANAGERIAL ROLES IN SMALL BUSINESS
LESSON 6 MANAGERIAL ROLES IN SMALL BUSINESS Sonia Sabharwal STRUCTURE 6.0 Introduction 6.1 Objectives 6.2 Enterprise Management 6.3 Managerial Functions 6.4 Summary 6.5 Glossary 6.6 Self Assessment Questions
More informationDEALING WITH MASS AUTOMATION
IT TRANSFORMATION DEALING WITH MASS AUTOMATION There is a recognised shift in the industry towards widespread/mass automation. Although this is not a recent concept, the technologies and techniques to
More informationFramework for Measuring the Quality of Software Specification
Framework for Measuring the Quality of Software Specification E.Stephen, E.Mit Faculty of Computer Science and Information Technology, Universiti Malaysia Sarawak (UNIMAS), 94300 Kota Samarahan, Sarawak.
More informationTHE HARMONISED ELECTRICITY MARKET ROLE MODEL
1 THE HARMONISED ELECTRICITY MARKET ROLE MODEL ASSOCIATED ORGANISATIONS: APPROVED 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 TABLE OF CONTENTS 1 INTRODUCTION...
More informationFACEBOOK GUIDE HOW TO USE FACEBOOK FOR RECRUITMENT MARKETING
FACEBOOK GUIDE HOW TO USE FACEBOOK FOR RECRUITMENT MARKETING 01 01 CONTENTS INTRODUCTION 2 WHAT IS A FACEBOOK PAGE? 3 WHY DO EMPLOYERS USE FACEBOOK? 4 FACEBOOK STRATEGY 5 GETTING STARTED 6 THE BASICS 8
More information7. Model based software architecture
UNIT - III Model based software architectures: A Management perspective and technical perspective. Work Flows of the process: Software process workflows, Iteration workflows. Check Points of The process
More informationOrganising Requirements
Requirements Organisation, Analysis and Evolution Software Requirements and Design CITS 4401 Lecture 20 CITS4401 Software Requirements and Design 2 Viewpoints Organising Requirements Interactor viewpoints:
More informationStrategic Thinking - Processual Process
Author: Acumen Insights Version: 0.1 Date Published: 20-Mar-2009 http://www.acumen-insights.com This document and the contents are the sole property of Acumen Insights Ltd. Any referenced material is the
More informationThe Work Breakdown Structure in the Systems Engineering Process. Abstract. Introduction
The Work Breakdown Structure in the Systems Engineering Process Mark A. Wilson Strategy Bridge International, Inc. 9 North Loudoun Street, Suite 208 Winchester, VA 22601-4798 mwilson@strategybridgeintl.com
More informationThe Systems and Software Product Line Engineering Lifecycle Framework
Revised January 27, 2013 Contact Information: info@biglever.com www.biglever.com 512-426-2227 The Systems and Software Product Line Engineering Lifecycle Framework Report ##200805071r4 Mainstream forces
More informationUsing Provenance to Improve Workflow Design
Using Provenance to Improve Workflow Design Frederico T. de Oliveira 1, Leonardo Murta 1,2, Claudia Werner 1, and Marta Mattoso 1 1 COPPE/ Computer Science Department Federal University of Rio de Janeiro
More informationSoftware Process Improvement plan
UNIVERSITY OF OSLO Software Process Improvement plan TDD Karoline Lunder(karollu@ifi.uio.no) 11/15/2012 INF5181 Table of Contents Introduction... 3 Improvement context... 3 The issue... 3 Process improvement
More informationExtending an Agile Method to Support Requirements Management and Development in Conformance to CMMI
Extending an Agile Method to Support Requirements Management and Development in Conformance to CMMI Alexandre Lazaretti Zanatta 1, Patrícia Vilain 2 1 Instituto de Ciências Exatas e Geociências - Ciência
More informationIDEF0 Activity Modeling
IDEF0 Activity Modeling What is an Activity Model? A representation of the activities and the relationships between and among those activities in an existing or planned system. A collection of diagrams,
More informationChapter 9 Software Evolution and Maintenance. Chapter 9 Software evolution
Chapter 9 Software Evolution and Maintenance 1 Topics covered Evolution processes Change processes for software systems Program evolution dynamics Understanding software evolution Software maintenance
More informationSyllabus Product Management in Information Technology Spring 2017; Mini-4
95-821: Product Management in IT 1 Syllabus 95-821 Product Management in Information Technology Spring 2017; Mini-4 Description: This introductory course (6 Units) is designed for MISM and MSIT students
More information