Specification & Design of Real-time Systems

1 Specification & Design of Real-time Systems FA_07_SE_545: ERAU TEAM BLUE Software Requirements Specification Automatic Production Environment Christopher Griffis Steve Harvey Leonardo Matos Jason McGuire Sean Pfeifer Caylyne Shelton Software Requirements Specification : Automatic Production Environment Version: FA_07_SE_545: ERAU TEAM BLUE Date: 10/24/07 ii Document Information Category Information Document ID Software Requirements Specification : Automatic Production Environment Document Owner FA_07_SE_545: ERAU TEAM BLUE Revision History Date Version Description Author 9/20/07 Initial document template Christopher Griffis 10/05/07 Template alterations Christopher Griffis 10/07/07 System requirements Hardware Requirements User Interface Requirements Specific Requirements Sean Pfeifer Jason McGuire Jason McGuire Christopher Griffis 10/08/07 SRS Draft release for peer review Christopher Griffis 10/10/07 SRS version 1 release TEAM BLUE 10/24/07 SRS version 2 release after inspection TEAM BLUE Document Approvals Role Name Signature Date Project Sponsor A.

2 Kornecki 10/24/07 Project Review Group FA_07_SE_545 10/24/07 Project Lead Christopher Griffis 10/24/07 Requirements Lead Sean Pfeifer 10/24/07 Hardware Lead Jason McGuire 10/24/07 Design Lead Caylyne Shelton 10/24/07 Programming Lead Steve Harvey 10/24/07 Quality Manager Leonardo Matos 10/24/07 Preface This Software Requirements Specification loosely follows the layout suggested by IEEE Std. 830-1998, IEEE Recommended Practice for Software Requirements Specifications. However, certain liberties have been taken with the compliance of the format suggested in IEEE Std. 830-1998; the material provided herein is presented to best fit the needs of Software Requirements Specification as a project communication tool and reference document.

3 Software Requirements Specification : Automatic Production Environment Version: FA_07_SE_545: ERAU TEAM BLUE Date: 10/24/07 iii Table of Contents TITLE PAGE ..ii SIGNATURE CHANGE PREFACE ..ii 1. INTRODUCTION ..1 DOCUMENT DEFINITIONS, ACRONYMS, AND 2. OVERALL PRODUCT Models ..3 System User Hardware Software Interfaces ..6 Communications Interfaces ..6 PRODUCT USER Local Web development Standards Compliance ..7 ASSUMPTIONS AND 3. SPECIFIC SYSTEM System Functional System Interface Requirements ..8 Timing Constraints ..8 HARDWARE Hardware Constraints ..8 Hardware Nonfunctional Hardware Functional EXTERNAL INTERFACE User Communications Interfaces.

4 10 Software Requirements Specification : Automatic Production Environment Version: FA_07_SE_545: ERAU TEAM BLUE Date: 10/24/07 iv SOFTWARE Functional Requirement: PROC1 ..12 Functional Requirement: PROC2 ..13 Functional Requirement: PROC3 ..15 Functional Requirement: PROC4 ..16 Functional Requirement: PROC5 ..17 System PERFORMANCE Design SOFTWARE SYSTEM OTHER 4. APPENDICES ..21 DATA USE Use Case Diagram ..23 Use Case Sequence REQUIREMENTS TRACEABILITY Software Requirements Specification : Automatic Production Environment Version: FA_07_SE_545: ERAU TEAM BLUE Date: 10/24/07 v Table of Figures FIGURE 1: AUTOMATIC PRODUCTION ENVIRONMENT - LOGICAL COMPONENT LAYOUT ..4 FIGURE 2: APE SYSTEM CONTEXT FIGURE 3: APE ENTITY-RELATIONSHIP FIGURE 4: DATA FLOW DIAGRAM FOR ALL SOFTWARE FIGURE 5: APE STATE CHART.

