These courseware materials are to be used in conjunction with Software Engineering: A Practitioner’s Approach, 6/e and are provided with permission by R.S. Pressman & Associates, Inc., copyright © 1996, 2001, 20051WVU, LCSEEWVU, LCSEECS 430CS 430Fall 2004Fall 2004copyright © 1996, 2001, 2005R.S. Pressman & Associates, Inc.For University Use OnlyMay be reproduced ONLY for student use at the university levelwhen used in conjunction with Software Engineering: A Practitioner's Approach.Any other reproduction or use is expressly prohibited.These courseware materials are to be used in conjunction with Software Engineering: A Practitioner’s Approach, 6/e and are provided with permission by R.S. Pressman & Associates, Inc., copyright © 1996, 2001, 20052Requirements AnalysisRequirements AnalysisRequirements analysis Requirements analysis specifies softwarespecifies software’’s operational characteristicss operational characteristicsindicates software's interface with other system elements indicates software's interface with other system elements establishes constraints that software must meetestablishes constraints that software must meetRequirements analysis allows the software engineer Requirements analysis allows the software engineer (called an (called an analystanalystor or modelermodelerin this role) to:in this role) to:elaborate on basic requirements established during earlier elaborate on basic requirements established during earlier requirement engineering tasksrequirement engineering tasksbuild models that depict user scenarios, functional activities, build models that depict user scenarios, functional activities, problem classes and their relationships, system and class problem classes and their relationships, system and class behavior, and the flow of data as it is transformed. behavior, and the flow of data as it is transformed. These courseware materials are to be used in conjunction with Software Engineering: A Practitioner’s Approach, 6/e and are provided with permission by R.S. Pressman & Associates, Inc., copyright © 1996, 2001, 20053A BridgeA Bridgesystem descriptionanalysis modeldesign modelThese courseware materials are to be used in conjunction with Software Engineering: A Practitioner’s Approach, 6/e and are provided with permission by R.S. Pressman & Associates, Inc., copyright © 1996, 2001, 20054Rules of ThumbRules of ThumbThe model should focus on requirements that are visible within tThe model should focus on requirements that are visible within the he problem or business domain. The level of abstraction should be problem or business domain. The level of abstraction should be relatively high. relatively high. Each element of the analysis model should add to an overall Each element of the analysis model should add to an overall understanding of software requirements and provide insight into understanding of software requirements and provide insight into the the information domain, function and behavior of the systeminformation domain, function and behavior of the system..Delay consideration of infrastructure and other nonDelay consideration of infrastructure and other non--functional functional models until design. models until design. Minimize coupling throughout the systemMinimize coupling throughout the system. . Be certain that the analysis model provides value to all Be certain that the analysis model provides value to all stakeholders. stakeholders. Keep the model as simple as it can be. Keep the model as simple as it can be. These courseware materials are to be used in conjunction with Software Engineering: A Practitioner’s Approach, 6/e and are provided with permission by R.S. Pressman & Associates, Inc., copyright © 1996, 2001, 20055Data ModelingData Modelingexamines data objects independently of examines data objects independently of processingprocessingfocuses attention on the data domainfocuses attention on the data domaincreates a model at the customercreates a model at the customer’’s level s level of abstractionof abstractionindicates how data objects relate to one indicates how data objects relate to one anotheranotherThese courseware materials are to be used in conjunction with Software Engineering: A Practitioner’s Approach, 6/e and are provided with permission by R.S. Pressman & Associates, Inc., copyright © 1996, 2001, 20056What is a Data Object?What is a Data Object?ObjectObject——something that is described by a setsomething that is described by a setof attributes (data items) and that will be of attributes (data items) and that will be manipulated within the software (system)manipulated within the software (system)each each instanceinstanceof an object (e.g., a book) of an object (e.g., a book) can be identified uniquely (e.g., ISBN #) can be identified uniquely (e.g., ISBN #) each plays a necessary role in the systemeach plays a necessary role in the systemi.e., the system could not function without i.e., the system could not function without access to instances of the objectaccess to instances of the objecteach is described by attributes that are each is described by attributes that are themselves data itemsthemselves data itemsThese courseware materials are to be used in conjunction with Software Engineering: A Practitioner’s Approach, 6/e and are provided with permission by R.S. Pressman & Associates, Inc., copyright © 1996, 2001, 20057Typical ObjectsTypical Objectsexternal entitiesexternal entities(printer, user, sensor)(printer, user, sensor)thingsthings(e.g, reports, displays, signals) (e.g, reports, displays, signals) occurrences or eventsoccurrences or events(e.g., interrupt, alarm)(e.g., interrupt, alarm)rolesroles(e.g., manager, engineer, salesperson)(e.g., manager, engineer, salesperson)organizational unitsorganizational units(e.g., division, team)(e.g., division, team)placesplaces(e.g., manufacturing floor) (e.g., manufacturing floor) structuresstructures(e.g., employee record)(e.g., employee record)These courseware materials are to be used in conjunction with Software Engineering: A Practitioner’s Approach, 6/e and are provided with permission by R.S. Pressman & Associates, Inc., copyright © 1996, 2001, 20058Data Objects and AttributesData Objects and AttributesA data object contains a set of attributes that A data object contains a set of attributes that act as an aspect, quality,