DOCSLIB.ORG

Geo-DB Requirement Analysis

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
Geo-DB Requirement Analysis 2.1.1. Overview Lifecycle 2 Conceptual Database Design 2.1 Requirement analysis -> Text 2.2 Modeling languages Requirement analysis -> Conceptual Model 2.1.1 Overview Conceptual Design 2.1.2 Requirement Analysis (case study) 2.2.1 Basic Modeling Primitives 2.2.2 Modeling Languages: UML and CREATE TABLE Studentin (SID INTEGER PRIMARY KEY, -> Database schema VName CHAR(20) Name CHAR(30)CREATE NOT TABLENULL, Kurs Entity-Relationship Model (ERM) Logical Schema Design Email Char(40));(KID CHAR(10) PRIMARY KEY, Name CHAR(40) NOT NULL, Dauer INTEGER); CREATE TABLE Order 2.2.3 Conceptual DB design: basics ODate DATE soldBy INTEGER FOREIGN KEY REFEREBCES Peronal(PID) 2.2.4 From Requirements to Models CID INTEGER FOREIGN KEY REFERENCES Customer (CID)); Physical Schema Design -> Access paths References: Kemper / Eickler chap 2, Elmasri / Navathe chap. 3 Administration Garcia-Molina / Ullmann / Widom: chap. 2 © HS-2009 Redesign 02-DBS-Conceptual-2 Database Design:Terminology 2.1.2 Requirement Analysis Most important: talk with your customers! Def.: Database Design The process of defining the overall structure of a database, Tasks during RA: i.e. the schema, on different layers of abstraction. Identify essential "real world" information (e.g. Design levels: Conceptual, logical, physical interviews) Remove redundant, unimportant details Includes "Analysis" and "Design" from SE Clarify unclear natural language statements DB Modeling: defining the "static model" using formal or visual languages Fill remaining gaps in discussions Distinguish data and operations DB SE Requirements Requirements Conceptual modeling Analysis Requirement analysis & Conceptual Design aims at Logical modeling Design focusing thoughts and discussions ! Physical modeling Implementation © HS-2009 02-DBS-Conceptual-3 © HS-2009 02-DBS-Conceptual-4 Example: Geo-DB Requirement Analysis The database we develop will contain data about countries, cities, Clarify unclear statements organizations and geographical facts. In the first step, countries, cities, • what is a country? regions (like "Bundesländer" or geographical regions), and continents Political unit: compare Korea vs South /North Korea are to be represented in the DB. Fill gap • Cities are located in regions. What if In the requirements analysis it has to be clarified, what kind of a country does not have regions? information is supposed to be represented, not how it should be → region is country itself represented! • Can a region belong to different countries? No, but there may be regions with the same name in different countries • Can a country belong to different continents? Yes. Distinguish data from operations First step: filter essential information , ignore unim- • Gross National Product per inhabitant: calculate portant details • "It happens that countries are united" .... Note: importance of some piece of information depends on the application scenario © HS-2009 02-DBS-Conceptual-5 © HS-2009 02-DBS-Conceptual-6 1 2.2.1 Basic modeling primitives Modeling language requirements Conceptual modeling What is the right language for "modeling reality"? Distinguish between types (classes) and individual facts (metadata vs data) Which language primitives ? The name of this woman is Kunz with first name Tamara. As opposed to: An old problem of philosophy: how to describe the A person is identified by first name, last name and birth date. world in an appropriate, comprehensible way? Describe reality on a type level One of the answers were logic languages. They allow to express more than we (currently) want to: Use a graphical language in order to get an overall facts and rules. impression of the domain modeled. e.g.: human(Plato) , ∀x (human(x) ⇒ mortal(x) © HS-2009 02-DBS-Conceptual-7 © HS-2009 02-DBS-Conceptual-8 Basic modeling primitives Basic modeling primitives Modeling the "Real World" Issues Design choices Entity (type) City Country attribute or entity? something which exists, has a name continent: attribute of country or separate entity? City Country Attribute There is never exactly one way of modeling reality. property of an entity populat name name GNP Many good designs, much more bad designs. populat Relationship Country Continent connects two or more entities Identification name name inhabit encom_ area e.g. name obviously identifies continents but not cities passes population? "Non sunt multiplicanda entia praeter necessitatem" Identifying attributes needed at all? William van Ockham, English philosopher, 13th century (Principle of Economy, Law of Parsimony) © HS-2009 02-DBS-Conceptual-9 © HS-2009 02-DBS-Conceptual-10 2.2.2 Modeling notations and languages Graphical modeling languages Entity-Relationship-Model (ERM) Unified modeling language (UML) data-oriented: static modeling of data 1976 introduced by P.P. Chen Modeling of data and operations (Peter P. Chen: The Entity-Relationship Model - Toward a Unified View of Data. ACM TODS 1(1): 9-36, 1976, see Reader) Traditional graphical notation with squares, bullets and diamond Object oriented flavor e.g: each object (entity) has identity - a unique pointer ERM: entities having the same type and the same attribute values are indistinguishable Student Name FName Attributes may be constructed (lists, sets, arrays,…) Matr-Nr Title attend Relationships are directed (uni- or bidirectional) Email ERM: always bidirectional LID Lecture hours © HS-2009 02-DBS-Conceptual-11 © HS-2009 02-DBS-Conceptual-12 2 UML versus ERM 2.2.3 Conceptual Design: Basics UML Entities & attributes attend Called association Student Lecture in UML, may be Matr-Nr LID directed Name Title <Entity> FName Hours entity name {Email} <attribute> assignRoom(R r) attribute list <attribute> register(Lect x) <attribute> Operations on data No methods … multivalued attribute {<attribute>} example: first name for entity Person ERM Student Name FName Matr-Nr attend Title Email LID Lecture We basically use hours simplified UML notation © HS-2009 02-DBS-Conceptual-13 © HS-2009 02-DBS-Conceptual-14 Basics Conceptual Design: Basics Identifying attributes Relationships "Axiom" of Relational DB: <Entity> <Entity> Two individual entities can always be distinguished relates_to <attribute> <attribute> by the values of some of its attribute(s), together <attribute> <attribute> called the key <attribute> <attribute> … <attribute> … … Person <attribute > Key attributes are <<PK1>> name <<PK2 >>birthDate Always have a name underlined firstName Note: one single attribute may not {phones} No direction or annotated by be identifying for an entity. <<PKi >> May have attributes Example: buys No identifying attributes Customer Product << something>> : UML Stereotype, allows to extend UML – here primary key attributes quantity Alternative notation: underline all PK attributes (which we use) © HS-2009 02-DBS-Conceptual-15 © HS-2009 02-DBS-Conceptual-16 Modeling basics Conceptual Design: UML Weak entity Notation ! UML-Terminology Class = entity type (UML: attribute = field) account accTransaction has Object = entity accNumber s_number name day Association = relationship acc_type value //+ or - balance … NO keys: objects are identified by unique address … Relationship may have a direction Example: account statement identified by "number" and "acc_number" which is not attribute of 'statement' entity (!) <Entity> <Entity> relates_to <attribute> <attribute> Def:: A weak entity is an entity identified by some of <attribute> <attribute> <attribute> <attribute> its attributes and the relationship to another entity . … <attribute> … … <attribute > © HS-2009 02-DBS-Conceptual-17 © HS-2009 02-DBS-Conceptual-18 3 Conceptual Design: Basics Conceptual Design: Basics Notation Recursive relationships Sometimes attributes are omitted superior order of relationship role? Employee Employee Employee PK pid name belongs_to first_name superior Country Continent UML-Notation position encompasses salary Roles: particularly useful in recursive relations Role names Used in ERM boss rents and UML Employee child Customer DVD Person renter rental object to distinguish the roles of has superior entities in a parent role names relationship subordinate basically for © HS-2009 02-DBS-Conceptual-19 © HS-2009 02-DBS-Conceptual-20 documentation Conceptual Design: Basics 2.2.3 From requirements to models Multiple relationships Text to conceptual model The only step which cannot be automated <rel 1> Requirements as "cleaned" text <Entity > <Entity > <rel n> conceptual database design There may be no, one or many relationships Rough guideline: correspondence between… between entity types entities - nouns Every city has... relationships and verbs capital_of Country City ...is located in country (exactly one !) lays_in attributes and adjectives or phrases like “has a..”, “is...a” ...has a GNP (but also: .. has a capital) © HS-2009 02-DBS-Conceptual-21 © HS-2009 02-DBS-Conceptual-22 Conceptual Design: case study Summary • Conceptual modeling: the art of structuring the data of an application domain Region belongs-to • Basis: careful requirement analysis r_id: String name: String • Simple, powerful base constructs: population: Numb entities, attributes, relationships is_neighbor position ∈ {N,W,S,E,Z..} • Visual (graphical) language encompass Continent Country • E-R modeling language and UML related name: String capitalOf E-R language simpler name: String area: Numb L_ID: String More appropriate for modeling of data population: Numb area: Numb many dialects locatedIn GNP: Numb area: Compatibility to UML makes sense numb City Some differences, e.g. no keys in UML name: String capital population: Numb longitude: Numb © HS-2009 latitude:02-DBS-Conceptual-23 Numb © HS-2009 02-DBS-Conceptual-24 4.
Load more

Recommended publications
  • Design and Implementation of a Standards Based Ecommerce Solution in the Business-To-Business Area
    Design and implementation of a standards based eCommerce solution in the business-to-business area Thesis of Andreas Junghans Department of Computer Science Karlsruhe University of Applied Sciences, Germany Written at ISB GmbH, Karlstrasse 52-54, 76133 Karlsruhe 03/01/2000 to 08/31/2000 Supervisor at Karlsruhe University of Applied Sciences: Prof. Klaus Gremminger Co-supervisor: Prof. Dr. Lothar Gmeiner Supervisor at ISB GmbH: Dipl.Inform. Ralph Krause Declaration I have written this thesis independently, solely based on the literature and tools mentioned in the chapters and the appendix. This document - in the current or a similar form - has not and will not be submitted to any other institution apart from the Karlsruhe University of Applied Sciences to receive an academical grade. I would like to thank Ralph Krause and Gerlinde Wiest of ISB GmbH for their support over the last six month, as well as Peter Heil and Frank Nielsen of Heidelberger Druckmaschinen AG for providing informa- tion and suggestions for the requirements analysis. Acknowledgements also go to Christian Schenk for his MiKTEX distribution and the Apache group for their XML tools. Finally, I would like to thank Professor Klaus Gremminger of the Karlsruhe University of Applied Sciences for his supervision of this thesis. Karlsruhe, 3rd of September, 2000 (Andreas Junghans) Contents 1 Introduction 1 1.1 Document conventions ...................................... 1 1.2 Subject of this thesis ....................................... 1 1.3 Rough schedule .......................................... 2 2 Requirements analysis 3 2.1 Tools used ............................................. 3 2.2 Domain requirements ....................................... 3 2.2.1 Clarification of terms ................................... 3 2.2.2 Specific requirements on ”Business to Business” applications ............
    [Show full text]
  • Requirements Phase
    Requirements Phase • Chance of a product being on time and within budget is very slim unless the development team knows what the product should do • To achieve this level the development team must analyze the needs of the client as precisely as possible Ch10 Copyright © 2004 by Eugean 1 Hacopians Requirements Phase • After a clear picture of the problem the development teams can answer the question: – What should the product do? • The process of answering this question lies within the requirements phase Ch10 Copyright © 2004 by Eugean 2 Hacopians Requirements Phase • Common misconceptions are: – During requirement phase the developer must determine what the client wants – The client can be unclear as to what they want – The client may not be able to communicate what they want to the developer • Most clients do not understand the software development process Ch10 Copyright © 2004 by Eugean 3 Hacopians Requirements Elicitation • This process is finding out a client’s requirements • Members of the requirements team must be familiar with the application domain • Requirement analysis is the process of: – Understanding the initial requirements – Refining requirements – Extending requirements Ch10 Copyright © 2004 by Eugean 4 Hacopians Requirements Elicitation • This process starts with several members of the requirements analysis team meeting with several members of the client’s team • It is essential to use the correct terminology or settle on an agreed set – Misunderstanding terminology can result in a faulty product – This could result in
    [Show full text]
  • Data Quality Requirements Analysis and Modeling December 1992 TDQM-92-03 Richard Y
    Published in the Ninth International Conference of Data Engineering Vienna, Austria, April 1993 Data Quality Requirements Analysis and Modeling December 1992 TDQM-92-03 Richard Y. Wang Henry B. Kon Stuart E. Madnick Total Data Quality Management (TDQM) Research Program Room E53-320 Sloan School of Management Massachusetts Institute of Technology Cambridge, MA 02139 USA 617-253-2656 Fax: 617-253-3321 Acknowledgments: Work reported herein has been supported, in part, by MITís Total Data Quality Management (TDQM) Research Program, MITís International Financial Services Research Center (IFSRC), Fujitsu Personal Systems, Inc. and Bull-HN. The authors wish to thank Gretchen Fisher for helping prepare this manuscript. To Appear in the Ninth International Conference on Data Engineering Vienna, Austria April 1993 Data Quality Requirements Analysis and Modeling Richard Y. Wang Henry B. Kon Stuart E. Madnick Sloan School of Management Massachusetts Institute of Technology Cambridge, Mass 02139 [email protected] ABSTRACT Data engineering is the modeling and structuring of data in its design, development and use. An ultimate goal of data engineering is to put quality data in the hands of users. Specifying and ensuring the quality of data, however, is an area in data engineering that has received little attention. In this paper we: (1) establish a set of premises, terms, and definitions for data quality management, and (2) develop a step-by-step methodology for defining and documenting data quality parameters important to users. These quality parameters are used to determine quality indicators, to be tagged to data items, about the data manufacturing process such as data source, creation time, and collection method.
    [Show full text]
  • Business Requirements Analysis Document (BRAD) - Trading Partner Performance Management, Release 1.0.0
    Business Requirements Analysis Document (BRAD) - Trading Partner Performance Management, Release 1.0.0 Business Requirements Analysis Document (BRAD) For Trading Partner Performance Management BRAD: 1.0.0 BRG: Trading Partner Performance Management Work Group Date: 7-Nov-2008, Approved 7-Nov-2008, Approved All contents copyright © GS1 2008 Page 1 of 81 Business Requirements Analysis Document (BRAD) - Trading Partner Performance Management, Release 1.0.0 Document Summary Document Item Current Value Document Number 10713 Document Title Business Requirements Analysis Document (BRAD) Date Last Modified 7-Nov-2008 Status Approved Work Group / Chairperson Trading Partner Performance Management / Matt Johnson BRAD Template Version 2.4 Change Request Reference Date of CR Submission to GSMP: CR Submitter(s): Refer to Change Request (CR) Number(s): 13 - Jul – 2007 John Ryu, GS1 07-000283 Document Change History Date of Vers Changed By Reason for Summary of CR # Model Change ion Change Change Build # 31–Oct-2007 0.1.0 John Ryu Initial Draft Section 15 07-000283 N/A 3-Mar–2008 0.2.0 John Ryu Added agreed measures Section 15 Not N/A Matt Johnson Applicable 25-Mar-2008 0.2.2 John Ryu Based on Dallas F2F meeting Section 15 N/A N/A 9-Apr-2008 0.3.0 John Ryu Finalizing for GSMP Meeting on 20080414 Section 15 N/A N/A 11-Apr-2008 0.3.1 John Ryu Based on 20080409 teleconference Section 15 N/A N/A Matt Johnson 22-Apr-2008 0.3.2 John Ryu Based on Brussels F2F Meeting Section 15 N/A N/A 1-May-2008 0.3.3 John Ryu Posting for 60 Day Public Review Section 15 N/A N/A Start May 1 and End on June 30.
    [Show full text]
  • Fault-Based Analysis: How History Can Help Improve Performance and Dependability Requirements for High Assurance Systems
    Fault-Based Analysis: How History Can Help Improve Performance and Dependability Requirements for High Assurance Systems Jane Huffman Hayes David M. Pruett Elizabeth Ashlee Holbrook Geocontrol Systems Inies Raphael C.M. Incorporated University of Kentucky Dept. of Computer Science [email protected] [email protected], {ashlee|irchem2}@uky.edu Abstract Related work is discussed in Section 3. Our position is outlined in Section 4 as well as some Performance and dependability requirements are preliminary results. Finally, conclusions and future key to the development of high assurance systems. work round out the paper in Section 5. Fault-based analysis has proven to be a useful tool for detecting and preventing requirement faults 2. Fault-based analysis early in the software life cycle. By tailoring a generic fault taxonomy, one is able to better “The IEEE standard definition of an error is a prevent past mistakes and develop requirements mistake made by a developer. An error may lead to specifications with fewer overall faults. Fewer one or more faults [13]. To understand Fault- faults within the software specification, with Based Analysis (FBA), a look at a related respect to performance and dependability technique, Fault-Based Testing (FBT), is in order. requirements, will result in high assurance systems Fault-based testing generates test data to of improved quality. demonstrate the absence of a set of pre-specified faults. There are numerous FBT techniques. These 1. Introduction use a list of potential faults to generate test cases, generally for unit- and integration-level testing One needs only look to the increasing [20,3].
    [Show full text]
  • Requirements Analysis Software Requirements
    Requirements Analysis Software Requirements AA softwaresoftware (product)(product) requirementrequirementisis aa feature,feature, function,function, capability,capability, oror propertyproperty thatthat aa softwaresoftware productproduct mustmusthave.have. Software Design AAsoftwaresoftware designdesignisis aa specificationspecification ofof aa softwaresoftware systemsystem thatthat programmersprogrammers cancan implementimplement inin code.code. What vs How The traditional way to distinguish requirements from design: What a system is supposed to do is requirements How a system is supposed to do it is design What vs How Problems The what vs. how criterion is probably unworkable: •Other design disciplines do not make this distinction •Understanding needs and constraints must always be the first step in design •The what vs. how criterion does not hold up in practice Requirements vs Design Determining requirements is really the first step of design. RequirementsRequirementsstatestate clientclient needsneeds andand solutionsolution constraints.constraints. DesignsDesignsstatestate problemproblem solutions.solutions. Requirements Phase Activities Problem or requirements analysis Working with clients to understand their needs and the constraints on solutions Requirements Specification Documenting the requirements These activities are logically distinct but usually occur together. Requirements Phase Problems The requirements phase is HARD! There are several reasons for this: • requirements volatility • requirements elicitation problems • language
    [Show full text]
  • Dependability Attributes for Space Computer Systems
    DEPENDABILITY ATTRIBUTES FOR SPACE COMPUTER SYSTEMS Romani, M.A.S., [email protected] Lahoz, C.H.N., [email protected] Institute of Aeronautics and Space (IAE), São José dos Campos, São Paulo, Brazil Yano, E.T., [email protected] Technological Institute of Aeronautics (ITA), São José dos Campos, São Paulo, Brazil Abstract. Computer systems are increasingly used in critical applications in the space area where a failure can have serious consequences such as loss of mission, properties or lives. One way to improve quality of space computer projects is through the use of dependability attributes such as reliability, availability, safety, etc. to assist the identification of non-functional requirements. This work presents and discusses a minimum set of dependability attributes, selected for software applications, to be used in space projects. These attributes resulted from a research carried out on factors extracted from practices, standards and safety models both from international institutions of the aerospace field such as ESA, NASA and MOD (UK Ministry of Defense), as well as renowned authors in the area. An example illustrates the use of dependability attributes to identify dependability requirements. Keywords: dependability, requirements specification, software quality, space systems 1. INTRODUCTION Computer systems are increasingly used in space, whether in launch vehicles, satellites, and ground support and payload systems. Due to this fact, the software applications used in these systems have become more complex, mainly due to the high number of features to be met, thus contributing to a greater probability of hazards occurrence in a project. Pisacane (2005) emphasizes that spacecraft computer systems require space-qualified microcomputers, memories, and interface devices.
    [Show full text]
  • Defining and Managing Requirements: a Framework for Project Success and Beyond Requirements Are Critical As Project Managers Try to Control Project Failure Rates
    RG Perspective Defining and Managing Requirements: A Framework for Project Success and Beyond Requirements Are Critical as Project Managers Try to Control Project Failure Rates 11 Canal Center Plaza Alexandria, VA 22314 HQ 703-548-7006 Fax 703-684-5189 teamRG.com © 2017 Robbins-Gioia, LLC Defining and Managing Requirements Conventional wisdom says you will never reach Get at the true requirements your destination if you don’t know where you’re Enforce tracking and management of going. However, all too often, that’s exactly how requirements throughout the life-cycle projects are implemented, most often as a result Allow for a structured approach to the of the business and technical staff being unable to review and approval process communicate their needs to each other. This Contribute to future projects so that communication gap usually occurs early in a valuable assets are not lost project, and the negative impacts manifest Each of these four critical success factors is themselves throughout the entire life-cycle. discussed next. Extensive re-work, scope creep, missed deadlines, low morale, and required features being dropped Critical Success Factor #1: Eliciting from product releases are just some of the issues the True Requirements that are costly and can be traced back to a The key to uncovering real requirements (and by fundamental lack of understanding of the business that we mean those that meet true needs) is needs. three-fold. You must have an efficient and For the project manager, unclear requirements are effective process to guide the way requirements the cause of mounting frustration throughout the are gathered and documented; your process must life cycle.
    [Show full text]
  • Requirement Analysis Method of E- Commerce Websites Development for Small- Medium Enterprises, Case Study: Indonesia
    International Journal of Software Engineering & Applications (IJSEA), Vol.5, No.2, March 2014 REQUIREMENT ANALYSIS METHOD OF E- COMMERCE WEBSITES DEVELOPMENT FOR SMALL- MEDIUM ENTERPRISES, CASE STUDY: INDONESIA Veronica S. Moertini1, Suhok2, Silvania Heriyanto3 and Criswanto D. Nugroho4 Informatics Department, Parahyangan Catholic University, Indonesia ABSTRACT Along with the growth of the Internet, the trend shows that e-commerce have been growing significantly in the last several years. This means business opportunities for small-medium enterprises (SMEs), which are recognized as the backbone of the economy. SMEs may develop and run small to medium size of particular e-commerce websites as the solution of specific business opportunities. Certainly, the websites should be developed accordingly to support business success. In developing the websites, key elements of e-commerce business model that are necessary to ensure the success should be resolved at the requirement stage of the development. In this paper, we propose an enhancement of requirement analysis method found in literatures such that it includes activities to resolve the key elements. The method has been applied in three case studies based on Indonesia situations and we conclude that it is suitable to be adopted by SMEs. KEYWORDS Software Requirements Analysis, E-Commerce Website Development, Resolving Key Elements of E- Commerce Business Model 1. INTRODUCTION It is well recognized that small-medium enterprises (SMEs) are significant to the worldwide socio-economic development. It is even viewed that SMEs are the backbone of the economy. SMEs have also contributed significantly in higher growth of employment, output, promotion of exports, and fostering entrepreneurship [5, 7].
    [Show full text]
  • Requirements and Design for Dependable Systems
    COURSE DESCRIPTION – ACADEMIC YEAR 2019/2020 Course title Requirements and Design for Dependable Systems Course code 76052 Scientific sector INF/01 Degree Master in Software Engineering for Information Systems (LM-18) Semester 1 Year 1 Credits 6 Modular No Total lecturing hours 40 Total exercise hours 20 Not compulsory. Non-attending students have to contact the lecturer Attendance at the start of the course to agree on the modalities of the independent study. Prerequisites Basic courses in Programming and Software Engineering. Familiarity with UML and software modelling. Course page https://ole.unibz.it/ Specific educational The course belongs to the type caratterizzanti – discipline informatiche objectives and is part of the Foundations in Software Engineering. The course objective is to familiarize students with tools and techniques to acquire and analyze software requirements, and to define and design a software-based system with the focus on dependability as the key concern. Emphasis is given to traceability of requirements to architecture, to justification of design decisions based on collected requirements, to consequences of design decisions for dependable systems. Students will acquire skills and competencies resulting from the conception, negotiation, documentation and maintenance of dependability requirements in a specific domain and environment. Requirements analysis aims at reviewing, assessing, prioritizing, and balancing the requirements by developing technical specifications (functional and non-functional) for building a system that will meet the needs of the stakeholders. The design of dependable software- based systems aims at identifying or building software components that define the characteristics and quality of such a system. The students are exposed to problem-solving techniques that allow the synthesis of software solutions satisfying the requirements of the system.
    [Show full text]
  • A Tutorial for Requirements Analysis
    Project Scope Management Prof. Dr. Daning Hu Department of Informatics University of Zurich Some of the contents are adapted from “System Analysis and Design” by Dennis, Wixom, &Tegarden. Course Review: What do Project Managers Manage? The Triple Constraint of Project Management •Scope &Quality •Time •Cost 2 Course Review: Project Objectives Scope & Quality (fitness for purpose) Budget (to complete it within the budget) Time (to complete it within the given time) It is clear that these objectives are not in harmony! 3 3 Course Review: Requirements Analysis and System Specification Why is it one of first activities in (software) project life cycle? Need to understand what customer wants first! Goal is to understand the customer’s problem. Though customer may not fully understand it! Requirements analysis says: “Make a list of the guidelines we will use to know when the job is done and the customer is satisfied.” Also called requirements gathering or requirements engineering System specification says: “Here’s a description of what the program/system will do (not how) to satisfy the requirements.” Distinguish requirements gathering & system analysis? A top-level exploration into the problem and discovery of whether it can be done and how long it will take. 4 Learning Objectives: Project Scope Management Explain what scope management is and the related processes Discuss methods for collecting and documenting requirements Explain the scope definition process and describe the contents of a Project Scope Statement Discuss the process of constructing a Work Breakdown Structure (WBS) using various approaches Explain the importance of scope verification and control and how to avoid scope problems 5 What is Project Scope Management? Scope refers to all the work involved in creating the products of the project and the processes used to create them.
    [Show full text]
  • Computer Science CSC 235 System Requirements and Testing Credits and Contact Hours: 3 Credits, Contact Hours: 42 (1 Contact Hour = 50 Minutes) Instructor: Dr
    Computer Science CSC 235 System Requirements and Testing Credits and Contact Hours: 3 Credits, Contact Hours: 42 (1 contact hour = 50 minutes) Instructor: Dr. Vinitha Hannah Subburaj Textbook: 1. Mastering the Requirement Process: Getting Requirements Right, Robertson, S. and Robertson, J., 3rd Edition, Addison-Wesley Professional, 2012. 2. System Analysis and Design, Alan Dennis; Barbara Haley Wixom; Roberta M. Roth, 5th Edition, John Wiley & Sons, 2012 3. The Art of Software Testing, Glenford J. Myers; Corey Sandler; Tom Badgett, 3rd Edition, John Wiley & Sons, 2011 4. Software Testing: Concepts and Operations, Ali Mili; Fairouz Tchier, John Wiley & Sons, 2015 Course description: a. Catalog description: This course focuses on theoretical and practical aspects of system requirements gathering and testing. Students will be introduced to the fundamental concepts in system requirements gathering and testing process. The requirements gathering process includes techniques for eliciting requirements, analyzing, writing, and validating requirement for software systems. Testing process includes introduction to different types of testing models and testing techniques. Testing process also includes analyzing, and developing different components of a test plan using a specific standard. This course will be a combination of traditional lectures and in class activities that emphasize on real world requirements gathering and testing practices. b. Prerequisites: CSC 160 c. Required/Elective: a. Computer Science – Required b. Software Engineering – Required Specific Goals of Course: a. Specific outcomes of instruction After completing this course successfully students should be able to: i. Describe the role of requirements analysis in software development life cycle ii. Elicit requirements using a variety of techniques iii. Represent functional and non-functional requirements for different types of systems using formal and informal techniques iv.
    [Show full text]