Quiz Examination in Software Engineering Theory
|
|
- Rhoda Chandler
- 7 years ago
- Views:
Transcription
1 LINKÖPINGS UNIVERSITET IDA Kristian Sandahl, David Broman Quiz Examination in Software Engineering Theory Date: Time: This quiz examination is optional. If the student passes the quiz examination, he/she will earn 10 extra credits on the written examination on Note: The 10 extra credits will ONLY be valid on the written examination in October They will not be valid on any re-take exam or exams in coming years. This quiz is applicable for students taking / retaking courses: TDDB61, TDDB62, TDDC01, TDDC06, TDDC88, TDDC93. Allowed aids: One volume of dictionary to or from English or an English wordbook. Pass condition: To pass the quiz examination, the student must earn at least 50% of the total amount of possible credits. Result: The correct solution will be published on the course website latest on The individual results will be returned latest on the lecture on Instructions to students, please read carefully This is a multiple choice exam, where each assignment consists of a number of statements. If you think that a statement is true, the checkbox should be marked. If you believe the statement is false, leave the box empty. Note that more than one statement can be true on each assignment. For each statement that is checked and is in fact true, one credit is earned. For each statement that is checked and is in fact false, one credit is lost. It is not possible to get less than 0 credits on each assignment. Example1: A student has selected alternative A, C and D. The correct answer is only A. Hence, the student gets 0 credits out of 1 for the assignment. Example2: A student has selected alternative B. The correct answers are B and C. Hence, the student gets 1 credit out of 2 for the assignment. Good Luck! Kristian Your name (print) Signature Personal number TDDC88-TDDC93 (A) Page 1(8)
2 Problems Assignment 1. Project Management (A) It is not necessary to have a one-to-one relationship between mile-stones and toll-gates. Mile-stones can be set in a project plan without the direct connection to a toll-gate, and it is possible that several mile-stones have to be fulfilled before a single toll-gate passage is due. Mile-stones can be used for all internal goals of a project. (B) A mile-stone should have the properties of a SMART-goal That is in the definition of a mile-stone. (C) A toll-gate is a project-team internal decision False. The very idea with a toll-gate is that external stakeholders, such as, the customer should influence the decision of the continuation of the project. (D) The risk magnitude indicator of a risk is calculated by adding the probability and impact of that risk. False. You multiply the probability and the impact. (E) COCOMO and the Delphi methods are two parametric effort estimation methods False. Delphi is an expert judgmental method which has no connection to parametric estimation methods. Assignment 2. Architecture and Design (A) The pipe-and-filter architecture requires a UNIX-style operating system False. Pipe-and-filter is a general architecture. UNIX has operations that allow the realization of a pipe-and-filter system, even in small scale. TDDC88-TDDC93 (A) Page 2(8)
3 (B) You can combine the pipe-and-filter architecture and the layered architecture by implementing one or several layers according to the pipe-andfilter architecture. Most architectural styles can be applied on various levels. The combination above is not uncommon. (C) The Façade design pattern can be used when implementing a layered architecture. The idea with a single entry point to several components is central both in Façade and layered architecture. The major difference is that Façade does not exclude direct calls behind the Façade. (D) One consequence of having low cohesion is that you don t have to check many modules if you just did a change in one of the modules. False. The statement is true for coupling, which can be independent of cohesion. Even if you have low cohesion you can still have both high and low coupling. Assignment 3. UML part I Clean the machine <<include>> Open machine Service Collect coins <<include>> <<extend>> Add change (A) The use-case Open machine is a base use-case. False. The base use-cases are Clean the machine and Collect coins. Open machine is an inclusion use-case. (B) <<extend>> denotes that this is a stereotype with extended meaning for the association. That is the definition. TDDC88-TDDC93 (A) Page 3(8)
4 (C) The diagram shows that Clean the machine and Collect coins have to be done in parallel as soon as the flow of action is finished for Open machine. False. An actor can be associated with many use-cases without imposing any parallelism. The inclusion of Open the machine has nothing to do with parallelism, its only a convenient way of factoring out common behaviour. Assignment 4. UML - part Ii (A) Several instances of Attribute can be associated to the same instance of Type. (B) The number of the instances of Attribute and Operation must be the same for the instance of a single Class. False. The star indicates an arbitrary number of instances for each association. (C) Type is an abstract class that cannot be instantiated. False. The UML notation would require that the class name was in italic font for an abstract class.. (D) An instance of Attribute can be associated to an instance of Primitive_Type. Primitive_Type inherits the association from Type. TDDC88-TDDC93 (A) Page 4(8)
5 Assignment 5. Testing A B C D E F G H I J K L M (A) In data-flow testing it is acceptable if you find a variable that is first killed and later used. False. The KU is the most serious data flow fault. (B) Control-flow testing statement coverage requires more test cases than condition coverage since there are often more statements than conditions. False. Condition testing is a stronger coverage metric. They are equal for a program that has no conditions. (C) The order of a bottom-up integration testing of components in the hierarchy diagram above can look like: LM, LMK, LMKF, GHIJ, LMKFBCDE, GHIJD, LMKFBCGHIJDEA False. A correct one can look like: LMK, LMKF, LMKFB, GHIJD, LMKFBCGHIJDEA (D) When implementing a bottom-up integration approach, you need to implement drivers. (For a top-down approach, stubs would have been needed instead.) (E) An oracle is a human being or a system that determines if a test is successful by examining the input and the generated output from a test object. TDDC88-TDDC93 (A) Page 5(8)
6 Assignment 6. Requirements part I (A) The requirement The user must be able to change his or her personal password is a functional requirement. (B) The requirement After 14 days of some usage, an average user must be able to run the system for at least 4 hours without using any help information, look up in the user manual or asking a colleague is a functional requirement. False. This is a typical non-functional requirement, even though it is a bit underspecified. (C) The requirement The system shall lower the curtains if disturbing reflections occur in the room. can be regarded as a good, functional requirement meeting most of the desired properties of a requirement. False. It is definitely not a good requirement, it is impossible to test unless specified much better. (D) It is a good idea to make an initial stakeholder analysis before formulating the use-cases, because many of the stakeholders will be represented as actors. (E) It is important to follow the IEEE std 830 for Software Requirements Specification as close as possible. This will make your project compatible with the rest of the world even though you will have to write not applicable for many headlines. False. You should always adapt standards to your own company and customer. A requirements specification shall be as readable as possible, since there are many readers with different background. The standard itself gives suggestion of how to adapt the headlines for different types of software. Assignment 7. Requirements part II (A) Specifying requirements with mathematical, formal notation, such as Z, practically means that you have access to some tool support, since even fairly small systems soon become incomprehensible for humans. Only trivial systems are tractable, for instance, since the satisfiability proof grows exponentially. TDDC88-TDDC93 (A) Page 6(8)
7 (B) Parallel test in acceptance testing means that you investigate if performance can be increased by parallelizing the most critical algorithms. False. In parallel test you are running the new system and an older system in parallel to measure, for instance, increase in efficiency. (C) Requirements elicitation can be performed with demonstrations of different prototypes of a forthcoming system for customers and their endusers. This is a very good method, but you have to be aware that human bias might make the users commit too early to a certain approach to a solution. (D) Classifying requirements along different classification is a waste of time since all requirements are so likely to be changed anyway. False. By, for instance, classifying requirements according to stability you can identify requirements that are not likely to be changed, and give them extra attention as regards testability, clarity etc... (E) When you validate requirements you make sure, for instance, by simulation, that you have specified the true needs of customers and users. Assignment 8. Quality (A) By using the acronym REAL when detailing usability we mean that usability can be sub-divided into Reliability, Egoless Programming, Availability and Low cost. False. We mean Relevance, Efficiency, Attitude and Learnability. The words in the question can, of course, indirectly influence usability, but they are neither direct nor covering most of usability aspects. (B) Failure intensity is measured by grading failures according to a severity ranking scale. False. Failure intensity is measured as the number of failures per execution hour. (C) A safety requirements checklist can contain issues such as: Start-up routines of the system, Exception handling, Data ageing and how certain commands can be reversed. Plus many more. TDDC88-TDDC93 (A) Page 7(8)
8 (D) Prototyping methods, such as agile programming can never reach any quality systems, since they issue releases so frequently that none of them can be made with afterthought. False. For instance, usability benefit a lot from prototyping approaches with demonstration of systems to the end-users. (E) High testability means that it is easy to localize a fault to a single component. That s one reason of why low coupling leads to testable systems. TDDC88-TDDC93 (A) Page 8(8)
Requirements engineering
Learning Unit 2 Requirements engineering Contents Introduction............................................... 21 2.1 Important concepts........................................ 21 2.1.1 Stakeholders and
More informationKarunya University Dept. of Information Technology
PART A Questions 1. Mention any two software process models. 2. Define risk management. 3. What is a module? 4. What do you mean by requirement process? 5. Define integration testing. 6. State the main
More informationTDDC88 Lab 2 Unified Modeling Language (UML)
TDDC88 Lab 2 Unified Modeling Language (UML) Introduction What is UML? Unified Modeling Language (UML) is a collection of graphical notations, which are defined using a single meta-model. UML can be used
More informationRoles in software engineering
Roles in software engineering Software Engineering Theory Kristian Sandahl Department of Computer and Information Science 2015-09-02 Maintenance Validate Requirements, Verify Specification Requirements
More informationRequirements engineering and quality attributes
Open Learning Universiteit Unit 2 Learning Unit 2 Requirements engineering and quality attributes Contents Introduction............................................... 21 2.1 Important concepts........................................
More informationProject Management. Lecture 3. Software Engineering CUGS. Spring 2012 (slides made by David Broman) Kristian Sandahl
Project Lecture 3 Software Engineering CUGS Spring 2012 (slides made by David Broman) Kristian Sandahl Department of Computer and Information Science Linköping University, Sweden A Software Life-cycle
More informationProject Management. Lecture 3. Software Engineering CUGS. Spring 2011 (slides made by David Broman)
Lecture 3 Software Engineering CUGS Spring 2011 (slides made by David Broman) Kristian Sandahl Department of Computer and Information Science Linköping University, Sweden A Software Life-cycle Model Which
More informationMasters of Science in Software & Information Systems
Masters of Science in Software & Information Systems To be developed and delivered in conjunction with Regis University, School for Professional Studies Object Oriented Design Table of Contents January
More informationQuestions? Assignment. Techniques for Gathering Requirements. Gathering and Analysing Requirements
Questions? Assignment Why is proper project management important? What is goal of domain analysis? What is the difference between functional and non- functional requirements? Why is it important for requirements
More information11 Tips to make the requirements definition process more effective and results more usable
1 11 Tips to make the s definition process more effective and results more usable This article discusses what I believe are the key techniques for making s definition process repeatable from project to
More informationIT3205: Fundamentals of Software Engineering (Compulsory)
INTRODUCTION : Fundamentals of Software Engineering (Compulsory) This course is designed to provide the students with the basic competencies required to identify requirements, document the system design
More informationTECH. Requirements. Why are requirements important? The Requirements Process REQUIREMENTS ELICITATION AND ANALYSIS. Requirements vs.
CH04 Capturing the Requirements Understanding what the customers and users expect the system to do * The Requirements Process * Types of Requirements * Characteristics of Requirements * How to Express
More informationSOFTWARE ENGINEERING INTERVIEW QUESTIONS
SOFTWARE ENGINEERING INTERVIEW QUESTIONS http://www.tutorialspoint.com/software_engineering/software_engineering_interview_questions.htm Copyright tutorialspoint.com Dear readers, these Software Engineering
More informationContents. Introduction and System Engineering 1. Introduction 2. Software Process and Methodology 16. System Engineering 53
Preface xvi Part I Introduction and System Engineering 1 Chapter 1 Introduction 2 1.1 What Is Software Engineering? 2 1.2 Why Software Engineering? 3 1.3 Software Life-Cycle Activities 4 1.3.1 Software
More informationNon-Functional Requirements
IBM Software Group Non-Functional Requirements Peter Eeles peter.eeles@uk.ibm.com Agenda IBM Software Group Rational software Definitions Types of requirement Classifying requirements Capturing NFRs Summary
More informationIT3203 Fundamentals of Software Engineering (Compulsory) BIT 2 nd YEAR SEMESTER 3
Fundamentals of Software Engineering (Compulsory) BIT 2 nd YEAR SEMESTER 3 INTRODUCTION This course is designed to provide the students with the basic competencies required to identify requirements, document
More information應 用 測 試 於 軟 體 發 展 生 命 週 期. Testing In The Software Development Life Cycle
The Second Management Innovation and Practices Conference, Tamsui, Taiwan, April 2001,Volume 2, pp59-68 應 用 測 試 於 軟 體 發 展 生 命 週 期 Testing In The Software Development Life Cycle 蔡 博 元 莊 立 文 真 理 大 學 資 訊
More informationDecomposition into Parts. Software Engineering, Lecture 4. Data and Function Cohesion. Allocation of Functions and Data. Component Interfaces
Software Engineering, Lecture 4 Decomposition into suitable parts Cross cutting concerns Design patterns I will also give an example scenario that you are supposed to analyse and make synthesis from The
More informationChapter 4: Tools of Modern Systems Analysis
Just Enough Structured Analysis Chapter 4: Tools of Modern Systems Analysis Nature has... some sort of arithmetical-geometrical coordinate system, because nature has all kinds of models. What we experience
More informationSoftware testing. Objectives
Software testing cmsc435-1 Objectives To discuss the distinctions between validation testing and defect testing To describe the principles of system and component testing To describe strategies for generating
More informationThe Role of the Software Architect
IBM Software Group The Role of the Software Architect Peter Eeles peter.eeles@uk.ibm.com 2004 IBM Corporation Agenda Architecture Architect Architecting Requirements Analysis and design Implementation
More informationUML Diagram Types. Use Cases do the Following. Use Case Diagram
UML Diagram Types Dynamic Models activity diagrams statechart diagrams interaction diagrams sequence diagrams collaboration diagrams use case diagrams Structural Models class diagrams object diagrams packages
More informationRequirements / Use Case Specification
Object - Oriented Programming & Design Part IX - UML Use Case Diagrams CSCI 4448 - Spring 2002 Requirements / Use Case Specification Your way of echoing to the customer what you heard him/her say he/she
More informationSoftware Requirements Metrics
Software Requirements Metrics Fairly primitive and predictive power limited. Function Points Count number of inputs and output, user interactions, external interfaces, files used. Assess each for complexity
More informationSoftware Engineering. How does software fail? Terminology CS / COE 1530
Software Engineering CS / COE 1530 Testing How does software fail? Wrong requirement: not what the customer wants Missing requirement Requirement impossible to implement Faulty design Faulty code Improperly
More informationHow To Develop Software
Software Engineering Prof. N.L. Sarda Computer Science & Engineering Indian Institute of Technology, Bombay Lecture-4 Overview of Phases (Part - II) We studied the problem definition phase, with which
More informationCOURSE CODE : 4072 COURSE CATEGORY : A PERIODS / WEEK : 4 PERIODS / SEMESTER : 72 CREDITS : 4
COURSE TITLE : SOFTWARE ENGINEERING COURSE CODE : 4072 COURSE CATEGORY : A PERIODS / WEEK : 4 PERIODS / SEMESTER : 72 CREDITS : 4 TIME SCHEDULE MODULE TOPICS PERIODS 1 Software engineering discipline evolution
More informationSOFTWARE QUALITY MODELS: A COMPARATIVE STUDY
SOFTWARE QUALITY MODELS: A COMPARATIVE STUDY Mrs. Manisha L. Waghmode Assistant Professor Bharati Vidyapeeth Deemed University, Institute of Management and Rural Development Administration, Sangli Dr.
More informationSOFTWARE REQUIREMENTS
SOFTWARE REQUIREMENTS http://www.tutorialspoint.com/software_engineering/software_requirements.htm Copyright tutorialspoint.com The software requirements are description of features and functionalities
More informationSoftware Testing. Definition: Testing is a process of executing a program with data, with the sole intention of finding errors in the program.
Software Testing Definition: Testing is a process of executing a program with data, with the sole intention of finding errors in the program. Testing can only reveal the presence of errors and not the
More informationQuality Management. Lecture 12 Software quality management
Quality Management Lecture 12 Software quality management doc.dr.sc. Marko Jurčević prof.dr.sc. Roman Malarić University of Zagreb Faculty of Electrical Engineering and Computing Department of Fundamentals
More informationModernized and Maintainable Code. Frank Weil, Ph.D. UniqueSoft, LLC
Modernized and Maintainable Code Frank Weil, Ph.D. UniqueSoft, LLC UniqueSoft is a provider of next-generation software development tools and services specializing in modernizing legacy software using
More informationCPS122 Lecture: State and Activity Diagrams in UML
CPS122 Lecture: State and Activity Diagrams in UML Objectives: last revised February 14, 2012 1. To show how to create and read State Diagrams 2. To introduce UML Activity Diagrams Materials: 1. Demonstration
More informationBasic academic skills (1) (2) (4) Specialized knowledge and literacy (3) Ability to continually improve own strengths Problem setting (4) Hypothesis
1. Course Title(Course Code) Software Engineering(2236) 2. Instructor Mamoru ITO 3. Term Spring 1 4. Outline and Objectives Software plays an increasingly important role in the evolution of ICT systems.
More informationRemigijus Gustas. Department of Information Systems, Karlstad University, Sweden
Department of Information Systems, Karlstad University, Sweden Underlying principles of conventional Conceptual Modeling Approaches EM methods distinguish disparate views/dimensions (Zachman, 1987). UML
More informationThe Role of Information Technology Studies in Software Product Quality Improvement
The Role of Information Technology Studies in Software Product Quality Improvement RUDITE CEVERE, Dr.sc.comp., Professor Faculty of Information Technologies SANDRA SPROGE, Dr.sc.ing., Head of Department
More informationCharacteristics of Computational Intelligence (Quantitative Approach)
Characteristics of Computational Intelligence (Quantitative Approach) Shiva Vafadar, Ahmad Abdollahzadeh Barfourosh Intelligent Systems Lab Computer Engineering and Information Faculty Amirkabir University
More informationSoftware Requirements Specification
1 of 7 17.04.98 13:32 Software Requirements Specification The sub-sections : 1. What is a Software Requirements Specification 2. Why is a Software Requirement Specification Required 3. What is Contained
More informationIn this Lecture you will Learn: Systems Development Methodologies. Why Methodology? Why Methodology?
In this Lecture you will Learn: Systems Development Methodologies What a systems development methodology is Why methodologies are used The need for different methodologies The main features of one methodology
More informationRequirements Engineering for Web Applications
Web Engineering Requirements Engineering for Web Applications Copyright 2013 Ioan Toma & Srdjan Komazec 1 What is the course structure? # Date Title 1 5 th March Web Engineering Introduction and Overview
More informationObject-Oriented Systems Analysis and Design
Object-Oriented Systems Analysis and Design Noushin Ashrafi Professor of Information System University of Massachusetts-Boston Hessam Ashrafi Software Architect Pearson Education International CONTENTS
More informationSoftware Engineering Question Bank
Software Engineering Question Bank 1) What is Software Development Life Cycle? (SDLC) System Development Life Cycle (SDLC) is the overall process of developing information systems through a multi-step
More informationCREDENTIALS & CERTIFICATIONS 2015
THE COMMUNITY FOR TECHNOLOGY LEADERS www.computer.org CREDENTIALS & CERTIFICATIONS 2015 KEYS TO PROFESSIONAL SUCCESS CONTENTS SWEBOK KNOWLEDGE AREA CERTIFICATES Software Requirements 3 Software Design
More informationUsing Power to Improve C Programming Education
Using Power to Improve C Programming Education Jonas Skeppstedt Department of Computer Science Lund University Lund, Sweden jonas.skeppstedt@cs.lth.se jonasskeppstedt.net jonasskeppstedt.net jonas.skeppstedt@cs.lth.se
More informationIEEE Computer Society Certified Software Development Associate Beta Exam Application
IEEE Computer Society Certified Software Development Associate Beta Exam Application Candidate Information (please print or type) Name Address ( Home Business) City, State, Postal Code Country Telephone
More informationICS 121 Lecture Notes Spring Quarter 96
Software Management Cost Estimation Managing People Management Poor managment is the downfall of many software projects Ð Delivered software was late, unreliable, cost several times the original estimates
More information(BA122) Software Engineer s Workshop (SEW)
Training for the Business Analyst (BA122) Software Engineer s Workshop (SEW) Duration: 4 days CDUs (Continuing Development Units): 28 Description: A practical workshop covering the role of the Business-Systems
More informationHow To Understand The Organizational Model Of A Multiagent System
A UML-Based Notation for Representing MAS Organizations WOA 2011 Dodicesimo Workshop Nazionale "Dagli Oggetti agli Agenti" M. C O S S E N T I N O, C. L O D A T O, S. L O P E S, P. R I B I N O I C A R I
More informationCOSC 3351 Software Design. Recap for the first quiz. Edgar Gabriel. Spring 2008. For the 1 st Quiz
COSC 3351 Software Design Recap for the first quiz Spring 2008 For the 1 st Quiz Three large topic areas: UML syntax and diagrams Software architectural styles Object oriented design principles A couple
More informationInformation Systems Analysis and Design CSC340. XXIV. Other Phases
XXIV. Other Phases Implementation Phase Testing and Installation Phase Post-Installation Tasks Course Summary 2004 John Mylopoulos Other Phases -- 1 The Software Lifecycle Revisited Survey project scope
More informationGrowing Agents - An Investigation of Architectural Mechanisms for the Specification of Developing Agent Architectures
Growing Agents - An Investigation of Architectural Mechanisms for the Specification of Developing Agent Architectures Virgil Andronache Matthias Scheutz University of Notre Dame Notre Dame, IN 46556 e-mail:
More informationLecture 03 (04.11.2013) Quality of the Software Development Process
Systeme hoher Qualität und Sicherheit Universität Bremen, WS 2013/14 Lecture 03 (04.11.2013) Quality of the Software Development Process Christoph Lüth Christian Liguda Your Daily Menu Models of Software
More informationUse Cases. Massimo Felici. Massimo Felici Use Cases c 2004 2011
Use Cases Massimo Felici Use Cases 1 Support requirements engineering activities and the requirement process Capture what a system is supposed to do, i.e., systems functional requirements Describe sequences
More informationSocial Network Website to Monitor Behavior Change Design Document
Social Network Website to Monitor Behavior Change Design Document Client: Yolanda Coil Advisor: Simanta Mitra Team #11: Gavin Monroe Nicholas Schramm Davendra Jayasingam Table of Contents PROJECT TEAM
More informationSoftware Specification and Architecture 2IW80
Software Specification and Architecture 2IW80 Julien Schmaltz (slides partly from M. Mousavi and A. Serebrenik) Lecture 03: Use Cases Before we start The system shall give access to the database to any
More informationSoftware Metrics. Lord Kelvin, a physicist. George Miller, a psychologist
Software Metrics 1. Lord Kelvin, a physicist 2. George Miller, a psychologist Software Metrics Product vs. process Most metrics are indirect: No way to measure property directly or Final product does not
More informationSoftware cost estimation
Software cost estimation Ian Sommerville 2004 Software Engineering, 7th edition. Chapter 26 Slide 1 Objectives To introduce the fundamentals of software costing and pricing To describe three metrics for
More informationAerospace Software Engineering
16.35 Aerospace Software Engineering Software Architecture The 4+1 view Patterns Prof. Kristina Lundqvist Dept. of Aero/Astro, MIT Why Care About Software Architecture? An architecture provides a vehicle
More informationA Software Engineering Model for Mobile App Development
APPENDIX C A Software Engineering Model for Mobile App Development As we mentioned early in the book (see Chapter 1), to successfully develop a mobile software solution you should follow an engineering
More informationDevelopment of AUTOSAR Software Components within Model-Based Design
2008-01-0383 Development of AUTOSAR Software Components within Model-Based Design Copyright 2008 The MathWorks, Inc. Guido Sandmann Automotive Marketing Manager, EMEA The MathWorks Richard Thompson Senior
More informationIntroduction to Algorithms March 10, 2004 Massachusetts Institute of Technology Professors Erik Demaine and Shafi Goldwasser Quiz 1.
Introduction to Algorithms March 10, 2004 Massachusetts Institute of Technology 6.046J/18.410J Professors Erik Demaine and Shafi Goldwasser Quiz 1 Quiz 1 Do not open this quiz booklet until you are directed
More informationStructure of Presentation. Stages in Teaching Formal Methods. Motivation (1) Motivation (2) The Scope of Formal Methods (1)
Stages in Teaching Formal Methods A. J. Cowling Structure of Presentation Introduction to Issues Motivation for this work. Analysis of the Role of Formal Methods Define their scope; Review their treatment
More informationBCS Certificate in Systems Modelling Techniques Syllabus
BCS Certificate in Systems Modelling Techniques Syllabus Version 3.4 March 2015 Change History Any changes made to the syllabus shall be clearly documented with a change history log. This shall include
More informationThe Software Development Process
Systeme hoher Qualität und Sicherheit Universität Bremen WS 2015/2016 Lecture 03 (26.10.2015) The Software Development Process Christoph Lüth Jan Peleska Dieter Hutter Your Daily Menu Models of software
More informationHow To Understand Software Engineering
PESIT Bangalore South Campus Department of MCA SOFTWARE ENGINEERING 1. GENERAL INFORMATION Academic Year: JULY-NOV 2015 Semester(s):III Title Code Duration (hrs) SOFTWARE ENGINEERING 13MCA33 Lectures 52Hrs
More information3. Mathematical Induction
3. MATHEMATICAL INDUCTION 83 3. Mathematical Induction 3.1. First Principle of Mathematical Induction. Let P (n) be a predicate with domain of discourse (over) the natural numbers N = {0, 1,,...}. If (1)
More informationCHAPTER 2. Logic. 1. Logic Definitions. Notation: Variables are used to represent propositions. The most common variables used are p, q, and r.
CHAPTER 2 Logic 1. Logic Definitions 1.1. Propositions. Definition 1.1.1. A proposition is a declarative sentence that is either true (denoted either T or 1) or false (denoted either F or 0). Notation:
More informationCPS122 - OBJECT-ORIENTED SOFTWARE DEVELOPMENT. Team Project
CPS122 - OBJECT-ORIENTED SOFTWARE DEVELOPMENT Team Project Due Dates: See syllabus for due dates for each milestone This project spans much of the semester, to be completed as a series of milestones, each
More informationAssuming the Role of Systems Analyst & Analysis Alternatives
Assuming the Role of Systems Analyst & Analysis Alternatives Nature of Analysis Systems analysis and design is a systematic approach to identifying problems, opportunities, and objectives; analyzing the
More informationSwirl. Multiplayer Gaming Simplified. CS4512 Systems Analysis and Design. Assignment 1 2010. Marque Browne 0814547. Manuel Honegger - 0837997
1 Swirl Multiplayer Gaming Simplified CS4512 Systems Analysis and Design Assignment 1 2010 Marque Browne 0814547 Manuel Honegger - 0837997 Kieran O' Brien 0866946 2 BLANK MARKING SCHEME 3 TABLE OF CONTENTS
More informationLecture 03 (26.10.2015) The Software Development Process. Software Development Models. Where are we? Your Daily Menu.
Your Daily Menu Systeme hoher Qualität und Sicherheit Universität Bremen WS 2015/2016 Lecture 03 (26.10.2015) The Software Development Process Christoph Lüth Jan Peleska Dieter Hutter Models of software
More informationSoftware Engineering. What is SE, Anyway? Based on Software Engineering, 7 th Edition by Ian Sommerville
Software Engineering What is SE, Anyway? Based on Software Engineering, 7 th Edition by Ian Sommerville Objectives To introduce software engineering and to explain its importance To set out the answers
More informationChapter 4 Software Lifecycle and Performance Analysis
Chapter 4 Software Lifecycle and Performance Analysis This chapter is aimed at illustrating performance modeling and analysis issues within the software lifecycle. After having introduced software and
More informationApplying 4+1 View Architecture with UML 2. White Paper
Applying 4+1 View Architecture with UML 2 White Paper Copyright 2007 FCGSS, all rights reserved. www.fcgss.com Introduction Unified Modeling Language (UML) has been available since 1997, and UML 2 was
More informationSoftware Development: An Introduction
Software Development: An Introduction Fact: Software is hard. Imagine the difficulty of producing Windows 2000 29 million lines of code 480,000 pages of listing if printed a stack of paper 161 feet high
More informationReliably computing cellular automaton, in 1-sparse noise
Reliably computing cellular automaton, in 1-sparse noise Peter Gács Boston University Peter Gács (Boston University) TRG Spring 2010 1 / 23 Ths is the second one of a series of three lectures on reliable
More informationSoftware Quality Management
Software Lecture 9 Software Engineering CUGS Spring 2011 Kristian Sandahl Department of Computer and Information Science Linköping University, Sweden A Software Life-cycle Model Which part will we talk
More informationRequirements Engineering Process
Software Engineering Requirements Engineering Process Based on Software Engineering, 7 th Edition by Ian Sommerville Objectives To describe the principal requirements engineering activities and d their
More informationModeling Guidelines Manual
Modeling Guidelines Manual [Insert company name here] July 2014 Author: John Doe john.doe@johnydoe.com Page 1 of 22 Table of Contents 1. Introduction... 3 2. Business Process Management (BPM)... 4 2.1.
More informationOutline. Definitions. Course schedule
SENG480A/CSC576A Topics in Software Engineering Software Development, Architecture & Evolution Lectures, Sep 17, 20, 2001 Hausi A. Müller University of Victoria Outline Assignment 1 due Sep 27 Last week
More informationR214 SPECIFIC REQUIREMENTS: INFORMATION TECHNOLOGY TESTING LABORATORY ACCREDITATION PROGRAM
The American Association for Laboratory Accreditation Document Revised: R214: Specific Requirements: Information Technology Testing Laboratory Accreditation July 13, 2010 Program Page 1 of 26 R214 SPECIFIC
More informationChapter 7: Software Engineering
Chapter 7: Software Engineering Computer Science: An Overview Eleventh Edition by J. Glenn Brookshear Copyright 2012 Pearson Education, Inc. Chapter 7: Software Engineering 7.1 The Software Engineering
More informationCase studies: Outline. Requirement Engineering. Case Study: Automated Banking System. UML and Case Studies ITNP090 - Object Oriented Software Design
I. Automated Banking System Case studies: Outline Requirements Engineering: OO and incremental software development 1. case study: withdraw money a. use cases b. identifying class/object (class diagram)
More informationVancouver Chapter Study Group. BABOK Chapter 1 Introduction. Jorge Vega
Vancouver Chapter Study Group BABOK Chapter 1 Introduction Jorge Vega 1 Study Group Sessions About me Format BABOK 2.0 Frequency Type of sessions Prep work required Professional Development Units Expanding
More informationCourse Outline. Foundation of Business Analysis Course BA30: 4 days Instructor Led
Foundation of Business Analysis Course BA30: 4 days Instructor Led Prerequisites: No prerequisites - This course is suitable for both beginner and intermediate Business Analysts who would like to increase
More informationOrganizational Requirements Engineering
Chapter 9, Non-functional Requirements Organizational Requirements Engineering Prof. Dr. Armin B. Cremers Sascha Alda Armin B. Cremers, Sascha Alda Organizational Requirements Engineering 1 Overview of
More informationUser experience storyboards: Building better UIs with RUP, UML, and use cases
Copyright Rational Software 2003 http://www.therationaledge.com/content/nov_03/f_usability_jh.jsp User experience storyboards: Building better UIs with RUP, UML, and use cases by Jim Heumann Requirements
More informationSoftware Requirements Specification. Task Management System. for. Prepared by. Version 1.0. Group Name: Pink and Purple. Date:
Software Requirements Specification for Task Management System Version 1.0 Prepared by Group Name: Pink and Purple Kathrynn Gonzalez 11387240 kathrynn.gonzalez@gmail.com Tina Roper 11380457 troper17@comcast.net
More information4. Multiagent Sys stems Design. Part 2: The PROMETHEUS methodology.
4. Multiagent Systems Design Part 2: Multiagent Syste ems (SMA-UPC) https://kemlg.upc.edu The PROMETHEUS methodology. Javier Vázquez-Salceda SMA-UPC Methodological Extensions to Object-Oriented Approaches
More informationA Framework for Software Architecture Visualization and Evaluation
A Framework for Software Architecture Visualization and Evaluation Dr. S. Margret Anouncia Merin Cherian Anubhuti Parija Professor, M.S Software Engg M.S Software Engg School of Computing Sciences VITU,
More informationLecture 8 About Quality and Quality Management Systems
Lecture 8 About Quality and Quality Management Systems Kari Systä 10.03.2014 10.03.2014 TIE-21100/21106; K.Systä 1 Content of today s lecture Two weeks ago we discussed about testing and inspections, that
More informationBCS THE CHARTERED INSTITUTE FOR IT. BCS HIGHER EDUCATION QUALIFICATIONS BCS Level 5 Diploma in IT SYSTEMS ANALYSIS & DESIGN EXAMINERS REPORT
BCS THE CHARTERED INSTITUTE FOR IT BCS HIGHER EDUCATION QUALIFICATIONS BCS Level 5 Diploma in IT SYSTEMS ANALYSIS & DESIGN EXAMINERS REPORT Monday 28 th September 2015 Case Study for both sections A and
More informationIF2261 Software Engineering. Introduction. What is software? What is software? What is software? Failure Curve. Software Applications Type
IF2261 Software Engineering Introduction Program Studi Teknik Informatika STEI ITB What is software? Definitions: Computer programs, procedures, and possibly associated documentation and data pertaining
More informationLecture 9: Requirements Modelling
A little refresher: What are we modelling? Lecture 9: Requirements Modelling Requirements; Systems; Systems Thinking Role of Modelling in RE Why modelling is important Limitations of modelling Brief overview
More informationHow to contribute to the joint course on software engineering by case studies
How to contribute to the joint course on software engineering by case studies Zoran Budimac, Klaus Bothe Version: February 27, 2004. Abstract. This document describes where and how the joint course on
More informationAn Introduction to Software Engineering
An Introduction to Software Engineering Ian Sommerville 2004 Software Engineering, 7th edition. Chapter 1 Slide 1 Objectives To introduce software engineering and to explain its importance To set out the
More informationAn Introduction to Software Engineering. Ian Sommerville 2004 Software Engineering, 7th edition. Chapter 1 Slide 1
An Introduction to Software Engineering Ian Sommerville 2004 Software Engineering, 7th edition. Chapter 1 Slide 1 Objectives To introduce software engineering and to explain its importance To set out the
More informationApplication of UML in Real-Time Embedded Systems
Application of UML in Real-Time Embedded Systems Aman Kaur King s College London, London, UK Email: aman.kaur@kcl.ac.uk Rajeev Arora Mechanical Engineering Department, Invertis University, Invertis Village,
More informationCertified Software Quality Engineer (CSQE) Body of Knowledge
Certified Software Quality Engineer (CSQE) Body of Knowledge The topics in this Body of Knowledge include additional detail in the form of subtext explanations and the cognitive level at which the questions
More informationThe V-model. Validation and Verification. Inspections [24.3] Testing overview [8, 15.2] - system testing. How much V&V is enough?
Validation and Verification Inspections [24.3] Testing overview [8, 15.2] - system testing Requirements Design The V-model V & V Plans Implementation Unit tests System tests Integration tests Operation,
More information