Principles of Engineering Economic Analysis, 5th edition Chapter 11 Replacement Analysis.
Chapter 8 Analysis Engineering
-
Upload
jackson-lambert -
Category
Documents
-
view
23 -
download
5
description
Transcript of Chapter 8 Analysis Engineering
![Page 1: Chapter 8 Analysis Engineering](https://reader036.fdocuments.in/reader036/viewer/2022062314/56812c5b550346895d90e705/html5/thumbnails/1.jpg)
Chapter 8Analysis Engineering
Software Engineering: A Practitioner’s Approach
by Roger S. Pressman
![Page 2: Chapter 8 Analysis Engineering](https://reader036.fdocuments.in/reader036/viewer/2022062314/56812c5b550346895d90e705/html5/thumbnails/2.jpg)
Analysis Model
Elements of the analysis model
![Page 3: Chapter 8 Analysis Engineering](https://reader036.fdocuments.in/reader036/viewer/2022062314/56812c5b550346895d90e705/html5/thumbnails/3.jpg)
Scenario-Based Modeling
![Page 4: Chapter 8 Analysis Engineering](https://reader036.fdocuments.in/reader036/viewer/2022062314/56812c5b550346895d90e705/html5/thumbnails/4.jpg)
Use-case Diagram
Use-case diagram for surveillance function
![Page 5: Chapter 8 Analysis Engineering](https://reader036.fdocuments.in/reader036/viewer/2022062314/56812c5b550346895d90e705/html5/thumbnails/5.jpg)
Alternative Actions
Can the actor take some other action at this point?
Is it possible that the actor will encounter some error condition at this point?
Is it possible that the actor will encounter behavior invoked by some event outside the actor’s control?
![Page 6: Chapter 8 Analysis Engineering](https://reader036.fdocuments.in/reader036/viewer/2022062314/56812c5b550346895d90e705/html5/thumbnails/6.jpg)
Activity diagram for Access camera surveillance—display camera views function
![Page 7: Chapter 8 Analysis Engineering](https://reader036.fdocuments.in/reader036/viewer/2022062314/56812c5b550346895d90e705/html5/thumbnails/7.jpg)
Swimlane diagram
![Page 8: Chapter 8 Analysis Engineering](https://reader036.fdocuments.in/reader036/viewer/2022062314/56812c5b550346895d90e705/html5/thumbnails/8.jpg)
Flow-Oriented Modeling
![Page 9: Chapter 8 Analysis Engineering](https://reader036.fdocuments.in/reader036/viewer/2022062314/56812c5b550346895d90e705/html5/thumbnails/9.jpg)
Guidelines
Depict the system as single bubble in level 0. Carefully note primary input and output. Refine by isolating candidate processes and their
associated data objects and data stores. Label all elements with meaningful names. Maintain information conformity between levels. Refine one bubble at a time.
![Page 10: Chapter 8 Analysis Engineering](https://reader036.fdocuments.in/reader036/viewer/2022062314/56812c5b550346895d90e705/html5/thumbnails/10.jpg)
Data Flow Diagram
Context-level DFD for SafeHome security function
![Page 11: Chapter 8 Analysis Engineering](https://reader036.fdocuments.in/reader036/viewer/2022062314/56812c5b550346895d90e705/html5/thumbnails/11.jpg)
Grammatical Parse
The SafeHome security function enables the homeowner to configure the security system when it is installed, monitors all sensors connected to the security system, and interacts with the homeowner through the Internet, a PC, or a control panel.
During installation, the SafeHome PC is used to program and configure the system. Each sensor is assigned a number and type, a master password is programmed for arming and disarming the system, and telephone number(s) are input for dialing when a sensor event occurs.
When a sensor event is recognized, the software invokes an audible alarm attached to the system. After a delay time that is specified by the homeowner during system configuration activities, the software dials a telephone number of a monitoring service, provides information about the location, reporting the nature of the event that has been detected. The telephone number will be redialed every 20 seconds until a telephone connection is obtained.
The homeowner receives security information via a control panel, the PC, or a browser, collectively called an interface. The interface displays prompting messages and system status information on the control panel, the PC, or the browser window. Homeowner interaction takes the following form…
![Page 12: Chapter 8 Analysis Engineering](https://reader036.fdocuments.in/reader036/viewer/2022062314/56812c5b550346895d90e705/html5/thumbnails/12.jpg)
![Page 13: Chapter 8 Analysis Engineering](https://reader036.fdocuments.in/reader036/viewer/2022062314/56812c5b550346895d90e705/html5/thumbnails/13.jpg)
Level 2 DFD that refines the monitor sensors process
![Page 14: Chapter 8 Analysis Engineering](https://reader036.fdocuments.in/reader036/viewer/2022062314/56812c5b550346895d90e705/html5/thumbnails/14.jpg)
Control Flow Diagram
State diagram for SafeHome security function
![Page 15: Chapter 8 Analysis Engineering](https://reader036.fdocuments.in/reader036/viewer/2022062314/56812c5b550346895d90e705/html5/thumbnails/15.jpg)
Class-Based Modeling
![Page 16: Chapter 8 Analysis Engineering](https://reader036.fdocuments.in/reader036/viewer/2022062314/56812c5b550346895d90e705/html5/thumbnails/16.jpg)
Identifying Analysis Classes
External entities that produce or consume information
Things that are part of the information domainOccurrences or eventsRoles played by people who interact with the
systemOrganizational unitsPlaces that establish contextStructures that define a class of objects
![Page 17: Chapter 8 Analysis Engineering](https://reader036.fdocuments.in/reader036/viewer/2022062314/56812c5b550346895d90e705/html5/thumbnails/17.jpg)
Class Selection Criteria
1. Retained information
2. Needed services
3. Multiple attributes
4. Common attributes
5. Common operations
6. Essential requirements
![Page 18: Chapter 8 Analysis Engineering](https://reader036.fdocuments.in/reader036/viewer/2022062314/56812c5b550346895d90e705/html5/thumbnails/18.jpg)
Identifying Classes
Potential class Classification Accept / Reject
homeowner role; external entity reject: 1, 2 fail
sensor external entity accept
control panel external entity accept
installation occurrence reject
(security) system thing accept
number, type not objects, attributes reject: 3 fails
master password thing reject: 3 fails
telephone number thing reject: 3 fails
sensor event occurrence accept
audible alarm external entity accept: 1 fails
monitoring service organizational unit; ee reject: 1, 2 fail
![Page 19: Chapter 8 Analysis Engineering](https://reader036.fdocuments.in/reader036/viewer/2022062314/56812c5b550346895d90e705/html5/thumbnails/19.jpg)
Class Diagram
Class diagram for the system class
![Page 20: Chapter 8 Analysis Engineering](https://reader036.fdocuments.in/reader036/viewer/2022062314/56812c5b550346895d90e705/html5/thumbnails/20.jpg)
Class Diagram
Class diagram for FloorPlan
![Page 21: Chapter 8 Analysis Engineering](https://reader036.fdocuments.in/reader036/viewer/2022062314/56812c5b550346895d90e705/html5/thumbnails/21.jpg)
CRC Modeling
A CRC model index card for FloorPlan class
![Page 22: Chapter 8 Analysis Engineering](https://reader036.fdocuments.in/reader036/viewer/2022062314/56812c5b550346895d90e705/html5/thumbnails/22.jpg)
Class Responsibilities
Distribute system intelligence across classes. State each responsibility as generally as possible. Put information and the behavior related to it in the
same class. Localize information about one thing rather than
distributing it across multiple classes. Share responsibilities among related classes, when
appropriate.
![Page 23: Chapter 8 Analysis Engineering](https://reader036.fdocuments.in/reader036/viewer/2022062314/56812c5b550346895d90e705/html5/thumbnails/23.jpg)
Class Collaborations
Relationships between classes: is-part-of — used when classes are part of an
aggregate class. has-knowledge-of — used when one class must
acquire information from another class. depends-on — used in all other cases.
![Page 24: Chapter 8 Analysis Engineering](https://reader036.fdocuments.in/reader036/viewer/2022062314/56812c5b550346895d90e705/html5/thumbnails/24.jpg)
Class Diagrams
Top: MultiplicityBottom: Dependencies
![Page 25: Chapter 8 Analysis Engineering](https://reader036.fdocuments.in/reader036/viewer/2022062314/56812c5b550346895d90e705/html5/thumbnails/25.jpg)
Behavioral Modeling
![Page 26: Chapter 8 Analysis Engineering](https://reader036.fdocuments.in/reader036/viewer/2022062314/56812c5b550346895d90e705/html5/thumbnails/26.jpg)
Identifying Events
A use-case is examined for points of information exchange.
The homeowner uses the keypad to key in a four-digit password. The password is compared with the valid password stored in the system. If the password in incorrect, the control panel will beep once and reset itself for additional input. If the password is correct, the control panel awaits further action.
![Page 27: Chapter 8 Analysis Engineering](https://reader036.fdocuments.in/reader036/viewer/2022062314/56812c5b550346895d90e705/html5/thumbnails/27.jpg)
State Diagram
State diagram for the ControlPanel class
![Page 28: Chapter 8 Analysis Engineering](https://reader036.fdocuments.in/reader036/viewer/2022062314/56812c5b550346895d90e705/html5/thumbnails/28.jpg)
Sequence Diagram
Sequence diagram (partial) for the SafeHome security function