5 18 FIGURE 6: DATA FLOW DIAGRAM FOR THE AUTO CONTROL MODE ..19 FIGURE 7: DATA FLOW DIAGRAM FOR THE USER CONTROL MODE ..20 FIGURE 8: APE TIMING DIAGRAM FOR 100MS FIGURE 9: APE USE CASE DIAGRAM ..23 FIGURE 10: SEQUENCE DIAGRAM FOR FIGURE 11: SEQUENCE DIAGRAM FOR FIGURE 12: SEQUENCE DIAGRAM FOR FIGURE 13: SEQUENCE DIAGRAM FOR FIGURE 14: SEQUENCE DIAGRAM FOR FIGURE 15: SEQUENCE DIAGRAM FOR FIGURE 16: APE REQUIREMENTS TRACEABILITY MATRIX, PART FIGURE 17: APE REQUIREMENTS TRACEABILITY MATRIX, PART Software Requirements Specification : Automatic Production Environment Version: FA_07_SE_545: ERAU TEAM BLUE Date: 10/24/07 vi List of Tables TABLE 1: PROCESS Specification FOR [PROC1]..12 TABLE 2: PROCESS Specification FOR [PROC2].

6 13 TABLE 3: RESPONSE LOOKUP TABLE FOR [PROC2] AUTOCONTROL() ..14 TABLE 4: PROCESS Specification FOR [PROC3]..15 TABLE 5: PROCESS Specification FOR [PROC4]..16 TABLE 6: PROCESS Specification FOR [PROC5]..17 TABLE 7: UC1: BELT1 MOVES TABLE 8: UC2: SCANNER SCANS PACKAGE ..25 TABLE 9: UC3: PUSHER PUSHES TABLE 10: UC4: BELT2 MOVES TABLE 11: UC5: USER VIEWS TABLE 12: UC6: USER TAKES Software Requirements Specification : Automatic Production Environment Version: FA_07_SE_545: ERAU TEAM BLUE Date: 10/24/07 Page 1 Software Requirements Specification Automatic Production Environment 1. Introduction SE545: Specification and Design of Real-time Systems is a graduate level software engineering course at Embry-Riddle Aeronautical University.

7 As of the fall of 2007, this course requires the production of software artifacts representing the core operational part of a selected system. [1] The project Automatic Production Environment aims to fulfill these course requirements through a well defined Real-time approach to software development . Purpose The Automatic Production Environment is an industry control system based on Fischertechnik blocks, imitating operation of airport luggage conveyor belt system with a scanning machine. It will simulate the ability of a Real-time software based system to transfer a payload/luggage item down a conveyer belt and scan it (simulating a security scan). A pneumatic/motor driven pushing device will then transfer the luggage to a second belt, which will carry the luggage to a specified final point.

8 The system will have the ability to meet specified transition, motion, and timing requirements provided in the user needs document. Unlike typical academic software projects, this project looks at the problem from a system perspective, and will serve to emphasize Real-time software principles. Document Purpose This document is to act as a project communication tool and reference document, outlining the system, hardware, interface, and software requirements intended for implementation. Stakeholders Sponsor: Dr. Andrew J. Kornecki, Embry-Riddle Aeronautical University Members of TEAM BLUE o Christopher Griffis (Project Lead) o Steve Harvey (Programming Lead) o Leo Matos (Quality Lead) o Jason McGuire (Hardware Lead) o Sean Pfeifer (Requirements Lead) o Caylyne Shelton ( Design Lead) Scope The requirements, diagrams, definitions, and related material in this document address how the system can be composed from the provided hardware parts and run with software following a set of specified characteristics.

9 It makes no assertions or specifications on the details, mechanics, or operations of the individual hardware (Fischertechnik) parts, but only how their composition should behave as a system. Many of the tools, interfaces, protocols, and software programs used in the development of the APE are simply mentioned by name but no specifics are given beyond that. Responses to certain system behavioral deviations are deferred to the Design phase; their declarations are considered outside the scope of this document. Definitions, Acronyms, and Abbreviations [INT_] Any requirements statement beginning with this prefix is an interface requirement. [SYS_] Any requirements statement beginning with this prefix is a system requirement.

10 Software Requirements Specification : Automatic Production Environment Version: FA_07_SE_545: ERAU TEAM BLUE Date: 10/24/07 Page 2 [HW_] Any requirements statement beginning with this prefix is a hardware requirement. [SW_] Any requirements statement beginning with this prefix is a software requirement. [ASMP] Any requirements statement beginning with this prefix is a project level assumption Active a motor is active if the motor is powered and turning APE Automatic Production Environment Auto Control Mode This is the default software mode in which control of the system occurs automatically and without user intervention. BELT1 see Figure 1; the conveyer belt driven by Motor1. BELT2 see Figure 1; the conveyer belt driven by Motor2.